Hello!
We had upgraded from SVN v1.6.5 to SVN v1.7.0, and now we have a
really big problems, because SVN v1.7.0 is not working as previous SVN
versions and incorrectly working with restrictions for some
directories in authz.
A simple example of the issue:
Let's assume this authz file:
===================================================
[repos:/PROJECT/trunk/Sample]
ax = rw
mh = rw
lk = rw
sa = r
ep = rw
[repos:/PROJECT/trunk/Sample/AnyDir/RestrictedDir]
ax = rw
mh = rw
* =
===================================================
SVN v1.6.5 and all clients worked with it in the following manner:
1. They are allowed to use 'svn update' command on the "Sample" directory.
2. They are showed "Sample/AnyDir/RestrictedDir" in repo-browser
(TortoiseSVN GUI), but did not allowed to update/commit or view
content of this directory.
3. There are no any problems to make svn update in any part of the
"/Sample" dir and subdirs using svn client (command line) or any
other (GUI) client.
After upgrading our server to SVN v1.7.0 we had a really big problems,
because now when we try to make update in the root directory (/Sample)
we see something like:
========================================================================
Updating '.': 13:5
Restored 'Sample\AnyDir\RestrictedDir'
svn: E155000: Failed to mark 'D:\BUILD_ROOT\PROJECT\trunk\Sample\AnyDir\RestrictedDir'
absent: item of the same name is already scheduled for addition
========================================================================
So, SVN update failed!
No we cannot use our BUILD SERVER, also coders are unable to make SVN
UPDATE locally with the same problem!
We have a complicated access rules for different users. Now it does
not work AT ALL! Because if some directory is available for user to
see that it is exist (it is made to give a possibility to make a
commits in a root directory, and do not split commits to a few dirs),
he will unable to make svn update in the root -- svn will fail on this
directory, that must be easly skipped, as SVN v1.6.5 server/clients
done before!
This is a really serious problem for us, we can't work now.
-- FTSOS
Andrey mailto:andrey_at_online-solutions.ru
Received on 2011-10-18 12:09:05 CEST