diff options
| author | anselmi@0a9758305bef5e058dd0263fa20a27b334b482c7 <anselmi@web> | 2016-11-28 18:42:34 +0000 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2016-11-28 18:42:34 +0000 |
| commit | 38408075a330fa45a9f1fb25f6368d38a011d7c6 (patch) | |
| tree | 4097a9dc5d10b086fc253d8b0dfc347ac530f047 | |
| parent | fd8357a5f5c399fa9c0835279ef2f82bf20e4643 (diff) | |
| -rw-r--r-- | doc/forum/propellor_and_gpg2.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/propellor_and_gpg2.mdwn b/doc/forum/propellor_and_gpg2.mdwn index 85ae1709..6337e3e6 100644 --- a/doc/forum/propellor_and_gpg2.mdwn +++ b/doc/forum/propellor_and_gpg2.mdwn @@ -1,6 +1,6 @@ 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: +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 |