Bug 1464193 - python-crypto2.6 RPM from EPEL does not install the library properly
Summary: python-crypto2.6 RPM from EPEL does not install the library properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: el6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-22 15:41 UTC by E. Filipov
Modified: 2017-06-24 03:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-24 03:37:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description E. Filipov 2017-06-22 15:41:22 UTC
Description of problem:
On a CentOS 6 system, the pycrypto library is still unavailable, even after the corresponding RPM is installed:

# yum install https://dl.fedoraproject.org/pub/epel/6/x86_64/python-crypto2.6-2.6.1-2.el6.x86_64.rpm
# python -c 'import Crypto'                                                                                                                                                              
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named Crypto


Version-Release number of selected component (if applicable): EPEL, CentOS 6, python-crypto2.6-2.6.1-2.el6.x86_64.rpm


How reproducible:
100%

Steps to Reproduce:
1. See description

Actual results:
Traceback

Expected results:
Blank line with no error

Additional info:
After creating a corresponding .pth file, things work fine:
# echo 'pycrypto-2.6.1-py2.6-linux-x86_64.egg' > /usr/lib64/python2.6/site-packages/pycrypto-2.6.1.pth
# python -c 'import Crypto'
#

Comment 1 Kevin Fenzi 2017-06-24 03:37:16 UTC
Yes, this is expected. :) This is a forward compat (ie newer than the base packge) version using these guidelines: 

https://fedoraproject.org/wiki/Packaging:Python_Eggs#Multiple_Versions

So, you should adjust your calling programs sys.path or setup a script wrapper.


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