Bug 968345
Summary: | abrt.pth prevents python virtualenv creation | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Moskovcak <jmoskovc> |
Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | abienven, abrt-devel-list, alevy, bburton, bgilbert, bleanhar, brian, code, dfediuck, dvlasenk, iprikryl, jfilak, jkurik, jmoskovc, lmiksik, mkyral, mmilata, mtoman, nobody+abrt-devel-list, rvokal, svenkatr, tlavigne |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | abrt-2.0.8-16.el6_4.1 | Doc Type: | Bug Fix |
Doc Text: |
* Previously, attempts to create a Python virtualenv environment using the "--system-site-packages" option resulted in an exception when the site.py() function attempted to load the abrt_exception_handler package. This was caused because Python tried to load the abrt.pth file, in which the abrt_exception_handler module was imported. Since the abrt_exception_handler module was installed under the /usr/lib64 directory and the abrt.pth file was installed under the /usr/lib directory, the site.py() function did not find the required module. This update moves the abrt.pth file to the architecture specific folder, so on 32-bit systems to the /usr/lib/python2.7/site-packages/ directory and on 64-bit systems to the /usr/lib64/python2.7/site-packages/ directory, which corrects this issue.
|
Story Points: | --- |
Clone Of: | 912672 | Environment: | |
Last Closed: | 2013-09-26 10:05:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 912540, 912672 | ||
Bug Blocks: | 907449, 947775, 964123, 976874 |
Comment 7
Martin Kyral
2013-09-12 15:03:40 UTC
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. http://rhn.redhat.com/errata/RHBA-2013-1289.html |