Re: [Lmuse-developer] MusE sourceforge upgraded

[Tim E. R. <ter...@ro...>]

On April 5, 2013 11:26:31 PM Robert Jonsson wrote:
> Hi Tim,
> 
> 2013/4/5 Tim E. Real <ter...@ro...>:
> <...>
> 
> > What would the command be for write access for us devs?
> 
> I think you should have gotten a mail from sourceforge about the new
> repository, no?
> 
> In any case, this should checkout the main branch:
> svn checkout --username=spamatica
> svn+ssh://spa...@sv.../p/lmuse/code/trunk/muse2
> muse2-code
> 
> Regards,
> Robert
> 
> > Thanks
> > Tim.
> 

Hm.

My SSH was not set up, no key rings. Never had to do it for a long time.

Before I would do:
svn co https://lmuse.svn.sourceforge.net/svnroot/lmuse/trunk lmuse-trunk

 and it never asked for my SF password, only when I would commit.

Now when I do:

svn checkout --username=terminator356 
svn+ssh://ter...@sv.../p/lmuse/code/trunk lmuse-trunk

 or the HTTP version:

svn checkout --username=terminator356  
https://svn.code.sf.net/p/lmuse/code/trunk lmuse-trunk

 or even attempting my old-style:

svn checkout https://svn.code.sf.net/p/lmuse/code/trunk lmuse-trunk

 it asks for my SF password *twice*. 

Worse, opening KdeSVN after the first command asked for the password
 many times (because my SSH was not set up?), and now after the other 
 commands KdeSVN asks for the password twice even though I entered
 a default keyring when asked. 
(But I didn't, I never, allow KdeWallet to store passwords.)

Is there a way to get me back to the easy way of before?
Sorry for the dumb questions. (You just knew I'd have trouble, eh?)

Thanks.
Tim.