Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xbps-src zap doesn't remove cross status files (e.g. .xbps-aarch64-musl-done)
Date: Mon, 21 Oct 2019 18:55:23 +0200	[thread overview]
Message-ID: <20191021165523.OEBSueT7wshVhkNxKtVv427n3ldxzqE6kmHuXSAZpwA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14476@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

Closed issue by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/issues/14476

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
* package:  
  *affected package(s) including the version*

### Expected behavior

`xbps-src zap` should remove every file in the zapped masterdir that is managed by xbps-src.

### Actual behavior

Currently the `.xbps-${CROSS_ARCH}-done` files won't get removed, and therefore trying to cross compile from this masterdir will fail.

### Steps to reproduce the behavior

```./xbps-src -m masterdir-test binary-bootstrap
./xbps-src -m masterdir-test extract kcoreaddons -a aarch64
./xbps-src -m masterdir-test zap
./xbps-src -m masterdir-test binary-bootstrap
./xbps-src -m masterdir-test  pkg kcoreaddons -a aarch64 <- will fail
```


      reply	other threads:[~2019-10-21 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 18:59 [ISSUE] xbps-src zap doesn't " voidlinux-github
2019-10-21 16:55 ` voidlinux-github [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191021165523.OEBSueT7wshVhkNxKtVv427n3ldxzqE6kmHuXSAZpwA@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).