On 31 October 2016 at 17:12, Michael Hudson-Doyle
<michael.hud...@canonical.com> wrote:
> The question is, do we backport the fixes for golang-1.6, or just remove it
> from the archive?
Looks like removal would be fairly straightforward; the only package
currently affected is "golang-github-docker-go", which could just as
well stop using patching and just use the pre-patched copy of
encoding/json embedded in upstream's source (since refreshing
_upstream's_ patches for Go 1.7 likely isn't worth the effort for such
a minor package IMO).
For reference:
$ ssh mirror.ftp-master.debian.org dak rm -Rn golang-1.6
Will remove the following packages from unstable:
golang-1.6 | 1.6.3-2 | source, all
golang-1.6-doc | 1.6.3-2 | all
golang-1.6-go | 1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el
golang-1.6-src | 1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el
Maintainer: Go Compiler Team <pkg-golang-de...@lists.alioth.debian.org>
------------------- Reason -------------------
----------------------------------------------
Checking reverse dependencies...
# Broken Build-Depends:
golang-github-docker-go: golang-1.6-go
golang-1.6-src
Dependency problem found.
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
