What | Removed | Added |
---|---|---|
Flags | needinfo?(william.brown@suse.com) |
(In reply to William Brown from comment #9) ... > Will this prevent successful upgrading of the profile in future though? That > file is owned by libvirt-daemon-8.0.0-150400.7.3.1.x86_64, and is listed as > a config file meaning that if I modify it, rpm will no longer alter or > upgrade the content going forward. Yes, fair point. It can be reverted after the test via: rm /etc/apparmor.d/abstractions/libvirt-qemu zypper in --force libvirt-daemon-8.0.0-150400.7.3.1.x86_64 Providing a test package would similarly result in upgrade issues due to the package vendor change, so I think testing the manual change would be the most straightforward. > So I think i'd rather just wait for an update. Please? Apparmor profile changes can often be a bit like whack-a-mole, so it'd be very helpful to confirm that nothing else pops up. I'd test myself but am running tumbleweed on my libvirt box and haven't had much luck with the Orthos host lottery.