Hi Joern, you did nothing wrong. Severity and justification looks quite right to me.
On Fri, Jul 04, 2014 at 12:42:43PM +0200, Joern Heissler wrote: > On Fri, Jul 04, 2014 at 09:08:21AM +0000, Gerrit Pape wrote: > > I looked into latest policy, but did not find anything about systemd > > support. I'm surprised that this is now a release critical bug, and the > > package marked for removal. What's the justification? > > With the current stable (wheezy) this package works for most users. > > I assume that the next stable release, Jessie, will use systemd by > default: https://lists.debian.org/debian-ctte/2014/02/msg00405.html > > So upon release, when this bug is not fixed yet, the package becomes > useless for most users. > "makes the package in question unusable" hence I choose "grave" as severity. Yep, fully understandable from you POV, thanks for filing the bug. > * Can I only choose a release-critical severity for bugs affecting the > current stable but not the next stable? Bug reporters are free to choose any severity they think applies. It's the maintainer setting it straight if she doesn't agree. I'm just asking debian-devel how to resolve this. I heard systemd is backward-compatible to sysvinit, but looks like this doesn't apply to the inittab interface. Regards, Gerrit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
