On Mon, Jan 26, 2015 at 5:49 PM, Don Armstrong wrote: > On Mon, 26 Jan 2015, Michael Gilbert wrote: >> Why? Option A, i.e. the only option, is already the status quo, so >> what's the point? > > It affirms the decisions which have been made by the other teams in > Debian, and resolves this particular issue. Issues which are properly > submitted to the CTTE have to be resolved, and the way that they're > resolved is with a resolution. > >> What possibly is there to gain from further init system meddling just >> when the clouds were clearing? > > I'm unsure how this particular resolution meddles at all with the init > system decision; it explicitly doesn't change anything, and points out > the multiple different ways that Developers have worked to mitigate any > issues with the transition. > > If your point is that we shouldn't resolve this issue at all, and should > simply leave the bug open in the BTS, I disagree completely.
No, my point is that the init system shells loaded into this shotgun are known to be explosive, already causing mass injury and even casualty to the project, and there is no reason to think they are any less volatile today. Declining to rule is a perfectly legitimate outcome and reason enough to close this request, but that option unfortunately doesn't exist on this ballot. Please consider not pulling the trigger again? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
