Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's now provided from the compat package `python27`. Packages that only use Python 2 at build time, like flowcanvas, had a general exception to keep using it in Fedora 31. Now, the dependency should be removed. Let us know if you need any help investigating or removing the dependency. (There are dozens of packages like this, so we didn't investigate this one thoroughly. We assume you know the package best.) If it's possible that the dependency won't be removed in Fedora 33. Please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243 It's good to mention: - What is the reason for the Python 2 build dependency? - What are the upstream/community plans/timelines regarding Python 2? - 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?) If you need anything from us, or something is unclear, please mention it here.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Adam, do you have any answers?
Hi Petr, Looks like upstream has moved on: http://drobilla.net/software/flowcanvas.html hence I need to look at the packages that depend on flowcanvas, rather than trying to fix it. Adam
$ repoquery --repo=rawhide{,-source} --whatrequires flowcanvas flowcanvas-devel-0:0.7.1-36.fc34.i686 flowcanvas-devel-0:0.7.1-36.fc34.x86_64 $ repoquery --repo=rawhide{,-source} --whatrequires flowcanvas-devel (nothing)
So should the package be retired? Nothing requires it at the moment.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Still valid on rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
What is your plan if we were to remove Python 2 from the distribution today? Should we block that on flowcanvas?
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 41. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2020-04-16). A week before the mass branching of Fedora 42 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 40 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html
I think this should be retired, not sure what the process is and who can do that though. > Note: FlowCanvas is dead, long live Ganv! > The latest version of FlowCanvas is 0.7.1, released on January 11, 2011. (https://drobilla.net/software/flowcanvas.html) Nothing in Fedora uses it as Miro already pointed out 3 years ago. The maintainer is clearly not responsive. (There must be a significant amount of "needinfo" emails in the inbox ;) It is only taking up space in the "FTBFS" trackers, among other places.
(seems like it was a bad idea to comment and therefore get subscribed to this but in the first place - unsubscribing ;))
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 42. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2020-04-16). A week before the mass branching of Fedora 43 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 41 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html