On Fri, Oct 24, 2014 at 01:31:55PM +0200, Tollef Fog Heen wrote: > > I would even go so far as to say that it's good that we're exposing these > > bugs now, during our release preparation process, so that they can be > > fixed prior to jessie. We need systemd-shim to work properly in jessie if > > we can find the resources to do that work; we know that a lot of users > > will want to continue using sysvinit for jessie. systemd is a big change, > > and, even if one thinks that the same thing that happpened with udev will > > happen to it in the long run, as with udev we need to support both > > configurations at least until one of them naturally fades away (if that > > happens). And, so far, it looks like the resources to make systemd-shim > > work will be available.
> I don't think the necessary manpower to fix those bugs is available. If > so, why are we now then at ten days before the freeze with bugs that > were made release critical in -shim more than a month ago with no > subsequent response from the maintainer? Is that bug #759745 which was assigned to systemd-shim 8 days ago and appears to be a duplicate of bug #757348, or bug #756076 which was marked *resolved* on September 10 and was reopened, with a subsequent history that in no way explains why it's been marked as "grave"? Regardless, "I don't think the RC bugs will be fixed" is still not an excuse for enforcing a different set of bugs via the dependencies of libpam-systemd. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org