So, basically, don't use the following macros but write the BuildRequires?
%generate_buildrequires %pyproject_buildrequires
The two packages I have attempted to migrate are libdnet[1] and strongswan[2]
[1] https://src.fedoraproject.org/rpms/libdnet
[2] https://src.fedoraproject.org/rpms/strongswan
Thank you!
Carlos R.F.
On 8/19/25 4:38 AM, Miro Hrončok wrote:
On 19. 08. 25 7:52, Carlos Rodriguez-Fernandez wrote:
Hi all,
There are two packages I maintain from different upstream developers that the setup.py is generated during the build, so they are setup.py.in. However, the new buildrequires macros [1] are expecting the setup.py to already exist, or the pyproject.toml, which could also be a pyproject.toml.in file upstream.
What would be the best course of action here?
1. Generate setup.py
2. Run the %pyproject macros
Could you please share a link to the packages you are talking about?
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
