Re: BUG? ... 'svn update' does not save authentication information

Jeff Putsch <putsch@mxim.com> writes:

> 7 run 'svn status -u foo/test', you will get prompted for a password.

You could also just run 'svn st -u' or 'svn up' on the entire working
copy, rather than on the specific foo/test path, and you won't be prompted.

> It seems to me the update command knows everything it needs to know to put
> these two files in place as part of the update process.

Hmmmm, ponder, ponder... when you run 'svn update target',
libsvn_client sends an http REPORT request on the target's url.
Apache responds with an auth challenge, and we currently only look in
target's .svn/auth/ area for the cached data.

So this means either:

   1. try to see if there's parent dir under version control with
       cached auth data, or...

   2. as you suggest, whenever 'svn update' creates a new directory,
       the existing auth data should be installed. It may already be
       present in some context structure, or maybe it needs to be
       copied from a parent dir.

Should we file an issue on this?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 18:55:07 2002