Your message dated Fri, 30 Jun 2023 05:03:44 +0000
with message-id <e1qf6ik-00e1is...@fasolo.debian.org>
and subject line Bug#1000128: fixed in mapcache 1.14.0-2
has caused the Debian Bug report #1000128,
regarding mapcache: 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.)


-- 
1000128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapcache
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: mapcache
Source-Version: 1.14.0-2
Done: Bas Couwenberg <sebas...@debian.org>

We believe that the bug you reported is fixed in the latest version of
mapcache, 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.
Bas Couwenberg <sebas...@debian.org> (supplier of updated mapcache 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: Fri, 30 Jun 2023 06:34:42 +0200
Source: mapcache
Architecture: source
Version: 1.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project <pkg-grass-de...@lists.alioth.debian.org>
Changed-By: Bas Couwenberg <sebas...@debian.org>
Closes: 1000128
Changes:
 mapcache (1.14.0-2) unstable; urgency=medium
 .
   * Bump debhelper compat to 13.
   * Disable PCRE support, pcre3 package will be removed.
     (closes: #1000128)
Checksums-Sha1:
 219fc1e8de28558ecfb054e5fdd704f09818b552 2751 mapcache_1.14.0-2.dsc
 78b1dc3f9c5bd08d052981e9c3fbf4ba290e8f79 15012 mapcache_1.14.0-2.debian.tar.xz
 5fbfe0471e50c3f8d3228b630240c4025a255654 20044 
mapcache_1.14.0-2_amd64.buildinfo
Checksums-Sha256:
 3faaa882b127dd9c27bcd88b1d1914d65a43ac090c4115d17d4173bc2efcb6a9 2751 
mapcache_1.14.0-2.dsc
 efd5d1b461b78ad6baa2b584d1d83c3ea191d270e1e92a3d6c50cb641c90132d 15012 
mapcache_1.14.0-2.debian.tar.xz
 984e3f837b92725ec746121d53e0160da0a73bf653ead0d3b2941a13df5ca564 20044 
mapcache_1.14.0-2_amd64.buildinfo
Files:
 fcfba1c5825407ef2ad808974e68390f 2751 devel optional mapcache_1.14.0-2.dsc
 56bdf229541822b6e75b85849f6dcc3f 15012 devel optional 
mapcache_1.14.0-2.debian.tar.xz
 f7dd10f8250768f8c30036daaa72bb45 20044 devel optional 
mapcache_1.14.0-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmSeXTwACgkQZ1DxCuiN
SvFeag/9E0L8Cyb3Iw8xSKbntc5dQ6M9eNQNpP3yHXnZaA/2Iu1Y5zwwKYHqt2YK
iyUl9ic8ujLG4LwX01VXC7+E+MfTbys3GT2jKMUUstsDvvQWZXQPVXu4M74niEhO
o7mRZBoKMxaEC5DaUL36Glk7Rb8sDqKxlE7zkkTAOiWn/7Q+1eTzaUjnXd7IwNvP
ugvFTgBtFayKKR3i600NbjPJdtA256H8kJEI+OK8iu0iX3tstOBsO/PDPgRadHUW
L11f5GDugrxYlpiuKukrJtSK/xswa1n0ULMeeMp2xyFuEngnYpTQxIMk+DZiLKyW
BtA72lmHdSZQJar0vSmnjRj4kpV0p9PiTwqnXZUKrr6PmjL58fIYaIx62mg8szbn
dMJKXApv7cfOmpK/AomV869djCySmxfQPEX/tfBNBfdR1lrMsrt0ugd7hjUzrBG8
5eAy49LrsZb6x4YB/RWqJ5jzPFqkDFtnTk0wmJYeB3mAUCU6PQhcmIa3ozZKrugj
S0DEPrcL/TiqrmJQjMaWwtE4dv5avytxdQtwJ1qkuJo+PnoouE3rWG/Z9lpInFyp
vgWHz5llrGIBlFitdoKeoAvjabzdqh4bJzi+obffWr9nCIbe1c5h1U2Q2on7tqzi
nzAYt1oLTWcwpMLFMo20GzyL8/zrBQ/fUCmnYB5HDOQMtZ+gr2E=
=E7Vx
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to