And something on arm64 already forces this, despite only being in -proposed.
For example if someone tries
linux-libc-dev (<5.19.0-1),
to avoid this FTBFS for now that works on all other architectures (right now), but on arm64 gives me:
Missing build dependencies: linux-libc-dev (<= 5.19.0-1)
So while both still exist:
linux-libc-dev | 5.15.0-27.28 | kinetic | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
linux-libc-dev | 5.19.0-15.15 | kinetic-proposed | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
Probably some other dependency makes this non-avoidable for now.
And something on arm64 already forces this, despite only being in -proposed.
For example if someone tries
linux-libc-dev (<5.19.0-1),
to avoid this FTBFS for now that works on all other architectures (right now), but on arm64 gives me:
Missing build dependencies: linux-libc-dev (<= 5.19.0-1)
So while both still exist:
linux-libc-dev | 5.15.0-27.28 | kinetic | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
linux-libc-dev | 5.19.0-15.15 | kinetic-proposed | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
Probably some other dependency makes this non-avoidable for now.