From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 38528@debbugs.gnu.org
Subject: bug#38528: Add test for `guix pull'
Date: Sun, 8 Dec 2019 21:59:41 +0100 [thread overview]
Message-ID: <CAJ3okZ166Rc+ucAAnL5o+o9YwEGXaiKDLOWZ+tdmge+MDf7UTQ@mail.gmail.com> (raw)
In-Reply-To: <87immqu8qw.fsf@ambrevar.xyz>
Hi,
Thank Pierre to raise this issue.
On Sun, 8 Dec 2019 at 16:40, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> The current way to do it is to run
>
> guix pull --url=/path/to/checkout --profile=/tmp/guix.master
When I put that in a test -- say tests/guix-pull.sh -- troubles
arises... The main one appears because there is no user (chroot
environment I guess). Currently, Guix looks at $USER and $LOGNAME then
goes in "default" and applies "Migrating" profile code. Note that it
appears too with non login shell as reported here [1], perhaps not
related.
[1] https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00021.html
What is the best:
- set manually the variable USER to `whoami`?
or - change to scheme code to call `whoami`? Does Guile expose that?
All the best,
simon
next prev parent reply other threads:[~2019-12-08 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 15:39 bug#38528: Add test for `guix pull' Pierre Neidhardt
2019-12-08 20:59 ` zimoun [this message]
2019-12-10 17:13 ` Ludovic Courtès
2019-12-11 0:11 ` Pierre Neidhardt
2019-12-12 13:12 ` Ludovic Courtès
2019-12-12 15:27 ` zimoun
2019-12-13 9:45 ` Pierre Neidhardt
2019-12-13 11:20 ` zimoun
2019-12-13 12:19 ` zimoun
2019-12-13 12:27 ` Pierre Neidhardt
2019-12-14 14:11 ` Ludovic Courtès
2019-12-16 13:19 ` Pierre Neidhardt
2019-12-16 14:36 ` Ludovic Courtès
2019-12-16 14:39 ` Pierre Neidhardt
2022-08-19 14:31 ` Maxim Cournoyer
2019-12-16 15:27 ` zimoun
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=CAJ3okZ166Rc+ucAAnL5o+o9YwEGXaiKDLOWZ+tdmge+MDf7UTQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=38528@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.