As per the summary, the following constraints are required to avoid a build failure in version 3.0:- qemu_softmmu_targets_risc32? ( fdt ) qemu_softmmu_targets_risc64? ( fdt )
Er, I should say riscv32 and riscv64 - sorry.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40e4d2a3c32609b313962224ee9d2a96075734b8 commit 40e4d2a3c32609b313962224ee9d2a96075734b8 Author: Matthias Maier <tamiko@gentoo.org> AuthorDate: 2018-12-19 21:11:21 +0000 Commit: Matthias Maier <tamiko@gentoo.org> CommitDate: 2018-12-19 21:46:41 +0000 app-emulation/qemu: version bump to 3.1.0 - use RESTRICT=strip, bug #651422 - switch to tar.xz, bug #666726 - add missing use constraints, bug #664474 qemu_softmmu_targets_riscv32? ( fdt ) qemu_softmmu_targets_riscv64? ( fdt ) - 3.1.0 already contains patches for CVE-2018-15746 - applied patch for CVE-2018-20123 - disable bt subsystem entirely as a "workaround" for CVE-2018-19665. Upstream deprecated the subsystem in November and states that it had been dysfunctional for years with likely no users. Bug: https://bugs.gentoo.org/664740 Bug: https://bugs.gentoo.org/672346 Bug: https://bugs.gentoo.org/673108 Closes: https://bugs.gentoo.org/651422 Closes: https://bugs.gentoo.org/664474 Closes: https://bugs.gentoo.org/666726 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Matthias Maier <tamiko@gentoo.org> app-emulation/qemu/Manifest | 1 + .../qemu/files/qemu-3.1.0-CVE-2018-20123.patch | 35 + app-emulation/qemu/files/qemu-binfmt.initd.head | 2 +- app-emulation/qemu/qemu-2.12.0-r3.ebuild | 2 +- app-emulation/qemu/qemu-2.12.1.ebuild | 2 +- app-emulation/qemu/qemu-3.1.0.ebuild | 821 +++++++++++++++++++++ 6 files changed, 860 insertions(+), 3 deletions(-)
