Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core

[Matthias Klumpp]

2014-07-20 12:00 GMT+02:00 Elimar Riesebieter <riesebie at lxtec.de>:
> * Michael Biebl <biebl at debian.org> [2014-07-17 17:25 +0200]:
>
>> Am 17.07.2014 16:20, schrieb Elimar Riesebieter:
> [...]
>> > I don't see the intention?
>>
>> You should read the changelog then. Not understanding the intentions is
>> not a justification for reopening a bug report which has been closed by
>> its maintainer.
>
> It seems that the intention is to push systemd as the only init
> system. Why did you upload 208-6 _before_ systemd-shim was adjusted?
> sysvinit is broken by that injudicious action!
Systemd 208 brings a lot of fixes and has been out for a year. The
systemd-shim people knew about the issues with systemd >= 205 and have
been notified that a new systemd will be uploaded to Debian in 4months
last November or December, if I remember correctly. A bug was filed
against the shim, and the systemd maintainers waited a huge extra-time
to see if the shim will get ready. But since this is not the case,
systemd 208 improves a lot of things and all necessary actions have
been taken to get the shim ready in time (which didn't happen), the
upload was absolutely justified.
I recommend helping
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 to make the
shim available again.
Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/