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

Re: "connection closed unexpectedly" and/or "not authorized to open root of edit operation"

From: Vlad Georgescu <vgeorgescu_at_gmail.com>
Date: 2007-08-10 19:06:22 CEST

Jason Huck wrote:
>
> Rainer Sokoll wrote:
>> On Fri, Aug 10, 2007 at 07:57:01AM -0700, Jason Huck wrote:
>>
>>> behavior. The other two seem fine. I use the Berkeley DB setup. Could
>>> there
>>> be some corruption there or perhaps a write-lock issue of some sort?
>> Maybe. I've never used bdb.
>> What if you export the repo in mention and import it into a FSFS repo?
>>
>> Rainer
>>
>>
>
> Just tried that. Didn't help, but, after doing it, I realized that the
> problem has something to do with authz. I've got two groups defined, and one
> group has r/w perms on the whole repo, while the other has read-only perms
> on just one folder within the repo. Have the rules for this changed in
> recent versions of Subversion? When I make perms wide open, everything works
> normally (in both the old and new versions of the repo), but obviously I
> can't leave it that way.

One known cause of the "Not authorized to open root of edit operation"
error is issue #2712 (which has been fixed in trunk, but not yet
backported to 1.4.x):
http://subversion.tigris.org/issues/show_bug.cgi?id=2712

Is anon-access set to "read" in the repositoy's svnserve.conf file?
If it is, and you don't want to allow anonymous users, you can set it to
"none" as a workaround.

-- 
Vlad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 10 19:04:50 2007

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