Bug#924683: binnmus for multiarch coinstallability
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: binnmu
Dear release team,
We don't epxect much churn in unstable anymore, so it is a good time to
cover up for past mistakes in binNMUing Multi-Arch: same packages and
make them coinstallable again. I know that you dislike excessive binNMUs
just to get the versions right, but the last time I asked was before the
release of stretch. It turns out than there are only 7 skewed packages
left. Would you be so kind and binNMU them to make their versions match?
# 61 affected
nmu libxt . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
# 32 affected
nmu libxdamage . amd64 arm64 armel armhf i386 mips mipsel ppc64el s390x . unstable . -m "multiarch sync"
# 19 affected
nmu rustc . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
# 8 affected
nmu libxkbfile . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
# 5 affected
nmu libxmu . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
# 3 affected
nmu libidl . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
# 1 affected
nmu libglu . amd64 arm64 armel armhf i386 mips64el ppc64el s390x . unstable . -m "multiarch sync"
I expect this to be my only binNMU request for multiarch syncing during
the buster cycle.
Helmut
Reply to: