解决svn pritine text not exist问题

最新推荐文章于 2024-11-08 15:22:36 发布

转载最新推荐文章于 2024-11-08 15:22:36 发布 · 1.2k 阅读

本文提供了一种解决SVN工作副本中丢失原始文件问题的方法。通过使用SQLite查询找到相关文件路径，并更新数据库记录为‘not-present’状态，再运行清理命令及强制更新，使SVN能够重新获取丢失的文件。

[转自：http://hxfcalf.blog.163.com/blog/static/2157554820133711237590/]

http://stackbox.org

1) Get an sqlite executable (for Windows: download a pre-compiled
binary from http://www.sqlite.com/download.html). Put it somewhere in
your PATH.
2) Open a command prompt and go to the root of your working copy. Execute:
sqlite3 .svn\wc.db "select * from nodes where checksum like '%d9b41b57756396b9cb236801fc02e0da0a83dffe'"
This should return exactly 1 row from the svn working copy database.
You can see in that row the local path that's related to that pristine file.
3) Now execute:
sqlite3 .svn\wc.db "update nodes set presence='not-present' where checksum like '%d9b41b57756396b9cb236801fc02e0da0a83dffe'"
Now you've changed the presence value of that particular row to "not-present", giving svn a chance to recover from the actually
missing pristine file.
4) "svn cleanup" again. There might be more missing pristines. Repeat steps 2 and 3 for them.
5) Finally:
svn update --force
This makes svn actually restore the pristines. The --force is there because svn will also try to install the working versions 
of the "not-present" files. But those files are still there. Without --force you'll get tree conflicts on those files because of the "unversioned
obstructions" that svn thinks they are (because of "not-present" svn thinks they shouldn't be there).