From: Brice Waegeneire <brice@waegenei.re>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: Danny Milosavljevic <dannym@scratchpost.org>,
40579@debbugs.gnu.org, me@tobias.gr
Subject: [bug#40579] [PATCH v2] gnu: Add iPXE.
Date: Tue, 09 Jun 2020 22:11:43 +0200 [thread overview]
Message-ID: <87k10gf18g.fsf@waegenei.re> (raw)
In-Reply-To: <6591cb7c-601d-dc58-f4a4-10999caecfa9@gmail.com> (Vincent Legoll's message of "Tue, 9 Jun 2020 21:58:55 +0200")
Vincent Legoll <vincent.legoll@gmail.com> writes:
> On 09/06/2020 21:31, Brice Waegeneire wrote:
>> Danny Milosavljevic <dannym@scratchpost.org> writes:
>>
>>> ipxe.iso is not reproducible it seems.
>>>
>>> [...]
>> The attached patch should be reproducible, it is based on v3 from
>> Vincent.
>> It adds the following:
>> - generate a BUILD_ID based on the package's output hash
>> - use 'let' to set BUILD_TIMESTAMP
>> - set some useful options
>> - add a patch that reset the timestamps of ipxe.iso
>
> Nice and thanks for taking care of this, I've got less time to
> contribute lately.
>
> Did you try to upstream the reproducibility patch ?
> Should be straightforward enough.
No problem :)
No I didn't submit it to upstream, I got frighten by the answers to a
much smaller patch from a Debian team member about reproduciblity[0][1].
Those threads were useful to make our build reproducible tho.
[0]: https://lists.ipxe.org/pipermail/ipxe-devel/2020-May/007023.html
[1]: https://lists.ipxe.org/pipermail/ipxe-devel/2020-May/007051.html
- Brice
next prev parent reply other threads:[~2020-06-09 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 17:59 [bug#40579] [RFC PATCH] add iPXE Vincent Legoll
2020-04-12 18:47 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-12 18:58 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-12 19:46 ` Danny Milosavljevic
2020-04-12 21:18 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-12 23:28 ` [bug#40579] [PATCH v2] gnu: Add iPXE Tobias Geerinckx-Rice via Guix-patches via
2020-04-14 15:11 ` [bug#40579] [PATCH v3] " Vincent Legoll
2020-04-15 20:41 ` [bug#40579] [PATCH v2] " Danny Milosavljevic
2020-04-15 20:55 ` Vincent Legoll
2020-06-09 19:31 ` Brice Waegeneire
2020-06-09 19:58 ` Vincent Legoll
2020-06-09 20:11 ` Brice Waegeneire [this message]
2021-01-12 21:01 ` Vincent Legoll
2021-01-12 21:44 ` [bug#40579] [PATCH 1/2] " Vincent Legoll
2021-01-12 21:44 ` [bug#40579] [PATCH 2/2] gnu: ipxe: Update to 1.21.1 Vincent Legoll
2021-01-12 21:47 ` [bug#40579] [PATCH 1/2] gnu: Add iPXE Vincent Legoll
2021-01-14 0:53 ` Danny Milosavljevic
2021-01-14 8:33 ` bug#40579: [RFC PATCH] add iPXE Vincent Legoll
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=87k10gf18g.fsf@waegenei.re \
--to=brice@waegenei.re \
--cc=40579@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=me@tobias.gr \
--cc=vincent.legoll@gmail.com \
/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).