Your message dated Wed, 02 Sep 2026 12:39:08 +0000
with message-id <[email protected]>
and subject line Bug#1144962: fixed in qpid-proton 0.37.0-10
has caused the Debian Bug report #1144962,
regarding qpid-proton: FTBFS due to missing PyString_FromString
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.)


-- 
1144962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qpid-proton
Version: 0.37.0-9
Severity: serious
Tags: ftbfs

I tried to rebuild qpid-proton against openssl 4 and noticed that it
doesn't build right now at all:

| make[3]: Leaving directory 
'/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build'
| make  -f python/CMakeFiles/cproton.dir/build.make 
python/CMakeFiles/cproton.dir/build
| make[3]: Entering directory 
'/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build'
| [ 99%] Building C object 
python/CMakeFiles/cproton.dir/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c.o
| cd 
/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build/python 
&& /usr/bin/x86_64-linux-gnu-gcc -Dcproton_EXPORTS 
-I/build/reproducible-path/qpid-proton-0.37.0/.pybuild/c 
python3_3.14/build/c/include -I/usr/include/python3.14 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/qpid-proton-0.37.0=. 
-fstack-protector-strong - fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-fvisibility=hidden -std=c99 -fPIC -MD -MT 
python/CMakeFiles/cproton.dir/CMakeFiles/c proton.dir/cprotonPYTHON_wrap.c.o 
-MF CMakeFiles/cproton.dir/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c.o.d -o 
CMakeFiles/cproton.dir/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c.o -c /build 
/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build/python/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c
| 
/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build/python/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c:
 In function ‘pn_pytracer’:
| 
/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build/python/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c:3846:23:
 error: implicit declaration of function ‘PyString_FromStr ing’; did you mean 
‘PyLong_FromString’? [-Wimplicit-function-declaration]
|  3846 |     PyObject *pymsg = PyString_FromString(message);
|       |                       ^~~~~~~~~~~~~~~~~~~
|       |                       PyLong_FromString
| 
/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build/python/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c:3846:23:
 error: initialization of ‘PyObject *’ {aka ‘struct _objec t *’} from ‘int’ 
makes pointer from integer without a cast [-Wint-conversion]
| make[3]: *** [python/CMakeFiles/cproton.dir/build.make:82: 
python/CMakeFiles/cproton.dir/CMakeFiles/cproton.dir/cprotonPYTHON_wrap.c.o] 
Error 1
| make[3]: Leaving directory 
'/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build'
| make[2]: *** [CMakeFiles/Makefile2:3848: python/CMakeFiles/cproton.dir/all] 
Error 2
| make[2]: Leaving directory 
'/build/reproducible-path/qpid-proton-0.37.0/.pybuild/cpython3_3.14/build'
| make[1]: *** [Makefile:149: all] Error 2

Maybe this broke during python transition and PyUnicode_FromString()
would be the right thing to use.

Sebastian

--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.37.0-10
Done: Thomas Goirand <[email protected]>

We believe that the bug you reported is fixed in the latest version of
qpid-proton, 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.
Thomas Goirand <[email protected]> (supplier of updated qpid-proton 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, 02 Sep 2026 14:10:55 +0200
Source: qpid-proton
Architecture: source
Version: 0.37.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Closes: 1144962
Changes:
 qpid-proton (0.37.0-10) unstable; urgency=medium
 .
   [ Rafael Laboissière ]
   * Add build-with-swig-4.5.0.patch (Closes: #1144962).
Checksums-Sha1:
 7eda184bbfcdc876edd986cb03475b5d83d8478c 2802 qpid-proton_0.37.0-10.dsc
 e081a409aaa80fe89f60220851ba09c2dbc42515 10912 
qpid-proton_0.37.0-10.debian.tar.xz
 69c61f74661a8716ba922ae25294ab09cbc0f28d 12326 
qpid-proton_0.37.0-10_amd64.buildinfo
Checksums-Sha256:
 afcce2ccd69d7ed7b810996f4e172ede198bd15525b75ee5c0c3c795dcf30175 2802 
qpid-proton_0.37.0-10.dsc
 f86bb55098e484d12282025b748b5cc37f7e0279a59bbbb7fa64f2a8a4116208 10912 
qpid-proton_0.37.0-10.debian.tar.xz
 87c0017b828b8cc9cfee3aea61ee228a3891b3be5aa966c6031e8a7765f17489 12326 
qpid-proton_0.37.0-10_amd64.buildinfo
Files:
 cd99c72e5f3a1187948113b816d8f25b 2802 libs optional qpid-proton_0.37.0-10.dsc
 1e88081d933ed5ed89d3164a14e2ec8c 10912 libs optional 
qpid-proton_0.37.0-10.debian.tar.xz
 05c646b596cd5fec8da2b5de57d96c28 12326 libs optional 
qpid-proton_0.37.0-10_amd64.buildinfo

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

iQIzBAEBCgAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmqYEvEACgkQ1BatFaxr
Q/4BRw/+P5DVzFHa6eH8OEZtNGCosmEHOZw6vq+G3qR/O6pQ8Yj9s3f4pcd0Qovt
pv+kihbMmZ/1t+tNVd43/SYXbA1+zoYfj6/QPeVChPoIBBW32Nf3oyhV2HFjxERP
+hSraeLA3tVGhWVsdlfF70808UAFoUc7CCF6000IWd1gury7BKEA/I3/HKXOBTQu
kaArz9we7oK34Z+9Z97fBWgiQ1uuI+xcQN34exrHSV/uMzsHxLXuJnOH9uAFqA3E
YwfeMwrrfC3pdzNDpr5NLpwf6cynyTDyy6Q6C7n225dHh3+1o7WvJ6ozNS6oEceB
NnAuFIu1noFQqbMt/d8MxjtNK60UXP9t73y9/j/RmrWb/1KH22ysbcXQs3TsrvFx
yarZw58/5AR5w8+sgyehC1UfpySk5OtLE/rV8wvNtL7fFZ5bHNwpPyiIng1FYoLa
hJ/56lqN+bTf4JQY4M1vQbmIoaqL5piOUmTFdVo2T/LHeeGpXLkGWYauqp0C1pia
QSUQYod+bWXXaxTf+jMB7HrKhAGqAktwnrh4lCkVqWf+WKdPMk85pP97JWBApo++
ik9Q+DW4b4oc0ptrDYQo5PCulIgZNN/SNtxCEko3yzLcRBDpupue+MPSCIzHfq7/
Q1CrNjSHuHEzS7LnrbyWjg83Sfc3Iw2ee8mI+YN21EeqNkj75hA=
=c6Ov
-----END PGP SIGNATURE-----

Attachment: pgpFAXoyULLYc.pgp
Description: PGP signature


--- End Message ---

Reply via email to