Comment 15 for bug 1846787

The autopkgtests regression on docker.io are unrelated to this change.

The failure is on debian/tests/basic-smoke; it happens because 'debootstrap stable <debian>' fails the gpg verification of the Release file -- the keys used for the Buster stable release are not found in Xenial's debian-archive-keyring.

This only happens on Xenial; on Bionic and later the debian-archive-keyring is sufficiently updated.

The workaround is to just patch docker.io/xenial to use 'debootstrap --no-gpg-check' (the debian debootstrap image is only used to run 'true' in a container).

The proper solution is a bit more involved on debian-archive-keyring; discussing this w/ cjwatson.

I'm not sure the proper solution is actually required on this case -- or even in the general case, as we haven't had bug reports yet about this since the Buster release in early July.

So we can probably just go with the workaround, but it's a non-runtime affecting change (build/test-time only), so would have to piggyback on another SRU to docker.io anyway, i.e., it won't make it to the archive just to fix this autopkgtest regression.

Thus, we should probably just ignore the docker.io regressions -- I'll test those w/ PPA build w/ the workaround above.