Comments on: Subversion Maintenance Scripts http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/ Musings of a software developer in Milwaukee, WI. Tue, 06 Jan 2009 11:12:45 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Windows Subversion Maintenance Scripts | Zorched / One Line Fix http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/comment-page-1/#comment-14286 Windows Subversion Maintenance Scripts | Zorched / One Line Fix Thu, 20 Nov 2008 02:46:47 +0000 http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/#comment-14286 [...] I wrote about the Subversion Maintenance Scripts that I use for doing things like backups and upgrades. They were bash shell scripts that automated [...] [...] I wrote about the Subversion Maintenance Scripts that I use for doing things like backups and upgrades. They were bash shell scripts that automated [...]

]]> By: Geoff Lane http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/comment-page-1/#comment-14284 Geoff Lane Wed, 19 Nov 2008 22:31:03 +0000 http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/#comment-14284 Daniel, Thanks for another way to do it. You are right, if you left the dump files in there and re-ran the script it would complain about those. I generally run it and then move all the dumps somewhere else. An easy way around the problem is just to redirect the dump output to another directory: <code lang="bash"> for i in *; do svnadmin dump $i > ../dumps/${i}.dump; done; </code> Daniel,
Thanks for another way to do it. You are right, if you left the dump files in there and re-ran the script it would complain about those. I generally run it and then move all the dumps somewhere else.

An easy way around the problem is just to redirect the dump output to another directory:

for i in *; do
    svnadmin dump $i > ../dumps/${i}.dump;
done;
]]> By: Daniel http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/comment-page-1/#comment-14283 Daniel Wed, 19 Nov 2008 21:37:27 +0000 http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/#comment-14283 Wouldn't your "dump all" script select files too and attempt to run the commands on them? If you are leaving all the dump files in the svn directory, then the ls would pick those up too so you'd have errors where the svnadmin command would be 'svnadmin dump x.dump > x.dump.dump' Here's a one liner that should avoid this problem: <code lang="bash"> find * -maxdepth 0 -type d -print0 | xargs -0 -I{} sh -c 'svnadmin dump {} > {}.dump' </code> Wouldn’t your “dump all” script select files too and attempt to run the commands on them? If you are leaving all the dump files in the svn directory, then the ls would pick those up too so you’d have errors where the svnadmin command would be ’svnadmin dump x.dump > x.dump.dump’

Here’s a one liner that should avoid this problem:

find * -maxdepth 0 -type d -print0 | xargs -0 -I{} sh -c 'svnadmin dump {} &gt; {}.dump'
]]> By: Brennan Stehling http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/comment-page-1/#comment-408 Brennan Stehling Thu, 28 Sep 2006 16:37:52 +0000 http://www.zorched.net/2006/09/27/subversion-maintenance-scripts/#comment-408 You may also want to note that your build integration server (CruiseControl) should be off during the upgrade because it will just slow down the process. I may wait till 1.4.1 before I make the jump. You may also want to note that your build integration server (CruiseControl) should be off during the upgrade because it will just slow down the process. I may wait till 1.4.1 before I make the jump.

]]>