I am running svn 0.30 on Win2k over http.
I just updated one of my project wc's to the latest revision (313). My
colleague had in that revision modified some files, added a dir called
"Common" and added a file inside that dir. However, when I performed
"svn update" (which completed successfully), the new dir and file wasn't
"svn info" shows that my wc is revision 313 and running "svn update"
again just tells me "At revision 313". "svn switch" to itself (so to
speak) complains that "directory 'Common' not locked". The .svn/entries
file looks like this:
?xml version="1.0" encoding="utf-8"?>
The Common directory should have an entry but is missing.
I saw that .svn/wcprops has a file called Common.svn-work with contents:
If I checkout the project in a new folder, all files gets downloaded
fine and the entries file list an entry for the "Common" dir.
I guess I should be able to create a "Common" folder myself and do a
checkout on that. But I first want to ask on the mailing list, maybe you
guys have any other suggestions?
Also, another colleague reported that he performed an update on the
project to the same revision and got the Common folder but the update
failed to modify one of the files. Performing an update on the file
itself instead of its parent dir worked, however.
The only thing that I can recall that could have affected the database
is that yesterday evening, when everyone but me had gone home, stopped
and restarted the apache server since it had eaten lots of memory.
Before today, we have been using svn heavily for a month, with nothing
but positive experience! But I would really appreciate any hints on what
could be causing the above effect. Should I dump/restore the repository?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Oct 16 16:19:50 2003