From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: use of git-fetch
Date: Fri, 24 Jul 2015 16:32:02 +0200 [thread overview]
Message-ID: <CAKrPhPNhHPbiStd5mu4HAZTus2b3D0==R1dBZ1qmMVFkCxWHkg@mail.gmail.com> (raw)
In-Reply-To: <87zj2mo5dy.fsf@gnu.org>
On Fri, Jul 24, 2015 at 12:50 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
>
>> On Wed, Jul 22, 2015 at 11:10 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> Federico Beffa <beffa@ieee.org> skribis:
>>>
>>>> (sha256
>>>> (base32
>>>> "06mc7kh3fzdh2mqkyynjnp0xpv30yfaiik8bqv8z5b6hldji3cky"))))
>>>
>>> [...]
>>>
>>>> (sha256
>>>> (base32
>>>> "06mc7kh3fzdh2mqkyynjnp0xpv30yfaiik8bqv8z5b6hldji3cky"))))
>>>
>>> Both recipes are telling that they use the same source. So the daemon
>>> cleverly saves one download since it already has the thing with that
>>> hash on disk. See? :-)
>>
>> Thanks for the reply!
>>
>> I thought about this and, before posting, I also tried with an hash
>> where the first character was changed from '0' to '6'. It gave the
>> same result, even after deleting any existing 'emacs-dash' and
>> 'emacs-s' derivation in the store. In my understanding that shouldn't
>> happen. Is that correct?
>
> Right, but we’d have to check the exact sequence of actions that you
> took.
Basically I did:
1. write the package for emacs-dash
2. guix build emacs-dash
3. copy emacs-dash and make emacs-s out of it, keeping the hash unchanged
4. guix build emacs-s
Boom: in the generated derivation I find dash.el instead of s.el.
5. change the first char of the hash 0->6
Boom: same.
6. change the full hash to a sequence of 6s.
OK, now I get the expected result.
7. change hash, rebuild and inspect.
Regards,
Fede
next prev parent reply other threads:[~2015-07-24 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 16:32 use of git-fetch Federico Beffa
2015-07-22 17:00 ` Thompson, David
2015-07-23 6:20 ` Federico Beffa
2015-07-22 21:10 ` Ludovic Courtès
2015-07-23 6:29 ` Federico Beffa
2015-07-23 22:50 ` Ludovic Courtès
2015-07-24 14:32 ` Federico Beffa [this message]
2015-07-24 20:35 ` Ludovic Courtès
2015-07-24 17:46 ` Alex Kost
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='CAKrPhPNhHPbiStd5mu4HAZTus2b3D0==R1dBZ1qmMVFkCxWHkg@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).