[roll] Roll fuchsia [pkg-cache] Use caching package server to resolve subpackages

The superpackage should be in the cache because component manager
should hold on to the client connection (to protect the subpackage
from GC) from the time that the superpackage is resolved through
when it attempts to resolve the subpackage.

Original-Bug: 307977824
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/991414
Original-Revision: f47033313903ff5c72a9bcc3a854a90afeba2299
GitOrigin-RevId: 5de54cf1f453eb888164e025dc60e762cd1da3ce
Change-Id: I8a20beb87369428e15bc9afe5ac266f759a2ecd5
1 file changed
tree: e277334be827d7a88ba9e065e8a0c108e86aadba
  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 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.