Sorry Senthil, my build was wrong, as stsp kindly pointed out to me.
I still had a --disable-shared in the builds of some deps that I forgot to
remove, so Subversion automatically switched to --disable-shared mode (there
was no error that --with-gnome-keyring can't work like that).
So, I removed all of the --disable-shared things and made sure that libtool
can't find any other packages to accidentally link to: I removed all
packages (dev and non-dev) of apr, apr-util and neon, which I'm building
manually. (sqlite is installed by package, not building it manually)
*now* I rebuilt everything, and now the Gnome Keyring works! :)
... But I'm still noting two-odd things:
1) My current build still asks for the Gnome password twice even after I
said I wouldn't store it at all:
[[[
$ ./gnome-keyring-check.sh.txt
svn, version 1.7.0 (dev build)
compiled Apr 25 2009, 01:01:54
Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository access (RA) modules are available:
* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
Password for 'login' GNOME keyring: ## entering wrong gnome password
Authentication realm: <svn://localhost:3690> norealm
Password for 'neels': ## entering correct svn password
Password for 'login' GNOME keyring: ## entering wrong gnome password
-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:
<svn://localhost:3690> norealm
can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.
You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/neels/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)? no
Password for 'login' GNOME keyring: ## entering wrong gnome password
Password for 'login' GNOME keyring: ## entering wrong gnome password
]]]
2) I encountered the situation where a previous 1.6.1 run already had a
Subversion password stored in the Keyring. So it looked like a new
application tried to access another application's password.
Thus I got a GUI window from Gnome, saying:
[[[
The application 'Subversion' (<bin path>) wants to access the password for
'network password' in the default keyring. -- Deny / Allow Once / Always Allow
]]]
It took me a while to figure out that it wasn't talking about my wireless
network password. No, Subversion stores the password in the Gnome Keyring
under the name 'network password'.
So,
2a) Gnome still pops up another GUI that probably needs to be in text mode
in case no Gnome is running, and
2b) It should probably be called "Subversion passwords" instead of "network
password".
(The keyring was in this case already unlocked, so no passphrase was asked)
It stored the password successfully once I allowed access to the "network
password".
To reproduce, move your binary to a different location and run again (I guess).
So, all is well, with a few but's.
Sorry for bothering with broken builds. I suck at sorting out builds, too :P
Note to self: remember "ldd `which svn`".
~Neels
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1899930
Received on 2009-04-25 02:03:24 CEST