If you maintain a package from PyPI, I wanted to give you a heads-up. It took me two hours to resolve this issue today
as it started with "why Packit did not created new PR when upstream has new version".
And quick check shows that about one thousand packages may be affected.
It seems that PyPI recently started to enforce
https://setuptools.pypa.io/en/latest/history.html#id118
And if project name of your package is affected you will likely hit
https://bugzilla.redhat.com/show_bug.cgi?id=2278073
In my case:
%{pypi_source ibm-cloud-sdk-core}
stopped working and I had to replace it by
%{pypi_source ibm_cloud_sdk_core}
But the new variant works only for recently uploaded tarballs. Not sure where
is the cut date.
You will be likely affected if the project name contains dashes, uppercase
letters or dots.
It will affect you if you do not pass argument to pypi_source macro too. I.e.
./python-azure-cosmos.spec
Source0: %pypi_source
Have to be replaced by %{pypi_source azure_cosmos} when there will be a new
release.
When your package is one-word only, it will likely not affect you. E.g.,
./python-winacl.spec:Source0: %{pypi_source}
will continue to work without a problem.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to 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/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
