Hi Alexander! There is something that I don't understand. How are we supposed to follow this move from mirrors to archive.debian.org then if there is no fixed date when BPO will be removed form mirrors? Will bullseye-backports be available from August 15th in the archive.debian.org mirror? A bit of context: The recent removal of buster-backports broke our CI [1], we fixed it by redeploying Debian Buster images with the correct sources.list (our VMs are based on cloud-init images [2] that still contain the wrong sources.list as of today BTW). Can you point me to the right direction/documentation or how you would handle this? Thanks! -- Faustin [1] https://buildbot.mariadb.org/#/builders/436/builds/15268/steps/2/logs/stdio [2] https://cloud.debian.org/images/cloud/buster/latest/ Alexander Wirt <formorer@debian.org>, 16/04/2024 – 22:08:54 (+0200): > Hi, > > Debian Backports does not support LTS [1], therefore buster-backports is unsupported since August 1st > 2022. Despite of the documentation buster-backport was still available on the mirrors, that changed > recently with the archival of buster-backports. Unfortunately I missed to create an announcement in > 2022 which led so some surprise, I have to apologize for that. Please take this as the missing > announcement. > > Short reminder: on August 15th bullseye-backports will be deprecated and can be removed at any time > from the mirrors after that date. A seperate announcement will follow in August. > > > formorer - backports ftpmaster > > [1] https://backports.debian.org/Instructions/#index4h2 - > Second, Packages in backports-sloppy are > provided "as-is" and have no official support. Like old-stable-backports, > old-stable-backports-sloppy is taken offline one year after a new Debian release has been made. >
Attachment:
signature.asc
Description: PGP signature