[pkg-gnupg-maint] Bug#1022702: gnupg: Migrating packaging from 2.2.x to "stable" 2.3.x

[Andreas Metzler]

Control: retitle -1 gnupg: Migrating packaging from 2.2.x to "stable" 2.4.x

On 2022-10-24 Hideki Yamane <henrich at iijmio-mail.jp> wrote:
> Package: gnupg
> Severity: wishlist

> Dear Maintainer,

>  I've noticed that now upstream says 2.3 branch is "stable" series,
>  not development ones since 2.3.5.
[...]

Hello,

I have spent a little bit of effort on packaging 2.4.0. I have pushed
this to salsa (sans tags) into 3 temporary branches that could be
fast-forwarded:
tmp-ametzler-pristine-tar   --ff->   pristine-tar
tmp-ametzler-upstream       --ff->   upstream
tmp-ametzler-v2.4           --ff->   debian/experimental

(Merge request does not really seem to make sense for something that
requires updating 3 branches at the same time.)

However there are some open questions:
* The Debian package features some non-trivial patches that need to be
  doublechecked. The gpg-agent-idling patches were already disabled by
  Christoph in the 2.3.1-1 upload.
* Policy. There seems to be dissens between gnupg and the IETF openpgp
  workgroup. (See
  https://lists.gnupg.org/pipermail/gnupg-devel/2022-December/035183.html
  ff) I do not understand the whole thing well enough to judge the
  benefits of gnupg's approach, however dissens is evident from reading
  the thread. I amn not sure whether I could make sense for Debian to
  wait for thing to play out.

cu Andreas


-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'