From: Leo Famulari <leo@famulari.name>
To: Zacchaeus Scheffer <zaccysc@gmail.com>
Cc: 53886@debbugs.gnu.org
Subject: bug#53886: guix home not respecting guix pull -C
Date: Tue, 8 Feb 2022 20:06:39 -0500 [thread overview]
Message-ID: <YgMTn82V+ojqNVkn@jasmine.lan> (raw)
In-Reply-To: <CAJejy7kJDnnjJNkqD5Gk2xt0Mms0kCOr_aDbLFa1PJU_KiJ_6g@mail.gmail.com>
On Tue, Feb 08, 2022 at 06:57:14PM -0500, Zacchaeus Scheffer wrote:
> Hi Guix!
>
> I came across some weird behavior with guix home. I wanted to recreate a
> working home environment from one machine on another (because I need a
> working qutebrowser install :3). I did this by doing "guix pull
> --allow-downgrades -C" on my non-working computer using a channels file on
> the working one generated with "guix package --export-channels". However,
> when I did "guix home reconfigure ...", old versions of packages were NOT
> installed. I was able to downgrade the desired package with "guix package
> -i" (only that package was downgraded).
I'm curious, after you did `guix pull --allow-downgrades -C`, did you
use `guix show foo` before reconfiguring, in order to check if the pull
had taken effect?
Also, did you pull and reconfigure as the same user, with the same
privileges? Remember that your "view" of Guix (i.e. `guix pull`) is
per-user.
> 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.
next prev parent reply other threads:[~2022-02-09 1:07 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 [this message]
2022-02-09 6:40 ` Zacchaeus Scheffer
2022-02-09 9:10 ` Josselin Poiret via Bug reports for GNU Guix
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=YgMTn82V+ojqNVkn@jasmine.lan \
--to=leo@famulari.name \
--cc=53886@debbugs.gnu.org \
--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.