Comment 5 for bug 1829823

Hi Matthew,
I have discussed this with Corey on Friday.

My general preferred solution would still be to not do a Xenial upload at all. But after the talk with Corey he explained that for T-M there isn't really a good other way.
Just as you I have double checked and agree that this should not have any effect on Xenial, but there are two things to consider:
- people might still have tweaked their xenial to run with upstart (but for those it will be a fix)
- for the majority this will be a download of ~25MB for nor real change which is a waste of
  resources that we should not do.

Corey and I have agreed to handle it the following way:
- I'm willing to help you to push this to Xenial-Proposed
  - ME: re-Review the current solution
  - ME: sponsor it to Xenial unapprove
- YOU: If the SRU team objects you should do the discussion/convincing
- We will LEAVE it hanging in proposed and intentionally NOT release to Xenial it as-is
  - that means only testers of proposed will pick it up
  - When there is a libvirt fix later any normal SRU or security push will be based
    on what is in proposed
  - Only then it will be really available to Xenial users
- We didn't get to the point if the Cloud-Archive could sync from -proposed in this case
  - for now I expect the answer is no, which means you have no ETA when this will
    really be released

@Mathew - please confirm that this approach will work for you, then I'll do my steps
@Corey - please confirm here that this approach will work for you, also add if UCA-T-M could sync from proposed once it is verified there.