Your message dated Fri, 01 Sep 2023 15:04:28 +0000
with message-id <e1qc5he-009dew...@fasolo.debian.org>
and subject line Bug#999992: fixed in pike8.0 8.0.1738-1.1
has caused the Debian Bug report #999992,
regarding pike8.0: 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.)


-- 
999992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pike8.0
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: pike8.0
Source-Version: 8.0.1738-1.1
Done: Bastian Germann <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pike8.0, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <b...@debian.org> (supplier of updated pike8.0 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: SHA512

Format: 1.8
Date: Tue, 22 Aug 2023 11:50:42 +0000
Source: pike8.0
Architecture: source
Version: 8.0.1738-1.1
Distribution: unstable
Urgency: medium
Maintainer: Magnus Holmgren <holmg...@debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 999992
Changes:
 pike8.0 (8.0.1738-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop pike8.0-pcre (Closes: #999992).
Checksums-Sha1:
 321a914b3e2fc7291b681bf45f944fdb73c0bdc8 3396 pike8.0_8.0.1738-1.1.dsc
 80145e0c1ce4fa42058b9bde9a524c0a40ba9a95 37696 
pike8.0_8.0.1738-1.1.debian.tar.xz
 29f71f81cce0b1547575314270143574fb9d92a6 7192 
pike8.0_8.0.1738-1.1_source.buildinfo
Checksums-Sha256:
 a17bbc912acd962ff63a77d310b52d1ae5d43ed2bac2a8d2c1aa0a2a1bc3c9fd 3396 
pike8.0_8.0.1738-1.1.dsc
 3a057547eaa105695caa3d35940e08484fada93b1de2a8a90b3acb66c222ab31 37696 
pike8.0_8.0.1738-1.1.debian.tar.xz
 18c05249f8cce9b34dbe4e2f61ae763d80358f1f93a571321bdbedb6aa248e0b 7192 
pike8.0_8.0.1738-1.1_source.buildinfo
Files:
 946c42d79a2af769c7ef47661e140ae1 3396 interpreters optional 
pike8.0_8.0.1738-1.1.dsc
 82025e8ae11ed122b39815ecd5b31a04 37696 interpreters optional 
pike8.0_8.0.1738-1.1.debian.tar.xz
 167f8605624984ec252c29291492bb9a 7192 interpreters optional 
pike8.0_8.0.1738-1.1_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx+GgQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFJTAC/9xohGVoJtsJc3z2MP1+sod1F3jVhy6TZTG
xsprWXi/WeScmitOXAiRpYUwjDAjGF/B2AxQKRXPyrkTVv06zuGsCj8Reck6YH8U
3gCawuGra+U9W7x6EaxMraqL+Qc799TNyLLTHPR/u/pDobV0ZbIzayEQIu8Adhw0
8nlG+ruUom6t9s1Rzl8KDjeSash+cJY2B31xSrXSnk7LRlg0/l1cSwkORnjCVBYu
JBfyEjW5t5xskPvEtPSl91ytGR11Ttd+P3y4ZPFZhIkY4UIn71Vlvr8Oo5mU+NT9
/lYlagtZkPFnM56Vy70G1OCz7HN/r07K0rMEoGb3XC/uDuhBLl8xEaW7aOgzYk96
QY2mlVnqIsJH/aY3P6tk2z6DOI8xp+9JGtKmxmqFlNdX3Lh6RvrXr9hpoVsO1PhW
puKK/Hy8I+nsOOCztwS5aXy9CXXuqm5a87VYI0BqURKbhxCtXeLcoCIZIYmTKZY3
VwbIVvhUPEArf4nCBTF6O3ugJ55c0Lo=
=v5IK
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to