From: Pierre Lorenzon <devel@pollock-nageoire.net>
To: spluque@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: psvn with svn+ssh protocol working copy
Date: Sat, 24 Oct 2009 21:12:15 +0200 (CEST) [thread overview]
Message-ID: <20091024.211215.193736066.devel@pollock-nageoire.net> (raw)
In-Reply-To: <87ocnwx1ab.fsf@kolob.sebmags.homelinux.org>
Hi,
I encountered similar problem with cvs instead of svn. But
since psvn is implemented following same as scheme as pcvs, I
suspect the problem to be similar. I solved it writing a piece
of code caching the password. I did not have much help on this
list. Finally I got to svn with an apache server. In this
configuration passwrd is automatically cached by the svn client
and will only be asked at the first checkout.
Regards
Pierre
From: Seb <spluque@gmail.com>
Subject: psvn with svn+ssh protocol working copy
Date: Sat, 24 Oct 2009 10:24:44 -0500
> Hi,
>
> Although I can checkout, commit and do all operations I need from a
> shell, I cannot update my working copy of a directory under SVN control
> with svn+ssh in Emacs with psvn. I get the message:
>
> svn failed:
> Network connection closed unexpectedly
>
> in the minibuffer. Checking the comments on psvn.el, I see that using
> x11-ssh-askpass would help, so I installed Debian sid's ssh-askpass
> package, and now I'm shown a graphical dialog to enter the passphrase.
> This works fine, but requires typing the passphrase with every commit or
> update.
>
> The comment in psvn.el ($Id: psvn.el 35820 2009-02-11 21:35:14Z) from
> GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.3) of
> 2009-10-23 on elegiac, modified by Debian, reads:
>
> ,-----[ psvn.el (lines: 1283 - 1292) ]
> | ;; Communicate with the subprocess via pipes rather
> | ;; than via a pseudoterminal, so that if the svn+ssh
> | ;; scheme is being used, SSH will not ask for a
> | ;; passphrase via stdio; psvn.el is currently unable
> | ;; to answer such prompts. Instead, SSH will run
> | ;; x11-ssh-askpass if possible. If Emacs is being
> | ;; run on a TTY without $DISPLAY, this will fail; in
> | ;; such cases, the user should start ssh-agent and
> | ;; then run ssh-add explicitly.
> `-----
>
> However, I do have ssh-agent running, and have also run ssh-add, but I'm
> still being presented with the dialog. Has somebody had to deal with
> this? Thanks in advance.
>
>
> Cheers,
>
> --
> Seb
>
>
>
prev parent reply other threads:[~2009-10-24 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 15:24 psvn with svn+ssh protocol working copy Seb
2009-10-24 19:12 ` Pierre Lorenzon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091024.211215.193736066.devel@pollock-nageoire.net \
--to=devel@pollock-nageoire.net \
--cc=help-gnu-emacs@gnu.org \
--cc=spluque@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).