From: Pierre Neidhardt <mail@ambrevar.xyz>
To: help-guix <help-guix@gnu.org>
Subject: About /var/guix/profiles and guix pull generations
Date: Sat, 08 Dec 2018 11:53:37 +0100 [thread overview]
Message-ID: <878t10xpam.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi!
I had a look at /var/guix/profiles and noticed that there were some forgotten links
there. For instance, of some custom profiles I didn't use and all.
After removing those links (sudo rm ...), guix gc could free a lot of
space!
I also noticed that "guix pull" generations were accumulating, and that
might eat up some disk space as well. So I ran a
--8<---------------cut here---------------start------------->8---
$ guix package -p ~/.config/guix/current -d1m
--8<---------------cut here---------------end--------------->8---
to free all guix checkouts older than a month.
I wonder if we should not document this more. Maybe have "guix" display
extensive information about the profiles in /var/guix/profiles?
When the guix store runs low on disk space, Guix currently suggests to
run "guix gc" and all. I think we should suggest the above command and
to check for other GC rotos in /var/guix/profiles.
Thoughts?
Finally, do I need /var/guix/profiles/per-user/root at all? Is it safe to
remove?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-12-08 10:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 10:53 Pierre Neidhardt [this message]
2018-12-09 4:35 ` About /var/guix/profiles and guix pull generations Chris Marusich
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 13:38 ` Pierre Neidhardt
2018-12-09 22:21 ` Chris Marusich
2018-12-10 8:22 ` Pierre Neidhardt
2018-12-17 9:12 ` Pierre Neidhardt
2018-12-19 2:48 ` Chris Marusich
2018-12-19 7:49 ` Pierre Neidhardt
2018-12-19 16:16 ` Chris Marusich
2018-12-19 16:28 ` Pierre Neidhardt
2018-12-19 16:31 ` Pierre Neidhardt
2018-12-19 16:49 ` Pierre Neidhardt
2018-12-25 17:51 ` swedebugia
2018-12-25 18:49 ` Pierre Neidhardt
2018-12-26 0:09 ` swedebugia
2020-05-20 8:26 ` Pierre Neidhardt
2018-12-19 13:49 ` GC hints Ludovic Courtès
2018-12-19 14:31 ` Pierre Neidhardt
2018-12-19 14:49 ` Ricardo Wurmus
2018-12-19 16:25 ` Chris Marusich
2018-12-20 12:12 ` Mark H Weaver
2018-12-20 20:03 ` Alex Kost
2018-12-21 8:30 ` Chris Marusich
2018-12-21 8:47 ` swedebugia
2018-12-23 15:58 ` Mark H Weaver
2018-12-25 12:05 ` swedebugia
2018-12-25 14:00 ` Pierre Neidhardt
2019-01-08 22:27 ` 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
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=878t10xpam.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--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).