> Scott Lenser <slenser@gs104.sp.cs.cmu.edu> writes:
> > I can't reproduce it but I did manage to gather a little more info.
> >
> > It seems to get into a state were it asks for the username/passwd on
> > every operation until you type it in. The .svn/auth files are still
> > there when it is in this state and still readable by the user. Also,
> > the same working copy without modifications can work later without
> > problems so the server must be involved in the problem somehow.
> >
> > I'll let everyone know if I figure out anything more.
>
> Scott, do you think it might have to do with the fact that you run
> "svn commit" and wait for $EDITOR to pop up?
>
> I don't experience this problem, and I also don't use $EDITOR. See if
> you get the bug with "svn commit -m 'msg'", then see if you get it
> with similar changes but just "svn commit"...
>
> -K
I don't know. I'm having trouble getting it to do it now. It's very random.
It seemed like it happened more with a newer repository and I got it to do
it again when I remade the repository, but I just remade the repository and
now I can't get it to happen at all. The repository I've been making is
structured roughly like so:
code/
code/file1
code/file2
code/file3
more files in same directory
I was able to get it to happen some by committing a change to one file in the
directory. svn status seems to behave somewhat differently from the other
commands in that the other commands seem to recover easier into a state with
I no longer have to authenticate. It also fixes itself after a delay.
I can't really get it to happen enough to test whether the editor thing makes
a difference. I'm not sure why it happened so many times when I first tested
it.
Blech. I hate heisen-bugs.
- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006