[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1037613: marked as done (cups-bjnp: ftbfs with GCC-13)



Your message dated Fri, 18 Aug 2023 20:18:17 +0000
with message-id <E1qX5vF-00D8kz-I1@fasolo.debian.org>
and subject line Bug#1037613: fixed in cups-bjnp 2.0.3-4.1
has caused the Debian Bug report #1037613,
regarding cups-bjnp: ftbfs with GCC-13
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 owner@bugs.debian.org
immediately.)


-- 
1037613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037613
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:cups-bjnp
Version: 2.0.3-4
Severity: normal
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-13

[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-13/g++-13, but succeeds to build with gcc-12/g++-12. 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/2023/05/22/logs/cups-bjnp_2.0.3-4_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking types of arguments for select... int,fd_set *,struct timeval *
checking for string.h... (cached) yes
checking for fcntl.h... yes
checking for arpa/inet.h... yes
checking for netdb.h... yes
checking for netinet/in.h... yes
checking for sys/socket.h... (cached) yes
checking for sys/time.h... yes
checking for sys/timeb.h... yes
checking for wchar.h... yes
checking for cups/cups.h... yes
checking for cups/backend.h... yes
checking for cups/http.h... yes
checking for sys/types.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for arpa/nameser.h... yes
checking for netdb.h... (cached) yes
checking for resolv.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_build
	make -j8
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make  all-am
make[2]: Entering directory '/<<PKGBUILDDIR>>'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp.o `test -f 'bjnp.c' || echo './'`bjnp.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-runloop.o `test -f 'bjnp-runloop.c' || echo './'`bjnp-runloop.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-io.o `test -f 'bjnp-io.c' || echo './'`bjnp-io.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-debug.o `test -f 'bjnp-debug.c' || echo './'`bjnp-debug.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-utils.o `test -f 'bjnp-utils.c' || echo './'`bjnp-utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-discover.o `test -f 'bjnp-discover.c' || echo './'`bjnp-discover.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-commands.o `test -f 'bjnp-commands.c' || echo './'`bjnp-commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall  -Werror  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bjnp-bjnp-levels.o `test -f 'bjnp-levels.c' || echo './'`bjnp-levels.c
In function ‘strstrtok’,
    inlined from ‘report_ink_status_messages’ at bjnp-levels.c:451:13,
    inlined from ‘bjnp_report_levels’ at bjnp-levels.c:653:12:
bjnp-levels.c:307:14: error: storing the address of local variable ‘warnings’ in ‘next’ [-Werror=dangling-pointer=]
  307 |         next = in;
      |         ~~~~~^~~~
bjnp-levels.c: In function ‘bjnp_report_levels’:
bjnp-levels.c:434:10: note: ‘warnings’ declared here
  434 |     char warnings[BJNP_ARG_MAX];
      |          ^~~~~~~~
bjnp-levels.c:302:18: note: ‘next’ declared here
  302 |     static char *next = NULL;
      |                  ^~~~
cc1: all warnings being treated as errors
make[2]: *** [Makefile:570: bjnp-bjnp-levels.o] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:333: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: cups-bjnp
Source-Version: 2.0.3-4.1
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
cups-bjnp, 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 1037613@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated cups-bjnp 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 04 Aug 2023 21:07:31 +0300
Source: cups-bjnp
Architecture: source
Version: 2.0.3-4.1
Distribution: unstable
Urgency: low
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1037613
Changes:
 cups-bjnp (2.0.3-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Don't build with -Werror. (Closes: #1037613)
Checksums-Sha1:
 50783ef30c8556208543d12cfe3d91cd77af9d1b 1982 cups-bjnp_2.0.3-4.1.dsc
 5eadaa364488cc3c26a201897cd43ee7fe0906d1 140764 cups-bjnp_2.0.3.orig.tar.gz
 017d4a38b9447cc70d61dc55e4efa2a067004936 4632 cups-bjnp_2.0.3-4.1.debian.tar.xz
Checksums-Sha256:
 23ecde6fba9c32898d3f28fc4b774622db1edaf4b696f49ef58919abf73b23ed 1982 cups-bjnp_2.0.3-4.1.dsc
 c914b2fd9d8e26ce22f2df6244d9defeec31ee9a5360f723eecb3b00f2168500 140764 cups-bjnp_2.0.3.orig.tar.gz
 0fc13ff767313a56b5c74c581c45a5c3e9aa896e8c8ac9e78f720ac1214623a0 4632 cups-bjnp_2.0.3-4.1.debian.tar.xz
Files:
 ceacc690da3b781e34e054e4dcfb3cec 1982 text optional cups-bjnp_2.0.3-4.1.dsc
 1d5a1588f3649ce7c5758cbea5a86900 140764 text optional cups-bjnp_2.0.3.orig.tar.gz
 2ff65ce28e10c52af523d386fc74f937 4632 text optional cups-bjnp_2.0.3-4.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmTNPyIACgkQiNJCh6LY
mLF8cQ//YNKCPPHeF9cD+FLsqUfeAFHfJsGqqfOLKw1GhUNkqYZ4IaX3xoYzm3rr
e+iG0H5fQ+wSDseuZU9UVvDKRFZximhLr7mDmCCJGEPfIHHNchyGlH9BhHZiwKFG
gAofVTrx8BCp2AOFaItwD1H2FgDbHgTHE1LqFz1y/WzlZxKZoHd8gIQ3EK4ncikj
FpLaGz5oj4HdN/5fCS24EPHPnwKBD8IvctbfmljAQQSkrh4tIe3QXD+XDE7DEOgx
JGjzGy6yV6bNljex1z0amLt84RI+5Kd0LKi1VLyoNUJrGDzl5pj3BnfvNalxGPp7
Jy6FrN8Outoz8G9CNvWrLfJKiH0NlhS+GGbtWTgWnCjvdKDAbD8wPrkuznOqihRS
cIi0aiDNHi0lY3EHOCF/BeTIHWR8O4yAXSkvrzCAyrg5X7VqB5cxvojuGQs8Td4q
NT/eQMc5qvRwh0EiftSax8oB7z4+Z3chAGqaAfDvaaKEF3jRYvWSkp/2Yjf/VBrU
mdMl9DyxAiu1D4lmfhhrtGhIKOcFc61mK8iy0zRoiM9gytJvLKNec6pg4U8XuM8Q
BD7gBlDasxB8+y4pMLTbikYY4H0PIALwH+B9h1GUKyP3dccWPMhuYzmy+NSMS3bE
YCv7NItVhpFHUekPB+th8ObUH/lQfAmoFoGeKBYSz7BF0VY5DgA=
=CKMo
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: