Paul Gevers 18633e275c

autopkgtest: figure out which packages from unstable are needed ...

Currently autopkgtest tries to install our trigger from unstable and the rest
from testing. If that fails, than autopkgtest has a fall-back to allow all
packages from unstable to be installed. This has two severe issues:

1) the version of the test and the package it came from may be out-of-sync

2) too much from unstable may be installed, even stuff that should not/is not
allowed to migrate as it breaks stuff.

Make sure that test depends also get added to triggers if they are broken.
E.g. imagine the following scenario: trigger X changes (breaks) the output
generated by Y. Package Z has Y in the test dependencies and compares the
output in the autopkgtest. We want to have the opportunity that a new version
is automatically fixing the situation.

Two use cases are currently unsupported: needs-build (autopkgtest restriction)
and test dependencies generated by autodep8.

2018-09-05 21:37:23 +02:00

..

policy-test-data

test_policy: Add additional tests of AgePolicy

2018-08-04 20:09:03 +00:00

__init__.py

inst-builder: Replace RelationBuilder with a set_relations method

2018-08-12 13:06:48 +00:00

mock_swift.py

autopkgtest: switch from testing=series to testing=testing

2017-09-08 11:08:22 +02:00

test_autopkgtest.py

autopkgtest: figure out which packages from unstable are needed

2018-09-05 21:37:23 +02:00

test_hint_parser.py

Use a proper Suite object for MigrationItem.suite

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

test_inst_tester.py

inst_tester: add is_pkg_in_testing

2018-09-05 21:27:41 +02:00

test_policy.py

SourcePackage: Add field for Build-Depends-Indep

2018-08-08 16:18:02 +00:00

test_yaml.py

Add 'unsatisifiable dependencies' to YAML excuses

2018-08-07 18:55:57 +00:00