Remove lava (lava-dispatcher & lava-server) from ubuntu universe

[Neil Williams]

The LAVA Software Team at Linaro has discussed the complications of having lava-server and lava-dispatcher in Ubuntu Xenial 16.04LTS and, despite having fixed packages available for sync in Debian unstable, it will be better if lava-server and lava-dispatcher are removed from Ubuntu universe before Xenial is released as the LAVA software team do not have the resources
to properly support these packages through the lifetime of Xenial LTS at the versions currently available. Please also block migration of these packages back into Ubuntu.

lava-tool is completely unaffected by this step and will be fully supportable in Xenial, so please keep that.

[Adam Conrad (adconrad)]

(base)adconrad@nosferatu:~$ demote-to-proposed -m 'LP: #1554843' lava-server lava-dispatcher
Demoting packages to xenial-proposed:
 lava-server 2016.2-3 in xenial
 lava-dispatcher 2015.9-1ubuntu1 in xenial
Comment: LP: #1554843
Demote [y|N]? y
Remove lava-server from release [y|N]? y
Remove lava-dispatcher from release [y|N]? y
2 packages successfully demoted.

[Jeremy Bícha (jbicha)]

Is this block still desired for yakkety?

[Neil Williams (codehelp)]

Yes, the block should remain in place until there are upstream resources to maintain and test on Ubuntu and likely until the current migration has completed in the upstream codebase (which will be in 2017).

[Matthias Klose (doko)]

well, then please file a removal request. lava-dispatcher unfortunately has autopkg tests that trigger on other packages. Please be honest and just have it gone.

[Neil Williams (codehelp)]

That was my understanding of the block - to keep what has been released but prevent new releases in Debian from arriving in Ubuntu until someone offers to maintain a LAVA instance in/for Ubuntu. Why was 2016.8-1 allowed to bypass the block?

There should be no releases of lava-dispatcher in Ubuntu after 2014.9.post1 but I'll leave it up to Ubuntu developers to decide whether to apply this to wily as that's been released. yakity should not have lava-dispatcher nor should any further uploads to Debian migrate into Ubuntu until further notice.

[Neil Williams (codehelp)]

That was my understanding of the block - to keep what has been released but prevent new releases in Debian from arriving in Ubuntu until someone offers to maintain a LAVA instance in/for Ubuntu. Why was 2016.8-1 allowed to bypass the block?

There should be no releases of lava-server in Ubuntu after 2014.9.post1 but I'll leave it up to Ubuntu developers to decide whether to apply this to wily as that's been released. yakity should not have lava-server nor should any further uploads to Debian migrate into Ubuntu until further notice.

[Matthias Klose (doko)]

each release has two pockets, proposed and release. packages need to migrate to the release pocket, and one requirement is that the autopkg tests of the reverse dependencies succeed. This is now the case for the lava packages, but wasn't before. So every time the lava autopkg test fails, we are stuck with migrations for other packages.

[Dimitri John Ledkov (xnox)]

Release team can badtest autopkgtests now, so it should be a problem.

BTW, should this block remain in place for the Bionic LTS release?

[Neil Williams (codehelp)]

Yes. There is no support for Ubuntu at this time (same for lava-server).

[Steve Langasek (vorlon)]

I see that there are no longer installability problems for the lava source package in Ubuntu. Should it still be kept out of Ubuntu?

[Matthias Klose (doko)]

removed the block-proposed. it's in Debian bullseye, which is longer supported than 21.04.