ftbfs on yakkety
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
juju-core ftbfs on yakkety like this:
dh_golang
Use of uninitialized value $ENV{"DH_GOPKG"} in concatenation (.) or string at /usr/share/
warning: "/..." matched no packages
Use of uninitialized value in split at /usr/share/
can't load package: package .: no buildable Go source files in /<<PKGBUILDDIR>>
go list of targets failed with code 256, at /usr/bin/dh_golang line 48.
debian/rules:26: recipe for target 'binary' failed
This is my fault; I changed dh_golang in debian to use go list and friends to compute Built-Using, rather than processing Build-Depends and the way that juju-core's rules are set up doesn't let dh_golang find the Go packages. Perhaps dh_golang shouldn't override a GOPATH set in the environment (which I think would fix this) but something that's a bit strange about the juju packaging is that it uses any installed go package in favour of the one bundled by juju, rather than just the ones it build-depends upon. This is fine on a buildd, but it seems to me that it might be a bit confusing on a developer system. lxd does this sort of thing in it's packaging: https:/
I think I'll patch dh_golang tomorrow either way...
Related branches
- Martin Packman (community): Approve
-
Diff: 141 lines (+67/-23)3 files modifieddebian/control (+1/-0)
debian/helpers/setup-build-directory.py (+42/-0)
debian/rules (+24/-23)
Changed in juju-core (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core (Ubuntu): | |
status: | Triaged → Fix Released |