Debian 12 release tasks

[emillon]

Hi, Debian 12 ("bookworm") is planned to be released this week. This means that the distro that was known as debian testing for the past 2 years is now known as debian 12. One thing this means for opam-repo-ci is that packages marked as known to be failing in debian-testing should be expected to be failing in debian-12. (Technically this change needs to happen once debian-12 (new stable) is added to base-images.)

As an aside, I'm not sure why there are so many packages that are marked as allowed failures for debian-unstable and not for debian-testing since most of the time these distributions are fairly close to each other. I suspect that it makes sense to do the above for packages marked as failing on unstable too.

[avsm]

Thanks for flagging this up @emillon! What packages do you have in mind that are marked as failing? I only see two in opam-repo (both conf- packages), and no OCaml packages. Should I be looking for something other than "debian-testing" ?

[emillon]

My train of thoughts was the following:

• earlier this year, I noticed that several packages were failing on debian 11 in CI, but had been marked as failing on debian unstable earlier (#22983 #22985 #22993 #22995 #23066)
• there's a ton of packages (precisely, 105) that are marked x-ci-accept-failures: ["debian-unstable"]
• the same phenomenon is going to happen for debian 12 so it's useful if we can be proactive with that.

While writing this bug report, I remembered that it's not unstable that becomes stable, it's testing that becomes stable. So my interrogation remains: why aren't these packages marked as failing on testing?

In any case: the important thing for CI is that these failures should be ignored when these packages are being built as part of the revdeps run. So it's when the base-image config is going to pick debian 12 for revdeps runs that we'll have to fix that.