I've now come to the conclusion that this is in fact actually not an RC bug, none of the criteria listed on http://www.debian.org/Bugs/Developer#severities for severity grave apply. The original setting of "important" turns out to have been spot on.
The current package is installable just fine. While no doubt resulting in a bit of an ugly state, the update from one particular unstable package to another breaks but also works at least to the point of not leaving the package unusable and according to Paul there is also an easy workaround to resolve the situation. Nothing qualifying for grave severity that I can see. I find it highly irritating that nobody wanted to properly maintain this package for years and now that I've taken on this difficult task of cleaning up this year-long neglect everybody and their uncle thinks they know better how to do that. And in all honesty, this may very well be the case (I certainly make many mistakes along the way) but the fact remains nobody else stepped up to the plate when it was necessary. I take cleaning up the package and maintaining a high quality seriously and would appreciate if those who never cared about it to not constantly making my life more difficult than it needs to be. This bug never affected testing, it's in fact not an RC bug even for unstable itself. Anybody who blocks the current package from going to testing is not doing Debian a favour. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
