Control: retitle -1 unblock: golang-go.crypto/1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1
Looking at the auto removals list [1], it seems there are about 64 reverse build dependencies on this package. Using the updated packaging [2], built against testing, I was able to successfully rebuild nearly all of them. The two failures I had were with: - runc - restic The package runc is facing removal from testing for other reasons [3]. I don't think it makes sense to hold up anything for this package. The packaging for restic is hosted in a private repository. The build failure seems to have nothing to do with the changes made in this upload. Also, the version in unstable is a few "minor" versions of what is in testing. For these reasons, I would like to file an RC bug against restic and request the maintainer handle this one separately from this issue. As for the remaining 62 successful builds. Would it be possible to unblock this package and request an nmu rebuild against those packages in testing (after migrated) and unstable (soon)? Side note: It'd be a neat policy if we treated experimental like unstable during freeze, leaving unstable to be only for testing changes going into new-stable(testing). If that's written in policy somewhere, I've never read it. [1] https://udd.debian.org/cgi-bin/autoremovals.cgi [2] http://cdn-fastly.deb.debian.org/debian/pool/main/g/golang-go.crypto/golang-go.crypto_0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1.dsc [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855208 [4] https://git.gueux.org/restic.git -- Michael Lustfield
