all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: X <volf.tomas@gmail.com>
To: 66837@debbugs.gnu.org
Subject: bug#66837: Some kernels cannot be built
Date: Mon, 30 Oct 2023 13:42:55 +0000	[thread overview]
Message-ID: <CAJZHhuRcF2c6sJVf-LtptvJv9niRf00LODAcv2R8ZEY=waRqJg@mail.gmail.com> (raw)

Hello,

there is an error when trying to reconfigure using latest guix when
building linux-libre-lts:

\sha256 hash mismatch for
/gnu/store/dfv5mppsr8z76pj37km0p11aqw721qia-linux-libre-deblob-check-6.1.60-gnu:
  expected hash: 1c73516nbhnz0cxjz38b5794dxygb8sznv9idiibw7ablmjbhd11
  actual hash:   1hdibv43xbn1lv83i6qjgfmf1bvqxvq17fryfsq4r4sjgs9212js
hash mismatch for store item
'/gnu/store/dfv5mppsr8z76pj37km0p11aqw721qia-linux-libre-deblob-check-6.1.60-gnu'


I believe the commit
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=kernel-updates&id=d75760a3fc281a27c6d3ec02e9bac1275c1d6c25
failed to update the deblob checksums.

From CI it seems to affect multiple versions.

Cheers,
T.

-- 
Tomas P4l4cl][n Volf
-- "There are only 10 types of people in the world: Those who
understand binary, and those who don't."




             reply	other threads:[~2023-10-31 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 13:42 X [this message]
2023-10-30 22:26 ` bug#66837: [PATCH 0/4] Some kernels cannot be built Wilko Meyer
2023-10-30 22:26   ` bug#66837: [PATCH 1/4] gnu: deblob-scripts 6.5: Update hash Wilko Meyer
2023-10-30 22:26   ` bug#66837: [PATCH 2/4] gnu: deblob-scripts 6.1: " Wilko Meyer
2023-10-30 22:26   ` bug#66837: [PATCH 3/4] gnu: deblob-scripts 5.15: " Wilko Meyer
2023-10-30 22:26   ` bug#66837: [PATCH 4/4] gnu: deblob-scripts 5.10: " Wilko Meyer
2023-11-04 18:47     ` Leo Famulari
2023-11-03 23:54   ` bug#66837: [PATCH 0/4] Some kernels cannot be built Leo Famulari

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='CAJZHhuRcF2c6sJVf-LtptvJv9niRf00LODAcv2R8ZEY=waRqJg@mail.gmail.com' \
    --to=volf.tomas@gmail.com \
    --cc=66837@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 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.