Bug 1674322 - heat-cfntools uninstallable due to requirements
Summary: heat-cfntools uninstallable due to requirements
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: heat-cfntools
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steven Hardy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-10 23:55 UTC by Kevin Fenzi
Modified: 2019-02-15 01:13 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-15 01:13:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Fenzi 2019-02-10 23:55:20 UTC
Due to the recent python generators enablement:
https://fedoraproject.org/wiki/Changes/EnablingPythonGeneratorsByDefault

heat-cfntools gets requirements info from the package, which results in: 

Error: 
 Problem: conflicting requests
  - nothing provides python3.7dist(pbr) < 1.0 needed by heat-cfntools-1.4.2-7.fc30.noarch
  - nothing provides python3.7dist(psutil) < 2.0.0 needed by heat-cfntools-1.4.2-7.fc30.noarch

✗ cat requirements.txt 
pbr>=0.6,!=0.7,<1.0
boto>=2.12.0,!=2.13.0
psutil>=1.1.1,<2.0.0
six>=1.9.0

Indeed both pbr and psutil are newer than 1.0, and 2.0.0, so the requirement cannot be met. 

I am untagging the mass rebuild version of this package for now to get composes working again, but any new build will expose the same error(s), so please fix this before any new build.

Comment 1 Adam Williamson 2019-02-15 00:41:10 UTC
Of note:

https://git.openstack.org/cgit/openstack/heat-cfntools/commit/?id=bee7811c80d123bb088a5e3b9683b1ab699e5bf9

I'm just checking if any prior commits are needed to actually make those requirements valid, then I'll try a package update.

Comment 2 Adam Williamson 2019-02-15 01:13:42 UTC
Looks like everything to current git master is useful and seems safe, so I just backported it all.

https://koji.fedoraproject.org/koji/taskinfo?taskID=32823630 should fix this (tested a scratch build installs happily and commands seem to run without exploding).


Note You need to log in before you can comment on or make changes to this bug.