SteveKing wrote:
> Mark Phippard wrote:
>
>> OK, I just built 1.2.2 from the zip and did this test. I get the
>> same thing as you, except svn crashes at the end when I do it.
>
>
> It also crashes for me, but only if I have my auth data already
> stored. If I clean the auth cache on my harddrive, then I just get an
> 'authorization failed' without a crash.
> And it also only crashes if I *don't* give --username and/or
> --password on the commandline.
>
> I've sent Branko my auth folder via PM (hope he doesn't try to crack
> the password :) ) to try. But I'm not even sure that will help: the
> auth data is encrypted now and I think windows won't let him decrypt
> it (haven't thought of that before I sent him the zip file).
>
>> I thought I would try svn st -u after to see if that had the
>> problem. It seems to work OK.
>
>
> I've tested the 'svn st -u' with the 1.2.2 and that works. Ben has
> fixed that really good.
>
> I've just built svn from HEAD, and it too crashes.
>
> So I'll try to get together what we found out so far:
>
> $ svn lock file
> with client 1.2.1 up to 1.2.2 (and HEAD) can crash if
> - the lock is done to a http server 1.1.1 (like tigris.org)
> - the user has commit access to the repository
> - the user has the auth data cached on disk
> - no --username and/or --password is given on the command line
With write access to the tsvn repo, I can confirm this -- both 1.2.2 and
trunk.
Stefan, thanks, you can revoke my write access now.
Anyway, I think doesn't make sense to ship 1.2.2 with such a bug.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 11 22:09:10 2005