unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Kai Mertens <kmx@posteo.net>
Cc: 37865@debbugs.gnu.org
Subject: bug#37865: guix pull: error: You found a bug:
Date: Thu, 24 Oct 2019 13:49:56 -0700	[thread overview]
Message-ID: <20191024204956.GA991@PhantoNv4ArchGx.localdomain> (raw)
In-Reply-To: <20191024133429.714337fb.kmx@posteo.net>

On +2019-10-24 13:34:29 +0200, Kai Mertens wrote:

[...]

> This machine is running GNU Guix on top of an old GNU/Linux-libre
> distro (Trisquel7).
> 
> I edited the /etc/init/guix-daemon.conf configuration file and added
> --substitute-urls=https://ci.guix.gnu.org to the exec line.
> 
> Then I used
>  $ sudo -i
>  # guix archive --authorize < path/to/ci.guix.gnu.org.pub
> to authorize the server url.
> 
> But I think guix still tried to substitute from hydra.
> So I deleted the rsa key entries in /etc/guix/acl manually and
> performed a logout-login sequence to restart the daemon.
> 
> Now it works, hurray! I was able to perform a fast 'guix pull' (~2h)
> and the space in / and /tmp turned out to be sufficient.
> 
> When invoking guix package -I for example, I encountered an error like
>  guile: failed to install locale
>

I have encountered the same error. It seems to recur for me after major updates.
So there seems to be something lurking to reawaken the real error message source.
I collected some symptoms and posted them as bug#37900.

I hope it will be obvious to someone what is happening, so this nuisance
can be eliminated (and everyone will be relieved of hearing about it repeatedly :)
(if I am doing something dumb for my case, I promise to try to avoid repeating :)

> But that went away after having updated and installed some packages.
> Unfortunately, I don't know exactly which action was responsible to
> make this message disappear.
>

When you were getting the error message from guix commands (which apparently
uses guile in a way that causes _guile_ to complain),
were you also getting the same error message when invoking guile directly?

I was not -- please see #bug37900 for my attempt to explore the difference.

> Now that I am running an up-to-date version of guix, there seem to be
> no further need to use --substitute-urls=https://ci.guix.gnu.org in the exec
> line of the daemon config file nor to have the rsa key deleted in /etc/guix/acl.
> 
> I thank you all very much for your help. I feel pretty much relieved
> and encouraged to keep trying guix.
>

Me too. I think guix can be great, though my user experience
is not quite great yet :)
HTH
--
Regards,
Bengt Richter

  parent reply	other threads:[~2019-10-24 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  6:34 bug#37865: guix pull: error: You found a bug: Kai Mertens
2019-10-22 21:21 ` Ludovic Courtès
2019-10-23  6:55   ` Kai Mertens
2019-10-23  9:50     ` Ludovic Courtès
2019-10-23 14:26       ` Kai Mertens
2019-10-23 16:55         ` Efraim Flashner
2019-10-24 11:34           ` Kai Mertens
2019-10-24 11:44             ` Efraim Flashner
2019-10-24 20:49             ` Bengt Richter [this message]
2019-10-25  6:55               ` Bengt Richter
2019-10-27  7:54               ` Kai Mertens
2019-10-27 11:52                 ` Bengt Richter
2019-11-16  1:52                   ` Kai Mertens
2019-10-24 17:43         ` 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=20191024204956.GA991@PhantoNv4ArchGx.localdomain \
    --to=bokr@bokr.com \
    --cc=37865@debbugs.gnu.org \
    --cc=kmx@posteo.net \
    /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).