Fix the Copresence permission.

Fix the Copresence permission.

The initializer for the Copresence permission is malformed. It specifies the
message id instead of the flag.

R=kalman@chromium.org
BUG=408843
Committed to pending queue: https://chromium.googlesource.com/chromium/src/+/c2a41e8

Committed: https://crrev.com/5df416cab1a378864933a89cd9f7f81b91788633
Cr-Commit-Position: refs/heads/master@{#292952}

[not at google - send to devlin, 2014-08-28 23:25:20]

lgtm

[rkc, 2014-08-28 23:33:28]

Committed patchset #1 (id:1) to pending queue manually as c2a41e8 (presubmit
successful).

[Alpha Left Google, 2014-08-29 01:10:23]

A revert of this CL (patchset #1) has been created in
https://codereview.chromium.org/520493002/ by hclam@chromium.org.

The reason for reverting is: This change causes a test failure:

http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%2...

Error:

[ RUN      ] PermissionsTest.PermissionMessages
../../chrome/common/extensions/permissions/permission_set_unittest.cc:781:
Failure
Value of: permission_info->message_id()
Actual: 65
Expected: PermissionMessage::kNone
Which is: 1
unexpected message_id for copresence

Looks like this change is the cause..

[not at google - send to devlin, 2014-08-29 01:13:05]

Rkc please dont dcommit especially without running a try run.

[benwells, 2014-08-29 02:49:43]

On 2014/08/29 01:13:05, kalman wrote:
> Rkc please dont dcommit especially without running a try run.

+1 CQ is your friend. I just wasted time tracking down what had happened, as did
kalman@ probably.

Only dcommit when you absolutely need to, and then make sure you won't break
stuff.

[rkc, 2014-09-02 15:28:17]

I apologize. I usually don't land without the CQ but this 'seemed' like a
harmless change. I was trying to make sure this landed in time for the canary to
pick this up (since it breaks all our users).

Live and learn.

[rkc, 2014-09-02 15:52:33]

The CQ bit was checked by rkc@chromium.org

[commit-bot: I haz the power, 2014-09-02 15:59:45]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rkc@chromium.org/523433002/20001

[commit-bot: I haz the power, 2014-09-02 17:01:50]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[commit-bot: I haz the power, 2014-09-02 17:32:12]

Committed patchset #2 (id:20001) as b780a3047c20759afb14159fa4ac0ffe0d5f4cf6

[commit-bot: I haz the power, 2014-09-10 03:03:24]

Patchset 2 (id:??) landed as
https://crrev.com/99ae5386b85f81eb7ae3d811c240535b721017b8
Cr-Commit-Position: refs/heads/master@{#292495}

[commit-bot: I haz the power, 2014-09-10 03:19:16]

Patchset 2 (id:??) landed as
https://crrev.com/5df416cab1a378864933a89cd9f7f81b91788633
Cr-Commit-Position: refs/heads/master@{#292952}