Marking this invalid. I believe I just read the documentation wrong.
Sorry for the confusion, no MIR of this new binary package should be
needed.
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Invalid
--
[MIR] cloud-init (grub-legacy-ec2)
https://bugs.launchpad.net/bugs/6050
So, it appears that I dont need a main inclusion report for this after
all. I had mis-read https://wiki.ubuntu.com/MainInclusionProcess to
believe that i did.
--
[MIR] cloud-init (grub-legacy-ec2)
https://bugs.launchpad.net/bugs/605013
You received this bug notification because you are a member
cloud-init the binary package is already in main. The "complicated" bit of
this source package is in the binary cloud-init package.
This main inclusion request is for "grub-legacy-ec2", which is a binary package
put here for lack of any better place to put it.
The code in grub-legacy-ec2 is cop
Scratch that. Most of those requirements deal with ferreting out
details about upstreams (true-upstream and Debian), which don't really
apply here.
The package is relatively complicated, but seems necessarily so since it
is a wedge into early boot and takes over from grub2. And it is needed
and
Scott, can you please provide the info from
https://wiki.ubuntu.com/UbuntuMainInclusionRequirements?
I'll look at it a bit now, but that legwork would help.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: cloud-init (Ubuntu)
Assignee: Michael Terry (mterry
moving to mterry who loves the cloud.
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
[MIR] cloud-init (grub-legacy-ec2)
https://bugs.launchpad.net/bugs/605013
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Summary changed:
- [MIR] cloud-init (legacy-grub-ec2)
+ [MIR] cloud-init (grub-legacy-ec2)
** Description changed:
Binary package hint: cloud-init
- the legacy-grub-ec2 package is part of 'cloud-init'. It was developed
+ the grub-legacy-ec2 package is part of 'cloud-init'. It was develop
