Здравствуйте, Johan. Вы писали 18 октября 2011 г., 17:43:48:
JC> 2011/10/18 Andrey <and...@online-solutions.ru>: >> Здравствуйте, Stefan. >> >> Вы писали 18 октября 2011 г., 17:20:56: >> >>>> But when we using SVN v1.7.0 (console client from the same build as >>>> server; or TortoiseSVN), we had a problem. When user (who is >>>> restricted to access /RestrictedDir) tries to make svn update on the >>>> root dir (/Sample), he got error as I described above. >>>> >>>> Updating '.' >>>> 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 >>>> >>>> SVN does not skip this directory, it creates is locally(!) as empty >>>> directory(!) and stop/fail on svn update after this. >>>> >>>> That's all. >> >> SS> Can you please clarify which versions were running on the client >> SS> and which version was running on the server when the problem appeared? >> >> SS> Both running 1.7? >> SS> Server 1.6 and clients 1.7? >> SS> Clients 1.6 and server 1.7? >> >> SS> From what you're saying the only thing I understand is that both >> SS> 1.6 client and 1.6 server was working. >> >> All for users, who have no access to restricted dir: >> >> 1. Server: SVN v1.7.0 (WANdisco build) >> Client: TortoiseSVN v1.7.0 >> >> NOT WORKING (update problem; empty directory created, update failed) >> >> 2. Server: SVN v1.7.0 (WANdisco build) >> Client: Console SVN v1.7.0 (WANdisco build) >> >> NOT WORKING (update problem; empty directory created, update failed) >> >> 3. Server: SVN v1.7.0 (WANdisco build) >> Client: TortoiseSVN v1.6.15 (Subversion v1.6.16) >> >> [!] WORKING as previous behaviour! >> >> So, the problem is really inside CLIENT interpretation of server >> statuses. Both new version of console svn.exe (svn client) and >> TortoiseSVN working incorrectly now. JC> Is it broken only for working copies that were upgraded from 1.6 to JC> 1.7, or also for new checkouts done with your 1.7 client? JC> I'm wondering if it's a bug in the upgrade code (server-excluded nodes JC> being incorrectly upgraded), or in the general handling of JC> server-exluded nodes in 1.7. Yes, you are right, it is a bug with upgrade procedure. I made an expirement: 1. Made a clean checkout to a new place on a computer of user with restricted access. Checkout was without any problem. 2. After this I tried to make svn update -- all was fine. 3. After this from my computer I made a "cross" commit (one commit includes a change to a files, where users have no access, and to a files accessed by them). I used SVN update on root directory on restricted-users -- all was fine. So, if a clean checkout (without upgrade) is made, there is no such problem. -- С уважением, Andrey mailto:and...@online-solutions.ru
