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

anon-access is killing me!

From: Gre7g Luterman <gre7g.luterman_at_gmail.com>
Date: Mon, 25 Aug 2008 12:24:09 -0600

Long time fan of TortoiseSVN, first time poster...

Over the years, I've set up almost a dozen different svn repositories on my
Ubuntu box that I serve with svnserve. In each, I've required authorized
access for both read and write privileges, until today.

Today, I made a new repository that I'd like to allow anyone to read, but
require a user/pass to make changes. So, the [general] section of my
conf/svnserve.conf includes:

anon-access = read
auth-access = write

I connected to this repository with TortoiseSVN and did a check-out. Since
no autothorization was required, it didn't ask me for a user/pass. Then I
added files and tried to do a commit.

Instead of asking me for a password now, it just gives me:

Error: Commit failed (details follow):
Error: Authorization failed

Grr. Yes, I know I need to enter my user/pass, but how do I convince
TortoiseSVN to ask me for them? Since anonymous access is okay, it doesn't
think of this on its own.

I'm connecting with WindowsXP Home. Admittedly, my TortoiseSVN is only
1.4.7, and I can upgrade if this has been patched in a later version.

I even tried specifying my user name in the check out (by saying
svn://<user>@<serverpath>) but that didn't change anything.

The workarounds I can see are to:

1) turn off anonymous access temporarily -- which will only defer problems
until the next person needs to check in files

2) create an anon user with read-only rights -- not preferred since it is
one more thing I need to communicate to peopl before they can access

Any ideas? Thanks in advance!

Received on 2008-08-25 20:24:18 CEST

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