Re: Bug#178373: debconf: severity critical

2003-01-31 Thread Joey Hess
Josselin Mouette wrote: > Your python installation is screwed. The compileall.py module in Debian > does support -q in all versions. It's not possible to be mistaken about > that, as the error message included in Debian's compileall.py is not > exactly this one. Ok so it is a local install of an o

Re: Bug#178373: debconf: severity critical

2003-01-31 Thread Joey Hess
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

Re: Bug#178373: debconf: severity critical

2003-01-31 Thread Graham Wilson
On Fri, Jan 31, 2003 at 02:46:00PM +1100, Donovan Baarda wrote: > On Fri, 2003-01-31 at 09:59, Josselin Mouette wrote: > > Le jeu 30/01/2003 ? 22:42, Bernhard Kuemel a ?crit : > [...] > > > ImportError: /usr/local/lib/python2.2/lib-dynload/math.so: undefined > >^

Re: Bug#178373: debconf: severity critical

2003-01-31 Thread Bernhard Kuemel
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

Re: Bug#178373: debconf: severity critical

2003-01-31 Thread Josselin Mouette
Le ven 31/01/2003 à 16:19, Bernhard Kuemel a écrit : > 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. Because debhelper uses an explicit path to /usr/lib/python2.2/compileal