Bug#924683: marked as done (binnmus for multiarch coinstallability)
Your message dated Sun, 17 Mar 2019 08:04:00 +0000
with message-id <0a6b4ffb-17fb-3e3f-30e6-3d44f9942b8d@thykier.net>
and subject line Re: Bug#924683: binnmus for multiarch coinstallability
has caused the Debian Bug report #924683,
regarding binnmus for multiarch coinstallability
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
924683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924683
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Helmut Grohne:
> 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
>
Scheduled, thanks.
~Niels
--- End Message ---
Reply to: