Bug #5685
open
Dropping debian 10 (buster)
Added by osmith over 1 year ago.
Updated about 1 year ago.
Description
Debian 10 was EOL in 2022-08. It still has LTS support (https://wiki.debian.org/DebianReleases).
laforge:
- Do we want to remove it form OBS now? (after migrating all docker containers to debian 11)
- In general, when do we want to stop supporting old Debian releases?
Currently it is still in use by various docker containers:
$ git grep debian-buster
debian-buster-build/Makefile:DISTRO=debian-buster
debian-buster-jenkins/Makefile:DISTRO=debian-buster
debian-buster-simtrace2/Dockerfile:FROM $USER/debian-buster-build
fpga-build/Dockerfile:FROM $USER/debian-buster-build
jenkins-common.sh: debian-buster-*) echo "debian-buster" ;;
jenkins-common.sh: debian-buster-*) echo "debian:buster" ;;
nplab-m3ua-test/jenkins.sh: "debian-buster-build" \
nplab-sua-test/jenkins.sh: "debian-buster-build" \
osmo-gsm-tester/Dockerfile:FROM $USER/debian-buster-jenkins
osmo-gsm-tester/jenkins.sh: "debian-buster-jenkins" \
sigtran-tests/Dockerfile:FROM $USER/debian-buster-build
- Related to Feature #4107: Start systemd services as non-root user added
Is there a ticket to track container migration to Debian 11?
msuraev wrote in #note-3:
Is there a ticket to track container migration to Debian 11?
Yes, see #4969.
- Related to Feature #4969: Migrate docker containers from debian 9 (stretch) to 11 (bullseye) added
- Assignee changed from laforge to manawyrm
- % Done changed from 0 to 40
osmith wrote:
laforge:
- Do we want to remove it form OBS now? (after migrating all docker containers to debian 11)
- In general, when do we want to stop supporting old Debian releases?
We don't really have a clear policy. Knowing that many users are slow to migrate from legacy distros, I would argue for a bit of caution. So I'd say:
- our own docker containers / ttcn3 / testing etc. should not use distributions after EOL, we should migrate as soon as they go EOL or ASAP if they already are
- removal of package builds from OBS is not that urgent, as long as we don't see build or unit test failures just on those old distros.
- If we do see build or unit test failures, we should remove the distro from the builds and not invest time in work-arounds.
- Assignee changed from manawyrm to osmith
Note: Debian 9 is also used by create-vm.sh script in osmo-ci - not sure if it's actually used by some of the jobs.
Rhizomatica needs debian 10 for forseeable future.
Also available in: Atom
PDF
