Carlos Henrique Lima Melara wrote:
> Hi,
>
> On Thu, Feb 05, 2026 at 07:02:11PM +0000, Moritz Mühlenhoff wrote:
> > On Fri, Jan 30, 2026 at 03:20:32PM -0300, Matheus Polkorny wrote:
> > > On Fri, Jan 30, 2026 at 09:27:12AM +0000, Moritz Mühlenhoff wrote:
> > > >
> > > > For Wireshark we had moved to a setup where we are following
> > > > the upstream LTS releases for as along as they are supported,
> > > > so we should rebase to 4.4.13 instead.
> > >
> > > Ok. I updated the MR with a new upstream LTS version:
> > > https://salsa.debian.org/debian/wireshark/-/merge_requests/6
> > >
> > > And uploaded also a new upstream/trixie branch
> >
> > Looks good, please upload to security-master.
>
> I was going to sponsor the upload but spotted an API/ABI breakage in the
> upstream point release [1]. ws_base32_decode() was removed from
> wireshark due to license problems [2], the 4.6.x reintroduced the symbol
> [3] but removed the function code (basically rendering the function
> useless but keeping the ABI stable). There were reports [4] of issues
> upstream concerning windows plugins, there seems to be no other packages
> using this symbol in Debian, but people using third party plugins or
> software with Debian stable can be impacted. Should we wait upstream
> answer our ping [4] in there before moving forward with the upload?
I think local Wireshark plugins to be run with a Debian-packaged
Wireshark are quite a fringe scenario, I don't think we need to hold
back for it? If they fix this in 4.4.x going forward we'll pick it up
with the next rebase, but I don't think we need to strictly wait for it?
Cheers,
Moritz
