From: Simon Tournier <zimon.toutoune@gmail.com>
To: Jeremiah@pdp10.guru, 70838@debbugs.gnu.org
Subject: bug#70838: guix pull fails
Date: Mon, 13 May 2024 16:30:59 +0200 [thread overview]
Message-ID: <87msot3hss.fsf@gmail.com> (raw)
In-Reply-To: <874jb8t0pu.fsf@ITSx01.pdp10.guru>
Hi,
On mer., 08 mai 2024 at 22:09, Jeremiah@pdp10.guru wrote:
> ──⚙ guix pull [4/559]
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
> Authenticating channel 'guix', commits 9edb3f6 to 7b7f299 (1,287 new commits)...
> Building from this channel:
> guix https://git.savannah.gnu.org/git/guix.git 7b7f299
[...]
> building /gnu/store/8379qa0y6s7ssjr8gplm5fyw9r5pnxhn-nss-3.99.0.drv...
> \ 'check' phasebuild-log 30161 101
> [ OK ] Pkcs11ModuleTest.ListSlots (1 ms)
> [ RUN ] Pkcs11ModuleTest.PublicCertificatesToken
> - 'check' phasebuild-log 30161 121
> [ OK ] Pkcs11ModuleTest.PublicCertificatesToken (1 ms)
> [ RUN ] Pkcs11ModuleTest.PublicCertificatesTokenLookup
> \ 'check' phaseBacktrace:
[...]
> failed to compute the derivation for Guix (version: "7b7f299bb493e485c5534b8c554e51d4f3a8c026"; system: "x86_64-linux";
> host version: "0f68306268773f0eaa4327e1f6fdcb39442e4a34"; pull-version: 1).
> Please report the COMPLETE output above by email to <bug-guix@gnu.org>.
Well, first the authenticating message is weird because:
9edb3f66fd807b096b48283debdcddccfea34bad
AuthorDate: Tue May 26 22:30:51 2020 +0200
CommitDate: Tue May 26 22:30:51 2020 +0200
and
7b7f299bb493e485c5534b8c554e51d4f3a8c026
AuthorDate: Wed May 8 15:51:45 2024 +0200
CommitDate: Wed May 8 15:51:45 2024 +0200
Therefore, something seems unexpected here. I am doubtful that the
message is accurate.
Second, the error message seems more accurate,
0f68306268773f0eaa4327e1f6fdcb39442e4a34
AuthorDate: Tue Apr 2 18:54:06 2024 +0200
CommitDate: Sat Apr 20 10:35:35 2024 +0200
I.e., with the 1,287 new commits.
That’s said, could you confirm (guix describe) that you are currently
pulling from 0f68306268773f0eaa4327e1f6fdcb39442e4a34?
I think ’nss’ is substitutable, so I guess you are rebuilding from
source, right?
Well, the build of ’nss’ works for me.
--8<---------------cut here---------------start------------->8---
$ guix build /gnu/store/8379qa0y6s7ssjr8gplm5fyw9r5pnxhn-nss-3.99.0.drv --check
[...]
successfully built /gnu/store/8379qa0y6s7ssjr8gplm5fyw9r5pnxhn-nss-3.99.0.drv
guix build: error: derivation `/gnu/store/8379qa0y6s7ssjr8gplm5fyw9r5pnxhn-nss-3.99.0.drv' may not be deterministic: output `/gnu/store/wkdc0z86av7jfkig7g4xphp6k52y82am-nss-3.99.0' differs
--8<---------------cut here---------------end--------------->8---
Hum, I do not know what could be the origin of the failure. Maybe on
your side (free space). Or maybe hardware specific?
Cheers,
simon
next prev parent reply other threads:[~2024-05-13 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 22:09 bug#70838: guix pull fails Jeremiah
2024-05-09 21:22 ` jbranso--- via Bug reports for GNU Guix
2024-05-10 16:40 ` Jeremiah
2024-05-11 13:50 ` jbranso--- via Bug reports for GNU Guix
2024-05-13 20:55 ` Jeremiah
2024-05-13 14:30 ` Simon Tournier [this message]
2024-05-13 17:45 ` Christopher Baines
2024-05-14 9:24 ` Simon Tournier
2024-05-13 21:05 ` Jeremiah
2024-05-14 9:27 ` Simon Tournier
2024-05-15 1:09 ` Jeremiah
2024-05-15 16:41 ` 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
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=87msot3hss.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=70838@debbugs.gnu.org \
--cc=Jeremiah@pdp10.guru \
/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).