[roll] Roll fuchsia Revert "[package-tool] Avoid overwriting TUF repo data inside a product bundle"

This reverts commit cd599313851f3bc10e9f164119d3671e5fc01ca5.

Reason for revert:
Breaks OOT LSC tests. Please run `fx lsc presubmit` before relanding.
https://ci.chromium.org/ui/p/turquoise/builders/smart.try/sdk-google-linux-google3/b8735162923387149153/overview
https://ci.chromium.org/ui/p/fuchsia/builders/try/infra-bazel-rules/b8735158828631412961/overview

Original change's description:
> [package-tool] Avoid overwriting TUF repo data inside a product bundle
>
> This will copy the TUF metadate into a user-provided empty directory
> which serves as the (mutable) TUF metadata store for the blobs in the
> product bundle. This ensures the original TUF metadata in the product
> bundle is not modified when the blobs are served via the repo server.
>
> Original-Bug: b/335008631
> Change-Id: Ib90e5a8a14d7bb14aadf192c3a8c790a367bb0af
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1128015
> Commit-Queue: Thomas Zander <thomasalpinus@google.com>
> Reviewed-by: Ben Keller <galbanum@google.com>

Original-Bug: b/335008631
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1130052
Original-Revision: 366161b2ecb23f13cedc0a562f174934e1f11ccc
GitOrigin-RevId: 28921e20d95621718aa498ea5e5cbf5bea09552c
Change-Id: I397e7640f79f81b723f7efeab2ad8bd34ecb9aea
1 file changed
tree: 17830d12b0aad07044075bc7a190f93c997a92bf
  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.