reason for removal of zeroc-ice on armhf and arm64.

[Peter Green <plugwash@debian.org>]

I recently became aware that mumble's build-dependencies were no longer
satisfiable on armhf due to a missing zeroc-ice. I looked at the build
logs for zeroc-ice and all were green. So I looked at the removal log
and found the following.

> [Date: Sun, 12 Feb 2023 17:56:51 -0000] [ftpmaster: Scott Kitterman]
> Removed the following packages from unstable:
>
> libzeroc-ice-dev |  3.7.8-2.1 | arm64, armhf
> libzeroc-ice3.7 |  3.7.8-2.1 | arm64, armhf
> libzeroc-icestorm3.7 |  3.7.8-2.1 | arm64, armhf
> mumble-server |    1.3.4-4 | arm64, armhf
> php-zeroc-ice |  3.7.8-2.1 | arm64, armhf
> python3-zeroc-ice |  3.7.8-2.1 | arm64, armhf
> zeroc-glacier2 |  3.7.8-2.1 | arm64, armhf
> zeroc-ice-compilers |  3.7.8-2.1 | arm64, armhf
> zeroc-ice-utils |  3.7.8-2.1 | arm64, armhf
> zeroc-icebox |  3.7.8-2.1 | arm64, armhf
> zeroc-icebridge |  3.7.8-2.1 | arm64, armhf
> zeroc-icegrid |  3.7.8-2.1 | arm64, armhf
> zeroc-icepatch2 |  3.7.8-2.1 | arm64, armhf
> Closed bugs: 1031160
>
> ------------------- Reason -------------------
> RoQA; openjfx no longer builds on arm64 and armhf, build-depends not available

This strikes me as strange in a couple of ways.

1. The only relationships of zeroc-ice to openjfx are in build-depends-indep
   and in the binary dependencies of an arch all package. Afaict it is perfectly
   normal for build-depends-indep and the binary dependencies of arch all
   packages to only be satisfiable on a subset of the architectures where
2. Only one of the two binaries from the mumble source package was removed.

Was this removal just a mistake? or was there a reason behind it that I am not
seeing?