Joey Hess wrote: > > Bernhard Kuemel wrote: > > Thank you very much. I had python 2.1 installed and with 2.2 the > > problem disappeared. Seems python2.2 should be a dependency for > > debconf and mailman. > > Why? They only run python2.2 if it can be found in the path. I dont > really understand how you could possibly have seen the problem with > debians python 2.1, which provides a python2.1 binary, or fixed it by > upgrading to 2.2. I suspect you are not accuratly reporting whatever > happened or are confused.
Well, firstly I was confused at that time in that I did not know that my flat mate had installed a non debian python2.2 in /usr/local which comes first in roots $PATH. When I checked, upon you request, what version of python2.2 I had installed, dpkg reported 2.1 installed, 2.2 not installed. So I apt-get installed python2.2. Secondly I am still confused why the installation of python2.2 made the 'compileall.py -q' bug disappear when in any case /usr/local/bin/python would have been called. Thirdly: Why did the non debian python2.2 not understand 'compileall.py -q'? My problems are solved and it's ok for me to close the bug. Bernhard
