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

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.

Thanks,
Jason

-- 
View this message in context: http://www.nabble.com/%22connection-closed-unexpectedly%22-and-or-%22not-authorized-to-open-root-of-edit-operation%22-tf4248974.html#a12095116
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org