SVN 1.4.3 : behaviour change when stored credential doesn't have the required rights

Hi,

I recently upgraded from 1.2.3 to 1.4.3 (on Tru64 v5.1 and Linux RHEL 3/4,
the behaviour is the same). After this upgrade I experience problems with
stored credentials.

I had a stored credential (in .subversion/auth/svn.simple) that allowed to
write to a specific branch in a specific repository. To access (or write)
other branches or repositories, this credential had no specific rights and
thus svn client was asking me for another credential (first for a new
password with the opportunity to enter a new username if not entering a
password). With 1.4.3, this is not considered as an authentication failure
giving the right to enter a new one but leads to an access failure. I need
to put --username explicitly to workaround this new behaviour.

Is it an intended change I need to live with or is it a bug ?

Thanks in advance for any help.

Cheers,

Michel

     *************************************************************
     * Michel Jouvin Email : jouvin@lal.in2p3.fr *
     * LAL / CNRS Tel : +33 1 64468932 *
     * B.P. 34 Fax : +33 1 69079404 *
     * 91898 Orsay Cedex *
     * France *
     *************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 16 22:07:50 2007