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

[Mark Hindley <mark@hindley.org.uk>]

Sam,

Many thanks for your input on this.

On Tue, Sep 03, 2019 at 03:12:18PM -0400, Sam Hartman wrote:
> 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.

Absolutely.

> >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.

My suggestion is to raise #934491 and/or #935910 to RC status and for the
Release Team to remove the manual migration block. That way, once all RC bugs
are satisfactorily resolved, normal migration can take place.

Thanks

Mark