Thanks for your report. This doesn't come completely unexpected: I knew that python-gnupg wasn't going to build as-is with gnupg pointing to gnupg2.1 (#834514), and in the last few days I've been working on a fix, which is currently building locally, but wouldn't build on a buildbot for lack of entropy.
I'm a bit more surprised by the specific failure: while gnupg is not essential, installing build-essential in a chroot where it wasn't available did install it, so AFAIK it should be available (altough in version 2.1) Manually forcing the removal of gnupg afterwards did indeed result in the error you mentioned, among a number of others, but I'm not sure how such a situation would end up happening. (The version I'm currently working on does add an explicit dependency on gnupg1, but I was planning to remove it by the time #834514 is fixed upstream) Could you please tell me how are you generating the chroot, and how it ends up not having any version of gnupg installed? -- Elena ``of Valhalla''
