Hi,

I have gnupg-agent installed, and gpg2. When I use gpg before running
dpkg-buildpackage for some other work (like signing stuff symmetricaly)
and run dpkg-buildpackage later, it tells me: "incorrect passphrase".

However, when I use debsign instead, it works as usual and displays the
password query dialog.

I guess debsign incorrectly uses a wrong cached password here?

To work around that, I have to kill gpg-agent and restart "gpg-agent
--daemon" again.

Regards,
Eduard.

Hi!

Does this happen too if you use gpg, and then gpg2? That's what should
be happening here with dpkg-buildpackage which defaults to gpg2 if
present, compared to debsign which uses gpg.

I'd assume perhaps a local configuration problem or a weird
interaction problem between gpg, gpg2 and gpg-agent here, but not a
problem with dpkg-buildpackage in principle.

Thanks,
Guillem

Hallo,
* Guillem Jover [Fri, Dec 04 2015, 03:28:59AM]:

Oh, well, this detail is confusing. I checked with debuild, then
dpkg-buildpackage directly, assuming they are doing the same thing. But
debuild runs debsign separately unlike d-b.

Using gpg and debsign (or debuild) afterwards works.
(gpg-agent restarted)
Using gpg2 and using dpkg-buildpackage afterwards works too.
Using debsign after that works too.
(gpg-agent restarted)
Used gpg -c -a ...
dpkg-buildpackage used -> works (hm...)
debsign used -> works (hm...)

This stops making sense now. I tried more different combinations of gbp,
dpkg-buildpackage, debsign and vim (gnupg.vim plugin).

Agreed, thanks.

Regards,
Eduard.