Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for asterisk's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to asterisk. If you need anything from us, or something is unclear, please mention it here. Thank you.
Asterisk uses Python 2 in its test suite. The upstream community is contemplating moving the test suite to Python 3, but I doubt that would happen before January 2020.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.). If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies). [1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions
but when it's only for the testsuite why is it pulled on machines with just this packages? [root@asterisk:~]$ rpm -qa | grep asterisk asterisk-sip-16.4.0-1.fc30.x86_64 asterisk-voicemail-plain-16.4.0-1.fc30.x86_64 asterisk-voicemail-16.4.0-1.fc30.x86_64 asterisk-16.4.0-1.fc30.x86_64 asterisk-iax2-16.4.0-1.fc30.x86_64 ------------------ luckily we work with metapackages per machine pulling deps and so hacks like this one prevent it from get pulled Provides: python(abi) = 2.7 Provides: /usr/bin/python2 ------------------ the downside of such hacks is that it drives dnf crazy for whatever reason [root@asterisk:~]$ dnf leaves asterisk-16.4.0-1.fc30.x86_64 asterisk-iax2-16.4.0-1.fc30.x86_64 asterisk-sip-16.4.0-1.fc30.x86_64 asterisk-voicemail-16.4.0-1.fc30.x86_64 asterisk-voicemail-plain-16.4.0-1.fc30.x86_64 lounge-voip-30.1-1.fc30.20191022.rh.noarch ------------------ luckily another hack prevents mistakes while "lounge-voip" has Requires: for all asterisk packages and "dnf leaves" should never list something in /etc/dnf/protected.d/ to begin with [root@asterisk:~]$ dnf remove asterisk-16.4.0-1.fc30.x86_64 asterisk-iax2-16.4.0-1.fc30.x86_64 asterisk-sip-16.4.0-1.fc30.x86_64 asterisk-voicemail-16.4.0-1.fc30.x86_64 asterisk-voicemail-plain-16.4.0-1.fc30.x86_64 lounge-voip-30.1-1.fc30.20191022.rh.noarch Error: Problem: The operation would result in removing the following protected packages: asterisk, asterisk-iax2, asterisk-sip, asterisk-voicemail, asterisk-voicemail-plain, lounge-voip (try to add '--skip-broken' to skip uninstallable packages)
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This was already fixed. Thank you!