There were some incompatible changes made to dissector API in
wireshark-4.6.0. While upstream libvirt merged a fix recently [1]
it's not in any release yet and thus pin wireshark to pre-4.6.0
era.
1: b42a12174c
Closes: https://bugs.gentoo.org/show_bug.cgi?id=963985
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Part-of: https://github.com/gentoo/gentoo/pull/44234
Signed-off-by: Sam James <sam@gentoo.org>
There most recent stable version is 11.6.0-r1, drop the old ones.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Part-of: https://github.com/gentoo/gentoo/pull/44234
Signed-off-by: Sam James <sam@gentoo.org>
Upstream did merge the change but have since temporarily reverted it.
Bug: https://bugs.gentoo.org/960591
Signed-off-by: James Le Cuirot <chewi@gentoo.org>
It has been masked since 2017 due to the removal of openvz. Simply
disable the driver unconditionally (as it is built by default on linux,
if no option is passed).
Acked-by: Sam James <sam@gentoo.org>
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Libvirt has a handful of python scripts used during build. They
are perfectly capable of running with python 3.14.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Part-of: https://github.com/gentoo/gentoo/pull/42439
Signed-off-by: Sam James <sam@gentoo.org>
In its upstream commit [1], libvirt bumped the minimal required
version of glib to 2.66.0. Reflect that in our live ebuild.
1: 420c39d6bd
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
Some kernel config options are renamed and to allow users to run
libvirt on older kernels we had to check kernel version and
either include old or new name in CONFIG_CHECK.
Well, I think it is safe to assume nobody runs the most recent
libvirt on 4.X or <5.2 kernels and thus these workarounds can be
dropped.
Just to be on the safe side, let's make the change only for the
live ebuild for now.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/40566
Signed-off-by: Sam James <sam@gentoo.org>
In its upstream commit of v10.10.0-rc1~2 [1] libvirt introduced a
firewall rule to recompute checksum of DHCP packets because
otherwise in some configurations guests may be unable to acquire
IP address. Unfortunately, while reviewing the patch upstream, I
didn't realize corresponding check for kernel config should be
introduced into our ebuilds.
1: e9e5ebe6a6
Closes: https://bugs.gentoo.org/949588
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
The actual patch is named
libvirt-11.0.0-Fix-paths-in-libvirt-guests.sh.in.patch not
libvirt-11.0.0-fix_paths_in_libvirt-guests_sh.patch. Subtle
difference, big consequence.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/40495
Signed-off-by: Sam James <sam@gentoo.org>
The original patch doesn't apply cleanly anymore because of [1]
which partially merged one change we were making.
1: 2c79c42477
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/40476
Signed-off-by: Sam James <sam@gentoo.org>
These are all overshadowed by the latest stable version
10.3.0-r4.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
When installing a VM, it may happen that layered tools like
virt-install will add TPM to domain definition (some guests like
Windows 11 require it). But in libvirt-10.10.0 there is a crasher
and those layered tools tickle it. Backport a fix from upstream.
Closes: https://bugs.gentoo.org/946930
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/39845
Signed-off-by: Sam James <sam@gentoo.org>
