Source: kiki
Version: 0.5.6-4
Severity: serious
I rebuilt kiki in an up-to-date sid chroot. The resulting binary package
didn't work at all:
$ kiki
Traceback (most recent call last):
File "/usr/bin/kiki", line 3, in <module>
import kiki
ImportError: No module named kiki
This is caused by the fact that its modules were installed into
/usr/lib/python2.5/site-packages and 2.5 is not supported by
python-support anymore:
$ dpkg -L kiki | grep package
/usr/lib/python2.5/site-packages
/usr/lib/python2.5/site-packages/kiki
/usr/lib/python2.5/site-packages/kiki/kiki.wxg
/usr/lib/python2.5/site-packages/kiki/__init__.py
/usr/lib/python2.5/site-packages/kiki/kiki.py
In any case, is there any reason why kiki modules are installed as
public? If there is none, the easiest way to solve the bug is to move
them e.g. to /usr/share/kiki/.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
