[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Error updating projects without full access rights

From: Marco Maccaferri <macca_at_maccasoft.com>
Date: Thu, 11 Dec 2008 10:17:50 +0100

Hi.

With Subversion 1.5 I get errors when I try to update projects where
some source file was renamed or moved. My user doesn't have full read
access to the repository, I can access only specific projects, whenever
svn encounters a moved file it attempts to request OPTIONS the
repository root failing with 403 Forbidden because I don't have access
to it.

The repository is structured like this:

https://svn.server/svnroot/project/trunk/plugin1

I have read/write access to plugin1 but not to the parent directories.
Whenever a file is renamed I get an OPTIONS error accessing
https://svn.server/svnroot.

With svn 1.4 it was working well, however I can't say if it is an issue
on the client or server side because I was aware of problem only after
both were updated to svn 1.5. I can say that using svn from the command
line I can check-out the projects without problems, using svnkit (with
Subclipse in my case) I can't even check-out the projects with
refactorings, so maybe the issue is related to the client side.

Is there an option I can set to prevent the access to the repository
root when not needed ?

Regards,
Marco.

-- 
Marco Maccaferri
Software Consulting, Design and Development
http://www.maccasoft.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=982741
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-11 10:18:52 CET

This is an archived mail posted to the Subversion Users mailing list.