stephan@jareth:~/cvs/qboard/trunk$ svn ci -m "testing gnome-keyring thingie"
config.qmake
Password for 'login' GNOME keyring:
Sending config.qmake
Transmitting file data .
So i must assume i mis-typed my login password before, which i didn't try
until the 3rd or 4th attempt because i though it wanted the password for my
SSH or PGP _key_ (since it is a keyring manager).
:-D
Killing the keyring app didn't help - it was being re-started automatically
each time i tried to commit. That behaviour _might_ go away if i unset
SSH_AUTH_SOCK in my login shell, but i haven't tried (i can't log out just
yet - too many emaces and shells configured for work mode).
Now i've got a workaround, but i'm still damned annoyed that i have to enter
my login password after i'm already logged in (it's not a sudo operation,
after all). i do a considerable of committing, so this is going to get old
really fast.
Nonetheless, THANK YOU Sebastian for the workaround!
i would recommend closing this as "uninformed/surprised user experience",
but i suspect others will soon encounter this problem and be confused by it.
In many years of using svn over SourceForge i've never had this happen, so i
was surprised as hell by it.
On Wed, Nov 4, 2009 at 12:20 AM, Sebastien Bacher <email address hidden> wrote:
>
> ignore the question about the login password the response is in the
> description
>
Actually:
stephan@ jareth: ~/cvs/qboard/ trunk$ echo $SSH_AUTH_SOCK
stephan@ jareth: ~/cvs/qboard/ trunk$ svn ci -m "testing gnome-keyring thingie"
config.qmake
Password for 'login' GNOME keyring:
Sending config.qmake
Transmitting file data .
So i must assume i mis-typed my login password before, which i didn't try
until the 3rd or 4th attempt because i though it wanted the password for my
SSH or PGP _key_ (since it is a keyring manager).
:-D
Killing the keyring app didn't help - it was being re-started automatically
each time i tried to commit. That behaviour _might_ go away if i unset
SSH_AUTH_SOCK in my login shell, but i haven't tried (i can't log out just
yet - too many emaces and shells configured for work mode).
Now i've got a workaround, but i'm still damned annoyed that i have to enter
my login password after i'm already logged in (it's not a sudo operation,
after all). i do a considerable of committing, so this is going to get old
really fast.
Nonetheless, THANK YOU Sebastian for the workaround!
i would recommend closing this as "uninformed/ surprised user experience",
but i suspect others will soon encounter this problem and be confused by it.
In many years of using svn over SourceForge i've never had this happen, so i
was surprised as hell by it.
:)
-- wanderinghorse. net/home/ stephan/
----- stephan beal
http://