Your message dated Thu, 21 Mar 2024 16:12:47 +0000
with message-id <e1rnl27-00ctff...@fasolo.debian.org>
and subject line Bug#1000001: fixed in pgpcre 0.20190509-7
has caused the Debian Bug report #1000001,
regarding pgpcre: 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.)
--
1000001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgpcre
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: pgpcre
Source-Version: 0.20190509-7
Done: Christoph Berg <m...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pgpcre, 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.
Christoph Berg <m...@debian.org> (supplier of updated pgpcre 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: Thu, 21 Mar 2024 16:32:43 +0100
Source: pgpcre
Architecture: source
Version: 0.20190509-7
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgre...@tracker.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Closes: 1000001
Changes:
pgpcre (0.20190509-7) unstable; urgency=medium
.
[ Yavor Doganov ]
* Port to PCRE2 (Closes: #1000001).
.
[ Christoph Berg ]
* B-D on pkconf.
Checksums-Sha1:
32bb5c1860daef2f2dc868122406389e382995cd 2042 pgpcre_0.20190509-7.dsc
533d35f9fb52a2231ac7b9967579de66450f04b0 4688 pgpcre_0.20190509-7.debian.tar.xz
Checksums-Sha256:
bb92168bc6ce589cd011256d554028eec591b07a605fdb755aace519df73c054 2042
pgpcre_0.20190509-7.dsc
7da0f583b6f52ad8ae9a20393fc06cbd64c163f5adf64599d5affb5cd40ee5a3 4688
pgpcre_0.20190509-7.debian.tar.xz
Files:
2424cae2c93ffb00b49144d46dd805b8 2042 database optional pgpcre_0.20190509-7.dsc
cf47f11bc628f4890ce48dfffb4e28bf 4688 database optional
pgpcre_0.20190509-7.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmX8VU4ACgkQTFprqxLS
p65L/g//RItAuqAUBIZM/n5JKR+S4VcZ0ZZrU5jqpW7xrsJvjK+Qfq55bOBBlq3U
Ve9tXdX2zJft8/CtkEyPzm3gDfG1upF2UFcMUgp4vQF9OHyIVDd/gYiY1A08J7D2
4MbU7aW9Al55JAbPQyFvHJ9dTZN3KwO828ET9CaDh/BMw3EzR7G+MZPtVKghukG7
ECTwfjH+w3z4v8fVpxhgRXfyV93MhUCD33crC+i4MGD1whQlDXsrU2cPaJ2JxBBy
KfdrfUT25xaKeX1V+vpI/1xLPUmXiY6QWQfINynVYucEuzocp9X+Z8Sp6xJUO0Op
QapBDSS5Xn3zwhm/UDV80d6dhoELj7Bkj2tdNTjllmiHi5fdW3lcfq/GFzmr7Jlx
XqWEi0bu8wr6xcw1vw59TAaehsg+J3lVkNs3DwQSsvyFLev4qqYbTQZd6Cd97Vua
oO4aryKXM3JwsIUAIvs7tyB4hxdbgP5Dwg+jvJkMSXvxDME1H/UlBOIJ0n5qgOV1
OCYgRg15+tyd7DvXpqe/Pbim0Br1Q4DnEVTxQ65Ehg//N6NcaUPQrl6YLDyFjrAz
SQsft/O9MkgutusIv+VU4WxhRDxNQuEf75FLkFvA463Wk99vCrTOJVrZsHlhIE2I
31AWrIx3bl99ZToN9RpJvcKVek6uiw4JwqiYn0xQgJg2rROa7QA=
=72BA
-----END PGP SIGNATURE-----
pgpT_eEQHxeLA.pgp
Description: PGP signature
--- End Message ---
