Your message dated Fri, 15 Nov 2024 15:20:00 +0000
with message-id <e1tby76-0044st...@fasolo.debian.org>
and subject line Bug#1087564: fixed in pcre2 10.44-3
has caused the Debian Bug report #1087564,
regarding pcre2: FTBFS on 32-bit: test failures, memory allocations smaller
than expected
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.)
--
1087564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcre2
Version: 10.44-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org, debian-h...@lists.debian.org,
debian-powe...@lists.debian.org, b...@debian.org
User: debian-...@lists.debian.org
Usertags: armhf
https://buildd.debian.org/status/fetch.php?pkg=pcre2&arch=armhf&ver=10.44-2&stamp=1731586953&raw=0
shows lots of test failures that look like this:
> /((?i)b)/
> -Memory allocation - compiled block : 153
> +Memory allocation - compiled block : 129
> Memory allocation - code portion : 17
armel has a different failure mode (some of the tests crash) which I have
reported as a separate bug - that's out of scope here. All of the other
32-bit architectures (i386, hppa, powerpc, x32) show symptoms similar to
armhf, which makes me think this is a general 32-bit problem rather than
being architecture-specific (and armel would probably have the same issue
if its tests hadn't crashed first).
Is this perhaps just an overly-strict test that is making assumptions
about the size of data structures on 64-bit architectures, which aren't
going to be true on 32-bit because pointers and 'long' are smaller there?
10.44-1 in experimental previously failed with similar symptoms.
smcv
--- End Message ---
--- Begin Message ---
Source: pcre2
Source-Version: 10.44-3
Done: Matthew Vernon <matt...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pcre2, 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 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthew Vernon <matt...@debian.org> (supplier of updated pcre2 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, 15 Nov 2024 14:47:09 +0000
Source: pcre2
Architecture: source
Version: 10.44-3
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon <matt...@debian.org>
Changed-By: Matthew Vernon <matt...@debian.org>
Closes: 1087562 1087564
Changes:
pcre2 (10.44-3) unstable; urgency=medium
.
* Use dh_autoreconf to fix FTBFS on mips64el (Closes: #1087562)
* Cherry-pick upstream commit to fix 32-bit issue (Closes: #1087564)
Checksums-Sha1:
687278762381a28e27e507b047973853133e1a93 2340 pcre2_10.44-3.dsc
9daa558a544321a5924b5c16e236479079fb7432 15961 pcre2_10.44-3.diff.gz
Checksums-Sha256:
ae1fa2e826cc1b0173f812d0fff2790850830ad6a34b9e210ceca191b008ee2b 2340
pcre2_10.44-3.dsc
73596763aea95fa9a325513cb09f6f1fe3410fa5c72732ce8a021537e89c49bd 15961
pcre2_10.44-3.diff.gz
Files:
522d3d7d2c852e462ba1b748d217343a 2340 libs optional pcre2_10.44-3.dsc
70693bf37cc532d106bf4a51651a3f38 15961 libs optional pcre2_10.44-3.diff.gz
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmc3Yb0THG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyKbCD/kBG2gq3icScOokSm3xyJ5SRmGwBVCs
gWGOpxgH1fQhjvmJCzfRfBn4s2OQPoxIXoDLjIGuB+l/eX0w3ob896J/UR6lkpBt
bDPr9jWerTIEgYNk5olTWLKxrf2egwINLecCThd01WpOb4ngQGIwqqsFDf8DIKFv
JOK1D563Lcu5cjb7emCVB+JcoZFwK2d2qHecY6posw6daUk9Y2YEMC2niE3/AdES
Sf7iAVgbBsXN2utup2n3pdVCiKCBPtgYXs3+/5k/hXe/vnxT2I1KI63lKD87pdVr
iikdjveg7bRh3xVG4UN1Tb00zWjoXuiaCE4AOIfj5eHBe2MZCtZGvQckVKMT5Pg1
Ll5GQiHorpH/vlIkRwuKqaynFV+LZAkM3Ho0r4taojrYNiCnlvtl2Ch6rLtKsp2O
dOpElDSbeTz4eaBBROYdEnVdHOLAiTm2rMmLUxlye0lDkjaXlyKqaV5+crJNnCeG
ZFdIqy7G83FScL/kGEioU1ZYVBiIN6A/GaoEkVC5UmfMjikzY5VRc56x1xQsZLxJ
PJfWbwMuYNNaMlbsZ2mIopR9BvVFgijB2ACdn9k3HU98YkQ73F7bBP3ZYunybCE1
7M6kblUsSnGEEgwV7aRevXKlaLiDZWoBxeQnZsvi7IeIVbgRCTTqvOTy97VPo1VK
FSXiywdpKNIfKQ==
=ewFJ
-----END PGP SIGNATURE-----
pgpK9vZHaGlJb.pgp
Description: PGP signature
--- End Message ---
