DickLane
I am puzzled by this. Is it the case that svnadmin verify (path to old repo) svnadmin dump (path to old repo) > old.dump svnadmin create (path to new repo) svnadmin load (path to new repo) < old.dump will create and populate a repository which uberSVN cannot handle?
wmellors
One way around this is that you could create the repo in whatever external manner you wish and then via uberSVN use one of the options on the Add Repo feature. Options such as Import From Local Dump, Import From Server Dump, Add Existing Repo On Server, etc. That will then bring them under the control of uberSVN (and located within the repositories storage location set in uberSVN Administration). You can see all these options by following this path... Repositories > Add Repo > Enter Name And URL > Create Or Import Repository. There are three. Hope this helps. Wayne
munseym
Technically you can create a repo in ubersvn then manually edit the ubersvn/conf/conf.d/50-repositories.conf to point it at a repo somewhere else. However, this file gets overwritten any time a repo is created or deleted in ubersvn, so if you do this you will have to redo your change any time ubersvn overwrites it, and then restart apache.