"Your depot_tools checkout is configured to fetch from an obsolete URL Would you like to update it? [y/N]:"

[David Michael]

I ran gclient on Windows today and saw this message:

Your depot_tools checkout is configured to fetch from an obsolete URL Would you like to update it? [y/N]:

I dutifully answered "Y"es, and it broke depot_tools for me... running "gclient sync" gave me:
'GIT_SVN_UPDATE' is not recognized as an internal or external command, operable program or batch file.

I fixed it by cd-ing to my depot_tools directory and running:

git config remote.origin.url "https://chromium.googlesource.com/chromium/tools/depot_tools.git"

It looks like this change might have happened in:
https://codereview.chromium.org/11778024

Is anyone else seeing this?

[Nick Carter]

I'm seeing this too, starting today. I do not use cygwin.

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

[Wez]

I saw the message, said "yes" and checked remote.origin.url in my depot_tools, which seems to be set to the value you've listed.

[Stefan Zager]

I haven't been able to reproduce this.  If anyone else is having the same problem, I'd welcome an opportunity to chromote into your machine and poke it with a stick.

Thanks,

Stefan

[Sigurður Ásgeirsson]

I got this yesterday as well.

--

[Sigurður Ásgeirsson]

On Windows, msys git.

[Sungguk Lim]

Same here

This can be regenerated by extracting tarball, run 'gclient sync --force'

Any information about this?

2013년 1월 9일 수요일 오전 7시 48분 53초 UTC+9, David Michael 님의 말:

[David Michael]

To clarify, it's fine and expected to get this message: 

Your depot_tools checkout is configured to fetch from an obsolete URL Would you like to update it? [y/N]:

If you say "yes", and everything works after that, then you're fine.

But if gclient starts failing with:

'GIT_SVN_UPDATE' is not recognized as an internal or external command, operable program or batch file.

Then you should contact Stefan Zager. If you're in a hurry, you can use the work-around I listed above.

(In case it helps: I use Windows, and I don't use Cygwin).

--

[Kerry Kobashi]

Yes, I'm seeing this too. After running gclient tonight, I stepped away while it was downloading.
Came back to see the attached screen shot.

[Emmanuel Saint-loubert]

Same thing happened to me...

[Stefan Zager]

I've root-caused this, and I'll upload a new depot_tools.zip ASAP.

Thanks,

Stefan

[William Byrne]

>> I've root-caused this, and I'll upload a new depot_tools.zip ASAP.

Any news on this?

[William Byrne]

Got off a build on Win7 64 bit with the following steps:

1. Installed CollabNet SVN 1.6.20 (Win 32-bit) (in addition to my other SVN installs)
2. Opened a regular cmd shell (no vcvars, no elevation)
   
3. cd \path\to\chromium\..  (parent folder of empty chromium directory, or directory to be)
   
4. svn co http://src.chromium.org/svn/trunk/tools/depot_tools
   (this step gave me the depot_tools directory next to my empty chromium directory)
   
5. Opened cmd shell as Administrator to make the symlink in the next step
   
6. mklink'd  .\depot_tools\svn_bin to SVN installed in step #1  (hid/renamed the default svn_bin folder)
   (03/23/2013  06:19 PM    <SYMLINKD>     svn_bin [C:\Program Files (x86)\CollabNet\Subversion Client])
   
7. Returned to my regular cmd shell
8. path=\path\to\depot_tools;%path%   (give priority visibility to the depot tools)
   
9. cd \path\to\chromium

10. gclient config http://src.chromium.org/chrome/trunk/src 

11. gclient sync --revision src@###### --jobs 8 --force  (I used src@187216 - the --revision option can be omitted)

12. gclient sync --revision src@######  (ran a second time to verify download - had a few download errors.)

13. python src\tools\win\toolchain\toolchain.py   (See final output below. Installed tools already on system, but this step
    successfully placed the require tools/libs local to the workspace. Ran this step twice to see what would happen. 2nd run did nothing.)
14. Opened a new regular cmd shell. May not be necessary but wanted to verify for future builds.
15. cd \path\to\chromium
16. path=\path\to\depot_tools;%path%   (give priority visibility to the depot tools)
17. win_toolchain\env.bat
18. gclient runhooks
19. cd src
20. ninja -C out\Debug chrome  (ran to completion without errors with minimal display activity to console. Produced chrome.exe)
    

Steps 3-12 from BranchesAndBuilding # Manual Downloading section
Steps 13-20 from build-instructions-windows # Automatic simplified toolchain setup section

It was a bit of struggle to get this done, but it worked. The important tweak involved setting up SVN 1.6.20 and setting the symlink.

* Final output of step #13 - python src\tools\win\toolchain\toolchain.py

Pulling together required pieces...
Stubbing ammintrin.h...
Patching asyncinfo.h...
Cleaning up temporaries...

In a (clean) cmd shell, you can now run

  \path\to\google\chromium\win_toolchain\env.bat

then

  gclient runhooks (or gclient sync if you haven't pulled deps yet)
  ninja -C out\Debug chrome

Note that this script intentionally does not modify any global
settings like the registry, or system environment variables, so you
will need to run the above env.bat whenever you start a new
shell.