8

I am synchronizing an SVN repository between two systems using svnsync and I am not 100% sure if its possible to make it independent for my "new users" after the sync is finished.

What do I need to do to make it a completely independent entity? Is it enough just to change the passwd file?

4

2 に答える 2

11

What do I need to do to make it a completely independent entity?

The only link between the new repository and the original are a number of revision properties that are used by svnsync synchronize. You can safely remove those like this:

svn propdel --revprop -r 0 svn:sync-from-uuid http://svn.example.com
svn propdel --revprop -r 0 svn:sync-last-merged-rev http://svn.example.com
svn propdel --revprop -r 0 svn:sync-from-url http://svn.example.com

This doesn't do much except making sure that svnsync synchronize cannot be run anymore.

edit: Just thought of something else. You might have used svn:externals properties in your projects for pointing to another repository, or another location within the same repository.

One should use the relative URL syntax for links within the same repository, in which case there is no problem. But if an absolute URL was used for that, then such links will continue to point to the original repository after an svnsync. You can inspect all svn:externals properties like this (might take a while, recursively scans all folders):

svn propget -R svn:externals http://svn.example.com/
于 2011-01-20T17:48:18.920 に答える
0

基本的に、次のようなapache構成が必要です。

  • 別のURLと別の新しいリポジトリを参照するAuthName
  • conf/authz上記の新しいリポジトリのファイルで新しいユーザーを宣言します。
  • パスワードの宣言（使用している場合：q！AuthType Basic認証モード）

異なるパスワードを持つことは必須ではありません。2つのリポジトリが2つの異なるアドレス（同じapacheまたは2つの異なる「apache」の下）で管理されると、それらは互いに独立します。

于 2011-01-20T07:25:00.157 に答える