If the move to golang-yaml.v2 is low risk and can be done, then I'll include that package for MIR and drop golang-goyaml and golang-gocheck; however if that's not the case, then I think we should *not* use golang- goyaml-dev and fallback to the embedded code copy in juju-core for this cycle; juju should be able to switch in a newer release at a future date.
-- 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, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
