@Stephane - thank you for the 0.20-0ubuntu4 upload. Also, as Michael said, security team approval alone is not enough for approval and so regardless of the misunderstanding surrounding the embedded code copes, the other issues to be done before acceptance.
Regarding the embedded copies, I appreciate that you have resources dedicated to fixing this. I guess I am just surprised both that it will take so long for using at least the copies in the archive (the juju team seemed to not have too terribly much trouble with it). Also, I communicated the need for splitting this out on IRC at least a month ago and in the juju/golang/lxd mir interlock weekly hangout. Unfortunately, miscommunication and/or misunderstanding on both sides seems to have gotten us into the position we are in now (it was never communicated directly to me and I missed the 'current plan' in comment #9, I guess due to the LP snafu with that comment). At this point, there is so little time for the LXD team to make the changes and they've already resourced the work for the embedded copies for 16.04. I've created bug #1507156 to track breaking out the embedded code copies. Since 0.20-0ubuntu4 addresses the other packaging concerns, marking Fix Committed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481507 Title: [MIR] lxd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1481507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
