all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: git push via VC failure
Date: Mon, 30 Jul 2018 13:09:41 -0400	[thread overview]
Message-ID: <CAM-tV-9oEXfqepH1pG=xVS0yXXq-Lz5RBOUuuvWFSRGJFcHKJg@mail.gmail.com> (raw)
In-Reply-To: <87sh40evhu.fsf@gmx.net>

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?

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.

Or if you expect to get a password prompt every time, then I think
it's just that Emacs is not using a pty when running 'git push', which
causes git (or ssh?) to use ssh-askpass instead.



  reply	other threads:[~2018-07-30 17:09 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 [this message]
2018-07-30 17:20   ` Stephen Berman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM-tV-9oEXfqepH1pG=xVS0yXXq-Lz5RBOUuuvWFSRGJFcHKJg@mail.gmail.com' \
    --to=npostavs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.