From: Olaf Hering <olaf@aepfle.de>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] edk2 fails to compile in v4.0.0-rc2
Date: Mon, 8 Apr 2019 11:09:10 +0200 [thread overview]
Message-ID: <20190408110911.46d3b9d0.olaf@aepfle.de> (raw)
In-Reply-To: <9a4ea235-29ce-2a98-a723-0a61be55433f@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Am Mon, 8 Apr 2019 11:04:09 +0200
schrieb Laszlo Ersek <lersek@redhat.com>:
> This is not a QEMU build failure, but an issue in the downstream
> packaging that not only tries to build QEMU, but performs a maintainer
> build on binary artifacts.
I'm sure everyone will rebuild the things from source that can be rebuilt.
Who would ship random binary blobs from unknown origin?
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-04-08 9:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 10:39 [Qemu-devel] edk2 fails to compile in v4.0.0-rc2 Olaf Hering
2019-04-05 10:39 ` Olaf Hering
2019-04-05 10:49 ` Philippe Mathieu-Daudé
2019-04-05 10:49 ` Philippe Mathieu-Daudé
2019-04-05 10:59 ` Olaf Hering
2019-04-05 10:59 ` Olaf Hering
2019-04-05 11:14 ` Philippe Mathieu-Daudé
2019-04-05 11:14 ` Philippe Mathieu-Daudé
2019-04-05 11:24 ` Philippe Mathieu-Daudé
2019-04-05 11:24 ` Philippe Mathieu-Daudé
2019-04-05 11:27 ` Olaf Hering
2019-04-05 11:27 ` Olaf Hering
2019-04-05 11:16 ` Olaf Hering
2019-04-05 11:16 ` Olaf Hering
2019-04-05 11:29 ` Philippe Mathieu-Daudé
2019-04-05 11:29 ` Philippe Mathieu-Daudé
2019-04-05 11:31 ` Olaf Hering
2019-04-05 11:31 ` Olaf Hering
2019-04-08 9:04 ` Laszlo Ersek
2019-04-08 9:04 ` Laszlo Ersek
2019-04-08 9:09 ` Olaf Hering [this message]
2019-04-08 9:09 ` Olaf Hering
2019-04-08 9:42 ` Laszlo Ersek
2019-04-08 9:42 ` Laszlo Ersek
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190408110911.46d3b9d0.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).