It seems go-crypto now depends on a sys/unix package which we don't have in gentoo yet: >>> Compiling source in /var/tmp/portage/dev-go/go-crypto-9999/work/go-crypto-9999 ... env GOPATH=/var/tmp/portage/dev-go/go-crypto-9999/work/go-crypto-9999:/usr/lib/go-gentoo go build -v -work -x golang.org/x/crypto/... WORK=/var/tmp/portage/dev-go/go-crypto-9999/temp/go-build852957153 src/golang.org/x/crypto/ssh/terminal/util.go:20:2: cannot find package "golang.org/x/sys/unix" in any of: /usr/lib64/go/src/golang.org/x/sys/unix (from $GOROOT) /var/tmp/portage/dev-go/go-crypto-9999/work/go-crypto-9999/src/golang.org/x/sys/unix (from $GOPATH) /usr/lib/go-gentoo/src/golang.org/x/sys/unix This also prevents from bumping the package.
Actually I was wrong, we have that as dev-go/go-sys. However that is also quite old and we need a newer one to compile current go-crypto. So ideally we should: * Bump go-sys to a newer snapshot. * Make go-crypto depend on go-sys. * Bump go-crypto as well to a newer snapshot.
I've updated the go-crypto ebuilds: commit 3a53cec38986055834621629c810d5734cb5d4df Author: Zac Medico <zmedico@gentoo.org> Date: 2018-08-19 16:57:16 -0700 dev-go/go-crypto: update 9999 ebuild Package-Manager: Portage-2.3.47, Repoman-2.3.10 commit d0ae10486b917df0d7443e11ba6ddf012f37b816 Author: Zac Medico <zmedico@gentoo.org> Date: 2018-08-18 18:23:11 -0700 dev-go/go-crypto: version bump to 0_pre20180816 Package-Manager: Portage-2.3.47, Repoman-2.3.10
