Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1737633
Summary: | python2-moksha-hub fails to install due to missing Python 2 dependencies (was removed) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | python-moksha-hub | Assignee: | Fedora Infrastructure SIG <infra-sig> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | infra-sig, lbalhar, lewk, rbean |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-04 09:14:15 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: | 1700324, 1690439, 1737530, 1737532, 1737534, 1737535, 1737579, 1737642, 1737643, 1737804, 1738468, 1738469, 1739656 |
Description
Miro Hrončok
2019-08-05 22:39:42 UTC
The last build of python-moksha-hub (from yesterday) does not provide python 2 subpackage. https://koji.fedoraproject.org/koji/buildinfo?buildID=1347214 Lumír, given the dependent bugs, I doubt this will be the best solution of the problem. OTOH if the dependents want python2-moksha-hub, they can package their own, however such thing should be properly communicated. I understand, and I apologize but the problem did not start in python-moksha-hub. I wasn't able to build python2-moksha-hub because python2-stomper was removed from rawhide and python2-stomper cannot be build because there is no python2-future etc. I think that the chain of FTBFS packages is longer. I can, of course, enable python2-moksha-hub back but it'd need to bring back python2-stomper, python2-future and maybe more packages. OK. Let's see what the dependent package maintainers will say. 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. Are there any bugs open for the lack of python2-stomper and python2-future this one can depend on? I am afraid that if we don't fix this soon other dependencies will disappear from rawhide. > Are there any bugs open for the lack of python2-stomper and python2-future this one can depend on?
No. That's why this and all the other bugs were opened, so the maintainers could decide whether they want the packages back or get rid of them.
So far, either they have removed it or they kept silent.
See https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro "Packages still failing to install due to a missing Python 2 dependency will be retired at Beta Freeze, assuming they have a Bugzilla bug open for at least 2 weeks. The package maintainer may postpone this retirement to the Final Freeze by promising to fix it until then." Let me know if this package shall not be retired yet. The beta freeze is at 2019-08-29, the final freeze is at 2019-10-08. (In reply to Miro Hrončok from comment #9) > See > https://fedoraproject.org/wiki/Changes/ > F31_Mass_Python_2_Package_Removal#Removing_non- > installable_packages_from_the_distro > > "Packages still failing to install due to a missing Python 2 dependency will > be retired at Beta Freeze, assuming they have a Bugzilla bug open for at > least 2 weeks. The package maintainer may postpone this retirement to the > Final Freeze by promising to fix it until then." > > Let me know if this package shall not be retired yet. The beta freeze is at > 2019-08-29, the final freeze is at 2019-10-08. This is not applicable here. Python 2 subpackage was removed and it's still not clear whether I'll revert the change or not. Noted. Sorry, the comment was mass posted. Well, there was no interest of the dependent package maintainers, all of the consumers should be gone now. |