From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
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 11:46:14 -0400 [thread overview]
Message-ID: <5B4065FE-7A9D-4780-8F21-831DDB08DD0A@lepiller.eu> (raw)
In-Reply-To: <871rb37qnm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
I can't copy-paste easily to my email client right now, so here's a paste. I'll send the content later.
https://paste.debian.net/1194563/
Le 21 avril 2021 08:45:01 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>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’.
[-- Attachment #2: Type: text/html, Size: 1631 bytes --]
next prev parent reply other threads:[~2021-04-21 15:47 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
2021-04-21 15:46 ` Julien Lepiller [this message]
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=5B4065FE-7A9D-4780-8F21-831DDB08DD0A@lepiller.eu \
--to=julien@lepiller.eu \
--cc=47734@debbugs.gnu.org \
--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).