From: Simon Tournier <zimon.toutoune@gmail.com>
To: 65979@debbugs.gnu.org
Subject: bug#65979: incorrect “guix hash” for FastQC
Date: Thu, 14 Sep 2023 18:46:05 +0200 [thread overview]
Message-ID: <87v8ccd7oy.fsf@gmail.com> (raw)
Hi,
Currently Guix stores in its source the hash
00y9drm0bkpxw8xfl8ysss18jmnhj8blgqgr6fpa58rkpfcbg8qk and this has not
changed since February (Guix revision
b6a4fbb488f1f539ae45ed7924c9af8905fa0d8b).
Well, because the origin contains a snippet, “guix build -S” does not
return the result of the fixed derivation. Instead, it is one or the other:
--8<---------------cut here---------------start------------->8---
$ guix gc -R $(guix build -S fastqc -d) | grep checkout.drv
/gnu/store/8gxx74w8pa0fx74lx1ka654rhyyr51cs-fastqc-0.11.9-checkout.drv
/gnu/store/7rdcyl7iq00xfdwh6azgmc3i7mr2769b-fastqc-0.11.9-checkout.drv
--8<---------------cut here---------------end--------------->8---
Let pick the correct one and I get:
--8<---------------cut here---------------start------------->8---
$ guix hash -rx $(guix build /gnu/store/8gxx74w8pa0fx74lx1ka654rhyyr51cs-fastqc-0.11.9-checkout.drv)
0jyk90kg6s62w3dn6qjx9nrawjs12qx172lii0yxbvsfylhnx479
--8<---------------cut here---------------end--------------->8---
Oh, it is not the expected result! Instead, I have to omit the option
’-x’:
--8<---------------cut here---------------start------------->8---
$ guix hash -r $(guix build /gnu/store/8gxx74w8pa0fx74lx1ka654rhyyr51cs-fastqc-0.11.9-checkout.drv)
00y9drm0bkpxw8xfl8ysss18jmnhj8blgqgr6fpa58rkpfcbg8qk
--8<---------------cut here---------------end--------------->8---
Hum, I am missing something…
Let clone from upstream.
--8<---------------cut here---------------start------------->8---
$ git clone https://github.com/s-andrews/FastQC
$ git -C FastQC checkout v0.11.9
$ guix hash -rx FastQC
0jyk90kg6s62w3dn6qjx9nrawjs12qx172lii0yxbvsfylhnx479
--8<---------------cut here---------------end--------------->8---
Ah… incorrect but consistent with previously. The question is why is
this following,
--8<---------------cut here---------------start------------->8---
$ mv FastQC/.git bye-bye
$ guix hash -r FastQC
00y9drm0bkpxw8xfl8ysss18jmnhj8blgqgr6fpa58rkpfcbg8qk
--8<---------------cut here---------------end--------------->8---
is correct? And obviously without .git we get the same hash just as
above,
--8<---------------cut here---------------start------------->8---
$ guix hash -rx FastQC
0jyk90kg6s62w3dn6qjx9nrawjs12qx172lii0yxbvsfylhnx479
--8<---------------cut here---------------end--------------->8---
Any idea?
Cheers,
simon
next reply other threads:[~2023-09-14 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 16:46 Simon Tournier [this message]
2023-09-26 13:00 ` bug#65979: incorrect “guix hash” for FastQC Simon Tournier
2023-09-26 13:34 ` Ludovic Courtès
2023-09-26 16:23 ` Simon Tournier
2023-10-01 15:07 ` Ludovic Courtès
2023-10-01 15:24 ` Simon Tournier
2023-10-17 17:56 ` Simon Tournier
2023-09-26 13:29 ` 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=87v8ccd7oy.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=65979@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).