New upstream version of elogind (v241.1)

Mark Hindley mark at
Mon Mar 25 21:11:34 GMT 2019

On Wed, Mar 13, 2019 at 06:13:34AM +0000, Mark Hindley wrote:
> > That's not really a fault on our side -- required patches were provided
> > since January _2018_ (then June, then November, December, ...), without any
> > response from the systemd side -- but with the last minute change of plan,
> > to patch not policykit but elogind, it's elogind that would need to get a
> > freeze exception.
> > 
> > Not sure what to do.
> Yes, I appreciate this difficulty.
> My suggestion is to upload into unstable. Once it is there we can try to get it
> accepted. If not for the initial release of buster maybe the first point
> release? Having the ABI compatible version in unstable will help with getting
> the default-logind | logind dependencies done as well -- as the lack of it was
> sometimes being used as an excuse not to change the dependencies.


Many thanks for uploading.

As elogind has passed 10 days in unstable with no new bugs, I have had a go at
getting it unblocked. See #925489


More information about the Debian-init-diversity mailing list