blocks|key|1241200|text|我设法解决了这个问题，方法是恢复到mysql目录所在的最后一个版本，然后删除目录中的内容，将新内容放入其中，然后重新检入新信息。尽管我很好奇是否有人能更好地解释那里到底发生了什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1241201|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|$]]

I managed to work around it by reverting back to the last version that I had the mysql directory in, then deleting the contents of the directory, putting the new contents in it, and checking the new information back in. Although I'm curious if anyone has a better explanation for what the heck was going on there.

blocks|key|1241326|text|我不确定这是否对你有帮助，但我猜当你在删除它之后执行svn+add+mysql时，它只会重新实例化目录(所以不要自己执行mkdir+)。如果你自己创建了一个目录，svn希望里面有一个.svn目录，因为它已经“知道”了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1241327|entityMap^0|Q|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|$]]

I'm not sure if this is helping you, but I guess that when you do a <code>svn add mysql</code> after you've deleted it it will just reinstantiate the directory (so don't do a mkdir yourself). If you create a directory yourself svn expects a .svn directory inside it because it already 'knows' about it.

blocks|key|1241394|text|已经有了这种类型的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1241395|我的解决方案是：|1241396|从svn中删除文件夹，但在某个地方保留该文件夹的副本，然后提交更改。在备份副本中，递归删除其中的所有.svn文件夹。为此，您可以运行|1241397|#!/bin/bash

find+-name+'.svn'+%7C+while+read+directory;
do
++++echo+$directory;
++++rm+-rf+"$directory";
done;|code-block|syntax|javascript|1241398|删除本地存储库并重新签出整个项目。不知道部分删除/签出是否足够。|1241399|问候|1241400|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

already had this type of problem.

my solution was:

delete the folder from svn but keep a copy of the folder somewhere, commit the changes.
in the backup-copy, delete recursively all the .svn-folders in it. for this you might run

<pre><code>#!/bin/bash

find -name '.svn' | while read directory;
do
 echo $directory;
 rm -rf "$directory";
done;
</code></pre>

delete the local repository and re-check out entire project.
don't know whether partial deletion/checkout are sufficient.

regards

blocks|key|1241463|text|这是一个令人讨厌的.神秘的错误和没有明确的修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1241464|更新/恢复/提交在我的情况下不起作用。我没有做任何奇怪的事情--只是一些svn的动作。|1241465|对我来说起作用的是：|1241466|svn+remove+offender
svn+commit
cd+..
rm+-fR+parent
svn+up+parent
cd+parent
svn+remove+offender+again
svn+commit
copy+offender+back+in+(minus+.svn+dirs)
svn+add
svn+commit|code-block|syntax|javascript|1241467|至少可以说很奇怪。基本上，由于某些原因，svn+remove+--force+offender并没有完全移除。这就是错误消息所说的。只有通过移除父级，然后更新父级，这才变得明显，因为然后攻击者又出现了！svn删除罪犯再次，然后适当地删除它。|offset|length|style|CODE|1241468|entityMap^0|0|0|0|0|K|R|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

This is a nasty one... mysterious error and no clear fix.

update/revert/commit did NOT work in my situation. I hadn't done anything weird - just some svn moves.

What DID work for me was:

<pre><code>svn remove offender
svn commit
cd ..
rm -fR parent
svn up parent
cd parent
svn remove offender again
svn commit
copy offender back in (minus .svn dirs)
svn add
svn commit
</code></pre>

Weird to say the least. Basically, the <code>svn remove --force offender</code> wasn't doing completely removing for some reason. Which is sort of what the error message was saying. Only by removing the parent, then updating the parent, did this become obvious because then the offender reappeared! svn removing offender again then properly removed it.

blocks|key|1456355|text|我在Netbeans上运行的一个项目中遇到了这个问题。我只需在文件上单击鼠标右键并进行更新以修复它(在SVN建立之后)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1456356|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|$]]

I had this problem on a project I run on Netbeans. 
I simply right clicked on the file and update to fix it (after SVN up).

