SVN specific version install

[Joseph Hales]

I am migrating to an new server and was gonna bring the new server up to the samve svn 2952 that my main server is running before backing up my live data and restoring it to the new hardware. When I run the command [B]svn up -r 2952[/B] I get the message [B]Skipped ‘.’ [/B]and nothing seems to download am I doing something wrong.

[Tom Elliott]

If you’ve already checked out the repo, then svn up will work, if you haven’t recheck it all out with:

[code]svn co -r 2952 https://svn.code.sf.net/p/freeghost/code/trunk[/code]

[Sebastian Roth]

Sounds like you were not in the correct directory. Please run ‘svn status’ from that same directory to see if this is a SVN path really…

[Joseph Hales]

svn status gives me
svn: warning: ‘.’ is not a working copy

[Tom Elliott]

What folder are you in?

[Joseph Hales]

Running
[FONT=Consolas]svn co -r 2952 [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url][/FONT]
[FONT=Consolas]does allow me to upgrade but [/FONT]
[FONT=Consolas]svn status still retuns the error[/FONT]
[FONT=Consolas][FONT=Tahoma]svn: warning: ‘.’ is not a working copy [/FONT][/FONT]this is from the ~\svn folder

[Tom Elliott]

if you’re not in the working copy directly, or explicitly telling it where the “working copy” is, it assumes the CWD.

For example:

You have terminal-ed in to: /root or /home/jhales

If you run svn up from here, but the working copy is in /root/svn or /home/jhales/svn it will give the error:

[code][jhales@localhost ~] $ svn up
svn: warning: ‘.’ is not a working copy
[/code]

if you cd into the proper directory as such:
[code][jhales@localhost ~] $ cd svn
[jhales@localhost ~/svn] $ svn up[/code]

You shouldn’t have any issues.

Or explicitly set the “working directory”
[code][jhales@localhost ~] $ svn up svn[/code]

You shouldn’t have any issues.