Add new maintainer key and force repo self-update on sync.

Add new maintainer key and force repo self-update on sync.

This is necesary to force an existing repo working directory to check
out a new version of the repo tool which has been signed with a new
key.

R=cmp@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=217347

[cmp, 2013-08-12 20:48:37]

lgtm

Can you have 2-3 ChromeOS devs apply this by-hand locally and verify all works
well with it applied?  (That may not even work.)

[szager1, 2013-08-12 22:28:01]

On 2013/08/12 20:48:37, cmp wrote:
> lgtm
> 
> Can you have 2-3 ChromeOS devs apply this by-hand locally and verify all works
> well with it applied?  (That may not even work.)

It's pretty difficult to test this change.  It involves:

- Me publishing somewhere a copy of repo.git with this change landed on the
stable branch, and a new PGP-signed tag pointing to the new commit.
- Dev updates depot_tools/repo with the patch, and in their repo working dir,
changes remote.origin.url in /.repo/repo/.git/config to point to my test
version.
- Dev deletes /.repo/repo/.git/FETCH_HEAD, for force repo to auto-update.
- Dev runs 'repo sync'

I have done all of this on my local system (because I was able to create a
mirror repo.git with the signed tag on localhost), but setting it up for testing
on other machines will be difficult.

[cmp, 2013-08-12 22:29:48]

A reasonable approach would be to prep 2-3 ChromeOS devs to help test once you
land it, land the change, then stand-by with a firehose to revert it if it
catches fire.  Then verify with those 2-3 ChromeOS devs that this works.  If it
doesn't work, revert, and verify the revert is working correctly.

[szager1, 2013-08-13 20:44:05]

On 2013/08/12 22:29:48, cmp wrote:
> A reasonable approach would be to prep 2-3 ChromeOS devs to help test once you
> land it, land the change, then stand-by with a firehose to revert it if it
> catches fire.  Then verify with those 2-3 ChromeOS devs that this works.  If
it
> doesn't work, revert, and verify the revert is working correctly.

David and Vadim have verified.  Note that once the change lands, it will take up
to 24 hours for it to take effect on developer machines.

[cmp, 2013-08-13 20:53:17]

lgtm

[szager1, 2013-08-13 21:37:54]

Committed patchset #3 manually as r217347.