blocks|key|1456400|text|也有类似的问题。为了解决这个问题，从svn主干更新了本地文件的优先级选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1456401|svn+update+path/+--accept=mine-full|code-block|syntax|javascript|1456402|在你可以像往常一样提交之后。当然，要小心使用它。|1456403|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Had similar problem. To resolve it, updated from svn trunk with option of priority of local files.

<pre><code>svn update path/ --accept=mine-full
</code></pre>

After You could commit as usual. Of course, be careful using it.

blocks|key|1456498|text|问题是签出是在笔记本电脑上进行的，在这种情况下，subversion无法处理离线同步。这个问题可以在其他笔记本电脑上重现，而在台式机上，我可以毫不费力地签出相同的存储库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1456499|我希望这个答案会对你有所帮助，我花了很长时间才找到答案。|1456500|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|$]]

The problem is that the checkout takes place on a laptop and in this case subversion can not cope with the off-line synchronization. The problem is reproducable on an other laptop while on a desktop I have no problem checking out the same repository.

I hope this answer wil help you, it took me quite long to find out.

blocks|key|1456608|text|根据Atmocreation的解决方案，除非您不需要重新签出整个项目，如果您有正在进行的现有工作，这将非常有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1456609|假设你有一个正常工作的副本：|1456610|/foo/|code-block|syntax|javascript|1456611|其中包含目录：|1456612|/foo/bar/baz|1456613|并且在提交时会收到错误消息：|1456614|svn:+File+already+exists:+filesystem+'/foo/bar'|1456615|将bar的内容备份到某个位置：|1456616|mkdir+-p+~/tmp/code_backup
cp+-r+/foo/bar+~/tmp/code_backup|1456617|从备份中删除.svn控制目录。确保你的命令正确，否则你会造成严重的破坏！！如果您不确定，请手动删除它们。|1456618|find+~/tmp/code_backup/bar+-name+.svn+-type+d+-exec+rm+-rf+{}+\;|1456619|仔细检查副本是否相同：|1456620|diff+-r+-x+.svn+dist+~/tmp/code_backup/dist|1456621|从工作副本中删除有问题的目录:+cd+/foo+rm+-rf+bar|1456622|然后从存储库中恢复它：|1456623|cd+/foo
svn+update+bar|1456624|从备份中复制回修改后的文件：|1456625|cp+-r+~/tmp/code_backup/bar+/foo/|1456626|您现在应该能够在不出现错误的情况下提交。|1456627|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1I|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1J|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1K|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1L|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1M|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|1N|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1O|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1Q|8|@]|9|@]|A|$G|H]]|$1|Y|3|Z|5|6|7|1R|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|1S|8|@]|9|@]|A|$G|H]]|$1|12|3|13|5|6|7|1T|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1U|8|@]|9|@]|A|$]]|$1|16|3|17|5|F|7|1V|8|@]|9|@]|A|$G|H]]|$1|18|3|19|5|6|7|1W|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|F|7|1X|8|@]|9|@]|A|$G|H]]|$1|1C|3|1D|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]]|1F|$]]

As per Atmocreation's solution, except you don't need to re-checkout the whole project, which is useful if you have existing work in progress.

Let's say you have a working copy:

<pre><code>/foo/
</code></pre>

which contains directories:

<pre><code>/foo/bar/baz
</code></pre>

and you're getting the error message on commit: 

<pre><code>svn: File already exists: filesystem '/foo/bar'
</code></pre>

Backup the contents of bar somewhere: 

<pre><code>mkdir -p ~/tmp/code_backup
cp -r /foo/bar ~/tmp/code_backup
</code></pre>

Delete the .svn control directories from the backup. Make sure you get this command right, or you can do pretty serious damage!! Delete them manually if you're unsure.

<pre><code>find ~/tmp/code_backup/bar -name .svn -type d -exec rm -rf {} \;
</code></pre>

Double check that the copy is identical:

