From: zimoun <zimon.toutoune@gmail.com>
To: mail@brendan.scot, 58561@debbugs.gnu.org
Cc: phodina <phodina@protonmail.com>, Marius Bakke <marius@gnu.org>
Subject: bug#58561: Source hash mismatch with aggregator + possible guix bug with hashes.
Date: Mon, 17 Oct 2022 10:44:33 +0200 [thread overview]
Message-ID: <87y1ten8jy.fsf@gmail.com> (raw)
In-Reply-To: <0df50579-d645-5a43-d558-4c49e503bb57@brendan.scot>
Hi,
I am also confused.
On dim., 16 oct. 2022 at 14:42, Brendan Tildesley <mail@brendan.scot> wrote:
> sha256 hash mismatch for
> /gnu/store/iv6ixlrvh0swq22fjal0cbfbr9ayaq7m-akregator-22.04.3.tar.xz:
> expected hash: 1yy5c29zxpli4cddknmdvjkgii3j7pvw6lhwqfrqjc8jh83gm8f8
> actual hash: 08n713271i7ifnbrgwrqmxvcpvj45wfqjiidw8zf9rpwxg2m2m9g
>
>
> However what concerned me more is that when I look in the source code it
> looks like this:
>
> (sha256
> (base32 "9yy5c29zxpli4cddknmdvjkgii3j7pvw6lhwqfrqjc8jh83gm8f8"))
>
> Notice how at the start its a '9', not a '1'?
Indeed, commit 6971feca53a19d60fdd2b39fb2a8966ccf1d6598 pushed on
core-updates reads,
--8<---------------cut here---------------start------------->8---
(define-public akregator
(package
(name "akregator")
- (version "21.12.3")
+ (version "22.04.3")
(source
(origin
(method url-fetch)
(uri (string-append "mirror://kde/stable/release-service/" version
"/src/akregator-" version ".tar.xz"))
(sha256
- (base32 "1yy5c29zxpli4cddknmdvjkgii3j7pvw6lhwqfrqjc8jh83gm8f8"))))
+ (base32 "9yy5c29zxpli4cddknmdvjkgii3j7pvw6lhwqfrqjc8jh83gm8f8"))))
(build-system qt-build-system)
--8<---------------cut here---------------end--------------->8---
> Is there a bug with how guix is reading/writing sha256 hashes?
Is it a mistake here? A human-typo replacing ’1’ by ’9’? Or
something else? Petr?
Then, indeed KDE did a in-place replacement since the hash is now,
--8<---------------cut here---------------start------------->8---
$ guix download https://mirrors.xtom.de/kde/stable/release-service/22.04.3/src/akregator-22.04.3.tar.xz
Starting download of /tmp/guix-file.JTZn04
From https://mirrors.xtom.de/kde/stable/release-service/22.04.3/src/akregator-22.04.3.tar.xz...
….04.3.tar.xz 2.2MiB 22.2MiB/s 00:00 [##################] 100.0%
/gnu/store/w4jqrza9ffsflim5ilwq7jr75rxicn1g-akregator-22.04.3.tar.xz
08n713271i7ifnbrgwrqmxvcpvj45wfqjiidw8zf9rpwxg2m2m9g
--8<---------------cut here---------------end--------------->8---
as submitted in patch#57608 [1].
1: <https://issues.guix.gnu.org/57608#1>
Cheers,
simon
next prev parent reply other threads:[~2022-10-17 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 3:42 bug#58561: Source hash mismatch with aggregator + possible guix bug with hashes Brendan Tildesley
2022-10-16 4:13 ` bug#58561: [PATCH 1/2] gnu: akregator: Correct source hash 'Brendan Tildesley
2022-10-16 4:33 ` bug#58561: [PATCH 2/2] gnu: akregator: Fix build 'Brendan Tildesley
2022-10-16 5:39 ` phodina via Bug reports for GNU Guix
2022-10-17 11:42 ` Marius Bakke
2022-10-17 21:19 ` Brendan Tildesley
2022-10-16 9:45 ` bug#58561: Source hash mismatch with aggregator + possible guix bug with hashes Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-17 8:49 ` zimoun
2022-10-17 8:44 ` zimoun [this message]
2022-10-17 18:29 ` phodina via Bug reports for GNU Guix
2023-05-13 1:56 ` Brendan Tildesley
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=87y1ten8jy.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=58561@debbugs.gnu.org \
--cc=mail@brendan.scot \
--cc=marius@gnu.org \
--cc=phodina@protonmail.com \
/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).