Control: tags -1 + patch
Control: forwarded -1
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/584
On Wed, 02 Oct 2024 at 16:14:57 +0200, Daniel Leidert wrote:
Attempting to build a container for Buster, I observe the following error:
...
The following packages have unmet dependencies:
dpkg-dev : Depends: bzip2 but it is not going to be installed
This is probably because Debian 10 'buster' reached end-of-life in June
2024, and was subsequently removed from deb.debian.org and
security.debian.org.
If you are still working with end-of-life branches of Debian for
whatever reason, there are several options:
1. Write a suitable sources.list(5) for it into a file,
using archive.debian.org, snapshot.debian.org or your own archival copy,
then set environment variable AUTOPKGTEST_APT_SOURCES_FILE to the path to
that file when you run autopkgtest-build-{docker,podman}. It will
overwrite the sources.list from the original Docker image.
2. Build a working "minbase" tarball using whatever mechanism you like best
(mmdebstrap or debootstrap or similar), and pass it to the the --tarball
option of autopkgtest-build-{docker,podman}.
3. Base your image on the debian/eol image instead:
autopkgtest-build-docker --image=debian/eol:buster ...
or
autopkgtest-build-podman --image=docker.io/debian/eol:buster ...
(This will change the default name used for output!)
In released versions of autopkgtest, the autopkgtest-build-docker
--mirror=... option is not enough, because setup-testbed currently
hard-codes security.debian.org.
I've opened
<https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/584> to
make it automatically select archive.debian.org - but if you're
routinely working with EOL branches of Debian, I'd recommend having your
own copy of it under your control (for example see
<https://www.freexian.com/lts/extended/docs/how-to-build-a-mirror/>), in
which case you will need to use AUTOPKGTEST_APT_SOURCES_FILE or
--tarball anyway.
smcv