<pre><code>diff -r -x .svn dist ~/tmp/code_backup/dist
</code></pre>

Remove the offending directory from the working copy:
 cd /foo
 rm -rf bar

And then restore it from the repository:

<pre><code>cd /foo
svn update bar
</code></pre>

Copy back the modified files from backup:

<pre><code>cp -r ~/tmp/code_backup/bar /foo/
</code></pre>

You should now be able to commit without the error.

blocks|key|1241843|text|我今天遇到了这个问题，Xcode在分支合并过程中崩溃了。不知何故，文件被上传到svn存储库，但是它没有正确地记录在svn数据库中。我在本地文件所在的目录中运行了以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1241844|svn+revert+bad.file
svn+del+svn://my.svnserver.com/svnDB/path/to/the/offending/file/bad.file|code-block|syntax|javascript|1241845|然后，我从本地系统重新添加了该文件：|1241846|svn+add+bad.file
svn+commit+-m+"Re+adding+bad.file"|1241847|成功！|1241848|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I ran into this problem today when Xcode crashed during a branch merge. Somehow the file was uploaded to the svn repository but it wasn't recorded in the svn db properly. I ran the following commands in the directory where the file existed locally:

<pre><code>svn revert bad.file
svn del svn://my.svnserver.com/svnDB/path/to/the/offending/file/bad.file
</code></pre>

Then I re-added the file from my local system:

<pre><code>svn add bad.file
svn commit -m "Re adding bad.file"
</code></pre>

Success!

blocks|key|1241908|text|您需要的是svn+'export‘命令。这样，您就可以将文件或整个目录树置于另一个分支中的另一个修订版本的状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1241909|所以就像这样|1241910|rm+file+#without+'svn'+in+front!
svn+export+myrepo/path/to/file@<revision>+.
svn+commit|code-block|syntax|javascript|1241911|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|$]]

What you need is the svn 'export' command. With this you can put a file or entire directory tree in the state of another revision in another branch.

So something like

<pre><code>rm file #without 'svn' in front!
svn export myrepo/path/to/file@&lt;revision&gt; .
svn commit
</code></pre>

So - I used to have a directory called mysql a few revisions ago. I deleted it, and decided to start over - but when I try to create the new mysql directory - I keep running into the 'File Already Exists' error:

<pre><code>support:/etc/puppet/modules# mkdir mysql
support:/etc/puppet/modules# svn add mysql/
A mysql
support:/etc/puppet/modules# svn commit -m " Test"
Adding modules/mysql
svn: Commit failed (details follow):
svn: File already exists: filesystem '/var/lib/svn/puppet/db', transaction '11-r', path '/trunk/modules/mysql'
support:/etc/puppet/modules# svn delete mysql
svn: Use --force to override this restriction
svn: 'mysql' has local modifications
support:/etc/puppet/modules# svn --force delete mysql
D mysql
</code></pre>

I saw some other posts suggest forcing an update

<pre><code>support:/etc/puppet/modules# svn status
support:/etc/puppet/modules# svn update
At revision 11.
support:/etc/puppet/modules# svn mkdir mysql
A mysql
support:/etc/puppet/modules# svn commit -m "Test"
Adding modules/mysql
svn: Commit failed (details follow):
svn: File already exists: filesystem '/var/lib/svn/puppet/db', transaction '11-s', path '/trunk/modules/mysql'
</code></pre>

Strange problem with Subversion - "File already exists" when trying to recreate a directory that USED to be in my repository

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

所以，在几次修订之前，我曾经有一个名为mysql的目录。我删除了它，并决定重新开始-但当我尝试创建新的mysql目录时-我总是遇到‘文件已经存在’错误：support:/etc/puppet/modules# mkdir mysqlsupport:/etc/puppet/modules# svn add mysql/A...

问Subversion有一个奇怪的问题--当尝试重新创建我的存储库中曾经存在的目录时，“文件已经存在”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Subversion有一个奇怪的问题--当尝试重新创建我的存储库中曾经存在的目录时，“文件已经存在”EN