unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brendan Tildesley <mail@brendan.scot>
To: 58561@debbugs.gnu.org
Subject: bug#58561: Source hash mismatch with aggregator + possible guix bug with hashes.
Date: Sun, 16 Oct 2022 14:42:14 +1100	[thread overview]
Message-ID: <0df50579-d645-5a43-d558-4c49e503bb57@brendan.scot> (raw)

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: 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'?

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?





             reply	other threads:[~2022-10-16  3:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  3:42 Brendan Tildesley [this message]
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
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=0df50579-d645-5a43-d558-4c49e503bb57@brendan.scot \
    --to=mail@brendan.scot \
    --cc=58561@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).