#999938 trafficserver: depends on obsolete pcre3 library

Package:
src:trafficserver
Source:
trafficserver
Submitter:
Matthew Vernon
Date:
2025-12-01 18:06:01 UTC
Severity:
important
Tags:
#999938#5
Date:
2021-11-18 11:49:08 UTC
From:
To:
Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian

#999938#20
Date:
2023-12-29 14:54:27 UTC
From:
To:
Please find attached a patch which I admit I could not test properly.

This package is fairly specialized and I'm absolutely unfamiliar with
it.  It requires some extra knowledge and right configuration in order
to expose the functionality that has to be tested.  Also, some of the
affected plugins fail to load due to #1020989.

The testsuite passes, and the server runs and loads some of the
pcre-based global plugins.  I also tested loading of the remap plugins
with a hack to workaround #1020989 (I'll follow-up there with more
details).

#999938#27
Date:
2024-01-20 18:22:49 UTC
From:
To:
Somehow, trafficserver's bookworm-security version got into unstable and the package has migrated despite this issue.
I have never seen such a thing and am copying FTP Master.

#999938#38
Date:
2025-12-01 18:04:39 UTC
From:
To:
Please note that this is fixed now and will be released with 10.2.0.