The work around is to enable (append or edit) to barbar/conf/svnserve.conf lines:
password-db = passwd
authz-db = authz
And this setting must remain all the time.
But is NOT needed when using the old-repo I mentioned above.
So apparently if repo was created in other way (the old one was done afair with svn+ssh at first) then some parts of settings in svnserver are not important.
So this is ANOTHER of authz usage inconsistencies (see also bug#519083)!
Really this should be more consistent and documented. I will contact upstream.
Marking as security bug, really source code can be important, not everyone is [wide]open-source ;)
The work around is to enable (append or edit) to barbar/ conf/svnserve. conf lines:
password-db = passwd
authz-db = authz
And this setting must remain all the time.
But is NOT needed when using the old-repo I mentioned above.
So apparently if repo was created in other way (the old one was done afair with svn+ssh at first) then some parts of settings in svnserver are not important.
So this is ANOTHER of authz usage inconsistencies (see also bug#519083)!
Really this should be more consistent and documented. I will contact upstream.
Marking as security bug, really source code can be important, not everyone is [wide]open-source ;)