> So change the macro that controls this, and move on to some > other problem. From /usr/lib/rpm/macros: > > # > # Should unpackaged files in a build root terminate a build? > # > # Note: The default value should be 0 for legacy compatibility. > %_unpackaged_files_terminate_build 1 > > > Create /etc/rpm/macros with that line set to 0, and you get the old > behavior. Or put it in your build account's .rpmmacros file. Yes, I do know about that, and use it in the makefiles that build binary packages, so that there's actually not a problem from my end. Sadly, when I release what I'm doing as an srpm, and someone thinks they can "rpmbuild --rebuild stoopidpkgfromlsbproject.src.rpm" they then have it break if their system is using a recent rpm. Which is why a change like this is kind of a pain... different distros are using different versions of rpm, and I can't predict what the default behavior should be (the default should not have changed, for this reason). Mats _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
