[Bug 1541334] Re: Do not run britney on all of proposed

2016-02-03 Thread Martin Pitt
You can't remove it, as the thing that adds it is the autopkgtest worker and testbed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541334 Title: Do not run britney on all of proposed To manage

[Bug 1541334] Re: Do not run britney on all of proposed

2016-02-03 Thread Robert Bruce Park
I'm talking about removing it from the indexes: http://bazaar.launchpad.net/~cupstream2distro- maintainers/bileto/trunk/view/head:/britney/fetch-indexes#L84 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1541334] Re: Do not run britney on all of proposed

2016-02-03 Thread Robert Bruce Park
Instructions unclear: Should I remove -proposed *now* or do I need to wait for you to do something first? ** Changed in: bileto Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1541334] Re: Do not run britney on all of proposed

2016-02-03 Thread Martin Pitt
I think you should keep the indexes, they will make britney check installability against other -proposed packages which is useful. The thing Timo was spotting was that the autopkgtests run against all of -proposed, but CI train's britney cannot influence that. -- You received this bug

[Bug 1541334] Re: Do not run britney on all of proposed

2016-02-03 Thread Martin Pitt
It would actually not be wrong IMHO. Britney does installability tests in isolation, and for a fair while we have set up apt pinning to also run the tests in isolation -- i. e. we only install the trigger from -proposed, but the tested package (if different than the trigger) and all other test