Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
http://qa-logs.debian.net/2020/10/27/python-gnupg_0.4.6-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

I've tried, but I can't reproduce this test failure elsewhere, either
during the build of the package nor for the standalone source code, so
I'm lowering the severity.

One thing that makes me suspicious is that the failures are when running
the tests with python 3.8, while the new 3.9 is run earlier and ends
with a success: this would make me think about a failure to run the
tests twice in a row, but even that is running correctly when I try it
locally.

If anybody else is able to reproduce this and can explain how I'd be
happy to investigate more.

I've tried, but I can't reproduce this test failure elsewhere, either
during the build of the package nor for the standalone source code, so
I'm lowering the severity.

One thing that makes me suspicious is that the failures are when running
the tests with python 3.8, while the new 3.9 is run earlier and ends
with a success: this would make me think about a failure to run the
tests twice in a row, but even that is running correctly when I try it
locally.

If anybody else is able to reproduce this and can explain how I'd be
happy to investigate more.