Your message dated Sun, 18 Jun 2023 19:49:33 +0000
with message-id <e1qayoz-00dczz...@fasolo.debian.org>
and subject line Bug#1000072: fixed in libapache2-mod-qos 11.74-1
has caused the Debian Bug report #1000072,
regarding libapache2-mod-qos: depends on obsolete pcre3 library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1000072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-qos
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

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 

--- End Message ---
--- Begin Message ---
Source: libapache2-mod-qos
Source-Version: 11.74-1
Done: Marcelo Jorge Vieira <me...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libapache2-mod-qos, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcelo Jorge Vieira <me...@debian.org> (supplier of updated libapache2-mod-qos 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 17 Jun 2023 20:39:16 -0300
Source: libapache2-mod-qos
Binary: libapache2-mod-qos libapache2-mod-qos-dbgsym
Architecture: source amd64
Version: 11.74-1
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Marcelo Jorge Vieira <me...@debian.org>
Description:
 libapache2-mod-qos - quality of service module for the apache2
Closes: 1000072
Changes:
 libapache2-mod-qos (11.74-1) unstable; urgency=high
 .
   * QA upload
   * New upstream version (Closes: #1000072)
   * debian/patches: Remove 01_spelling.patch; applied by upstream
   * debian/control: Replace 'libpcre3-dev' with 'libpcre2-dev'
Checksums-Sha1:
 e89d3ae8d9fcb91944097cc2e60c64631e7114cc 2096 libapache2-mod-qos_11.74-1.dsc
 fd79c159d8b62b95abc7e0fc640ed464d0e49666 1288870 
libapache2-mod-qos_11.74.orig.tar.gz
 beda714e82ea310d63c6c3b3908c467dc8626aa2 5244 
libapache2-mod-qos_11.74-1.debian.tar.xz
 596e3654d63876265192428660dcd9d6dd800a8f 465988 
libapache2-mod-qos-dbgsym_11.74-1_amd64.deb
 b696ed7de82025f0f02d0cef35496b5e041c7716 8137 
libapache2-mod-qos_11.74-1_amd64.buildinfo
 e7fa66e03cb4f292f7c826ed7e589020a93d66d2 232636 
libapache2-mod-qos_11.74-1_amd64.deb
Checksums-Sha256:
 396087c2f5bfd13d92ac22a724d1ab7c4ac26e5aa7c68fb414039641161e79ce 2096 
libapache2-mod-qos_11.74-1.dsc
 dc2ed7f8916aca05a7ae79f77d9ed433d832b352ff67bf519015edb993e07354 1288870 
libapache2-mod-qos_11.74.orig.tar.gz
 84306b85bc2923e0fce1b6aa59fcdbbb27c696fcbe171a6119c83fc799307e2a 5244 
libapache2-mod-qos_11.74-1.debian.tar.xz
 a4f954ef389d5680d6401953df759f264ecbb5e82fde076a31a8f076199c45b8 465988 
libapache2-mod-qos-dbgsym_11.74-1_amd64.deb
 9c17a8a26d934cbdd2e4c397646840a4d47f113d69a3ba121e1a81650edf07f1 8137 
libapache2-mod-qos_11.74-1_amd64.buildinfo
 0e7eee0ac8043f3115ba6cd604588ea717f4d5b095443297a64453687564659c 232636 
libapache2-mod-qos_11.74-1_amd64.deb
Files:
 9d1b2b7e66efb5b7946e36fae1dbd64d 2096 httpd optional 
libapache2-mod-qos_11.74-1.dsc
 5345bc383b8813ec006dad14b140ea1d 1288870 httpd optional 
libapache2-mod-qos_11.74.orig.tar.gz
 85a889f689c2ecc7396c1f8580816e84 5244 httpd optional 
libapache2-mod-qos_11.74-1.debian.tar.xz
 0d1803ecff4586866e6f7553077ee161 465988 debug optional 
libapache2-mod-qos-dbgsym_11.74-1_amd64.deb
 ffce19084019234065399d2c9b7ac04c 8137 httpd optional 
libapache2-mod-qos_11.74-1_amd64.buildinfo
 3586bc039181582b33541ec30d57e0d2 232636 httpd optional 
libapache2-mod-qos_11.74-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEEX659A8zSLhyNqcUJW5JO4xAFXNMFAmSPVv8RHG1ldGFsQGRl
Ymlhbi5vcmcACgkQW5JO4xAFXNMsQBAAwbJrz7S4AjDZ/X+CXsrWhKiTfPtQi9x+
j0dDiHz20UcAtE5PPYPJ+hHhpXtG9QqUoZxjC9MyIN/bQSRYhHd4vs6TzOApE6WK
t4jckFDGXgnqkNqvM1pHvbSQ5VD70pb3mXfWRsR17A2lSXPmuRB45A5Y7oEB/5qy
cE7HpY9sduRtEv4QoPzkVdO2tRiclvFyPUKIkaVWOvcdvAAAtY6/vt7E2K5Gs5or
o62KmKBP7s8u5tnYdcs2xwxMBFhkgS1nh38Yi2elH992lGShyMSKDRb4+4ULndnT
LFoiGfwo7lY4lBehQzR1aZEdDN5iTiGagKHK6VfywHock+6L9UJyb49migrpOGci
dtjqEIWuM3rcN1EfvSP8TS32cej9hwvrb/YcoEZJxPB045VTG1NKavZmHNsWv7z8
IZgI0ozC2uEGpAjli3y+3t8h1clOD4SG8TcBVrdD7Sk9XNnaj/fcyWrTO728phon
OQeh5DwZ86vkkBU2Q9EVQmLuN8aLSxSSlFkCwEovw4niMwzpMJC5suUArkjHDRbp
Ycd1/ggFvC5eSJRkz2usx4/lVUQoo4AkaWgu4qVY1C3G5vwBegfRjaVqxEOVETsb
r1eV/ga47Dcb4PXH7rfy9HHqlfgUJNI/mpykgVnHhE0m9wlFhy0ez71rs+fQeW3j
Ut1GFBBcbVw=
=aMvI
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to