ppc64el: cannot find package "encoding"

[Curtis Hovey]

[Impact]
There is a packaging bug that means that go packages that import the little used standard library package "encoding" fail to compile.

[Test case]
$ cat enctest.go
package main

import (_ "encoding")

func main() {}
$ go run enctest.go
enctest.go:3:9: cannot find package "encoding" in any of:
 /usr/src/pkg/encoding (from $GOROOT)
 ($GOPATH not set)

[Regression potential]
None that I can see.

Original description follows:

Bug 1440940 has reappeared in ppc64el unit tests and now affects building binaries.
    http://reports.vapour.ws/releases/3044/job/run-unit-tests-trusty-ppc64el/attempt/3787
    http://reports.vapour.ws/releases/3044/job/build-binary-trusty-ppc64el/attempt/323

make build
skipping godeps
go build github.com/juju/juju/...
../httprequest/marshal.go:8:2: cannot find package "encoding" in any of:
 /usr/src/pkg/encoding (from $GOROOT)
 /home/ubuntu/juju-core_1.26-alpha1/src/encoding (from $GOPATH)
make: *** [build] Error 1

Unlike the first occurrence, we now use a machine that only gets trusty-updates and has only ever been used to run "make test" on the unpacked tree. Binaries are built in pristine containers provisioned to match the Lp build conditions.

[Curtis Hovey (sinzui)]

The only change from the last success as
    https://github.com/juju/juju/commit/d5fe7eb455740f0bc29f69971eacf4666ef1d3e0

[Michael Hudson-Doyle (mwhudson)]

This is really a packaging bug that I thought I'd fixed a seriously long time ago, but apparently the fix never got into trusty. Let's do it right (I guess the juju commit can be reverted in the mean time to fix that task)

[Steve Langasek (vorlon)]

Invalid for trunk because gccgo-go is only present in trusty. for wily this is fixed in the gcc-5 package.

[Martin Packman (gz)]

This has been temporarily addressed on master by backing out the change responsible:

<https://github.com/juju/juju/pull/3262>

[Chris J Arges (arges)]

Hello Curtis, or anyone else affected,

Accepted gccgo-go into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gccgo-go/1.2.1-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Michael Hudson-Doyle (mwhudson)]

I have verified that the bug is fixed in trusty-proposed.

(trusty-ppc64el)mwh@kelsey01:~$ dpkg -l gccgo-go
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================-====================-====================================================================
ii gccgo-go 1.2.1-0ubuntu1.1 ppc64el Go tool for use with gccgo

[Launchpad Janitor (janitor)]

This bug was fixed in the package gccgo-go - 1.2.1-0ubuntu1.1

---------------
gccgo-go (1.2.1-0ubuntu1.1) trusty; urgency=medium

  * Add "encoding" to the list of standard library packages (LP: #1494441)

 -- Michael Hudson-Doyle <email address hidden> Fri, 11 Sep 2015 08:06:33 +1200

[Chris J Arges (arges)]

The verification of the Stable Release Update for gccgo-go has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.