Your message dated Mon, 04 Jul 2016 16:24:53 +0000
with message-id <[email protected]>
and subject line Bug#771011: fixed in git-remote-gcrypt 1.0.0-1
has caused the Debian Bug report #771011,
regarding git-remote-gcrypt: Fails to connect to GPG agent due to --no-tty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
771011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771011
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-remote-gcrypt
Version: 0.20130908-7
Severity: important
Tags: patch
Thanks for maintaining git-remote-gcrypt!
When attempting to connect to a remote, I get the following...
git remote update
Fetching origin
+ [ x/run/user/1000/keyring/gpg:0:1 != x ]
+ gpg --no-tty --armor --gen-rand 1 9
+ set +x
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
+ [ x/run/user/1000/keyring/gpg:0:1 != x ]
+ gpg --no-tty --status-fd 3 -q -d
gpg: anonymous recipient; trying secret key 0123456789ABCDEF ...
gpg: Sorry, no terminal at all requested - can't get input
gcrypt: Failed to decrypt manifest!
error: Could not fetch origin
I don't understand why it doesn't use GPG_AGENT_INFO ... other
programs have no trouble using it. I don't think there's any
particularly strange configuration on my part...
If I unset GPG_AGENT_INFO it prompts me directly multiple times, but
does work... if I add --use-agent it also works, so here's a patch to
try that, not sure if it has other consequences:
From 72b3ce94c2f15e77b28c4bc32a04e1e6646897f1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <[email protected]>
Date: Tue, 25 Nov 2014 14:02:11 -0800
Subject: [PATCH] Pass --use-agent to gpg in addition to --no-tty, otherwise
gpg may warn: gpg: Sorry, no terminal at all requested - can't get input
gcrypt: Failed to decrypt manifest!
---
git-remote-gcrypt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-remote-gcrypt b/git-remote-gcrypt
index 8d68669..51bf46c 100755
--- a/git-remote-gcrypt
+++ b/git-remote-gcrypt
@@ -371,7 +371,7 @@ rungpg()
# due to trying to print messages to it, even if a gpg agent is set
# up. --no-tty fixes this.
if [ "x$GPG_AGENT_INFO" != "x" ]; then
- gpg --no-tty "$@"
+ gpg --no-tty --use-agent "$@"
else
gpg "$@"
fi
--
2.1.3
live well,
vagrant
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages git-remote-gcrypt depends on:
ii git 1:2.1.3-1
ii gnupg 1.4.18-4
ii gnupg2 2.0.26-3
Versions of packages git-remote-gcrypt recommends:
ii curl 7.38.0-3
ii rsync 3.1.1-2+b1
git-remote-gcrypt suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: git-remote-gcrypt
Source-Version: 1.0.0-1
We believe that the bug you reported is fixed in the latest version of
git-remote-gcrypt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton <[email protected]> (supplier of updated git-remote-gcrypt
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 04 Jul 2016 19:18:48 +0900
Source: git-remote-gcrypt
Binary: git-remote-gcrypt
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton <[email protected]>
Changed-By: Sean Whitton <[email protected]>
Description:
git-remote-gcrypt - encrypted git repositories
Closes: 771011 827943
Changes:
git-remote-gcrypt (1.0.0-1) unstable; urgency=medium
.
Upstream:
* Taking over as upstream maintainer.
* Remove notice about repository format potentially changing.
* Implement gcrypt.gpg-args git config setting (Closes: #771011).
* Respect git config gpg.program if configured.
Thanks Christian Amsüss. (Closes: #827943)
* Don't reset the remote ID when a gcrypt remote is not available.
Thanks Sebastian Reuße. (Closes: #827943)
* Suppress bogus warning about keyid matching multiple fingerprints.
Based on work by Raphaël Droz.
Closes https://github.com/joeyh/git-remote-gcrypt/pull/2
* Add "Note to users of GnuPG version 2" section to README.rst.
See https://github.com/joeyh/git-remote-gcrypt/pull/1
.
Debian packaging:
* Drop patch containing changes by Joey Hess: incorporated in release.
- Update d/copyright accordingly.
* Patch README.rst to remove references to installation.
* Add d/links to avoid duplicate changelogs Lintian warning.
* Drop Lintian override of no-upstream-changelog.
* Update URIs in old changelog entries.
* Add a comment to d/source/lintian-overrides.
* Bump standards version to 3.9.8 (no changes required).
Checksums-Sha1:
d272e1195b7ca1e9ce571444ed126e36080fa7aa 1944 git-remote-gcrypt_1.0.0-1.dsc
fe165c7110c834f40900754b6e1441115e567f4b 23440
git-remote-gcrypt_1.0.0.orig.tar.xz
a8664b08c8b428ec52358758ac60d296e728a1e7 3136
git-remote-gcrypt_1.0.0-1.debian.tar.xz
Checksums-Sha256:
86ef64bdf3cfd1ac18d8c9cf3f7fd328311818cfef191bb28c16eb7c84eec392 1944
git-remote-gcrypt_1.0.0-1.dsc
e6ff8200845db7e3c1d187fcb3c257be9a1d7bdd7ee8b5b01e009c2ab82ec7c0 23440
git-remote-gcrypt_1.0.0.orig.tar.xz
69cd1b9446eb7ca8a048ebf192b6a24e40b02532f08a963c03b99f6936432b81 3136
git-remote-gcrypt_1.0.0-1.debian.tar.xz
Files:
3551ebd31e522360cd044d0c71f475b7 1944 vcs optional
git-remote-gcrypt_1.0.0-1.dsc
97c310931e2f1ad4ff82709e045aae49 23440 vcs optional
git-remote-gcrypt_1.0.0.orig.tar.xz
2b727e71d4801ec53d0e8ab7ceb4e160 3136 vcs optional
git-remote-gcrypt_1.0.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJXeoA8AAoJEEsEP825REVAv5MP/RkQovUw/5KTdknvKEBSmlPy
z59INRa9h/zSNUe8LGQm+9AiW/ofQxrPL62unbAAUmAl5NtaE5F9j2ueJPu63QMP
zT24F660Dwjp9lJufznXCiYdf5IH6K/WmvRWA2al+XpzDeu3+uU9p1wuKhkquIRa
UVao48LX5+1jZd4euj7zAjqkYwEIbLbZ722ISDRWGj3BOjFqRDoTJJ4wytjFHnKL
wtjAqw9mrsEx/07l9BPcQ8hU9e0pXYHlNnQZNAwHnArxWYp2pfQGGWgg4JEeyWmK
0t3VcPOionf4bob8JcKnniuEZr3qG+2dftGkvxUr5uYeLYBsgWBvV7GAN/4nHKm/
iVXGE1zcSsAFLY7wQs7uqFn5GKdJAexJ5Vfca51DE9XOqBKio5JQHWH0FZ9tCZpk
fRlu/jSIi1t+sIUEOS+8lUjDqA/YEmYAGwaGVoHQ7UC2fE36ff1PsteKEc/l8KWT
QNh8D3U/B4z/LplBQDJKat4fdu5nOslGFHF998f1Whys38yKbgankFnVB1SmqZGA
TLUFBQmy0zlteCAtttmsQ/HPPI+d3Etm20cMkIDWAozD5Xf8FB2dtWiYbwlYZDC8
MicVyVkk+iUZ400JALP2QGqsOFdmGuibpDqTp06zcifepil1XNiuQs6I1U1JdS5N
DiGh0BE8n48qVOuNaOZ5
=8hCa
-----END PGP SIGNATURE-----
--- End Message ---
