From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: help-guix@gnu.org
Subject: How to properly upgrade Guix System & Home?
Date: Wed, 22 Mar 2023 18:11:45 +0100 [thread overview]
Message-ID: <167950510545.8638.5143588589556085001@localhost> (raw)
Hi Guix,
For quite some time, I'd been religiously upgrading my system weekly.
My mantra was something along those lines:
```console
$ sudo guix system delete-generations
$ guix package --delete-generations
$ guix gc
$ guix pull
$ sudo guix system reconfigure my-system.scm
$ guix package --upgrade
```
I was happy with it, but two recent events made me question my faith in this…
1) I realized that there was a third `delete-generations`!
Believe it or not, I didn't know about `guix pull --delete-generations`.
Actually `guix pull --list-generations` was listing a **lot** of month
old stuff.
2) I migrated to Guix Home!
Suddenly everything I thought I understood didn't seem to make any sense
any more! For instance, I can do `guix home reconfigure` and `guix gc` in
a loop and `guix home reconfigure` will keep on downloading things and
`guix gc` will keep on deleting them!? And when I say "things", I mean
packages that are explicitly declared in `my-home.scm` and that I actually use!
When I compare `ls -l (which imv)` before and after a cycle
(`guix home reconfigure` / `guix gc`), I have the same hash.
Which make sense because I haven't `guix pull` in between. So, why is a `imv`
garbage collected and re-downloaded/installed?!
Does it make any sense? Am I the only one facing this issue? What's the
proper way of upgrading a Guix System & Home?
Any help would be very much appreciated!
--
Tanguy
next reply other threads:[~2023-03-22 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 17:11 Tanguy LE CARROUR [this message]
2023-03-22 17:24 ` How to properly upgrade Guix System & Home? Julien Lepiller
2023-03-23 7:24 ` Tanguy LE CARROUR
2023-03-24 18:03 ` Maxim Cournoyer
2023-03-25 16:02 ` Tanguy LE CARROUR
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=167950510545.8638.5143588589556085001@localhost \
--to=tanguy@bioneland.org \
--cc=help-guix@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.
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).