<div dir="ltr">Hi,<div><br></div><div>I'm also affected by the issue reported in <a href="https://lists.gnupg.org/pipermail/gnupg-devel/2015-September/030334.html">https://lists.gnupg.org/pipermail/gnupg-devel/2015-September/030334.html</a></div><div><br></div><div>The patch supplied in #800641 includes two separate files for debian/patches, both of them coming from upstream:</div><div><br></div><div>* <a href="http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=6db18e29eb81b37ed6feb592add77d492c60fc35">http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=6db18e29eb81b37ed6feb592add77d492c60fc35</a></div><div>* <a href="http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=bd6f80061a7f7dd8831a2ce989bbd47f46a195bc">http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=bd6f80061a7f7dd8831a2ce989bbd47f46a195bc</a></div><div><br></div><div>Please apply this patch to the package, as for people affected by this issue, it basically makes it impossible to verify signatures.</div><div><br></div><div>In the meantime, for anyone affected by this issue, the last version that was compiled without GCC5 works, and can be obtained from <a href="http://snapshot.debian.org/package/gnupg/1.4.19-3/">http://snapshot.debian.org/package/gnupg/1.4.19-3/</a></div><div><br></div><div>Thanks!</div></div><div dir="ltr">-- <br></div><div dir="ltr">Cheers,<div>Marga</div></div>