From: Zacchaeus Scheffer <zaccysc@gmail.com>
To: 68811@debbugs.gnu.org
Subject: bug#68811: build hash inconsistency
Date: Mon, 29 Jan 2024 16:38:24 -0800 [thread overview]
Message-ID: <877cjr8xkv.fsf_-_@gmail.com> (raw)
In-Reply-To: <handler.68811.B.170657319418843.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Tue, 30 Jan 2024 00:07:02 +0000")
Some more context might be useful:
Device A (which successfully built qutebrowser over a couple days)
~ $ guix time-machine --commit=deeb7d1f53d7ddfa977b3eadd760312bbd0a2509 -- build qutebrowser --dry-run
/gnu/store/i9ir7a26gv1ii98b4bzgvxp1sx0akind-qutebrowser-2.5.4
Device B (trying to avoid building qutebrowser)
~ $ guix time-machine --commit=deeb7d1f53d7ddfa977b3eadd760312bbd0a2509 -- build qutebrowser --dry-run
The following derivations would be built:
/gnu/store/6n9aq7l5x26xfgrbvws7gvscbzvq5gqn-qutebrowser-2.5.4.drv
/gnu/store/05wj7wf7bdlkm1ar58kpakvp52drrz7p-qtwebengine-5.15.10.drv
/gnu/store/7nmv55qqw62jwzrd650vm434s3wpi7i3-python-pyqtwebengine-5.15.9.drv
I have noticed in the past that sometimes a package gets built twice
with two hashes, so I went back and checked if device A had built the
6n9..5gqn qutebrowser store item reported by B in addition to the
i9i..ind one A was reporting. There was no 6n9..5gqn qutebrowser build
on device A. I don't believe I have never run guix gc on either device.
-Zacchae
next prev parent reply other threads:[~2024-01-30 0:39 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 [this message]
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
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=877cjr8xkv.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).