Rolf Leggewie <debian-b...@rolf.leggewie.biz> (22/01/2012): > 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.
Erm. Breaking the dpkg configuration phase means you can break alot of other packages. On mine that was “just” glib*, gtk*, so the whole X session was totally broken. > 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. [ more whining ] Heh, welcome to maintaining libraries. The policy has details, lintian helps one not to trivial errors, and fixing the package (be it about where to ship this or that part of the -dev/lib packages, or about fixing upgradability issues) is AFAICT trivial. Why don't you just fix the package and move to other things? Mistakes happen every day, it's not the end of the world to have a grave bug in ones package if one learns about it and tries to avoid doing the same mistakes again. > 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. Wrong. Policy 7.6 says it's an RC bug. Mraw, KiBi.
signature.asc
Description: Digital signature
