Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Should ConsoleKit2 be removed?
Date: Thu, 02 Apr 2020 19:12:29 +0200	[thread overview]
Message-ID: <20200402171229.XT0XpwPocOKXlmVIxgC8mfU-XBgxVkEkxTUq6yhMVrc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20577@inbox.vuxu.org>

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

New comment by the-maldridge on void-packages repository

https://github.com/void-linux/void-packages/issues/20577#issuecomment-607976401

Comment:
Since the clean has to be run from an authoritative location, it can only clean things that that location is authoratative for.  In the current version there's an ARCHS variable up at the top, which needs to be set to "armv6l armv7l x86_64 i686" in one place "aarch64 aarch64-musl" in another, and "armv7l-musl armv6l-musl x86_64-musl" in a third.

  parent reply	other threads:[~2020-04-02 17:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 16:08 [ISSUE] " ericonr
2020-04-02 16:15 ` xtraeme
2020-04-02 16:22 ` xtraeme
2020-04-02 16:24 ` ericonr
2020-04-02 16:27 ` Duncaen
2020-04-02 16:29 ` xtraeme
2020-04-02 16:30 ` xtraeme
2020-04-02 16:31 ` xtraeme
2020-04-02 16:32 ` xtraeme
2020-04-02 16:32 ` Duncaen
2020-04-02 16:32 ` xtraeme
2020-04-02 16:33 ` Duncaen
2020-04-02 16:34 ` xtraeme
2020-04-02 16:35 ` xtraeme
2020-04-02 16:40 ` xtraeme
2020-04-02 16:42 ` xtraeme
2020-04-02 16:42 ` Duncaen
2020-04-02 16:42 ` xtraeme
2020-04-02 16:54 ` xtraeme
2020-04-02 17:00 ` the-maldridge
2020-04-02 17:02 ` xtraeme
2020-04-02 17:06 ` xtraeme
2020-04-02 17:12 ` the-maldridge [this message]
2020-04-02 17:16 ` xtraeme
2020-04-02 17:25 ` xtraeme
2020-04-12  0:00 ` ericonr
2020-07-14 18:40 ` [ISSUE] [CLOSED] " Chocimier
2020-07-14 18:40 ` Chocimier

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=20200402171229.XT0XpwPocOKXlmVIxgC8mfU-XBgxVkEkxTUq6yhMVrc@z \
    --to=the-maldridge@users.noreply.github.com \
    --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).