No problem.
Yes, depot_tools keeps its own copy of svn and python. "Reinstalling"
is an overstatement, it just puts it into depot_tools with svn.bat and
python.bat. :)
M-A
On Sun, May 17, 2009 at 1:49 PM, Eeyore wrote:
>
>> Try (assuming you already have svn on your system)
>> rd /q /s depot_t
> Try (assuming you already have svn on your system)
> rd /q /s depot_tools
> svn co http://src.chromium.org/svn/trunk/tools/depot_tools/
>
> It seems like an issue with svn version clash. Yay.
Wow, that seems to have worked. When I ran gclient after pulling
depot_tools from SVN, in actually *re
Try (assuming you already have svn on your system)
rd /q /s depot_tools
svn co http://src.chromium.org/svn/trunk/tools/depot_tools/
It seems like an issue with svn version clash. Yay.
M-A
On Sat, May 16, 2009 at 2:49 PM, Eeyore wrote:
>
> I think gclient is just totally busted on Vista and Win
I think gclient is just totally busted on Vista and Win7.
My machine has SVN and Python installed already so gclient doesn't
need to download them, and gclient still fails with the same errors.
Completely fresh directory at e:\chrome with freshly unzipped
depot_tools, this is what happens:
E:\c
Marc-Antoine Ruel wrote:
> svn: Your .svn/tmp directory may be missing or corrupt; run 'svn
> cleanup' and try again
>
> This error is really weird.
>
> svn: Can't open file 'C:\tmp\depot_tools\.svn\tmp\log': The system
> cannot find the path specified.
>
> This error is even more weird.
>
> c:\tm
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn
cleanup' and try again
This error is really weird.
svn: Can't open file 'C:\tmp\depot_tools\.svn\tmp\log': The system
cannot find the path specified.
This error is even more weird.
c:\tmp>echo %PATH%
C:\Windows\system32;C:\Window
