Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLokesh Mandvekar
2015-01-23 16:39:57 UTC
Description of problem:
docker-python depends on python-six, but the version available for rhel-7 is outdated.
Current situation with docker-python is this:
>>> import docker
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/docker/__init__.py", line 20, in <module>
from .client import Client # flake8: noqa
File "/usr/lib/python2.7/site-packages/docker/client.py", line 34, in <module>
import websocket
File "/usr/lib/python2.7/site-packages/websocket/__init__.py", line 43, in <module>
from six.moves.urllib.parse import urlparse
ImportError: No module named urllib.parse
This is taken care of with python-six-1.7.3 (which I grabbed from https://brewweb.devel.redhat.com/buildinfo?buildID=397532)
Comment 7Bohuslav "Slavek" Kabrda
2015-03-10 13:44:56 UTC
*** Bug 1173594 has been marked as a duplicate of this bug. ***
Comment 8Bohuslav "Slavek" Kabrda
2015-03-10 13:58:46 UTC
AFAICS python-six should be safe to update to latest upstream release (1.9.0 ATM) - upstream doesn't break backwards compatibility.
I'd highly recommend doing this, since new releases have important new features that more and more upstream projects will start relying on and it would be shame if people needed to start bundling six because of old version in RHEL 7.
I am also interested in seeing python-six in RHEL7 updated. I'm working on porting the falcon framework (python-falcon) to RHEL7 for my own use (via copr). I found that falcon actually needs six to at least be at version 1.4.0. That is the version that introduces the variable six.PY2, which is used several times in falcon.
Skimming through other bug reports, I also found these bugs that could be resolved by an update to six.
#1173594 - python-cryptography
#1123451 - python-novaclient
#1090169 - python-keystoneclient
(In reply to Matej Stuchlik from comment #17)
> This rebase requires pytest>=2.4.0 which in turn requires python-py>=1.4.25.
Are you sure about it? I have working COPR just with the packages included (without EPEL) https://copr.fedoraproject.org/coprs/mcepl/python-behave-epel7/ and it seems to build and work just fine just with the packages included.
(In reply to Matěj Cepl from comment #19)
> (In reply to Matej Stuchlik from comment #17)
> > This rebase requires pytest>=2.4.0 which in turn requires python-py>=1.4.25.
>
> Are you sure about it? I have working COPR just with the packages included
> (without EPEL)
> https://copr.fedoraproject.org/coprs/mcepl/python-behave-epel7/ and it seems
> to build and work just fine just with the packages included.
Looking at [0] at looks like you're using python-six 1.7.3, whereas this rebase is for 1.9.0, I reckon that could be why. I'm afraid I don't remember what exact feature it was that was missing from the older pytest, but there was something.
Note that the main reason for rebasing pytest was [1], not this bug.
[0] https://copr.fedoraproject.org/coprs/mcepl/python-behave-epel7/build/92841/
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1206254
Would it be possible to make the new RHEL python-six package have a virtual provides for python2-six?
Provides: python2-six = %{version}-%{release}
That would match the latest Fedora Python Packaging guidelines [1] and would enable EPEL package maintainers to require python2-six, allowing more similarities between Fedora and EPEL spec files.
It is already possible to do this with the main python packages.
# rpm -q --whatprovides python2
python-2.7.5-18.el7_1.1.x86_64
# rpm -q --whatprovides python2-devel
python-devel-2.7.5-18.el7_1.1.x86_64
[1]: http://fedoraproject.org/wiki/Packaging:Python#Provides
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2015-2166.html