|
From: | GNU bug Tracking System |
Subject: | bug#58561: closed (Source hash mismatch with aggregator + possible guix bug with hashes.) |
Date: | Sat, 13 May 2023 01:57:01 +0000 |
Your message dated Sat, 13 May 2023 01:56:23 +0000 with message-id <fdf80509-a5c9-77bf-df2a-040dc70c0a5e@brendan.scot> and subject line Source hash mismatch with aggregator + possible guix bug with hashes. has caused the debbugs.gnu.org bug report #58561, regarding Source hash mismatch with aggregator + possible guix bug with hashes. to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 58561: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58561 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Source hash mismatch with aggregator + possible guix bug with hashes. Date: Sun, 16 Oct 2022 14:42:14 +1100 I'm getting this after the recent updates:sha256 hash mismatch for /gnu/store/iv6ixlrvh0swq22fjal0cbfbr9ayaq7m-akregator-22.04.3.tar.xz:expected hash: 1yy5c29zxpli4cddknmdvjkgii3j7pvw6lhwqfrqjc8jh83gm8f8 actual hash: 08n713271i7ifnbrgwrqmxvcpvj45wfqjiidw8zf9rpwxg2m2m9gHowever 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'? I've tried with both guix pull local repo and building from source. Is there a bug with how guix is reading/writing sha256 hashes?
--- End Message ---
--- Begin Message ---Subject: Source hash mismatch with aggregator + possible guix bug with hashes. Date: Sat, 13 May 2023 01:56:23 +0000 Issue was fixed and Tobias explained the hash issue.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |