From: ng0 <ng0@we.make.ritual.n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Packaging packages with GPG signed source archives
Date: Fri, 02 Sep 2016 12:46:41 +0000 [thread overview]
Message-ID: <87inueo4em.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87twdyo5w1.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> ng0 <ng0@we.make.ritual.n0.is> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hi,
>>>
>>> ng0 <ng0@we.make.ritual.n0.is> skribis:
>>>
>>>> On the subject of git repos, I do not understand enough of the
>>>> git-download.scm at the moment to add this myself, but why don't we have
>>>> git-fsck in it as default?
>>>
>>> Dunno; what would it add?
>>>
>>> Ludo’.
>>
>> I don't understand enough of it, I only know someone else added it to
>> some project I contribute to.
>
> Guix ‘origin’ forms store the expected SHA256 of the checkout. So
> everytime we do a Git checkout, guix-daemon explicitly makes sure the
> the checkout contents match the given SHA256. IOW, we already have
> integrity checks built in Guix. For this reason, I think ‘git fsck’
> wouldn’t provide any additional guarantee.
>
> Hope this makes sense!
>
> Ludo’.
I agree
…and wonder if I run into equal problems once I have done the guix
publish/pull/package via gnunet-fs as Nix is discussing for the
distributed system they are discussing to move to, where their problem
is that they need to convert all the hashes for when they'll move all
the sources into that network. I'll see when I get there.
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
prev parent reply other threads:[~2016-09-02 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 5:37 Packaging packages with GPG signed source archives Arun Isaac
2016-08-31 7:33 ` Alex Kost
2016-08-31 7:47 ` Arun Isaac
2016-08-31 10:00 ` ng0
2016-08-31 17:22 ` Leo Famulari
2016-08-31 18:37 ` Arun Isaac
2016-08-31 20:21 ` Ludovic Courtès
2016-08-31 20:42 ` Troy Sankey
2016-09-01 8:29 ` Ludovic Courtès
2016-08-31 21:53 ` ng0
2016-09-01 8:30 ` Ludovic Courtès
2016-09-02 10:10 ` ng0
2016-09-02 12:14 ` Ludovic Courtès
2016-09-02 12:46 ` ng0 [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=87inueo4em.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=help-guix@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.
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).