ValueError: Globs did not match any module: xgboost

Hi all, I've recently been packaging xgboost for Fedora. It's a C++ project using cmake, with a python module on the side (all in one source tarball): https://nathans.fedorapeople.org/xgboost/ The dependent dmlc-core package is here: https://nathans.fedorapeople.org/dmlc-core/ Everything is prepared and working from the C++ and shared library perspectives, but I'm struggling with getting the python module to install using latest Fedora python spec guidelines. Can anyone point out where I've gone wrong? (looks like its during the final python step in the spec %install) https://nathans.fedorapeople.org/xgboost/xgboost.spec+python shows my additions to add the python sub-package and this is the error I now see (this is from the "%pyproject_save_files xgboost" line right at the end of %install): Traceback (most recent call last): File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 775, in <module> main(cli_args) File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 730, in main file_section, module_names = pyproject_save_files_and_modules( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 720, in pyproject_save_files_and_modules generate_file_list(paths_dict, globs, include_auto) File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 534, in generate_file_list raise ValueError(f"Globs did not match any module: {missed_text}") ValueError: Globs did not match any module: xgboost error: Bad exit status from /var/tmp/rpm-tmp.y91d9b (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.y91d9b (%install)

Thanks for the assistance Miro. I've uploaded a local build log here: https://nathans.fedorapeople.org/xgboost/build.log AFAICS the python parts of the %install step seemed to have worked, but based on Sandro's pointer I can see many files are missing.

Thanks Miro - that size pointer was helpful. Indeed, the only thing in the wheel are 3 metadata files. Things seem to be OK up to this point in the upstream hatchling build: https://github.com/dmlc/xgboost/blob/43897b829680d241491abe1ecd46b2ba9d33... ... that temporary directory is populated with all the python files in what looks like a good format, but the generated wheel is essentially empty. Is there any way to see what's happening inside that hatchling.build.build_wheel call I wonder?