On 2010-09-14 09:47, bebop52 wrote: > Thank you Larry, sorry for the late reply (holidays). > I'm still struggling with the same problem. Here is the whole error- > message (I translated the German parts) commiting a Change in a > Latexfile with Emacs VC from Ubuntu 10.04:
Hi, you don't need to translate anything if you run Subversion in an English locale setting: env LANG=en_US.utf8 svn ... To find out what locales are available, run "locale -a". > """Login: <https://xyz.googlecode.com:443> Google Code Subversion > Repository > Password for »myLinuxUsername«: Login: <https://xyz.googlecode.com: > 443> Google Code Subversion Repository > Username: svn: Transmission failed (Details folllow): > svn: MKACTIVITY from »/svn/!svn/act/ > 87b61f4b-1512-4235-82d2-6541103d5e74«: Authorisation failed: Could not > authenticate to server: rejected Basic challenge (https:// > xyz.googlecode.com)""" > > I did not change anything in my > ~/.subversion/servers > file, so everything is commented out. > > In my > ~/.subversion/config > file I have something like this: > > [groups] > # group1 = *.collab.net > myProject = https://xyz.googlecode.com/svn/trunk/ > # myProject = https://xyz.googlecode.com/ did not work either What about the following? myProject = xyz.googlecode.com > ### Information for myProject: > [myProject] > # http-proxy-host = proxy1.some-domain-name.com > # http-proxy-port = 80 > # http-proxy-username = blah > # http-proxy-password = doubleblah > # http-timeout = 60 > # http-auth-types = basic;digest;negotiate #uncommenting this did not > work > # neon-debug-mask = 130 > store-plaintext-passwords = yes #don't care about secutity in this > case > username = myGoogleCodeUsername > > Authentication should use myGoogleCodeUsername instead of > myLinuxUsername and prompt me for a password (?) > So my (very basic newbie) question remains: > How do I configure subversion on Ubuntu 10.04 to be able to > authenticate to a GoogleCode Repository? > Thanks for any help. What's in the "[auth]" section of your ~/.subversion/config? You should be able to disable support for GNOME Keyring (and KDE Wallet, for that matter) altogether by specifying "password-stores" accordingly in the "[auth]" section of your config file, like so: [auth] password-stores = keychain,windows-cryptoapi http://subversion.apache.org/faq.html#plaintext-passwords http://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.layout Here's the beginning of a fresh ~/.subversion/config file. You can have svn generate one if you just move the existing ~/.subversion out of the way first: $ mv ~/.subversion ~/.subversion.keep.me $ svn ls http://svn.apache.org/repos/asf/subversion $ cat ~/.subversion/config ### This file configures various client-side behaviors. ### ### The commented-out examples below are intended to demonstrate ### how to use this file. ### Section for authentication and authorization customizations. [auth] ### Set password stores used by Subversion. They should be ### delimited by spaces or commas. The order of values determines ### the order in which password stores are used. ### Valid password stores: ### gnome-keyring (Unix-like systems) ### kwallet (Unix-like systems) ### keychain (Mac OS X) ### windows-cryptoapi (Windows) # password-stores = gnome-keyring,kwallet ### ### Set KWallet wallet used by Subversion. If empty or unset, ### then the default network wallet will be used. # kwallet-wallet = ### ### Include PID (Process ID) in Subversion application name when ### using KWallet. It defaults to 'no'. # kwallet-svn-application-name-with-pid = yes ### ### The rest of this section in this file has been deprecated. ### Both 'store-passwords' and 'store-auth-creds' can now be ### specified in the 'servers' file in your config directory. ### Anything specified in this section is overridden by settings ### specified in the 'servers' file. ### ### Set store-passwords to 'no' to avoid storing passwords in the ### auth/ area of your config directory. It defaults to 'yes', ### but Subversion will never save your password to disk in ### plaintext unless you tell it to (see the 'servers' file). ### Note that this option only prevents saving of *new* passwords; ### it doesn't invalidate existing passwords. (To do that, remove ### the cache files by hand as described in the Subversion book.) # store-passwords = no ### Set store-auth-creds to 'no' to avoid storing any subversion ### credentials in the auth/ area of your config directory. ### It defaults to 'yes'. Note that this option only prevents ### saving of *new* credentials; it doesn't invalidate existing ### caches. (To do that, remove the cache files by hand.) # store-auth-creds = no ... -- Michael Diers, elego Software Solutions GmbH, http://www.elego.de
signature.asc
Description: OpenPGP digital signature
