Re: explaining syntax-check hook-script

Marc Lustig wrote on Tue, 8 Sep 2009 at 00:05 -0700:
> problem scenario 1: svnsync rejects to operate because it cannot handle some
> svn:log properties. You can fix this by editing those messages.
>

Usually svnsync works fine and it is the destination repository which
rejects the commit that svnsync attempts to make.

> problem scenario 2: svnsync operates, but it creates "empty" commit's! i.
> e., all of the revisions are created, but they do not have any content. (I
> am not quite sure if this is related to some encoding problem, thou. It
> might be a compatibility issue between different SVN-versions.)
>

Could be authz related (you see an empty commit when you don't have
permission to see the paths modified in that commit).

> problem scenario 3: user A commits a file; user B checks the file out and
> apprently special chars are "spoiled", they are not re-encoded as they have
> been encoded before.
>

Are you sure it's not that one user's tools assume a different encoding
than the other user's?

Try to check the raw file. (e.g., use md5sum or a hex editor.)

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2392366

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-08 14:46:59 CEST