Re: https://bugs.debian.org/850269:
I'm closing this bug report against gpgme because the underlying problem
was solved in libgcrypt. There isn't really a version of gpgme which
fixes the problem (the tests do apparently use --debug-quick-random in
1.8.1, but with the updated gcrypt that won't ma
On Tue, 24 Jan 2017 01:45, d...@fifthhorseman.net said:
> to drive gpg, though. I think we do still need that test in gpgme, just
> like we'd need a higher-level test for a mail user agent that was
Agreed. Upstream commit
a98951a * tests: Use --debug-quick-random for tests
will go into 1.8.
On Mon 2017-01-23 19:21:30 -0500, Santiago Vila wrote:
>> > I wonder, however, why the tests need to generate a key at all,
>> > just to discard it after the package is built. Would not be possible
>> > to use a pregenerated key for the tests?
>>
>> gpgme exercises functionality of the GnuPG suite
> > I wonder, however, why the tests need to generate a key at all,
> > just to discard it after the package is built. Would not be possible
> > to use a pregenerated key for the tests?
>
> gpgme exercises functionality of the GnuPG suite, including key
> generation. If we were to use a pregenera
Hi Santiago--
On Sat 2017-01-21 12:21:44 -0500, Santiago Vila wrote:
> I confirm that it's lack of entroy what makes this package to fail.
>
> Since I'm using sbuild, I added this line to /etc/schroot/default/fstab:
>
> /dev/urandom/dev/random nonerw,bind 0 0
>
> then tr
Hi.
I confirm that it's lack of entroy what makes this package to fail.
Since I'm using sbuild, I added this line to /etc/schroot/default/fstab:
/dev/urandom/dev/random nonerw,bind 0 0
then tried to build this package 40 times, and I got 40 successful
builds.
I wonder
Package: src:gpgme1.0
Version: 1.8.0-3
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
gpg: /<>/lang/python/tests/trustdb.gpg: trustdb
7 matches
Mail list logo
