Thank you for providing qemu 5.2.0 ebuild very fast. app-emulation/qemu-5.2.0 with use flag "pin-upstream-blobs" still pins sys-firmware/edk2-ovmf-201905. As described in the use flag description this pinning shall ensure that the precise version included by upstream release is installed locally -- different versions may lead to "random corruption". But IMHO qemu-5.2.0 recently changed to edk2-ovmf-202008 (also existing as ebuild): https://git.qemu.org/?p=qemu.git;a=tree;f=roms;hb=553032db17440f8de011390e5a1cfddd13751b0b https://git.qemu.org/?p=qemu.git;a=history;f=roms;hb=553032db17440f8de011390e5a1cfddd13751b0b Version bump was also reported in qemu 5.2 changelog. Should qemu-5.20 reflect this for edk2-ovmf (and maybe other FW files), to avoid stability issues? Reproducible: Didn't try
Would be needed to move on from bug #744412 when 5.2.0 is stable.
Yeah, that makes sense.
~app-emulation/qemu-5.2.0 has entered stable quite some days ago. any progress here?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=35a67be12ea5edac2eb8d12eef10e1d7cbd189da commit 35a67be12ea5edac2eb8d12eef10e1d7cbd189da Author: Matthias Maier <tamiko@gentoo.org> AuthorDate: 2021-04-05 00:41:32 +0000 Commit: Matthias Maier <tamiko@gentoo.org> CommitDate: 2021-04-05 01:05:21 +0000 app-emulation/qemu: pin new firmware versions Closes: https://bugs.gentoo.org/759298 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Matthias Maier <tamiko@gentoo.org> app-emulation/qemu/qemu-5.2.0-r50.ebuild | 868 +++++++++++++++++++++++++++++++ 1 file changed, 868 insertions(+)
