I'm running 1.0.0, compiled from source on Debian. I don't know enough about
scripting to know how to write a script - all I've done is compile/install
it (I was having different trouble with the testing package - it would take
a few minutes for it to respond to any remote connection over svn://, even
if the remote connection was from localhost), start svnserve -d -r
/usr/local/svn, and svnadmin create /usr/local/svn. And then set up the
password file and the conf file.
I have a custom-compiled apache2 installation also, btw, though I don't know
how that could be causing any problems since I'm currently not trying to use
mod_dav_svn. (Which is my next attempt . . .)
I could try providing step-by-step instructions after "install it", though.
lesse if I can get this happening again.
svnadmin create /usr/local/svn/mv
( edit /usr/local/svn/users to contain [users] \n username = password \n)
( edit /usr/local/svn/mv/conf/svnserve.conf to contain [general] \n
password-db = ../../users \n)
svnserve -d -r /usr/local/svn
svn import mv svn://localhost/mv
. . . and grr. Now it seems to be working - sort of - it's back to the
five-minute delay-before-doing-anything. At least, it takes five minutes to
authenticate my password, during which it uses 0% CPU.
Great. New bug now.
It works - it just takes approximately five minutes to verify my password.
Right now I'm trying to import - it takes five minutes to realize my old
password didn't work, then prompts me for the password for my current user.
I'm using a different username on subversion, so I hit enter and it takes
another five minutes. Then it prompts me for my username and password, which
I type in, and . . . it takes another five minutes.
And then works fine.
What five-minute delay am I missing? And why am I the one who keeps ending
up with weird bugs? :P
----- Original Message -----
From: "Tobias Ringström" <firstname.lastname@example.org>
To: "Ben Wilhelm" <email@example.com>
Sent: Thursday, March 04, 2004 8:58 AM
Subject: Re: password-db failure?
> Ben Wilhelm wrote:
> > It does exist - as I said, without the password-db line - that one
> > line - it works fine. Imports and everything, if I add anon-access =
> > I just don't want to leave it completely unprotected, y'know?
> > Without password-db, everything works (to the limit that it can, without
> > password-db.) Anon access checkout works, checkin works, import works.
> > With password-db, it says it can't find the repository. Nothing else
> > changes.
> > That's what's confusing me. At the least, it's a bad error message. At
> > worst, it's a bug.
> This sounds very strange. What version are you running? Can you
> reproduce it and post a reproduction recepie as a script that we can
> just run?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Mar 4 20:14:29 2004