Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

[Sam Hartman <hartmans@debian.org>]

>>>>> "Mark" == Mark Hindley <mark@hindley.org.uk> writes:

    Mark> Michael,
    Mark> On Tue, Sep 03, 2019 at 04:56:13PM +0200, Michael Biebl wrote:
    >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934491
    >> 
    >> This bug report should be taken into account here. Not sure why
    >> this is not marked as RC given that it can pretty much hose your
    >> system.

    Mark> If you actually read to the end of that report you will see
    Mark> the suggestion that this behaviour is actually caused by apt
    Mark> and/or dpkg, not elogind.

First, thanks for your work on elogind.
I appreciate the professional manner you've handled the communication
with the release team on this issue, the professional manner in which
you worked with the systemd maintainers to get to the current elogind
design, and the professional manner in which you worked through##934491.

I do agree with simon that #934491 does leave the system in a really bad
state.  And while I agree with you that it is not elogind's fault, it's
a situation that tends to only come up when elogind is in the picture.
I think Michael has a point that we should consider the impact of
#934491 on bullseye before introducing the elogind in sid to bullseye.

>From where I sit that impact is fairly significant, and I can see
wanting to fix apt or dpkg or whatever we're going to fix prior to
making that change in bullseye.

I can also see the argument that it's fairly early in the cycle and this
issue is not elogind's fault as discussed in #934491.