我如何知道当前 svn 存储库是哪个版本?
最近,我决定将我的 svn 存储库从 v1.5 升级到 v1.6。 运行升级命令后,我看到 CMD 窗口中留下的消息。
D:\svn>svnadmin upgrade repo
Repository lock acquired.
Please wait; upgrading the repository may take some time...
Upgrade completed.
D:\svn>_
呀!! 看起来很棒...但是...我如何知道当前存储库是哪个版本? 是升级到v1.6还是还是v1.5。 我的存储库很少。 我怎样才能找到他们的版本?
Recently, I made a decision to upgrade my svn repository from v1.5 to v1.6. After I run the upgrading command then I saw the message left in CMD windows.
D:\svn>svnadmin upgrade repo
Repository lock acquired.
Please wait; upgrading the repository may take some time...
Upgrade completed.
D:\svn>_
Ya!! It seems great... but.... How do I know which version current repository is? Is it upgraded to v1.6 or still is v1.5. There are few repositories I have. How can I find out their version?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
查看存储库路径中的文件“格式”。 它应该包含您的存储库的架构。 由于 Subversion 1.4 是 5,并且在 Subversion 2 之前可能不会更改。只要架构不更改,就不需要“svnadmin 升级”。
引用 http://svn.apache.org/repos/asf/ subversion/trunk/notes/repos_upgrade_HOWTO:
不要将存储库架构与工作副本混淆。 工作副本中的格式文件包含当前版本的 subversion 的“9”。
Take a look into the file 'format' in your repository-path. It should contain the schema of your repository. Since Subversion 1.4 that is 5 and will probably not changing before Subversion 2. As long as the schema don't change a 'svnadmin upgrade' is unnecessary.
To cite http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO:
Don't mix up the repository-schema with the one of the working-copy. The format-file in working-copy contains a '9' for current versions of subversion.
除了 /format 之外,现在还有一个文件 /db/format,例如在使用 1.6.x 创建的默认存储库中,它具有以下内容:
4
布局分片 1000
对于升级到 1.5.5 的存储库:
3
线性布局
对于普通香草 1.4.2 存储库:
2
Apart from /format, now there's also a file /db/format, e.g. in default repo created with 1.6.x it has the following content:
4
layout sharded 1000
For a repo upgraded to 1.5.5:
3
layout linear
For plain vanilla 1.4.2 repos:
2
查看此代码以更改 subversion 工作副本的格式
最新格式是
Looking at this code to change the format of subversion working copy
the latest formats are