| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
When SOFTMMU_TARGETS are empty the qemu-bridge-helper isn't installed
anymore causing a failure to build due to the fcaps call.
Closes: https://bugs.gentoo.org/675110
Signed-off-by: Doug Goldstein <cardoe@gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
|
|
|
|
|
| |
Package-Manager: Portage-2.3.54, Repoman-2.3.12
Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/674628
Package-Manager: Portage-2.3.54, Repoman-2.3.12
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/672950
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/673876
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/673458
Package-Manager: Portage-2.3.52, Repoman-2.3.12
RepoMan-Options: --force
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
| |
- update to EAPI=7
- drop versionator inherit
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Jonathan Callen <jcallen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
QEMU has deprecated sdl-1.2 support nearly a year ago (in
upstream commit of e52c6ba3414). It's not removed yet, but it
soon will be. Therefore, drop support for it in our ebuild. This
is achieved by basically dropping old 'sdl' use flag and then
renaming 'sdl2' to 'sdl'.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
QEMU has deprecated gtk2 support nearly a year ago, and recently
it dropped the support completely (upstream commit 89d85cde75143).
Reflect this change in the live ebuild.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
| |
Qemu dropped ppcemb target in
a69dc537cc1a6d3c3cb35d30197ed45914a150c3.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/663502
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/664052
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/662024
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
|
|
|
|
| |
c6b150836dfef848e51ec2cce801b12daf2c77b1 dropped versionator from
linux-info, which these ebuilds were using via the implicit inherit.
Package-Manager: Portage-2.3.44, Repoman-2.3.10
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
QEMU mailing list thread is here:
https://marc.info/?l=qemu-devel&m=153229252602494&w=2
The patch is here:
https://marc.info/?l=qemu-devel&m=153230940005574&w=2
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/659090
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
| |
This is a custom backport of a patch being prepared for 2.12.1.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/656886
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Thanks to Arfrever for the proper patch.
Closes: https://bugs.gentoo.org/657766
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
| |
- add missing USE=infiniband dependencies
- fix automagic libxml2 dependency, also fixes static build
- add python-3 support
- fix automagic libxbcommon dependency
Closes: https://bugs.gentoo.org/656006
Closes: https://bugs.gentoo.org/656076
Closes: https://bugs.gentoo.org/657428
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/654174
Package-Manager: Portage-2.3.36, Repoman-2.3.9
|
|
|
|
|
|
|
| |
commit to stable
Package-Manager: Portage-2.3.28, Repoman-2.3.9
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
| |
* desnappify
* fix ARM performance issue. Thanks to David Flogeras and Alexander Tsoy.
Closes: https://bugs.gentoo.org/647952
Closes: https://bugs.gentoo.org/651602
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7686
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
This reverts commit 289a2b775c75dd1e88aa972642624a0bf692e957.
|
|
|
|
| |
This reverts commit 2fc1bc6c7b1f41a3a7df74ce8e170996eb7e36d9.
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The device node /dev/vfio/vfio gets created on modprobing the vfio*
modules. This happens in particular on demand when a qemu vm with PCI
passthrough is started up. The default permissios for the freshly
created device node is
crw-rw-rw- 1 root root 10, 196 Mar 27 08:44 /dev/vfio/vfio
This is terrible.
This patch adds an udev rules and makes sure that the device node has rw
permissions for user root, and group kvm (and no permissions for all).
This fixes
- startup when a qemu-kvm is started as non-root (provided the user is
in group kvm, which is our current policy for accessing /dev/kvm, etc.,
anyway).
- work around this security vulnerability, where /dev/vfio/vfio is
created with world writable permissions upon modprobe. [1]
Thanks to username234, Kash Pande, Ted Rodgers for discovery and patch!
[1] Steps to reproduce:
% ls -la /dev/vfio/vfio
crw------- 1 root root 10, 196 Mar 27 15:40 /dev/vfio/vfio
% modprobe vfio
% ls -la /dev/vfio/vfio
crw-rw-rw- 1 root root 10, 196 Mar 27 15:41 /dev/vfio/vfio
[2] I cannot find an udev rule installed by libvirt/qemu/... that
triggers these permissions.
Bug: https://bugs.gentoo.org/651668
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|