Your message dated Sat, 27 Jul 2024 10:19:20 +0000
with message-id <e1sxewg-00957b...@fasolo.debian.org>
and subject line Bug#1075102: fixed in jpy 0.16.0-1
has caused the Debian Bug report #1075102,
regarding jpy: ftbfs with GCC-14
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.)
--
1075102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jpy
Version: 0.13.0-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/jpy_0.13.0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ^~~~~~~~~~~~
| |
| PyTracebackObject **
{aka struct _traceback **}
/usr/include/python3.12/pyerrors.h:42:67: note: expected ‘PyObject **’ {aka
‘struct _object **’} but argument is of type ‘PyTracebackObject **’ {aka
‘struct _traceback **’}
42 | PyAPI_FUNC(void) PyErr_NormalizeException(PyObject**, PyObject**,
PyObject**);
|
^~~~~~~~~~
src/main/c/jni/org_jpy_PyLib.c:2490:63: error: passing argument 1 of
‘PyObject_GetAttrString’ from incompatible pointer type
[-Wincompatible-pointer-types]
2490 | linenoChars =
PyLib_ObjToChars(PyObject_GetAttrString(pyTraceback, "tb_lineno"),
&pyLinenoUtf8);
|
^~~~~~~~~~~
| |
|
PyTracebackObject * {aka struct _traceback *}
In file included from /usr/include/python3.12/Python.h:44:
/usr/include/python3.12/object.h:407:47: note: expected ‘PyObject *’ {aka
‘struct _object *’} but argument is of type ‘PyTracebackObject *’ {aka ‘struct
_traceback *’}
407 | PyAPI_FUNC(PyObject *) PyObject_GetAttrString(PyObject *, const char *);
| ^~~~~~~~~~
src/main/c/jni/org_jpy_PyLib.c:2491:42: error: passing argument 1 of
‘PyObject_GetAttrString’ from incompatible pointer type
[-Wincompatible-pointer-types]
2491 | pyFrame = PyObject_GetAttrString(pyTraceback, "tb_frame");
| ^~~~~~~~~~~
| |
| PyTracebackObject * {aka
struct _traceback *}
/usr/include/python3.12/object.h:407:47: note: expected ‘PyObject *’ {aka
‘struct _object *’} but argument is of type ‘PyTracebackObject *’ {aka ‘struct
_traceback *’}
407 | PyAPI_FUNC(PyObject *) PyObject_GetAttrString(PyObject *, const char *);
| ^~~~~~~~~~
src/main/c/jni/org_jpy_PyLib.c:2491:17: error: assignment to ‘PyFrameObject *’
{aka ‘struct _frame *’} from incompatible pointer type ‘PyObject *’ {aka
‘struct _object *’} [-Wincompatible-pointer-types]
2491 | pyFrame = PyObject_GetAttrString(pyTraceback, "tb_frame");
| ^
src/main/c/jni/org_jpy_PyLib.c:2495:73: error: passing argument 1 of
‘PyObject_GetAttrString’ from incompatible pointer type
[-Wincompatible-pointer-types]
2495 | filenameChars =
PyLib_ObjToChars(PyObject_GetAttrString(pyCode, "co_filename"),
&pyFilenameUtf8);
|
^~~~~~
|
|
|
PyCodeObject *
/usr/include/python3.12/object.h:407:47: note: expected ‘PyObject *’ {aka
‘struct _object *’} but argument is of type ‘PyCodeObject *’
407 | PyAPI_FUNC(PyObject *) PyObject_GetAttrString(PyObject *, const char *);
| ^~~~~~~~~~
src/main/c/jni/org_jpy_PyLib.c:2496:74: error: passing argument 1 of
‘PyObject_GetAttrString’ from incompatible pointer type
[-Wincompatible-pointer-types]
2496 | namespaceChars =
PyLib_ObjToChars(PyObject_GetAttrString(pyCode, "co_name"), &pyNamespaceUtf8);
|
^~~~~~
|
|
|
PyCodeObject *
/usr/include/python3.12/object.h:407:47: note: expected ‘PyObject *’ {aka
‘struct _object *’} but argument is of type ‘PyCodeObject *’
407 | PyAPI_FUNC(PyObject *) PyObject_GetAttrString(PyObject *, const char *);
| ^~~~~~~~~~
src/main/c/jni/org_jpy_PyLib.c:2530:47: error: passing argument 1 of
‘python_traceback_report’ from incompatible pointer type
[-Wincompatible-pointer-types]
2530 | int err = python_traceback_report(pyTraceback,
&javaMessage, &bufLen);
| ^~~~~~~~~~~
| |
| PyTracebackObject * {aka
struct _traceback *}
src/main/c/jni/org_jpy_PyLib.c:48:46: note: expected ‘PyObject *’ {aka ‘struct
_object *’} but argument is of type ‘PyTracebackObject *’ {aka ‘struct
_traceback *’}
48 | static int python_traceback_report(PyObject *tb, char **buf, int*
bufLen);
| ~~~~~~~~~~^~
src/main/c/jni/org_jpy_PyLib.c: In function ‘append_to_java_message’:
src/main/c/jni/org_jpy_PyLib.c:2702:35: warning: comparison of integer
expressions of different signedness: ‘size_t’ {aka ‘long unsigned int’} and
‘int’ [-Wsign-compare]
2702 | if (strlen(*buf) + msgLen + 1 >= *bufLen) {
| ^~
src/main/c/jni/org_jpy_PyLib.c: In function ‘python_traceback_report’:
src/main/c/jni/org_jpy_PyLib.c:2787:36: error: passing argument 1 of
‘format_python_traceback’ from incompatible pointer type
[-Wincompatible-pointer-types]
2787 | return format_python_traceback(tb, buf, bufLen);
| ^~
| |
| PyObject * {aka struct _object *}
src/main/c/jni/org_jpy_PyLib.c:2721:55: note: expected ‘PyTracebackObject *’
{aka ‘struct _traceback *’} but argument is of type ‘PyObject *’ {aka ‘struct
_object *’}
2721 | static int format_python_traceback(PyTracebackObject *tb, char **buf,
int *bufLen)
| ~~~~~~~~~~~~~~~~~~~^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.12"
returned exit code 13
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: jpy
Source-Version: 0.16.0-1
Done: Alastair McKinstry <mckins...@debian.org>
We believe that the bug you reported is fixed in the latest version of
jpy, 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 1075...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated jpy 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: SHA256
Format: 1.8
Date: Sat, 27 Jul 2024 10:55:52 +0100
Source: jpy
Architecture: source
Version: 0.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1075102
Changes:
jpy (0.16.0-1) unstable; urgency=medium
.
* New upstream version
* Standards-Version: 4.7.0; no changes required
* Patch to fix FTBFS with g++-14. Closes: #1075102
Checksums-Sha1:
534029e3fc79636b7353bb53beac426fd3e9cea6 1973 jpy_0.16.0-1.dsc
c7457f4cb7f0903ffa250d36c1f4a79baa8c658f 177636 jpy_0.16.0.orig.tar.xz
10b313809ce291d767c6e1a049ab7a3defa6c58e 7420 jpy_0.16.0-1.debian.tar.xz
Checksums-Sha256:
9201fadd9b90dc5e990bc43a5b530e12b4f4111a97e960b4932509793d017526 1973
jpy_0.16.0-1.dsc
d031f83dba4bcfe1b87815ff2fd4a9480bee75fb84bf1aff271fa6a71fdc4a04 177636
jpy_0.16.0.orig.tar.xz
3445addee90569857744100cb83ce9c7f86f8caddf9ea4f0850b1ab3c4c0bbc6 7420
jpy_0.16.0-1.debian.tar.xz
Files:
708b82bd22630598c631e6bcdcafc1c1 1973 python optional jpy_0.16.0-1.dsc
160ebd97bd677fa81c948ba05607f27e 177636 python optional jpy_0.16.0.orig.tar.xz
e0b50014d9e682b584c85888214195d4 7420 python optional
jpy_0.16.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmakxPkACgkQy+a7Tl2a
06UuDhAAmaEloUsVF5ZZAJ7x/RmxejjLefjrAqhg/Uvz/gVctZhbHWUeL279KgGl
OL0CRSuOIm1t6PGyim/TGF4FdpNpHEftAN7qIzH2wrWkk9L9dgYyrxgmyre3GBKq
MBVmXpuBz4tLF/+BwQ0VyPKeJoOLQ+s2AuiIot775tRdQE3xumTMU6kNfwgORwyN
OiBxzfG6GCc7oteZEr98O81fZ0REE21ajbmPTiw4bxsEa2uQEDbEyMgkVpSudsG0
Qaj4JtZYPNX2AUxGt7t8KFV7zYfJsTKTGrDIFE9Xl+xc1pzCXNK3ZpLAG/efdMsX
B8Jr427g4rXga/tZ8BkxzUcBFZCG+gIMybTNn1nCD6y0u4434Iyvh8yEydxycGDn
ugXacWl8dTeH40tqmSSxGZC0gCqBJUhq06MtCiDbsuh2M109yNygZROeCnd5HpQT
Nhz4NGuqbE50EvrH/m1G2XbEuGaLAnkuBMXXaC/piUMKTTl6GPW9Ohoe8KU6zseO
ca5TZkhjTvR8L0cVI+tGfbcWavv/ZWgsvdxbZ5xCw8fCtygy8jFQVK6qd+Wa/min
EJiJnhD3mjjehkBiHdqkFfkQqbKVIEAm0h/yfy5SUbN3CHuNGTpW1ZWda/ah4uLi
3uVNGs5iJf9JjWik2VfjwrsgTPpEeYgMN3yKkty81Z8CJbtd168=
=M43y
-----END PGP SIGNATURE-----
pgpVRATJcOoMV.pgp
Description: PGP signature
--- End Message ---
