From: Vincent Legoll <vincent.legoll@gmail.com>
To: dannym@scratchpost.org, 40579@debbugs.gnu.org
Cc: me@tobias.gr
Subject: [bug#40579] [PATCH v2] gnu: Add iPXE.
Date: Wed, 15 Apr 2020 22:55:04 +0200 [thread overview]
Message-ID: <d6eb31b4-4f09-356d-57a4-06881ce30e12@gmail.com> (raw)
In-Reply-To: <20200415224134.2014eee9@scratchpost.org>
Hello,
On 15/04/2020 22:41, Danny Milosavljevic wrote:
> ipxe.iso is not reproducible it seems.
>
> --- /gnu/store/gbik17qks3cijj2jazx9a6z1v7a5mari-ipxe-1.20.1
> +++ /gnu/store/gbik17qks3cijj2jazx9a6z1v7a5mari-ipxe-1.20.1-check
> ├── share
> │ ├── ipxe
> │ │ ├── ipxe.iso
> │ │ │┄ xxd not available in path. Falling back to Python hexlify.
> │ │ │┄ 'isoinfo' not available in path. Falling back to binary comparison.
> [...]
>
> Otherwise really cool!
I'll try to have a look, but that's a first for me...
Does this prevent merging ?
--
Vincent Legoll
next prev parent reply other threads:[~2020-04-15 20:56 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 [this message]
2020-06-09 19:31 ` Brice Waegeneire
2020-06-09 19:58 ` Vincent Legoll
2020-06-09 20:11 ` Brice Waegeneire
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=d6eb31b4-4f09-356d-57a4-06881ce30e12@gmail.com \
--to=vincent.legoll@gmail.com \
--cc=40579@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=me@tobias.gr \
/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).