all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Fredrik Nyqvist <fredn@posteo.net>
Cc: 40820@debbugs.gnu.org
Subject: bug#40820: 28.0.50; vc: vc-push requires ssh-askpass to enter key password
Date: Thu, 22 Oct 2020 16:49:58 +0200	[thread overview]
Message-ID: <87pn5ajox5.fsf@gnus.org> (raw)
In-Reply-To: <87pnbxdkqw.fsf@posteo.net> (Fredrik Nyqvist's message of "Fri, 24 Apr 2020 16:24:55 +0200")

Fredrik Nyqvist <fredn@posteo.net> writes:

> 0. To get the error message at step 6, make sure that ssh-askpass is
> not installed on the system.
> 1. Start Emacs emacs -Q
> 2. Edit a version controlled file (in this case git is used)
> 3. Do vc-next-action (C-x v v)
> 4. Enter a commit message and then press: C-c C-c
> 5. Try to push the file: C-x v P
> 6. Emacs now tries to launch ssh-askpass to enter the password. An error
> message will be shown if ssh-askpass is not installed on the system:
>
> ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory

I don't think Emacs calls ssh-askpass directly -- it just leaves all
that stuff up to the OS setup, I think?

In any case, I was unable to reproduce this on Debian, presumably
because there's a lot of passphrase caching going on.  Without it I'm
just getting:

Running "git push"...
git@github.com: Permission denied (publickey).^M
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

So do you have a more complete recipe for how to reproduce this bug?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-10-22 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 14:24 bug#40820: 28.0.50; vc: vc-push requires ssh-askpass to enter key password Fredrik Nyqvist
2020-10-22 14:49 ` Lars Ingebrigtsen [this message]
2020-10-27 20:05   ` Fredrik Nyqvist
2020-10-28  9:22     ` Lars Ingebrigtsen

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=87pn5ajox5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=40820@debbugs.gnu.org \
    --cc=fredn@posteo.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.