unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: git push via VC failure
Date: Mon, 30 Jul 2018 19:20:27 +0200	[thread overview]
Message-ID: <87wotcvdwk.fsf@gmx.net> (raw)
In-Reply-To: <CAM-tV-9oEXfqepH1pG=xVS0yXXq-Lz5RBOUuuvWFSRGJFcHKJg@mail.gmail.com> (Noam Postavsky's message of "Mon, 30 Jul 2018 13:09:41 -0400")

On Mon, 30 Jul 2018 13:09:41 -0400 Noam Postavsky <npostavs@gmail.com> wrote:

> On 30 July 2018 at 08:52, Stephen Berman <stephen.berman@gmx.net> wrote:
>
>> I've gotten this on two different GNU/Linux systems, one does not have
>> ssh-askpass installed, the other does but it is in /usr/libexec/openssh;
>> so does VC really require ssh-askpass directly in /usr/libexec?  If so,
>> I guess I could symlink it there, but this seems suboptimal.  Again, in
>> both systems 'git push' from the shell succeeded, so git itself seems to
>> be configured correctly and ssh-askpass doesn't seem to be required.  Or
>> is there some other reason for the failure in VC?
>
> Are you using ssh-agent, and are SSH_AGENT_PID and SSH_AUTH_SOCK set
> in your shell but not in Emacs?

Ah, that must be it.  Thanks for calling it to my attention.

> I have written the ssh-agency package which tries to find the correct
> values for those environment variables automatically. Originally it
> was written for magit on w32 systems, but it turns out to be useful on
> GNU systems as well. And it should be usable for vc-git, it's just a a
> matter of arranging to have `ssh-agency-ensure' called before 'git
> push' is run.

Thanks for the pointer, I'll give it a try.

Steve Berman



      reply	other threads:[~2018-07-30 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 12:52 git push via VC failure Stephen Berman
2018-07-30 17:09 ` Noam Postavsky
2018-07-30 17:20   ` Stephen Berman [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=87wotcvdwk.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).