Re: 1.2.2 is not ready [was: Re: svn 1.2.2 tarballs are up for testing/voting]

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

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org