Bug 1785783
Summary: | python-pycryptodomex: Remove (sub)packages from Fedora 32+: python2-pycryptodomex | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | python-pycryptodomex | Assignee: | Miro Hrončok <mhroncok> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | cstratak, igor.raits, mhroncok, ngompa13, paul, pikachu.2014, pviktori, zbyszek |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-pycryptodomex-3.9.7-3.fc33 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-16 10:23:30 UTC | Type: | --- |
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: | 1625773, 1698500 |
Description
Miro Hrončok
2019-12-20 23:30:11 UTC
> if there is no objection in a week
Given the timing, I'll wait until 2020-01-08 before proceeding.
cryptodomex is covered by a FESCo exception ( https://pagure.io/fesco/issue/2266 ) as an alternative to python-crypto for python-dns's use. It's probably my fault; I might have compiled the data used to file this bug. Sorry for that! Miro, do you want to close this? It is not your fault. This is entirely on me and not a mistake. Cryptodomex has an exception, but nothing uses it (even the software that drove the exception). Hence my logic is this: It may have a Python 2 package if needed, but it is not needed now and the package shall be removed until it is needed (if). CCing Paul Howarth - Paul, does that make sense? Do you anticipate using cryptodomex any time soon on Python 2? Currently python-dns uses python-crypto (which I maintain but is dead upstream). The upstream of python-dns supports both python-crypto and python-pycryptodomex and prefers python-pycryptodomex but the Fedora package currently uses python-crypto. I would prefer it if python-dns switched to python-pycryptodomex so I could get rid of Python2 support in python-crypto (pull request https://src.fedoraproject.org/rpms/python-dns/pull-request/1). Hence I'd like to see python-pycryptodomex retain Python2 support unless the python-dns maintainer decides they don't want to switch to python-pycryptodomex for some reason. Unfortunately they have not responded to the pull request. Got it, thanks. python-dns has now switched to python-cryptography, so it should be possible to remove python2-pycryptodomex. *** Bug 1761070 has been marked as a duplicate of this bug. *** |