Your message dated Fri, 15 Mar 2024 13:21:17 +0000
with message-id <e1rl7ur-00gtyl...@fasolo.debian.org>
and subject line Bug#1066571: fixed in sane-frontends 1.0.14-18
has caused the Debian Bug report #1066571,
regarding sane-frontends: FTBFS: sanei_init_debug.c:103:17: error: implicit
declaration of function ‘isfdtype’; did you mean ‘isctype’?
[-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.)
--
1066571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sane-frontends
Version: 1.0.14-17
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -Wdate-time
> -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE
> -DPATH_SANE_DATA_DIR=/usr/share/sane -DV_MAJOR=1 -DV_MINOR=0 -DV_BUILD=14
> -DSANE_V_MAJOR=1 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wall sanei_load_values.c
> sanei_wire.c: In function ‘sanei_w_array’:
> sanei_wire.c:213:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 4 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 213 | DBG (0, "sanei_w_array: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 214 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> 215 | MAX_MEM, len * element_size, MAX_MEM + len *
> element_size);
> | ~~~~~~~~~~~~~~~~~~
> | |
> | size_t {aka long unsigned int}
> sanei_wire.c:214:59: note: format string is defined here
> 214 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> | unsigned int
> | %lu
> sanei_wire.c:213:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 213 | DBG (0, "sanei_w_array: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> sanei_wire.c:214:70: note: format string is defined here
> 214 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> |
> unsigned int
> |
> %lu
> sanei_wire.c: In function ‘sanei_w_ptr’:
> sanei_wire.c:291:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 4 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 291 | DBG (0, "sanei_w_ptr: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 292 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> 293 | MAX_MEM, value_size, (w->allocated_memory +
> value_size));
> | ~~~~~~~~~~
> | |
> | size_t {aka long unsigned int}
> sanei_wire.c:292:59: note: format string is defined here
> 292 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> | unsigned int
> | %lu
> sanei_wire.c:291:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 291 | DBG (0, "sanei_w_ptr: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 292 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> 293 | MAX_MEM, value_size, (w->allocated_memory +
> value_size));
> |
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | |
> | size_t
> {aka long unsigned int}
> sanei_wire.c:292:70: note: format string is defined here
> 292 | "exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> |
> unsigned int
> |
> %lu
> sanei_init_debug.c: In function ‘sanei_debug_msg’:
> sanei_init_debug.c:103:17: error: implicit declaration of function
> ‘isfdtype’; did you mean ‘isctype’? [-Werror=implicit-function-declaration]
> 103 | if ( 1 == isfdtype(fileno(stderr), S_IFSOCK) )
> | ^~~~~~~~
> | isctype
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:68: sanei_init_debug.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/sane-frontends_1.0.14-17_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&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: sane-frontends
Source-Version: 1.0.14-18
Done: Jörg Frings-Fürst <debian@jff.email>
We believe that the bug you reported is fixed in the latest version of
sane-frontends, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jörg Frings-Fürst <debian@jff.email> (supplier of updated sane-frontends
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, 13 Mar 2024 20:45:20 +0100
Source: sane-frontends
Architecture: source
Version: 1.0.14-18
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst <debian@jff.email>
Changed-By: Jörg Frings-Fürst <debian@jff.email>
Closes: 1066571
Changes:
sane-frontends (1.0.14-18) unstable; urgency=medium
.
* New debian/patches/0145-ftbfs-impfuncdef.patch.
Fix FTBFS -Werror=implicit-function-declaration (Closes: #1066571).
* debian/copyright
- Add year 2024 to myself.
* debian/control:
- Change to new repository.
Checksums-Sha1:
552048821d1c015a6e9d6d5329258ecb703f46e8 1916 sane-frontends_1.0.14-18.dsc
f0f8db01abe7d09987e6929030998f8f87d883ad 16192
sane-frontends_1.0.14-18.debian.tar.xz
b4ee4e89719cd06192281ef2ac56eb5e6b852888 13902
sane-frontends_1.0.14-18_source.buildinfo
Checksums-Sha256:
514490e0876b0279c4704c3d4eb28f5de28c48c1be8d0f62d4d5071fa866f8a9 1916
sane-frontends_1.0.14-18.dsc
44633fe07b5b04e71ab22f1327ca5e7b4c8b5b3a19b2afbf601703047d4c1638 16192
sane-frontends_1.0.14-18.debian.tar.xz
15e1c8c891df33ac3aad719b63a47bfa57fac8fe4aec6ea0fa9394f4d0ca6dfd 13902
sane-frontends_1.0.14-18_source.buildinfo
Files:
bbb48f6536bb51480c3738dec46628fe 1916 graphics optional
sane-frontends_1.0.14-18.dsc
c15ed20da78f738bfd67883ca366a345 16192 graphics optional
sane-frontends_1.0.14-18.debian.tar.xz
a40e49aeb78e66926387e8c4be3bcad2 13902 graphics optional
sane-frontends_1.0.14-18_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmX0R2wACgkQgNMC9Yht
g5xkzBAAh6HBf2CAH4CGVqR2Jxn5WJ/lL47gz+0mtLjY2FDB3f4eZohZHfEwS8nT
1FljikfCdqGVa4p0zzu8ssjWiGFQhCMVAYmDE5LMwS0tMqHRj+fvD7zXZsF6AChB
YXudTpX523HuGwpgOCgGuIiznS1wslt9o07PL0JCKvF0GSyi9Hw66IycXggJ11E1
oYVkiC7FZsaOclVcMGjU+nVp8mwftRW/ndU+pwLdhKU7uj3sFYuRmv6rm1D5SaXn
+tW4T3HnXmsjn04KSytpsyVn5gs3QvlfLJxe/B23xsv4SRePujMvaTf2RXfPD+BO
thcMcR3K9cwpYB9g2t4vl3rklWZbawKLXVNiYXMJBXiNGPiozTXoORpKRnPHlfrQ
hdOLjLLtKngvi2UEhjCHYbiRN6cauOSdTmTR0/D+LXQTQ0agEfLsAkGyIwbX1yrv
j5C3wOeH/xLRe4cVNGJut7BRV25NT9XyHp/E/h4A8gCFYFu3XSFQhTfO0ai23UNB
ObKRzbh12yP3QR6In6qjW3/WH4atJSuJKefD92lcwCeR9kMPn7RhP1KHgfpt4UYG
VfGqzH10LahoijkDWGbwlhilfyIkwlV6bft4Aod6KxfXmHg1amkwzyZkcbqFcEZC
vWJXBl8etEtlKIFS5+U6r5xwMDEpnGoNeFS31oCOlBTXhyTfdUs=
=UgN8
-----END PGP SIGNATURE-----
pgpCOxZBQgaNb.pgp
Description: PGP signature
--- End Message ---
