Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl writes:
Yeah, sure! I sit half an hour to figure out how to bring my system back
to life (and posibly keep it that way after next time you forget about
dependencies) just to hear from you that I should break it again before
filing a bug report. Am I the only insane here?
Filing RC bugs against the version in unstable because the version in
testing is broken causes the version in unstable to not migrate to
testing. The net effect is that, in attempting to report the bug, you
actually prevent it from being fixed for other testing users.
This is extremely unobvious if you don't know how the Debian bug tracking
and testing migration process works, and I'm sure you weren't doing it
intentionally, but that's why the bug was closed.
For the record, next time, the best thing to do is to change the version
in the bug report before you send it. But in this case it's not
necessary, as the same bug had already been filed several other times.
We're definitely aware that the version in testing is broken. We're in
the middle of a transition of responsibility for the package, but getting
that fixed is a high priority.
(Properly speaking, Julien probably could have merged it with those bugs
and marked it closed in the relevant version, but that's mostly busy-work
since the bug is properly tracked elsewhere.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
