Ah! stretch! that's why you weren't seeing the same FTBFS I was working
on (which is caused by the new gnupg, and thus right now only in sid).
I've investigated a bit on the issue, and found that gnupg is indeed
installed when installing build-essential, but only as a Recommends, and
thus it
On Wed, Aug 17, 2016 at 04:55:13PM +0200, Elena ``of Valhalla'' wrote:
> Could you please tell me how are you generating the chroot, and how it
> ends up not having any version of gnupg installed?
I can't tell for sure.
I often use tools like deborphan and debfoster to make sure that the
chroot
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
Package: src:python-gnupg
Version: 0.3.8-2
Severity: serious
Tags: patch
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)"
but it failed:
4 matches
Mail list logo
