Comment 25 for bug 1481507

Jamie. What you're saying seems at odds with what Seth said:
"Security team ACK for promoting lxd to main."

So I don't believe I've done anything prematurely and have in fact waited for a security team ack, which I got.

We are now past final freeze with this package installed in official images, so putting it back to universe seems pretty impractical.

As for your other points:

1) Should be easy to fix
2) same
3) doesn't really matter and makes backporting to trusty significantly easier as we don't have go 1.5 with the nice meta packages in there yet. We'll change that once we've managed to get 1.5 into trusty-backports so we can keep following the "don't modify the source packaging" rule of backports.
4) our plan (and that's what i communicated to Seth and anyone else who asked) is to switch to using packaged dependencies with the first 16.04 upload. I will definitely NOT do this in 15.10 as there is absolutely no way for us to offer any kind of support on this particular version combination. I expect it will be a multi-month effort to bump some of those packages, distro-patch some of the others, ... to end up with a combination which works for lxd and for everyone else without causing us all different weird issues.

As I believe was communicated to you over IRC. I am on vacation until after 15.10 is out the door. I have a couple of hours at random airports on the way back from Seattle right now and will try to address 1) and 2) during that time.

Given when we got the security feedback (less than a week ago) and the fact that said feedback told us we were good to promote, that's the absolute maximum I'm ready to do for this cycle.