Comment 134 for bug 408903

> right, we still need to change other components, I've tagged the verification-done because the only piece up for verification at the moment is libx11 and you verified that one, getting it in updates would put us one step closer from fixing the issue right?

This is exactly right.

>> Additionally, this requires a revert of xkeyboard-config that we have in -proposed. I'm not sure how to work that because this is my first verification-failed bug, but I assume I can just revert it.
>
> Do you need revert or extra changes? in any case the update is in precise-updates so you can't verification-failed it anymore (that's just used to get things dropped from proposed/not copied to updates), you need another upload on top of the current version

This is in relation to bug #937822. Since that bug is verification-failed, we pulled the update of xkeyboard-config from the -proposed archive. But it's still living out in the launchpad bzr code archive. So specifically, my question is whether I should branch from the -updates lp archive or the -proposed lp archive (and pull the patch, as I have have done). I've ran into this situation before in bug 1011073 but cyphermox solved it for me. Sorry if this is too much minutia.

https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/xkeyboard-config/precise-updates
https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/xkeyboard-config/precise-proposed