Yuriy M. Kaminskiy
yumkam at gmail.com
Sun Jun 4 02:36:16 CEST 2017
On 03.06.2017 17:32, Yuriy M. Kaminskiy wrote:
> On 31.05.2017 04:12, NIIBE Yutaka wrote:
>> "Yuriy M. Kaminskiy" <yumkam at gmail.com> wrote:
>>> When I tried to rebuild gnupg2 2.1.21-2 debian package from
>>> experimental in pbuilder, I got a number of sigsegv's from scdaemon
>>> while running tests:
> And, finally, (likely) culprit: after I backed out
Oops, sorry *this* was false positive - I just ran wrong version of code
(without scdaemon fixes). With scdaemon fixes applied and
skip-missing-signing-keys patch removed test-suite still freezes.
So, this patch is NOT guilty, and culprit is NOT found :-|
I tried disabling *other* potentially related debian patches
(dirmngr-idling/*, gpg-agent-idling/*), and still no result - once
scdaemon fixes applied, testsuite freezes in "plain-2" test.
I re-verified that gnupg2_2.1.20-3 builds and passes test-suite without
problem in same environment, with or without scdaemon fixes applied (but
it apparently never invoked scdaemon during test-suite, as unfixed
scdaemon would always sigsegv in this environment).
> test-suite passed without problems. So, this debian-specific patch
> apparently conflicts with some changes in 2.1.21 (and it was not
> noticed, as it was masked by scdaemon silent crashes).
> Environment: debian jessie/i386
> cowbuilder(->pbuilder(->chroot)), with also jessie/i386.
> Libraries used for build:
> 1) libassuan-dev [2.4.3-2~bpo8+1 (jessie-backports)]
> 2) libassuan0 [2.4.3-2~bpo8+1 (jessie-backports)]
> 3) libgcrypt20-dev [1.7.6-1~bpo8+1 (jessie-backports)]
> 4) libgpg-error-dev [1.26-2~bpo8+1 (jessie-backports)]
> 5) libksba-dev [1.3.5-2~bpo8+1 (jessie-backports)]
> 6) libksba8 [1.3.5-2~bpo8+1 (jessie-backports)]
> 7) libnpth0 [1.3-1~bpo8+1.1~local1 (jessie-local)]
> 8) libnpth0-dev [1.3-1~bpo8+1.1~local1 (jessie-local)]
>>> With patch below, it just freezes at
>>> === cut ===
>>> PASS: tests/openpgp/decrypt-unwrap-verify.scm
>>> Checking signing with the default hash algorithm
>>> > plain-1 plain-2 <<< [here]
>>> === cut ===
>>> Have no idea why.
>> I don't know what's going here. Let's see...
More information about the Gnupg-users