Inconsistent architecture availability across patch versions (23.08 / 24.02)

MariaDB MaxScale patch releases for the 23.08 and 24.02 series have inconsistent Debian package availability across architectures (amd64/arm64) and distributions. Certain patch versions are missing packages for one architecture or an entire distribution, with no documentation or release note explaining these gaps.

1. 1. Pattern

The issue appears in the most recent patch releases of both series. The gaps follow a similar pattern across both 23.08 and 24.02:

1. Earlier patch versions have full coverage for all distros and both architectures.
2. Starting around the 3rd-to-last patch release, individual arch/distro combos start disappearing (typically bullseye arm64 first).
3. The missing combinations vary between consecutive releases — it's not a permanent platform drop but rather *alternating gaps*, suggesting intermittent build failures in the CI/CD pipeline rather than intentional platform changes.

1. 1. How to reproduce

Browse the package pool for each version:

1. 1. 1. 24.02 examples

• https://dlm.mariadb.com/browse/mariadbmaxscale/24.02.5/debian/pool/main/m/maxscale/ — both arches, all distros ✅
• https://dlm.mariadb.com/browse/mariadbmaxscale/24.02.6/debian/pool/main/m/maxscale/ — bullseye arm64 missing ❌
• https://dlm.mariadb.com/browse/mariadbmaxscale/24.02.7/debian/pool/main/m/maxscale/ — focal entirely missing, bullseye arm64 missing ❌
• https://dlm.mariadb.com/browse/mariadbmaxscale/24.02.8/debian/pool/main/m/maxscale/ — trixie amd64 missing ❌

1. 1. 1. 23.08 examples

• https://dlm.mariadb.com/browse/mariadbmaxscale/23.08.9/debian/pool/main/m/maxscale/ — both arches, all distros ✅
• https://dlm.mariadb.com/browse/mariadbmaxscale/23.08.10/debian/pool/main/m/maxscale/ — bullseye arm64 missing ❌
• https://dlm.mariadb.com/browse/mariadbmaxscale/23.08.11/debian/pool/main/m/maxscale/ — focal dropped, bullseye arm64 missing, trixie arm64 missing ❌
• https://dlm.mariadb.com/browse/mariadbmaxscale/23.08.12/debian/pool/main/m/maxscale/ — focal dropped, trixie amd64 missing ❌

1. 1. Impact

• Users pinning MaxScale to a specific patch version (e.g. via apt preferences) may find that a routine upgrade breaks on one architecture while working on the other.
• Multi-arch environments (e.g. mixed amd64/arm64 fleets, or CI pipelines running on both) cannot reliably target the same MaxScale patch version.
• Ansible roles and automation that install a specific version will fail unpredictably depending on the target architecture.

1. 1. Expected behavior

All patch releases within a supported series should provide packages for all supported architecture/distribution combinations, or clearly document in the release notes when a platform is intentionally dropped and why.