Agreed, I'll let you know if I see the problem again. Thanks
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #120.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/120#event-944454134___
Rpm-maint mailing list
hey @pmatilai - i'm using fedora 24 with:
```
$ rpm -q rpm rpm-sign gnupg2 gnupg
rpm-4.13.0-1.fc24.x86_64
rpm-sign-4.13.0-1.fc24.x86_64
gnupg2-2.1.13-2.fc24.x86_64
gnupg-1.4.21-1.fc24.x86_64
```
my DISPLAY variable is unset but my `TERM` is `screen-256color`. What is odd
that I am trying to
OTOH the pinentry bug doesn't explain behavior change with different %_gpg_name
value. Can you reproduce the problem if you explicity set TERM to something, eg
`TERM=xterm rpm --addsign ./grub2-2.02-0.38.fc25.dusty.x86_64.rpm`
--
You are receiving this because you are subscribed to this
Okay, this is actually a bug in pinentry, see
https://bugs.gnupg.org/gnupg/issue2452
With that info I can also reproduce the behavior by forcing an empty
environment:
```
error: gpg exec failed (2)
[pmatilai@sopuli rpm]$ cp ~/Downloads/xfce4-terminal-0.8.2-2.fc25.x86_64.rpm
/tmp/; env -i
That's strange. I'm not able to reproduce that, and it doesn't seem to be about
actual length either since my name is longer and I always had this in my
~/.rpmmacros:
`%_gpg_name Panu Matilainen `
What version of rpm, gpg and what distro are you using?
--
You are
In the example shown
[here](https://github.com/rpm-software-management/rpm/blob/1ce844ab263bf49ee6d5145ed09e73f2c17924cc/doc/rpmsign.8#L67)
I should be able to specify a macro of `%_gpg_name Dusty Mabe
` and be able to use that. Unfortunately, i get this error
instead: