force update crostini |
|||||
Issue descriptionas I have learned from adlr, crostini teams have been constantly making changes to the platform and incompatibility between platform and termina component happen many times. We might have to uprev ENV more frequently than now (no uprev at all). But on ToT (canary) uprevving ENV on each platform release is too much but incompatible change does happen between canary releases (on same milestone). Currently, component updater does not automatically update a compatible component (with no EVN uprev) and instead component updater service automatically update components in the background but this behavior is not consistent on user's device. Current way to force an update is to go to chrome://components and click 'Check for update' button. We might need an option 'force_update' in component Load API so chrome crostini_manager can leverage to push the 'update' button on behalf of users.
,
Jun 8 2018
,
Jul 2
,
Jul 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/845e1e053ec358fdd971aec1e52f9e59e4a88733 commit 845e1e053ec358fdd971aec1e52f9e59e4a88733 Author: Xiaochu Liu <xiaochu@chromium.org> Date: Mon Jul 09 23:16:15 2018 component updater:: allow force update for crostini Component updater does not force an update if an compatible component is installed. We provide an option in the Load API to support forced update check. BUG= chromium:850798 ,chromium:859573 TEST=platform_AddPrinter.epson Change-Id: I1649e0ce641089cd57d4910155fc93e660967df1 Reviewed-on: https://chromium-review.googlesource.com/1119199 Reviewed-by: Sorin Jianu <sorin@chromium.org> Reviewed-by: Nicholas Verne <nverne@chromium.org> Reviewed-by: Toni Barzic <tbarzic@chromium.org> Reviewed-by: Ben Wells <benwells@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> Commit-Queue: Xiaochu Liu <xiaochu@chromium.org> Cr-Commit-Position: refs/heads/master@{#573512} [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/chromeos/crostini/crostini_manager.cc [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/chromeos/dbus/component_updater_service_provider.cc [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/chromeos/printing/printer_configurer.cc [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/component_updater/cros_component_installer_chromeos.cc [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/component_updater/cros_component_installer_chromeos.h [modify] https://crrev.com/845e1e053ec358fdd971aec1e52f9e59e4a88733/chrome/browser/extensions/api/media_perception_private/media_perception_api_delegate_chromeos.cc
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Sep 5
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xiaochu@chromium.org
, Jun 8 2018