There has been a lot confusion about this bug. As the reporter, I am
happy to say vivid packaging (or cloud/builder images) were fixed last
week. Without any changes to juju packaging. Launchpad and lxc can
again built vivid ppc64el packages without explicitly setting the GOARCH
to match the dpkg
** Changed in: juju-release-tools
Status: Triaged => Invalid
** Changed in: gccgo-go (Ubuntu Vivid)
Status: Confirmed => Fix Released
** Changed in: gccgo-5 (Ubuntu Vivid)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of U
The last 2 Lp builds of juju packages succeeded, as does my own builds.
I think this issue resolved itself since I did not change packaging
rules. I will do a little more investigation, but hope to close this bug
in a few hours.
--
You received this bug notification because you are a member of Ub
It is my understanding that GOARCH doesn't include the endian
information on any architecture. So the assumption to use ppc64el seems
to be outdated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14177
the default gccgo in vivid is gccgo-5. Please check that all needed
patches are available in vivid. the gccgo-go package should be removed,
or just contain symlinks pointing to go-5 and gofmt-5.
** Also affects: gccgo-5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-4.9
I wouldn't mind a backport of gccgo-5 to trusty, if needed.
** Changed in: gccgo-5 (Ubuntu)
Status: New => Incomplete
** Also affects: gcc-4.9 (Ubuntu Vivid)
Importance: High
Status: Invalid
** Also affects: gccgo-go (Ubuntu Vivid)
Importance: High
Status: Confirmed
** Changed in: gcc-4.9 (Ubuntu)
Status: New => Confirmed
** Changed in: gccgo-go (Ubuntu)
Importance: Undecided => High
** Changed in: gcc-4.9 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
It turns out the vivid package does not yet have the needed patch from
https://go-review.googlesource.com/#/c/1840/ we'll have to wait for an
upstream release I guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
OK, jamespage confirmed a port to precise is not happening, as there's
no ppc64 support in there. That's fine - let's see what we can do for
trusty though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
There's an updated gccgo-go version for vivid -
https://launchpad.net/ubuntu/+source/gccgo-go/1.2.1-0ubuntu7 which
includes fixes for a number of issues we're seeing (tests failing,
builds failing due to duplicate symbols, random instabilities). Why is
this 1.2.1-0ubuntu7 not backported to trusty (
** Description changed:
The vivid ppc64el builds are failing. The last success was on
2015-01.20. their first failure was on 2015-01-23.
We suspect that golang-go sets the wrong GOARCH in vivid.
We cannot see the build logs because Lp is a punk. The builds were in the
~juju-package
We captured a snippet of the private build log and we can see the issue
is the same as the report. The first call to access bin/juju fails
because it is not there, it is in $GOPATH/bin/linux__ppc64le. VIvid's
gccgo-go thinks it is cross-compiling.
mkdir -p /build/buildd/juju-core-1.21.2/bin/linux_
12 matches
Mail list logo
