For version 1.0.5, released in December 2006, the noarch.rpm file is not available.
Reason is mentioned in the CHANGES file, more details in this forum posting.
The command used to build the RPM file:
python setup.py bdist_rpm
fails with these errors now:
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/bin/blockhosts.pyc
/usr/bin/blockhosts.pyo
From the BlockHosts CHANGES file:
* Not including noarch.rpm with this release - the scripts that used to
work, no longer work, and from searching on the web, this may be
a distutils/rpmbuild interaction problem. For now, use the non-RPM
install instructions to install this program, INSTALL has details.
Web search yielded someone else running into what looks like the same problem: distutils-sig@python.org/msg02536
But the fix mentioned in that email thread did not fix blockhosts rpm
build.
To build RPM, try this
Hi,
I have experienced this problem before when building another package, try this:
echo "%_unpackaged_files_terminate_build 0" >> /etc/rpm/macros
then build from your spec.
Regards,
Michael.
fixes it
Thanks, this works around the problem, RPM version now available.
Another thing which may be more correct
Hi ac,
I thought you'd like to know, a similar problem was found with the latest proftpd 1.3.1rc1 spec file:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/packages/BUILD/proftpd-1.3.1rc1-root
error: Installed (but unpackaged) file(s) found:
/usr/include/proftpd/auth.h
/usr/include/proftpd/bindings.h
/usr/include/proftpd/buildstamp.h
/usr/include/proftpd/child.h
/usr/include/proftpd/class.h
/usr/include/proftpd/compat.h
and what fixed this (maybe more correctly than the "ignore" I notified about before) was this:
adding "%{prefix}/include/proftpd/*" to the %files section in proftpd.spec
So in terms of blockhosts you're getting this:
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/bin/blockhosts.pyc
/usr/bin/blockhosts.pyo
it might be an indea to try adding:
%{prefix}/bin/*
to the %files section in your spec file which will capture both the .pyc and .pyo files (even though I doubt we need them since they look like python out files which can usually be ignored).
Regards,
Michael.