all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Aleksandr Vityazev <avityazev@posteo.org>, guix-devel@gnu.org
Subject: Re: rrdtool hash mismatch
Date: Wed, 12 Apr 2023 23:12:01 +0200	[thread overview]
Message-ID: <871qkovm8u.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87y1mxj5tp.fsf@posteo.org>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Hi,

Aleksandr Vityazev <avityazev@posteo.org> writes:

> Hi,
>
> rrdtool package has not been updated for several years and according to
> ci.guix.gnu.org builds normally, but if you run:
>
> ./pre-inst-env guix build --no-substitutes --check --no-grafts rrdtool
>
> it outputs an error
> sha256 hash mismatch for /gnu/store/icyq4d3fsbbf2yw3dmg7cxgb05qzfd3q-rrdtool-1.7.2.tar.gz:
> expected hash: 1nsqra0g2nja19akmf9x5y9hhgc35ml3w9dcdz2ayz7zgvmzmm6d1
> actual hash: 029r3h7l06m3sy9q0hr2krvinhzkqvyl14wj7qjck79bm7rdvp48
>
> which looks strange to me. Maybe it's not, but I haven't figured out
> why?

The upstream-provided tarball has probably been changed on the server
without a version bump.  The reason why you can still use it with
substitutes is that Guix just uses the version that's built with the old
tarball because we know its hash.  When you try to download it from
upstream, Guix rightfully complains that the hash has changed and
refuses to go forward!

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2023-04-12 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 18:47 rrdtool hash mismatch Aleksandr Vityazev
2023-04-12 21:12 ` Josselin Poiret [this message]
2023-04-13  9:52 ` Simon Tournier
2023-04-13  9:59   ` Simon Tournier

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=871qkovm8u.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=avityazev@posteo.org \
    --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.