On 3/9/07, Andy Levy <andy.levy@gmail.com> wrote:
>
> On 3/9/07, Jim Lynch <jimlynch1@gmail.com> wrote:
> > I had been putting off moving my repositories from a ssh+svn access
> mode to
> > one that would accommodate access from more than just me so when the
> system
> > was destroyed I reloaded the repositories and put them under svnserver
> > control. On my dev system I have modifications that didn't get into the
> > repositories before the destruction. I know I can remove all the .svn
> files
> > and directories, check out the repository somewhere else, do something
> like
> > an rsync or find/cpio to replace the changed files and check the mods
> back
> > in. I've done that before and I know it works.
> >
> > Is there another way of telling svn that I'd like to check this into a
> > different repository? A simple svn ci complains that the repository
> can't
> > be accessed, of course.
>
> No need to touch your .svn directories - it's an easy way to hose your
> working copy.
>
> Use svn switch --relocate <NEWURL>
That didn't work, it gave me an error and generated a usage: block for svn
switch. So got to looking at the docs and tried:
cd test ( directory under svn control)
svn switch --relocate svn+ssh:/jlynch@<oldlocation>/home/jlynch/svntest
svn://jim@<newlocation>/svntest
That hangs forever. So I deleted test and recreated it ( identical to the
original test directory) and tried:
cd test ( directory under svn control)
svn switch --relocate
svn+ssh:/jlynch@<oldlocation>/home/jlynch/svntest/trunk
svn://jim@<newlocation>/svntest/trunk
This also hangs forever. No error messages, it just sits there and stares
at me, blinking.
Jim.
Received on Fri Mar 9 20:57:09 2007