memcached binaries seeded in Ubuntu.Maverick supported-misc-servers seed

[Matthias Klose]

please either remove the seed, or prepare a MIR

libmemcached: libhashkit0 libmemcached-dbg libmemcached-dev libmemcached-tools libmemcached5 libmemcachedprotocol0 libmemcachedutil0
   [Reverse-Depends: Rescued from libmemcached, Ubuntu.Maverick supported-misc-servers seed, libmemcached-dev]

[Matthias Klose (doko)]

same for memcached

[Thierry Carrez (ttx)]

Clint, I think you spearheaded that effort, could you please have a look ?

[Clint Byrum (clint-fewbar)]

Hi guys, we probably need to have a better process for seed management, as these both had MIR's approved:

memcached MIR, approved:

https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/586634

libmemcached MIR, approved:

https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/586638

Apologies that this wasn't clear by the commit logs and comments.

[Clint Byrum (clint-fewbar)]

To be even more clear, all of the mentioned packages come from the libmemcached source package, and so by my understanding of the MIR process, should have been included in the MIR's approval.

[Matthias Klose (doko)]

well, the MIR's were closed before the promotion was done.
you should not set the status of a MIR to `released' without doing the promotion.

memcached is a separate source afaics

[Matthias Klose (doko)]

both source packages now promoted

[Clint Byrum (clint-fewbar)]

Ahh, that explains the confusion.

Matthias, is there any way you could clarify the bug management in the Main inclusion process wiki page?

https://wiki.ubuntu.com/MainInclusionProcess

Its very unclear who does the promotion and how the bug should be handled after a MIR team member has approved it.