guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Preparing the reduced bootstrap tarballs, take 3


From: Mark H Weaver
Subject: Re: Preparing the reduced bootstrap tarballs, take 3
Date: Fri, 14 Dec 2018 16:13:40 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Ludovic Courtès <address@hidden> writes:

> Mark H Weaver <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>>
>>> Jan Nieuwenhuizen <address@hidden> skribis:
>>>
>>>> Ludovic Courtès writes:
>>>>
>>>> Hi!
>>>>
>>>>> I’ve just uploaded these to
>>>>> <https://alpha.gnu.org/gnu/guix/bootstrap/i686-linux/20181020>:
>>>>>
>>>>>   linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz
>>>>>   linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz.sig
>>>>>   mescc-tools-static-0.5.2-0.bb062b0-i686-linux.tar.xz
>>>>>   mescc-tools-static-0.5.2-0.bb062b0-i686-linux.tar.xz.sig
>>>>>   mes-minimal-stripped-0.18-0.08f04f5-i686-linux.tar.xz
>>>>>   mes-minimal-stripped-0.18-0.08f04f5-i686-linux.tar.xz.sig
>>>>
>>>> Great!
>>>>
>>>>> Could you adjust bootstrap.scm to refer to this URL?  Currently I see
>>>>> bootstrap.scm refers to a different version of
>>>>> linux-libre-headers-stripped so it should be the only one whose hash
>>>>> needs to be changed.
>>>>
>>>> I don't see that...and the hash matches.
>>>
>>> We’ve discussed it in person, and now I think we’re all set!  :-)
>>
>> Does our documentation include instructions on how to reproducibly build
>> these new bootstrap binaries, to independently verify them?
>
> The build procedure remains unchanged (info "(guix) Bootstrapping"):
>
>   guix build bootstrap-tarballs
>
> To verify them, you can do what I described in this thread, which is to
> use the same commit as Janneke and myself used, run “guix build
> bootstrap-tarballs”, and compare the three tarballs listed above.

What commit did you use?  It would be good to document this, so that
others can independently verify our bootstrap binaries, now or in the
future.

     Thanks,
       Mark



reply via email to

[Prev in Thread] Current Thread [Next in Thread]