unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix@gnu.org
Subject: Re: How to remove old (test) builds from store?
Date: Thu, 02 Jun 2016 19:10:12 +0800	[thread overview]
Message-ID: <87k2i7q223.fsf@member.fsf.org> (raw)
In-Reply-To: <575006ED.6000607@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 2 Jun 2016 12:14:05 +0200")

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Hi,
>
> when creating packages and refining the build step by step, I end up
> with many entries in the store I do not need. When tying to delete them,
> only a few are removed and many are kept. E.g:
>
>
> # guix gc -d /gnu/store/*teensy*
> finding garbage collector roots...
> deleting `/gnu/store/…-teensy-loader-cli-2.1-1.f289b7a.drv'
> deleting `/gnu/store/…-teensy-loader-cli-2.1-1.f289b7a.tar.xz.drv'
> guix gc: error: build failed: cannot delete path
> `/gnu/store/…-teensy-loader-cli-2.1-1.f289b7a.tar.gz.drv' since it is
> still alive
> $ ls -d /gnu/store/*teensy* | wc -l
> 35
>
> The one still alive if okay, since I have an older version of this
> package installed in my current environment.
>
>
> How do I get rid of these ca. 30 outdated store items?
I think call gc for each one will work, eg:

for i in /gnu/store/*teensy*; do guix gc -d $i; done

  reply	other threads:[~2016-06-02 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 10:14 How to remove old (test) builds from store? Hartmut Goebel
2016-06-02 11:10 ` 宋文武 [this message]
2016-06-02 11:35   ` Hartmut Goebel
2016-06-02 12:02   ` Ludovic Courtès
2016-06-02 12:51     ` Hartmut Goebel
2016-06-02 12:56       ` Thompson, David
2016-06-02 13:27         ` Hartmut Goebel
2016-06-02 15:22           ` Leo Famulari
2016-06-02 21:06           ` 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=87k2i7q223.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=h.goebel@crazy-compilers.com \
    --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).