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.
Cause: python{2,3}-scipy packages were missing python{2,3}-six runtime dependency
Consequence: scipy module failed to import
Fix: missing dependencies were added
Result: scipy module can now be imported
Description of problem:
When installing python2-scipy python2-six is not properly resolved and pulled in. After installing just python2-scipy and attempting to import it there is a traceback for the missing six modules.
Version-Release number of selected component (if applicable):
python2-scipy-1.0.0-19.module+el8.0.0+2961+596d0223.x86_64
How reproducible:
Always
Steps to Reproduce:
1. # yum install python2-scipy
2. # python2
Python 2.7.15 (default, Apr 4 2019, 20:16:50)
[GCC 8.2.1 20180905 (Red Hat 8.2.1-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
3. >>> import scipy
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib64/python2.7/site-packages/scipy/__init__.py", line 109, in <module>
from scipy._lib._version import NumpyVersion as _NumpyVersion
File "/usr/lib64/python2.7/site-packages/scipy/_lib/_version.py", line 11, in <module>
from six import string_types
ImportError: No module named six
Actual results:
python2-scipy doesn't pull in python2-six as a dependency.
Expected results:
python2-scipy should pull in python2-six as a dependency. If you manually install python2-six then python2-scipy does actually function as intended and you can import and utilize it.
Additional info:
I see that we unbundled six from python2-scipy in the following bug (for 2.7)
https://bugzilla.redhat.com/show_bug.cgi?id=1647341
I also see that the spec does still have a requires on python2-six. I dug a bit and wasn't able to find exactly why it's not getting resolved to pull in python2-six. I did confirm that python2-scipy isn't showing that it actually provides python2-six, and that python2-six does show itself providing python2-six.
# yum provides python2-six
Updating Subscription Management repositories.
Last metadata expiration check: 2:29:08 ago on Mon 13 May 2019 04:21:20 PM EDT.
python2-six-1.11.0-4.module+el8+2540+b19c9b35.noarch : Python 2 and 3 compatibility utilities
Repo : rhel-8-for-x86_64-appstream-rpms
Matched from:
Provide : python2-six = 1.11.0-4.module+el8+2540+b19c9b35
python2-six-1.11.0-5.module+el8.0.0+2961+596d0223.noarch : Python 2 and 3 compatibility utilities
Repo : rhel-8-for-x86_64-appstream-rpms
Matched from:
Provide : python2-six = 1.11.0-5.module+el8.0.0+2961+596d0223
[root@localhost ~]# repoquery --provides python2-scipy
Updating Subscription Management repositories.
Last metadata expiration check: 2:32:25 ago on Mon 13 May 2019 04:21:20 PM EDT.
python2-scipy = 1.0.0-18.module+el8+2540+b19c9b35
python2-scipy = 1.0.0-19.module+el8.0.0+2961+596d0223
python2-scipy(x86-64) = 1.0.0-18.module+el8+2540+b19c9b35
python2-scipy(x86-64) = 1.0.0-19.module+el8.0.0+2961+596d0223
python2.7dist(scipy) = 1.0.0
python2dist(scipy) = 1.0.0
[root@localhost ~]# repoquery --provides python2-six
Updating Subscription Management repositories.
Last metadata expiration check: 2:32:34 ago on Mon 13 May 2019 04:21:20 PM EDT.
python2-six = 1.11.0-4.module+el8+2540+b19c9b35
python2-six = 1.11.0-5.module+el8.0.0+2961+596d0223
python2.7dist(six) = 1.11.0
python2dist(six) = 1.11.0
As a side note to this as well, the issue isn't present for python3, so I didn't have to open up a bug for that. The reason being that python3-six is actually a core package, and not having it on the system isn't viable for RHEL 8 (if you tried to remove it it's going to attempt to remove protected packages like dnf), so python3-scipy doesn't hit the issue. That being said, I could imagine a scenario where there is an update to python3-scipy and python3-six that results in python3-scipy not pulling in a required updated version of python3-six, so we may want to look into that as well once the python2 cause is identified.
Comment 1Charalampos Stratakis
2019-05-30 17:11:26 UTC
I think the problem is that the Requires are applied on the srpm and not on the correct sections at the %package directives of the python*-* binary rpms.
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://access.redhat.com/errata/RHSA-2019:3335
Description of problem: When installing python2-scipy python2-six is not properly resolved and pulled in. After installing just python2-scipy and attempting to import it there is a traceback for the missing six modules. Version-Release number of selected component (if applicable): python2-scipy-1.0.0-19.module+el8.0.0+2961+596d0223.x86_64 How reproducible: Always Steps to Reproduce: 1. # yum install python2-scipy 2. # python2 Python 2.7.15 (default, Apr 4 2019, 20:16:50) [GCC 8.2.1 20180905 (Red Hat 8.2.1-3)] on linux2 Type "help", "copyright", "credits" or "license" for more information. 3. >>> import scipy Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/scipy/__init__.py", line 109, in <module> from scipy._lib._version import NumpyVersion as _NumpyVersion File "/usr/lib64/python2.7/site-packages/scipy/_lib/_version.py", line 11, in <module> from six import string_types ImportError: No module named six Actual results: python2-scipy doesn't pull in python2-six as a dependency. Expected results: python2-scipy should pull in python2-six as a dependency. If you manually install python2-six then python2-scipy does actually function as intended and you can import and utilize it. Additional info: I see that we unbundled six from python2-scipy in the following bug (for 2.7) https://bugzilla.redhat.com/show_bug.cgi?id=1647341 I also see that the spec does still have a requires on python2-six. I dug a bit and wasn't able to find exactly why it's not getting resolved to pull in python2-six. I did confirm that python2-scipy isn't showing that it actually provides python2-six, and that python2-six does show itself providing python2-six. # yum provides python2-six Updating Subscription Management repositories. Last metadata expiration check: 2:29:08 ago on Mon 13 May 2019 04:21:20 PM EDT. python2-six-1.11.0-4.module+el8+2540+b19c9b35.noarch : Python 2 and 3 compatibility utilities Repo : rhel-8-for-x86_64-appstream-rpms Matched from: Provide : python2-six = 1.11.0-4.module+el8+2540+b19c9b35 python2-six-1.11.0-5.module+el8.0.0+2961+596d0223.noarch : Python 2 and 3 compatibility utilities Repo : rhel-8-for-x86_64-appstream-rpms Matched from: Provide : python2-six = 1.11.0-5.module+el8.0.0+2961+596d0223 [root@localhost ~]# repoquery --provides python2-scipy Updating Subscription Management repositories. Last metadata expiration check: 2:32:25 ago on Mon 13 May 2019 04:21:20 PM EDT. python2-scipy = 1.0.0-18.module+el8+2540+b19c9b35 python2-scipy = 1.0.0-19.module+el8.0.0+2961+596d0223 python2-scipy(x86-64) = 1.0.0-18.module+el8+2540+b19c9b35 python2-scipy(x86-64) = 1.0.0-19.module+el8.0.0+2961+596d0223 python2.7dist(scipy) = 1.0.0 python2dist(scipy) = 1.0.0 [root@localhost ~]# repoquery --provides python2-six Updating Subscription Management repositories. Last metadata expiration check: 2:32:34 ago on Mon 13 May 2019 04:21:20 PM EDT. python2-six = 1.11.0-4.module+el8+2540+b19c9b35 python2-six = 1.11.0-5.module+el8.0.0+2961+596d0223 python2.7dist(six) = 1.11.0 python2dist(six) = 1.11.0 As a side note to this as well, the issue isn't present for python3, so I didn't have to open up a bug for that. The reason being that python3-six is actually a core package, and not having it on the system isn't viable for RHEL 8 (if you tried to remove it it's going to attempt to remove protected packages like dnf), so python3-scipy doesn't hit the issue. That being said, I could imagine a scenario where there is an update to python3-scipy and python3-six that results in python3-scipy not pulling in a required updated version of python3-six, so we may want to look into that as well once the python2 cause is identified.