[pkg-gnupg-maint] gpg-error, assuan, gpgme, gnupg

[Daniel Kahn Gillmor]

Hi Andreas--

On Tue 2024-07-09 17:24:01 +0200, Andreas Metzler wrote:

> I have been so bold as to upload libgpg-error 1.50 to experimental.

thank you for this work.  I think we should move libgpg-error 1.50 to
unstable.  Would you like to do that, or would you like me to do it?

> I have also prepared libassuan 3.0.1 and gpgme 1.23.2 using separate
> fast-forwardable branches (tmp-ametz-debian/experimental
> tmp-ametz-upstream) and would appreciate review/comments.

I have taken a look at both of these now, thanks.

I think we should upload both of these packages into debian/experimental.

I can do that, if you want me to take the final publication steps, or if
you want to go ahead and do it that's also fine with me.

Before the upload to experimental, i'd modify debian/gbp.conf and
debian/control's Vcs-Git entries to refer to the debian/experimental
branch.

once they've landed in experimental, it should be pretty straightforward
to move gpgme into unstable if we hear no complaints.

Becawuse of the change in soname, libassuan will trigger a transition,
which i haven't tested extensively.  getting it into experimental should
make it more straightforaward to sort out the next steps.

> All of these are predepedencies for gnupg 2.5.

I think considering gnupg 2.5 (or 2.6) for debian would be a serious
mistake, as it will further extend the wire format schism as compared to
other OpenPGP implementations, without resolving the cryptographic
updates that we know the standard needs.

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20240801/eaabeeab/attachment.sig>