all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raid5atemyhomework via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 47149@debbugs.gnu.org
Subject: bug#47149: guix system init seems to ignore --fallback
Date: Mon, 15 Mar 2021 00:41:06 +0000	[thread overview]
Message-ID: <OlaG5Cn5TykkiCQhdHpGNECQysgn0fGmus1cX2UQs6FSP8nnc9DjauxYlVeQ6Wz4awH_j-Pn__9tEyqi2Q5gbpHwJamt-lrgUSqZQmWx7VU=@protonmail.com> (raw)

Split off from 46942

Recently I had to rebuild my Guix OS (ummm it was practice for installing Guix, not at all being too overconfident with `guix system --delete-generations` and screwing up a shepherd start service so that shepherd got into an infinite loop in an edge case...).  Because the official Guix Cuirass in Berlin is ridiculously slow, I used a modified installer with the SJTUG mirror as the first substitute URL and the Guix Cuirass server as second substitute URL.

However, during guided install the SJTUG server gave strange errors to the substituter (which I was unable to capture since it was an install environment and I had no good way to copy-paste from it - I am running Guix on the metal, not in a VM).

Now of course any failure in the first substitute URL should cause the substituter to fall back to the second substitute URL and so on, but that's 47147

*This* bug report is about `guix system init --fallback`.

The same errors happened when I fell back to manual installation and used `guix system init`.  So I tried passing in `--fallback` to make Guix build the package (some `e2fsck` package, do not remember details) instead of trying to download it from SJTUG (since it couldn't download it, it would fail catastrophically).

In order to continue, I had to use `guix system build --fallback`, which seemed to work in that it completed, and a a subsequent `guix system init` succeeded.

So it looks to me that `guix system init` does not propagate `--fallback`.

Thanks
raid5atemyhomework




                 reply	other threads:[~2021-03-15  0:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='OlaG5Cn5TykkiCQhdHpGNECQysgn0fGmus1cX2UQs6FSP8nnc9DjauxYlVeQ6Wz4awH_j-Pn__9tEyqi2Q5gbpHwJamt-lrgUSqZQmWx7VU=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=47149@debbugs.gnu.org \
    --cc=raid5atemyhomework@protonmail.com \
    /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.