From: Tobias Geerinckx-Rice <me@tobias.gr>
To: contact.ng0@cryptolab.net
Cc: guix-devel@gnu.org
Subject: Re: hash of fish is wrong.
Date: Tue, 14 Feb 2017 20:14:43 +0100 [thread overview]
Message-ID: <50b7eab5-c8e6-0eb4-3dc1-570e0761255f@tobias.gr> (raw)
In-Reply-To: <20170214171922.bxcegs7o7e76oa7a@wasp>
[-- Attachment #1.1: Type: text/plain, Size: 1219 bytes --]
ng0 (again, and this time the list),
Thanks for catching and reporting this.
On 14/02/17 18:19, ng0 wrote:
> can someone else check which hash should be the correct one? I think
> 19djav128nkhjxgfhwhc32i5y9d9c3karbh5yg67kqrdranyvh7q is correct.
We're both right! Yay! It's a Valentine's day miracle:
$ ~/guix/pre-inst-env guix hash /gnu/store/*-fish-2.5.0.tar.gz
0kn2n9qr9cksg2cl78f3w0yd24368d35djhi6w5x3gbdxk23ywq3
$ boring-old-wget https://fishshell.com/files/2.5.0/fish-2.5.0.tar.gz
$ guix hash fish-2.5.0.tar.gz
19djav128nkhjxgfhwhc32i5y9d9c3karbh5yg67kqrdranyvh7q
Hm. Did I mis-label an old fish-2.4.0 tarball by mistake when updating?
Nope:
$ tar tf /gnu/store/*-fish-2.5.0.tar.gz | head -n1
fish-shell-2.5.0/
$ tar tf ~/fish-2.5.0.tar.gz | head -n1
fish-2.5.0/
What the—
Once again, hashing all the things catches a sneaky upstream
dirty-handed. The original fish-2.5.0.tar.gz lacked a configure script
(see commit 89eb56f05fa1561b09d1050147d968b98a16b07a). Apparently, the
way to fix that is by silently replacing your tarball in-place.
Anyone want to scan a 20,357-line diff for a back door before I push an
update?
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]
next prev parent reply other threads:[~2017-02-14 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 17:19 hash of fish is wrong ng0
2017-02-14 19:14 ` Tobias Geerinckx-Rice [this message]
2017-02-14 19:27 ` Leo Famulari
2017-02-14 19:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50b7eab5-c8e6-0eb4-3dc1-570e0761255f@tobias.gr \
--to=me@tobias.gr \
--cc=contact.ng0@cryptolab.net \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.