Am 03.02.25 um 12:13 schrieb Miro Hrončok:
Hello Björn.
Hi Miro.
I just realized you pushed a commit like this to all Pythons < 3.13:https://src.fedoraproject.org/rpms/python3.12/ c/14bc16980718d47128c25af68f33f1e249f0a36d?branch=rawhideIt says "Add explicit BR: libxcrypt-devel" and it adds it and bump a release.However, it does not explain why. Why was this necessary?
Python <= 3.12 is still building the crypt module, which links libcrypt.so; thus those packages should express an explicit BR in libxcrypt.
Why only for Python < 3.13?
Python >= 3.13 does not ship the crypt module anymore; we're using the external python-crypt_r module as a replacement.
Why there was no communication with us about the thing?
I never intended to build them; I just added the explicit BR so there will be no fallout, when some time in the future libxcrypt-devel may not be an implicit part of the buildroots anymore. The explicit BR on libxcrypt-devel should have been in spec file since the times Fedora changed from glibc libcrypt to libxcrypt some time ago.
Please do not build the packages, I will use this opportunity to pin tk- devel to < 9.
OpenPGP_0xF52E98007594C21D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ 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
