Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run rpmlint on a package with filenames containing spaces e. g., https://dl.dropbox.com/u/17870887/spotify-client-0.8.4.103.g9cb177b.260-1.fc17.src.rpm 2. Watch warnings like these: warning: Recognition of file "/home/leamas/rpmbuild/BUILDROOT/spotify-client-0.8.4.103.g9cb177b.260-1.fc17.i386/usr/share/spotify/theme/default/Now" failed: mode 000000 cannot open `/home/leamas/rpmbuild/BUILDROOT/spotify-client-0.8.4.103.g9cb177b.260-1.fc17.i386/usr/share/spotify/theme/default/Now' (No such file or directory These warnings apply for the path "/usr/share/spotify/theme/default/Now Playing/share.png" Actual results: Warnings, rpmlint cant handle files. Expected results: No warnings, rpmlint handles paths with spaces without problems.
Oops... wrong component. This happens when invoking rpmbuild, in package rpm-build which is not in list. Trying rpmrebuild.
not rpmrebuild... still the wrong component.
(In reply to comment #2) > not rpmrebuild... still the wrong component. OTOH, Tom Callaway moved it to rpm in between (thanks!). Might add that the problem seems related to filtering. The warnings occurred when I added the %filter code, without this it was fine. Running on F17, rpm-build-4.9.1.3-8
It's indeed an issue with the Fedora-specific filtering macros from redhat-rpm-config, easily avoided by using the built-in filtering (see http://rpm.org/wiki/PackagerDocs/DependencyGenerator) The problem is here: %global __deploop() while read FILE; do /usr/lib/rpm/rpmdeps -%{1} ${FILE}; done | /bin/sort -u \ When there are spaces in ${FILE}, it get passed as multiple separate arguments to rpmdeps which obviously wont work, and just adding the apparently missing quotes doesn't help either. I guess there's some extra shell magic needed, or alternatively this would work: %global __deploop() while read FILE; do echo "${FILE}" | /usr/lib/rpm/rpmdeps -%{1}; done | /bin/sort -u \ CC'ing Chris Weyl who introduced these macros and switching component to redhat-rpm-config.
Hm... just about two months ago I used the proper %__requires_exclude macros. Forgetting fast, it seems. But I guess this will happen at least others again and again until someone finds the time to update the fedora packaging guidelines. Anyway, thanks for pointing out the correct macros. The bug is obviously still there, but not a problem for me.
*** This bug has been marked as a duplicate of bug 783932 ***