Source: python-gnupg
Version: 0.4.1-1
Severity: normal

Since I've turned the package back to use gpg by default (now pointing
to gnupg 2.1) the option to use urandom for key generation doesn't seem
to do anything, and thus running the package tests (e.g. at build time)
can take a lot of time (easily hours), depending on the entropy
availability on the machine where it is built.

Keeping the severity normal because Debian infrastructure has been able
to build the package (from a source-only upload) and users are probably
also able to build it as long as they don't set a timeout.

Reply via email to