Hi all,
I'm getting a weird commit bug on MacOS X. Symptoms are as follows:
I have a repos freshly loaded from a dump file. I have a tar file of
updates to one of the dirs.
I check out the dir. Unpack the tar file over it. Use
svn st | awk '/\?/ {print $2}' | xargs svn add
to add the new files. Then I make some property changes making all the
files added have a binary svn:mime-type. Then I commit, and get the
following:
% svn commit
[snip sending and adding lines]
Transmitting file data .....................
subversion/libsvn_client/commit.c:685
svn_error: #21076 : <Item already exists in filesystem>
Commit failed (details follow):
subversion/libsvn_fs/bdb/nodes-table.c:262
svn_error: #21076 : <Item already exists in filesystem>
successor id `jv.11.5u' (for `jv.0.5f') already exists in filesystem
/Users/will/svnroot/db
This is totally repeatable. I tried to narrow it down:
- I am using ra_local
- It is possible to commit a few files at a time and have all the commits
succeed.
- There are about 35 files varying in size from 10k-100k
- I can create a new repository, export the offending dir, add it to the new
repos, commit and check out, then unpack the tar'd changes, add and commit
the new files. This does not reproduce the problem - there is something
about the repository (which was freshly loaded from a dumpfile).
- On the way I discovered that 'svn export' is making '.svn' dirs in the
exported dir. I filed a bug report on that.
I may make it onto #svn Monday... We'll see.
Later,
\x/ill :-}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 29 05:20:30 2002