Description of problem:
In my automatic rebuild of Python packages I use the special `+auto` argument with %pyproject_save_files.
This uncovered an issue with man pages. If upstream includes a man page to its package data, it becomes compressed by RPM brp-compress script, and as a result changes the extension (i.e. example.1 becomes example.1.gz). The file example.1 is then looked for and not found, which results in failed RPM build, even though the actual build process went just fine.
It would be nice to have %pyproject_save_files go through the same directories as RPM does when it looks for man pages and append asterisk to each filename (i.e. example.1 becomes example.1*) as defined in the Fedora Packaging Guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_manpages.
Note: RPM hard codes the paths it traverses when looking for man pages to compress. Until they're provided as a macro, we'll have to maintain a list of the directories in pyproject macros as well.
RPM RFE: https://github.com/rpm-software-management/rpm/issues/1865
Build error traceback:
error: File not found: /builddir/build/BUILDROOT/python-getmac-0.8.3-1.fc36.x86_64/usr/share/man/man1/getmac.1
File not found: /builddir/build/BUILDROOT/python-getmac-0.8.3-1.fc36.x86_64/usr/share/man/man1/getmac.1
FEDORA-2022-fd6afbc4b2 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fd6afbc4b2
FEDORA-2022-fd6afbc4b2 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.