From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 35621@debbugs.gnu.org
Subject: bug#35621: Simplify comparing guix challenge results
Date: Tue, 07 May 2019 11:02:05 -0700 [thread overview]
Message-ID: <87sgtqxhwi.fsf@yucca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
I'd like to see a simpler process for comparing challenge results
producing differences.
While the manual documents how to compare a failing challenge result
$ wget -q -O - https://ci.guix.info/nar/…-git-2.5.0 \
| guix archive -x /tmp/git
$ diff -ur --no-dereference /gnu/store/…-git.2.5.0 /tmp/git
To check "git", you need to run "guix challenge git" and if the results
are inconclusive, manually cut-and-paste the correct URL(s) from the
challenge output and manually download it and unpack with guix archive,
and then run a comparison utility...
What about an argument to "guix challenge" that handles the downloading
and unpacking to a temporary directory, and possibly another that also
runs a comparison tool against the results. Maybe something like:
$ guix challenge --download-differences
/tmp/git-XXXXX/SUBSTITTE-X/...-git-2.5.0
/tmp/git-XXXXX/SUBSTITUTE-Y/...-git-2.5.0
/gnu/store/...-git-2.5.0
Downloads and unpacks the substitutes, and outputs the resulting
directories.
$ guix challenge --download-differences --compare-with="diffoscope ..."
This would do the above, plus run diffoscope on the directories
... though I think diffoscope can only compare between two things at a
time... so that might get difficult if many substitutes return results.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2019-05-07 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:02 Vagrant Cascadian [this message]
2019-05-08 13:04 ` bug#35621: Simplify comparing guix challenge results Ludovic Courtès
2019-05-08 20:28 ` Ricardo Wurmus
2019-12-09 11:02 ` Ludovic Courtès
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=87sgtqxhwi.fsf@yucca \
--to=vagrant@reproducible-builds.org \
--cc=35621@debbugs.gnu.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).