When building dlib and related packages in the fedora build system, a check for sys.version_info < (3, 14) to ensure correct behavior of the way references are counted [links](https://docs.python.org/3.14/whatsnew/3.14.html#limited-c-api-changes), [links] (https://github.com/davisking/dlib/issues/3096), does not return the correct value.
This can be seen in the build logs [here](https://download.copr.fedorainfracloud.org/results/starfish/howdy-beta/fedora-43-x86_64/09748464-dlib/builder-live.log.gz), where the behavior is identical to this [bug report](https://bugzilla.redhat.com/show_bug.cgi?id=2366197) that lead to the dlib package being orphaned. *said behavior means that when the build is ran without mitigations in place, when using python 3.14. If one makes the behavior "always correct"(i.e. assume the build is always ran with Python 3.14 by removing the conditional), the build will complete correctly. Additionally, in the build logs, we can see that `mock.py version 6.5 starting (python version = 3.13.7 ...` My questions are: Whether way(s) to fix this in the COPR are possible; and if so, how? and if not, is there a way to detect build target in said python script and fix this issue? Cheers, and thanks in advance. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
