[roll] Roll fuchsia Reland "[assembly] Fix dep cycle for non-bazel-only builds"

Reason: not the culprit

In some gn assemblies we encounter a dep cycle due to the
fshost-validator:

fshost-validator -> legacy aib -> bazel assembly -> licenses
-> gn assembly -> fshost-validator

Remove the very first dep in this cycle for non-bazel-only builds to
address this.

Original-Bug: b/287558873
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/901201
Original-Revision: 4ffb3d79d747f0ef4319aa6f3d1124f35a1e11d3
GitOrigin-RevId: a6bfe5d5240ab678236418ddf3d6075b7207f000
Change-Id: I780b9cf84c46ebd26c296db33bde24f347eac2e4
1 file changed
tree: d998407d86bd787baa3f82f169b5f964989ae311
  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.