Hi Andreas,

On Sun, Sep 06, 2026 at 03:05:58PM +0200, Andreas Henriksson wrote:
> Hello Adrian, Salvatore,
> 
> On Tue, Jul 14, 2026 at 10:36:29PM +0200, Salvatore Bonaccorso wrote:
> > Source: gawk
> > Version: 1:5.3.2-1
> > Severity: important
> > Tags: security upstream
> > X-Debbugs-Cc: [email protected], Debian Security Team 
> > <[email protected]>
> > 
> > Hi,
> > 
> > The following vulnerabilities were published for gawk.
> [...]
> 
> I picked up the task of handling gawk for LTS Team. As the problem is
> unfixed in unstable/testing/stable/LTS/ELTS releases I'm offering my
> assistance to NMU and fix the issues in all releases.
> 
> I'm attaching initial draft patches for backporting the relevant
> upstream commits against the unstable version. I've also prepared a
> draft bookworm (LTS) update and the backported patches are very similar
> there. The trixie version is the same as bookworm.
> I'm thus proposing we fix the issues in unstable/testing by backporting
> patches as that should give some partial confidence that they are
> correct for older releases, and postpone updating to then new upstream
> release that is available. (Once unstable/testing is done, I'm willing
> to take care of stable-proposed-update next.)
> 
> I'm also tempted at taking care of some lintian warnings while at it,
> but maybe I should resist the urge.
> 
> Please speak up if you'd like to proceed differently!

I cannot speak for Adrian, who is active and the maintainer for gawk,
but I would leave him some time to do it as he plans (the issues are
not particular serious). As you say though addressing top-town is the
right thing to do here. Start at unstable, then point release update,
then LTS can be considered.

Regards,
Salvatore

Reply via email to