On 26 Jan 2003, Karl Fogel wrote:
Faheem Mitha faheem@email.unc.edu writes:
faheem /tmp/repossvn commit
Deleting newthesis
Committed revision 4.
and then
faheem /tmpsvn import http://localhost:8080/svn/repos foo.c foo.c
Adding foo.c
Transmitting file data .
Committed revision 5.
and now I get
faheem /tmpsvn co http://localhost:8080/svn/repos
svn: Obstructed update
svn: revision 5 doesn't match existing revision 4 in 'repos'
From looking at the name of your working copy, you seem maybe confused
about a working copy vs a repository? (Or is that a misimpression?)
No, I'm not really confused about the difference. See below.
The directory you call /tmp/repos is not, in fact, a repository, but
rather a working copy. Even if you know that in your head, it's
better when posting examples to the list to use some other name, so
*we* don't get confused, nor mistakenly think you are confused.
Anyway, don't try to check out ('co') over your existing working
copy. You need to use 'svn update' instead. Checkout is for creating
new working copies; update is for bringing existing working copies
up-to-date with respect to the working copy.
I see. I didn't realise or forgot that I was already inside a working copy
when I did the checkout, and then I got confused by the error message,
thinking the 'repos' referred to my repository when it really referred to
the local/working copy :-). The /tmp/repos name came because I originally
checked out the entire repository into /tmp. Yes, it is confusing, but how
would you suggest avoiding this? Renaming the working copy to something
else, perhaps?
I'm rather new at this. I will get better. Thanks for your help.
Faheem.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:19:07 2006