From: Catonano <catonano@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: cleaning the store
Date: Thu, 26 May 2016 22:09:35 +0200 [thread overview]
Message-ID: <CAJ98PDyyrWHoDcsR4_u3bLmB2uhZdpRUeGwcDfPhOCsyYnZWBQ@mail.gmail.com> (raw)
In-Reply-To: <20160526193447.GA21548@jasmine>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
2016-05-26 21:34 GMT+02:00 Leo Famulari <leo@famulari.name>:
> On Thu, May 26, 2016 at 09:10:53PM +0200, Catonano wrote:
>
> 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.
>
Because I tried several variations of the recipe and got always the same
error, I thought something wrong was happening.
Now I notice that at least one of the unreachable dependencies is not well
packaged.
I guess I was a bit confused, sorry
[-- Attachment #2: Type: text/html, Size: 1135 bytes --]
prev parent reply other threads:[~2016-05-26 20:09 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
2016-05-26 20:09 ` Catonano [this message]
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=CAJ98PDyyrWHoDcsR4_u3bLmB2uhZdpRUeGwcDfPhOCsyYnZWBQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).