> -----Original Message-----
> From: Andrey [mailto:andrey_at_online-solutions.ru]
> Sent: dinsdag 18 oktober 2011 11:54
> To: users_at_subversion.apache.org
> Subject: Very big problems with access rights (authz file using) in SVN
v1.7.0
> Importance: High
>
> 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.
Can you post a simple walkthrough script that describes your exact problem.
By just reading your mail I would guess the script is:
As user lk do:
$ svn co http://server/repos/PROJECT/trunk/Sample sample
$ svn up sample
(repeat the update)
But this simple scenario appears to work correctly for me as it doesn't
check out AnyDir/RestrictedDir in my tests.
The ouput of svn says that you update the directory above 'Sample'.
Things I'm interested in are like:
* Do multiple users share a single working copy?
So AnyDir/restricteddir is checked out by one user, but wouldn't be by the
user updating. Or the other way around.
* Is the configuration changed between updates?
Is some change in a specific location required between updates?
E.g. one in AnyDir, RestrictedDir, etc.
I can see some problems, which might need fixing but I'm still not sure what
your specific problem is.
(I'm not sure if the problems I currently see are regressions. Still looking
into that)
The error you see would only make sense if the working copy doesn't know
about RestrictedDir, except that it is a locally added file or directory.
When the server then tells that there should be a restricted path there you
get this error.
But giving a working copy with a single user, that is +- impossible to read
in your mail.
Bert
Received on 2011-10-18 14:43:24 CEST