Your message dated Wed, 18 Feb 2026 21:19:08 +0000
with message-id <[email protected]>
and subject line Bug#1115559: fixed in pchar 1.5-7
has caused the Debian Bug report #1115559,
regarding pchar FTCBFS: ancient autoconf
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 [email protected]
immediately.)
--
1115559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115559
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pchar
Version: 1.5-6
Severity: serious
Justification: missing source
Tags: trixie forky sid
User: [email protected]
Usertags: ftcbfs
pchar fails to cross build from source, because it misdetects the C++
compiler and once we force that, it fails to compute sizeof(bool). This
is a problem in autoconf that has been about fixed 15 years ago. The
configure script used autoconf version 2.13, which is not part of
trixie nor forky. Therefore, pchar misses source code for the generated
file configure in those releases.
Please regenerate configure with a more recent autoconf version.
Alternatively, enable autoreconf and do so during every build as this is
now the standard procedutre. Doing so will very likely also fix the
compiler and sizeof detection. Failing that, a method of last resort is
adding autoconf2.13 to Build-Depends (even when not using it) just to
ensure that autoconf2.13 is present in the same suite. Then, pchar will
be autoreomoved from forky.
Helmut
--- End Message ---
--- Begin Message ---
Source: pchar
Source-Version: 1.5-7
Done: Petter Reinholdtsen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pchar, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Petter Reinholdtsen <[email protected]> (supplier of updated pchar 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 18 Feb 2026 22:04:54 +0100
Source: pchar
Architecture: source
Version: 1.5-7
Distribution: unstable
Urgency: medium
Maintainer: Petter Reinholdtsen <[email protected]>
Changed-By: Petter Reinholdtsen <[email protected]>
Closes: 1115559
Changes:
pchar (1.5-7) unstable; urgency=medium
.
* Added 1060-autoconf-newer.patch to work with fix build problem
(Closes: #1115559).
Checksums-Sha1:
044f566bdb1aeb30e1f01a53a4d6a503385c25c7 1813 pchar_1.5-7.dsc
439687d9fe6d29ec8be8b0c0158e0902180f4373 8536 pchar_1.5-7.debian.tar.xz
eb646cb5228fb4319e57f746a4d862a1618986d5 6730 pchar_1.5-7_source.buildinfo
Checksums-Sha256:
74a59dd7cfe1f24b2a3827a706b604218e8de06a777d7de4cfb2c88324aec5ed 1813
pchar_1.5-7.dsc
654f0d62ded3c777118d8f65b923f78f19e10dc0b35a1b282c1356f5fd3b2260 8536
pchar_1.5-7.debian.tar.xz
751daf410f1c2a6ddcbfdd00fbd3f47940b84546e0a4bb07f2ac6e81976c08a8 6730
pchar_1.5-7_source.buildinfo
Files:
90e2ee1d17e43cbad1a38d9fc108f8a3 1813 net optional pchar_1.5-7.dsc
807ac6802950dff97ae099c07bed2dee 8536 net optional pchar_1.5-7.debian.tar.xz
90911aec8bb8d1d181b46f0ad159c3fd 6730 net optional pchar_1.5-7_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmmWKeEACgkQgSgKoIe6
+w7qxA//Sq81goEeMLEG1ob06S2A1naXCOF6VN7VuLNjYiTKOPdbC41NuSWR9t0f
B+NKQnZOFi6UtjCQSHu3uDidywoUROk7RMCCSXUQyGgLC61nW9H7JDRJ7TjY8HNE
qnu4mv+6PVeNOZaZWJOzRGMznlGdjVfMYEHyo8qvLlpiepGW5tEjlYQh4bekubIm
8AArWkFQk3BThulhHGcORwWFLX+7VJ2YZIV/O9NGL32NmPP5XS9B77IH8XxCnv/7
ohb6kEwuIv2E4ZQeXc4pY1kjv8DUqGWTRAR8y/xYjHvqnVAeAyMv0vba7m1TxDRW
HLor/uYMUUEiOzGaMNk3fYD53fxQ5Sn8iQGhJpF5xJfm5aI1GdhduuYtAN0BAvHa
k+f46hmI9RVAoDAWc+rn/sAmbHo10Rk3liXo8w8vxe+HmOXaZuUeKsHX6Va/HoHb
Z5C91vftueaxOy3K1nmFbUAYycSwdE/APgGvMZWq5dyy6mbwQU6wrdOYmZUCDBI8
1twn7SpNZXxRdmM/xxniv5iz/2YXkfd6ykciLL8zOZbp21M0kFquHRrt9xdHie05
Y2IZ8yDk9QEaXJX79jd9k7zVe6XWiBAFglpAwBM30i3G2DjKeUm+2x/dbZKWlg4T
alkZ7LZC6XikKYceH1gDS0dwtKnpro8Q6Hn+qyLuJlvVImi9ojc=
=SPa5
-----END PGP SIGNATURE-----
pgpNG86z03K4I.pgp
Description: PGP signature
--- End Message ---
