From: Christopher Howard <christopher@librehacker.com>
To: Brendan Tildesley <btild@mailbox.org>,
"48373@debbugs.gnu.org" <48373@debbugs.gnu.org>
Subject: bug#48373: vice: processor dependency
Date: Wed, 12 May 2021 07:30:19 -0800 [thread overview]
Message-ID: <e66972afe58959cf5bedaebe9524b157b3bd4974.camel@librehacker.com> (raw)
In-Reply-To: <802557135.259431.1620832086709@office.mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Hello, I ran the following:
guix gc -D $(guix build --no-grafts vice); guix build --no-substitutes
vice
guix challenge vice
The result of the last command was
/gnu/store/ixsr68sfkyfvp66mzg6291sv2gbdwvzc-vice-3.5 contents differ:
local hash: 1gw2m26g506fivlki829h4ljjxs4s6c4c9hyi8bdzl1h4kw4qz6l
https://ci.guix.gnu.org/nar/lzip/ixsr68sfkyfvp66mzg6291sv2gbdwvzc-vice-3.5
: 0bsm4lf5pbfpq6q82jbvv0c9swpais572bf4lhbbrn2i9kld1krm
differing files:
/bin/xscpu64
/bin/vsid
/bin/x64sc
/bin/xplus4
/bin/x128
/bin/xcbm5x0
/bin/xvic
/bin/xcbm2
/bin/xpet
1 store items were analyzed:
- 0 (0.0%) were identical
- 1 (100.0%) differed
- 0 (0.0%) were inconclusive
--
Christopher Howard
blog: https://librehacker.com
social: https://gnusocial.club/librehacker
On Wed, 2021-05-12 at 17:08 +0200, Brendan Tildesley wrote:
> guix gc -D $(guix build --no-grafts vice); guix build --no-
> substitutes vice
[-- Attachment #2: Type: text/html, Size: 1804 bytes --]
next prev parent reply other threads:[~2021-05-12 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 2:33 bug#48373: vice: processor dependency? Christopher Howard
2021-05-12 13:44 ` Christopher Howard
2021-05-12 15:08 ` bug#48373: vice: processor dependency Brendan Tildesley via Bug reports for GNU Guix
2021-05-12 15:30 ` Christopher Howard [this message]
2021-05-12 15:38 ` Brendan Tildesley via Bug reports for GNU Guix
2021-05-12 16:21 ` bug#48373: vice: processor dependency? Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e66972afe58959cf5bedaebe9524b157b3bd4974.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=48373@debbugs.gnu.org \
--cc=btild@mailbox.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).