Re: severity of bug #22783
You wrote:
[I don't agree with the severity level of bug #22783, asking for a
fix in the hamm release. See
http://www.debian.org/Bugs/db/22/22783-b.html as well]
The recent upload of python 1.5.1-4 didn't fix this bug. I really
consider this bug as important, so the severity level should be
upgraded to important and the bug should be fixed for hamm.
I'm the maintainer of python. I agree with Matthias that #22783 is at least a very severe annoyance that hurts anybody who installs any python-related Debian package:
Like the emacsen add-on packages, many python packages contain files that will be byt-compiled in postinst for better performance. Since quite a long time, the Debian python package looked at the timestamps of the files and only conditionally recompiled files at installation time (the recompilation goes directory-wise). By my fault, this check was dropped in 1.5.1-1 so that possibly all files in /usr/lib/python1.5 will be recompiled whenever a new package installs files there. There was never reported any problem with that checked in any previous version of the python packages (the check was there at least since bo), therefore I'd trust it, although it's not in upstream.
My reason to drop the severity of this bug from important to normal was that Brian White told me that he could allow the fix at this late stage. As Brian told me, there was a choice between dropping python from hamm or dropping the severity to normal.
IMHO the bug is not release-critical for the package and it's not worth dropping python from hamm. Still it makes up for a major annoyance ;-)
The decision is upon you...
Gregor
--
To UNSUBSCRIBE, email to debian-qa-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: