unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jimmy Thrasibule via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39195@debbugs.gnu.org
Subject: bug#39195: guix pull switching between profiles/per-user and profiles/default
Date: Mon, 20 Jan 2020 10:26:10 +0100	[thread overview]
Message-ID: <CAE5JQ8BmpoAxFVTa3KuK2q05ou_cEJVJAxydeTf+91UvgrhveQ@mail.gmail.com> (raw)
In-Reply-To: <87d0bfqeu6.fsf@gnu.org>

> What do you mean by “unpacking the store”?

I'm actually deploying Guix from the archive at
https://ftp.gnu.org/gnu/guix/guix-binary-1.0.1.x86_64-linux.tar.xz in
a Docker container.

> I believe /var/guix/profiles/default is used because neither $USER nor
> $LOGNAME were defined, right?
>
> This was fixed here:
>
>   https://git.savannah.gnu.org/cgit/guix.git/commit/?id=c20ba18304ee63f01895f092bb51bc2a9ce3303b

This is the piece of code I was looking for to understand where this
"default" profile was coming from. The $USER environment variable was
indeed not set into the Docker image. Now that it is done, Guix does
not complain about the profile anymore.

> but it’s possible that you were running a version that lacks this fix.

That's is what I started to understand after playing around a bit. The
Guix version provided into the archive is old so it was failing back
to the "default" profile. Once upgraded, the "new" Guix was trying to
switch back to the "root" profile.

Now with the $USER environment variable set all is working great.

  reply	other threads:[~2020-01-20 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 19:22 bug#39195: guix pull switching between profiles/per-user and profiles/default Jimmy Thrasibule
2020-01-19 22:08 ` Ludovic Courtès
2020-01-20  9:26   ` Jimmy Thrasibule via Bug reports for GNU Guix [this message]
2020-01-20 15:45     ` Ludovic Courtès
2020-01-20 17:06       ` zimoun
2020-01-21  9:04         ` Ludovic Courtès
2020-01-21 13:49           ` 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

  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=CAE5JQ8BmpoAxFVTa3KuK2q05ou_cEJVJAxydeTf+91UvgrhveQ@mail.gmail.com \
    --to=bug-guix@gnu.org \
    --cc=39195@debbugs.gnu.org \
    --cc=jimmy@thrasibule.mx \
    --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).