https://bugzilla.redhat.com/show_bug.cgi?id=2115102
--- Comment #4 from Adam Williamson <awilliam(a)redhat.com> ---
In general, when you get an error like that, you should ask "why is a file I
don't want getting installed?" and fix that, rather than just telling RPM to
ignore it. Why is the upstream install stuff installing a file
`/usr/pylero.cfg` in the first place? That's a very weird thing to install. To
me it would indicate something's wrong with the upstream installer scripts. But
I'd also be wondering, is there meant to be a sample or real config file
installed? If so, how do I get it installed to the right place, and is it
appropriate to package it?
If you're sure you don't need the file and it being there isn't an indicator
of
something more seriously wrong, then as I said, instead of specifying
`_unpackaged_files_terminate_build`, I would wipe the file at the end of
%install , e.g.:
%install
%py3_install
rm -f %{buildroot}{%_bindir}/pylero
to get rid of the executable you don't want to ship.
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2115102