blocks|key|3025136|text|我的猜测是，您尝试添加的文件夹在SVN中已经存在。您可以通过将文件签出到不同的文件夹来确认，并查看trunk是否已经具有所需的文件夹。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3025137|entityMap^0|B|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

My guess is that the folder you are trying to add already exists in SVN. You can confirm by checking out the files to a different folder and see if trunk already has the required folder.

blocks|key|301207|text|对我来说，修复它的最快方法是复制受影响的文件夹，并使用替代名称提交它。然后是svn+mv+duplicateFolder+originalFolder。很简单。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|301208|因此，使用folder1并创建一个folder1Copy：|301209|svn+delete+folder1
svn+add+folder1Copy|code-block|syntax|javascript|301210|提交和更新：|301211|svn+mv+folder1Copy/+folder1/|301212|再提交一次，问题就解决了。|301213|entityMap^0|12|11|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

The quickest way for me to fix it was to duplicate the affected folder, and commit it with an alternative name. Then <code>svn mv duplicateFolder originalFolder</code>. Pretty easy.

So, take folder1 and make a folder1Copy:

<pre><code>svn delete folder1
svn add folder1Copy
</code></pre>

Commit and update:

<pre><code>svn mv folder1Copy/ folder1/
</code></pre>

Commit again and it's fixed.

blocks|key|298417|text|我的“消失”文件夹是libraries/fof。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|298418|如果我删除了它，然后运行更新，它就不会出现了。|298419|cd+libaries
svn+up|code-block|syntax|javascript|298420|(什么都不会发生)。|298421|但使用实际名称进行更新：|298422|svn+update+fof|298423|做了这个小把戏，并且更新了。因此，我将我的(手动归档的)工作副本放在上面，然后重新提交。最简单的解决方案。|298424|entityMap^0|A|D|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|6|7|14|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|V|$]]

My "disappeared" folder was <code>libraries/fof</code>.

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

<pre><code>cd libaries
svn up
</code></pre>

(nothing happens).

But updating with the actual name:

<pre><code>svn update fof
</code></pre>

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

blocks|key|3239481|text|我刚刚在我自己的存储库中修复了这个问题。我在Windows上使用的是TortoiseSVN，所以我不确定这在命令行上翻译成了什么命令，但我这样做了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3239482|这个有问题的文件夹名为lib，应该添加它。|offset|length|style|CODE|3239483|3239484|首先我撤销了添加操作，这样SVN就不再关注它了。|unordered-list-item|3239485|然后我使用Windows上下文菜单将它重命名(改为libs，这不重要)，添加它，并成功提交。最后，我使用|3239486|的上下文菜单将其重命名为lib+(这可能很重要)，并再次提交。|3239487|3239488|entityMap^0|0|B|3|0|0|0|P|4|0|C|3|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|N|3|O|5|K|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

I just fixed this in my own repository. I'm using TortoiseSVN on Windows, so I'm not sure exactly what commands this translates to on the command line, but here's what I did:

The problematic folder is called <code>lib</code>, and it was due to be added. 

<ul>
<li>First I undid the add, so that SVN was no longer paying attention to
it.</li>
<li>Then I renamed it (to <code>libs</code>, not that that matters) using the Windows context menu, added it, and committed successfully. </li>
<li>Finally I renamed it back to <code>lib</code> using TortoiseSVN's context menu (this is probably important), and committed again.</li>
</ul>

blocks|key|298347|text|我刚才也遇到了这个问题，就是这样解决的。所以我把它录在这里，我希望它能对其他人有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298348|场景：|298349|在我提交代码之前，|298350|：100|ordered-list-item|298351|(其他人提交代码...版本增加到199)|298352|I+(忘记运行"svn+up"，)提交代码，现在我的版本:+200|298353|I+run+"svn+up“。|298354|298355|出现错误。|298356|解决方案：|298357|298358|$+mv+current_copy+copy_back+#重命名当前代码copy|298359|$+svn+checkout+current_copy+#再次签出|298360|$+cp+copy_back/+current_copy+#恢复您的copy|298361|298362|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|19|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|1E|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|1F|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|1G|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|12|$]]

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:

<ol>
<li>Before I commit the code, revision: 100</li>
<li>(Someone else commits the code... revision increased to 199)</li>
<li>I (forgot to run "svn up", ) commit the code, now my revision: 200</li>
<li>I run "svn up".</li>
</ol>

The error occurred.

Solution:

<ol>
<li>$ mv current_copy copy_back # Rename the current code copy</li>
<li>$ svn checkout current_copy # Check it out again</li>
<li>$ cp copy_back/ current_copy # Restore your modifications</li>
</ol>

