Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12030 - Binary python modules may segfault if found on python 2.5 and 2.6 site-packages

Attached to Project: Arch Linux
Opened by Piotr (riklaunim) - Friday, 07 November 2008, 11:52 GMT
Last edited by Allan McRae (Allan) - Friday, 07 November 2008, 21:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I've made a QTermWidget bindings for PyQt4. It worked on Python 2.5. When I rebuilded it for 2.6 and installed it segfaulted. the *so module was in 2.5 and 2.6 site-packages. Removing *so from 2.5 site-packages resolved the problem.

/usr/lib/python2.5/site-packages/ should be banned from system paths :)
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 07 November 2008, 21:06 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Friday, 07 November 2008, 12:11 GMT
So the problem was that files were not removed when you rebuilt then upgraded the package? Or did you install this package without using pacman?
Comment by Piotr (riklaunim) - Friday, 07 November 2008, 13:24 GMT
It was not a pacman package. The problem was that the module existed in both site-packages. IMHO when there is not python 2.5 the python 2.5 site-packages shoudn't be visible to the system.
Comment by Allan McRae (Allan) - Friday, 07 November 2008, 21:06 GMT
There is also the argument that people don't want to unnecessarily recompile all their python modules that are compatible. IMO, pacman should manage everything not in /home in which case you would not have this problem.

Loading...