all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 74797@debbugs.gnu.org
Subject: bug#74797: linux-libre 6.11.11 fails to build on aarch64 (drivers/clk/meson/gxbb.c)
Date: Sun, 15 Dec 2024 13:11:40 -0500	[thread overview]
Message-ID: <Z18b3ErZe6sX9eSh@jasmine.lan> (raw)
In-Reply-To: <87ed29bh66.fsf@contorta>

On Sat, Dec 14, 2024 at 10:21:05PM -0800, Vagrant Cascadian wrote:
> Well, it only hgappened once, and with the same commit, it successfully
> regenerated the tarball and everything was fine...

Understood. Unfortunately I think it suggests a hardware malfunction,
although it could be a software bug.

> FWIW, the guix pull'ed commits where it happened were:
> 
> 68d3c1adcb4d2667ad053aacf5b2ab6602377475
> 6f8c8a86d827627f503a803381bce7fbcf8f39a0
> 
> I cannot remember off the top of my head weather it was the upstream
> tarball or:
> 
> /gnu/store/3aawi9saa92n35kknxv1m97lhjkx7j8g-linux-libre-6.11.11-guix.tar.zst

Okay, thanks. I did check on ci.guix.gnu.org, and this file does not
exist in the store.

> But I removed the tarballs with 'guix gc' and then everything was fine
> on the next tries after it redownloaded and regenerated the new
> tarballs. So, I daresay I have destroyed the evidence...
> 
> If i happens again, I can do more research.

Thanks, I'd appreciate it!




      reply	other threads:[~2024-12-15 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 18:36 bug#74797: linux-libre 6.11.11 fails to build on aarch64 (drivers/clk/meson/gxbb.c) Vagrant Cascadian
2024-12-12  8:37 ` bug#74797: - " Vincent Legoll
2024-12-14  7:15   ` bug#74797: " Maxim Cournoyer
2024-12-14  7:56   ` bug#74797: - " Vagrant Cascadian
2024-12-14 11:12     ` Vincent Legoll
2024-12-15  1:03       ` Maxim Cournoyer
2024-12-15  4:51 ` bug#74797: " Leo Famulari
2024-12-15  6:21   ` Vagrant Cascadian
2024-12-15 18:11     ` Leo Famulari [this message]

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=Z18b3ErZe6sX9eSh@jasmine.lan \
    --to=leo@famulari.name \
    --cc=74797@debbugs.gnu.org \
    --cc=vagrant@debian.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.