[roll] Roll fuchsia [pbm] Add --force-repo flag to product-bundle get

The attached bug requests a way for users to overwrite a repository when
downloading a product bundle, as was the behavior before
https://fuchsia-review.git.corp.google.com/c/fuchsia/+/735685.

This CL adds a new flag, --force-repo, which allows the product-bundle
get command to proceed even if a repository with the same name already
exists. The existing repo registry entry will be overwritten with the
path for the bundle being downloaded. Note that even if the bundle is
already in the local cache, the repo will be overwritten, but the bundle
will not be re-downloaded unless the user also includes the --force
flag.

Original-Bug: 112892
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/757769
Original-Revision: 054600ce357023ee62fd669ec3facda1836c1ad3
GitOrigin-RevId: 0a37e52328b24c36549f80295b6017b891db39db
Change-Id: I39a2d74984231718f161675527e968c10f166be6
1 file changed
tree: e7bc1bd10424da45337009f742e65de5bca6f9cd
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.