Description of problem: python-cryptography depends on a non-existent package Error: nothing provides python-ipaddress needed by python-cryptography-0.9-1.fc21.x86_64 Version-Release number of selected component (if applicable): python-cryptography-0.9-1.fc21.x86_64 How reproducible: always Steps to Reproduce: yum install python-cryptography or dnf install python-cryptography Additional info: OpenStack deployment CI is broken because of this, it's a high severity issue for us.
The depcheck test in https://admin.fedoraproject.org/updates/FEDORA-2015-8354/python-cryptography-0.9-1.fc21 actually caught this: output: |- Build python-cryptography-0.9-1.fc21 failed depcheck conflicting requests nothing provides python-ipaddress needed by python-cryptography-0.9-1.fc21.x86_64 conflicting requests nothing provides python-ipaddress needed by python-cryptography-0.9-1.fc21.x86_64 Does https://admin.fedoraproject.org/updates/FEDORA-2015-9676/python-ipaddress-1.0.7-2.fc21 fix this?
https://admin.fedoraproject.org/updates/FEDORA-2015-8385/python-ipaddress-1.0.7-1.fc21 It was pushed to stable today and should be there in the next compose.
Things are still very badly broken because we now have packages which require python-ipaddr and python-ipaddress (which conflict with each other). The only way I could fix upstream TripleO as things stand was to install both python-ipaddr and python-ipaddress with --nodeps: https://review.openstack.org/#/c/189745/ Until this is fixed Fedora 21 is unusable w/ upstream TripleO packages... As a work around we've cherry picked the review above into our CI environment to take the pressure off things...
I'm not sure what to do here. python-ipaddress is required for python-cryptography. It is a backport of the ipaddress module from Python 3.x. Unfortunately, python-ipaddr exposes different stuff in the same namespace used by upstream Python 3.x (and implicitly python-ipaddress). I'm open to proposals.
Would it make sense to use Obsoletes: python-ipaddr in the python-ipaddress package? It seems like that is the desired behavior you are going for here. As is the use of Conflicts: breaks quite a few things... for packages that may get installed alongside python-cryptography which require the old python-ipaddr dependency.
No. python-ipaddr provides a *different* API in the same namespace.
Alright, with some further digging I think we can remove the conflicts. The main issue is bojan's comment here: https://admin.fedoraproject.org/updates/FEDORA-2015-8290/python-ipaddress-1.0.7-1.fc21 However, this may just be a bug in pypolicyd-spf. I will remove the conflicts and see if we can track down the bug in pypolicyd-spf.
python-ipaddress-1.0.7-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/python-ipaddress-1.0.7-3.fc22
python-ipaddress-1.0.7-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-ipaddress-1.0.7-3.fc21
python-ipaddress-1.0.7-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/python-ipaddress-1.0.7-3.fc20
https://bugzilla.redhat.com/show_bug.cgi?id=1230373
Package python-ipaddress-1.0.7-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-ipaddress-1.0.7-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9750/python-ipaddress-1.0.7-3.fc20 then log in and leave karma (feedback).
python-ipaddress-1.0.7-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
python-ipaddress-1.0.7-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
python-ipaddress-1.0.7-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.