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 1770851
Summary: | python3-pyvirtualize fails to install in Fedora rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | python-pyvirtualize | Assignee: | Raphael Groner <projects.rg> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | projects.rg, pviktori |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | Patch | ||
Fixed In Version: | python-pyvirtualize-0.10-2.20191018gitdc2d971.fc30 python-pyvirtualize-0.10-2.20191018gitdc2d971.fc31 python-pyvirtualize-0.10-2.20191018gitdc2d971.el7 python-pyvirtualize-0.10-2.20191018gitdc2d971.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-13 16:45:21 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: | 1763484 | ||
Bug Blocks: | 1750909 |
Description
Miro Hrončok
2019-11-11 12:09:23 UTC
The automatically generated dependencies strictly use '=' instead and do not care about '>=' as mentioned in requirements.txt . https://github.com/rocky1109/pyVirtualize/blob/latest/requirements.txt The packaged version doesn't yet have this: https://github.com/rocky1109/pyVirtualize/commit/8a5e90282ca8f75988e6b8e7edc52b3b567994d9 TBH I fail to understand anything of that useless magic crap. The RPM format itself is already able to handle all the dependencies and the version checks and does not need that vaporous dependency generator with obviously not more than about 10 listed entries. My decision is to get rid of requirements.txt as it doesn't mean any benefit for our package based on rpm in Fedora as downstream. No doubt there could be some sense for upstream with pip as well as any bigger dependency trees in general (that said to avoid any general flameware in here). https://www.idkrtm.com/what-is-the-python-requirements-txt/ You can disable it with: %{?python_disable_dependency_generator} FWIW, the generator ignores requirements.txt (there's no standard for it). It looks at package metadata. pyVirtualize, however, uses requirements.txt for both: https://github.com/rocky1109/pyVirtualize/blob/latest/setup.py#L20-L22 I wonder what's the benefit of requirements.txt in this case? In most projects, setup.py would list only the direct dependencies; requirements.txt is used when you want to recreate the exact same environment (e.g. when deploying an app). > I wonder what's the benefit of requirements.txt in this case?
Just a guess: Maybe upstream thinks a textual list with line by line for each individual dependency is better than just a long python list inside setup.py as latter it's done usually? I don't know, that's a too philosophical question and really out of scope here for downstream packaging. Otherwise, I can fully agree what you write.
> You can disable it with:
> %{?python_disable_dependency_generator}
That doesn't work either. Patches welcome.
Please take a look into attachment of bug #1763484 and explain why explicit Requires fails. Continuation with this package may depend on the (promised) support of the (proprietary) APIs of Horizon View. Propably it's not that easy to do with python as it's documented for PowerShell only but the tests indicate a complex WSDL in the background. https://github.com/rocky1109/pyVirtualize/issues/14 This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. FEDORA-2020-ef349cf180 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180 FEDORA-EPEL-2020-7ec765d2b0 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0 FEDORA-2020-e57249355d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d FEDORA-2020-22c3fdfa42 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42 FEDORA-2020-22c3fdfa42 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-22c3fdfa42` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-e57249355d has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e57249355d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-ef349cf180 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ef349cf180` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-7ec765d2b0 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-22c3fdfa42 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42 FEDORA-2020-ef349cf180 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180 FEDORA-EPEL-2020-7ec765d2b0 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0 FEDORA-2020-e57249355d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d FEDORA-EPEL-2020-7ec765d2b0 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-22c3fdfa42 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-22c3fdfa42` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-e57249355d has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e57249355d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-ef349cf180 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ef349cf180` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-e57249355d has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-ef349cf180 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-7ec765d2b0 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-22c3fdfa42 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |