summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authoranselmi@0a9758305bef5e058dd0263fa20a27b334b482c72016-11-28 18:41:48 +0000
committeradmin2016-11-28 18:41:48 +0000
commitfd8357a5f5c399fa9c0835279ef2f82bf20e4643 (patch)
treebab932bd80ad4fe3da9d2ba6386d81794a4e362b /doc
parent9abbf06c80eda52d81b8eb1ad766554c8632d059 (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/propellor_and_gpg2.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/propellor_and_gpg2.mdwn b/doc/forum/propellor_and_gpg2.mdwn
new file mode 100644
index 00000000..85ae1709
--- /dev/null
+++ b/doc/forum/propellor_and_gpg2.mdwn
@@ -0,0 +1,16 @@
+I had a problem similar to [[Key sign problem]]. Maybe in that case the fix was easy, just supplying the secret key.
+
+In my case this was a fresh install into a new Debian/sid system (so gpg2 is the default) and the failure happened during the propellor --init following the directions in the quick start at <https://propellor.branchable.com/>. During the --init I selected to create a gpg key. The message, after finally getting enough entropy and creating the gpg key was:
+ error:gpg failed to sign the data
+ fatal: failed to write commit object
+
+So it was frustrating that propellor didn't work out of the box and there were no hints what was wrong with signing commits in git (the error above is from git and doing git commit -S was enough to reproduce it).
+
+But I persevered and happened across a sort of solution. I'm sharing it here because searching for git commit failures with gpgp2 wasn't very helpful.
+
+The issue has to do with prompting for a passphrase in gpg2. If the agent is running and $GPG_TTY is set correctly you get a prompt and things will work. If the agent is not running then gpg doesn't prompt for the passphrase and the commit fails as above. Luckily I was able to try this on a Mac, which gave an agent ioctl error, which got me to this answer.
+
+Initially I was trying propellor before I installed a desktop so I didn't have the gpg agent. I'm not sure how to work around this issue without the agent but I'll keep looking for git + gpg2 help.
+
+Dave
+