1.0.2-1ubuntu1~14.04.1 in trusty-proposed needs to depend on gccgo-go not gccgo
Bug #1510288 reported by
Michael Hudson-Doyle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
go-md2man (Ubuntu) |
Confirmed
|
Undecided
|
dann frazier | ||
Trusty |
In Progress
|
High
|
dann frazier |
Bug Description
[Impact]
This package does not currently build on architectures that do not support golang, but do have gccgo support. Since this package is a build-dependency for docker.io, docker.io is also not available.
[Test Case]
Build docker.io in trusty on an impacted architecture (I'm using arm64).
[Regression Risk]
The changes to enable gccgo are restricted to architectures that currently do not build.
tags: | added: patch |
Changed in go-md2man (Ubuntu): | |
assignee: | nobody → dann frazier (dannf) |
Changed in go-md2man (Ubuntu Trusty): | |
status: | New → Confirmed |
assignee: | nobody → dann frazier (dannf) |
importance: | Undecided → High |
description: | updated |
Changed in go-md2man (Ubuntu Trusty): | |
status: | Confirmed → In Progress |
To post a comment you must log in.
OK, but this is a new package in Trusty and docker.io in Trusty has never built against arm64, powerpc or ppc64el. So this isn't an SRU regression.
I guess we could fix this in the backport, although it's a bit awkward since we're using a script to generate the backports and I'd prefer to not have to special case this one. But does it gain anything if we're not aiming to enable extra architectures for Docker in Trusty anyway?