From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Zacchaeus Scheffer <zaccysc@gmail.com>, 53886@debbugs.gnu.org
Subject: bug#53886: guix home not respecting guix pull -C
Date: Wed, 09 Feb 2022 10:10:16 +0100 [thread overview]
Message-ID: <87wni4mmmf.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAJejy7=NpMxoa4Yb80TrhLaFMdkt2Mx9xc3zsNY3HhkTVY8hdA@mail.gmail.com>
Hello Zacchaeus and Leo,
Zacchaeus Scheffer <zaccysc@gmail.com> writes:
> Looking at guix package --list-generations, my packages were only modified
> the one time I ran guix package -i qutebrowser. After running guix package
> -i qutebrowser, guix package --export-channels DID have the content passed
> to guix pull -C PLUS the following comment:
> ;; Note: these other commits were also used to install some of the packages
> in this profile:
> ;; "97d97d7da1f5b500b2b76210131ca6adff6a1e80"
>
> [snip]
>
> Looking at guix home list-generations, it looks like the generation has not
> updated any of the numerous times I guix home reconfigured today after guix
> pull --allow-downgrades -C'ing an old channels. However, I was not able to
> reproduce this behavior, so take it with a grain of salt.
>> > My understanding is that "guix home reconfigure" SHOULD behave like "guix
>> > package --manifest", and install all packages in the most recent guix
>> pull.
>>
>> That's my understanding as well.
I believe that's the main misunderstanding here, `guix home` acts like
`guix system`: it creates home generations, inside which there is a
profile. That profile is _not_ ~/.guix-profile, but rather
~/.guix-home/profile. They are disjoint and not operated on by the same
commands, guix home will not touch ~/.guix-profile. If you configure
your shell environment variables with guix home alone, I believe only
the the guix home profile is available by default.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-02-09 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 23:57 bug#53886: guix home not respecting guix pull -C Zacchaeus Scheffer
2022-02-09 1:06 ` Leo Famulari
2022-02-09 6:40 ` Zacchaeus Scheffer
2022-02-09 9:10 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-02-09 18:17 ` Zacchaeus Scheffer
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=87wni4mmmf.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=53886@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=zaccysc@gmail.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 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.