** 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 stable and devel ppas - https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages - https://launchpad.net/~juju-packaging/+archive/ubuntu/devel/+packages?field.name_filter=juju-core&field.status_filter=superseded&field.series_filter=vivid + https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages + https://launchpad.net/~juju-packaging/+archive/ubuntu/devel/+packages?field.name_filter=juju-core&field.status_filter=superseded&field.series_filter=vivid Using the source packages at - https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages?field.name_filter=juju-core&field.status_filter=published&field.series_filter=vivid + https://launchpad.net/~juju-packaging/+archive/ubuntu/stable/+packages?field.name_filter=juju-core&field.status_filter=published&field.series_filter=vivid - We trued to build it in a vivid lxc on a ppc64el machine (stilson-07). - the build failed at the first call to use the built juju. The first call - is to generate the man pages using "juju version" and "juju help - commands" debian/rules sets the GOPATH and then adds the GOPATH/bin to - PATH. The build binaries were placed in $GOPATH/bin/linux__ppc64le, not + When we build in a vivid ppc64el container on (stilson-07). the build + failed at the first call to use the built juju. The first call is to + generate the man pages using "juju version" and "juju help commands" + debian/rules sets the GOPATH and then adds the GOPATH/bin to PATH. The + build binaries were placed in $GOPATH/bin/linux__ppc64le, not $GOPATH/bin! The "dpkg --print-architecture" for both the host and the container are "ppc64el". The host'ss "go env" shows GOARCH="ppc64" The container's "go env" shows GOARCH="ppc64le" I can contrive a successful build doing this - GOARCH=ppc64 dpkg-buildpackage -us -uc + GOARCH=ppc64 dpkg-buildpackage -us -uc So we could change debian/rules, but we first need to understand if GOARCH for vivid ppc64el is sane.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417771 Title: juju-core vivid ppc64el fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1417771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
