Frank Schoolmeesters a écrit :
The reasons for the NMU can be found here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347126
So the NMU was needed and fall back the the previous package is not a
option i guess.
afaik a small patch like this, sould not cause an instability like it does now,
though i can't test it for the moment, currently i use Sarge and not Sid.
I agree that the NMU was needed and rollbacking to the previous package
is not an option. Indeed it looks like a small change, and it certainly
shouldn't introduce any bug, but it seems it does.
I run Etch and tried confirming the regression, but I'm unable to
reproduce the bug using 1.60.0-3.1. In one of the merged reports,
someone mentionned creating a test case for this, so contacting this
person could allow to reproduce and confirm the regression (but I'm not
going to do this myself).
Of course, it's always ideal to have the latest upstream version in
unstable, but that doesn't happen magically. The maintainer has possibly
been unavailable since about 2 months, but that's not a big problem,
i'm afraid it's longer than that, today
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336169
is 133 days open.
OK, I missed release 1.60.1, so this package might indeed start being
considered as neglected, but that doesn't change the fact that the
situation won't be fixed magically.
