Hi Konstantin, Thanks for the reply.
On 30/09/2011, at 5:31 PM, Konstantin Kolinko wrote: > 2011/9/30 Gavin Baumanis <gav...@thespidernet.com>: >> Hi Everyone, >> We recently created a DNS entry for our subversion repository. >> Prior to this we just use the private LAN IP address to access the repo via >> http (Apache) >> Post the change to having a hostname to use I created a new branch - and >> used the host name to do this. >> Subsequently when I perform an svn update I a now prompted for username and >> password for the named instance of our repo. >> I did some reading in the "good" book. >> and used svn switch >> (svn switch old_IP_address new_HostName_Address >> at the root of my working copy. > > It should have been "svn switch --relocate" which is very different > to usual "svn switch" (so that 1.7 introduces a separate "svn > relocate" command to lessen the confusion). > > Just for future readers. It does not seem to be a problem here. > You're absolutely correct. I did indeed use the --relocate switch - I just omitted it (accidentally) from my original post. >> svn info confirms that the repo address is now set to the hostname version >> of the URL. >> However I am still getting prompted for a username and password. >> If I enter the "usual" password - all is good... but the prompt is playing >> havoc without Continuous Integration scripts. > > What havoc? > > You should use --username and --non-interactive. > I'll give that a try - thanks. > The password can be are either > a) taken from cached auth credentials (auth subdirectory in subversion > configuration area) > b) entered interactively. > c) entered on the command line as --password. > > If you never connected that system, there may be no cached password. > > b),c) cache the password automatically, unless you use > --no-auth-cache, (and I think they wouldn't cache it without a prompt > on *nix systems where password is stored unencrypted). > > Another question is whether the server is accessed directly or through > a proxy (and you'll need a proxy password). -> servers file in > subversion configuration area. > >> Some more reading suggests that I might need to add a new authentication >> realm and users via; conf/svnserve.conf > > svnserve,conf is for svnserve, > but you are using Apache HTTPD and all authentication is handled by > Apache HTTPD. > > Subversion handles only authorization. > >> I was hoping that I might just get some confirmation that is indeed what I >> need to do - before I go "playing" with the config scripts. >> As always - a big thanks for your help. >> Gavin. > > Best regards, > Konstantin Kolinko For the purposes of helping out anyone who might visit the thread later, here is what I have done to get it working. I deleted the cached credentials from; ~/.subversion/auth/svn.simple/ I then performed svn update and entered in the correct username and password. The cached credentials were then updated (correctly) and my; scripts worked correctly. I have tried the --username / --non-interactive yet - but I will. Thanks again for the reply. Gavin.
