From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 40017-done@debbugs.gnu.org
Subject: bug#40017: hplip-3.20.2 source tarball hash mismatch
Date: Tue, 10 Mar 2020 22:05:03 +0100 [thread overview]
Message-ID: <87blp3j4zk.fsf@nckx> (raw)
In-Reply-To: <87fteg12tj.fsf@netris.org>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
Mark,
Mark H Weaver 写道:
> The following commit updated hplip to 3.20.2, but the actual
> hash of the
> source tarball does not match the expected hash in the commit.
[…]
> sha256 hash mismatch for
> /gnu/store/xnqrxpngp4505228zib9zp8b5n7v4ri6-hplip-3.20.2.tar.gz:
> expected hash:
> 1hkiyj29vzmz14cy68g94i617ymxinzvjvcsfdd78kcbd1s9vi4h
> actual hash:
> 00vcbpnp478l2v61mlxb4kr6q3gzkxspm4lwfky39f6ck72pqxb7
Thanks. This happens, although I wish it would stop.
The differences are: timestamps, differing .ppd.gz file order in
.inc files, and a modified pre-compiled binary (locatedriver).
Luckily, the latter is snippeted out, leaving only harmless
changes AFAICT.
Here's the original diff, although the list will probably scrub
it:
[-- Attachment #1.2: hplipdiff.lz --]
[-- Type: application/octet-stream, Size: 145051 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 225 bytes --]
The world would be a better place if $big_hosters didn't allow
rewriting tarballs in-place. But then people would upload their
privkeys and cry.
Fixed with 6048241f10210c79925ca40b75c8697d2b2a5848.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-03-10 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 18:28 bug#40017: hplip-3.20.2 source tarball hash mismatch Mark H Weaver
2020-03-10 21:05 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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=87blp3j4zk.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=40017-done@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=mhw@netris.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).