Bug#384381: trac: Caused by using "wrong" python version

2006-10-16 Thread Otavio Salvador
Jesus Climent <[EMAIL PROTECTED]> writes: > On Sun, Oct 15, 2006 at 12:20:25AM +0300, Damyan Ivanov wrote: >> >> > What method for running trac is being used? mod-python, perhaps? >> >> mod-python, yes. >> >> Aaah! Look at this. You are right about the 2.3 thing! >> >> $ dpkg -l libapache*-mod-

Bug#384381: trac: Caused by using "wrong" python version

2006-10-16 Thread Jesus Climent
On Sun, Oct 15, 2006 at 12:20:25AM +0300, Damyan Ivanov wrote: > > > What method for running trac is being used? mod-python, perhaps? > > mod-python, yes. > > Aaah! Look at this. You are right about the 2.3 thing! > > $ dpkg -l libapache*-mod-python* | grep ^i > ii libapache2-mod-python2.3 3.1

Bug#384381: trac: Caused by using "wrong" python version

2006-10-14 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Luis, I was not subscribed to the bug (I am now) and thus the late reply. > Looking at the traces, it appears that the bug has to do with running > under python2.3. python-subversion depends on python >= 2.4 and thus > does not provide .py{,c,o}

Bug#384381: trac: Caused by using "wrong" python version

2006-10-13 Thread Luis Rodrigo Gallardo Cruz
Package: trac Followup-For: Bug #384381 Looking at the traces, it appears that the bug has to do with running under python2.3. python-subversion depends on python >= 2.4 and thus does not provide .py{,c,o} files for 2.3, hence the import error. Weird thing is, all executables in the package use a