Ok, this needed to be on top of the 2022.02.21 cycle. Unfortunately this one was sitting in proposed unreleased (waiting on stakeholder-signoff) when the respin was started. So rather than starting against -updates we needed to start with -proposed. Confusing much? Yes.
You can tell if you have the right version by looking at the debian.azure/tracking-bug file, which has the spin in it.
Ok, this needed to be on top of the 2022.02.21 cycle. Unfortunately this one was sitting in proposed unreleased (waiting on stakeholder- signoff) when the respin was started. So rather than starting against -updates we needed to start with -proposed. Confusing much? Yes.
You can tell if you have the right version by looking at the debian. azure/tracking- bug file, which has the spin in it.