On Thu, 23 Nov 2023 at 05:45, Otto Kekäläinen <o...@debian.org> wrote: > > Hi! > > One more clarifying question: > > > > Thus a third thing the README could advise on is how Debian Developers and > > > Debian sysadmins are advised to build CI systems and test upgrade paths > > > for > > > the next 10 years as what worked in the past 10 years does not apply as-is > > > anymore. > > People using CI systems will get an updated debootstrap in the next > > point release and everything will be fine. > > Do you refer above to the next Bookworm point update (scheduled on Dec > 9th according to https://release.debian.org/) or do you mean in > general that all CI upgrades tests will start working after the next > point release of both Bookworm and Bullseye and Buster? > > I am currently struggling to grasp how I should get for example > MariaDB 10.5 / Buster to MariaDB 10.11 / Bookworm testing running > again as usrmerge 38 removed the workaround the CI was relying on. > Example of current CI run: > https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/4945062. > Are you saying that a point release of Buster is going to do something > that CI systems can continue to operate?
Just create the chroot for the CI with --merged-usr and all will be fine. Debootstrap in Buster is not going to be updated to do it automatically, only in Bookworm/Bullseye.
