[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Jeff Putsch <putsch_at_mxim.com>
Date: 2002-10-09 18:42:41 CEST

Howdy,

When using a remote repository requiring authentication information, svn
seems to store authentication information under a .snv/auth directory. This
is nice because future commands will not require prompting or using
the "--username" and "--password" arguments. Unfortunately "svn update"
does not store this information in the .svn directory under newly added
directories. This makes the next svn command that operates on an item
under the newly added directory require either the "--username/--password"
option or prompting of the user. Such behavior seems inconsistent and is
fairly incompatible with using svn in scripts.

I'm using version r3316.

To reproduce this behavior:

  1 create a repository with two users that require passwords to even
     access it.

  2 put some files and directories in the repository.

  3 make sure both users are in sync with the prepostiry.

  4 have user2 add a directory and file under the new directory
     to their working copy and commit it, e.g.:

       cd wc
       mkdir foo
       echo test > foo/test
       svn add foo foo/test
       svn commit -m'add dummy dir and file, test update & passwd' foo

  5 have user1 update their working copy.

  6 check the foo/.svn/auth directory. There are no username or password
     files present.

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

Step 7 is the problem is scripts. Either I must explicitly pass username
and password information everytime I do something that touches the repository
or 'svn update' needs to be 'fixed'. I would like to have the 'svn checkout'
command be the only one that I need to pass username/password information to
and after that have the wc keep track of it for me.

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.

Thanks,

Jeff.

-- 
Jeff Putsch                       Email: putsch@mxim.com
Maxim Integrated Products        Office: (503)547-2037
High Frequency CAD Engineering
---------------------------------------------------------------------
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:43:22 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.