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: Thu, 23 Jul 2015 08:29:39 +0200 [thread overview]
Message-ID: <CAKrPhPOqWddXZzFO9=5uvYKiu_2jCrAt5Jyo-qLjZD_4ZNoFbw@mail.gmail.com> (raw)
In-Reply-To: <87h9ov6gqe.fsf@gnu.org>
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?
By changing the hash to a totally different one (a string of '6's) it
downloads the right repo. As expected, it complains about the hash and
gives me the right one which I can copy into the package recipe.
(That's The Lazy work-flow :-).)
Regards,
Fede
>
> HTH,
> Ludo’.
next prev parent reply other threads:[~2015-07-23 6:29 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 [this message]
2015-07-23 22:50 ` Ludovic Courtès
2015-07-24 14:32 ` Federico Beffa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKrPhPOqWddXZzFO9=5uvYKiu_2jCrAt5Jyo-qLjZD_4ZNoFbw@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 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.