Bug#1087183: RFS: golang-github-protonmail-gopenpgp-v3/3.0.0-1 [ITP] -- high-level OpenPGP library built on top of golang crypto library

[Martin Dosch]

Dear Simon,

thanks for looking into it.

Currently the following packages depend on gopenpgp:
- go-sendxmpp
- golang-github-henrybear327-go-proton-api
- golang-github-henrybear327-proton-api-bridge
- gosop



Best regards,
Martin

Am 09.11.2024 23:13, schrieb Simon Josefsson:

From those the new gosop version requires gopenpgp v3 while the others depend on v2. For go-sendxmpp (which I also maintain upstream) I'd like to keep using v2 as I want to be able to backport for bookworm-backports. Once trixie is out I think I'll do the switch to v3. I am not involved with the other two packages. So I'd like to keep v2 for go-sendxmpp and have v3 for now. The v2 version is not deprecated by the release of v3 and is still maintained upstream.

Hi.  This builds fine and packaging looks good, so I was about to upload
this when I noticed we already have golang-github-protonmail-gopenpgp --
why doesn't it work to bump that package to v3 instead?  What packages
in Debian require the 2.8.x branch?  Can't they be made to work with 3.x
instead?

Build pipeline:
https://salsa.debian.org/jas/golang-github-protonmail-gopenpgp-v3/-/pipelines/760246

/Simon

signature.asc
Description: PGP signature