Hi,

I'm tinkering with a package in review, trying to understand the Python RPM build process. The package is hatch-fancy-pypi-readme [1].

The package uses hatch for build, but it includes a non-license file, AUTHORS.md, which I thought would be trivial to patch around, so it's not included in the RPM.

I patched the pyproject.toml and added:

[tool.hatch.build]
exclude = ["AUTHORS.md"]

Then I realized %pyproject_buildrequires has the option -w enabled, producing a wheel for metadata extraction. So, I added a patch, putting a MANIFEST.in in the root dir of the project with one line:

exclude AUTHORS.md

Yet the whl archive still contains the file:

hatch_fancy_pypi_readme-22.3.0.dist-info/licenses/AUTHORS.md

and so does the final RPM.

Do I have to resort to manually removing the file in %prep?

I encountered another issue with %pyproject_buildrequires when passing the -t option for automatic test requirements.

I wanted to see if I can get rid of the extra BuildRequires in the submitters spec file [2], so I commented out all but python3-dev and python3-test BuildRequires and added -t to %pyproject_buildrequires.

That made the build fail with:

No matching package to install: 'python3dist(pytest-icdiff)'

Yet, I don't see any test or other python module importing icdiff. Building with the original spec file, tests are run and succeed.

Is that a known issue with the -t option? Or am I missing something?

[1] https://github.com/hynek/hatch-fancy-pypi-readme
[2] https://pnemade.fedorapeople.org/python-hatch-fancy-pypi-readme.spec

-- Sandro
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to