Description of problem: autodep adds a Requires for libgfapi.so.0 Soon gluster will ship glusterfs-api with libgfapi.so.6 for various reasons, which is compatible with libgfapi.so.0. to allow updates to gluster to succeed when samba is installed the requires of libgfapi.so.0 needs to be deleted with a %filter_from_requires /libgfapi.so.0/d', maybe need to add a $ to mark it eol Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This seems to do the trick, although AFAICT this uses the old style filtering. But I'm also concerned about the advice in http://fedoraproject.org/wiki/EPEL:Packaging_Autoprovides_and_Requires_Filtering#Removing_items_from_the_requires_stream_.28post-scan_filtering.29 which indicates: These filtering macros MUST only be used with packages which meet one of the following criteria: ... Architecture specific packages with ... no system libs in libdir. diff --git a/samba.spec b/samba.spec index 055f9e3..6994920 100644 --- a/samba.spec +++ b/samba.spec @@ -284,6 +284,11 @@ Requires: %{name}-libs = %{epoch}:%{samba_version}-%{releas Obsoletes: samba-glusterfs Provides: samba-glusterfs +%{?filter_setup: +%filter_from_requires /libgfapi.so.0/d +%filter_setup +} + %description vfs-glusterfs Samba VFS module for GlusterFS integration. %endif
Instead of filtering the auto-detected requires, it is better to rebuild the samba-vfs-gluster (or samba, in case it is a sub-package) when glusterfs-api provides the new library so-name. Other packages are affected with this too: $ repoquery --releasever=rawhide -s --whatrequires 'libgfapi.so.0()(64bit)' \ | sort -u glusterfs-3.5.0-0.6.beta4.fc21.src.rpm libvirt-1.2.2-1.fc21.src.rpm nfs-ganesha-2.0.0-4.fc21.src.rpm qemu-1.7.0-5.fc21.src.rpm samba-4.1.6-1.fc21.src.rpm The SONAME bump will need to be announced on the Fedora devel mailinglist, and ask the maintainers of the above packages to do a rebuild after the new glusterfs-api has landed in Rawhide.