A new Debian release may break your CI
What better way to start your week than discovering that Debian's latest release broke all your CI?
Running with gitlab-runner ... on a-random-builder 4mHpT2K9 Preparing the "docker" executor 00:03 Using Docker executor with image a-random-debian-buster-based-image ... [...] $ apt update && apt install -y --no-install-recommends python3 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Get:2 http://deb.debian.org/debian buster InRelease [122 kB] Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB] Reading package lists... E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates' ERROR: Job failed: exit code 1
To avoid that, don't forget that
apt update can also ask questions, and can also accept the
-y flag, making your
line look like this:
$ apt update -y && apt install -y --no-install-recommends python3