[roll] Roll fuchsia [system-update-checker] Use the new image package manifest

The system-update-checker compares the active system to the system
described by the update package to see if a new update is available.

The update package format was recently migrated from storing images
(e.g. zbi, vbmeta) directly to storing a manifest that lists their
hashes and URLs from which they can be resolved. The
system-update-checker was not migrated, so it was still looking for
the images in the update package, which broke the check that
determined if the zbi or vbmeta were out-of-date, so the
system-update-checker would erroneously think the system was
up-to-date if only the zbi or vbmeta had changed. This would commonly
surface as kernel devs making a zbi-only change but then `fx ota`
would not update their device.

With this change, the system-update-checker uses the new image
manifest and so should again correctly trigger an update on zbi-only
changes.

Original-Fixed: b/317524358
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/966533
Original-Revision: 2a448fe54e06ba9f444824063429a5680dce0097
GitOrigin-RevId: aba5a4bd12530edb3ca06542e627b4f2657ad477
Change-Id: I1699833e1656ebc37a2dc4b0b7fcbd270cd1c7a3
1 file changed
tree: e529d0405c926d70a833fcc18881601c98c39bee
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.