Your message dated Wed, 31 Jul 2024 17:35:16 +0000
with message-id <e1szdek-00cwl3...@fasolo.debian.org>
and subject line Bug#1075453: fixed in ruamel.yaml.clib 0.2.8+ds-2
has caused the Debian Bug report #1075453,
regarding ruamel.yaml.clib: 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.)
--
1075453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruamel.yaml.clib
Version: 0.2.8+ds-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/ruamel.yaml.clib_0.2.8+ds-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
[...]
23001 | __pyx_t_2 = (yaml_alias_event_initialize((&__pyx_v_event),
__pyx_v_anchor) == 0);
|
^~~~~~~~~~~~~~
| |
| char *
yaml.h:555:63: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
555 | yaml_alias_event_initialize(yaml_event_t *event, yaml_char_t *anchor);
| ~~~~~~~~~~~~~^~~~~~
_ruamel_yaml.c:23731:67: warning: pointer targets in passing argument 2 of
‘yaml_scalar_event_initialize’ differ in signedness [-Wpointer-sign]
23731 | __pyx_t_2 = (yaml_scalar_event_initialize((&__pyx_v_event),
__pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length,
__pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0);
|
^~~~~~~~~~~~~~
| |
| char *
yaml.h:581:22: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
581 | yaml_char_t *anchor, yaml_char_t *tag,
| ~~~~~~~~~~~~~^~~~~~
_ruamel_yaml.c:23731:83: warning: pointer targets in passing argument 3 of
‘yaml_scalar_event_initialize’ differ in signedness [-Wpointer-sign]
23731 | __pyx_t_2 = (yaml_scalar_event_initialize((&__pyx_v_event),
__pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length,
__pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0);
|
^~~~~~~~~~~
|
|
|
char *
yaml.h:581:43: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
581 | yaml_char_t *anchor, yaml_char_t *tag,
| ~~~~~~~~~~~~~^~~
_ruamel_yaml.c:23731:96: warning: pointer targets in passing argument 4 of
‘yaml_scalar_event_initialize’ differ in signedness [-Wpointer-sign]
23731 | __pyx_t_2 = (yaml_scalar_event_initialize((&__pyx_v_event),
__pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length,
__pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0);
|
^~~~~~~~~~~~~
|
|
|
char *
yaml.h:582:22: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
582 | yaml_char_t *value, int length,
| ~~~~~~~~~~~~~^~~~~
_ruamel_yaml.c:24088:75: warning: pointer targets in passing argument 2 of
‘yaml_sequence_start_event_initialize’ differ in signedness [-Wpointer-sign]
24088 | __pyx_t_2 =
(yaml_sequence_start_event_initialize((&__pyx_v_event), __pyx_v_anchor,
__pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0);
|
^~~~~~~~~~~~~~
|
|
|
char *
yaml.h:604:22: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
604 | yaml_char_t *anchor, yaml_char_t *tag, int implicit,
| ~~~~~~~~~~~~~^~~~~~
_ruamel_yaml.c:24088:91: warning: pointer targets in passing argument 3 of
‘yaml_sequence_start_event_initialize’ differ in signedness [-Wpointer-sign]
24088 | __pyx_t_2 =
(yaml_sequence_start_event_initialize((&__pyx_v_event), __pyx_v_anchor,
__pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0);
|
^~~~~~~~~~~
|
|
|
char *
yaml.h:604:43: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
604 | yaml_char_t *anchor, yaml_char_t *tag, int implicit,
| ~~~~~~~~~~~~~^~~
_ruamel_yaml.c:24601:74: warning: pointer targets in passing argument 2 of
‘yaml_mapping_start_event_initialize’ differ in signedness [-Wpointer-sign]
24601 | __pyx_t_2 =
(yaml_mapping_start_event_initialize((&__pyx_v_event), __pyx_v_anchor,
__pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0);
|
^~~~~~~~~~~~~~
|
|
|
char *
yaml.h:636:22: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
636 | yaml_char_t *anchor, yaml_char_t *tag, int implicit,
| ~~~~~~~~~~~~~^~~~~~
_ruamel_yaml.c:24601:90: warning: pointer targets in passing argument 3 of
‘yaml_mapping_start_event_initialize’ differ in signedness [-Wpointer-sign]
24601 | __pyx_t_2 =
(yaml_mapping_start_event_initialize((&__pyx_v_event), __pyx_v_anchor,
__pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0);
|
^~~~~~~~~~~
|
|
|
char *
yaml.h:636:43: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but
argument is of type ‘char *’
636 | yaml_char_t *anchor, yaml_char_t *tag, int implicit,
| ~~~~~~~~~~~~~^~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1:
python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ruamel.yaml.clib
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.12"
returned exit code 13
make: *** [debian/rules:13: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: ruamel.yaml.clib
Source-Version: 0.2.8+ds-2
Done: Michael R. Crusoe <cru...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ruamel.yaml.clib, 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.
Michael R. Crusoe <cru...@debian.org> (supplier of updated ruamel.yaml.clib
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: Wed, 31 Jul 2024 19:00:29 +0200
Source: ruamel.yaml.clib
Architecture: source
Version: 0.2.8+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Michael R. Crusoe <cru...@debian.org>
Closes: 1075453
Changes:
ruamel.yaml.clib (0.2.8+ds-2) unstable; urgency=medium
.
* d/patches/fix-typecasts-s390x.patch: adopted from Fedora to fix
FTBFS with GCC 14. Closes: #1075453
* Standards-Version: 4.6.2 (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
b690e5b53b0956f502c298d040c1448f1ba859df 2236 ruamel.yaml.clib_0.2.8+ds-2.dsc
1e78d3e8a27d9ec54db61f9aa7f4eaadeee3060e 5416
ruamel.yaml.clib_0.2.8+ds-2.debian.tar.xz
f1416ac9844af798aeb63d495ccbf4a3bb6227ae 7383
ruamel.yaml.clib_0.2.8+ds-2_source.buildinfo
Checksums-Sha256:
4c31c82c01bbbfae1623dfd13fbccfdb5eeaeaa84dee7da03979ea3a1567f818 2236
ruamel.yaml.clib_0.2.8+ds-2.dsc
b9fea2074c4775643d7b833e22da9a55499bce8555520c97201818f7dc845011 5416
ruamel.yaml.clib_0.2.8+ds-2.debian.tar.xz
2bf8dedbb7712cf5085e15b6113e59f5a3c5c536e026db6bfc34ce4247506240 7383
ruamel.yaml.clib_0.2.8+ds-2_source.buildinfo
Files:
465949a084c3d16020516bebc838b977 2236 python optional
ruamel.yaml.clib_0.2.8+ds-2.dsc
6dd78efc796d4d4dcafd3c9f9094c338 5416 python optional
ruamel.yaml.clib_0.2.8+ds-2.debian.tar.xz
e6b41befdb358edafd511c5215446ba6 7383 python optional
ruamel.yaml.clib_0.2.8+ds-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmaqbdsACgkQPCZ2P2xn
5uLOgRAAwje/ROYaGOI6rvecjiEJ7Cy9TbzW1dln6V9oBywZqMrW5tocTgpTBplB
52hbrQIjrbqk6fMFZhM1NbxKyxMiqGxR/WqvnpPdbNV22dhlEK1ZXZkLAn2mNAos
eopFXML+Vn+v5B7OsfJlq0aggRsgpEUdEyo9Lhj+S3Lb/qmSh+dT538WpmgwPKT9
uH23DlvTYbZSGOTkkQ4CXVt74KDQILhu2f/qQSwavkmk+YGldlZ24Xi/hiYCSqLw
ybhc4uT8ZuGepSf/pU4qABjC2o65ixSuy+Eo/jwBkqdqmsXgl8+6jp5V+vu0hcyb
z/BB+DVQI1L41Z+m9/Hh71JYvR2zip4wnJPifUjQCq+VSaOD7Pp3qhKhrpBRFuJc
tkoKUC6QfyiNlPV5pGyHvKJ5Llw7N1bcxf+9Qew9do+Ux+nYP7W+J5m6sAf8KATc
QhDPzD6CnB8yRSiKgLL3NSWyuLXiILXOrI1C+Tbk8v4pifv3eze9UfFj77sz6jwS
osnvxsSxu3NRwJoC7LvqUydokios5V/1wnLqjWyKa6X1vO3/SiH1uCZUjJmKwHqZ
Ejohw0+ERx4IR+Hhbv98S5HsZSlqpiZh+A9bl3sWjZxGTks6ONYjPloNU11fKzv+
gWcl8BEwX4sYrJSMvvNRBZ2utwFFwu1hNYcIF3wGzqLN04Ypcio=
=5hms
-----END PGP SIGNATURE-----
pgpyF_Fcstn44.pgp
Description: PGP signature
--- End Message ---
