unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 47734@debbugs.gnu.org
Subject: bug#47734: Guix install script on foreign distro fails to add berlin public key
Date: Wed, 21 Apr 2021 14:45:01 +0200	[thread overview]
Message-ID: <871rb37qnm.fsf@gnu.org> (raw)
In-Reply-To: <E82DB7A3-398D-4D3F-9599-98087BEA94A2@lepiller.eu> (Julien Lepiller's message of "Mon, 12 Apr 2021 15:48:10 -0400")

Hi Julien,

Julien Lepiller <julien@lepiller.eu> skribis:

> When installing Guix on a new machine (foreign distro), substitute were not properly set up:
>
> …
> Permit downloading pre-built package binaries from the project's build farm? (yes/no) yes
> /home/roptat/guix-install.sh: line 445: /root/.config/guix/current/share/guix/ci.guix.gnu.org.pub: No such file or directory
>
> That was the latest version of the script downloaded from savannah. It downloaded and installed the 1.2.0 tarball.
>
> I was able to fix that later manually, but let's make sure the script doesn't fail like that with the release :)

I don’t see how this can happen: ‘sys_create_store’ creates
~root/.config/guix/current, before ‘sys_authorize_build_farms’ runs.

Can you reproduce it, Julien?

Alternatively, could you paste the complete output of the
guix-install.sh script when it failed?

Thanks,
Ludo’.




  parent reply	other threads:[~2021-04-21 12:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 19:48 bug#47734: Guix install script on foreign distro fails to add berlin public key Julien Lepiller
2021-04-14 19:52 ` Leo Famulari
2021-04-20  0:48   ` Leo Famulari
2021-04-21 12:45 ` Ludovic Courtès [this message]
2021-04-21 15:46   ` Julien Lepiller
2021-04-21 19:56     ` Ludovic Courtès
2021-04-25 19:54       ` Ludovic Courtès

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=871rb37qnm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47734@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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).