Bug#649259: frescobaldi fails to start when libpython2.6 is not installed
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
Bug#649259: frescobaldi fails to start when libpython2.6 is not installed
Package: frescobaldi Version: 1.2.0-1 Severity: normal 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. 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 Could you please take care of the missing libpython2.6 dependency or make frescobaldi not depend on a specific python version at all? Thanks in advance, Andreas. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages frescobaldi depends on: ii kdebase-bin 4:4.6.5-1 ii lilypond 2.14.2-2+b1 ii okular 4:4.6.5-3 ii python-dbus 0.84.0-2 ii python-kde4 4:4.6.80-3+b2 ii python-qt4 4.8.6-2 ii python-qt4-dbus 4.8.6-2 ii python2.62.6.7-4 frescobaldi recommends no packages. Versions of packages frescobaldi suggests: ii alsa-utils1.0.24.2-4 ii lilypond-doc 2.14.2-2 ii rumor none ii timidity 2.13.2-39+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
