Hi,
I'm just playing aroung with TextMate's Subversion bundle. I'm totally new to this, so please forgive me if I'm missing something obvious or leaving out important information.
Martin Ott's svn client is installed. svnX is installed, too, and I can browse the repository there.
In Textmate, I selected "Check Out...", entered the URL to the subversion server (after starting a VPN connection) and all the files were downloaded to my hard disk. Fine. :-)
But then I changed a file, selected "Commit" and TextMate said: svn: Commit failed (details follow): svn: Can't get password
So what am I doing wrong?
Kind regards, Tobias
On 16. Feb 2007, at 16:53, Tobias Jung wrote:
[...] But then I changed a file, selected "Commit" and TextMate said: svn: Commit failed (details follow): svn: Can't get password
So what am I doing wrong?
The various subversion commands in TextMate does not support interactive prompting of passwords.
If the repository is accessed via webdav (http) the authentication should be cached by svn automatically, but you need to give it at least once (so e.g. do a checkin via Terminal).
If the repository is accessed via ssh, you need to generate a public/ private key pair to allow login via private key (do not put a passphrase on the private key, otherwise svn will instead prompt for that password).
At 21:45 Uhr +0100 16.02.2007, Allan Odgaard wrote:
On 16. Feb 2007, at 16:53, Tobias Jung wrote:
[...] But then I changed a file, selected "Commit" and TextMate said: svn: Commit failed (details follow): svn: Can't get password
So what am I doing wrong?
The various subversion commands in TextMate does not support interactive prompting of passwords.
If the repository is accessed via webdav (http) the authentication should be cached by svn automatically, but you need to give it at least once (so e.g. do a checkin via Terminal).
If the repository is accessed via ssh, you need to generate a public/private key pair to allow login via private key (do not put a passphrase on the private key, otherwise svn will instead prompt for that password).
The repository is accessed via svn, like this: svn://servers-ip-address/projectname
I now checked in via a subversion client (SmartSVN) which worked because I provided the password there. Then I tried to commit via TextMate but it still didn't work, so obviously the authentication is not cached.
Will the public/private key pair work here, too?
Kind regards, Tobias
On 17. Feb 2007, at 18:03, Tobias Jung wrote:
The repository is accessed via svn, like this: svn://servers-ip-address/projectname
I now checked in via a subversion client (SmartSVN) which worked because I provided the password there. Then I tried to commit via TextMate but it still didn't work, so obviously the authentication is not cached.
Will the public/private key pair work here, too?
I don’t think so, since you are not using svn+ssh.
I am surprised the auth. wasn’t cached. Try checkin from Terminal instead, maybe SmartSVN gave an option to not have svn cache the authentication.
-
Allan Odgaard -
Tobias Jung