Add new Linux signing keys to packages.

Add new Linux signing keys to packages.

BUG=603808
R=thestig@chromium.org, sburford@google.com

Committed: https://chromium.googlesource.com/chromium/src/+/d7368111613da050a22597f70c1314453a093174

[Lei Zhang, 2016-04-18 19:14:48]

lgtm

[Michael Moss, 2016-04-18 21:55:00]

The CQ bit was checked by mmoss@chromium.org

[commit-bot: I haz the power, 2016-04-18 21:56:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1897933002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1897933002/1

[Michael Moss, 2016-04-18 21:56:55]

FYI, to test, I did a local "official" build and installed the the resulting deb
package, and verified that I see both keys with apt-key, which I didn't before.

[chromium-reviews, 2016-04-18 23:22:11]

Hi,

https://codereview.chromium.org/1897933002/diff/1/chrome/installer/linux/comm...
Lines 13-15 will prevent the new key from installing if you already have
the old key, right?

On Tue, Apr 19, 2016 at 7:56 AM, <mmoss@chromium.org> wrote:

> FYI, to test, I did a local "official" build and installed the the
> resulting deb
> package, and verified that I see both keys with apt-key, which I didn't
> before.
>
> https://codereview.chromium.org/1897933002/
>



-- 
Sean Burford <sburford@google.com>
lg​​t᠎m, a᠎p​pro​v᠎al.

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[commit-bot: I haz the power, 2016-04-19 00:01:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-19 00:01:02]

Try jobs failed on following builders:
  android_clang_dbg_recipe on tryserver.chromium.android (JOB_TIMED_OUT,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)

[Michael Moss, 2016-04-19 03:27:11]

On 2016/04/18 23:22:11, chromium-reviews wrote:
> Hi,
> 
>
https://codereview.chromium.org/1897933002/diff/1/chrome/installer/linux/comm...
> Lines 13-15 will prevent the new key from installing if you already have
> the old key, right?

Yeah, though I don't actually know the command-line to check for the new key,
nor have a rpm distro handy to test with. thestig, would you happen to know? In
the meantime, it won't hurt to get the new key in there, and then fix that check
in a follow-on, so I'm going to go ahead and commit.

[commit-bot: I haz the power, 2016-04-19 03:31:22]

Description was changed from

==========
Add new Linux signing keys to packages.

BUG=603808
R=sburford@google.com, thestig@chromium.org
==========

to

==========
Add new Linux signing keys to packages.

BUG=603808
R=thestig@chromium.org, sburford@google.com

Committed: https://crrev.com/d7368111613da050a22597f70c1314453a093174
Cr-Commit-Position: refs/heads/master@{#388124}
==========

[commit-bot: I haz the power, 2016-04-19 03:31:23]

Patchset 1 (id:??) landed as
https://crrev.com/d7368111613da050a22597f70c1314453a093174
Cr-Commit-Position: refs/heads/master@{#388124}

[Michael Moss, 2016-04-19 03:32:05]

Description was changed from

==========
Add new Linux signing keys to packages.

BUG=603808
R=thestig@chromium.org, sburford@google.com

Committed: https://crrev.com/d7368111613da050a22597f70c1314453a093174
Cr-Commit-Position: refs/heads/master@{#388124}
==========

to

==========
Add new Linux signing keys to packages.

BUG=603808
R=thestig@chromium.org, sburford@google.com

Committed:
https://chromium.googlesource.com/chromium/src/+/d7368111613da050a22597f70c13...
==========

[Michael Moss, 2016-04-19 03:32:06]

Committed patchset #1 (id:1) manually as
d7368111613da050a22597f70c1314453a093174 (presubmit successful).