Your message dated Fri, 19 Apr 2024 18:02:56 +0000
with message-id <e1rxszc-007caz...@fasolo.debian.org>
and subject line Bug#1066005: fixed in epic4 1:2.10.10-1.1
has caused the Debian Bug report #1066005,
regarding epic4: FTBFS on arm{el,hf}: gailib.c:95:17: error: implicit
declaration of function ‘strlcpy’; did you mean ‘strncpy’?
[-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.) -- 1066005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: epic4 Version: 1:2.10.10-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=epic4&arch=armhf&ver=1%3A2.10.10-1%2Bb5&stamp=1709806588&raw=0 gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I./../include -I../include -c gailib.c gailib.c: In function ‘get_name’: gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] 95 | strlcpy((ai)->ai_canonname, (str), strlen(str) + 1);\ | ^~~~~~~ gailib.c:426:17: note: in expansion of macro ‘GET_CANONNAME’ 426 | GET_CANONNAME(cur, hp->h_name); | ^~~~~~~~~~~~~ cc1: some warnings being treated as errors make[2]: *** [Makefile:31: gailib.o] Error 1 Cheers -- Sebastian Ramacher
--- End Message ---
--- Begin Message ---Source: epic4 Source-Version: 1:2.10.10-1.1 Done: Bastian Germann <b...@debian.org> We believe that the bug you reported is fixed in the latest version of epic4, 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. Bastian Germann <b...@debian.org> (supplier of updated epic4 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: Fri, 19 Apr 2024 18:46:14 +0200 Source: epic4 Architecture: source Version: 1:2.10.10-1.1 Distribution: unstable Urgency: medium Maintainer: Kurt Roeckx <k...@roeckx.be> Changed-By: Bastian Germann <b...@debian.org> Closes: 1066005 Changes: epic4 (1:2.10.10-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix implicit function declarations. (Closes: #1066005) Checksums-Sha1: 633d799c5558322f158bd31b1bbd6640fc924481 1581 epic4_2.10.10-1.1.dsc 3cd9e2d20facc3efc1e7a4e27e450708c3bb1f3b 16916 epic4_2.10.10-1.1.debian.tar.xz 77fd295b6c9794683e830330640d73039aaa2a97 5553 epic4_2.10.10-1.1_source.buildinfo Checksums-Sha256: 3425a3bf75cd3466281d49fb0d9a001028e9c4e6cf82e253f8f36a09cc7018f0 1581 epic4_2.10.10-1.1.dsc 391b0e6afe386f05f6b0f05063fff2ef71fab5f45d565f559a4ccd806df83e28 16916 epic4_2.10.10-1.1.debian.tar.xz 9e631a755a7e7eea2c05615934a7c5e9f123285e0453966ebbb8ebaef4cda8e3 5553 epic4_2.10.10-1.1_source.buildinfo Files: 5ecef19a6b0f9f5970479d5557a42dd3 1581 net optional epic4_2.10.10-1.1.dsc 6f05c79acf0ab6e8a712cbdae46f613f 16916 net optional epic4_2.10.10-1.1.debian.tar.xz 6c26c9442905c2456480d17bea4e18ac 5553 net optional epic4_2.10.10-1.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYioIIQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFDKgC/9KxUQyDzbIjIJxTMJHug+6qeFpYdK3+/fF 7W5WW4Q2/4d/YLa8zRkGaOHeIxee6EkEqJeAQ3X77XYrFCX8B170kYegGJlHMTRM 9DEKE7r/IjvnktWOnfJyfTf5KX4tXtIx7WVxIvdEC5ne87KT02oM8lzN2Xt3068E HyKq8bcDgVEmOeN4PqqBGlBKN8JQ6qm6pvi8MQMFOxDLXENIltNESKiD9MlPlUF/ sYlhtvP6lKVVW8waDHlief87V/grCO2HUhjRb+quztLCmc0FZ938r5q9WT2rU3hF +2ApnndTWepkKlZoaJoG09ltaaeP6oKjqR3ZzEeqPqFMAq3yoStlTGFjxobErgNT MkkZJfpYBMy6Qh/8huZHf9QObqmrH80ULvjPW2W0ptYQHg+ltw16wlXu5+59Wmxj SbdiXqDmFk7duyt/0ggLdHxosMee3U+3DBHbyjPLm4Z9vhoCGPHyBICSI6OTqaHJ CQmj7VymBxTquPIjc+Fnk/JUHwDX9XQ= =A66a -----END PGP SIGNATURE-----
pgp0jGQIg0wby.pgp
Description: PGP signature
--- End Message ---
