From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 56618@debbugs.gnu.org
Subject: [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations
Date: Thu, 21 Jul 2022 11:07:28 +0200 [thread overview]
Message-ID: <87v8rqn8a7.fsf@gnu.org> (raw)
In-Reply-To: <87bktlbfjo.fsf@trop.in> (Andrew Tropin's message of "Tue, 19 Jul 2022 12:46:51 +0300")
Hi,
Andrew Tropin <andrew@trop.in> skribis:
> BTW, a little offtopic (related to gc, but not related to these changes)
> problem I have, which is very annoying: After guix gc, guix home
> rebuilds/redownloads a lot of stuff. The configuration and channels are
> absolutely the same.
>
> guix home reconfigure home-configs.scm # builds/downloads a lot of stuff
> guix gc
> guix home reconfigure home-configs.scm # do everything again
>
> Am I missing something and it is expected behavior or is it a bug?
It’s an expected annoyance: to determine whether a graft needs to be
applied, we first need to download/build the ungrafted variant, which is
why you’re seeing this (this is worsened by the fact that many packages
are candidates for grafting currently on ‘master’).
Ludo’.
next prev parent reply other threads:[~2022-07-21 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 15:19 [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations Ludovic Courtès
2022-07-17 15:21 ` [bug#56618] [PATCH 1/2] home: Add 'home-generation-base' Ludovic Courtès
2022-07-17 15:21 ` [bug#56618] [PATCH 2/2] guix gc: '--delete-generations' now deletes old Home generations Ludovic Courtès
2022-07-18 12:51 ` [bug#56618] [PATCH 1/2] home: Add 'home-generation-base' Andrew Tropin
2022-07-19 8:01 ` Ludovic Courtès
2022-07-18 12:59 ` [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations Andrew Tropin
2022-07-19 8:28 ` Ludovic Courtès
2022-07-19 9:46 ` Andrew Tropin
2022-07-21 9:07 ` Ludovic Courtès [this message]
2022-07-21 20:10 ` Maxim Cournoyer
2022-07-22 12:20 ` Ludovic Courtès
2022-07-25 2:04 ` Maxim Cournoyer
2022-08-01 12:39 ` Ludovic Courtès
2022-07-22 22:42 ` bug#56618: " Ludovic Courtès
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=87v8rqn8a7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56618@debbugs.gnu.org \
--cc=andrew@trop.in \
/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.