My sysadmin migrated a repo by just zipping up a chunk of the filesystem
and stuffing it in an identical file structure on the new box. The new
box is suppose to be a functional copy of the old one, including host
name, the idea is all working copies could just continue to
checkout/commit/etc without haveing to change anything. He set up a
server that runs under xinetd and listens on a svn port. I thought it
might work even though that is not the recommended way to migrate a repo
but gives the error No repository found...... when you try a test commit
OK no problem I will do it the "right" way. I did svnadmin dump, then
packed up the dump, scp'd it to the new server, unpacked it and did
svnadmin load and that went through a lengthy procedure of adding each
commit from the dump. It all looked very reasonable. But now when I
add a new graphic to a working cpy and just try to just test commit it
to the repo from an old working copy it says No repository found in
svn://my.host.com:port/path/to/repo which is what it was doing in the
first place. Now what? I can give specific info privately but obvious
not in public. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-17 04:48:52 CEST