[roll] Roll fuchsia [python] Start from clean temporary directory when bundling PYZ.

* Reusing dirty (from prev builds) temp directories can lead to non-determinism in local builds. Notably write-protected data resources may be left-over and cause build failures.

Test: Confirmed locally that left-over write-protected resources do not prevent subsequent builds from succeeding.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1139755
Original-Revision: 92e8c4f3d6f07707f33fa911186987357b780043
GitOrigin-RevId: 6544f6610ebaf9ad7bf920a6bb836fef388b6ce4
Change-Id: Iaa01b6487d2b334172fd46fd9476a38bddb02a02
1 file changed
tree: 772ef8f612c6c05469d1c3bd3b2b358876fd4b7e
  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.