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

[Roberto C. Sánchez]

Hi Andreas,

On Wed, Jan 14, 2026 at 07:28:33PM +0100, Andreas Metzler wrote:
> 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. 

I understand that I technically push without any additional permissions.
However, I wanted to err on the side of caution by making sure that the
work on older versions was welcome. On top of that, gnupg2 is rather an
important piece of software, and I don't want to cause any sort of
problems.

> Afaict most of them already exist:
> 
> remotes/origin/debian/bullseye
> remotes/origin/debian/buster
> remotes/origin/debian/stretch
> 
That's perfect. I worked from those branches locally in preparing the
packages that I just uploaded a few hours ago. I will push the branches
and tags momentarily.

> There is no jessie branch yet but
> remotes/origin/debian/jessie-security 
> exists
> 
I didn't do any update for jessie, so I don't intend to push anything
there.

> 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.)
> 
OK. That's helpful to know, but I can tell you that I simply synced the
changes that went into trixie and bookworm, so no new upstream release.

Regards,

-Roberto

-- 
Roberto C. Sánchez