[roll] Roll fuchsia [logs] Explicitly depend on LogSink shards

Currently, these CML files depend on the LogSink shard
implicitly through RealmBuilder. These multiple layers
of shard nesting are causing problems with migrating
out-of-tree LogSink users to the diagnostics dictionary,
so implicit dependencies are being migrated to explicit dependencies
in preparation for the removal of the LogSink shard from
RealmBuilder.

Original-Bug: 404543928
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1232024
Owners-Override: James Robinson <jamesr@google.com>
Original-Revision: c77d1e4056815c67f0195e107900ef8f5f6f9008
GitOrigin-RevId: 9d41ee09654b5a5918b8397d4f8d9855b87f2ceb
Change-Id: I076bb5a03ac8515cbb91de379efe6bbac9db65f9
1 file changed
tree: e73af95e43ee968c9a8490d619676a86e39030cc
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.