dominic
/
oe7drt-website
1
1
Fork 0
Code Issues Pull Requests Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '62ffea3ac0'
${ noResults }
oe7drt-website/content/posts/2020/10-error-with-signed-commits/index.md

38 lines
697 B
Raw Normal View History Unescape

first commit; still need to update content/posts
2 years ago
---
title: Error with signed commits
update posts aliases; fix some dates; fix some typography - post aliases instead of redirects - some dates were wrong, fixed and create multiple aliases to not brake the old date - fix some typography like newlines on end of file
1 year ago
aliases: /posts/2020-11-14-error-with-signed-commits
first commit; still need to update content/posts
2 years ago
categories: [computerstuff]
fix tags in posts
2 years ago
tags: [git]
first commit; still need to update content/posts
2 years ago
date: 2020-11-14T23:22:42+01:00
---
For some reason my git commits failed when I re-enabled gpg signing. This is how
I finally fixed that problem.
<!--more-->
##### Add to `~/.gnupg/gpg.conf`
~~~plain
use-agent
pinentry-mode loopback
~~~
##### And add to `~/.gnupg/gpg-agent.conf`
~~~plain
allow-loopback-pinentry
~~~
##### Restart the agent
~~~console
$ echo RELOADAGENT | gpg-connect-agent
~~~
This information was found on
[d.sb/2016/11/gpg-inappropriate-ioctl-for-device-errors][1].
[1]: https://d.sb/2016/11/gpg-inappropriate-ioctl-for-device-errors