2009/5/14 Andrew Sasak <andrew.sasak_at_gmail.com>
> I recently started use svnsync to maintain a mirror of a repository where I
> do not have read permission for everything. Occasionally new subdirectories
> are added to the repository and if necessary I am granted read access. Since
> access is usually granted *after* the directory is created, it throws
> svnsync for a loop.
>
> Apart from changing the policy regarding how access/permission is granted,
> how can I solve this problem?
>
> It seems like I could dump from my mirror up until the creation of the
> directory, then recreate the mirror using the dumpfile and sync. However,
> I'm not sure if this work because it seems like the mirror uses rev 0 to
> keep track of the most recently synced revision. In the case of access being
> granted several (hundred or thousand) revisions after the directory being
> added, even if this worked it seems like there should be a more efficient
> way to do this, although its probably not currently implemented (like
> "resyncing" starting at a specified revision).
>
Since subversion is essentially a write once file system, re-syncing will
not work, as the transactions have already been committed.
You would probably need to do a dump-load up to the first dodgy transaction,
then manually edit the svnsync properties on rev 0.
As regards fixing svnsync... the only solution I can see is that svnsync
stops as soon as it reaches something it cannot read... thus you would loose
sync until you are granted read access to the new folder... then you start
svnsync and it will pick up from where it started.
Of course the svn developers may have a better answer...
-Stephen
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2267344
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-15 08:43:41 CEST