Bug#893754: autopkgtest 5.1 "autopkgtest-default-release" breaks tests that exercise apt
On 22-03-18 01:18, Steve Langasek wrote:
> apt_pkg.Error: E:The value 'bionic' is invalid for APT::Default-Release as such
> a release is not available in the sources
I suspect that this is an Ubuntu issue as this is just an apt option:
(see man apt_preferences).
Interestingly, installing the packages went OK, so it's not autopkgtest
that is broken. I see multiple packages from bionic-proposed being
installed (eg. Get:14 http://ftpmaster.internal/ubuntu
bionic-proposed/main armhf dconf-service armhf 0.26.1-3ubuntu2 [24.5 kB])
> So far we've seen test failures from update-manager,
> ubuntu-release-upgrader, and snapcraft - none of which are present in
> Debian. It possibly affects all consumers of python-apt (so may affect
> python-apt itself, which is present in Debian). Since python-apt
> autopkgtests appear to be passing in Debian according to
> <https://ci.debian.net/packages/p/python-apt/unstable/amd64/>, this may be
> an Ubuntu-specific problem
I am not sure where python-apt gets it's data from, but I suspect it may
be python-debian/python3-debian that needs to become aware of the Ubuntu
release names. At least, I found the Debian release names in
> , or perhaps 5.1 is not yet rolled out to
It is, as it is a prerequisite for debci on testing, the future of
britney being aware of autopkgtest results.
> To unbreak Ubuntu I have reverted the changes from the merge of the pin-v2
> branch in our production deployment.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature