During a June 25 configuration change, there was a bad push to several chromium repos:
deps/cygwin, deps/gpu/software_rendering_list, deps/hunspell, deps/hunspell_dictionaries,
reference_builds/chrome_win, src/crypto, third_party/gles2_book, tools/build/third_party/simplejson
We had to manually clean up, which involved force pushes to the repos above.
Summary of problem:
which has a different uuid than
src.chromium.org/svn. git-svn didn't recognize existing commits, but happily reimported everything
on a fresh commit line, created a merge commit and then pushed another fresh copy on top of everything,
with a different uuid (the 0039 one). This evaded the safety checks in place at the time.
deps2git picks the most recent commit with a matching revision line, and it appears to have picked up the bad sha and broke .DEPS.git between 10pm PST on June 25 and 6am on June 26.
For the record, here was the two shas (for the same svn revision):
hunspell.git$ git rev-list 37403978cd | wc -l
45 [good]
hunspell.git$ git rev-list b7195d9c26 | wc -l
152 [bad]