[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2018-10-11 Thread Neil Williams
** Also affects: lava (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Remove lava-dispatcher from ubuntu universe + Remove lava (lava-dispatcher & lava-server) from ubuntu universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2018-02-04 Thread Neil Williams
Yes. There is no support for Ubuntu at this time (same for lava-server). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava-dispatcher from ubuntu universe To manage notificat

[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2018-02-04 Thread Dimitri John Ledkov
Release team can badtest autopkgtests now, so it should be a problem. BTW, should this block remain in place for the Bionic LTS release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title:

[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2016-09-06 Thread Matthias Klose
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

[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2016-09-02 Thread Neil Williams
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 afte

[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe

2016-09-02 Thread Neil Williams
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