unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: Julien Lepiller <julien@lepiller.eu>,  help-guix@gnu.org
Subject: Re: How to properly upgrade Guix System & Home?
Date: Fri, 24 Mar 2023 14:03:25 -0400	[thread overview]
Message-ID: <87sfduxc0i.fsf@gmail.com> (raw)
In-Reply-To: <167955626537.2439.10778558862410854160@localhost> (Tanguy LE CARROUR's message of "Thu, 23 Mar 2023 08:24:25 +0100")

Hi,

Tanguy LE CARROUR <tanguy@bioneland.org> writes:

> Hi Julien,
>
> Thanks for your reply!
>
> Quoting Julien Lepiller (2023-03-22 18:24:37)
>> Most likely, you're just seeing a weird behavior caused by grafts. […]
>> When you reconfigure, guix needs to download the ungrafted package
>> before it figures out it already has the graft.
>
> Oh… Oh… grafts! 🤯
>
>
>> Since they have the same name and version, I think you're just
>> cwnfusing the two :)
>
> "Confused" is the appropriate word, indeed! 😅
>
> The thing is, I've been (for the last few months! 😱) in the process of
> writing home services definitions to replace **all** my configuration files,
> so I run **a lot** of `guix home reconfigure`. The command usually takes 30
> seconds to run, but right after I `guix gc` it takes 10 minutes. So I
> guess I should stop collecting garbage for the time being, which is most
> inconvenient for it saves more than 4Go of disk space.

I think we should do something on Guix's side too; it'd be more
intuitive and save resource/time if the things needed by grafts were
always available, i.e. prevented from being garbage collected.

-- 
Thanks,
Maxim


  reply	other threads:[~2023-03-24 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 17:11 How to properly upgrade Guix System & Home? Tanguy LE CARROUR
2023-03-22 17:24 ` Julien Lepiller
2023-03-23  7:24   ` Tanguy LE CARROUR
2023-03-24 18:03     ` Maxim Cournoyer [this message]
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=87sfduxc0i.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=tanguy@bioneland.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).