Please merge debian version of golang-golang-x-crypto-dev
Bug #1629412 reported by
Nicholas Skaggs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-go.crypto (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The current ubuntu (xenial / yakkety) packages are missing needed updates. Specifically, juju needs golang.
I can note that sid contains these updated packages, but yakkety is still missing them. See https:/
tags: | added: needs-debian-merge |
description: | updated |
summary: |
- golang-golang-x-crypto-dev missing acme/autocert + Please merge debian version of golang-golang-x-crypto-dev |
To post a comment you must log in.
I've done rebuild tests of the revdeps of golang-go.crypto in /launchpad. net/~vorlon/ +archive/ ubuntu/ multiarch/ +packages>. Results:
<https:/
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. 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. github- xenolf- lego: FTBFS on 32-bit archs, not a regression (present in yakkety release, package not built for those archs).
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-
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-
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.