Roll libyuv chromium deps to same as webrtc jun8

Roll libyuv chromium deps to same as webrtc jun8

contains the following changes in chromium:
https://chromium.googlesource.com/chromium/src/+log/2d938c84..7fa6701b

R=kjellander@chromium.org
TBR=kjellander@chromium.org
BUG=libyuv:626
Committed: https://chromium.googlesource.com/libyuv/libyuv/+/e75fcb03e5dc06a517f819ee4732d4d7727bf8ab

[kjellander_chromium, 2016-08-01 20:21:42]

I suggest rolling to a newer revision instead. There seems to be something
missing with Android manifests as well (I haven't spent time looking into it
though)

https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp
File libyuv.gyp (right):

https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp#newcode37
libyuv.gyp:37: 'linux_use_bundled_gold%': 0,
You can roll to a newer revision instead, as this is now cleaned up (see
bugs.webrtc.org/5977).

[fbarchard1, 2016-08-02 19:35:28]

On 2016/08/01 20:21:42, kjellander_chromium wrote:
> I suggest rolling to a newer revision instead. There seems to be something
> missing with Android manifests as well (I haven't spent time looking into it
> though)
> 
> https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp
> File libyuv.gyp (right):
> 
> https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp#newcode37
> libyuv.gyp:37: 'linux_use_bundled_gold%': 0,
> You can roll to a newer revision instead, as this is now cleaned up (see
> bugs.webrtc.org/5977).

The method I used was look thru webrtc DEPS rolls for ones requiring other
changes, and roll to those.
In this case .gn and libyuv.gyp.  I can try for the next one.  But should I go
ahead with the .gn and libyuv.gyp changes, leaving out the DEPS?

[kjellander_chromium, 2016-08-02 20:53:40]

On 2016/08/02 19:35:28, fbarchard1 wrote:
> On 2016/08/01 20:21:42, kjellander_chromium wrote:
> > I suggest rolling to a newer revision instead. There seems to be something
> > missing with Android manifests as well (I haven't spent time looking into it
> > though)
> > 
> > https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp
> > File libyuv.gyp (right):
> > 
> > https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp#newcode37
> > libyuv.gyp:37: 'linux_use_bundled_gold%': 0,
> > You can roll to a newer revision instead, as this is now cleaned up (see
> > bugs.webrtc.org/5977).
> 
> The method I used was look thru webrtc DEPS rolls for ones requiring other
> changes, and roll to those.
> In this case .gn and libyuv.gyp.  I can try for the next one.  But should I go
> ahead with the .gn and libyuv.gyp changes, leaving out the DEPS?

I see. You can pick whatever one you want (and I understand if you want to do it
step by step). I mostly wanted you to know that the MIPS workaround was later
removed
(https://chromium.googlesource.com/external/webrtc/+/4c7f8aec411d7c51ab3ea84d6...)
so if you roll to the version at that point in time you won't need it.

[fbarchard1, 2016-08-02 21:26:19]

https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp
File libyuv.gyp (right):

https://codereview.chromium.org/2183633002/diff/60001/libyuv.gyp#newcode37
libyuv.gyp:37: 'linux_use_bundled_gold%': 0,
On 2016/08/01 20:21:42, kjellander_chromium wrote:
> You can roll to a newer revision instead, as this is now cleaned up (see
> bugs.webrtc.org/5977).

Acknowledged.

[fbarchard1, 2016-08-02 21:42:35]

Description was changed from

==========
Roll libyuv chromium deps to same as webrtc jun8

contains the following changes in chromium:
https://chromium.googlesource.com/chromium/src/+log/2d938c84..7fa6701b

R=kjellander@chromium.org
TBR=kjellander@chromium.org
BUG=libyuv:626
==========

to

==========
Roll libyuv chromium deps to same as webrtc jun8

contains the following changes in chromium:
https://chromium.googlesource.com/chromium/src/+log/2d938c84..7fa6701b

R=kjellander@chromium.org
TBR=kjellander@chromium.org
BUG=libyuv:626

Committed:
https://chromium.googlesource.com/libyuv/libyuv/+/e75fcb03e5dc06a517f819ee473...
==========

[fbarchard1, 2016-08-02 21:42:37]

Committed patchset #5 (id:80001) manually as
e75fcb03e5dc06a517f819ee4732d4d7727bf8ab (presubmit successful).