Bug#926316: systemd: Installing the systemd package switches the init system to systemd

[Felipe Sateler]

On Thu, Apr 4, 2019 at 7:15 AM Michael Biebl <biebl at debian.org> wrote:

> Am 03.04.19 um 20:34 schrieb Felipe Sateler:
> > On Wed, Apr 3, 2019 at 1:23 PM Michael Biebl <biebl at debian.org
> > <mailto:biebl at debian.org>> wrote:
>
> >     I have no idea how common that is, so maybe an alternative could be
> to
> >     move the libpam-systemd Recommends from systemd to systemd-sysv
> >     (alongside the existing libnss-systemd).
> >
> >
> > Makes a lot of sense to me.
> >
> >
> >     WDYT? Is it too late in the release cycle to make such a change?
> >
> >
> > I don't know. Most likely we would need a tight dependency on systemd,
> > to ensure at least one pacakge Recommends libpam-systemd.
>
> If we want to ensure that, we'd have to add a versioned systemd-sysv
> dependency to systemd (or a versioned Breaks for that matter). Both are
> problematic.
> But I might be misunderstanding what you have in mind here.
>

That's precisely what I meant.  Otherwise you might end up with old
systemd-sysv + new systemd => nothing depends on libpam-systemd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190404/3d7f1214/attachment.html>