commit | 3100d3e733e9c6151220a7e24e5d87420814dee2 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Tue Dec 18 01:33:49 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Dec 18 01:33:49 2018 |
tree | efa992328111568a1f6f1b0adb00735ba39b1d0a | |
parent | af9eb67beb77706454e440b6424a9aceb03b3c69 [diff] |
[cipd] Deal with the situation when files change case during upgrade. Imagine when upgrading a package file a/b/c changes to a/b/C. Here's what happened before this CL on case-insensitive file systems: * a/b/c is installed (since it is considered new). In reality it either rewrites body of a/b/C, or replaces a/b/C completely (depending on file system and OS). * a/b/C is removed (since it is considered old). In reality it deletes what was supposed to be a/b/c. * As a result we end up with nothing. This case is now handled correctly. R=iannucci@chromium.org, tandrii@chromium.org BUG=915278 Change-Id: I9c46e1d4499f74fc8d50b40c421343f9453d7e91 Reviewed-on: https://chromium-review.googlesource.com/c/1381273 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.