Re: Issue 89900 in chromium: svn within depot_tools' svn_bin.zip fails for "svn --version" at Windows Command Prompt

12 views
Skip to first unread message

chro...@googlecode.com

unread,
Jul 21, 2011, 2:59:47 PM7/21/11
to chromi...@chromium.org

Comment #5 on issue 89900 by mar...@google.com: svn within depot_tools'
svn_bin.zip fails for "svn --version" at Windows Command Prompt
http://code.google.com/p/chromium/issues/detail?id=89900

Since you have svn.exe already installed, simply modify depot_tools\svn.bat
to call your installed copy and call it done.

chro...@googlecode.com

unread,
Jul 21, 2011, 4:08:54 PM7/21/11
to chromi...@chromium.org

Comment #6 on issue 89900 by epo...@google.com: svn within depot_tools'
svn_bin.zip fails for "svn --version" at Windows Command Prompt
http://code.google.com/p/chromium/issues/detail?id=89900

Yes, that is exactly what I did as my workaround. But if depot_tools is
going to provide its own version of svn, shouldn't we make it work?

For me personally, the need for manual adjustment within depot_tools
complicates automated setup of new Windows buildbot slaves; I imagine there
must be others out there whom this causes other forms of pain.

Bottom line: if I create a new svn_bin.zip that works better, can I replace
the one in the repository with it?

chro...@googlecode.com

unread,
Jul 21, 2011, 4:33:22 PM7/21/11
to chromi...@chromium.org

Comment #7 on issue 89900 by mar...@google.com: svn within depot_tools'
svn_bin.zip fails for "svn --version" at Windows Command Prompt
http://code.google.com/p/chromium/issues/detail?id=89900

Supporting people with a svn client already installed has never been a
goal. None of our buildbot has svn installed. So yes, right now it just
works for our devs in the normal case.

chro...@googlecode.com

unread,
Jul 24, 2011, 10:08:53 PM7/24/11
to chromi...@chromium.org

Comment #11 on issue 89900 by epo...@google.com: svn within depot_tools'
svn_bin.zip fails for "svn --version" at Windows Command Prompt
http://code.google.com/p/chromium/issues/detail?id=89900

I just tried it out on a virgin Windows machine (my home Windows 7 machine)
and it worked fine as described below. So this does indeed seem to have
been a problem with my particular installation--please feel free to close
this bug. Sorry for the noise.


- downloaded depot_tools.zip from
http://www.chromium.org/developers/how-tos/install-depot-tools

- unzipped depot_tools.zip into c:\temp

- opened a Command Prompt window...
cd c:\temp\depot_tools
gclient --help
[this installed subversion and python]

- added c:\temp\depot_tools to my PATH as described at
http://www.chromium.org/developers/how-tos/install-depot-tools

- opened a new Command Prompt window...
cd c:\temp
mkdir test
cd test
gclient config http://src.chromium.org/svn/trunk/tools/depot_tools
gclient sync --manually_grab_svn_rev
[and it worked fine, checking out revision 93835]
gclient sync --manually_grab_svn_rev -r 93834
[and it worked fine... nothing different to check out]
gclient sync --manually_grab_svn_rev -r 90000
[and it worked fine]
svn --version
[reported version 1.6.6 and worked fine]

chro...@googlecode.com

unread,
Jul 25, 2011, 1:10:31 PM7/25/11
to chromi...@chromium.org
Updates:
Status: WontFix

Comment #12 on issue 89900 by mar...@chromium.org: svn within depot_tools'

svn_bin.zip fails for "svn --version" at Windows Command Prompt
http://code.google.com/p/chromium/issues/detail?id=89900

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages