Svn commit does not work svn: '/ svn /! svn / bc /

Question

After doing some refactoring, in Eclipse, Subversion starts complaining about the commit. I do not know how to fix this. I uninstalled (and committed the removal of GPFragmentRef.java .

 > niclas@nl :~/$svn commit -m "trying again" Adding core/doc/GDocSection.java Adding core/doc/GDocSectionID.java Adding core/doc/GDocSectionRef.java svn: Commit failed (details follow): svn: '/svn/!svn/bc/21791/DST/trunk/grammar-core/src/main/java/dts/grammar/core/policy/GPFragmentRef.java' path not found 

What does svn/!svn/bc mean?

Answer 1

It looks like svn is trying to make changes to GPFragmentRef.java . Perhaps you can run svn cleanup to see if this helps. Another possibility is to try to revert changes to this file by running svn revert only in this file .

Answer 2

The solution to the problem was as follows:

• Issue a new working copy.
• Manually adding changes to a new working copy from a broken one.

Answer 3

I'm sure you moved, but I just got the same error using the subversion client from the command line, and this turned out to be a capitalization problem in my way. Pretty obvious, but I thought I would drop him there to save someone else for a while.

Answer 4

This can happen if you manually copy the project to another repository locally and all .svn directories still exist.

Use this in the copied directory to erase Subversion metadata:

 find . -type f -name ".svn" -exec rm -i -f -r '{}' \; 

Answer 5

I had the same problem (also caused by too many renaming / refactors / moves / etc.). I was able to solve it by creating a patch, returning all the changes, and then applying the patch. After that I could do very well.

Answer 6

This is an internal set of URLs that Subversion uses to manage commit transactions, etc. It looks like your server is no longer configured to host your repository at this URL.

You must verify that mod_dav_svn is still configured and configured. Can you get a clean check or perform any operation that negotiates with the server, for example. svn status -u ?

Alternatively, it could be a route filtering problem if your administrator tried to filter your access to specific paths in the repository. You will also always need access to the / svn / tree! Svn / tree and possibly also (thanks to an old error) to make an OPTIONS request to the root of the repository, / svn.

Answer 7

This can happen when you perform a series of actions related to copying, modifying, and deleting one or more files. Subversion may lose them during the rename / delete process, and commits will fail. Move aside the intruder files or directory, reinstall it using the svn update, and copy the modified files to the new directory. You may lose information about renaming renamed / moved files, but you can commit your changes.

Answer 8

It worked for me: Gradually change your changes, update, hand over again, and then commit.