unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 50264@debbugs.gnu.org, Lars-Dominik Braun <lars@6xq.net>
Subject: bug#50264: ca-certificate-bundle fails to build
Date: Tue, 14 Sep 2021 12:04:22 -0400	[thread overview]
Message-ID: <YUDIBgbIIUOgKZ96@jasmine.lan> (raw)
In-Reply-To: <87a6kf5mpo.fsf@gnu.org>

On Tue, Sep 14, 2021 at 03:08:19PM +0200, Ludovic Courtès wrote:
> Hi,
> 
> Lars-Dominik Braun <lars@6xq.net> skribis:
> 
> > Failure:
> > /gnu/store/kxkxji6m101ylgpa82jmxvmy5szpvk1k-ca-certificate-bundle.drv
> > /gnu/store/wahy9p8985vbcibwwjk3p73hxh82f90v-ca-certificate-bundle-builder
> >
> > Success:
> > /gnu/store/rx6pqcpgwcyl6spfi8acgjzksrpqhac1-ca-certificate-bundle.drv
> > /gnu/store/wahy9p8985vbcibwwjk3p73hxh82f90v-ca-certificate-bundle-builder
> >
> > (Yes, exactly the same builder input hash. I double-checked.)
> 
> As discussed on IRC, I stumbled upon this bug while running:
> 
>   ./pre-inst-env guix system vm gnu/system/examples/desktop.tmpl
> 
> on commit 580984f2417853379d98ea927fd95c0f0fbe2c97.
> 
> The first attempt downloaded lots of substitutes and produced, as in
> your case, a broken ca-certificate-bundle.drv: the ‘-builder’ script is
> correct, but there are only ~80 derivation inputs instead of ~230.
> 
> The second run right after that produced the correct
> ca-certificate-bundle.drv: same ‘-builder’ script, but all the
> derivation inputs were there, including glibc-utf8-locales.drv.
> 
> I’ve tried to reproduce it running GC during or before the command, to
> no avail so far.  If someone has an easy and reliable way to reproduce
> it, please share!
> 
> I don’t have a good hypothesis so far as to where things go wrong…

I wonder if the problem began after the introduction of
bordeaux.guix.gnu.org, and if everyone who experiences the bug is using
both substitute servers.

I can't imagine what the actual problem is, but it does sound like the
dependency graph has somehow diverged...




  reply	other threads:[~2021-09-14 16:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30  8:12 bug#50264: ca-certificate-bundle fails to build Lars-Dominik Braun
2021-09-04 16:27 ` Ludovic Courtès
2021-09-06 11:22   ` Lars-Dominik Braun
2021-09-10 16:04     ` Ludovic Courtès
2021-09-10 16:17       ` Jack Hill
2021-09-11  7:08       ` Lars-Dominik Braun
2021-09-14 13:08         ` Ludovic Courtès
2021-09-14 16:04           ` Leo Famulari [this message]
2021-09-15  6:40             ` Lars-Dominik Braun
2021-09-15 12:34               ` Ludovic Courtès
2021-09-15 16:25                 ` Ludovic Courtès
2021-09-15 16:30                 ` Ludovic Courtès
2021-09-15 16:30                 ` Ludovic Courtès
2021-09-06 23:18 ` Kyle Andrews
2021-09-06 23:29   ` bdju via Bug reports for GNU Guix
2021-09-10 11:24 ` Vladilen Kozin

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=YUDIBgbIIUOgKZ96@jasmine.lan \
    --to=leo@famulari.name \
    --cc=50264@debbugs.gnu.org \
    --cc=lars@6xq.net \
    --cc=ludo@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).