blocks|key|3025339|text|我也遇到过类似的问题。我最终从轨道上删除了它，并在此过程中丢失了我的SVN历史记录。但至少我让那个该死的错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3025340|这可能是一个次优的执行命令序列，但它应该与我实际执行的命令序列非常接近：|3025341|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+%7C+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"|code-block|syntax|javascript|3025342|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

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:

<pre><code>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"
</code></pre>

blocks|key|298448|text|如果您使用code.google.com托管您的Subversion存储库。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|298449|你知道下面的事情，对吧？|298450|If+you+plan+to+make+changes,+use+this+command+to+check+out+the+code+as+yourself+using+HTTPS:

#+Project+members+authenticate+over+HTTPS+to+allow+committing+changes.
svn+checkout+https://.../svn/trunk/+user-...

When+prompted,+enter+your+generated+googlecode.com+password.
Use+this+command+to+anonymously+check+out+the+latest+project+source+code:

#+Non-members+may+check+out+a+read-only+working+copy+anonymously+over+HTTP.
svn+checkout+http://.../svn/trunk/+...-read-only|code-block|syntax|javascript|298451|您所提到的错误就是您使用的Non-members+may+check+out+a+read-only+working+copy+anonymously+over+HTTP状态。因此，到目前为止，您不能提交或执行任何操作。|298452|您必须使用Project+members+authenticate+over+HTTPS+to+allow+committing+changes+thing。|298453|现在会好起来的。|298454|entityMap^0|5|F|0|0|0|D|20|0|5|1V|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|15|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|T|$]]

If you use <code>code.google.com</code> to host your Subversion repository.

You know below things, right?

<pre><code>If you plan to make changes, use this command to check out the code as yourself using HTTPS:

# Project members authenticate over HTTPS to allow committing changes.
svn checkout https://.../svn/trunk/ user-...

When prompted, enter your generated googlecode.com password.
Use this command to anonymously check out the latest project source code:

# Non-members may check out a read-only working copy anonymously over HTTP.
svn checkout http://.../svn/trunk/ ...-read-only
</code></pre>

The error you mentioned exactly you are using <code>Non-members may check out a read-only working copy anonymously over HTTP</code> status. Therefore, you can not commit or do anything so far.

You must use <code>Project members authenticate over HTTPS to allow committing changes</code> thing.

It will be fine now.

blocks|key|298405|text|当前添加的目录已提交到存储库中。因此，删除存储库中的目录并再次提交相同的目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298406|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The currently added directory is already committed in the repository. So delete the directory in the repository and commit the same directory again.

blocks|key|301360|text|我遇到了同样的问题，并能够通过以下方式修复它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301361|301362|将文件夹复制到另一个位置。|ordered-list-item|301363|从复制的文件夹中删除|301364|右键单击原始文件夹并选择'SVN+.svn‘|301365|如果找不到(3)，则您的情况与我的不同。|301366|查看存储库浏览器上的目录是否正确。对于我的情况，这是原因。|301367|Check+out|301368|将文件从复制的文件夹中恢复到原始文件夹中|301369|301370|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|11|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

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

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

blocks|key|298475|text|这意味着您尝试放在svn上的文件夹/文件已经存在。我的建议是，在做任何事情之前，只需点击文件夹/文件，然后点击repo-browser。通过这样做，您将能够看到svn上已经存在的所有文件/子文件夹等。如果svn上不存在所需的文件/文件夹，则只需删除(备份后)要添加的文件，然后运行更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298476|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|3239743|text|我得到这个错误是因为我将URL地址替换为以"/“结尾的新地址。我指的是存储库表中.svn文件夹中wc.db数据库中的记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3239744|当我删除符号："/“时，错误就消失了。|3239745|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

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 well as the server copy. I can do updates and commits without problems on any other file or folder, but if I try to create a folder with the same name, add, and commit, it gives me the following error:

<blockquote>
 svn: Server sent unexpected return value (405 Method Not Allowed) in response to MKCOL request for '/svn/www/!svn/wrk/9de0d765-2203-456c-af16-58e792ec7ac0/trunk/htdocs/solutions/medical'
</blockquote>

I have run countless cleanups, commits, updates, etc. Nothing resolves the issue. Ideas?

FYI, I do not have the option of renaming the top level folder.

SVN 405 Method Not Allowed

我无意中删除了SVN中的一个文件夹，并立即将其添加回来。我遇到了一个问题，我的解决方案最终从我的本地副本和服务器副本中完全删除了该文件夹。我可以对任何其他文件或文件夹进行更新和提交而不会出现问题，但如果我尝试创建一个具有相同名称、添加和提交的文件夹，则会出现以下错误：MKCOL :服务器在响应'/svn/www/!svn/wrk/9de0d765-2203-456c-af16-58e792ec7a

问不允许使用SVN 405方法
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不允许使用SVN 405方法EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不允许使用SVN 405方法
EN