On 2015-Apr-13, Bert Huijben wrote with possible deletions:
> >
> > Current access file contains:
> >
> > [groups]
> > proj_staff = [...]
> > proj_other = [...]
> >
> > [proj:/]
> > @proj_staff = rw
> > @proj_other = r
> >
> > [proj:/pub]
> > * = r
> > @proj_staff = rw
> >
> > [proj:/eval]
> > @proj_other =
> >
> > [proj:/group]
> > @proj_other = rw
> >
> > [proj:/group/foo]
> > foo = rw
> >
> > The problem is:
> >
> > * I can *NOT* `svn co https://...proj/pub` without authentification.
>
> For the record: I don't see anything in your config that you setup anonymous
> authentication. Even with a * = r line some operations might still need to
> know who you are, even though everybody has access to read.
What would that be? Something like this?
[sq_15s:/pub]
$anonymous = r
@proj_staff = rw
As I read the docs, this would not apply to the authenticated users,
i.e., it would be less users than thos addressed with `*`. Anyways, I
have tried this, andit makes no difference.
> For 1.8.x a checkout will retrieve inherited properties from all ancestor
> directories of where you checked out (see release notes for the new features
> that provides), so I'm not surprised that the client asks for your
> credentials if you only provide access to those other directories if a user
> is authenticated. (Not being able to read the properties is not an issue...
> But the client will try to read them, which will produce a prompt)
Well, there are no properties set on `/`, so there's nothing to
inherit.
What is the right way to make only a subdirectory accessible to the
world via `svn co`? Exporting works, so what's the point to disallow
checkout?
> If there is something on the server side related to your issue everybody
> will recommend you to upgrade to a supported Subversion release first.
Yes, well, I'm not the admin of the service I have to use. Sorry
about that.
--
http://stefan-klinger.de o/X
/\/
\
