Description of problem: When I did a yum update today in Fedora 15 branch, I get " Updating : libvirt-client-0.8.8-4.fc15.x86_64 14/132 Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overriden by native systemd configuration. Updating : libvirt-python-0.8.8-4.fc15.x86_64 15/132 " Looking at the spec, it uses chkconfig --list and using that provides this output. You should be using systemctl instead and add a dependency. If you are migrated services from sysv to systemd, refer to https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft
Really, it should just do 'chkconfig --level $level <service>' to check if a service is enabled. The scriptlet as is today will already fail if you're running in a non-english locale, for example.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
bug 738725 tracks the change to silence the update; however, it missed out on your observation in comment 1 that non-C locale may break the behavior of the snippet.
Patch for comment 1 proposed: https://www.redhat.com/archives/libvir-list/2011-December/msg00296.html
This should be backported to F15, and cloned to F16. commit fea83dde7b7e0725e4353a2cc5b6e5c7c61cb294 Author: Eric Blake <eblake> Date: Tue Dec 6 16:16:34 2011 -0700 spec: don't use chkconfig --list https://bugzilla.redhat.com/show_bug.cgi?id=694403 reports that the specfile is incorrectly checking for a running libvirt-guests service. For example, $ LC_ALL=es_ES chkconfig --list libvirt-guests libvirt-guests 0:desactivado 1:desactivado 2:desactivado 3:activo 5:activo 6:desactivado will fail to find 5:on, even though it is active. But chkconfig already has a mode where you can silently use the exit status to check for an active service. * libvirt.spec.in (%post): Use simpler chkconfig options, to avoid issues with localization.
This is fixed for F16+ - as F15 is nearing EOL and libvirt hasn't been updated in 10 Months I guess it's save to close this bug now.