What were you trying to do that didn't work?

When working on `iptables-epel` in EPEL 10 to ship the legacy subpackages turned off in RHEL and CentOS Stream, I noticed `%define _unpackaged_files_terminate_build 0` is set - which is dangerous as files could be accidentally left unpackaged.

It looks like all the files that show up in the build warnings are files belonging to the disabled legacy packages, so they should just be removed if `do_legacy_pkg` is off

What is the impact of this issue to you?

I can't base the `iptables-epel` package on the `c10s` `iptables` package with confidence that I have taken care of all the files needed

Please provide the package NVR for which the bug is seen:

iptables-1.8.11-1.el10

How reproducible is this bug?:

Always

Steps to reproduce

1. Rebuild the package in mock
2.  
3.  

Expected results

Warnings about unpackaged files

Actual results

Build should succeed without warnings