elogind testing migration

Mark Hindley mark at hindley.org.uk
Thu Oct 31 16:15:20 GMT 2019



On Thu, Oct 31, 2019 at 12:36:37PM +0100, Thorsten Glaser wrote:
> On Thu, 31 Oct 2019, Mark Hindley wrote:
> > On Thu, Oct 31, 2019 at 04:38:48AM +0100, Joost van Baal-Ilić wrote:
> > > I'd just wait a couple of days and see what happens.
> It says today:
>      * Migration status for elogind (239.3+20190131-1+debian1 to 241.3-1+debian1): Will attempt migration        
>        (Any information below is purely informational)

Yes, which I think means that britney attempts migration. This, however,
fails[1] with:

trying: elogind
skipped: elogind (1, 9, 344)
    got: 30+0: a-1:a-0:a-0:a-0:i-28:m-0:m-0:p-0:s-1
    * i386: elogind, libelogind-dev, libelogind0, libpam-elogind

I have installed the sid packages in a bullseye docker container with no
problems. I can't see the problem. However, since asking the Release Team for
help with this back in July was the reason elogind was blocked, I am reluctant
to go down that path again.


More information about the Debian-init-diversity mailing list