On Wed, Mar 31, 2021 at 11:45:54PM +0200, Miro Hrončok wrote:
On 31. 03. 21 21:52, Ben Cotton wrote:
>* Strict checking for unpackaged content in builds
> ...
>* Many existing packages will fail to build due to the stricter
>buildroot content checking. Fixing this in the packaging is always
>backwards compatible. We could temporarily set
>`%_unpackaged_files_terminate_build 0` in rawhide to alleviate initial
>impact if necessary.
This is my main concern with this update.
tl;dr If you %exclude something and there is no other subpackage to
own the files, the build fails:
Whaaat? What is the point of %exclude if not to exclude files from the
list? Why would rpm upstream want to break this? Seems like a completely
backwards change that will make packaging harder instead of easier.
Zbyszek
> This fails:
>
> %install
> ...
> touch %{buildroot}/foo %{buildroot}/bar
>
> %files
> /
> %exclude /foo