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 - python3-pyvirtualize fails to install in Fedora rawhide
Summary: python3-pyvirtualize fails to install in Fedora rawhide
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyvirtualize
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Raphael Groner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: Patch
Depends On: 1763484
Blocks: F32FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2019-11-11 12:09 UTC by Miro Hrončok
Modified: 2020-04-25 02:16 UTC (History)
2 users (show)

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:
Clone Of:
Environment:
Last Closed: 2020-04-13 16:45:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2019-11-11 12:09:23 UTC 
python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch fails to install in Fedora rawhide:

  nothing provides python3.8dist(alabaster) = 0.7.10 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-sphinx-theme-alabaster-0.7.12-7.fc32.noarch)
  nothing provides python3.8dist(babel) = 2.4 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-babel-2.7.0-7.fc32.noarch)
  nothing provides python3.8dist(colorama) = 0.3.9 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-colorama-0.4.1-4.fc32.noarch)
  nothing provides python3.8dist(docutils) = 0.13.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-docutils-0.15.2-3.fc32.noarch)
  nothing provides python3.8dist(imagesize) = 0.7.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-imagesize-1.1.0-1.fc32.noarch)
  nothing provides python3.8dist(jinja2) = 2.9.6 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-jinja2-2.10.1-5.fc32.noarch)
  nothing provides python3.8dist(markupsafe) = 1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-markupsafe-1.1.1-4.fc32.x86_64)
  nothing provides python3.8dist(packaging) = 16.8 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-packaging-19.2-1.fc32.noarch)
  nothing provides python3.8dist(pygments) = 2.2 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-pygments-2.4.2-5.fc32.noarch)
  nothing provides python3.8dist(pyparsing) = 2.2 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-pyparsing-2.4.2-1.fc32.noarch)
  nothing provides python3.8dist(pytz) = 2017.2 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-pytz-2019.3-1.fc32.noarch)
  nothing provides python3.8dist(pyvmomi) = 6.5 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-pyvmomi-6.7.3-1.fc32.noarch)
  nothing provides python3.8dist(pyyaml) = 3.12 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-pyyaml-5.1.2-3.fc32.x86_64)
  nothing provides python3.8dist(requests) = 2.14.2 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-requests-2.22.0-7.fc32.noarch)
  nothing provides python3.8dist(six) = 1.10 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-six-1.12.0-7.fc32.noarch)
  nothing provides python3.8dist(snowballstemmer) = 1.2.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-snowballstemmer-1.9.0-4.fc32.noarch)
  nothing provides python3.8dist(sphinx) = 1.6.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-sphinx-1:2.1.2-6.fc32.noarch)
  nothing provides python3.8dist(sphinxcontrib-websupport) = 1.0.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-sphinxcontrib-websupport-1.1.2-4.fc32.noarch)
  nothing provides python3.8dist(typing) = 3.6.1 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
  nothing provides python3.8dist(xmltodict) = 0.11 needed by python3-pyvirtualize-0.9-8.20181003git57d2307.fc32.noarch
    (we have python3-xmltodict-0.12.0-5.fc32.noarch)
Comment 1 Raphael Groner 2019-11-11 19:50:46 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
Comment 2 Miro Hrončok 2019-11-11 20:36:37 UTC 
The packaged version doesn't yet have this: https://github.com/rocky1109/pyVirtualize/commit/8a5e90282ca8f75988e6b8e7edc52b3b567994d9
Comment 3 Raphael Groner 2019-11-14 08:21:24 UTC 
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/
Comment 4 Petr Viktorin 2019-11-14 09:17:32 UTC 
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).
Comment 5 Raphael Groner 2019-11-14 09:51:22 UTC 
> 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.
Comment 6 Raphael Groner 2019-11-14 09:51:58 UTC 
> You can disable it with:
>   %{?python_disable_dependency_generator}

That doesn't work either. Patches welcome.
Comment 7 Raphael Groner 2019-11-14 10:09:10 UTC 
Please take a look into attachment of bug #1763484 and explain why explicit Requires fails.
Comment 8 Raphael Groner 2019-11-17 08:22:49 UTC 
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
Comment 9 Ben Cotton 2020-02-11 16:39:27 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 10 Fedora Update System 2020-04-02 09:17:41 UTC 
FEDORA-2020-ef349cf180 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180
Comment 11 Fedora Update System 2020-04-02 09:17:41 UTC 
FEDORA-EPEL-2020-7ec765d2b0 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0
Comment 12 Fedora Update System 2020-04-02 09:17:43 UTC 
FEDORA-2020-e57249355d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d
Comment 13 Fedora Update System 2020-04-02 09:17:45 UTC 
FEDORA-2020-22c3fdfa42 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42
Comment 14 Fedora Update System 2020-04-03 19:56:15 UTC 
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.
Comment 15 Fedora Update System 2020-04-03 20:35:12 UTC 
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.
Comment 16 Fedora Update System 2020-04-03 20:49:42 UTC 
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.
Comment 17 Fedora Update System 2020-04-03 21:18:29 UTC 
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.
Comment 18 Fedora Update System 2020-04-05 09:11:24 UTC 
FEDORA-2020-22c3fdfa42 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-22c3fdfa42
Comment 19 Fedora Update System 2020-04-05 09:13:37 UTC 
FEDORA-2020-ef349cf180 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ef349cf180
Comment 20 Fedora Update System 2020-04-05 09:17:59 UTC 
FEDORA-EPEL-2020-7ec765d2b0 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7ec765d2b0
Comment 21 Fedora Update System 2020-04-05 10:03:24 UTC 
FEDORA-2020-e57249355d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e57249355d
Comment 22 Fedora Update System 2020-04-06 00:42:12 UTC 
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.
Comment 23 Fedora Update System 2020-04-06 08:44:41 UTC 
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.
Comment 24 Fedora Update System 2020-04-06 09:19:42 UTC 
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.
Comment 25 Fedora Update System 2020-04-06 09:30:20 UTC 
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.
Comment 26 Fedora Update System 2020-04-13 16:45:21 UTC 
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.
Comment 27 Fedora Update System 2020-04-13 17:24:25 UTC 
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.
Comment 28 Fedora Update System 2020-04-20 19:49:40 UTC 
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.
Comment 29 Fedora Update System 2020-04-25 02:16:32 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.