There's a new version released: 8.1.0. And while I would simply post a MR to introduce ebuild for the new version, there are couple of problems that need to be addressed: 1) a nasty crasher was found with the 8.1.0 release, fix was merged upstream already, but I need to backport it first. 2) Some patches that we already apply on top need rebasing (libvirt-6.7.0-do-not-use-sysconfig.patch so far). I'm failing this bug for awareness. Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d802ae84726a1051e9358f681c460f037f5a7372 commit d802ae84726a1051e9358f681c460f037f5a7372 Author: Michal Privoznik <mprivozn@redhat.com> AuthorDate: 2022-03-02 09:21:18 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-03-02 17:36:02 +0000 app-emulation/libvirt: version bump to 8.1.0 Ideally, this would be way simpler, just introduce new ebuild and append hashes to the Manifest file. Unfortunately, a nasty crasher was found in the freshly released 8.1.0 so we need to backport the fix. And while at it, rebase two patches that don't apply cleanly anymore (libvirt-6.7.0-do-not-use-sysconfig.patch and libvirt-6.7.0-fix-paths-for-apparmor.patch). Closes: https://bugs.gentoo.org/834483 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Closes: https://github.com/gentoo/gentoo/pull/24388 Signed-off-by: Joonas Niilola <juippis@gentoo.org> app-emulation/libvirt/Manifest | 2 + .../files/libvirt-8.2.0-do-not-use-sysconfig.patch | 211 +++++++++++++ .../libvirt-8.2.0-fix-paths-for-apparmor.patch | 140 +++++++++ ...tation-fault-in-virtqemud-executing-qemuD.patch | 50 +++ app-emulation/libvirt/libvirt-8.1.0.ebuild | 337 +++++++++++++++++++++ 5 files changed, 740 insertions(+)
