...
> On Mon, Mar 31, 2014 at 01:30:45PM -0000, Mark Ramm wrote: > > I think a key point here is that the juju package does not generally > > install or pull down binaries from anywhere to your machine. It does > > instruct the cloud installation of a server to use a specific ubuntu > > image from simplestreams and a specific jujud binary (also from > > simplestreams) on the remote host. > > I agree with Martin; the fact that these binaries do not originate in the > Ubuntu archive, and are not subjected to the normal standards and > procedures > for the Ubuntu archive, is very concerning. > > Using simplestreams as the distribution method or not makes no difference > to > me - but the actual software that's being distributed should be built using > Ubuntu best practices. > > We've been turning a blind eye to this so long as the package has been in > universe. I don't think we want juju-core to go into main until jujud is > also > brought "in house" in Ubuntu. > > > > I'm pretty sure the jujud binaries are being built by the archive. At least, ISTR that we had to wait for some things to get built into Trusty before we could publish them. It may be that we switched to a PPA to increase turn around time, but that isn't as relevant for what we would publish as a stable release. John =:-> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
