Andreas Stieger wrote on Fri, 13 Mar 2020 11:45 +00:00:
> Hello,
>
>
> > “svnsync init --allow-non-empty --username abcd file:///u03/svn/repos
> > svn://xxx.xxx.xxx.xxx/”
> [...]
> > svnsync: E165001: Revprop change blocked by pre-revprop-change hook (exit
> > code 1) with output:
> > Changing revision properties is not permitted, the user used is klnm
>
> When running the svnsync sync command from your cron, specify the
> destination repository username using one of the following options:
>
> --username ARG : specify a username ARG (deprecated;
> see --source-username and --sync-username)
> --sync-username ARG : connect to sync repository with username ARG
>
The OP already does this, according to the command line they gave. Note
that --username=foo implies --sync-username=foo
> The credentials originally given to svnsync init are cached in the
> authentication cache. However they are not "remembered" in the sense of
> always using the same user. You still need to specify the user if it
> deviates from the user executing the cron job.
If this is true, then why don't I need to specify «--username=danielsh»
when I commit to svn.a.o? My local username is "daniel", and when
I commit to svn.a.o, it doesn't try to authenticate as "daniel" (as it would
if the auth cache were empty); it tries to authenticate as "danielsh" right
off the bat.
Cheers,
Daniel
