To see this bug fixed and are able to reproduce it against a later version Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 33 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you At that time this bug will be closed as EOL if it remains open with a It is Fedora's policy to close all bug reports from releases that are no longer This message is a reminder that Fedora 33 is nearing its end of life.įedora will stop maintaining and issuing updates for Fedora 33 on. If you need anything from us, or something is unclear, please mention it here. What is the guidance for porting the build 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?) What are the upstream/community plans/timelines regarding Python 2? What is the reason for the Python 2 build dependency? You can refer to the exception for mercurial as an example: If it's possible that the dependency won't be removed in Fedora 33. I assume SeaMonkey is in a similar situation as the packages tracked here: Packages that only use Python 2 at build time, like seamonkey, had a general exception to keep using it in Fedora 31. In Fedora Rawhide, it's now provided from the compat package `python27`. Python 2 reached upstream end-of-life in January 2020.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |