Bug#760102: gnupg 2.0.27 in debian unstable, with some fixes that we might want to consider for jessie

[Daniel Kahn Gillmor]

hey debian gnupg folks--

I've uploaded gnupg2 2.0.27-2 to unstable.  This brings unstable closer
to upstream (most of debian/patches is removed), and includes some
debian-specific attempts to address some problems that might be relevant
for a wider userbase.

The most important changes included in 2.0.27-2 that i'd like people to
look at are:

https://anonscm.debian.org/cgit/pkg-gnupg/gnupg2.git/commit/?id=154d606ed022cee8ef1b86183f6a444d198a8a39

   This proposes a workaround for GNOME keyring hijacking gpg-agent,
   including shipping /usr/bin/gnome-keyring-unhijack-gpg-agent as an
   interim measure, and suggesting its use if a hijack is detected.
   (#760102 and #753163)

https://anonscm.debian.org/cgit/pkg-gnupg/gnupg2.git/commit/?id=be070c6017fede8dbd3549c0071e3f0ac44bebcd

   This imports NIIBE's upstream fix to not choke on repeated copies of
   unknown key material (#787045)

If folks can take a look at these changes and let me know what you think
about them, that would be great.

In particular, i want to consider the two changes above for a stable
point release, so if you see any concerns about either of them, please
say something.

      --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20150528/8e8c8716/attachment.sig>