unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Zacchaeus Scheffer <zaccysc@gmail.com>
To: 68811@debbugs.gnu.org
Subject: bug#68811: build hash inconsistency
Date: Tue, 30 Jan 2024 15:25:09 -0800	[thread overview]
Message-ID: <87eddy76ay.fsf@gmail.com> (raw)
In-Reply-To: <87le867jm0.fsf@gmail.com> (Zacchaeus Scheffer's message of "Tue,  30 Jan 2024 10:37:43 -0800")

Hi Josselin,

Alas, the problem persists ~.~

Device A:
~ $ guix time-machine --commit=deeb7d1f53d7ddfa977b3eadd760312bbd0a2509 -- build qtwebengine --derivations --system=aarch64-linux --no-grafts --dry-run
/gnu/store/gnrk76mlrv3ipm2k3lpmy1533mn9dqc3-qtwebengine-6.5.2.drv

Device B:
~ $ guix time-machine --commit=deeb7d1f53d7ddfa977b3eadd760312bbd0a2509 -- build qtwebengine --derivations --system=aarch64-linux --no-grafts --dry-run
/gnu/store/qpb6d1qqx357rkydk0xv6ail6b9dcqs6-qtwebengine-6.5.2.drv

The fact that Device A finds substitutes for nearly everything while
Device B doesn't makes me think that B is "wrong".  Device A is a 3GiB
RAM Librem 5 (made in China), and Device B is a 4GiB RAM Liberty Phone
(made in USA).  (Maybe US backdoor bots need to up their stealth game?)
You can find info on how I set up guix at
https://zacchae.us/guix-usd.org, specifically the section "Setting up
guix home"


-Zacchae


PS - I see your response on issues.guix.gnu.org, but didn't get an
email.  I thought submitting bugs automatically subscribed me?




  parent reply	other threads:[~2024-01-30 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  0:06 bug#68811: build hash inconsistency Zacchaeus Scheffer
     [not found] ` <handler.68811.B.170657319418843.ack@debbugs.gnu.org>
2024-01-30  0:38   ` Zacchaeus Scheffer
2024-01-30  7:06     ` Saku Laesvuori via Bug reports for GNU Guix
2024-01-30 18:37       ` Zacchaeus Scheffer
2024-01-30 21:59         ` Josselin Poiret via Bug reports for GNU Guix
2024-01-30 23:25         ` Zacchaeus Scheffer [this message]
2024-01-31 18:34           ` Zacchaeus Scheffer

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=87eddy76ay.fsf@gmail.com \
    --to=zaccysc@gmail.com \
    --cc=68811@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).