I decided to start fresh, and downloaded the source tar-ball. Then
when I ran gclient sync, here is what I got:
$ gclient sync 21 | tee sync.log
running '/Users/mjaffe/Development/depot_tools/bin/../
platform/mac/bin/svn update' in '/Users/mjaffe/Development/Chrome/
chromium/src'
U
This was the behavior of an old gclient.py as well. How did you get gclient?
On Fri, Dec 19, 2008 at 1:01 PM, Jaff jaffe.m...@gmail.com wrote:
Well, this is too strange. It would seem as if some other file-system
mechanism is cacheing
data. I created a new directory and attempted a fresh
Well, this is too strange. It would seem as if some other file-system
mechanism is cacheing
data. I created a new directory and attempted a fresh checkout, and it
crashes/halts in exactly the same place. Complains about src/
third_party/WebKit:
svn: '/trunk/deps/third_party/web...@7278' does not
Just to confirm, today I checked out two new clients on two fresh machines
(Mac, Windows) and haven't had issues.
Sounds like a gclient issue to me (either the configuration or the script
itself).
On Fri, Dec 19, 2008 at 1:09 PM, Mark Larson (Google) m...@chromium.orgwrote:
On Fri, Dec 19,
On Fri, Dec 19, 2008 at 13:01, Jaff jaffe.m...@gmail.com wrote:
Well, this is too strange. It would seem as if some other file-system
mechanism is cacheing
data. I created a new directory and attempted a fresh checkout, and it
crashes/halts in exactly the same place. Complains about src/
OK, here is the contents of .gclient
# An element of this array (a solution) describes a repository
directory that
# will be checked out into your working copy. Each solution may
optionally define
# additional dependencies (via its DEPS file) to be checked out
alongside the
# solution's
I had an older checkout in another directory
I may need to update the client config.
On Dec 19, 1:10 pm, Evan Martin e...@chromium.org wrote:
This was the behavior of an old gclient.py as well. How did you get gclient?
On Fri, Dec 19, 2008 at 1:01 PM, Jaff jaffe.m...@gmail.com wrote:
OK, now I cannot even use svn anymore, trying to do a new client
config yieds this error:
dhcp-172-19-240-54:~/Development/Google mjaffe$ gclient sync
svn: '.' is not a working copy
svn: This client is too old to work with working copy '/Users/mjaffe/
Development/Google/src'; please get a newer
You've been updated since svn: '.' is not a working copy is an
error I recently introduced on non-Windows platforms. You can safely
ignore it.
That's strange that you have svn version issues since we don't include
svn in the depot_tools on non-windows platform.
FYI, svn 1.4 can't read
Personally I've never seen that error before.
I'd suggest you try checking out a fresh copy. Let us know if that fixes
things...
Best regards,
Jeremy
On Thu, Dec 18, 2008 at 12:34 PM, Jaff jaffe.m...@gmail.com wrote:
Hi,
I've been wanting to get into some contribution-mode, so I have
Probably my fault, let me confirm.
M-A
On Thu, Dec 18, 2008 at 3:34 PM, Jaff jaffe.m...@gmail.com wrote:
Hi,
I've been wanting to get into some contribution-mode, so I have gotten
far enough to download the source and make my environment compatible
(MacbookPro, 2.4GHz, 2Gb RAM). However,
This is odd; it is an entirely fresh copy. Except maybe I left a .svn
directory in there...
On Dec 18, 12:50 pm, Jeremy Moskovich jer...@chromium.org wrote:
Personally I've never seen that error before.
I'd suggest you try checking out a fresh copy. Let us know if that fixes
things...
12 matches
Mail list logo
