From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
YOANN P <yoann_mac_donald@hotmail.com>
Subject: Re: guix gc doesn't seem to clean old guix revision
Date: Tue, 10 Dec 2019 17:32:27 +0100 [thread overview]
Message-ID: <CAJ3okZ2y7EfzH+qG6XzhYpVcvxN41nBMMuFctMF-1e7DwUX+YA@mail.gmail.com> (raw)
In-Reply-To: <87eexcp2zk.fsf@gnu.org>
Hi Ludo,
On Tue, 10 Dec 2019 at 17:19, Ludovic Courtès <ludo@gnu.org> wrote:
> YOANN P <yoann_mac_donald@hotmail.com> skribis:
> >> As said, it is not a bug of "guix pull" but a bug of the
> >> configuration. Adding the root user to your Dockerfile should fix the
> >> issue you encounter.
> >
> > The fact that guix require $USER to be set is IMO a kind of bug and is
> > documented anywhere.
>
> I had not understood that. I guess the patch below fixes it, I’ll push
> it shortly.
Bug or not a bug? that is the question. ;-)
If I understand well, the "default" case will never happen now.
And does the addition not include (getenv "USER") and LOGNAME?
Cheers,
simon
next prev parent reply other threads:[~2019-12-10 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:33 guix gc doesn't seem to clean old guix revision YOANN P
2019-11-20 12:00 ` YOANN P
2019-11-20 15:43 ` Julien Lepiller
2019-11-20 15:47 ` John Soo
2019-11-20 16:09 ` YOANN P
2019-11-23 17:43 ` Ludovic Courtès
2019-11-24 18:07 ` YOANN P
2019-11-26 19:26 ` zimoun
2019-11-27 14:21 ` zimoun
2019-11-29 15:14 ` YOANN P
2019-12-02 15:44 ` zimoun
2019-12-02 20:55 ` YOANN P
2019-12-02 21:51 ` zimoun
2019-12-10 16:19 ` Ludovic Courtès
2019-12-10 16:32 ` zimoun [this message]
2019-12-11 11:13 ` YOANN P
2019-12-19 16:14 ` Ludovic Courtès
2019-11-21 11:31 ` zimoun
2019-11-21 21:12 ` YOANN P
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=CAJ3okZ2y7EfzH+qG6XzhYpVcvxN41nBMMuFctMF-1e7DwUX+YA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=yoann_mac_donald@hotmail.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 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).