[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang

[Adam Conrad]

"Upstream released jujud binaries are/will be distributed officially via
simplestreams using a documented build process (details TBC)."

I've said it before, and I'll reiterate, this is fundamentally broken.
A package in the archive shouldn't have have of its binaries not in the
archive.  This *must* be a solvable problem.

If the problem is that the package can't be BUILT in the archive, then
this isn't remotely suitable for main.  Otherwise, I don't see what the
blocker is at all.  Just package up those binaries, and done.

What fundamental flaw in the process is being hidden by shipping
binaries outside the archive?  Does the build system pull random deps
from the internet, does it pull prebuilt objects from the internet, sans
source code (again, absolutely unacceptable for main).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in 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