On Sun, Jul 27, 2008 at 10:11 PM, Blair Smith <b.smith_at_irl.cri.nz> wrote:
> I have a user who wants to backup an entire svn project, including the
> ".svn/" directory.
> He's having write problems for files like ".svn/all-wcprops",
> "./svn/entries", "./svn/format"
> these all only have read permission and his backup utility program
> obviously tries
> incremental backup0s or diff backups, he's a Windoze user and I'm not
> familiar with
> his backup software, but it is a program called "Unison File Synchronizer"
> (Version 2.26.12).
> I wondered if it would bust svn if I simply added write permissions for
> those three files?
> If it is "only risky" to do so (version corruption risk???) then I'll warn
> him and let him decide.
> Thanks for any help,
> Blair M. Smith
> Industrial Research Limited
> TEL: +64 4 931 3132
> PS. I'm not an IT guy, I'm just a scientist who manages one server.
Unison may be overkill. He could just use zip (or 7za) with the -u (update)
flag to keep a compressed backup of the directory.
@rem assume a working copy here:
@rem run periodically (could put into a batch file)
zip -9ru e:\BACKUP\fred\ProjectA.zip c:\src\work\ProjectA
and run that periodically to update the zip. If there are no changes to the
working copy, then the zip file is not updated.
If you're user is using unison to keep two working copies in sync, then he
probably needs to change they way he's using svn.
Received on 2008-07-28 18:22:33 CEST