New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 917352 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
ed...@chromium.org
mnissler@chromium.org
vapier@chromium.org
█ djkurtz@chromium.org
ejcaruso@chromium.org
hashimoto@chromium.org
hidehiko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue 733477


Sign in to add a comment

libchrome crypto/ is older than other directories.

Project Member Reported by hidehiko@chromium.org, Dec 21 
aosp/external/libchrome/crypto directory is out of sync from upstream (Android r456626), unlike other directories.

It looks like it is probably because boringssl is not supported: crbug.com/733477.
Eric, could you share what happened when you made the update?

Comment 1 by ed...@chromium.org, Dec 21

Cc: ed...@chromium.org

Comment 2 by ejcaruso@chromium.org, Jan 8 

Do you mean it's out of sync with the rest of the r456626 libchrome? I'm not sure why that should be the case. The r456626 libchrome should be the same one as on Android...

Comment 3 by hidehiko@chromium.org, Jan 17 (5 days ago) 

Re #8: Actually I could find so huge diff from upstream...
Currently, libchrome base version is r462023, but I left the crypto/ directory so you can still find the diff. Eric, could you take a look?

Comment 4 by osh...@chromium.org, Jan 18 (4 days ago)

Components: Infra>ChromeOS>Build

Comment 5 by vapier@google.com, Jan 18 (4 days ago)

Cc: vapier@chromium.org
Components: -Infra>ChromeOS>Build OS>Packages
►

Sign in to add a comment