Your message dated Mon, 17 Jun 2024 14:28:49 +0000
with message-id <e1sjdll-00hiw1...@fasolo.debian.org>
and subject line Bug#1073314: fixed in yaz 5.34.0-2
has caused the Debian Bug report #1073314,
regarding yaz: FTBFS: xmlquery.c:56:23: error: implicit declaration of function
‘atoi’; did you mean ‘atoi_n’? [-Werror=implicit-function-declaration]
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.)
--
1073314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaz
Version: 5.34.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o tokenizer.lo tokenizer.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c http.c -fPIC -DPIC -o .libs/http.o
> xmlquery.c: In function ‘check_diagnostic’:
> xmlquery.c:56:23: error: implicit declaration of function ‘atoi’; did you
> mean ‘atoi_n’? [-Werror=implicit-function-declaration]
> 56 | *error_code = atoi(code_str);
> | ^~~~
> | atoi_n
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o record_conv.lo record_conv.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c mime.c -fPIC -DPIC -o .libs/mime.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c oid_util.c -fPIC -DPIC -o
> .libs/oid_util.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c tokenizer.c -fPIC -DPIC -o
> .libs/tokenizer.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c xmlerror.c -o xmlerror.o
> >/dev/null 2>&1
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c mime.c -o mime.o >/dev/null 2>&1
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c record_conv.c -fPIC -DPIC -o
> .libs/record_conv.o
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o retrieval.lo retrieval.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c oid_util.c -o oid_util.o
> >/dev/null 2>&1
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o elementset.lo elementset.c
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o snprintf.lo snprintf.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c tokenizer.c -o tokenizer.o
> >/dev/null 2>&1
> record_conv.c: In function ‘construct_rdf_lookup’:
> record_conv.c:814:21: error: implicit declaration of function ‘atoi’; did you
> mean ‘atoi_n’? [-Werror=implicit-function-declaration]
> 814 | debug = atoi((const char *) attr->children->content);
> | ^~~~
> | atoi_n
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c retrieval.c -fPIC -DPIC -o
> .libs/retrieval.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c elementset.c -fPIC -DPIC -o
> .libs/elementset.o
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o query-charset.lo query-charset.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/libxml2
> -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c snprintf.c -fPIC -DPIC -o
> .libs/snprintf.o
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o copy_types.lo copy_types.c
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:1120: xmlquery.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/06/15/yaz_5.34.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240615&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: yaz
Source-Version: 5.34.0-2
Done: Hugh McMaster <h...@debian.org>
We believe that the bug you reported is fixed in the latest version of
yaz, 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 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hugh McMaster <h...@debian.org> (supplier of updated yaz 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: Mon, 17 Jun 2024 22:43:08 +1000
Source: yaz
Architecture: source
Version: 5.34.0-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean <vdanj...@debian.org>
Changed-By: Hugh McMaster <h...@debian.org>
Closes: 1058064 1073314
Changes:
yaz (5.34.0-2) unstable; urgency=medium
.
* debian/control:
+ Update my email address.
+ Build-Depend on pkgconf instead of pkg-config.
+ Sort libyaz-dev package dependencies.
+ Remove references to libyaz4-dev.
+ Raise Standards-Version to 4.7.0 (no changes needed).
* debian/copyright: Extend my copyright to 2024.
* debian/patches:
+ Include stdlib.h in several files (Closes: #1073314).
+ Support cross-building with pkg-config (Closes: #1058064).
Thanks to Helmut Grohne for providing a patch.
Checksums-Sha1:
23433e03a3a0608166f264590d1b5a3c4eac31c5 2311 yaz_5.34.0-2.dsc
c0cf9e8b150f51722384f32e370ef04ada9bad89 21720 yaz_5.34.0-2.debian.tar.xz
d5209fe1e6a7b64c634c94c61ad1407eac9c7674 6973 yaz_5.34.0-2_source.buildinfo
Checksums-Sha256:
55798971a621a487bdfde1ab8b313fa2ef9a76decbbf2fd010cee2b8022caf91 2311
yaz_5.34.0-2.dsc
e8d212ad5f6aa27c55d4af3bc7f38d0a9457569d8d9b5ead9dcac24ffb4898bb 21720
yaz_5.34.0-2.debian.tar.xz
10dae5338820e8b4c530f29e1703da7ae574050152bc5dc35ff6629a997b9cab 6973
yaz_5.34.0-2_source.buildinfo
Files:
2f1ba30cb01c6288ea8db2274f1ccab9 2311 utils optional yaz_5.34.0-2.dsc
ca4fbc63e514ba813651fb640b786ed9 21720 utils optional
yaz_5.34.0-2.debian.tar.xz
872778871034ecd6f329daa340abc3cc 6973 utils optional
yaz_5.34.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEOiCBPKV5RoaMUVIRWsYQdMXoG8QFAmZwL+IPHGhtY0BkZWJp
YW4ub3JnAAoJEFrGEHTF6BvEV84QAIbspJS32gp7mueLXlMGI/Q4bmK6Ml/qJHzE
+nAmNYP7rjk7njrfD6mTTMWsr1vQFrzCGU92fvWDvMEHL29pX9ZacylSiiVlA67m
ooc97UaUqnAibDJEBZK+Mu/PU4p6ndiSOIZRghfgVFMTwwba+EfsspJ6IKyX0UIc
XxEOUUTvKXRauem1q/bAcACkK3OZ1D8KazblEN1fKNxzvvMQkf/sHuEOR6PQpttI
c+M7x2JQIDyJLiHzR+Kq74tqnla5V4D+YRJEZbaDf8s4uuZchvCll1yiK6UAu3ah
M0omDAkfTIl57alNth2LsoXH4wqlICTAh2rgpk2Zo0A+IIGtUm/PHSqD+QsACUNI
wxwifo9RCe+nJeb7sWcP7kqU1iDPNjITtOT5Bb1ZVtYL3WGO0QoLH+GXb51hVs5R
Z+NgAdIqyxmBONuPPTlgLupz36oH9HPSkQmp8YNr+sHuy2vVw82eNCdNcNLPmuhc
63Oz1HrhKkrdlB+CvW5qka5tbahiwURbQmxVhlzBfrTj3rOb+ovQLfSJCb8YyriY
T+RX9w5yHZl4sqNrMcbJXgB9zi18AC8WAve7cPwqRCJTKSEgCsJ64GfqpByiEBQk
tqO9MOhRQ1DAS4YJ/BjJfkNCYiTrarXthH/Z8agN+Abkf0NWiHaed+/t7cBRuSPO
7tjA653S
=aru5
-----END PGP SIGNATURE-----
pgpZt7O_vhbeT.pgp
Description: PGP signature
--- End Message ---
