[pkg-gnupg-maint] Bug#1022702: I volunteer to maintain GnuPG and friends in the long-term

[NIIBE Yutaka]

Hello,

I'd like to help the packaging of GnuPG and its friends in Debian, in
the long term.  I am a developer of the GnuPG team, and DD who maintains
scute in Debian.  I joined the team in 2011, then, mainly working for
smartcard support.

I don't think I can help solving the policy issue which Andreas Metzler
addressed.  Rather, I'm afraid that I will make the situation more
complicated and unsolvable, if I will try to solve something political
by myself.

So, I should work for the parts where there are no conflicts of policy
(between GnuPG and IETF specification thing).

For the packaging work, I think that we should value current Debian
specific changes, so that Debian users will see less surprise.  We need
to maintain Debian specific changes (for foreseeable future, at least).

Here are some topics of Debian specific changes.

- Debian packaging of GnuPG has its specific preferences:
  debian/patches/update-defaults/

- ... and default keyserver choice:
  debian/patches/Use-hkps-keys.openpgp.org-as-the-default-keyserver.patch

- And for the specific keyserver, there are local changes:
  debian/patches/import-merge-without-userid/

And the change of upstream which should not be introduced for Debian
users:

- Upstream deprecates systemd support, which was originally introduced
  in Debian version.  Perhaps, we will need a Debian local patch for
  this.


Today, I cloned libgpg-error, libassuan, npth, and gnupg2 from
salsa.d.o.

I found that we have an issue of build for x86_64-w64-mingw32.  In the
upstream, we maintain a local change of libtool to change shared library
name for 64-bit version (so that users can see less problem when
installing 32-bit version and 64-bit version at the same time).  In the
current Debian build process, the local change of libtool is ignored.
IIUC, it's not intentional.

Let me start by fixinig this problem (of libgpg-error) at first.
--