[pkg-gnupg-maint] Suitability of LTS (and ELTS?) changes for inclusion in salsa.d.o project

[Andreas Metzler]

On 2026-01-09 "Roberto C. Sánchez" <roberto at debian.org> wrote:
> Hello gnupg2 maintainers,

> I am working on an update of gnupg2 targetting bullseye (and will also
> end up soon working on updates for buster and stretch). Would you accept
> the changes that I make on the respective branches in your repo?

> If so, then I will push the changes on the relevant branches
> (debian/bullseye, etc.). If you prefer that I exclude some (e.g., buster
> and stretch), please let me know. Also, if you prefer that I not push
> work in your repo, please let me know that as well.

> For the work that you are willing to have pushed in your repo (if any),
> do you prefer that I push directly? (I will only push after having
> backported, tested, etc., and making sure everything is ready.) Or do
> you prefer that I submit my changes via MR?

Hello Roberto,

given that gnupg lives in salsa's Debian namespace please push to the
respective branches. Afaict most of them already exist:

remotes/origin/debian/bullseye
remotes/origin/debian/buster
remotes/origin/debian/stretch

There is no jessie branch yet but
remotes/origin/debian/jessie-security 
exists

In the unlikely event that you choose to package a new upstream 2.2.x
version  you would need to set
upstream-branch = upstream-2.2
in debian/gbp.conf
to avoid messing up sid's upstream branch (based on 2.4.)

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'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20260114/68eeff90/attachment.sig>