Your message dated Sat, 08 Aug 2026 15:19:11 +0000
with message-id <[email protected]>
and subject line Bug#1133589: fixed in octave-strings 1.3.1-3
has caused the Debian Bug report #1133589,
regarding octave-strings: ftbfs with GCC-16
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.)
--
1133589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133589
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:octave-strings
Version: 1.3.1-2
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: ftbfs-gcc-16
Hi,
octave-strings fails to build in a test rebuild on at least amd64 and arm64 with
gcc-16/g++-16, but builds properly with gcc-15/g++-15. The severity of this
report will be raised before the forky release.
The full build log can be found at:
https://people.debian.org/~ema/gcc-16-rebuilds/output-1/octave-strings_arm64.build.xz
The last lines of the build log are at the end of this report.
To build with GCC 16, either set CC=gcc-16 CXX=g++-16 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures include unused (but set) variables, array subscripts
partly outside array bounds, and new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-16/porting_to.html
Please only close this issue after double-checking that the package can be
built correctly with GCC 16.
Please do not reassign this bug to another package. If a fix in another package
is required, then file a bug for the other package (or clone), and mark this
bug as blocked by the bug in the other package.
[...]
dh_clean -O--buildsystem=octave
debian/rules binary
dh binary --buildsystem=octave
dh_update_autotools_config -O--buildsystem=octave
dh_autoreconf -O--buildsystem=octave
dh_octave_version -O--buildsystem=octave
Checking the Octave version... ok
dh_auto_configure -O--buildsystem=octave
dh_auto_build -O--buildsystem=octave
dh_auto_test -O--buildsystem=octave
create-stamp debian/debhelper-build-stamp
dh_testroot -O--buildsystem=octave
dh_prep -O--buildsystem=octave
dh_auto_install --destdir=debian/octave-strings/ -O--buildsystem=octave
octave --no-gui --no-history --silent --no-init-file --no-window-system
/usr/share/dh-octave/install-pkg.m
/build/reproducible-path/octave-strings-1.3.1/debian/octave-strings/usr/share/octave/packages
/build/reproducible-path/octave-strings-1.3.1/debian/octave-strings/usr/lib/aarch64-linux-gnu/octave/packages
mkdir (/tmp/oct-7BGcaT)
untar (/tmp//octave-strings-1.3.1.tar.gz, /tmp/oct-7BGcaT)
checking for mkoctfile... /usr/bin/mkoctfile --verbose
checking for octave-config... /usr/bin/octave-config
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... -std=gnu++11
checking how to run the C++ preprocessor... g++ -std=gnu++11 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PCRE2... yes
checking gripe_wrong_type_arg or err_wrong_type_arg... gripe_wrong_type_arg
checking unwind_protect or octave::unwind_protect... unwind_protect
checking for octave::unwind_action... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
make[1]: Entering directory '/tmp/oct-7BGcaT/octave-strings-1.3.1/src'
/usr/bin/mkoctfile --verbose -o pcregexp.oct pcregexp.cc -DUSE_PCRE2 -lpcre2-8
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/octave-11.1.0/octave/.. -I/usr/include/octave-11.1.0/octave
-pthread -fopenmp -g -O2
-ffile-prefix-map=/build/reproducible-path/octave-strings-1.3.1=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -DUSE_PCRE2 pcregexp.cc
-o /tmp/oct-BNTmh3.o
Extracting tests from pcregexp.cc ...
In file included from pcregexp.cc:36:
pcregexp.cc: In function ‘octave_value_list Fpcregexp(const octave_value_list&,
int)’:
config.h:43:32: error: ‘unwind_protect’ was not declared in this scope; did you
mean ‘octave::unwind_protect’?
43 | #define OCTAVE__UNWIND_PROTECT unwind_protect
| ^~~~~~~~~~~~~~
pcregexp.cc:88:5: note: in expansion of macro ‘OCTAVE__UNWIND_PROTECT’
88 | OCTAVE__UNWIND_PROTECT cleanup;
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/octave-11.1.0/octave/../octave/error.h:35,
from /usr/include/octave-11.1.0/octave/../octave/oct.h:37,
from pcregexp.cc:24:
/usr/include/octave-11.1.0/octave/../octave/unwind-prot.h:40:18: note:
‘octave::unwind_protect’ declared here
40 | class OCTAVE_API unwind_protect : public action_container
| ^~~~~~~~~~~~~~
pcregexp.cc:89:5: error: ‘cleanup’ was not declared in this scope
89 | cleanup.add_fcn (pcre2_match_data_free, match_data);
| ^~~~~~~
make[1]: *** [Makefile:36: pcregexp.oct] Error 1
make[1]: Leaving directory '/tmp/oct-7BGcaT/octave-strings-1.3.1/src'
error: pkg: error running 'make' for the strings package
error: called from
configure_make at line 121 column 9
install at line 202 column 7
pkg at line 692 column 9
/usr/share/dh-octave/install-pkg.m at line 45 column 1
dh_auto_install: error: octave --no-gui --no-history --silent --no-init-file
--no-window-system /usr/share/dh-octave/install-pkg.m
/build/reproducible-path/octave-strings-1.3.1/debian/octave-strings/usr/share/octave/packages
/build/reproducible-path/octave-strings-1.3.1/debian/octave-strings/usr/lib/aarch64-linux-gnu/octave/packages
returned exit code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--- End Message ---
--- Begin Message ---
Source: octave-strings
Source-Version: 1.3.1-3
Done: Sébastien Villemot <[email protected]>
We believe that the bug you reported is fixed in the latest version of
octave-strings, 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.
Sébastien Villemot <[email protected]> (supplier of updated octave-strings
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: Sat, 08 Aug 2026 17:06:11 +0200
Source: octave-strings
Architecture: source
Version: 1.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group <[email protected]>
Changed-By: Sébastien Villemot <[email protected]>
Closes: 1133589
Changes:
octave-strings (1.3.1-3) unstable; urgency=medium
.
* Team upload
.
[ Rafael Laboissière ]
* d/salsa-ci.yml: New file
* d/control: Drop the redundant Priority field, which defaults to optional
now
* d/control: Bump Standards-Version to 4.7.3
* d/control: Bump Standards-Version to 4.7.4 (no changes needed)
* Change Maintainer and Vcs-* paths to octave-team
* d/control: Remove reference to Octave-Forge, which no longer exists
* d/control: Bump debhelper compatibility level to 14
* d/control: Drop useless substitution variables
.
[ Sébastien Villemot ]
* Remove myself from Uploaders
* debian/autoreconf: new file, for regenerating autotools files.
This fixes the compilation failure with GCC 16, which was caused by
#1133694, now fixed in autoconf. (Closes: #1133589)
Checksums-Sha1:
67a2f311eaffd130183c466a3bfe7be49ddc0961 2127 octave-strings_1.3.1-3.dsc
af1f7a55371e0684dfbd684c7d194a6ef819ea6f 6064
octave-strings_1.3.1-3.debian.tar.xz
04757b7eb6cc092a1a6c4e360cd69679edf7dccf 24692
octave-strings_1.3.1-3_amd64.buildinfo
Checksums-Sha256:
06a4cb1bc07b4e28773f82d4272883d8356db6cd35ccff5604d57812c282508e 2127
octave-strings_1.3.1-3.dsc
4bcccfbab2dfbd5d7578cd6f8f95d08c3ad3422a1cf164e45a87ed5d5ff33d9e 6064
octave-strings_1.3.1-3.debian.tar.xz
a593349680b2bd16123d4795cfe2832161c25c338cde0d0765513825ae5586cf 24692
octave-strings_1.3.1-3_amd64.buildinfo
Files:
cadc5676f3e5167c36c3114947226aeb 2127 math optional octave-strings_1.3.1-3.dsc
55b455444d6f5bc49bb054fad07cdbc8 6064 math optional
octave-strings_1.3.1-3.debian.tar.xz
003233d52a6725bf7c10f2fb9611b46e 24692 math optional
octave-strings_1.3.1-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmp3RlIACgkQLOzpNQ7O
vkoKWg/8CkucAzfE+/baxAMnY09N06T2ztc5THBIfoAZoVppwgwEwTtpV+bWju+C
p+5ph/eREKBIa50dKN3U4LuZ06GcsJU7ZyWURNlW1vtmyuHqiakIgNXN36l8ZzDW
fmwd8V3Y1okRr0eDhNS1V8s6JfVU7rCVdpOHMtlxPiPcYXz1mffW1tPL6n0Iy3Di
MupcLm3GaNJiE1/lHpzj9M4Gk4PMY+gqmWqddikRXrrdda59Nr+aZNcW2+LKrdrK
wuRFP9fV7/5H5bGpMeZd5wRUrdAebyx3hl9iluZaccRlfxvqOhedVX1XbdNFg0Bi
1qQAGRWXYDHuAlGXLnFDpCy4jHeOaFx2L2qHpPxPyfQv/gj9mgchsyQhZx+KB3FM
chqhlJC8dP/XR/GGKw8i5iB5zHFFscp1t7zAnwILxne9TDL25+N6++mQ4sAORtVv
vnol9BwRGt4biVkP3Q5t4eL8BIiK2XN92KolVQ2vgoEmdFdC4M+X7a0nqC+DxvwA
k2iBHjoaWnjcquZxyLJhgzKN3EHhb42w+qiwGqPPFHuVNaumxDoGTT/KeaHl5I/e
KWOuP9KkYorYATYdu/Okch8Mi3oRtJHeRQ/YJg2N32m48D6IPPGywKf7FCV5apy3
vx9aOYh2NDDmeyYZa2NuPMHruxKp62RHMuqP7mTJecjC864a3u4=
=tA3D
-----END PGP SIGNATURE-----
pgpN6Oum4X8R5.pgp
Description: PGP signature
--- End Message ---
