Paul Gevers 08a6cdde6f Don't have britney create migration-references itself ...

The initial idea was to do this to bootstrap the baseline, but it turns out
that this has the drawback it triggers runs for a package that has a new
autopkgtest where it didn't have it in the version in the target suite. It was
considered harmless (as it would just have a failing reference), but due to
autodep8, package can have a passing result in the target suite while the new
autopkgtest is actually broken. Such a package should not be blocked / getting
a penalty.

The alternative is to make the check here smarter, but as this is only for
bootstrapping, lets do that outside of britney proper.

2018-07-29 14:03:41 +00:00

..

__init__.py

Move PolicyVerdict to britney2.policies

2017-11-02 19:31:11 +00:00

autopkgtest.py

Don't have britney create migration-references itself

2018-07-29 14:03:41 +00:00

policy.py

policies: Make policies suite name agnostic

2018-07-29 09:23:12 +00:00