> Checked out revision 59.
>
> It works as expected.
>
> Some random thoughts:
> - this was indeed a bug in svn 1.3.1 (as another reply already pointed out),
> so that would be me first guess too.
> - you say that the user can't update, but if he's trying an update he must
> have already succeeded in doing a checkout. where did he get the working
> copy from then? Can you try checking out a new working copy?
> - before trying, make sure you clear svn's authentication cache (or use
> --username and --password), then you're sure which account you're using.
>
> If this doesn't succeed, please give me an exact recipe of reproduction and
> I'll try it on my Linux or Mac box.
Interesting. The user had already checked out a version (before the
addition of the authz-db), and was trying do to an update over the
top.
But it now works as advertised, so that fixed it.
Good to know: When you add authorzation, users will need to do a
clean checkout. I wonder why?
Thanks for your help!
Tankko
On 6/13/06, Lieven Govaerts <lgo@mobsol.be> wrote:
>
>
> > -----Original Message-----
> > From: Tankko [mailto:tankko@gmail.com]
> > Sent: dinsdag 13 juni 2006 18:22
> ..
> > He is not trying to check out the /trunk, he is checking out
> > /trunk/Data and /trunk/Source separately and being denied access.
> >
> > I am running svnserve, not apache, so I don't know if that
> > matters to your execute comment. I did not see anything
> > about execute permissions in the docs about the authz-db file
> > for svnserve.
> >
> > This seems like a very basic thing: give someone access to
> > only one folder in a repository, but I just can't see what I
> > am doing wrong.
> > Have other people gotten this to work (no read access!, just
> > the ability to checkout, update and commit one folder)? Is
> > so, can you post your authzfile?
> >
> Hi,
>
> what you want to do is definitely possible with svnserve 1.3.2, I can
> simulate it right here on my Windows pc.
>
> I have a repository called repos, located in c:\devel\lgo\svn\repos. It
> contains a trunk branch in which I created a folder 't'.
>
> This is my configuration for repos:
> == svnserve.conf
> [general]
> anon-access = none
> auth-access = write
> password-db = passwd
> authz-db = authz
> realm = My First Repository
>
> == authz
> [/]
> lgo = rw
>
> [/trunk/t]
> test = rw
>
> == passwd
> [users]
> lgo = lgo
> test = test
>
> I start up svnserve like this:
> C:\svn-win32-1.3.2>svnserve -d -r C:\devel\lgo\svn
>
> and then checkout my t folder (I specify username & password so I'm this
> username is used, not the cached one):
>
> C:\svn-win32-1.3.2>svn checkout --username test --password test
> svn://localhost/repos/trunk/t ./wc
> A wc\file
> A wc\test.txt
> Checked out revision 59.
>
> It works as expected.
>
> Some random thoughts:
> - this was indeed a bug in svn 1.3.1 (as another reply already pointed out),
> so that would be me first guess too.
> - you say that the user can't update, but if he's trying an update he must
> have already succeeded in doing a checkout. where did he get the working
> copy from then? Can you try checking out a new working copy?
> - before trying, make sure you clear svn's authentication cache (or use
> --username and --password), then you're sure which account you're using.
>
> If this doesn't succeed, please give me an exact recipe of reproduction and
> I'll try it on my Linux or Mac box.
>
> regards,
>
> Lieven.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 20:44:03 2006