Description of problem: Unpackaged files for bind if sdb and libbind are disabled. Version-Release number of selected component (if applicable): bind-9.3.1-1 How reproducible: Everytime, see below. Steps to Reproduce: 1. Set in bind.spec: %{?!SDB: %define SDB 0} %{?!LIBBIND:%define LIBBIND 0} 2. rpmbuild -ba bind.spec 3. Get the list of unpackaged files. Actual results / Expected results: Replace: gunzip < %{SOURCE9} | (cd $RPM_BUILD_ROOT/usr/share; tar -xpf -) by %if %{LIBBIND} gunzip < %{SOURCE9} | (cd $RPM_BUILD_ROOT/usr/share; tar -xpf -) %endif and rebuilding should work both times.
Oops! Yes, you are right, that line should be conditional on %{LIBBIND}. I will make it so in the next version. But it doesn't really make any difference: the bind, bind-libs, bind-utils, bind-devel and bind-chroot packages obtained are identical with or without %{LIBBIND} and/or %{SDB} enabled or disabled - just don't install the bind-sdb or bind-libbind-devel packages if you don't want them . The bind-sdb package provides /usr/sbin/named_sdb, leaving the /usr/sbin/named unchanged, and no BIND code uses libbind in any case. Why do you need to rebuild the BIND package ? If you need to install BIND 9.3.1 on an FC3 system, they are avaiable in pre-built form at: http://people.redhat.com/~jvdias/BIND/9.3.1/FC-3
I rebuilt the bind package for a special and absolutely non-supported system environment, which hasn't postgresql(-devel) for example. Otherwise I wouldn't have notice this small mistake. And - if it is conditional - it maybe should also work ;-)
Fix was built in Rawhide today, closing now.