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 1609965
| Summary: | Port Python bindings to Python 3 or drop them (cmpi-bindings-pywbem cannot be installed on F29+) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | cmpi-bindings | Assignee: | Vitezslav Crhonek <vcrhonek> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | fge, jsafrane, mhroncok, vcrhonek |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-31 07:39:08 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, 1700321, 1700323 | ||
|
Description
Adam Williamson
2018-07-30 22:46:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. Please drop cmpi-bindings-pywbem, they don't install and hence are not beneficial to anybody. It's also a leaf package. In preparation for the Python 2 EOL, we are removing all non-installable Python 2 packages: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned. Note that you don't have to actually fix this right now, setting the bug to ASSIGNED will just mark this as being worked on, so I'll know it is being taken care of. If this happens too quickly, feel free to reach to me any time for help (with specific problems). (If you know for sure this package shall be removed, consider doing it.) Thank You! This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned. See the previous comment for details. This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned. See the previous comment for details. 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. Retired the package. Requesting a freeze exception based on https://pagure.io/fesco/issue/2216#comment-593925 A freeze exception for what, though? Why is this marked as ON_QA? I do not see an update listed above at all. If there is an update that fixes this bug, please mark it as fixing this bug; the blocker/FE process relies on the update being marked as fixing the bug. Thanks. The package was retired. There is no update. I just want to make sure it won't be part of beta. Sigh. I see. You want freeze exceptions for the *retirements*? We could probably handle that differently than proposing individual FEs for every retired package, though :/ Retirements aren't handled through update pushes in any case... I've verified that the package is gone from the fedora repo. Thanks and sorry for panicking. |