all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: 54495@debbugs.gnu.org
Subject: bug#54495: unexpected download after gc
Date: Fri, 18 Mar 2022 14:50:01 +0100	[thread overview]
Message-ID: <877d8r8j5i.fsf@gmail.com> (raw)

Hi,

Considering this with revision a03936a:

    guix gc
    guix install python-ipython -p tools
    guix gc
    guix install python-ipython -p tools

I am surprised that:

 1. the second GC collects things
 2. the second install downloads things

especially by this line:

python-ipython-7.27.0  892KiB  4.6MiB/s 00:00 [##################] 100.0%


Well, it is because of grafts.  The profile contains the grafted
version and the installation expect first the non-grafted for computing
the graft.  For instance:

--8<---------------cut here---------------start------------->8---
$ guix gc --list-dead | grep ipython
finding garbage collector roots...
determining live/dead paths...
/gnu/store/xmw4vxabnkm7vwa0ywfcqcmknbnia0c3-python-ipython-7.27.0

guix build python-ipython --no-grafts
/gnu/store/xmw4vxabnkm7vwa0ywfcqcmknbnia0c3-python-ipython-7.27.0
--8<---------------cut here---------------end--------------->8---

When something is grafted, is it possible to consider the non-grafted as
a "derivation", i.e., control the GC with 'gc-keep-derivations'.

Or the grafted could keep a reference to the non-grafted?


Well, I was expecting that this composition:

    guix gc && guix install

was "idempotent" in a way. :-) And to me, the fact that it is not is
somehow a bug.  Maybe, it is already well-known and not considered as
bug.


Cheers,
simon




             reply	other threads:[~2022-03-21 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 13:50 zimoun [this message]
2022-03-22 20:00 ` bug#54495: unexpected download after gc raingloom
2023-10-29 19:36 ` David Elsing

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=877d8r8j5i.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=54495@debbugs.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.
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.