© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
> golang 1.5 is now built on arm64 and ppc64el, however juju-core
> is built using gccgo. Is there a reason for it?
The reason for this is that the package is being backported directly to trusty, under the juju Stable Release Exception for SRUs. Since there is not a compatible version of golang in trusty, the package is currently built for all releases using gccgo.
I believe we will want to revisit this in the future, but I think this should be separable from the MIR question, do you agree?
> - the packaging is a copy of the mongodb package, however it looks
> like the packaging itself isn't merged / updated where needed.
> This problem is shared with the mongodb package in Ubuntu.
The mongodb package is in universe and unsupported. The juju-mongodb package exists to support juju-core and provides a subset of functionality specifically validated for use with juju. I don't think this should be a blocker for the MIR?
> - google-perftools is available on all archs. Is there a need to
> disable that for some architectures?
It's not available on arm64 in trusty, so probably should not be enabled on that architecture. It probably should be enabled on ppc64el and powerpc.
> - the package should be built for the upcoming s390x architecture as
> well.
Yes, it should; the architecture list in debian/control should just be dropped so that the package builds automatically for all architectures.
These last two points are good packaging feedback, but they don't seem to be critical for the package's current supportability in main (especially considering s390x is not in wily) (https:/