Your message dated Fri, 31 May 2024 18:49:11 +0000
with message-id <e1sd7jp-00a33f...@fasolo.debian.org>
and subject line Bug#1066342: fixed in eterm 0.9.6-7.2
has caused the Debian Bug report #1066342,
regarding eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of
function ‘safe_print_string’ [-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.)
--
1066342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eterm
Version: 0.9.6-7.1
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):
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -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 libscream.lo libscream.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include -Wdate-time
> -D_FORTIFY_SOURCE=2 -I/usr/include -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 libscream.c -fPIC -DPIC -o
> .libs/libscream.o
> libscream.c: In function ‘ns_attach_by_URL’:
> libscream.c:1489:2: warning: #warning compiling in libscream [-Wcpp]
> 1489 | #warning compiling in libscream
> | ^~~~~~~
> libscream.c:1495:2: warning: #warning compiling in support for GNU screen
> [-Wcpp]
> 1495 | #warning compiling in support for GNU screen
> | ^~~~~~~
> In file included from feature.h:100,
> from libscream.c:46:
> libscream.c: In function ‘ns_parse_screen’:
> libscream.c:3231:16: error: implicit declaration of function
> ‘safe_print_string’ [-Werror=implicit-function-declaration]
> 3231 | safe_print_string(p, width)));
> | ^~~~~~~~~~~~~~~~~
> libscream.c:3230:5: note: in expansion of macro ‘D_ESCREEN’
> 3230 | D_ESCREEN(("ns_parse_screen(0x%08x, %d, %d, \"%s\")\n", screen,
> force, width,
> | ^~~~~~~~~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:632: libscream.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/eterm_0.9.6-7.1_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: eterm
Source-Version: 0.9.6-7.2
Done: Chris Hofstaedtler <z...@debian.org>
We believe that the bug you reported is fixed in the latest version of
eterm, 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.
Chris Hofstaedtler <z...@debian.org> (supplier of updated eterm 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: Fri, 31 May 2024 20:22:04 +0200
Source: eterm
Architecture: source
Version: 0.9.6-7.2
Distribution: unstable
Urgency: medium
Maintainer: José Antonio Jiménez Madrid <donjosemad...@gmail.com>
Changed-By: Chris Hofstaedtler <z...@debian.org>
Closes: 1066342
Changes:
eterm (0.9.6-7.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Apply patch from Steve Langasek <steve.langa...@canonical.com> to fix
FTBFS. (Closes: #1066342)
Checksums-Sha1:
36ca8a27c4f9fb21b303cb97a044d89019aa54b5 1873 eterm_0.9.6-7.2.dsc
cf75a9c2efa57c771d1567c19b5bc59f7229c7b6 14360 eterm_0.9.6-7.2.debian.tar.xz
15a28a6be22a8b61022ed182371b2ce6b4b99f8b 12270 eterm_0.9.6-7.2_arm64.buildinfo
Checksums-Sha256:
bc8c092a3317d9677f8f6ab28f7f1a99a87184d73482b6284d5fbf5ccf6aef3e 1873
eterm_0.9.6-7.2.dsc
63c62776408c486c1477760d13bf288b3554795317368eecbfab24cfe2c6e806 14360
eterm_0.9.6-7.2.debian.tar.xz
77107a730e323e624522ccdfef21f817ab24b36c08ba1cfe6de145b0432a1c58 12270
eterm_0.9.6-7.2_arm64.buildinfo
Files:
be1275e4e43c6620b2c61089d1b492e7 1873 x11 optional eterm_0.9.6-7.2.dsc
a912e33cc0655c7fa01d073fd1b6dde1 14360 x11 optional
eterm_0.9.6-7.2.debian.tar.xz
94caf8276c0f50f0e3924372d738bd57 12270 x11 optional
eterm_0.9.6-7.2_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZaFqoACgkQXBPW25MF
LgMusxAAhIuy8jCBUGzWZMF6qVG/AovhJ2jSPumMgElOiyh8vwpEcgD6Zi9DcrdP
WLBT4KvsxpXznXZMTofehCjY1viRAI60JSUmP+V1zhIsLR9qX5bX+ATLWZG4Dn9W
BHZOTIizWwM75p3RPHBgWsR12KNdXOHOM1ApBlSEr03vU5yVBaCnIe8eLGIfO16T
CA4o2Vozc+gB2+YFEEVG4C0SvIDqBlXIWTbrhsMWnE0G/VPalJIUqK+1e9x4B1VD
6bseZ8T7jLbnt0st+iD8MFZE0fFWfSk8rGbsIgT9vRH6VDxQQMFmFunkUQ4D0ayf
e/BI5mtu8YqYXxGkA2QH3cXxvs2hziczQfKTxPxhllOnHedC96Salkh1glLoY/bg
IFkOAOX1O5STmhM+FMw9lwJG+tcNsB32TmjwK4ACQYpjtTwceeIAXn7wCqTmMIqi
9zIAntusig5gthSinVIX3MRwu8ToJUEd60ZkP1M44Uh69KfZPw928H12OMxi40Mg
YOn6ZN7qeha6bt/JjuOYr8iCG6wa1ItaqhTEwWNQ8UYC6yBU4IJrzp+dLRvvIwcL
c/MnRG+QgUQpxE34uJvOIPDuxZmaEpdttuRRChHleHsGlq+F+9Dc/XJj28njtaOc
fHsmo0o+KY7jVyM5lWiorRb1WeXi8dAy/O87+K70QM1e5nG62zg=
=ZTah
-----END PGP SIGNATURE-----
pgp1APofTubsK.pgp
Description: PGP signature
--- End Message ---
