SVN 405 Method Not Allowed

Question

I accidentally deleted a folder in SVN and added it back immediately. I ran into an issue with this and my solution ended up removing the folder completely from my local copy as

Answer 1

I got this error because I replaced URL address with new one ending up with "/". I mean record in wc.db database in .svn folder in REPOSITORY table.

When I removed sign: "/" then the error went away.

Answer 2

I encountered the same issue and was able to fix it by:

1. Copy the folder to another place.
2. Delete .svn from copied folder
3. Right click the original folder and select 'SVN Checkout'
4. If you can't find (3), then your case is different than mine.
5. See if the directory on the REPO-BROWSER is correct. For my case, this was the cause.
6. Check out
7. Get back the files from the copied folder into the original directory.
8. Commit.

Answer 3

I also met this problem just now and solved it in this way. So I recorded it here, and I wish it be useful for others.

Scenario:

1. Before I commit the code, revision: 100
2. (Someone else commits the code... revision increased to 199)
3. I (forgot to run "svn up", ) commit the code, now my revision: 200
4. I run "svn up".

The error occurred.

Solution:

1. $ mv current_copy copy_back # Rename the current code copy
2. $ svn checkout current_copy # Check it out again
3. $ cp copy_back/ current_copy # Restore your modifications

Answer 4

This means that the folder/file that you are trying to put on svn already exists there. My advice is that before doing anything just right click on the folder/file and click on repo-browser. By doing this you will be able to see all the files/sub-folders etc that are already present on svn. If the required file/folder is not present on the svn then you just delete(after taking backup) the file that you you want to add and then run an update.

Answer 5

My "disappeared" folder was libraries/fof.

If I deleted it, then ran an update, it wouldn't show up.

cd libaries
svn up

(nothing happens).

But updating with the actual name:

svn update fof

did the trick and it was updated. So I exploded my (manually tar-archived) working copy over it and recommitted. Easiest solution.

Answer 6

I had a similar problem. I ended up nuking it from orbit, and lost my SVN history in the process. But at least I made that damn error go away.

This is probably a sub-optimal sequence of commands to execute, but it should fairly closely follow the sequence of commands that I actually did to get things to work:

cp -rp target ~/other/location/target-20111108
svn rm target --force
cp -rp ~/other/location/target-20111108 target-other-name
cd target-other-name
find . -name .svn -print | xargs rm -rf
cd ..
svn add target-other-name
svn ci -m "Re-re-re-re-re-re-re-re-re-re import target"
svn mv target-other-name target
svn ci -m "Re-re-re-re-re-re-re-re-re-re import target"