Hello!
hydra.gnu.org is under maintenance for a couple of days; the web
front-end remains available, but builds don’t get queued.
Among other things, it’s migrating from /nix/store to /gnu/store.
Stay tuned! :-)
Ludo’.
Nikita Karetnikov skribis:
>> There’s an important check missing here: the code verifies that BODY* is
>> a valid signature, but it doesn’t check whether what it signs
>> corresponds to this narinfo up to but excluding the ‘Signature’ field.
>
> Oh, indeed.
>
>> 5. pass the hash to the signatur
> There’s an important check missing here: the code verifies that BODY* is
> a valid signature, but it doesn’t check whether what it signs
> corresponds to this narinfo up to but excluding the ‘Signature’ field.
Oh, indeed.
> 5. pass the hash to the signature verification procedure.
Then, it s
ggr...@riseup.net skribis:
> Hoping to gradually get back into packaging some stuff of interest. Here's
> libglade for now, if anything looks wrong be sure to let me know. :^)
OK, so here’s a proper review, on the assumption that it’s needed.
> From 58b053edfabd89b5c9da034b295791ceb1cf1281 Mon S
> ggr...@riseup.net skribis:
>
>> +(define-public libglade
>> + (package
>> +(name "libglade")
>> +(version "2.6.4")
>> +(source (origin
>> + (method url-fetch)
>> + (uri (string-append
>> +
>> "http://ftp.gnome.org/pub/GNOME/sources/libglade/2.6/libglade-";
>
>
> How do you envision the transition from this single-signature
> architecture to one where other users and/or independent build farms
> can add their signatures to hydra? Will those signatures be treated
> differently than the signatures created by hydra.gnu.org? Will they
> be stored and sent t
ggr...@riseup.net skribis:
> +(define-public libglade
> + (package
> +(name "libglade")
> +(version "2.6.4")
> +(source (origin
> + (method url-fetch)
> + (uri (string-append
> +
> "http://ftp.gnome.org/pub/GNOME/sources/libglade/2.6/libglade
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> The difficulty here will be to compute the hash up to the Signature
>> field. To do that, ‘read-narinfo’ should probably:
>>
>> 1. read everything from PORT with ‘get-string-all’ in a string (make
>> sure PORT’s encoding
l...@gnu.org (Ludovic Courtès) writes:
> The difficulty here will be to compute the hash up to the Signature
> field. To do that, ‘read-narinfo’ should probably:
>
> 1. read everything from PORT with ‘get-string-all’ in a string (make
> sure PORT’s encoding is UTF-8);
>
> 2. isolate the
Hoping to gradually get back into packaging some stuff of interest. Here's
libglade for now, if anything looks wrong be sure to let me know. :^)
0001-gnu-Add-libglade.patch
Description: Binary data
10 matches
Mail list logo
