clone 649259 -1
reassign -1 python-kde4 4:4.6.80-3
retitle -1 python-kde4: Python modules linked with libpython
severity 649259 serious
retitle 649259 frescobaldi: should use default version of Python
user debian-pyt...@lists.debian.org
usertags 649259 + python2.7 python2.6-removal
thanks
* Andreas Kurth <deb...@akurth.de>, 2011-11-19, 13:55:
Trying to start up frescobaldi results in the following error message
on my system (Debian unstable):
$ frescobaldi
Traceback (most recent call last):
File "/usr/bin/frescobaldi", line 28, in <module>
from PyKDE4.kdecore import (ki18n, ki18nc,
ImportError: libpython2.6.so.1.0: cannot open shared object file: No
such file or directory
Since frescobaldi is hardwired to python 2.6 there should also be a
dependency to libpython2.6.
Or, even better, it should not be hardwired to a specific python
version at all.
There are two problems here:
1) frescobaldi should be using default version of Python, not python2.6.
2) Python 2.6 modules in python-kde4 are linked with libpython2.6, but
the package is not in Depends, only is Suggests. This would be best
solved by not linking to libpython* at all.
Setting the following symlink fixed the problem for me, but for several
obvious reasons that's not what users want:
$ ln -s /usr/lib/libpython2.7.so.1.0 /usr/lib/libpython2.6.so.1.0
Please don't ever do that. These libraries have different names because
they are not compatible.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
