Bug 1738969
Summary: | gdeploy depends on Python 2 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lumír Balhar <lbalhar> |
Component: | gdeploy | Assignee: | Sachidananda Urs <sacchi> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | mhroncok, pviktori, ramkrsna, sacchi |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gdeploy-3.0.0-1 gdeploy-3.0.0-3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-23 09:00:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1698500 |
Description
Lumír Balhar
2019-08-08 12:08:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know. Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know. Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know. (In reply to Lumír Balhar from comment #0) > 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 gdeploy'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?) The software is written in Python2. > > - What are the upstream/community plans/timelines regarding Python 3? > Will plan to review the code and migrate to Python3 by early December 2019. > - 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?) > We do not have anyone who knows the project and willing to migrate. But will plan to find someone who could help. Thanks for the info. 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 Here is an example exception request: https://pagure.io/fesco/issue/2208 gdeploy needs these Python 2 packages: - python2-setuptools - python2-pyyaml Check with their maintainers if they want to keep maintaining the python2 parts, and request the exception for them as well. The python2-setuptools maintainer will most likely ask you to co-maintain the package: https://bugzilla.redhat.com/show_bug.cgi?id=1747850 FEDORA-2019-49ab2323ae has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-49ab2323ae gdeploy-3.0.0-1 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-49ab2323ae I've seen some updates for Fedora 30 that claim to port this to Python 3. Thanks! Does it work? Could you please do this in Fedora rawhide? Note that it is probably not possible to build the same package version-release on rawhide and Fedora 31 and Fedora 30 due to this change: https://src.fedoraproject.org/rpms/gdeploy/c/ba834ba2dea953df5f257619f79b7cf1115cca03?branch=master Would you like me to fix the release tags and do the builds? (In reply to Miro Hrončok from comment #11) > I've seen some updates for Fedora 30 that claim to port this to Python 3. > Thanks! Does it work? > Yes, it does work. I have tested a few cases. > Could you please do this in Fedora rawhide? Note that it is probably not > possible to build the same package version-release on rawhide and Fedora 31 > and Fedora 30 due to this change: > > https://src.fedoraproject.org/rpms/gdeploy/c/ > ba834ba2dea953df5f257619f79b7cf1115cca03?branch=master > > Would you like me to fix the release tags and do the builds? I can do the builds. I tried earlier, as you said it complained that build is already present. I'll change the release number and do another build. Thanks. FEDORA-2019-00498b2f16 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-00498b2f16 (In reply to Sachidananda Urs from comment #12) > (In reply to Miro Hrončok from comment #11) > > I've seen some updates for Fedora 30 that claim to port this to Python 3. > > Thanks! Does it work? > > > > Yes, it does work. I have tested a few cases. > > > Could you please do this in Fedora rawhide? Note that it is probably not > > possible to build the same package version-release on rawhide and Fedora 31 > > and Fedora 30 due to this change: > > > > https://src.fedoraproject.org/rpms/gdeploy/c/ > > ba834ba2dea953df5f257619f79b7cf1115cca03?branch=master > > > > Would you like me to fix the release tags and do the builds? > > > I can do the builds. I tried earlier, as you said it complained that build > is already present. > I'll change the release number and do another build. Thanks. I've built the package for rawhide. Thank You. gdeploy-3.0.0-3 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-00498b2f16 gdeploy-3.0.0-1 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. gdeploy-3.0.0-3 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |