[roll] Roll fuchsia [package-tool] Don't publish from the TUF repo in a product bundle

Publishing packages directly from a TUF repo in a product bundle may
result in it being changed, e.g. due to metadata refreshing or key
management when publishing. The package-tool will now refuse such
attempts, maintaining the immutability invariant of product bundles.

Original-Bug: b/335008631
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1127935
Original-Revision: 3b33243a05325813a2935466cd1e3b69d350d121
GitOrigin-RevId: e6f27bae1a086aea785cdf90a7115ed0475774c8
Change-Id: I8c63a01b4a8d1b42a65bf634a3850f3485c9f702
1 file changed
tree: 7672c4cbb26298818f610d5ddbaea954d04a23d6
  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.