Comment 1 for bug 1629412

I've done rebuild tests of the revdeps of golang-go.crypto in
<https://launchpad.net/~vorlon/+archive/ubuntu/multiarch/+packages>. Results:

syncthing: FTBFS. not a regression, package in the release pocket also ftbfs in rebuild test, and package in yakkety-proposed, though built, FTBFS on a rebuild with all of -proposed minus golang-go.crypto with essentially the same test failures.
snapd: release version FTBFS, not previously reported in the rebuild test; -proposed version builds.
rkt: FTBFS in yakkety release, not a regression. dep-wait in yakkety-proposed.
juju-mongo-tools3.2: amd64-only build (test) failure; I can't imagine how the progress bar output is related to golang-go.crypto, so retrying the build and otherwise disregarding.
juju-2.0: yakkety release version FTBFS with uninstallable build-deps seemingly unrelated to golang-go.crypto. -proposed version builds fine, but of course this version has vendorized golang-go.crypto...
influxdb: release version FTBFS, reported in rebuild test; -proposed version builds.
golang-github-xenolf-lego: FTBFS on 32-bit archs, not a regression (present in yakkety release, package not built for those archs).
fleet: uninstallable build-deps due to etcd FTBFS. But also, FTBFS in yakkety release with downgraded golang-go.crypto.
etcd: FTBFS that's reproducible without golang-go.crypto.

So this looks good for moving ahead with the transition.