elogind testing migration

Mark Hindley mark at hindley.org.uk
Fri Nov 1 06:52:13 GMT 2019

On Thu, Oct 31, 2019 at 05:19:17PM +0100, Thorsten Glaser wrote:
> On Thu, 31 Oct 2019, Mark Hindley wrote:
> > Yes, which I think means that britney attempts migration. This, however,
> > fails[1] with:
> fail*ed*, wait a night, then we’ll know more.

Still failing in the latest britney runs:

Generated on: 2019.10.31 16:08:23 +0000
Arch order is: amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
info: main run


trying: elogind
skipped: elogind (0, 10, 351)
    got: 30+0: a-1:a-0:a-0:a-0:i-24:m-0:m-0:p-0:s-5
    * s390x: elogind, libelogind-dev, libelogind0, libpam-elogind

And the next one failed for mipsel.

It looks to me as if the arch is random -- whatever britney tries first?
But I can't see the issue.




More information about the Debian-init-diversity mailing list