Your message dated Mon, 15 Apr 2024 17:50:05 +0000
with message-id <e1rwqsz-005dvq...@fasolo.debian.org>
and subject line Bug#1066970: fixed in esnacc 1.8.1-4
has caused the Debian Bug report #1066970,
regarding FTBFS: error: implicit declaration of function 'InitNibbleMem' 
[-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.)


-- 
1066970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: esnacc
Version: 1.8.1-3
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-impfuncdef

Hi,

esnacc FTBFS:

gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -c -o c-examples/simple/sbuf-sbuf-ex.o `test -f 'c-examples/simple/sbuf-ex.c' || echo './'`c-examples/simple/sbuf-ex.c /bin/bash ./libtool --tag=CC --mode=link gcc -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -Wl,-z,relro -o c-examples/simple/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o c-examples/simple/sbuf-sbuf-ex.o c-lib/libcasn1.la -lm libtool: link: gcc -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -Wl,-z -Wl,relro -o c-examples/simple/.libs/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o c-examples/simple/sbuf-sbuf-ex.o c-lib/.libs/libcasn1.so -lm -pthread gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -c -o c-examples/test-lib/testlib-test-lib.o `test -f 'c-examples/test-lib/test-lib.c' || echo './'`c-examples/test-lib/test-lib.c
c-examples/test-lib/test-lib.c: In function 'main':
c-examples/test-lib/test-lib.c:68:5: error: implicit declaration of function 'InitNibbleMem' [-Werror=implicit-function-declaration]
   68 |     InitNibbleMem (256, 256);
      |     ^~~~~~~~~~~~~
[...]

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

Indeed a build with export DEB_BUILD_MAINT_OPTIONS=qa=-bug-implicit-func works. But better than disabling it would be to fix it of course ;)

Regards,

Rene

--- End Message ---
--- Begin Message ---
Source: esnacc
Source-Version: 1.8.1-4
Done: Andreas Beckmann <a...@debian.org>

We believe that the bug you reported is fixed in the latest version of
esnacc, 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.
Andreas Beckmann <a...@debian.org> (supplier of updated esnacc 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: Mon, 15 Apr 2024 19:35:47 +0200
Source: esnacc
Architecture: source
Version: 1.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Closes: 1011071 1044667 1066970
Changes:
 esnacc (1.8.1-4) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
     (Closes: #1066970)
   * Fix building twice in a row.  (Closes: #1044667)
   * esnacc-doc: Do not recommend evince.  (Closes: #1011071)
   * Declare Rules-Requires-Root: no.
   * CI: Allow the reprotest to fail due to libeoffice #1065448.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
     + libesnacc-dev: Add Multi-Arch: same.
Checksums-Sha1:
 fc4d4525b8014f90334758183a9d1584afb92be5 2121 esnacc_1.8.1-4.dsc
 2681312d536bf62f68fcc887c6927e8f2e08f96e 11084 esnacc_1.8.1-4.debian.tar.xz
 3634445bc8fa71d7e5f969ef18904db90a654302 5870 esnacc_1.8.1-4_source.buildinfo
Checksums-Sha256:
 0c3d45d5f01a55409cbae6f38e947d8edeaf011a65535566012bc46f75d3ba02 2121 
esnacc_1.8.1-4.dsc
 c9410bda41832825db2b47d78a23729e0a1b4003aa32dd241f2a84a6ca718498 11084 
esnacc_1.8.1-4.debian.tar.xz
 7989ac997002845ab99f03a542e67312a692263726a3bbce464e75594d44298b 5870 
esnacc_1.8.1-4_source.buildinfo
Files:
 2c67d113fea50ff0dafc796fbba4d798 2121 devel optional esnacc_1.8.1-4.dsc
 a3008e8f740bc424f8828023ae4d1a8a 11084 devel optional 
esnacc_1.8.1-4.debian.tar.xz
 c23a242a2fc6c94605a758ccaf734828 5870 devel optional 
esnacc_1.8.1-4_source.buildinfo

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

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdZcwQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCO8iD/4zTJn++OCwI8HRB8DtapNzQV0pE5w+/g/4
V4a5oVdLhHQrr2qakAxfagn2F4CzUtl+kbBPB9SnrndE6OZmEXn30qB9E4CDrMaU
LfaTFSNhGP5wIW/XN3+ZuF0JxB7NjBCqaFlH/cAdJhOAjQvaNJXvIl7Sn4rw9Ttl
In/IvRU1wLEm2omSmJ9eG2VilCulApTPy6BRBwlmpSsqDacqXEM4KRtF2jeHu4n7
9h2lll9JiDypmnbsOhOiBcFaau49xJWu+ccZ+FJjNEcCI7/hyEw289MKnLhnlLQb
6wGUb1leZtNWqg264NKHR1UKir1YHtpM5u44h+rCNE47oOqTBCWfpMq43tPYCwyr
kfEsq0CFGEVV0JQvfifxs3EMDAjnnpZZm5AzGSER2bDClEDRAx/cDst7ATZlQsw/
X3HNob1pyT9l9Js16m0WRENSIFlib/mJaBgqDiUVuGF9vdnZ6i+KlCkcIqL/lgiQ
m/uj9kljdbd2/fzLAUcffqHMsxbNi0FQTXuwc53GqZOcKZoWbAVBS8JjFlxYOP3J
P08/KFAXbGOgE1XsdlCP7Z2glq/xzUhg2MULwmRwcH+MGzWvBCGtuSSaa3wMKFfu
Dyh4Mf6msZaUpG57IfHcowHhvVrymMhcEu3UW9aab3WxndD1wySv0z7rvDdImxgD
8sit1llljg==
=tRuP
-----END PGP SIGNATURE-----

Attachment: pgpNlXEfdC5rQ.pgp
Description: PGP signature


--- End Message ---

Reply via email to