1 |
I now have this: |
2 |
|
3 |
$ git pull --rebase gentoo master |
4 |
remote: Enumerating objects: 1358, done. |
5 |
remote: Counting objects: 100% (1358/1358), done. |
6 |
remote: Compressing objects: 100% (90/90), done. |
7 |
remote: Total 1816 (delta 1268), reused 1358 (delta 1268), pack-reused 458 |
8 |
Receiving objects: 100% (1816/1816), 674.35 KiB | 1.74 MiB/s, done. |
9 |
Resolving deltas: 100% (1297/1297), completed with 491 local objects. |
10 |
From https://github.com/gentoo/gentoo |
11 |
* branch master -> FETCH_HEAD |
12 |
775c75ac491..1eb533aad99 master -> gentoo/master |
13 |
First, rewinding head to replay your work on top of it... |
14 |
Applying: CATEGORY/PACKAGE: new ebuild / new package |
15 |
error: gpg failed to sign the data |
16 |
fatal: failed to write commit object |
17 |
|
18 |
Seems good, except for that ugly fatal message. Should I worry about it? |
19 |
|
20 |
Note that both gpg --version and gpg2 --version show the same version number (2.2.10). |
21 |
|
22 |
Of course I defined: |
23 |
|
24 |
$ git config --local user.signingkey 0xLONG-GPG-KEY |
25 |
$ git config --local commit.gpgsign 1 |
26 |
$ git config --local push.gpgsign 1 |
27 |
|
28 |
I can see the key in .git/config, as well as with: |
29 |
|
30 |
$ gpg --list-secret-keys --keyid-format LONG |
31 |
|
32 |
Thanks, |
33 |
|
34 |
Vieri |