gclient sync runs successfully not updating local Chromium checkout

[Simon Que]

Hi all,

I ran "gclient sync" but found that it didn't update my src/ repo or any sub-repos (e.g. src/v8). I didn't see any error messages to indicate something went wrong.

The remotes/origin/master branch of src/ was also not updated. However, I do see that src/v8's remotes/origin/master branch was updated to some newer revisions.

See the verbose output log here (Googlers only):

https://drive.google.com/a/google.com/file/d/0BzPK_1nFytaUTXBha09jcFdhYm8/view?usp=sharing

Simon

[Scott Graham]

gclient sync doesn't update src, per

----------------------------------------

[0:00:00] Started.

_____ src at refs/remotes/origin/master

[0:00:00] ________ unmanaged solution; skipping src

[0:00:00] Finished.

You need to do something like git fetch origin && git checkout origin/master && gclient sync.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Simon Que]

Has the workflow changed recently? I remember gclient sync used to be all I needed to run.

[Dirk Pranke]

Not recently, no. This changed a couple years ago.

However, there's a setting in your .gclient file that you can toggle to get the old behavior back: set 'managed': True.

[Simon Que]

That makes sense. I recently got a new workstation after using the same Chromium checkout on my previous workstation for a few years.

[Scott Graham]

Yes, but "unmanaged" has been default for a very long time now, see e.g. https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/n9N5N3JL2_U .