This is not the bug report you are looking for. Well not really.
-
I needed a SVN GUI client that can actually remember ssh passwords since rapidsvn can't be bothered, found rabbitSVN, and decided to see if it was what I needed.
Appears that it doesn't work on exported stuff over sftp (i.e. the working copy is on a remote machine,) so I go to look to see if it's known about.
A search for
sftp
on their issue tracker returned nothing, so go searching and find this:No support for mounted locations
RabbitVCS currently does not support mounted locations, e.g. when you access a directory over SFTP, SMB, FTP or some other protocol with a custom URI scheme. For more information see Issue #158.
I click #158, get 404'd, so I file a report:
-
@PJH It's a self-fulfilling link.
-
In other news, Archive.org's Internet Archive seems to have captured the original issue #158. It's unamazingly devoid of help.
-
@JBert said in This is not the bug report you are looking for. Well not really.:
In other news, Archive.org's Internet Archive seems to have captured the original issue #158. It's unamazingly devoid of help.
2009
Ah. Ta for that. I won't be holding my breath and will look elsewhere if I'm ever in the market for a useful GUI for SVN again. (RapidSVN would be OK if it didn't ask for your SSH password on every transaction it does, and Ubuntu dropped kdesvn a while back.)
I ended up doing what I wanted to do on the command line, and manually in a spreadsheet, since in the long run it seems to have been quicker anyway.
-
@PJH said in This is not the bug report you are looking for. Well not really.:
ask for your SSH password on every transaction it does
-
@dkf said in This is not the bug report you are looking for. Well not really.:
@PJH said in This is not the bug report you are looking for. Well not really.:
ask for your SSH password on every transaction it does
Quite. And while I do have admin to our SVN server, and it's on our side of the DMZ, I'm not willing to put a passwordless key on there that can have write access just so I can use rapidsvn.
-
@PJH said in This is not the bug report you are looking for. Well not really.:
if it didn't ask for your SSH password on every transaction it does
Sorry to hijack the topic a bit, but... Git keeps doing this to me when using SSH. I did the whole
ssh-key-add
thing and all, no dice. Maybe I have to set it to use KWallet and set it up that way or something? Anyone have any ideas?
-
You tried to replace RapidSVN with RabbitSVN? You had it coming, then!
-
@PJH said in This is not the bug report you are looking for. Well not really.:
rabbitSVN ... No support for mounted locations
There's some irony, for you.
-
@Onyx said in This is not the bug report you are looking for. Well not really.:
@PJH said in This is not the bug report you are looking for. Well not really.:
if it didn't ask for your SSH password on every transaction it does
Sorry to hijack the topic a bit, but... Git keeps doing this to me when using SSH. I did the whole
ssh-key-add
thing and all, no dice. Maybe I have to set it to use KWallet and set it up that way or something? Anyone have any ideas?You have to do a bit more than just ssh-key-add. Look here.
And yes, you have to do that in every shell session, unfortunately.
-
@Dreikin said in This is not the bug report you are looking for. Well not really.:
And yes, you have to do that in every shell session, unfortunately.
Not if you use
keychain
you don't. At least not manually.
-
@PJH said in This is not the bug report you are looking for. Well not really.:
@Dreikin said in This is not the bug report you are looking for. Well not really.:
And yes, you have to do that in every shell session, unfortunately.
Not if you use
keychain
you don't. At least not manually.I'll have to look into that.
-
@Dreikin said in This is not the bug report you are looking for. Well not really.:
I'll have to look into that.
~/.bashrc
:CERTFILES= for public in ~/.ssh/*.pub; do private=${public%.*} if [ -e $private ]; then CERTFILES="${CERTFILES} $private" fi done KEYCHAIN=`which keychain` $KEYCHAIN $CERTFILES && source ~/.keychain/$HOSTNAME-sh
Will load up any private key for which a public key is also present (and by extension, remove/rename/move the public key if you don't want the private one auto-loading.) First shell you open since boot will prompt for any passwords, subsequent ones won't.
If you have cron jobs that rely on any of those keys, simply stick this near the beginning (this is bash but same principle for anything else):
source $HOME/.keychain/$HOSTNAME-sh
and they'll work, provided you've entered the passwords previously.
-
@PJH Thanks :D I'll try to remember to remember to look for this the next time I'm fiddling around with them.
-
@PJH Cheers! Will take a look at work, though
which keychain
returns nothing on my home machine. Will look into that, probably a KDE-specific issue.
-
@Onyx said in This is not the bug report you are looking for. Well not really.:
which keychain returns nothing on my home machine.
From experience it tends not to be installed by default, and the repository it's in may need adding first.
-
@PJH Ah, read up now, I thought it should connect to your wallet (whichever one you're using), apparently not. Seems to be in Debian repos, will see on Monday.
-
@Onyx said in This is not the bug report you are looking for. Well not really.:
I thought it should connect to your wallet (whichever one you're using)
I think it's probably a wallet in its own right...