Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33632 - [libvirt] Please remove audit dependency from libvirt
Attached to Project:
Community Packages
Opened by Adam (adam900710) - Wednesday, 30 January 2013, 01:06 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 01 February 2013, 06:18 GMT
Opened by Adam (adam900710) - Wednesday, 30 January 2013, 01:06 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 01 February 2013, 06:18 GMT
|
DetailsDescription:
The latest libvirt 1.0.1-4 needs audit as dependency. But since Archlinux does not use audit as default, is this really needed? The previous version does not need audit and the PKGBUILD is quiet easy to remove the audit dependency, is it really needed to use audit? Additional info: * package version(s) libvirt 1.0.1-4 * config and/or log files etc. Steps to reproduce: Update libvirt to latest version |
This task depends upon
libaudit.so.1 => /usr/lib/libaudit.so.1 (0x00007f5274243000)
$ pacman -Qo /usr/lib/libaudit.so.1
/usr/lib/libaudit.so.1 is owned by audit 2.2.2-1
See also
FS#33604, item #6.Things works fine and no dependency on audit now.
$ ldd /usr/lib/libvirt.so.0.1000.1 | grep audit
(No output)
The modified PKGBUILD is here:
http://pastebin.com/3uDFZbdp
(The --without-audit options seems not working and it will auto detect the audit headers/libs when compiling,
so on the building system, the audit packages should be removed)
In my opinion since the audit packages is not in [base] group, and according to the minimalistic principle of Arch,
audit should not be included as dependency unless the core function is under affect.
If libvirt upstream can make audit runtime auto-dectect, this will be perfect.....
Neither way, not a problem for most users.