From: Leo Famulari <leo@famulari.name>
To: Catonano <catonano@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: cleaning the store
Date: Thu, 26 May 2016 15:34:47 -0400 [thread overview]
Message-ID: <20160526193447.GA21548@jasmine> (raw)
In-Reply-To: <CAJ98PDzAhJ65ahCdZ18W0uf022nZYbEfgPV2d2yEkuK8gZmv9Q@mail.gmail.com>
On Thu, May 26, 2016 at 09:10:53PM +0200, Catonano wrote:
> 2016-05-26 20:38 GMT+02:00 Leo Famulari <leo@famulari.name>:
>
> > On Thu, May 26, 2016 at 06:36:39PM +0200, Catonano wrote:
> > > I erased ALL the prevoius generations and still there are some elements
> > > that "guix gc -d ..." cannot eliminate from the store because they turn
> > out
> > > to be "still alive"
> > >
> > > Of course emacs-cider is not installed in the current generation
> >
> > `guix package -s cider` returns nothing. Nor is that string present in
> > the Guix source tree. It's a private package, yes?
> >
>
> yes, it's a private package
>
> I was trying to make a recipe for cider but there were some errors in the
> log, some dependencies couldn't be reached.
>
> Maybe I messed up the inputs.
>
> I wanted to clean to be sure that there were o interferences from the relics
If you make a change to your cider recipe, then the "relics" can't
interfere with later builds, because the new cider directory in
/gnu/store will have a new hash. It is impossible for the build process
to guess the hash of the old cider "relics", so they won't be used.
If you don't change the cider recipe, then the relics will be used.
next prev parent reply other threads:[~2016-05-26 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 16:36 cleaning the store Catonano
2016-05-26 16:58 ` Leo Famulari
2016-05-26 18:16 ` Catonano
2016-05-26 18:36 ` Leo Famulari
2016-05-26 18:41 ` Leo Famulari
2016-05-27 6:39 ` Ricardo Wurmus
2016-05-26 18:40 ` Thompson, David
2016-05-26 18:38 ` Leo Famulari
2016-05-26 19:10 ` Catonano
2016-05-26 19:34 ` Leo Famulari [this message]
2016-05-26 20:09 ` Catonano
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=20160526193447.GA21548@jasmine \
--to=leo@famulari.name \
--cc=catonano@gmail.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.
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.