unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 71332@debbugs.gnu.org
Subject: bug#71332: guix gc delete order
Date: Mon, 03 Jun 2024 09:30:34 +0000	[thread overview]
Message-ID: <87plsygypx.fsf@kitej> (raw)
In-Reply-To: <87bk4i5r3p.fsf@ngraves.fr> (Nicolas Graves via Bug reports for's message of "Mon, 03 Jun 2024 11:10:34 +0200")

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

Nicolas Graves via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:

> Hi Guix,
>
> I feel the way `guix gc` choose its files to delete quite
> inconvenient. For instance, when developping big programs locally, I
> often find myself missing space, but when I will `guix gc -C30G`,
> instead of the expected unused items (not present in any profile, just
> built but discarded as the package I'm building is updated for
> instance), I will instead loose most of the native-inputs that are
> needed to build my `guix home` and `guix system`.
>
> This make me stuck in an endless loop of removing / redownloading over
> and over the same native-inputs, while my intention is first to remove
> files that aren't these native-inputs.
>
> I haven't delved into `guix gc` yet, how hard is that issue to solve? 

Hi.
Is the guix-daemon of your system started with the
"--gc-keep-derivations=yes" and "--gc-keep-outputs=yes" options?
It should prevent "guix gc" from deleting the build dependencies of live
profiles.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2024-06-03  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  9:10 bug#71332: guix gc delete order Nicolas Graves via Bug reports for GNU Guix
2024-06-03  9:30 ` Guillaume Le Vaillant [this message]
2024-06-03 13:26   ` Nicolas Graves via Bug reports for GNU Guix
2024-06-03 15:22     ` Andrew Tropin via Bug reports for GNU Guix

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=87plsygypx.fsf@kitej \
    --to=glv@posteo.net \
    --cc=71332@debbugs.gnu.org \
    --cc=ngraves@ngraves.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).