[roll] Roll fuchsia [fuchsia-repo] Improve publish conflict error

This changes fuchsia_repo::RepoBuilder to track the package manifest
paths. This allows us to report better error messages when we have
a conflict between two package manifests.

In addition, when we detect a conflict, we compute a difference between
the two manifests to report which files are different. This hopefully
better guides users to figure out why a build system might be trying
to publish two different versions of a package.

Finally it moves dependency tracking into RepoBuilder to simplify
tracking.

Original-Fixed: 115432

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/760667
Original-Revision: 284d01d798d5722587e4ec7d64c1c70a2ea47826
GitOrigin-RevId: a796958c02e676e7b0235d6497263114e0c3537b
Change-Id: I2e1871c0eee9f49a5ebdaf6787a658a850325e0f
1 file changed
tree: 4d26876d0a088bd8ee602d8620d9a8b6d3b6d59f
  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.