Bug#1066836: libcamera: ftbfs with 64-bit time_t
Package: libcamera Version: 0.2.0-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Dear maintainers, libcamera fails to build from source on 32-bit architectures under 64-bit time_t, because it has a module that legitimately un-sets _FILE_OFFSET_BITS for building but this is not allowed without also unsetting _TIME_BITS: [...] [267/430] c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move -Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp FAILED: src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o c++ -Isrc/v4l2/v4l2-compat.so.p -Isrc/v4l2 -I../src/v4l2 -Iinclude -I../include -Iinclude/libcamera/ipa -Iinclude/libcamera -fdiagnostics-color=always -Wall -Winvalid-pch -Wextra -Werror -std=c++17 -Wno-redundant-move -Wno-psabi -Wshadow -include /<>/obj-arm-linux-gnueabihf/config.h -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/libcamera-0.2.0-1ubuntu3 -Wno-error -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -DLIBCAMERA_BASE_PRIVATE -U_FILE_OFFSET_BITS -D_FILE_OFFSET_BITS=32 -D_LARGEFILE64_SOURCE -fvisibility=hidden -MD -MQ src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -MF src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o.d -o src/v4l2/v4l2-compat.so.p/v4l2_camera.cpp.o -c ../src/v4l2/v4l2_camera.cpp In file included from /usr/include/features.h:394, from /usr/include/arm-linux-gnueabihf/c++/13/bits/os_defines.h:39, from /usr/include/arm-linux-gnueabihf/c++/13/bits/c++config.h:679, from /usr/include/c++/13/bits/requires_hosted.h:31, from /usr/include/c++/13/deque:60, from ../src/v4l2/v4l2_camera.h:10, from ../src/v4l2/v4l2_camera.cpp:8: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ [...] (https://launchpad.net/ubuntu/+source/libcamera/0.2.0-1ubuntu3/+build/27902670) Since this is a legitimate un-setting of _FILE_OFFSET_BITS in order to get access to the necessary libc6 prototypes and macros, and since the functions being intercepted are not sensitive to time_t, the simplest solution is to also unset _TIME_BITS. Please see the attached patch, which has been uploaded to Ubuntu to fix this build failure. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru libcamera-0.2.0/debian/control libcamera-0.2.0/debian/control --- libcamera-0.2.0/debian/control 2024-01-17 13:27:50.0 -0800 +++ libcamera-0.2.0/debian/control 2024-03-13 22:27:39.0 -0700 @@ -1,7 +1,6 @@ Source: libcamera Priority: optional -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Debian Multimedia Maintainers +Maintainer: Debian Multimedia Maintainers Uploaders: Emmanuel Arias , IOhannes m zmölnig (Debian/GNU) , Andrej Shadura , diff -Nru libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch --- libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch 1969-12-31 16:00:00.0 -0800 +++ libcamera-0.2.0/debian/patches/64-bit-time-t-compat.patch 2024-03-13 22:27:33.0 -0700 @@ -0,0 +1,21 @@ +Description: 64-bit time_t compatibility for v4l2 module + The v4l2 build unsets _FILE_OFFSET_BITS, which is not allowed when setting + _TIME_BITS=64. Having verified that nothing in this module is sensitive to + 64-bit time_t (none of the functions it intercepts handle time), we also + unset _TIME_BITS to allow this to build as before. +Author: Steve Langasek +Forwarded: no +Last-Update: 2024-03-13 + +Index: libcamera-0.2.0/src/v4l2/meson.build
Bug#1066792: marked as done (rocblas: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/clang++-15')
Your message dated Thu, 14 Mar 2024 05:12:06 + with message-id and subject line Bug#1066792: fixed in rocblas 5.5.1+dfsg-5 has caused the Debian Bug report #1066792, regarding rocblas: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/clang++-15' 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.) -- 1066792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rocblas Version: 5.5.1+dfsg-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DROCM_SYMLINK_LIBS=OFF > -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF > -DAMDGPU_TARGETS="gfx803;gfx900;gfx906:xnack-;gfx908:xnack-;gfx90a:xnack+;gfx90a:xnack-;gfx1010;gfx1030" > -DROCBLAS_TENSILE_LIBRARY_DIR=/usr/lib/x86_64-linux-gnu/rocblas/2.47.0 > -DTensile_TEST_LOCAL_PATH="../tensile" -DTensile_LOGIC=asm_full > -DTensile_LIBRARY_FORMAT=msgpack -DTensile_LAZY_LIBRARY_LOADING=OFF > -DTensile_SEPARATE_ARCHITECTURES=OFF -DRUN_HEADER_TESTING=OFF > -DBUILD_CLIENTS_TESTS=ON > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_CXX_COMPILER=hipcc > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release > -DROCM_SYMLINK_LIBS=OFF -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF > -DAMDGPU_TARGETS=gfx803\;gfx900\;gfx906:xnack-\;gfx908:xnack-\;gfx90a:xnack\+\;gfx90a:xnack-\;gfx1010\;gfx1030 > -DROCBLAS_TENSILE_LIBRARY_DIR=/usr/lib/x86_64-linux-gnu/rocblas/2.47.0 > -DTensile_TEST_LOCAL_PATH=../tensile -DTensile_LOGIC=asm_full > -DTensile_LIBRARY_FORMAT=msgpack -DTensile_LAZY_LIBRARY_LOADING=OFF > -DTensile_SEPARATE_ARCHITECTURES=OFF -DRUN_HEADER_TESTING=OFF > -DBUILD_CLIENTS_TESTS=ON .. > Re-run cmake no build system arguments > -- The CXX compiler identification is Clang 17.0.6 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/hipcc - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Use hip-clang to build for amdgpu backend > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success > -- Found Threads: TRUE > -- Found Python3: /usr/bin/python3 (found version "3.11.8") found components: > Interpreter > -- OS detected is debian > -- Performing Test COMPILER_HAS_TARGET_ID_gfx803 > -- Performing Test COMPILER_HAS_TARGET_ID_gfx803 - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx900 > -- Performing Test COMPILER_HAS_TARGET_ID_gfx900 - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx906_xnack_off > -- Performing Test COMPILER_HAS_TARGET_ID_gfx906_xnack_off - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx908_xnack_off > -- Performing Test COMPILER_HAS_TARGET_ID_gfx908_xnack_off - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_on > -- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_on - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_off > -- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_off - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx1010 > -- Performing Test COMPILER_HAS_TARGET_ID_gfx1010 - Success > -- Performing Test COMPILER_HAS_TARGET_ID_gfx1030 > -- Performing Test COMPILER_HAS_TARGET_ID_gfx1030 - Success > -- The C compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- hip::amdhip64 is SHARED_LIBRARY > -- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS > -- Perfor
Bug#1066430: marked as done (namazu2: FTBFS: ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp')
Your message dated Thu, 14 Mar 2024 05:06:58 + with message-id and subject line Bug#1066430: fixed in namazu2 2.0.21-24 has caused the Debian Bug report #1066430, regarding namazu2: FTBFS: ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp' 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.) -- 1066430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: namazu2 Version: 2.0.21-23 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wl,-z,relro > -Wl,-z,now -o namazu.cgi form.o namazu.o output.o rcfile.o charset.o result.o > usage.o cgi.o namazu-cgi.o ../nmz/libnmz.la ../lib/libnmzut.a -lm > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu.cgi form.o > namazu.o output.o rcfile.o charset.o result.o usage.o cgi.o namazu-cgi.o > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu form.o > namazu.o output.o rcfile.o charset.o result.o usage.o namazu-cmd.o > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp' > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/namazu2_2.0.21-23_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: namazu2 Source-Version: 2.0.21-24 Done: NOKUBI Takatsugu We believe that the bug you reported is fixed in the latest version of namazu2, 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. NOKUBI Takatsugu (supplier of updated namazu2 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: Thu, 14 Mar 2024 04:36:00 + Source: namazu2 Architecture: source Version: 2.0.21-24 Distribution: unstable Urgency: medium Maintainer: NOKUBI Takatsugu Changed-By: NOKUBI Takatsugu Closes: 1066430 Changes: namazu2 (2.0.21-24) unstable; urgency=medium . * Remove -Werror=implicit-function-declaration flag on configure (Closes: #1066430) Checksums-Sha1: bf799842cd23e45e4f72eec0fe82ef5d79625aae 2175 namazu2_2.0.21-24.dsc b6e01a6cd454018caa72987fb11747c289e6e710 16380 namazu2_2.0.21-24.debian.tar.xz b137d7ff6384515a777f70f22098a43766156083 7435 namazu2_2.0.21-24_source.buildinfo Checksums-Sha256: 03e2bd396874c778dcf27040379cfd9c69798c7113583a69abbe9c30a626db8b 2175 namazu2_2.0.
Bug#1057549: marked as done (crowdsec: FTBFS: FAIL: TestOneShot/permission_denied)
Your message dated Thu, 14 Mar 2024 04:50:55 + with message-id and subject line Bug#1057549: fixed in crowdsec 1.4.6-7 has caused the Debian Bug report #1057549, regarding crowdsec: FTBFS: FAIL: TestOneShot/permission_denied 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.) -- 1057549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:crowdsec Version: 1.4.6-6 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- -ldflags '-s -w -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Version=v1.4.6-6 -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Tag=debian -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Codename=alphaga -X github.com/crowdsecurity/crowdsec/pkg/cwversion.BuildDate=2023-07-14_18:54:27 ' cd _build && go install -trimpath -v -p 2 -ldflags "-s -w -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Version=v1.4.6-6 -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Tag=debian -X github.com/crowdsecurity/crowdsec/pkg/cwversion.Codename=alphaga -X github.com/crowdsecurity/crowdsec/pkg/cwversion.BuildDate=2023-07-14_18:54:27 " github.com/crowdsecurity/crowdsec/cmd/crowdsec github.com/crowdsecurity/crowdsec/cmd/crowdsec-cli github.com/crowdsecurity/crowdsec/pkg/acquisition github.com/crowdsecurity/crowdsec/pkg/acquisition/configuration github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/cloudwatch github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/docker github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/file github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/journalctl github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/kinesis github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/syslog github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/syslog/internal/parser/rfc3164 github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/syslog/internal/parser/rfc5424 github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/syslog/internal/parser/utils github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/syslog/internal/server github.com/crowdsecurity/crowdsec/pkg/acquisition/modules/wineventlog github.com/crowdsecurity/crowdsec/pkg/apiclient github.com/crowdsecurity/crowdsec/pkg/apiserver github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers/v1 github.com/crowdsecurity/crowdsec/pkg/apiserver/middlewares/v1 github.com/crowdsecurity/crowdsec/pkg/csconfig github.com/crowdsecurity/crowdsec/pkg/csplugin github.com/crowdsecurity/crowdsec/pkg/csprofiles github.com/crowdsecurity/crowdsec/pkg/cstest github.com/crowdsecurity/crowdsec/pkg/cwhub github.com/crowdsecurity/crowdsec/pkg/cwversion github.com/crowdsecurity/crowdsec/pkg/database github.com/crowdsecurity/crowdsec/pkg/database/ent github.com/crowdsecurity/crowdsec/pkg/database/ent/alert github.com/crowdsecurity/crowdsec/pkg/database/ent/bouncer github.com/crowdsecurity/crowdsec/pkg/database/ent/decision github.com/crowdsecurity/crowdsec/pkg/database/ent/enttest github.com/crowdsecurity/crowdsec/pkg/database/ent/event github.com/crowdsecurity/crowdsec/pkg/database/ent/hook github.com/crowdsecurity/crowdsec/pkg/database/ent/machine github.com/crowdsecurity/crowdsec/pkg/database/ent/meta github.com/crowdsecurity/crowdsec/pkg/database/ent/migrate github.com/crowdsecurity/crowdsec/pkg/database/ent/predicate github.com/crowdsecurity/crowdsec/pkg/database/ent/runtime github.com/crowdsecurity/crowdsec/pkg/database/ent/schema github.com/crowdsecurity/crowdsec/pkg/exprhelpers github.com/crowdsecurity/crowdsec/pkg/hubtest github.com/crowdsecurity/crowdsec/pkg/leakybucket github.com/crowdsecurity/crowdsec/pkg/metabase github.com/crowdsecurity/crowdsec/pkg/models github.com/crowdsecurity/crowdsec/pkg/parser github.com/crowdsecurity/crowdsec/pkg/protobufs github.com/crowdsecurity/crowdsec/pkg/time/rate github.com/crowdsecurity/crowdsec/pkg/types
Bug#1066430: namazu2: FTBFS: ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'
On Wed, 13 Mar 2024 13:03:57 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2
> > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> > -fstack-protector-strong -fstack-clash-protection -Wformat
> > -Werror=format-security -fcf-protection -Wall -pedantic -Wl,-z,relro
> > -Wl,-z,now -o namazu.cgi form.o namazu.o output.o rcfile.o charset.o
> > result.o usage.o cgi.o namazu-cgi.o ../nmz/libnmz.la ../lib/libnmzut.a -lm
> > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu.cgi form.o
> > namazu.o output.o rcfile.o charset.o result.o usage.o cgi.o namazu-cgi.o
> > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm
> > libtool: link: gcc -g -O2 -Werror=implicit-function-declaration
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> > -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/namazu form.o
> > namazu.o output.o rcfile.o charset.o result.o usage.o namazu-cmd.o
> > ../nmz/.libs/libnmz.so ../lib/libnmzut.a -lm
> > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'
> > /usr/bin/ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'
> > collect2: error: ld returned 1 exit status
It was caused by configure script, checking memcmp function:
conftest.c:72:5: note: include '' or provide a declaration of 'exit'
cc1: some warnings being treated as errors
configure:15824: $? = 1
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "namazu"
| #define PACKAGE_TARNAME "namazu"
| #define PACKAGE_VERSION "2.0.21"
| #define PACKAGE_STRING "namazu 2.0.21"
| #define PACKAGE_BUGREPORT "bug-nam...@namazu.org"
| #define PACKAGE_URL ""
| #define PACKAGE "namazu"
| #define VERSION "2.0.21"
| #define MAILING_ADDRESS "bug-nam...@namazu.org"
| #define TRAC_URI "http://www.namazu.org/trac-namazu/trac.cgi;
| #define COPYRIGHT "Copyright (C) 1997-1999 Satoru Takabayashi All
rights reserved.\nCopyright (C) 2000-2011 Namazu Project All rights
reserved."
| #define HAVE_STDIO_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_PARAM_H 1
| #define STDC_HEADERS 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define ENABLE_NLS 1
| #define HAVE_GETTEXT 1
| #define HAVE_DCGETTEXT 1
| #define HAVE_LC_MESSAGES 1
| #define HAVE_LIBM 1
| #define HAVE_FCNTL_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_MALLOC_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STRING_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_ERRNO_H 1
| #define SIZEOF_INT 4
| #define SIZEOF_LONG 8
| #define SIZEOF_LONG_LONG 8
| #define HAVE_ALLOCA_H 1
| #define HAVE_ALLOCA 1
| #define HAVE_GETPAGESIZE 1
| #define HAVE_VPRINTF 1
| #define HAVE_MMAP 1
| /* end confdefs.h. */
|
| main()
| {
| /* Some versions of memcmp are not 8-bit clean. */
| char c0 = 0x40, c1 = 0x80, c2 = 0x81;
| if (memcmp(, , 1) >= 0 || memcmp(, , 1) >= 0)
| exit (1);
|
| /* The Next x86 OpenStep bug shows up only when comparing 16 bytes
| or more and with at least one buffer not starting on a 4-byte boundary.
| William Lewis provided this test program. */
| {
| char foo[21];
| char bar[21];
| int i;
| for (i = 0; i < 4; i++)
| {
| char *a = foo + i;
| char *b = bar + i;
| strcpy (a, "0111");
| strcpy (b, "1000");
| if (memcmp (a, b, 16) >= 0)
|exit (1);
| }
| exit (0);
| }
| }
|
configure:15835: result: no
The test program didn't include stdlib.h, so
-Werror=implicit-function-declaration caused error then the script
check failed.
I'll try to make a workaround.
Processed: Bug#1057549 marked as pending in crowdsec
Processing control commands: > tag -1 pending Bug #1057549 [src:crowdsec] crowdsec: FTBFS: FAIL: TestOneShot/permission_denied Added tag(s) pending. -- 1057549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057549: marked as pending in crowdsec
Control: tag -1 pending Hello, Bug #1057549 in crowdsec reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/crowdsec/-/commit/b2beee2140e7cdb9d4732c4e48a568fce70248ee Fix missing build-dependency on passwd (Closes: #1057549). Thanks to Santiago Vila for the bug report and the analysis. (this message was generated automatically) -- Greetings https://bugs.debian.org/1057549
Bug#1060915: marked as done (golang-entgo-ent: Flaky tests due to relying on default result ordering)
Your message dated Thu, 14 Mar 2024 04:06:18 +
with message-id
and subject line Bug#1060915: fixed in golang-entgo-ent 0.11.3-5
has caused the Debian Bug report #1060915,
regarding golang-entgo-ent: Flaky tests due to relying on default result
ordering
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.)
--
1060915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-entgo-ent
Version: 0.11.3-4
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: paul.m...@canonical.com
Dear Maintainer,
A test of the golang test suite of ent is sometimes failing because the results
fetched from the database are not sorted as expected.
681s === RUN Example_M2M2Types
681s --- FAIL: Example_M2M2Types (0.00s)
681s got:
681s [Group(id=2, name=GitLab) Group(id=1, name=GitHub)]
681s [Group(id=1, name=GitHub)]
681s [User(id=1, age=30, name=a8m) User(id=2, age=28, name=nati)]
681s want:
681s [Group(id=1, name=GitHub) Group(id=2, name=GitLab)]
681s [Group(id=1, name=GitHub)]
681s [User(id=1, age=30, name=a8m) User(id=2, age=28, name=nati)]
By default sqlite does not guaranty results ordering but this can go unnoticed
on simple cases. I suspect some race condition somewhere is triggering the bug
and the 2 results are swapped.
To make it reliable we need to explicitly call .Order(ent.Asc("id")).
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-14-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: golang-entgo-ent
Source-Version: 0.11.3-5
Done: Cyril Brulebois
We believe that the bug you reported is fixed in the latest version of
golang-entgo-ent, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cyril Brulebois (supplier of updated golang-entgo-ent
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: Thu, 14 Mar 2024 04:46:38 +0100
Source: golang-entgo-ent
Architecture: source
Version: 0.11.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Cyril Brulebois
Closes: 1060915
Changes:
golang-entgo-ent (0.11.3-5) unstable; urgency=medium
.
[ Paul Mars ]
* Add patch to avoid test failures due to different SQLite result
ordering (Closes: #1060915, LP: #2049502):
- 0005-force-result-ordering-in-tests.patch
Checksums-Sha1:
86a28403a38d687351fd2444371a519c5b0b04aa 2746 golang-entgo-ent_0.11.3-5.dsc
af839f4b0615196bd08263da4d1d598fada235a9 7272
golang-entgo-ent_0.11.3-5.debian.tar.xz
88c3598aaf6274f2e222967c2cd47903fb89f5ee 7710
golang-entgo-ent_0.11.3-5_source.buildinfo
Checksums-Sha256:
ca98c1681e2b1faa66780c1fa9bf286c9f36f08df7e575b7bff7a99756797e80 2746
golang-entgo-ent_0.11.3-5.dsc
387b767754e48319ff2499abf43e020375b14ceac5f2efa1ac80101237b58e56 7272
golang-entgo-ent_0.11.3-5.debian.tar.xz
d520981dee2c798092b0d6ac94c6f3ffb0b895d02874888c2d7f01bff81fcf3a 7710
golang-entgo-ent_0.11.3-5_source.buildinfo
Files:
f60d8060feeb048899c136d9ad90c48b 2746 golang optional
golang-entgo-ent_0.11.3-5.dsc
5d0f2541904fdd175006c59fdeacc97f 7272 golang optional
golang-entgo-ent_0.11.3-5.debian.tar.xz
2efae20d6de4cf9f44820fb9b8f45baf 7710 golang optional
golang-entgo-ent_0.11.3-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmXydFsQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIAx5EACqdNaWm6DaAZkK5y32gBvn6ivwy9dn9Ofb
GfWQRmzq2aeXgIpLs0f0RH/RDva5XtC4e26N1VugQVcvMSfApfvFSi8Gkp0QhqZ8
Bug#1060915: golang-entgo-ent: Flaky tests due to relying on default result ordering
Hi Paul, Paul Mars (2024-01-16): > Here is a patch to fix the issue. Sorry, I didn't spot this bug report right away (its metadata got adjusted along the way). Thanks for the bug report and the patch, on their way to unstable! Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1066669: marked as done (grace: FTBFS: configure: error: M*tif has not been found)
Your message dated Thu, 14 Mar 2024 03:42:53 + with message-id and subject line Bug#109: fixed in grace 1:5.1.25-14 has caused the Debian Bug report #109, regarding grace: FTBFS: configure: error: M*tif has not been found 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.) -- 109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grace Version: 1:5.1.25-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for xpm.h... no > checking X11/xpm.h usability... yes > checking X11/xpm.h presence... yes > checking for X11/xpm.h... yes > checking for a Motif >= 1002 compatible API... no > configure: error: M*tif has not been found > make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2024/03/13/grace_5.1.25-13_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: grace Source-Version: 1:5.1.25-14 Done: Nicholas Breen We believe that the bug you reported is fixed in the latest version of grace, 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. Nicholas Breen (supplier of updated grace 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 19:11:39 -0700 Source: grace Architecture: source Version: 1:5.1.25-14 Distribution: unstable Urgency: medium Maintainer: Nicholas Breen Changed-By: Nicholas Breen Closes: 109 Changes: grace (1:5.1.25-14) unstable; urgency=medium . * d/patches/configure-implicit-declarations.diff: Patch configure script to compile all tests with new default CFLAGS in dpkg 1.22.6. Thanks to Lucas Nussbaum for the report, and Ryan Carsten Schmidt and Macports contributors for background and their own patch. (Closes: #109) * Assorted housekeeping: - d/control: Bump Standards-Version to 4.6.2, no changes required. - d/copyright: Update years. - d/grace.lintian-overrides: Restore embedded-library override. Checksums-Sha1: ce9827abbd9c4bd6d4f823258d5ea802e1eaa6a0 2144 grace_5.1.25-14.dsc 899339242010d9bfdc1fdce03294087acd437f72 110924 grace_5.1.25-14.debian.tar.xz 12af183c6fc7daea8ab1f296d27ab7eafbd49a47 9104 grace_5.1.25-14_source.buildinfo Checksums-Sha256: 69693e145b822916955dd9eb55628b9708c5ec34831b5c147f39d211b122a9ba 2144 grace_5.1.25-14.dsc 6ac9ea3f50394c03f7699075d86af1dc7fed7b282305c9ee62d470d902a6af5c 110924 grace_5.1.25-14.debian.tar.xz c6c4b5a9869f26f2b60994a00b4d5f4c5f8208f266d20382b97257b2fcedceed 9104 grace_5.1.25-14_source.buildinfo Files: c80072adf2a9ade60029d2756f096567 2144 math optional grace_5.1.25-14.dsc 5f9381ebc85116d351fe8b7736f3938b 110924 math optional grace_5.1.25-14.debian.tar.xz 4a18af0e1c737a87b377adc8292f896f 9104 math optional grace_5.1.25-14_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEhD5fph5gYziYdtLl7kr9aexlEI8FAmXyYkQSHG5icmVlbkBk ZWJpYW4ub3JnAAoJEO5K/WnsZRCP25EP/0Uy432hjQWIzlR0ateLx2cZdDLk9vS8 9+LC3xy+1j+F8pC8SPiw/puMtmWRrED4WG/eG8u5udNg3qNT6Xl1vXvvfAHBXcyh XpQU8UAv/qCkNgpmBkeecSkHtWWgTCD
Bug#1066279: [Debian-zh-dev] Bug#1066279: unicon: FTBFS: cin2tab.c:238:13: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration]
Hi,
Thanks for your report.
I'd uploaded the new version in mentors to fix this bug.
https://mentors.debian.net/package/unicon/
Welcome to review and upload.
Thanks!
在 2024/3/13 19:46, Lucas Nussbaum 写道:
Source: unicon
Version: 3.0.4+dfsg1-4
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 -fPIC -g -Wall -I../../include -I. -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c -g -I../../include -I. cin2tab.c -o cin2tab.o
cin2tab.c: In function ‘get_line’:
cin2tab.c:80:16: warning: pointer targets in passing argument 1 of ‘fgets’
differ in signedness [-Wpointer-sign]
80 | fgets (tt, 128, fr);
|^~
||
|u_char * {aka unsigned char *}
In file included from /usr/include/stdio.h:906,
from cin2tab.c:27:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:209:25: note: expected ‘char *
restrict’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’}
209 | fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
|~^~~
cin2tab.c: In function ‘cmd_arg’:
cin2tab.c:96:18: warning: pointer targets in passing argument 1 of ‘skip_space’
differ in signedness [-Wpointer-sign]
96 | s=skip_space(s);
| ^
| |
| u_char * {aka unsigned char *}
cin2tab.c:50:24: note: expected ‘char *’ but argument is of type ‘u_char *’
{aka ‘unsigned char *’}
50 | char *skip_space(char *s)
| ~~^
cin2tab.c:96:6: warning: pointer targets in assignment from ‘char *’ to ‘u_char
*’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
96 | s=skip_space(s);
| ^
cin2tab.c:97:16: warning: pointer targets in passing argument 1 of ‘to_space’
differ in signedness [-Wpointer-sign]
97 | t=to_space(s);
|^
||
|u_char * {aka unsigned char *}
cin2tab.c:56:22: note: expected ‘char *’ but argument is of type ‘u_char *’
{aka ‘unsigned char *’}
56 | char *to_space(char *s)
|~~^
cin2tab.c:100:13: warning: pointer targets in assignment from ‘char *’ to
‘u_char *’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
100 | *arg=t;
| ^
cin2tab.c:107:9: warning: pointer targets in assignment from ‘char *’ to
‘u_char *’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign]
107 | *arg=t;
| ^
cin2tab.c: In function ‘main’:
cin2tab.c:194:13: warning: pointer targets in passing argument 1 of ‘cmd_arg’
differ in signedness [-Wpointer-sign]
194 | cmd_arg(tt, , );
| ^~
| |
| char *
cin2tab.c:89:22: note: expected ‘u_char *’ {aka ‘unsigned char *’} but argument
is of type ‘char *’
89 | void cmd_arg(u_char *s, u_char **cmd, u_char **arg)
| ^
cin2tab.c:195:16: warning: pointer targets in passing argument 1 of ‘strcmp’
differ in signedness [-Wpointer-sign]
195 | if (strcmp(cmd,"%ename") || !(*arg) )
|^~~
||
|u_char * {aka unsigned char *}
In file included from cin2tab.c:30:
/usr/include/string.h:156:32: note: expected ‘const char *’ but argument is of
type ‘u_char *’ {aka ‘unsigned char *’}
156 | extern int strcmp (const char *__s1, const char *__s2)
|^~~~
cin2tab.c:198:27: warning: pointer targets in passing argument 2 of ‘strcpy’
differ in signedness [-Wpointer-sign]
198 | strcpy(InpTable.ename,arg);
| ^~~
| |
| u_char * {aka unsigned char *}
In file included from /usr/include/features.h:490,
from
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
from /usr/include/stdio.h:27:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:77:1: note: expected
‘const char * restrict’ but argument is of type ‘u_char *’ {aka ‘unsigned char
*’}
77 | __NTH (strcpy (char *__restrict __dest, const char *__restrict __src))
| ^
cin2tab.c:200:13: warning: pointer targets in passing argument 1 of ‘cmd_arg’
differ in signedness [-Wpointer-sign]
200
Bug#1066831: nbd-server: Crash on -C /dev/null or -C /missing/file
Package: nbd-client
Version: 1:3.26.1-1
Severity: serious
Tags: patch
X-Debbugs-Cc: none, Hilko Bengen
Dear Maintainer,
While investigating libnbd build failures (see ##1066766), I stumbled
across a bug that makes nbd-server crash without an error message when
trying to read its configuration from /dev/null or any non-existing
file:
$ ./nbd-server -C /dev/null
Segmentation fault
It turns out that one g_key_file_free() call was left in the code when
auto-freeing was introduced in upstream commit
ab41c4f5a91857d9466d83ea062ec60435f7eaa0. The attached patch fixes this.
Cheers,
-Hilko
Index: nbd-3.26.1/nbd-server.c
===
--- nbd-3.26.1.orig/nbd-server.c
+++ nbd-3.26.1/nbd-server.c
@@ -881,7 +881,6 @@ GArray* parse_cfile(gchar* f, struct gen
G_KEY_FILE_KEEP_TRANSLATIONS, )) {
g_set_error(e, NBDS_ERR, NBDS_ERR_CFILE_NOTFOUND, "Could not open config file %s: %s",
f, err->message);
- g_key_file_free(cfile);
return retval;
}
startgroup = g_key_file_get_start_group(cfile);
Processed: Bug#1066207 marked as pending in mrpt
Processing control commands: > tag -1 pending Bug #1066207 [src:mrpt] mrpt: FTBFS: xstimestamp.c:145:34: error: implicit declaration of function ‘timegm’; did you mean ‘time’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066207: marked as pending in mrpt
Control: tag -1 pending Hello, Bug #1066207 in mrpt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/robotics-team/mrpt/-/commit/26ef06161dcc53c70a646d7fd6e3c189da10dd95 Add d/patch to fix FTBFS (Closes: #1066207) (this message was generated automatically) -- Greetings https://bugs.debian.org/1066207
Bug#1066459: yiyantang: FTBFS: xmalloc.c:136:16: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration]
Hi, Thanks for your report. I'd uploaded the new version in mentors to fix this bug. https://mentors.debian.net/package/yiyantang/ Welcome to review and upload. Thanks! 在 2024/3/13 19:59, Lucas Nussbaum 写道: Source: yiyantang Version: 0.7.0-8 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): x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -DG_LOG_DOMAIN=\"yyt\" -I../intl -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c yiyantang_init.c xmalloc.c: In function ‘xstrdup’: xmalloc.c:136:16: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration] 136 | p = xmalloc (strlen (str) + 1); |^~ xmalloc.c:48:1: note: include ‘’ or provide a declaration of ‘strlen’ 47 | #include "error.h" +++ |+#include 48 | xmalloc.c:136:16: warning: incompatible implicit declaration of built-in function ‘strlen’ [-Wbuiltin-declaration-mismatch] 136 | p = xmalloc (strlen (str) + 1); |^~ xmalloc.c:136:16: note: include ‘’ or provide a declaration of ‘strlen’ xmalloc.c:137:3: error: implicit declaration of function ‘strcpy’ [-Werror=implicit-function-declaration] 137 | strcpy (p, str); | ^~ xmalloc.c:137:3: note: include ‘’ or provide a declaration of ‘strcpy’ xmalloc.c:137:3: warning: incompatible implicit declaration of built-in function ‘strcpy’ [-Wbuiltin-declaration-mismatch] xmalloc.c:137:3: note: include ‘’ or provide a declaration of ‘strcpy’ loop.c: In function ‘loop’: loop.c:91:25: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration] 91 | exit (ret); | ^~~~ loop.c:42:1: note: include ‘’ or provide a declaration of ‘exit’ 41 | #include "zhconv.h" +++ |+#include 42 | loop.c:91:25: warning: incompatible implicit declaration of built-in function ‘exit’ [-Wbuiltin-declaration-mismatch] 91 | exit (ret); | ^~~~ loop.c:91:25: note: include ‘’ or provide a declaration of ‘exit’ loop.c:117:33: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 117 | write (ptym, ibuf, ret); | ^~~ loop.c:162:41: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 162 | write (STDOUT_FILENO, tbuf2, ret); | ^ cc1: some warnings being treated as errors make[3]: *** [Makefile:201: xmalloc.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/yiyantang_0.7.0-8_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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. -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066454: marked as done (wpewebkit: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLo
Your message dated Thu, 14 Mar 2024 00:19:48 + with message-id and subject line Bug#1066454: fixed in wpewebkit 2.42.5-1.2 has caused the Debian Bug report #1066454, regarding wpewebkit: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() [with Mutex = std::mutex]’: recursive inlining 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.) -- 1066454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wpewebkit Version: 2.42.5-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DANGLE_ENABLE_ESSL -DANGLE_ENABLE_GLSL -DANGLE_ENABLE_OPENGL > -DANGLE_PLATFORM_LINUX -DBUILDING_WEBKIT=1 -DBUILDING_WITH_CMAKE=1 > -DBUILDING_WPE__=1 -DBWRAP_EXECUTABLE=\"/usr/bin/bwrap\" > -DDBUS_PROXY_EXECUTABLE=\"/usr/bin/xdg-dbus-proxy\" -DEGL_EGL_PROTOTYPES=0 > -DEGL_NO_PLATFORM_SPECIFIC_TYPES -DGETTEXT_PACKAGE=\"WPE\" > -DGL_GLES_PROTOTYPES=0 -DHAVE_CONFIG_H=1 -DJSC_GLIB_API_ENABLED > -DLIBANGLE_IMPLEMENTATION -DPAS_BMALLOC=1 -DUSE_SYSTEM_EGL > -I/<>/Source/ThirdParty/ANGLE/WebKit > -I/<>/Source/ThirdParty/ANGLE/include > -I/<>/Source/ThirdParty/ANGLE/include/KHR > -I/<>/Source/ThirdParty/ANGLE/src > -I/<>/Source/ThirdParty/ANGLE/src/common/base > -I/<>/Source/ThirdParty/ANGLE/src/common/third_party/xxhash > -I/<>/Source/ThirdParty/ANGLE/third_party/zlib/google > -I/<>/obj-x86_64-linux-gnu/Source/ThirdParty/ANGLE/include -g1 > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -std=c++20 > -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -w -MD -MT > Source/ThirdParty/ANGLE/CMakeFiles/ANGLE.dir/src/libANGLE/SharedContextMutex.cpp.o > -MF > Source/ThirdParty/ANGLE/CMakeFiles/ANGLE.dir/src/libANGLE/SharedContextMutex.cpp.o.d > -o > Source/ThirdParty/ANGLE/CMakeFiles/ANGLE.dir/src/libANGLE/SharedContextMutex.cpp.o > -c > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp > cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > is not valid for C++ > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp: > In member function ‘egl::SharedContextMutex* > egl::SharedContextMutex::doTryLock() [with Mutex = std::mutex]’: > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp:219:41: > error: inlining failed in call to ‘always_inline’ > ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() > [with Mutex = std::mutex]’: recursive inlining > 219 | ANGLE_INLINE SharedContextMutex > *SharedContextMutex::doTryLock() > | ^ > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp:230:67: > note: called from here > 230 | SharedContextMutex *const lockedRoot = root->doTryLock(); > |~~~^~ > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp:219:41: > error: inlining failed in call to ‘always_inline’ > ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() > [with Mutex = std::mutex]’: recursive inlining > 219 | ANGLE_INLINE SharedContextMutex > *SharedContextMutex::doTryLock() > | ^ > /<>/Source/ThirdParty/ANGLE/src/libANGLE/SharedContextMutex.cpp:230:67: > note: called from here > 230 | SharedContextMutex *const lockedRoot = root->doTryLock(); > |~~~^~ > In member function ‘egl::SharedContextMutex* > egl::SharedContextMutex::doTryLock() [with Mutex = std::mutex]’, > inlined from ‘egl::SharedContextMutex* > egl::SharedContextMutex::doTryLock() [with Mutex = std::mutex]’ at > /<>/Source/ThirdParty/ANGLE/src/libANGLE/
Bug#1066199: marked as done (wv: FTBFS: wvWare.c:1474:40: error: implicit declaration of function ‘strcasecmp’; did you mean ‘g_strcasecmp’? [-Werror=implicit-function-declaration])
Your message dated Thu, 14 Mar 2024 00:20:00 +
with message-id
and subject line Bug#1066199: fixed in wv 1.2.9-8
has caused the Debian Bug report #1066199,
regarding wv: FTBFS: wvWare.c:1474:40: error: implicit declaration of function
‘strcasecmp’; did you mean ‘g_strcasecmp’?
[-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.)
--
1066199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wv
Version: 1.2.9-7
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 -DHAVE_CONFIG_H -DVERSION=\"1.2.9\"
> -DXMLCONFIG=\"/usr/share/wv/wvConfig.xml\"
> -DHTMLCONFIG=\"/usr/share/wv/wvHtml.xml\" -DWVDATADIR=\"/usr/share/wv\" -I.
> -I. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libgsf-1
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/libxml2 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -ansi -MT wvWare.o -MD -MP -MF .deps/wvWare.Tpo -c -o wvWare.o wvWare.c
> wvWare.c: In function ‘wvPrintGraphics’:
> wvWare.c:1262:19: warning: repeated '-' flag in format [-Wformat=]
> 1262 | printf ("\n\\resizebox{%dpt}{%dpt}\
> | ^~~
> 1263 | {\\includegraphics{%s.eps}}\
> |
> 1264 | \n% -- %#.2x graphic -- \n", width, height, source,
> graphicstype);
> | ~~~
> wvWare.c:1262:19: warning: repeated ' ' flag in format [-Wformat=]
> wvWare.c:1262:19: warning: conversion lacks type at end of format [-Wformat=]
> wvWare.c: In function ‘mySpecCharProc’:
> wvWare.c:1474:40: error: implicit declaration of function ‘strcasecmp’; did
> you mean ‘g_strcasecmp’? [-Werror=implicit-function-declaration]
> 1474 | if ((!message) && (strcasecmp ("UTF-8", charset)))
> |^~
> |g_strcasecmp
> wvWare.c: In function ‘HandleBitmap’:
> wvWare.c:182:18: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 182 | if (ps->dir) chdir (ps->dir);
> | ^~~
> wvWare.c:184:18: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 184 | if (ps->dir) chdir (wv_cwd);
> | ^~
> wvWare.c: In function ‘HandleMetafile’:
> wvWare.c:209:18: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 209 | if (ps->dir) chdir (ps->dir);
> | ^~~
> wvWare.c:211:18: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 211 | if (ps->dir) chdir (wv_cwd);
> | ^~
> wvWare.c: In function ‘main’:
> wvWare.c:410:5: warning: ignoring return value of ‘getcwd’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 410 | getcwd (wv_cwd,4096);
> | ^~~~
> wvWare.c: In function ‘mySpecCharProc’:
> wvWare.c:1362:34: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 1362 | if (ps->dir) chdir (ps->dir);
> | ^~~
> wvWare.c:1367:34: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 1367 | if (ps->dir)
Bug#1066599: marked as done (libquicktime: FTBFS: qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:59:37 + with message-id and subject line Bug#1066599: fixed in libquicktime 2:1.2.4-16 has caused the Debian Bug report #1066599, regarding libquicktime: FTBFS: qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ [-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.) -- 1066599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libquicktime Version: 2:1.2.4-15 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../../include -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libpng16 -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > -o lqt_png.lo lqt_png.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libpng16 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > lqt_png.c -fPIC -DPIC -o .libs/lqt_png.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include > -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libpng16 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -finline-functions -Wall -Winline > -Wmissing-declarations -Wdeclaration-after-statement -fvisibility=hidden -c > qtpng.c -fPIC -DPIC -o .libs/qtpng.o > qtpng.c: In function ‘read_function’: > qtpng.c:74:5: error: implicit declaration of function ‘memcpy’ > [-Werror=implicit-function-declaration] >74 | memcpy(data, codec->buffer + codec->buffer_position, length); > | ^~ > qtpng.c:30:1: note: include ‘’ or provide a declaration of ‘memcpy’ >29 | #include "qtpng.h" > +++ |+#include >30 | > qtpng.c:74:5: warning: incompatible implicit declaration of built-in function > ‘memcpy’ [-Wbuiltin-declaration-mismatch] >74 | memcpy(data, codec->buffer + codec->buffer_position, length); > | ^~ > qtpng.c:74:5: note: include ‘’ or provide a declaration of ‘memcpy’ > qtpng.c: In function ‘write_function’: > qtpng.c:88:3: warning: incompatible implicit declaration of built-in function > ‘memcpy’ [-Wbuiltin-declaration-mismatch] >88 | memcpy(codec->buffer + codec->buffer_size, data, length); > | ^~ > qtpng.c:88:3: note: include ‘’ or provide a declaration of ‘memcpy’ > qtpng.c: In function ‘set_parameter’: > qtpng.c:213:7: error: implicit declaration of function ‘strcasecmp’ > [-Werror=implicit-function-declaration] > 213 | if(!strcasecmp(key, "png_compression_level")) > | ^~ > cc1: some warnings being treated as errors > make[5]: *** [Makefile:532: qtpng.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libquicktime_1.2.4-15_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://w
Bug#1066414: marked as done (pcb-rnd: FTBFS: ./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; /usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here)
Your message dated Wed, 13 Mar 2024 23:56:20 + with message-id and subject line Bug#1066414: fixed in genht 1.1.3-1 has caused the Debian Bug report #1066414, regarding pcb-rnd: FTBFS: ./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; /usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here 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.) -- 1066414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pcb-rnd Version: 3.1.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: txt2bxl.o: in function `main': > ./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; > /usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/pcb-rnd_3.1.3-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: genht Source-Version: 1.1.3-1 Done: Bdale Garbee We believe that the bug you reported is fixed in the latest version of genht, 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. Bdale Garbee (supplier of updated genht 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 16:40:22 -0600 Source: genht Architecture: source Version: 1.1.3-1 Distribution: unstable Urgency: low Maintainer: Bdale Garbee Changed-By: Bdale Garbee Closes: 1066414 Changes: genht (1.1.3-1) unstable; urgency=low . * new upstream version, closes: #1066414 * move .so symlink to -dev package Checksums-Sha1: 48c20ed56c8247ffdd6d06fd7f4ad8a0cc2f24ef 1739 genht_1.1.3-1.dsc e3a8aa862367580d8642b629f164a777cf791e1d 10936 genht_1.1.3.orig.tar.bz2 2985fcb8ba86628f7de7257cf7e5d3b93129548f 1724 genht_1.1.3-1.debian.tar.xz 45f9d852e2b0aa3bbb8769c88b71a30c4c5844cb 6375 genht_1.1.3-1_amd64.buildinfo Checksums-Sha256: 5680dccbd95d0d59f4d2b24c46b5eb898f867c74163dc71f21c9c3181f9de2d5 1739 genht_1.1.3-1.dsc 9861a35c30b5d0023c5f50fa8bb44c3e1df15c232de155888faa492f71f3b1cc 10936 genht_1.1.3.orig.tar.bz2 0f0124839b3060782b09b7d12a56598f61bdd9805c743467a0d87ce5908857a3 1724 genht_1.1.3-1.debian.tar.xz 63d82a935b7d8d36a1c9ddadc95c6619c138625e49ea0d9942fda658808205fa 6375 genht_1.1.3-1_amd64.buildinfo Files: d9b832e19cb95e1725105d82d40b9c05 1739 libs optional genht_1.1.3-1.dsc bda12d887f2b154c984edefec8fa486d 10936 libs optional genht_1.1.3.orig.tar.bz2 c124d14abe54d029357bcde64c7f9496 1724 libs optional genht_1.1.3-1.debian.tar.xz 8bf933685ff1d2fa9f7bc318bb8abff6 6375 libs optional genht_1.1.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmXyLVMACgkQtwRxBYML n6GfhRAAlWzeoW2/EZrd4tAujGQZuIJ0fiZkha0hU4XeW7K/iZ7cjTu8A1oSZd2Z 2fTRQD8ftYWc8UXMOGQ1GBNiQzHvGzyB3IPsT0pAblOXbVyC5rW7UcvRMOsO9CX/ lJSeRfL4efb21NLv+wOwLMBlQbfN9a7F3jZ90cfzJoXI6K8AMzJp2cPteUTt0m8f BI/Man2u6oMLl/tkNh9/7H+07x/Mv7CBBDM4KhfYm6gYQ/+lZgUjwH9enkzzkAO2 wbykMS4KmaizRviffEFWPf8UB+9wOQg7RVgaatnwIo/Eut3QfZziI5GUx5KCKLYX iarAed5rOLQ9CmyeVK6uT9gWadfPsnHOK1j1mykGmqbqR0tEKZjJ
Bug#1066528: marked as done (dino-im: FTBFS: encrypt.vala:60:3: error: implicit declaration of function ‘xmpp_xep_omemo_encrypt_state_set_encrypted’; did you mean ‘xmpp_xep_omemo_encrypt_state_get_enc
Your message dated Wed, 13 Mar 2024 23:51:41 + with message-id and subject line Bug#1066528: fixed in dino-im 0.4.3-3 has caused the Debian Bug report #1066528, regarding dino-im: FTBFS: encrypt.vala:60:3: error: implicit declaration of function ‘xmpp_xep_omemo_encrypt_state_set_encrypted’; did you mean ‘xmpp_xep_omemo_encrypt_state_get_encrypted’? [-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.) -- 1066528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dino-im Version: 0.4.3-2 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): > /usr/bin/cc -DGETTEXT_PACKAGE=\"dino-omemo\" -DG_LOG_DOMAIN=\"OMEMO\" > -DLOCALE_INSTALL_DIR=\"/usr/share/locale\" -Domemo_EXPORTS > -I/<>/obj-x86_64-linux-gnu/plugins/omemo > -I/<>/obj-x86_64-linux-gnu/exports -isystem > /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/glib-2.0 -isystem > /usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/libpng16 > -isystem /usr/include/webp -isystem /usr/include/libmount -isystem > /usr/include/blkid -isystem /usr/include/gee-0.8 -isystem > /usr/include/gtk-4.0 -isystem /usr/include/pango-1.0 -isystem > /usr/include/harfbuzz -isystem /usr/include/freetype2 -isystem > /usr/include/fribidi -isystem /usr/include/cairo -isystem > /usr/include/pixman-1 -isystem /usr/include/graphene-1.0 -isystem > /usr/lib/x86_64-linux-gnu/graphene-1.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -fdiagnostics-color -Wall -Wextra -Werror=format-security > -Wno-duplicate-decl-specifier -fno-omit-frame-pointer -g -fPIC > -Wno-unused-but-set-variable -Wno-unused-function -Wno-unused-label > -Wno-unused-parameter -Wno-unused-value -Wno-unused-variable > -Wno-discarded-qualifiers -Wno-discarded-array-qualifiers > -Wno-incompatible-pointer-types-discards-qualifiers > -Wno-deprecated-declarations -Wno-missing-braces -pthread -mfpmath=sse -msse > -msse2 -MD -MT plugins/omemo/CMakeFiles/omemo.dir/src/logic/encrypt.c.o -MF > plugins/omemo/CMakeFiles/omemo.dir/src/logic/encrypt.c.o.d -o > plugins/omemo/CMakeFiles/omemo.dir/src/logic/encrypt.c.o -c > /<>/obj-x86_64-linux-gnu/plugins/omemo/src/logic/encrypt.c > /<>/plugins/omemo/src/logic/encrypt.vala: In function > ‘dino_plugins_omemo_omemo_encryptor_encrypt’: > /<>/plugins/omemo/src/logic/encrypt.vala:60:3: error: implicit > declaration of function ‘xmpp_xep_omemo_encrypt_state_set_encrypted’; did you > mean ‘xmpp_xep_omemo_encrypt_state_get_encrypted’? > [-Werror=implicit-function-declaration] >60 | status.encrypted = true; > | ^ > | xmpp_xep_omemo_encrypt_state_get_encrypted > /<>/plugins/omemo/src/logic/encrypt.vala: In function > ‘dino_plugins_omemo_omemo_encryptor_encrypt_key_to_recipients’: > /<>/plugins/omemo/src/logic/encrypt.vala:74:2: error: implicit > declaration of function ‘xmpp_xep_omemo_encrypt_state_set_own_list’; did you > mean ‘xmpp_xep_omemo_encrypt_state_get_own_list’? > [-Werror=implicit-function-declaration] >74 | status.own_list = true; > | ^ ~~~ > | xmpp_xep_omemo_encrypt_state_get_own_list > /<>/plugins/omemo/src/logic/encrypt.vala:75:2: error: implicit > declaration of function ‘xmpp_xep_omemo_encrypt_state_set_own_devices’; did > you mean ‘xmpp_xep_omemo_encrypt_state_get_own_devices’? > [-Werror=implicit-function-declaration] >75 | status.own_devices = > trust_manager.get_trusted_devices(account, self_jid).size; > | ^ ~ > | xmpp_xep_omemo_encrypt_state_get_own_devices
Bug#1066720: marked as done (seyon: FTBFS: SeGeneric.c:222:16: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:25:16 + with message-id and subject line Bug#1066720: fixed in seyon 2.20c-35 has caused the Debian Bug report #1066720, regarding seyon: FTBFS: SeGeneric.c:222:16: error: implicit declaration of function ‘time’ [-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.) -- 1066720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seyon Version: 2.20c-34 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 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fcommon -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall > -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o SeGeneric.o SeGeneric.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from SeGeneric.c:12: > /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > SeGeneric.c: In function ‘TtyTimedWaitFor’: > SeGeneric.c:222:16: error: implicit declaration of function ‘time’ > [-Werror=implicit-function-declaration] > 222 | expireTime = time((time_t*)0) + waitTime; > |^~~~ > SeGeneric.c:26:1: note: ‘time’ is defined in header ‘’; did you > forget to ‘#include ’? >25 | #include "SeDecl.h" > +++ |+#include >26 | > cc1: some warnings being treated as errors > make[2]: *** [: SeGeneric.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/seyon_2.20c-34_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: seyon Source-Version: 2.20c-35 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of seyon, 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. Sebastian Ramacher (supplier of updated seyon 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 22:54:54 +0100 Source: seyon Architecture: source Version: 2.20c-35 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes:
Bug#1041477: php-net-ftp: PHP Fatal error with Bookworm PHP 8.2
Hi David, Le 09/03/2024 à 11:49, David Prévot a écrit : Also, this package has no reverse dependencies. Given the amount of care it brought in the last few years, I believe it should be removed from the archive. Bumping the severity to see it removed from testing ASAP, maybe it should also be removed from (at least) Bookworm. I intend to follow up with RM requests in a few months if nobody objects (but feel free to beat me to it). Thanks for return. I removed my dependencies on this package since I discovered this problem. So, for me, feel free to remove this package, I don't use it anymore :) Freely, -- Benjamin Renard
Bug#1066633: marked as done (poa: FTBFS: fasta_format.c:48:9: error: implicit declaration of function ‘stringptr_cat_pos’; did you mean ‘stringptr_cat’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:21:58 + with message-id and subject line Bug#1066633: fixed in poa 2.0+20060928-9 has caused the Debian Bug report #1066633, regarding poa: FTBFS: fasta_format.c:48:9: error: implicit declaration of function ‘stringptr_cat_pos’; did you mean ‘stringptr_cat’? [-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.) -- 1066633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poa Version: 2.0+20060928-8 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 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g > -DUSE_WEIGHTED_LINKS -DUSE_PROJECT_HEADER -I. -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o align_lpo_po2.o align_lpo_po2.c > In file included from align_lpo_po2.c:2: > align_lpo_po2.c: In function ‘get_lpo_stats’: > default.h:155:20: warning: format ‘%d’ expects argument of type ‘int’, but > argument 4 has type ‘long unsigned int’ [-Wformat=] > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |^~~~ ~ > | | > | long unsigned int > align_lpo_po2.c:41:3: note: in expansion of macro ‘CALLOC’ >41 | CALLOC (node_type, len, int); > | ^~ > default.h:155:37: note: format string is defined here > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |~^ > | | > | int > |%ld > default.h:155:20: warning: format ‘%d’ expects argument of type ‘int’, but > argument 4 has type ‘long unsigned int’ [-Wformat=] > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |^~~~ ~ > | | > | long unsigned int > align_lpo_po2.c:42:3: note: in expansion of macro ‘CALLOC’ >42 | CALLOC (refs_from_right, len, int); > | ^~ > default.h:155:37: note: format string is defined here > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |~^ > | | > | int > |%ld > default.h:155:20: warning: format ‘%d’ expects argument of type ‘int’, but > argument 4 has type ‘long unsigned int’ [-Wformat=] > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |^~~~ ~ > | | > | long unsigned int > align_lpo_po2.c:43:3: note: in expansion of macro ‘CALLOC’ >43 | CALLOC (tmp, len, int); > | ^~ > default.h:155:37: note: format string is defined here > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof(ATYPE)); > \ > |~^ > | | > | int > |%ld > default.h:155:20: warning: format ‘%d’ expects argument of type ‘int’, but > argument 4 has type ‘long unsigned int’ [-Wformat=] > 155 | fprintf(stderr,"requested %d x %d bytes \n",(N),sizeof
Bug#1066516: marked as done (openwince-jtag: FTBFS: flash/cfi.c:84:9: error: implicit declaration of function ‘printf’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:20:53 +
with message-id
and subject line Bug#1066516: fixed in openwince-jtag 0.5.1-9
has caused the Debian Bug report #1066516,
regarding openwince-jtag: FTBFS: flash/cfi.c:84:9: error: implicit declaration
of function ‘printf’ [-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.)
--
1066516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openwince-jtag
Version: 0.5.1-8
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 -DHAVE_CONFIG_H -I. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/include/openwince -I/usr/include/openwince/device
> -I/usr/include/openwince/arm -I./../include -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -Wall -c -o cfi.o `test -f
> 'flash/cfi.c' || echo './'`flash/cfi.c
> flash/cfi.c: In function ‘cfi_detect’:
> flash/cfi.c:84:9: error: implicit declaration of function ‘printf’
> [-Werror=implicit-function-declaration]
>84 | printf("buswidth: %d\n",bw);
> | ^~
> flash/cfi.c:38:1: note: include ‘’ or provide a declaration of
> ‘printf’
>37 | #include
> +++ |+#include
>38 | #include
> flash/cfi.c:84:9: warning: incompatible implicit declaration of built-in
> function ‘printf’ [-Wbuiltin-declaration-mismatch]
>84 | printf("buswidth: %d\n",bw);
> | ^~
> flash/cfi.c:84:9: note: include ‘’ or provide a declaration of
> ‘printf’
> cc1: some warnings being treated as errors
> make[5]: *** [Makefile:429: cfi.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/openwince-jtag_0.5.1-8_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: openwince-jtag
Source-Version: 0.5.1-9
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
openwince-jtag, 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.
Sebastian Ramacher (supplier of updated openwince-jtag
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 23:08:59 +0100
Source: openwince-jtag
Architecture: source
Version: 0.5.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Sebastian Ramacher
Closes: 1066516
Changes:
openwince-jtag (0.5.1-9) unstable; urgency=medium
.
* QA upload.
* debian/patches: Add missing includes. (Closes: 1066516)
Checksums-Sha1:
55f19add9aeb3071b9c4fbe0b365f52d2c1b8cf3 1219 openwince-jtag_0.5.1-9.dsc
5cff1eff7caf7ffc3ae1ab612f0bf6d5b30b7765 4248
openwince-jtag_0.5.1-9.debian.tar.xz
e
Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function âgsskrb5_register_acceptor_identityâ [-Werror=implicit-function-declaration]
Dixi quod… >Suggested fix: > >+ AC_CHECK_HEADERS(gssapi/gssapi_krb5.h) > AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity) > if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then >- AC_CHECK_HEADERS(gssapi/gssapi_krb5.h) > >If it’s really that, anyway. At least it allows the build to proceed further. It’s still building, though, so I cannot say if this fixes the build. (Thanks to #1066811 the result will not work right anyway.) bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs
Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration
Dixi quod… >I just tested the 2.2 patch on gnupg1, and it applies cleanly, >[…] >For gnupg1, the B-D are also already installable, so there’s no >current need to modify them there, just apply the same patch as >was applied in gnupg2 2.2 and upload. It finished building with the patch, so please do ☻ Thanks, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Bug#1066825: alsa-oss: FTBFS on arm{el,hf}: error: ‘__open’ aliased to undefined symbol ‘open’
Source: alsa-oss Version: 1.1.8-2 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=alsa-oss=armhf=1.1.8-2%2Bb1=1710256499=0 libtool: compile: gcc -DPACKAGE_NAME=\"alsa-oss\" -DPACKAGE_TARNAME=\"alsa-oss\" -DPACKAGE_VERSION=\"1.1.8\" "-DPACKAGE_STRING=\"alsa-oss 1.1.8\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.1.8\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBASOUND=1 -I. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c mixer.c -fPIC -DPIC -o .libs/libalsatoss_la-mixer.o alsa-oss.c:794:20: error: ‘__open’ aliased to undefined symbol ‘open’ 794 | strong_alias(open, __open); |^~ alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’ 792 | extern __typeof (name) aliasname __attribute__ ((alias (#name))); | ^ alsa-oss.c:805:21: error: ‘__fopen’ aliased to undefined symbol ‘fopen’ 805 | strong_alias(fopen, __fopen); | ^~~ alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’ 792 | extern __typeof (name) aliasname __attribute__ ((alias (#name))); | ^ alsa-oss.c:804:22: error: ‘__select’ aliased to undefined symbol ‘select’ 804 | strong_alias(select, __select); | ^~~~ alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’ 792 | extern __typeof (name) aliasname __attribute__ ((alias (#name))); | ^ alsa-oss.c:801:20: error: ‘__mmap’ aliased to undefined symbol ‘mmap’ 801 | strong_alias(mmap, __mmap); |^~ alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’ 792 | extern __typeof (name) aliasname __attribute__ ((alias (#name))); | ^ alsa-oss.c:800:21: error: ‘__fcntl’ aliased to undefined symbol ‘fcntl’ 800 | strong_alias(fcntl, __fcntl); | ^~~ alsa-oss.c:792:26: note: in definition of macro ‘strong_alias’ 792 | extern __typeof (name) aliasname __attribute__ ((alias (#name))); | ^ make[2]: *** [Makefile:519: alsa-oss.lo] Error 1 Cheers -- Sebastian Ramacher
Bug#1066823: plptools: FTBFS on arm{el,hf}: plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous
Source: plptools
Version: 1.0.13-2
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=plptools=armhf=1.0.13-2%2Bb1=1710265542=0
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../intl -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -c plpdirent.cc
-fPIC -DPIC -o .libs/plpdirent.o
plpdirent.cc: In constructor ‘PlpDirent::PlpDirent()’:
plpdirent.cc:44:35: error: call of overloaded ‘PsiTime(long int)’ is ambiguous
44 | : size(0), attr(0), name(""), time(0L), attrstr("") {
| ^~~~
In file included from plpdirent.h:30,
from plpdirent.cc:23:
./psitime.h:179:5: note: candidate: ‘PsiTime::PsiTime(const PsiTime&)’
179 | PsiTime(const PsiTime );
| ^~~
./psitime.h:161:5: note: candidate: ‘PsiTime::PsiTime(psi_timeval*,
psi_timezone*)’
161 | PsiTime(psi_timeval *_ptv, psi_timezone *_ptz = 0L);
| ^~~
./psitime.h:153:5: note: candidate: ‘PsiTime::PsiTime(time_t)’
153 | PsiTime(time_t time);
| ^~~
./psitime.h:146:5: note: candidate: ‘PsiTime::PsiTime(timeval*, timezone*)’
146 | PsiTime(struct timeval *_utv, struct timezone *_utz = 0L);
| ^~~
make[3]: *** [Makefile:579: plpdirent.lo] Error 1
Cheers
--
Sebastian Ramacher
Bug#1066664: marked as done (wmstickynotes: FTBFS: wmstickynotes.c:229:17: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 22:08:14 +
with message-id
and subject line Bug#104: fixed in wmstickynotes 0.7-4
has caused the Debian Bug report #104,
regarding wmstickynotes: FTBFS: wmstickynotes.c:229:17: error: implicit
declaration of function ‘asprintf’; did you mean ‘vsprintf’?
[-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.)
--
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmstickynotes
Version: 0.7-3
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 -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0
> -pthread -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o wmstickynotes.o wmstickynotes.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from wmstickynotes.c:8:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
> deprecated [-Wdeprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
> from /usr/include/glib-2.0/gobject/gbinding.h:31,
> from /usr/include/glib-2.0/glib-object.h:24,
> from /usr/include/glib-2.0/gio/gioenums.h:30,
> from /usr/include/glib-2.0/gio/giotypes.h:30,
> from /usr/include/glib-2.0/gio/gio.h:28,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32:
> /usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
> 723 | {
> | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
> from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtk.h:126:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
>73 | GTimeVal last_popdown;
> | ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:34,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:30:
> /usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
> 580 | struct _GTimeVal
> |^
> wmstickynotes.c: In function ‘delete_note’:
> wmstickynotes.c:229:17: error: implicit declaration of function ‘asprintf’;
> did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
> 229 | asprintf(, "%d", note->id);
> | ^~~~
> | vsprintf
> cc1: some warnings being treated as e
Bug#1066418: marked as done (tinyssh: FTBFS: ld: cannot find -lsocket: No such file or directory)
Your message dated Wed, 13 Mar 2024 22:07:27 + with message-id and subject line Bug#1066418: fixed in tinyssh 20240101-3 has caused the Debian Bug report #1066418, regarding tinyssh: FTBFS: ld: cannot find -lsocket: No such file or directory 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.) -- 1066418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tinyssh Version: 20240101-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > sh -e make-tinyssh.sh > === Tue Mar 12 20:33:37 UTC 2024 === obtaining compiler > === Tue Mar 12 20:33:37 UTC 2024 === cc ok > === Tue Mar 12 20:33:37 UTC 2024 === finishing > === Tue Mar 12 20:33:37 UTC 2024 === checking compiler options > === Tue Mar 12 20:33:37 UTC 2024 === -Wdate-time ok > === Tue Mar 12 20:33:37 UTC 2024 === -D_FORTIFY_SOURCE=2 ok > === Tue Mar 12 20:33:37 UTC 2024 === -g ok > === Tue Mar 12 20:33:37 UTC 2024 === -O2 ok > === Tue Mar 12 20:33:37 UTC 2024 === -Werror=implicit-function-declaration > ok > === Tue Mar 12 20:33:37 UTC 2024 === -ffile-prefix-map=/<>=. ok > === Tue Mar 12 20:33:37 UTC 2024 === -fstack-protector-strong ok > === Tue Mar 12 20:33:37 UTC 2024 === -fstack-clash-protection ok > === Tue Mar 12 20:33:37 UTC 2024 === -Wformat ok > === Tue Mar 12 20:33:37 UTC 2024 === -Werror=format-security ok > === Tue Mar 12 20:33:38 UTC 2024 === -fcf-protection ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wl,-z,relro ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wl,-z,now ok > === Tue Mar 12 20:33:38 UTC 2024 === -pedantic ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wall ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wno-long-long ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wno-overlength-strings ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wno-unused-function ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wshadow ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wdeclaration-after-statement ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wwrite-strings ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wmissing-declarations ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wmissing-prototypes ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wstrict-prototypes ok > === Tue Mar 12 20:33:38 UTC 2024 === -Wunused-value ok > === Tue Mar 12 20:33:39 UTC 2024 === -Wunused-parameter ok > === Tue Mar 12 20:33:39 UTC 2024 === -Wundef ok > === Tue Mar 12 20:33:39 UTC 2024 === -fstack-protector-strong ok > === Tue Mar 12 20:33:39 UTC 2024 === -fwrapv ok > === Tue Mar 12 20:33:39 UTC 2024 === -fno-strict-overflow ok > === Tue Mar 12 20:33:39 UTC 2024 === -Os ok > === Tue Mar 12 20:33:39 UTC 2024 === -fomit-frame-pointer ok > === Tue Mar 12 20:33:39 UTC 2024 === -funroll-loops ok > === Tue Mar 12 20:33:39 UTC 2024 === cc -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wl,-z,relro -Wl,-z,now -pedantic -Wall -Wno-long-long > -Wno-overlength-strings -Wno-unused-function -Wshadow > -Wdeclaration-after-statement -Wwrite-strings -Wmissing-declarations > -Wmissing-prototypes -Wstrict-prototypes -Wunused-value -Wunused-parameter > -Wundef -fstack-protector-strong -fwrapv -fno-strict-overflow -Os > -fomit-frame-pointer -funroll-loops > === Tue Mar 12 20:33:39 UTC 2024 === finishing > === Tue Mar 12 20:33:39 UTC 2024 === checking libs > === Tue Mar 12 20:33:39 UTC 2024 === -lutil ok > === Tue Mar 12 20:33:39 UTC 2024 === -lsocket -lnsl failed > === Tue Mar 12 20:33:39 UTC 2024 === finishing > === Tue Mar 12 20:33:39 UTC 2024 === checking $LIBS > === Tue Mar 12 20:33:39 UTC 2024 === finishing > === Tue Mar 12 20:33:39 UTC 2024 === building sysdep headers > === Tue Mar 12 20:33:39 UTC 2024 === hasasmvolatilememory.h > hasasmvolatilememory.h-yes > === Tue Mar 12 20:33:39 UTC 2024 === hasmlock.h hasmlock.h-yes > === Tue Mar 12 20:33:39 UTC 2024 === haslibutilh.h default.h-no > === Tue Mar 12 20:33:39 UTC 2024 === hasutilh.h default.h-no > === Tue Mar 12 20:33:40 UTC 2024
Bug#1066452: marked as done (r-base-dev: missing dependency on libtirpc-dev)
Your message dated Wed, 13 Mar 2024 22:04:11 + with message-id and subject line Bug#1066403: fixed in r-base 4.3.3-3 has caused the Debian Bug report #1066403, regarding r-base-dev: missing dependency on libtirpc-dev 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.) -- 1066403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rapache Version: 1.2.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/share/apr-1.0/build/libtool --mode=link --tag=disable-static > x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -lpcre2-8 > -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0-o mod_R.la -rpath > /usr/lib/apache2/modules -module -avoid-versionmod_R.lo > -Wl,--export-dynamic -fopenmp -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 > -llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n > -L/usr/lib/x86_64-linux-gnu -lapreq2 > libtool: link: x86_64-linux-gnu-gcc -shared -fPIC -DPIC .libs/mod_R.o > -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 -L/usr/lib/R/lib -lR -lpcre2-8 > -llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n > -L/usr/lib/x86_64-linux-gnu -lapreq2 -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z > -Wl,now -Wl,--export-dynamic -fopenmp -Wl,-z -Wl,relro -fopenmp -Wl,-soname > -Wl,mod_R.so -o .libs/mod_R.so > /usr/bin/ld: cannot find -ltirpc: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/rapache_1.2.10-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: r-base Source-Version: 4.3.3-3 Done: Dirk Eddelbuettel We believe that the bug you reported is fixed in the latest version of r-base, 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. Dirk Eddelbuettel (supplier of updated r-base 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: Wed, 13 Mar 2024 13:57:18 -0500 Source: r-base Architecture: source Version: 4.3.3-3 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Closes: 1066403 Changes: r-base (4.3.3-3) unstable; urgency=medium . * debian/control: Add libtirpc-dev to Depends for r-base-dev too (Closes: #1066403) Checksums-Sha1: e830f803eab910aca7c78dbb5d8cb9d5db1af683 2939 r-base_4.3.3-3.dsc d0fc7a27f6b39ca8d5de2c6fd58535e357ac 99652 r-base_4.3.3-3.debian.tar.xz de38a77e9e05ccceb087ad0d5f8ff6b327462f48 18685 r-base_4.3.3-3_amd64.buildinfo Checksums-Sha256: 2cc6bf2a03a8049b9e56d63786c60294fbffdfb915332f0290b5c8fa01e9e17f 2939 r-base_4.3.3-3.dsc 9608923b341950c3afc7d31336e74a0e2d931690987262def50441cb41e35bba 99652 r-base_4.3.3-3.debian.tar.xz cdc626b357ef8de3ba2725d85008843e8adc5034792f64ec77d4e37a6a4d3a54 18685 r-base_4.3.3-3_amd64.buildinfo Files: 49f4ea0e0a9e2f767596160e68550f88 2939 gnu-r optional r-base_4.3.3-3.dsc ce4406b4a62b424e88729f2f313a8c5d 99652 gnu-r optional r-base_4.3.3-3.debian.tar.xz 72e75cc1576b204d0e25db3b6020b235 18685 gnu-r optional r-base_4.3.
Bug#1066455: marked as done (r-base-dev: missing dependency on libtirpc-dev)
Your message dated Wed, 13 Mar 2024 22:04:11 + with message-id and subject line Bug#1066403: fixed in r-base 4.3.3-3 has caused the Debian Bug report #1066403, regarding r-base-dev: missing dependency on libtirpc-dev 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.) -- 1066403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: littler Version: 0.3.19-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -o r -g -O2 -ffile-prefix-map=/build/reproducible-path/r-base-4.3.3=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/share/R/include littler.c -Wl,-z,relro -Wl,--export-dynamic -fopenmp > -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 -llzma -lbz2 -lz -ltirpc -lrt > -ldl -lm -licuuc -licui18n -lblas -llapack -Wl,-rpath,/usr/lib/R/lib > -Wl,-rpath,/usr/lib/x86_64-linux-gnu > -Wl,-rpath,/usr/lib/jvm/default-java/lib/server -Wl,-rpath,/usr/lib/R/lib > -Wl,-rpath,/usr/lib/x86_64-linux-gnu > -Wl,-rpath,/usr/lib/jvm/default-java/lib/server -Wl,-rpath,/usr/lib/R/lib > -Wl,-rpath,/usr/lib/x86_64-linux-gnu > -Wl,-rpath,/usr/lib/jvm/default-java/lib/server > -Wl,-rpath,/usr/lib/x86_64-linux-gnu/libfakeroot > -Wl,-rpath,/usr/lib64/libfakeroot -Wl,-rpath,/usr/lib32/libfakeroot > /usr/bin/ld: cannot find -ltirpc: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/littler_0.3.19-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: r-base Source-Version: 4.3.3-3 Done: Dirk Eddelbuettel We believe that the bug you reported is fixed in the latest version of r-base, 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. Dirk Eddelbuettel (supplier of updated r-base 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: Wed, 13 Mar 2024 13:57:18 -0500 Source: r-base Architecture: source Version: 4.3.3-3 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Closes: 1066403 Changes: r-base (4.3.3-3) unstable; urgency=medium . * debian/control: Add libtirpc-dev to Depends for r-base-dev too (Closes: #1066403) Checksums-Sha1: e830f803eab910aca7c78dbb5d8cb9d5db1af683 2939 r-base_4.3.3-3.dsc d0fc7a27f6b39ca8d5de2c6fd58535e357ac 99652 r-base_4.3.3-3.debian.tar.xz de38a77e9e05ccceb087ad0d5f8ff6b327462f48 18685 r-base_4.3.3-3_amd64.buildinfo Checksums-Sha256: 2cc6bf2a03a8049b9e56d63786c60294fbffdfb915332f0290b5c8fa01e9e17f 2939 r-base_4.3.3-3.dsc 9608923b341950c3afc7d31336e74a0e2d931690987262def50441cb41e35bba 99652 r-base_4.3.3-3.debian.tar.xz cdc626b357ef8de3ba2725d85008843e8adc5034792f64ec77d4e37a6a4d3a54 18685 r-base_4.3.3-3_amd64.buildinfo Files: 49f4ea0e0a9e2f767596160e68550f88 2939 gnu-r optional r-base_4.3.3-3.dsc ce4406b4a62b424e88729f2f313a8c5d 99652 gnu-r optional r-base_4.3.3-3.debian.tar.xz 72e75cc1576b204d0e25db3b6020b235 18685 gnu-r optional
Bug#1066456: marked as done (r-base-dev: missing dependency on libtirpc-dev)
Your message dated Wed, 13 Mar 2024 22:04:11 + with message-id and subject line Bug#1066403: fixed in r-base 4.3.3-3 has caused the Debian Bug report #1066403, regarding r-base-dev: missing dependency on libtirpc-dev 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.) -- 1066403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rpy2 Version: 3.5.15-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:305: python3.12 setup.py config > /usr/bin/ld: cannot find -ltirpc: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/rpy2_3.5.15-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: r-base Source-Version: 4.3.3-3 Done: Dirk Eddelbuettel We believe that the bug you reported is fixed in the latest version of r-base, 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. Dirk Eddelbuettel (supplier of updated r-base 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: Wed, 13 Mar 2024 13:57:18 -0500 Source: r-base Architecture: source Version: 4.3.3-3 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Closes: 1066403 Changes: r-base (4.3.3-3) unstable; urgency=medium . * debian/control: Add libtirpc-dev to Depends for r-base-dev too (Closes: #1066403) Checksums-Sha1: e830f803eab910aca7c78dbb5d8cb9d5db1af683 2939 r-base_4.3.3-3.dsc d0fc7a27f6b39ca8d5de2c6fd58535e357ac 99652 r-base_4.3.3-3.debian.tar.xz de38a77e9e05ccceb087ad0d5f8ff6b327462f48 18685 r-base_4.3.3-3_amd64.buildinfo Checksums-Sha256: 2cc6bf2a03a8049b9e56d63786c60294fbffdfb915332f0290b5c8fa01e9e17f 2939 r-base_4.3.3-3.dsc 9608923b341950c3afc7d31336e74a0e2d931690987262def50441cb41e35bba 99652 r-base_4.3.3-3.debian.tar.xz cdc626b357ef8de3ba2725d85008843e8adc5034792f64ec77d4e37a6a4d3a54 18685 r-base_4.3.3-3_amd64.buildinfo Files: 49f4ea0e0a9e2f767596160e68550f88 2939 gnu-r optional r-base_4.3.3-3.dsc ce4406b4a62b424e88729f2f313a8c5d 99652 gnu-r optional r-base_4.3.3-3.debian.tar.xz 72e75cc1576b204d0e25db3b6020b235 18685 gnu-r optional r-base_4.3.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIVAwUBZfIAD6FIn+KrmaIaAQiaLg/8Dfhhxmo8ZMtFyFguyRd+r5SPdjHefuBl Yt5eeZtOeeiI6l7ttHmbv8Um+jK+ckEU1D5vyPWmc/lLLMRjFshZZjw9sK7de4WQ qPJVqBGIUk2Y+kOhPg3j9H9ivuO926TYOFpxklAcU2dz4ylJTjd2JkO31F5VZex/ QA507KbqWsEzODN1dT5Gia7PAGWAL/2gAyHlAdskRbQfI4y5caGC861QQulQnu3I cuDEuItw7aEH8hmMPCP2wc0vRhODDsF7v7E0d1bZWN3PjwhPZRd5k5GwSSTg9Cz7 Fff9e7ORziVyyNm7V5f8Rg3XAIgvcoIFiP8rxLKZb1sDCa0tlK7q6LDVQ3wIuRt3 msz0KyDTuGLRWmdu35MscsHAKFzZEXoWoHzPLQfAn1tNCUtb/+12PS86w15WncBp yu+G25lN0/UZU5m3SCpZitZVysFpLYSLxANjzCEvkmp7/vcK8oFV56KSwg8nqtQG Kqfja+/pXx7zZ1W+Zeqk+z755a/upE7GdzA7D5PV
Bug#1066403: marked as done (r-base-dev: missing dependency on libtirpc-dev)
Your message dated Wed, 13 Mar 2024 22:04:11 + with message-id and subject line Bug#1066403: fixed in r-base 4.3.3-3 has caused the Debian Bug report #1066403, regarding r-base-dev: missing dependency on libtirpc-dev 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.) -- 1066403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rjava Version: 1.0-11-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -o libjri.so Rengine.o jri.o Rcallbacks.o Rinit.o globals.o rjava.o > rjstring.o -Wl,-z,relro -Wl,-z,relro -shared > -L/usr/lib/jvm/default-java/lib/server -ljvm -Wl,--export-dynamic -fopenmp > -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 -llzma -lbz2 -lz -ltirpc -lrt > -ldl -lm -licuuc -licui18n > /usr/bin/ld: cannot find -ltirpc: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/rjava_1.0-11-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: r-base Source-Version: 4.3.3-3 Done: Dirk Eddelbuettel We believe that the bug you reported is fixed in the latest version of r-base, 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. Dirk Eddelbuettel (supplier of updated r-base 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: Wed, 13 Mar 2024 13:57:18 -0500 Source: r-base Architecture: source Version: 4.3.3-3 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Closes: 1066403 Changes: r-base (4.3.3-3) unstable; urgency=medium . * debian/control: Add libtirpc-dev to Depends for r-base-dev too (Closes: #1066403) Checksums-Sha1: e830f803eab910aca7c78dbb5d8cb9d5db1af683 2939 r-base_4.3.3-3.dsc d0fc7a27f6b39ca8d5de2c6fd58535e357ac 99652 r-base_4.3.3-3.debian.tar.xz de38a77e9e05ccceb087ad0d5f8ff6b327462f48 18685 r-base_4.3.3-3_amd64.buildinfo Checksums-Sha256: 2cc6bf2a03a8049b9e56d63786c60294fbffdfb915332f0290b5c8fa01e9e17f 2939 r-base_4.3.3-3.dsc 9608923b341950c3afc7d31336e74a0e2d931690987262def50441cb41e35bba 99652 r-base_4.3.3-3.debian.tar.xz cdc626b357ef8de3ba2725d85008843e8adc5034792f64ec77d4e37a6a4d3a54 18685 r-base_4.3.3-3_amd64.buildinfo Files: 49f4ea0e0a9e2f767596160e68550f88 2939 gnu-r optional r-base_4.3.3-3.dsc ce4406b4a62b424e88729f2f313a8c5d 99652 gnu-r optional r-base_4.3.3-3.debian.tar.xz 72e75cc1576b204d0e25db3b6020b235 18685 gnu-r optional r-base_4.3.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIVAwUBZfIAD6FIn+KrmaIaAQiaLg/8Dfhhxmo8ZMtFyFguyRd+r5SPdjHefuBl Yt5eeZtOeeiI6l7ttHmbv8Um+jK+ckEU1D5vyPWmc/lLLMRjFshZZjw9sK7de4WQ qPJVqBGIUk2Y+kOhPg3j9H9ivuO926TYOFpxklAcU2dz4ylJTjd2JkO31F5VZex/ QA507KbqWsEzODN1dT5Gia7PAGWAL/2gAyHlAdskRbQfI4y5caGC861QQulQnu3I cuDEuItw7aEH8hmMPCP2wc0vRhODDsF7v7E0d1bZWN3PjwhPZRd5k5GwSSTg9Cz7 Fff9e7ORziVyyNm7V5f8Rg3XAIgvcoIFiP8rxLKZb1sDCa0tlK7q6LDVQ3wIuRt3 msz0KyDTuGLRWmdu35MscsHAKFzZEXoWoHzPLQfAn1tNCUtb/+12PS86w15WncBp yu+G25lN0/UZU5m3SCpZitZVysFpLYSLxANjzCEvkmp7/vcK8oFV56KSwg8nqtQG Kqfja
Bug#1066497: marked as done (qfits: FTBFS: dtfits.c:163:13: error: implicit declaration of function ‘qfits_query_n_ext’; did you mean ‘qfits_query_column’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 22:01:55 + with message-id and subject line Bug#1066497: fixed in qfits 6.2.0-9 has caused the Debian Bug report #1066497, regarding qfits: FTBFS: dtfits.c:163:13: error: implicit declaration of function ‘qfits_query_n_ext’; did you mean ‘qfits_query_column’? [-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.) -- 1066497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qfits Version: 6.2.0-8 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 -DHAVE_CONFIG_H -I. -I.. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o replacekey.o replacekey.c > dtfits.c: In function ‘qfits_dump’: > dtfits.c:163:13: error: implicit declaration of function ‘qfits_query_n_ext’; > did you mean ‘qfits_query_column’? [-Werror=implicit-function-declaration] > 163 | n_ext = qfits_query_n_ext(name_i); > | ^ > | qfits_query_column > qextract.c: In function ‘main’: > qextract.c:69:14: error: implicit declaration of function > ‘qfits_query_n_ext’; did you mean ‘qfits_query_column’? > [-Werror=implicit-function-declaration] >69 | nb_ext = qfits_query_n_ext(name_in) ; > | ^ > | qfits_query_column > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wl,-z,relro -o replacekey > replacekey.o ../src/libqfits.la -lm > cc1: some warnings being treated as errors > make[3]: *** [Makefile:472: qextract.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/qfits_6.2.0-8_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: qfits Source-Version: 6.2.0-9 Done: Aurelien Jarno We believe that the bug you reported is fixed in the latest version of qfits, 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. Aurelien Jarno (supplier of updated qfits 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 21:34:25 +0100 Source: qfits Architecture: source Version: 6.2.0-9 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno Changed-By: Aurelien Jarno Closes: 1066497 Changes: qfits (6.2.0-9) unstable; urgency=medium . * Add 08-implicit-function-declaration.diff patch to fix FTBFS with -Werror=implicit-function-declaration (closes: #1066497). * Mark libqfits-dev as Multi-Arch: same. * Swi
Bug#1066822: linuxtv-dvb-apps: FTBFS on arm{el,hf}: evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’
Source: linuxtv-dvb-apps Version: 1.1.1+rev1500-1.4 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=linuxtv-dvb-apps=armhf=1.1.1%2Brev1500-1.4%2Bb1=1710350526=0 test_video.c: In function ‘play_file_video’: test_video.c:245:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 245 | write(fd,buf,count); | ^~~ CC evtest evtest.c: In function ‘main’: evtest.c:244:38: error: ‘struct input_event’ has no member named ‘time’ 244 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, | ^ evtest.c:244:57: error: ‘struct input_event’ has no member named ‘time’ 244 | ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type, | ^ make[2]: *** [../Make.rules:82: evtest] Error 1 Cheers -- Sebastian Ramacher
Bug#1066299: marked as done (lcrq: FTBFS: test.c:208:26: error: implicit declaration of function ‘getrandom’; did you mean ‘srandom’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 21:46:23 + with message-id and subject line Bug#1066299: fixed in lcrq 0.1.2-1 has caused the Debian Bug report #1066299, regarding lcrq: FTBFS: test.c:208:26: error: implicit declaration of function ‘getrandom’; did you mean ‘srandom’? [-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.) -- 1066299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lcrq Version: 0.1.1-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): > gcc -I../src -I ../include -I../src -I ../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o test.o test.c > test.c: In function ‘test_randombytes’: > test.c:208:26: error: implicit declaration of function ‘getrandom’; did you > mean ‘srandom’? [-Werror=implicit-function-declaration] > 208 | return_ignored = getrandom(buf, len, 0); > | ^ > | srandom > cc1: some warnings being treated as errors > make[4]: *** [: test.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/lcrq_0.1.1-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: lcrq Source-Version: 0.1.2-1 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of lcrq, 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. Vagrant Cascadian (supplier of updated lcrq 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 12:39:37 -0700 Source: lcrq Architecture: source Version: 0.1.2-1 Distribution: unstable Urgency: medium Maintainer: Vagrant Cascadian Changed-By: Vagrant Cascadian Closes: 1048192 1066299 Changes: lcrq (0.1.2-1) unstable; urgency=medium . * New upstream release. (Closes: #1066299) * debian/rules: Add dh_auto_clean override to remove leftover cruft. (Closes: #1048192) Checksums-Sha1: 315ae345ebf3cd96c66904803550b883822491c0 1273 lcrq_0.1.2-1.dsc c622108e5e1ec02b8d5d6a642d7aa3b6bbac4866 557499 lcrq_0.1.2.orig.tar.gz f7c5a96b2436c9735429778f3869bdfeb0b4db63 2892 lcrq_0.1.2-1.debian.tar.xz 754c499d09fede3a2e96715fa1ba8a086d34a96b 5935 lcrq_0.1.2-1_amd64.buildinfo Checksums-Sha256: 0218ea0175cce709cb975d233bcea6ba374c0477a442cb3400702761a3dcd4e2 1273 lcrq_0.1.2-1.dsc 6375e3b108f44a8c04eae3cbbca240c71f03c869c8b3c0aeef08c01e19a12dea 557499 lcrq_0.1.2.orig.tar.gz 1441efbe960acc6681bf4025049558f7a72ec1f32c2d2e4f932ffc0b015abc09 2892 lcrq_0.1.2-1.debian.tar.xz 3b614d66ad10f08d7259d3be7088cbd094efa9add1ed6e27425f3f6d229bbfe5 5935 lcrq_0.1.2-1_amd64.buildinfo Files: 0ced52c3209ed81c22eb1d
Processed: Re: consolekit: install PAM module and udev files into /usr
Processing control commands:
> found -1 1.2.6-3.1~exp1
Bug #1061493 {Done: Michael Hudson-Doyle }
[src:consolekit2] consolekit: install PAM module and udev files into /usr
The source 'consolekit2' and version '1.2.6-3.1~exp1' do not appear to match
any binary packages
Marked as found in versions consolekit2/1.2.6-3.1~exp1; no longer marked as
fixed in versions consolekit2/1.2.6-3.1~exp1 and reopened.
> severity -1 serious
Bug #1061493 [src:consolekit2] consolekit: install PAM module and udev files
into /usr
Severity set to 'serious' from 'normal'
> tag -1 ftbfs
Bug #1061493 [src:consolekit2] consolekit: install PAM module and udev files
into /usr
Added tag(s) ftbfs.
--
1061493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066534: marked as done (daligner: FTBFS: ONElib.c:1792:29: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 21:39:03 +
with message-id
and subject line Bug#1066534: fixed in daligner 1.0+git20240119.335105d-2
has caused the Debian Bug report #1066534,
regarding daligner: FTBFS: ONElib.c:1792:29: error: implicit declaration of
function ‘vasprintf’; did you mean ‘vsprintf’?
[-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.)
--
1066534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: daligner
Version: 1.0+git20240119.335105d-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):
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -O3 -Wall -Wextra -Wno-unused-result
> -fno-strict-aliasing -o ONE2LA ONE2LA.c align.c DB.c QV.c ONElib.c -lm
> -Wl,-z,relro -Wl,-z,now
> ONE2LA.c: In function ‘main’:
> ONE2LA.c:135:13: warning: assignment to ‘int64 *’ {aka ‘long long int *’}
> from incompatible pointer type ‘I64 *’ {aka ‘long int *’}
> [-Wincompatible-pointer-types]
> 135 | list = oneIntList(file1);
> | ^
> ONE2LA.c:202:20: warning: assignment to ‘int64 *’ {aka ‘long long int *’}
> from incompatible pointer type ‘I64 *’ {aka ‘long int *’}
> [-Wincompatible-pointer-types]
> 202 | list = oneIntList(file1);
> |^
> ONE2LA.c:210:20: warning: assignment to ‘int64 *’ {aka ‘long long int *’}
> from incompatible pointer type ‘I64 *’ {aka ‘long int *’}
> [-Wincompatible-pointer-types]
> 210 | list = oneIntList(file1);
> |^
> ONE2LA.c:220:20: warning: assignment to ‘int64 *’ {aka ‘long long int *’}
> from incompatible pointer type ‘I64 *’ {aka ‘long int *’}
> [-Wincompatible-pointer-types]
> 220 | list = oneIntList(file1);
> |^
> ONE2LA.c:227:20: warning: assignment to ‘int64 *’ {aka ‘long long int *’}
> from incompatible pointer type ‘I64 *’ {aka ‘long int *’}
> [-Wincompatible-pointer-types]
> 227 | list = oneIntList(file1);
> |^
> ONE2LA.c:30:20: warning: variable ‘small’ set but not used
> [-Wunused-but-set-variable]
>30 | int tspace, small, tbytes;
> |^
> ONElib.c: In function ‘oneSchemaCreateDynamic’:
> ONElib.c:35:19: warning: statement with no effect [-Wunused-value]
>35 | #define assert(x) 0
> | ^
> ONElib.c:390:3: note: in expansion of macro ‘assert’
> 390 | assert (fileType && strlen(fileType) > 0) ;
> | ^~
> ONElib.c:35:19: warning: statement with no effect [-Wunused-value]
>35 | #define assert(x) 0
> | ^
> ONElib.c:391:3: note: in expansion of macro ‘assert’
> 391 | assert (!subType || strlen(subType) > 0) ;
> | ^~
> ONElib.c: In function ‘oneReadLine’:
> ONElib.c:35:19: warning: statement with no effect [-Wunused-value]
>35 | #define assert(x) 0
> | ^
> ONElib.c:943:3: note: in expansion of macro ‘assert’
> 943 | assert (!vf->isWrite) ;
> | ^~
> ONElib.c:35:19: warning: statement with no effect [-Wunused-value]
>35 | #define assert(x) 0
> | ^
> ONElib.c:944:3: note: in expansion of macro ‘assert’
> 944 | assert (!vf->isFinal) ;
> | ^~
> ONElib.c: In function ‘oneFileOpenRead’:
> ONElib.c:35:19: warning: statement with no effect [-Wunused-value]
>35 | #define assert(x) 0
> | ^
> ONElib.c:1156:3: note: in expansion of macro ‘assert’
> 1156 | assert (fileType == NULL || strlen(fileType) > 0) ;
> | ^~
> ONElib.c: In function ‘addProvenance’:
> ONElib.c:35:19: warning
Bug#1064950: marked as done (apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.)
Your message dated Wed, 13 Mar 2024 22:29:55 +0100
with message-id
and subject line Re: AW: AW: Bug#1064950: apache2: (Legacy?) "Depends:
apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.
has caused the Debian Bug report #1064950,
regarding apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in
debian/control breaks binNMU builds.
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.)
--
1064950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in
debian/control breaks binNMU builds.
Source: apache2
X-Debbugs-Cc: christof.warl...@siemens.com
Version: 2.4.57-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: patch ftbfs
Dear Maintainer,
(re)building apache2 as binNMU (i.e. with appending "+b to the
package version")
works, but installation of the resulting apache2 package fails due to the
following dependency
in debian/control:
Depends: apache2-data (= ${source:Version}),
It causes apt-get to look for the dependency "apache2-data" (= 2.4.57-2) which
does not exist
in the newly built packages. Instead, the dependency should be satisfied by
"apache2-data (= 2.4.57-2+b)".
The folliwing patch fixes the issue:
diff --git a/debian/control b/debian/control
index 2eddc60..31121fa 100644
--- a/debian/control
+++ b/debian/control
@@ -34,7 +34,7 @@ Rules-Requires-Root: binary-targets
Package: apache2
Architecture: any
Depends: apache2-bin (= ${binary:Version}),
- apache2-data (= ${source:Version}),
+ apache2-data (= ${binary:Version}),
apache2-utils (= ${binary:Version}),
lsb-base,
media-types,
Please consider applying the patch.
Best regards,
Christof Warlich
P.S.: Note that the information below, being produced by "reportbug", is
irrelevant as I executed "reportbug"
on WSL2 on Windows 10. The actual Debian version is "bookworm".
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.102.1-microsoft-standard-WSL2+ (SMP w/16 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 2024-03-04 12:33:39 +, Warlich, Christof wrote:
> Sebastian Ramacher wrote:
> > Christof Warlich wrote:
> > > If this assumption is true, then why is the Debian build system (i.e.
> > > dpkg-buildpackage) not smart enough to simply ignore an existing +bX
> > > extension for Architecture: all binary packages? IMHO, this would
> > > simplify matters, as it would have avoided the pitfall that I stumbled
> > > into altogether.
> >
> > binNMUs are handled a layer above. sbuild will pass the correct options to
> > dpkg-buildpackage to build binNMUs. If you are interested in having binNMU
> > builds for your own infrastructure, you'll probably need to take a look at
> > the sbuild source to see how it is implemented.
>
> Ok, so I'd better start using sbuild instead. Again, thanks for the valuable
> info and your time.
Closing this bug.
Cheers
--
Sebastian Ramacher--- End Message ---
Bug#1066821: apr-util: FTBFS on arm{el,hf}: /bin/bash: line 3: 3132384 Segmentation fault LD_LIBRARY_PATH="`echo "../crypto/.libs:../dbm/.libs:../dbd/.libs:../ldap/.libs:$LD_LIBRARY_PATH" | sed -
Source: apr-util Version: 1.6.3-1.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=apr-util=armhf=1.6.3-1.1=1709086833=0 testldap: SUCCESS testdbd : SUCCESS testdate: SUCCESS testmemcache: Error 111 occurred attempting to reach memcached on localhost:11211. Skipping apr_memcache tests... SUCCESS testredis : Error 111 occurred attempting to reach Redis on localhost:6379. Skipping apr_redis tests... SUCCESS testxml : SUCCESS testxlate : SUCCESS testrmm : SUCCESS testdbm : BDB1565 DB->put: method not permitted before handle's open method /bin/bash: line 3: 3132384 Segmentation fault LD_LIBRARY_PATH="`echo "../crypto/.libs:../dbm/.libs:../dbd/.libs:../ldap/.libs:$LD_LIBRARY_PATH" | sed -e 's/::*$//'`" ./$prog -v Programs failed: testall make[2]: *** [Makefile:60: check] Error 139 Cheers -- Sebastian Ramacher
Processed: Bug#1066633 marked as pending in poa
Processing control commands: > tag -1 pending Bug #1066633 [src:poa] poa: FTBFS: fasta_format.c:48:9: error: implicit declaration of function ‘stringptr_cat_pos’; did you mean ‘stringptr_cat’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066633: marked as pending in poa
Control: tag -1 pending Hello, Bug #1066633 in poa reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/poa/-/commit/321a813c57dcfaf6c8937bf5d4976da90af08c69 fix-declaration.patch: new: fix missing declarations. Closes: #1066633 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066633
Bug#1066498: dh-make-perl: autopkgtest regression due to time_t transition
On Wed, Mar 13, 2024 at 05:39:49PM +0100, gregor herrmann via pkg-perl-maintainers wrote: > On Wed, 13 Mar 2024 13:34:57 +0100, gregor herrmann wrote: > > > > 80s not ok 5 - Errno is in libperl5.38 or perl-base (or only perl-base > > > for perl < 5.22) > > libperl5.38 or as it's called nowadays: libperl5.38t64, that's the > > point probably … > > Fix committed in git. > > Reviews welcome; I'm not sure it's the most elegant and safe solution, > and also if this libperl5.38t64 naming has other effects. Thanks for fixing this. Didn't dig deeply into what the test is actually doing, but I think it'd be fine to just hardcode libperl5.38t64 FWIW. We can get rid of the suffix with 5.40, and I doubt any other distro will go through this than Ubuntu who we're syncing with anyway (for better or worse). But whatever works is good of course. -- Niko
Processed: Bug#1066534 marked as pending in daligner
Processing control commands: > tag -1 pending Bug #1066534 [src:daligner] daligner: FTBFS: ONElib.c:1792:29: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066534: marked as pending in daligner
Control: tag -1 pending Hello, Bug #1066534 in daligner reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/daligner/-/commit/3043c218631b8dc8d36a05feddd54d3e6f5c9359 fix-missing-include.patch: new: fix ftbfs with dpkg. Closes: #1066534 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066534
Bug#1066338: marked as done (emoslib: FTBFS: describe_input_field.c:463:17: error: implicit declaration of function ‘jnumgg_’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 19:47:32 +
with message-id
and subject line Bug#1066338: fixed in emoslib 2:4.5.9-10
has caused the Debian Bug report #1066338,
regarding emoslib: FTBFS: describe_input_field.c:463:17: error: implicit
declaration of function ‘jnumgg_’ [-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.)
--
1066338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emoslib
Version: 2:4.5.9-9
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):
> cd /<>/obj-x86_64-linux-gnu/libemos-dp-shared && /usr/bin/cc
> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT
> -DPOINTER_64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE64_SOURCE -Demos_shared_EXPORTS -Dgfortran -Dlinux
> -I/<>/obj-x86_64-linux-gnu/module -I/<>
> -I/<>/obj-x86_64-linux-gnu -I/<>/interpolation
> -I/<>/bufrdc_wmo -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC -fPIC
> -mcmodel=medium -MD -MT
> libemos-dp-shared/CMakeFiles/emos_shared.dir/__/interpolation/emos.c.o -MF
> CMakeFiles/emos_shared.dir/__/interpolation/emos.c.o.d -o
> CMakeFiles/emos_shared.dir/__/interpolation/emos.c.o -c
> /<>/interpolation/emos.c
> /<>/interpolation/sharedlib.c: In function ‘share_file’:
> /<>/interpolation/sharedlib.c:294:49: warning: format ‘%lld’
> expects argument of type ‘long long int’, but argument 3 has type ‘__off_t’
> {aka ‘long int’} [-Wformat=]
> 294 | fprintf( stdout, "sharedmem:read %lld bytes in %g
> secs\n",s2.st_size, time);
> | ~~~^
> ~~
> | |
> |
> | long long int
> __off_t {aka long int}
> | %ld
> /<>/interpolation/describe_input_field.c: In function
> ‘describe_input_field’:
> /<>/interpolation/describe_input_field.c:463:17: error: implicit
> declaration of function ‘jnumgg_’ [-Werror=implicit-function-declaration]
> 463 | jnumgg_(,,kpts,);
> | ^~~
> [ 45%] Building C object
> libemos-dp-shared/CMakeFiles/emos_shared.dir/__/interpolation/intf2.c.o
> cd /<>/obj-x86_64-linux-gnu/libemos-dp-shared && /usr/bin/cc
> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT
> -DPOINTER_64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE64_SOURCE -Demos_shared_EXPORTS -Dgfortran -Dlinux
> -I/<>/obj-x86_64-linux-gnu/module -I/<>
> -I/<>/obj-x86_64-linux-gnu -I/<>/interpolation
> -I/<>/bufrdc_wmo -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC -fPIC
> -mcmodel=medium -MD -MT
> libemos-dp-shared/CMakeFiles/emos_shared.dir/__/interpolation/intf2.c.o -MF
> CMakeFiles/emos_shared.dir/__/interpolation/intf2.c.o.d -o
> CMakeFiles/emos_shared.dir/__/interpolation/intf2.c.o -c
> /<>/interpolation/intf2.c
> [ 45%] Building C object
> libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/__/interpolation/sharedll.c.o
> cd /<>/obj-x86_64-linux-gnu/libemos-sp-shared && /usr/bin/cc
> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT
> -DPOINTER_64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE
> -Demos_sp_shar
Processed: Re: gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments
Processing commands for cont...@bugs.debian.org: > reassign 1065547 src:pygobject 3.47.0-1 Bug #1065547 [src:gst-python1.0] gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments Bug reassigned from package 'src:gst-python1.0' to 'src:pygobject'. No longer marked as found in versions gst-python1.0/1.23.90-1. Ignoring request to alter fixed versions of bug #1065547 to the same values previously set Bug #1065547 [src:pygobject] gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments Marked as found in versions pygobject/3.47.0-1. > affects 1065547 src:gst-python1.0 Bug #1065547 [src:pygobject] gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments Added indication that 1065547 affects src:gst-python1.0 > tags 1065547 +trixie Bug #1065547 [src:pygobject] gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments Added tag(s) trixie. > forwarded 1065547 https://gitlab.gnome.org/GNOME/pygobject/-/issues/624 Bug #1065547 [src:pygobject] gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments Changed Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/pygobject/-/issues/624' from 'https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1065547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]
Andrey Rakhmatullin dixit: >On Wed, Mar 13, 2024 at 12:36:37PM +0100, Lucas Nussbaum wrote: >> > gssapi.c:1600:9: error: implicit declaration of function >> > ‘gsskrb5_register_acceptor_identity’ >> > [-Werror=implicit-function-declaration] >> > 1600 | gsskrb5_register_acceptor_identity(keytab_path); >> > | ^~ >The function should be declared in , in this case it's >/usr/include/heimdal/gssapi/gssapi_krb5.h from heimdal-multidev, but >build-heimdal/config.h defines HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY but >doesn't define HAVE_GSSAPI_GSSAPI_KRB5_H, so is not >included but the code is compiled. That’s because m4/sasl2.m4… AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity) if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then AC_CHECK_HEADERS(gssapi/gssapi_krb5.h) if test "$ac_cv_header_gssapi_gssapi_krb5_h" = "yes"; then AC_CHECK_DECL(gsskrb5_register_acceptor_identity, [AC_DEFINE(HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY,1, [Define if your GSSAPI implementation defines gsskrb5_register_acceptor_identity])],, [ AC_INCLUDES_DEFAULT #include ]) fi fi … only checks for the header file if gsskrb5_register_acceptor_identity is not found without it included. Suggested fix: + AC_CHECK_HEADERS(gssapi/gssapi_krb5.h) AC_CHECK_FUNCS(gsskrb5_register_acceptor_identity) if test "$ac_cv_func_gsskrb5_register_acceptor_identity" = no ; then - AC_CHECK_HEADERS(gssapi/gssapi_krb5.h) If it’s really that, anyway. bye, //mirabilos -- When he found out that the m68k port was in a pretty bad shape, he did not, like many before him, shrug and move on; instead, he took it upon himself to start compiling things, just so he could compile his shell. How's that for dedication. -- Wouter, about my Debian/m68k revival
Bug#1064967: fontforge DSA (was: Re: Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1)
Hi Adrian, On Fri, Mar 08, 2024 at 02:03:55AM +0200, Adrian Bunk wrote: > Control: tags 1064967 + patch > Control: tags 1064967 + pending > > Dear maintainer, > > I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. > > @Security team: > If wanted, I could afterwards also prepare (pu or DSA) updates for > bookworm and bullseye. We came to the conclusion that it warrants a DSA. Could you prepare debdiffs for bookworm-security and bulseye-security? Regards, Salvatore
Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration
Hi again, >on 1.x or 2.4 before the weekend. I just tested the 2.2 patch on gnupg1, and it applies cleanly, and configure also seems happy: […] checking whether the resolver is usable... yes checking whether LDAP via "-lldap" is present and sane... yes checking for ldap_get_option... yes checking for ldap_set_option... yes checking for ldap_start_tls_s... yes checking for ldap_start_tls_sA... no checking for gawk... (cached) mawk […] For gnupg1, the B-D are also already installable, so there’s no current need to modify them there, just apply the same patch as was applied in gnupg2 2.2 and upload. Thanks, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh
Bug#1066811: cyrus-sasl2: assumes time_t fits into long for printf and scanf(!), will break on big endian
Source: cyrus-sasl2
Version: 2.1.28+dfsg1-4
Severity: serious
Justification: breaks
X-Debbugs-Cc: t...@mirbsd.de
cyrus-sasl2, before aborting the build due to #1066214, spews
several warnings like the following:
[…]
otp.c:648:43: warning: format '%ld' expects argument of type 'long int', but
argument 7 has type 'time_t' {aka 'long long int'} [-Wformat=]
648 | sprintf(data, "%s\t%04d\t%s\t%s\t%020ld",
| ~^
| |
| long int
| %020lld
649 | alg, seq, seed, buf, timeout);
| ~~~
| |
| time_t {aka long long int}
otp.c:709:48: warning: format '%ld' expects argument of type 'long int *', but
argument 7 has type 'time_t *' {aka 'long long int *'} [-Wformat=]
709 | sscanf(secret, "%s\t%04d\t%s\t%s\t%020ld",
| ~^
||
|long int *
| %020lld
710 |alg, seq, seed, buf, timeout);
| ~~~
| |
| time_t * {aka long long int *}
[…]
These are actual problems that not only result in bad data
being printed or read but, if the time_t argument is not
(like here) the last one, also wrong arguments being used
for subsequent positional parameters.
Please fix *all* -Wformat mismatches involving time_t, for
example:
- sprintf(data, "%s\t%04d\t%s\t%s\t%020ld",
+ sprintf(data, "%s\t%04d\t%s\t%s\t%020lld",
- alg, seq, seed, buf, timeout);
+ alg, seq, seed, buf, (long long)timeout);
+ long long tmptimeout;
- sscanf(secret, "%s\t%04d\t%s\t%s\t%020ld",
+ sscanf(secret, "%s\t%04d\t%s\t%s\t%020lld",
- alg, seq, seed, buf, timeout);
+ alg, seq, seed, buf, tmptimeout);
+ timeout = tmptimeout;
Justification: I’ve been fixing bugs like these on MirBSD
since its i386 port switched to 64-bit time_t in 2004…
Thanks,
//mirabilos
--
16:47⎜«mika:#grml» .oO(mira ist einfach gut) 23:22⎜«mikap:#grml»
mirabilos: und dein bootloader ist geil :)23:29⎜«mikap:#grml» und ich
finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann
gleich mal auf usb-stick installieren -- Michael Prokop über MirOS bsd4grml
Bug#1066668: marked as done (sphinxtrain: FTBFS: lexicon.c:202:19: error: implicit declaration of function ‘str2words’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 19:02:22 + with message-id and subject line Bug#108: fixed in sphinxtrain 1.0.8+5prealpha+1-6 has caused the Debian Bug report #108, regarding sphinxtrain: FTBFS: lexicon.c:202:19: error: implicit declaration of function ‘str2words’ [-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.) -- 108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinxtrain Version: 1.0.8+5prealpha+1-5 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../../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu/sphinxbase > -I../../../include -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -DPIC -c -o lexicon.lo lexicon.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c ck_seg.c -fPIC -DPIC > -o .libs/ck_seg.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c best_q.c -fPIC -DPIC > -o .libs/best_q.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c acmod_set.c -fPIC > -DPIC -o .libs/acmod_set.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c cvt2triphone.c -fPIC > -DPIC -o .libs/cvt2triphone.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c dtree.c -fPIC -DPIC > -o .libs/dtree.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -fPIC -DPIC -c heap.c -fPIC -DPIC -o > .libs/heap.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu > -I/usr/include/x86_64-linux-gnu/sphinxbase -I../../../include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protect
Bug#1066473: marked as done (multitail: FTBFS: mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean ‘waddnstr’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 18:58:15 +
with message-id
and subject line Bug#1066473: fixed in multitail 6.5.0-6
has caused the Debian Bug report #1066473,
regarding multitail: FTBFS: mt.c:707:25: error: implicit declaration of
function ‘waddnwstr’; did you mean ‘waddnstr’?
[-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.)
--
1066473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: multitail
Version: 6.5.0-5
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):
> cc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wall -Wno-unused-parameter -funsigned-char -O3 -DLinux -DVERSION=\"6.5.0\"
> -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -DCONFIG_FILE=\"/etc/multitail.conf\" -MMD -MP -DUTF8_SUPPORT -c -o mt.o mt.c
> mt.c: In function ‘do_color_print’:
> mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you
> mean ‘waddnstr’? [-Werror=implicit-function-declaration]
> 707 | waddnwstr(win -> win, , 1);
> | ^
> | waddnstr
> mt.c: In function ‘update_statusline’:
> mt.c:1467:126: warning: format ‘%lld’ expects argument of type ‘long long
> int’, but argument 5 has type ‘off64_t’ {aka ‘long int’} [-Wformat=]
> 1467 | mvwprintw(status ->
> win, 0, win_width - (strlen(timestamp) + cur_len), "%10lld - %s", fsize,
> timestamp);
> |
> ~^~
> |
>||
> |
>|off64_t {aka
> long int}
> |
>long long int
> |
> %10ld
> cc1: some warnings being treated as errors
> make[2]: *** [: mt.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/multitail_6.5.0-5_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: multitail
Source-Version: 6.5.0-6
Done: Rene Engelhard
We believe that the bug you reported is fixed in the latest version of
multitail, 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 maintenan
Processed: tagging 1066668
Processing commands for cont...@bugs.debian.org: > tags 108 + pending Bug #108 [src:sphinxtrain] sphinxtrain: FTBFS: lexicon.c:202:19: error: implicit declaration of function ‘str2words’ [-Werror=implicit-function-declaration] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: gnome-shell-extension-manager: FTBFS
Processing commands for cont...@bugs.debian.org: > forwarded 1066393 https://github.com/mjakeman/extension-manager/issues/590 Bug #1066393 [src:gnome-shell-extension-manager] gnome-shell-extension-manager: FTBFS: ../src/main.c:168:9: error: implicit declaration of function ‘waitpid’ [-Werror=implicit-function-declaration] Set Bug forwarded-to-address to 'https://github.com/mjakeman/extension-manager/issues/590'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1066393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base
On 13 March 2024 at 19:06, Aurelien Jarno wrote: | control: reassign 1066403 r-base-dev | control: reassign 1066452 r-base-dev | control: reassign 1066455 r-base-dev | control: reassign 1066456 r-base-dev | control: forcemerge 1066403 1066452 1066455 1066456 | control: affects 1066403 rjava | control: affects 1066403 rapache | control: affects 1066403 littler | control: affects 1066403 rpy2 | control: retitle 1066403 r-base-dev: missing dependency on libtirpc-dev | | Hi Dirk, | | There are 4 r-base packages failing to build in the latest archive | rebuild: | | #1066403 rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory | #1066452 rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory | #1066455 littler: FTBFS: ld: cannot find -ltirpc: No such file or directory | #1066456 rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory | | Investigating, it appears that the issue is actually at the r-base | level. They try to link with -ltirpc because R tell them to do so: | | $ R CMD config --ldflags | -Wl,--export-dynamic -fopenmp -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 -llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n | | Therefore it seems that r-base-dev is missing a dependency on | libtirpc-dev. Sorry for not having noticed that when filling #1065216. I should have noticed that too when I prepared 4.3.3-2 from your #1065216: r-base (4.3.3-2) unstable; urgency=medium * debian/control: Add libtirpc-dev to Build-Depends to fix build issue from side effects of t64 transition (Closes: #1065216) -- Dirk Eddelbuettel Mon, 04 Mar 2024 08:54:45 -0600 I will take care of it in -3. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 1066473 + pending Bug #1066473 [src:multitail] multitail: FTBFS: mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean ‘waddnstr’? [-Werror=implicit-function-declaration] Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1066473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066469: tack: FTBFS: configure: error: No curses header-files found
On Wed, Mar 13, 2024 at 07:03:29PM +0100, Sven Joachim wrote: > On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote: > > > Source: tack > > Version: 1.08-1 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20240313 ftbfs-trixie > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > > > Relevant part (hopefully): > >> configure: WARNING: pkg-config is not installed > >> checking for specific curses-directory... no > >> checking for specified curses library type... curses > >> checking for extra include directories... no > >> checking if we have identified curses headers... none > >> configure: error: No curses header-files found > >>tail -v -n \+0 config.log > > This reminds me that I really should update the tack package to a newer > version. The error is still present in tack 1.09 (the latest stable > release), but fixed as of tack 1.09-20230201 (the latest development > snapshot). > > @Thomas: since tack 1.09 is more than four years old and there has been > no new snapshot for over a year, how about releasing tack 1.10? This > bug will likely hit other distros as they upgrade to GCC 14. I suppose so - though others seem okay with the snapshots (I'll take a look "soon" - am working on Lynx at the moment) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration
Hi Andreas >I have upload a fix for 2.2 OK, that should help. >probably will not be able to spend any time on 1.x or 2.4 before the weekend. They can probably wait until then, no worries. >It is fixed in 2.4 and I am very reluctant to backport major packaging >updates to 2.2 For some values of major; Helmut already verified that the resulting binary packages are identical, and… >since I think we will need to ship some kind of 2.4 in trixie. … this massively helps with the current transition in unstable, which has to come before thinking of trixie. Even gdb-13 has temporarily lost its gdb B-D, and pam temporarily broke ABI by not including one module, to help the transition. For gnupg2 this is a no-change-in-binary source change, so of much less impact. Thanks, //mirabilos -- Gast: „Ein Bier, bitte!“ Wirt: „Geht auch alkoholfrei?“ Gast: „Geht auch Spielgeld?“
Bug#1066412: marked as done (hdf-eos5: FTBFS: gcc: error: unrecognized command-line option '-V')
Your message dated Wed, 13 Mar 2024 18:23:29 + with message-id and subject line Bug#1066412: fixed in hdf-eos5 2:2.0-2 has caused the Debian Bug report #1066412, regarding hdf-eos5: FTBFS: gcc: error: unrecognized command-line option '-V' 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.) -- 1066412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hdf-eos5 Version: 2:2.0-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 13.2.0 (Debian 13.2.0-18) > ... rest of stderr output deleted ... > configure:4368: $? = 1 > configure:4357: /usr/bin/h5cc -V >&5 > gcc: error: unrecognized command-line option '-V' > configure:4368: $? = 1 > configure:4357: /usr/bin/h5cc -qversion >&5 > gcc: error: unrecognized command-line option '-qversion'; did you mean > '--version'? > configure:4368: $? = 1 > configure:4357: /usr/bin/h5cc -version >&5 > gcc: error: unrecognized command-line option '-version' > configure:4368: $? = 1 > configure:4388: checking whether the C compiler works > configure:4410: /usr/bin/h5cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -D_HDFEOS5_THREADSAFE -Df2cFortran -Wdate-time -D_FORTIFY_SOURCE=2 > -Wl,-z,relro -lpthread conftest.c >&5 > configure:4414: $? = 0 > configure:4464: result: yes > configure:4467: checking for C compiler default output file name > configure:4469: result: a.out > configure:4475: checking for suffix of executables > configure:4482: /usr/bin/h5cc -o conftest -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_HDFEOS5_THREADSAFE -Df2cFortran > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -lpthread conftest.c >&5 > configure:4486: $? = 0 > configure:4509: result: > configure:4531: checking whether we are cross compiling > configure:4539: /usr/bin/h5cc -o conftest -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_HDFEOS5_THREADSAFE -Df2cFortran > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -lpthread conftest.c >&5 > configure:4543: $? = 0 > configure:4550: ./conftest > configure:4554: $? = 0 > configure:4569: result: no > configure:4574: checking for suffix of object files > configure:4597: /usr/bin/h5cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -D_HDFEOS5_THREADSAFE -Df2cFortran -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > >&5 > configure:4601: $? = 0 > configure:4623: result: o > configure:4627: checking whether the compiler supports GNU C > configure:4647: /usr/bin/h5cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -D_HDFEOS5_THREADSAFE -Df2cFortran -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c > >&5 > configure:4647: $? = 0 > configure:4657: result: yes > configure:4668: checking whether /usr/bin/h5cc accepts -g > configure:4689: /usr/bin/h5cc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 > conftest.c >&5 > configure:4689: $? = 0 > configure:4733: result: yes > configure:4753: checking for /usr/bin/h5cc option to enable C11 features > configure:4768: /usr/bin/h5cc -c -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_HDFEOS5_THREADSAFE -Df2cFortran > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:4768: $? = 0 > configure:4786: result: none needed > configure:4902: checking whether /usr/bin/h5cc understands -c and -o together > configure:4925: /usr/bin/h5cc -c conftest.c -o confte
Bug#1066473: multitail: FTBFS: mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean ‘waddnstr’? [-Werror=implicit-function-declaration]
tag 1066473: + pending
thanks
Hi,
Am 13.03.24 um 12:53 schrieb Lucas Nussbaum:
During a rebuild of all packages in sid, your package failed to build
on amd64.
Interesting. I almost wanted to tag it unreproducible since it didn't
happen in my already-existing chroot... But it definitely does fail in
cowbuilder build <.dsc> :/
Nope. Just works here. Yes, with dpkg-dev 1.22.6. In a manual chroot I
have here and upgraded and in a cowbuilder build multitail_6.5.0-1.dsc
Relevant part (hopefully):
cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wno-unused-parameter -funsigned-char -O3
-DLinux -DVERSION=\"6.5.0\" -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -DCONFIG_FILE=\"/etc/multitail.conf\" -MMD -MP -DUTF8_SUPPORT -c -o mt.o
mt.c
mt.c: In function ‘do_color_print’:
mt.c:707:25: error: implicit declaration of function ‘waddnwstr’; did you mean
‘waddnstr’? [-Werror=implicit-function-declaration]
707 | waddnwstr(win -> win, , 1);
| ^
| waddnstr
mt.c: In function ‘update_statusline’:
mt.c:1467:126: warning: format ‘%lld’ expects argument of type ‘long long int’,
but argument 5 has type ‘off64_t’ {aka ‘long int’} [-Wformat=]
1467 | mvwprintw(status -> win, 0,
win_width - (strlen(timestamp) + cur_len), "%10lld - %s", fsize, timestamp);
|
~^~
|
||
|
|off64_t {aka
long int}
|
long long int
|
%10ld
cc1: some warnings being treated as errors
make[2]: *** [: mt.o] Error 1
Actually upstream has
#if defined(UTF8_SUPPORT) && defined(NCURSES_WIDECHAR)
// FIXME warning: implicit declaration of function �~@~Xwaddnwstr�~@~Y
is invalid in C99 [-Wimplicit-function-declaration]
// see /usr/include/ncurses.h
waddnwstr(win -> win, , 1);
#else
wprintw(win -> win, "%c", wcur);
#endif
so is aware...
Actually (thanks to discussion on IRC) it seems that
CPPFLAGS:=$(shell pkg-config --cflags ncurses)
NCURSES_LIB:=$(shell pkg-config --libs ncurses)
is empty even though it shouldn't be. So fix is to add that missing
build-dep.
Regards,
Rene
Processed: limit source to bc, tagging 1043703, tagging 1065375
Processing commands for cont...@bugs.debian.org: > limit source bc Limiting to bugs with field 'source' containing at least one of 'bc' Limit currently set to 'source':'bc' > tags 1043703 + pending Bug #1043703 [src:bc] bc: Fails to build source after successful build Added tag(s) pending. > tags 1065375 + pending Bug #1065375 [src:bc] bc fails to build with abi=time64 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043703 1065375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration
On 2024-03-13 Thorsten Glaser wrote: > clone 1066137 -1 > reassign -1 gnupg1 1.4.23-1.1 > retitle -1 gnupg1: fails to build gpgkeys_ldap, probably due to > -Werror=implicit-function-declaration > thanks > Dixi quod… > >This matches the following failure mode at the end of the build: > Same for gnupg1 according to the buildd page: > https://buildd.debian.org/status/package.php?p=gnupg1 Hello Thorsten, I have upload a fix for 2.2, probably will not be able to spend any time on 1.x or 2.4 before the weekend. > >Trying to binNMU gnupg2 to make it installable during t64 transition, > Please do also reduce the B-D as Helmut noted in #980768; specifically, > dropping ghostscript, imagemagick, libcurl4-gnutls-dev and transfig > from src:gnupg2 produces identical binary packages according to his > analysis. Perhaps some of that applies to gnupg1 as well. This will > help tremendously. It is fixed in 2.4 and I am very reluctant to backport major packaging updates to 2.2 since I think we will need to ship some kind of 2.4 in trixie. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1066744: marked as done (gnupg2: FTBFS: dh_install: error: missing files, aborting)
Your message dated Wed, 13 Mar 2024 18:06:43 + with message-id and subject line Bug#1066137: fixed in gnupg2 2.2.40-2 has caused the Debian Bug report #1066137, regarding gnupg2: FTBFS: dh_install: error: missing files, aborting 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.) -- 1066137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnupg2 Version: 2.2.40-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/build' > make[4]: Nothing to be done for 'install-data-hook'. > make[4]: Leaving directory '/<>/build' > make[3]: Leaving directory '/<>/build' > make[2]: Leaving directory '/<>/build' > make[1]: Leaving directory '/<>/build' >dh_install -O--builddirectory=build > dh_install: warning: Cannot find (any matches for) > "debian/tmp/usr/lib/gnupg/dirmngr_ldap" (tried in ., debian/tmp) > > dh_install: warning: dirmngr missing files: > debian/tmp/usr/lib/gnupg/dirmngr_ldap > dh_install: error: missing files, aborting > make: *** [debian/rules:35: binary] Error 255 The full build log is available from: http://qa-logs.debian.net/2024/03/13/gnupg2_2.2.40-1.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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: gnupg2 Source-Version: 2.2.40-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnupg2, 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 Metzler (supplier of updated gnupg2 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 18:27:10 +0100 Source: gnupg2 Architecture: source Version: 2.2.40-2 Distribution: unstable Urgency: medium Maintainer: Debian GnuPG Maintainers Changed-By: Andreas Metzler Closes: 1066137 Changes: gnupg2 (2.2.40-2) unstable; urgency=medium . * Team upload. * ldap-implicit.diff: Fix FTBFS with -Werror=implicit-function-declaration due to using ldap deprecated interfaces in autoconf tests. Closes: #1066137 Checksums-Sha1: 293c5e7b55eb392565a736c75ea6338e7dbb5610 3824 gnupg2_2.2.40-2.dsc 0fe00340fb7401f9141feee20cf59c440acff79f 62656 gnupg2_2.2.40-2.debian.tar.xz Checksums-Sha256: 3440b1de877c780420063f8056814a8d7cc58ac610db7f49536bdb72f1a91946 3824 gnupg2_2.2.40-2.dsc e4c57f6336c0226107484eb7615031d2b08e3b92e1f4760e0b7caff00f69aaad 62656 gnupg2_2.2.40-2.debian.tar.xz Files: a8e61e24fd546b7d50309a6fb77d2c82 3824 utils optional gnupg2_2.2.40-2.dsc fa8b44a9720ba816a6737fbef0fa7647 62656 utils optional gnupg2_2.2.40-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmXx5bsACgkQpU8BhUOC FIR4ww//S/WXEL/3PP83hOPdpdX3z0YNdWk/dSPCAYQdjz3s6BIJZE3m/BoWJoni eYqwUaC7QsErI8Uput4O8OjTzw/bQYIfR2z6ap04+giAApWRpB0azSltXjhMj3Xo cCGiFb7dw9/dfVHhkQk+s+lXh5iB3j/0cs9iYCRUWyZXpoMDZBb5akdPmbbQyGGS /xRW1QvRgRkAXIShkMkLynAqPjaJB1+szRMDHSNyPFqbKu1XRjeSBqPG+9Q9Hw0z 7kLJ0/b64T5aSEn2yDSMtP75OQ6LPduhVzPDhYHDFGWdpJLpuVGKvVRbpTYl7MDL xZk2CGvASFqvXuQtFTGBvzAIkOChsAUfEWSqolTCalqYh/Umew4rM1Q5WNXGDkKz YCNPvLH3h1/0XtR+ady0+aFooERrEO5qBEuRa6sR4
Bug#1066137: marked as done (gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open)
Your message dated Wed, 13 Mar 2024 18:06:43 +
with message-id
and subject line Bug#1066137: fixed in gnupg2 2.2.40-2
has caused the Debian Bug report #1066137,
regarding gnupg2: -Werror=implicit-function-declaration failure testing for
ldap_open
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.)
--
1066137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg2
Version: 2.2.40-1.1
Severity: serious
Justification: ftbfs
X-Debbugs-Cc: t...@mirbsd.de
Trying to binNMU gnupg2 to make it installable during t64 transition,
I notice the following configury output:
[…]
checking for library containing dn_skipname... none required
checking whether the resolver is usable... yes
checking whether LDAP via "-lldap" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lwldap32" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking for ber_free in -llber... yes
configure: WARNING:
***
*** Building without LDAP support.
*** No CRL access or X.509 certificate search available.
***
checking for sendmail... no
[…]
This matches the following failure mode at the end of the build:
19:50⎜ I can't build gnugpg2:
19:50⎜dh_install -a -O--builddirectory=build
19:50⎜ dh_install: warning: Cannot find (any matches for)
⎜"debian/tmp/usr/lib/gnupg/dirmngr_ldap" (tried in ., debian/tmp)
19:50⎜ dh_install: warning: dirmngr missing files:
⎜debian/tmp/usr/lib/gnupg/dirmngr_ldap
19:50⎜ dh_install: error: missing files, aborting
The cause in config.log:
configure:11580: checking whether LDAP via "-lldap" is present and sane
configure:11600: gcc -o conftest -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/tmp/buildd/gnupg2-2.2.40=.
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now conftest.c -lldap
>&5
conftest.c: In function 'main':
conftest.c:96:1: error: implicit declaration of function 'ldap_open'; did you
mean 'ldap_turn'? [-Werror=implicit-function-declaration]
96 | ldap_open("foobar",1234);
| ^
| ldap_turn
cc1: some warnings being treated as errors
configure:11600: $? = 1
configure: failed program was:
[…]
| /* end confdefs.h. */
|
| #ifdef _WIN32
| #include
| #include
| #else
| #include
| #endif
|
| int
| main (void)
| {
| ldap_open("foobar",1234);
| ;
| return 0;
| }
configure:11608: result: no
Prototypes are now mandatory, both for C23 and because the t64 transition
can only work if prototypes are properly used.
bye,
//mirabilos
--- End Message ---
--- Begin Message ---
Source: gnupg2
Source-Version: 2.2.40-2
Done: Andreas Metzler
We believe that the bug you reported is fixed in the latest version of
gnupg2, 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 Metzler (supplier of updated gnupg2 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 18:27:10 +0100
Source: gnupg2
Architecture: source
Version: 2.2.40-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Andreas Metzler
Closes: 1066137
Changes:
gnupg2 (2.2.40-2) unstable; urgency=medium
.
* Team upload.
* ldap-implicit.diff: Fix FTBFS with -Werror=implicit-function-declaration
due to using ldap deprecated interfaces in autoconf tests.
Closes: #1066137
Checksums-Sha1:
293c5e7b55eb392565a736c75ea6338e7dbb5610 3824 gnupg2_2.2.40-2.dsc
0fe00340fb7401f9141feee20cf59c440acff79f 62656 gnupg2_2.2.40-2.debian.tar.xz
Processed: R packages failing to build with missing -ltirpc are actually an issue in r-base
Processing control commands: > reassign 1066403 r-base-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066452 r-base-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066455 r-base-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066456 r-base-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066456 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package > forcemerge 1066403 1066452 1066455 1066456 Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Merged 1066403 1066452 1066455 1066456 > affects 1066403 rjava Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 rapache Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 littler Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 rpy2 Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455
Processed: R packages failing to build with missing -ltirpc are actually an issue in r-base
Processing control commands: > reassign 1066403 r-base-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066452 r-base-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066455 r-base-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066456 r-base-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066456 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package > forcemerge 1066403 1066452 1066455 1066456 Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Merged 1066403 1066452 1066455 1066456 > affects 1066403 rjava Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 rapache Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 littler Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 rpy2 Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455
Processed: R packages failing to build with missing -ltirpc are actually an issue in r-base
Processing control commands: > reassign 1066403 r-base-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066452 r-base-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066455 r-base-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066455 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066456 to the same package > reassign 1066456 r-base-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to reassign bug #1066456 to the same package Ignoring request to reassign bug #1066403 to the same package Ignoring request to reassign bug #1066452 to the same package Ignoring request to reassign bug #1066455 to the same package > forcemerge 1066403 1066452 1066455 1066456 Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Removed indication that 1066455 affects rpy2, rapache, rjava, and littler Added indication that 1066455 affects rjava,rapache,rpy2,littler Removed indication that 1066403 affects rpy2, rapache, littler, and rjava Added indication that 1066403 affects rjava,rapache,rpy2,littler Removed indication that 1066452 affects rpy2, rjava, littler, and rapache Added indication that 1066452 affects rjava,rapache,rpy2,littler Removed indication that 1066456 affects rapache, littler, rjava, and rpy2 Added indication that 1066456 affects rjava,rapache,rpy2,littler Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Merged 1066403 1066452 1066455 1066456 > affects 1066403 rjava Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 rapache Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Ignoring request to set affects of bug 1066403 to the same value previously set Ignoring request to set affects of bug 1066452 to the same value previously set Ignoring request to set affects of bug 1066455 to the same value previously set Ignoring request to set affects of bug 1066456 to the same value previously set > affects 1066403 littler Bug #1066403 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066452 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066455 [r-base-dev] r-base-dev: missing dependency on libtirpc-dev Bug #1066456
Processed: R packages failing to build with missing -ltirpc are actually an issue in r-base
Processing control commands: > reassign 1066403 r-base-dev Bug #1066403 [src:rjava] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug reassigned from package 'src:rjava' to 'r-base-dev'. No longer marked as found in versions rjava/1.0-11-1. Ignoring request to alter fixed versions of bug #1066403 to the same values previously set > reassign 1066452 r-base-dev Bug #1066452 [src:rapache] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug reassigned from package 'src:rapache' to 'r-base-dev'. No longer marked as found in versions rapache/1.2.10-1. Ignoring request to alter fixed versions of bug #1066452 to the same values previously set > reassign 1066455 r-base-dev Bug #1066455 [src:littler] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug reassigned from package 'src:littler' to 'r-base-dev'. No longer marked as found in versions littler/0.3.19-1. Ignoring request to alter fixed versions of bug #1066455 to the same values previously set > reassign 1066456 r-base-dev Bug #1066456 [src:rpy2] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug reassigned from package 'src:rpy2' to 'r-base-dev'. No longer marked as found in versions rpy2/3.5.15-1. Ignoring request to alter fixed versions of bug #1066456 to the same values previously set > forcemerge 1066403 1066452 1066455 1066456 Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Merged 1066403 1066452 1066455 1066456 > affects 1066403 rjava Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Added indication that 1066403 affects rjava Added indication that 1066452 affects rjava Added indication that 1066455 affects rjava Added indication that 1066456 affects rjava > affects 1066403 rapache Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Added indication that 1066403 affects rapache Added indication that 1066452 affects rapache Added indication that 1066455 affects rapache Added indication that 1066456 affects rapache > affects 1066403 littler Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Added indication that 1066403 affects littler Added indication that 1066452 affects littler Added indication that 1066455 affects littler Added indication that 1066456 affects littler > affects 1066403 rpy2 Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Added indication that 1066403 affects rpy2 Added indication that 1066452 affects rpy2 Added indication that 1066455 affects rpy2 Added indication that 1066456 affects rpy2 > retitle 1066403 r-base-dev: missing dependency on libtirpc-dev Bug #1066403 [r-base-dev] rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066452 [r-base-dev] rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066455 [r-base-dev] littler: FTBFS: ld: cannot find -ltirpc: No such file or directory Bug #1066456 [r-base-dev] rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Changed Bug title to 'r-base-dev: missing dependency on libtirpc-dev' from 'rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory'. Changed Bug title to 'r-base-dev: missing dependency on libtirpc-dev' from 'rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory'. Changed Bug title to 'r-base-dev: missing dependency on libtirpc-dev' from 'littler: FTBFS: ld: cannot find -ltirpc: No such file or directory'. Changed Bug title to 'r-base-dev:
Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base
control: reassign 1066403 r-base-dev control: reassign 1066452 r-base-dev control: reassign 1066455 r-base-dev control: reassign 1066456 r-base-dev control: forcemerge 1066403 1066452 1066455 1066456 control: affects 1066403 rjava control: affects 1066403 rapache control: affects 1066403 littler control: affects 1066403 rpy2 control: retitle 1066403 r-base-dev: missing dependency on libtirpc-dev Hi Dirk, There are 4 r-base packages failing to build in the latest archive rebuild: #1066403 rjava: FTBFS: ld: cannot find -ltirpc: No such file or directory #1066452 rapache: FTBFS: ld: cannot find -ltirpc: No such file or directory #1066455 littler: FTBFS: ld: cannot find -ltirpc: No such file or directory #1066456 rpy2: FTBFS: ld: cannot find -ltirpc: No such file or directory Investigating, it appears that the issue is actually at the r-base level. They try to link with -ltirpc because R tell them to do so: $ R CMD config --ldflags -Wl,--export-dynamic -fopenmp -Wl,-z,relro -L/usr/lib/R/lib -lR -lpcre2-8 -llzma -lbz2 -lz -ltirpc -lrt -ldl -lm -licuuc -licui18n Therefore it seems that r-base-dev is missing a dependency on libtirpc-dev. Sorry for not having noticed that when filling #1065216. Regards Aurelien
Bug#1066469: tack: FTBFS: configure: error: No curses header-files found
On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote: > Source: tack > Version: 1.08-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): >> configure: WARNING: pkg-config is not installed >> checking for specific curses-directory... no >> checking for specified curses library type... curses >> checking for extra include directories... no >> checking if we have identified curses headers... none >> configure: error: No curses header-files found >> tail -v -n \+0 config.log This reminds me that I really should update the tack package to a newer version. The error is still present in tack 1.09 (the latest stable release), but fixed as of tack 1.09-20230201 (the latest development snapshot). @Thomas: since tack 1.09 is more than four years old and there has been no new snapshot for over a year, how about releasing tack 1.10? This bug will likely hit other distros as they upgrade to GCC 14. Cheers, Sven
Processed: packages using dcmtk failing to build with missing -lnsl are actually an issue in dcmtk
Processing control commands: > reassign 1066422 libdcmtk-dev Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Ignoring request to reassign bug #1066422 to the same package Ignoring request to reassign bug #1066423 to the same package > reassign 1066423 libdcmtk-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Ignoring request to reassign bug #1066423 to the same package Ignoring request to reassign bug #1066422 to the same package > forcemerge 1066422 1066423 Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Merged 1066422 1066423 > retitle 1066422 libdcmtk-dev: missing dependency on libnsl-dev Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Ignoring request to change the title of bug#1066422 to the same title Ignoring request to change the title of bug#1066423 to the same title > affects 1066422 plastimatch Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Ignoring request to set affects of bug 1066422 to the same value previously set Ignoring request to set affects of bug 1066423 to the same value previously set > affects 1066423 sight Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Ignoring request to set affects of bug 1066423 to the same value previously set Ignoring request to set affects of bug 1066422 to the same value previously set -- 1066422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066422 1066423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: packages using dcmtk failing to build with missing -lnsl are actually an issue in dcmtk
Processing control commands: > reassign 1066422 libdcmtk-dev Bug #1066422 [src:plastimatch] plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory Bug reassigned from package 'src:plastimatch' to 'libdcmtk-dev'. No longer marked as found in versions plastimatch/1.9.4+dfsg.1-2. Ignoring request to alter fixed versions of bug #1066422 to the same values previously set > reassign 1066423 libdcmtk-dev Bug #1066423 [src:sight] sight: FTBFS: ld.gold: error: cannot find -lnsl Bug reassigned from package 'src:sight' to 'libdcmtk-dev'. No longer marked as found in versions sight/23.1.0-2. Ignoring request to alter fixed versions of bug #1066423 to the same values previously set > forcemerge 1066422 1066423 Bug #1066422 [libdcmtk-dev] plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory Bug #1066423 [libdcmtk-dev] sight: FTBFS: ld.gold: error: cannot find -lnsl Merged 1066422 1066423 > retitle 1066422 libdcmtk-dev: missing dependency on libnsl-dev Bug #1066422 [libdcmtk-dev] plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory Bug #1066423 [libdcmtk-dev] sight: FTBFS: ld.gold: error: cannot find -lnsl Changed Bug title to 'libdcmtk-dev: missing dependency on libnsl-dev' from 'plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory'. Changed Bug title to 'libdcmtk-dev: missing dependency on libnsl-dev' from 'sight: FTBFS: ld.gold: error: cannot find -lnsl'. > affects 1066422 plastimatch Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Added indication that 1066422 affects plastimatch Added indication that 1066423 affects plastimatch > affects 1066423 sight Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev Added indication that 1066423 affects sight Added indication that 1066422 affects sight -- 1066422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066422 1066423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066422: packages using dcmtk failing to build with missing -lnsl are actually an issue in dcmtk
control: reassign 1066422 libdcmtk-dev control: reassign 1066423 libdcmtk-dev control: forcemerge 1066422 1066423 control: retitle 1066422 libdcmtk-dev: missing dependency on libnsl-dev control: affects 1066422 plastimatch control: affects 1066423 sight Hi, There are 2 packages using dcmtk failing to build in the latest archive rebuild: #1066422 plastimatch: FTBFS: ld: cannot find -lnsl: No such file or directory #1066423 sight: FTBFS: ld.gold: error: cannot find -lnsl Investigating, it appears that the issue is actually at the dcmtk package level. They try to link with -lnsl because dcmtk says so: $ grep nsl /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake INTERFACE_LINK_LIBRARIES "DCMTK::config;nsl;pthread;rt" dcmtk actually does not depends on libnsl-dev, but gets this dependency through the libwrap0-dev package. Therefore it seems that libdcmtk-dev is missing a dependency on libnsl-dev. In addition it might be good to add it as a build-dependency of the dcmtk package, to ensure it continues building even if libwrap0-dev drops it at some point. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1066336: marked as done (silo-llnl: FTBFS: silo_hdf5.c:2173:5: error: implicit declaration of function ‘zfp_init_zfp’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 17:55:06 + with message-id and subject line Bug#1066336: fixed in silo-llnl 4.11-4 has caused the Debian Bug report #1066336, regarding silo-llnl: FTBFS: silo_hdf5.c:2173:5: error: implicit declaration of function ‘zfp_init_zfp’ [-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.) -- 1066336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: silo-llnl Version: 4.11-3.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/sh ../../libtool --tag=CC --mode=compile mpicc -DHAVE_CONFIG_H -I. > -I../.. -I./../silo -I./../silo -I./../fpzip -DH5_HAVE_FILTER_ZFP > -DH5Z_ZFP_AS_LIB -DAS_SILO_BUILTIN -I./../zfp-0.5.5/include > -I/usr/include/hdf5/openmpi -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtGui > -I/usr/include/x86_64-linux-gnu/qt5/QtCore > -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/lib/openmpi/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 > -Wdeclaration-after-statement -c -o silo_hdf5.lo silo_hdf5.c > libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../.. -I./../silo -I./../silo > -I./../fpzip -DH5_HAVE_FILTER_ZFP -DH5Z_ZFP_AS_LIB -DAS_SILO_BUILTIN > -I./../zfp-0.5.5/include -I/usr/include/hdf5/openmpi > -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui > -I/usr/include/x86_64-linux-gnu/qt5/QtCore > -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/lib/openmpi/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 > -Wdeclaration-after-statement -c silo_hdf5.c -fPIC -DPIC -o .libs/silo_hdf5.o > silo_hdf5.c:61:2: warning: #warning DO WE NEED THIS HEADER FILE [-Wcpp] >61 | #warning DO WE NEED THIS HEADER FILE > | ^~~ > In file included from silo_hdf5.c:74: > silo_hdf5_private.h:110:2: warning: #warning REMOVE db_hdf5_CpListedObjects > [-Wcpp] > 110 | #warning REMOVE db_hdf5_CpListedObjects > | ^~~ > In file included from silo_hdf5_private.h:67: > silo_hdf5.c: In function ‘db_hdf5_get_obj_dsnames’: > silo_hdf5.c:1812:45: warning: passing argument 1 of ‘_db_safe_strdup’ makes > pointer from integer without a cast [-Wint-conversion] > 1812 | (*dsnames)[i] = strdup(m.MEMNAME[i]);\ > |~^~~ > | | > | char > ./../silo/silo_private.h:939:35: note: in definition of macro ‘strdup’ > 939 | #define strdup(s) _db_safe_strdup(s) > | ^ > silo_hdf5.c:1869:13: note: in expansion of macro ‘DB_OBJ_CASE’ > 1869 | DB_OBJ_CASE(DB_CURVE, DBcurve_mt, npts?1:1, yvarname) > | ^~~ > In file included from ./../silo/silo_private.h:79: > ./../silo/silo.h:2214:56: note: expected ‘const char *’ but argument is of > type ‘char’ > 2214 | SILO_API extern char * _db_safe_strdup(const char *); > |^~~~ > silo_hdf5.c: In function ‘db_hdf5_init’: > silo_hdf5.c:2173:5: error: implicit declaration of function ‘zfp_init_zfp’ > [-Werror=implicit-function-declaration] > 2173 | zfp_init_zfp(); > | ^~~~ > silo_hdf5.c: In function ‘db_hdf5_InitCallbacks’: > silo_hdf5.c:2799:2: warning: #warning GET RID OF CPLISTEDOBJECTS [-Wcpp] >
Bug#1066716: marked as done (libtfbs-perl: FTBFS: ./lib/pwm_searchPFF.c:55:7: error: implicit declaration of function ‘announce’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 17:50:44 +
with message-id
and subject line Bug#1066716: fixed in libtfbs-perl 0.7.1+ds-3
has caused the Debian Bug report #1066716,
regarding libtfbs-perl: FTBFS: ./lib/pwm_searchPFF.c:55:7: error: implicit
declaration of function ‘announce’ [-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.)
--
1066716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtfbs-perl
Version: 0.7.1+ds-2
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):
> x86_64-linux-gnu-gcc -c -I. -I./lib -D_REENTRANT -D_GNU_SOURCE -DDEBIAN
> -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.2\" -DXS_VERSION=\"0.2\"
> -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.38/CORE" pwmsearch.c
> In file included from pwmsearch.xs:4:
> ./lib/pwm_searchPFF.c: In function ‘do_search’:
> ./lib/pwm_searchPFF.c:55:7: error: implicit declaration of function
> ‘announce’ [-Werror=implicit-function-declaration]
>55 | announce("+++\nEntering main.\n+++\n");
> | ^~~~
> ./lib/pwm_searchPFF.c:74:9: error: implicit declaration of function
> ‘get_matrix’ [-Werror=implicit-function-declaration]
>74 |if ( get_matrix(,pwm) )
> | ^~
> ./lib/pwm_searchPFF.c:90:14: error: implicit declaration of function
> ‘loop_on_seqs’ [-Werror=implicit-function-declaration]
>90 |else if ( loop_on_seqs(,pwm,fp,outfp) )
> | ^~~~
> ./lib/pwm_searchPFF.c: At top level:
> ./lib/pwm_searchPFF.c:159:1: warning: return type defaults to ‘int’
> [-Wimplicit-int]
> 159 | best_pull(pargs,pbase,pstrand,pscore)
> | ^
> ./lib/pwm_searchPFF.c: In function ‘do_seq’:
> ./lib/pwm_searchPFF.c:229:18: error: implicit declaration of function
> ‘save_hit’; did you mean ‘save_hptr’? [-Werror=implicit-function-declaration]
> 229 | if ( save_hit(base,0,forward_score,hits,) )
> | ^~~~
> | save_hptr
> ./lib/pwm_searchPFF.c:239:20: error: implicit declaration of function
> ‘output’ [-Werror=implicit-function-declaration]
> 239 | else if ( output(pargs,seqid,base,seq,0,forward_score,outfp)
> )
> |^~
> ./lib/pwm_searchPFF.c: At top level:
> ./lib/pwm_searchPFF.c:526:1: warning: return type defaults to ‘int’
> [-Wimplicit-int]
> 526 | get_sequence(fp,seq_id,sequence)
> | ^~~~
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:324: pwmsearch.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libtfbs-perl_0.7.1+ds-2_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: libtfbs-perl
Source-Version: 0.7.1+ds-3
Done: Bas Couwenberg
We believe that the bug you reported is fixed in the latest version of
libtfbs-perl, which is due to be installed in the Debian FTP archive.
A summary of the ch
Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2
On Tue, Mar 12, 2024 at 5:16 PM Jeremy Bícha wrote: > > On Tue, Mar 12, 2024 at 4:13 PM Sebastian Andrzej Siewior > wrote: > > > > On 2024-03-12 09:26:32 [-0400], Jeremy Bícha wrote: > > > > Could someone check this, please? > > > > > > Did you try running autopkgtests on this version? The autopkgtests fail > > > for me. > > > > autopkgtests were the first thing that pointed me here and they passed. > > If you say they fail for you then I may have used the wrong xz version… > > I tried running the autopkgtests locally using a version of 1.50+nmu2 > that I built using your patch and the autopkgtests failed. > > None of the 3 test cases passed for me with that version or with 1.50+nmu1. The 3 test cases pass for me now with the uploaded 1.50+nmu2. Maybe my earlier test build used the old version of xz-utils. Thank you for your upload! Jeremy Bícha
Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote: > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’: > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function > > ‘vasprintf’; did you mean ‘vsprintf’? > > [-Werror=implicit-function-declaration] Looks like it's caused by the lack of -D_GNU_SOURCE, not sure who should set it. There is a very old debian/changelog entry about temporarily setting it from d/rules and fonttosfnt/write.c sets it but fonttosfnt/util.c doesn't and there is nothing related in the autotools stuff. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613 On 2024-02-17 18:53 +0100, Sven Joachim wrote: > Control: severity -1 grave > > On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote: > >> Package: libgl1-mesa-dri >> Version: 24.0.1-1 >> Severity: important >> >> Dear Maintainer, >> >> after the latest upgrade it's impossible for me to run a display manager >> or startx any window manager; after at most a few seconds / keypresses / >> mouse movements the screen freezes, completely unresponsive to anything >> other than the power button; the log below suggests a null pointer. >> >> Running "sleep 30; killall -u lorenzo" as root before startx returns me >> to a tty. >> >> Reverting to the previous version everything works. >> >> I'm running this on a debian derivative, devuan; afaik it shouldn't make >> a difference, as the package is unmodified from debian - I don't know >> how to verify that other than by installing debian in some partition, >> can one start some window manager from a debian chroot/whatever? >> >> If it's ok in debian or you need any more info please do let me know. > > I can reproduce that on my laptop which runs pure Debian, and at least > one other user seems to have the same problem. > >> VGA-compatible devices on PCI bus: >> -- >> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. >> [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 >> OEM] [1002:6611] > > I have the following graphics hardware: > > , > | 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, > | Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] [1002:985\ 0] (rev 40) > ` > > This is also using the radeonsi driver, and the symptoms and the > backtrace are the same as yours. > > Bumping severity to keep this mesa version out of testing, but I will > not be able to investigate the problem because I need the machine and > have already downgraded all packages from src:mesa. There does not seem > to be an upstream report yet. Looks like there is one now and it even has a patch which seems to have been applied in Archlinux and Ubuntu, but not committed upstream. :-( Cheers, Sven
Processed: Re: Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
Processing control commands: > forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613 Bug #1064123 [libgl1-mesa-dri] libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613'. -- 1064123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066716 marked as pending in libtfbs-perl
Processing control commands: > tag -1 pending Bug #1066716 [src:libtfbs-perl] libtfbs-perl: FTBFS: ./lib/pwm_searchPFF.c:55:7: error: implicit declaration of function ‘announce’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066716: marked as pending in libtfbs-perl
Control: tag -1 pending Hello, Bug #1066716 in libtfbs-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/libtfbs-perl/-/commit/c01f62e8932093818d86fde6fa0880ced0c4b4bd Add patch to fix FTBFS with GCC 14. (closes: #1066716) (this message was generated automatically) -- Greetings https://bugs.debian.org/1066716
Bug#1066272: bc: FTBFS: stack.c:40:5: error: implicit declaration of function ‘checkferror_output’ [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:35:55PM +0100, Lucas Nussbaum wrote: > > stack.c: In function ‘dc_binop’: > > stack.c:40:5: error: implicit declaration of function ‘checkferror_output’ > > [-Werror=implicit-function-declaration] > >40 | checkferror_output(stderr); \ > > | ^~ [etc.] This is most likely because debian/patches/05_notice_read_write_errors.diff adds calls of checkferror_output() to various files but doesn't add the relevant header (which seems to be "h/number.h"). -- WBR, wRAR signature.asc Description: PGP signature
Bug#1066296: xli: FTBFS: dither.c:77:36: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration]
Hello Lucas! Thanks! I will correct Nilson F. Silva De: Lucas Nussbaum Enviado: quarta-feira, 13 de março de 2024 08:46 Para: sub...@bugs.debian.org Assunto: Bug#1066296: xli: FTBFS: dither.c:77:36: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration] Source: xli Version: 1.17.0+20061110-8 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): > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 fill.c > dither.c: In function ‘dither’: > dither.c:77:36: error: implicit declaration of function ‘strlen’ > [-Werror=implicit-function-declaration] >77 | image->title = (char *)lmalloc(strlen(cimage->title) + 12); > |^~ > dither.c:28:1: note: include ‘’ or provide a declaration of ‘strlen’ >27 | #include "xli.h" > +++ |+#include >28 | > dither.c:77:36: warning: incompatible implicit declaration of built-in > function ‘strlen’ [-Wbuiltin-declaration-mismatch] >77 | image->title = (char *)lmalloc(strlen(cimage->title) + 12); > |^~ > dither.c:77:36: note: include ‘’ or provide a declaration of > ‘strlen’ > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 g3.c > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 gif.c > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 > halftone.c > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 > imagetypes.c > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 img.c > gif.c: In function ‘gifin_open_file’: > gif.c:193:7: error: implicit declaration of function ‘strcmp’ > [-Werror=implicit-function-declaration] > 193 | if (strcmp((char *) buf, GIF_SIG) == 0) > | ^~ > gif.c:21:1: note: include ‘’ or provide a declaration of ‘strcmp’ >20 | #include "imagetypes.h" > +++ |+#include >21 | > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O > -DSYSPATHFILE=\"/usr/lib/X11/Xli\" -Wdate-time -D_FORTIFY_SOURCE=2 mac.c > cc1: some warnings being treated as errors > imagetypes.c: In function ‘loadImage’: > imagetypes.c:66:39: error: implicit declaration of function ‘strlen’ > [-Werror=implicit-function-declaration] >66 | image_ops->fullname = lmalloc(strlen(fullname) + 1); > | ^~ > imagetypes.c:15:1: note: include ‘’ or provide a declaration of > ‘strlen’ >14 | #include > +++ |+#include >15 | > imagetypes.c:66:39: warning: incompatible implicit declaration of built-in > function ‘strlen’ [-Wbuiltin-declaration-mismatch] >66 | image_ops->fullname = lmalloc(strlen(fullname) + 1); > | ^~ > imagetypes.c:66:39: note: include ‘’ or provide a declaration of > ‘strlen’ > imagetypes.c:67:9: error: implicit declaration of
Processed: aalib: diff for NMU version 1.4p5-51.1
Processing control commands: > tags 1066351 + patch Bug #1066351 [src:aalib] aalib: FTBFS: aainfo.c:12:9: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066351 + pending Bug #1066351 [src:aalib] aalib: FTBFS: aainfo.c:12:9: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066351: aalib: diff for NMU version 1.4p5-51.1
Control: tags 1066351 + patch
Control: tags 1066351 + pending
Dear maintainer,
I've prepared an NMU for aalib (versioned as 1.4p5-51.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.
Regards.
--
WBR, wRAR
diff -Nru aalib-1.4p5/debian/changelog aalib-1.4p5/debian/changelog
--- aalib-1.4p5/debian/changelog 2024-01-25 20:07:26.0 +0500
+++ aalib-1.4p5/debian/changelog 2024-03-13 22:25:58.0 +0500
@@ -1,3 +1,10 @@
+aalib (1.4p5-51.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066351).
+
+ -- Andrey Rakhmatullin Wed, 13 Mar 2024 22:25:58 +0500
+
aalib (1.4p5-51) unstable; urgency=medium
* Accept MR: Fix Netscape typo
diff -Nru aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch
--- aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500
+++ aalib-1.4p5/debian/patches/fix-implicit-function-declaration.patch 2024-03-13 22:23:43.0 +0500
@@ -0,0 +1,109 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin
+Bug-Debian: https://bugs.debian.org/1066351
+Last-Update: 2024-03-13
+
+Index: aalib-1.4p5/src/aainfo.c
+===
+--- aalib-1.4p5.orig/src/aainfo.c
aalib-1.4p5/src/aainfo.c
+@@ -1,3 +1,4 @@
++#include
+
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aalinuxkbd.c
+===
+--- aalib-1.4p5.orig/src/aalinuxkbd.c
aalib-1.4p5/src/aalinuxkbd.c
+@@ -22,6 +22,7 @@
+ #include /* for VT stuff - nah, really? :) */
+ #include
+ #include
++#include
+ #ifdef GPM_MOUSEDRIVER
+ #include
+ #endif
+Index: aalib-1.4p5/src/aaxkbd.c
+===
+--- aalib-1.4p5.orig/src/aaxkbd.c
aalib-1.4p5/src/aaxkbd.c
+@@ -7,6 +7,7 @@
+ #include
+ #include
+ #include
++#include
+ #include "aalib.h"
+ #include "aaint.h"
+ #include "aaxint.h"
+Index: aalib-1.4p5/src/aalib.c
+===
+--- aalib-1.4p5.orig/src/aalib.c
aalib-1.4p5/src/aalib.c
+@@ -1,6 +1,7 @@
+ #include
+ #include
+ #include
++#include
+ #include "aalib.h"
+ #include "aaint.h"
+
+Index: aalib-1.4p5/src/aaregist.c
+===
+--- aalib-1.4p5.orig/src/aaregist.c
aalib-1.4p5/src/aaregist.c
+@@ -1,4 +1,5 @@
+ #include
++#include
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aakbdreg.c
+===
+--- aalib-1.4p5.orig/src/aakbdreg.c
aalib-1.4p5/src/aakbdreg.c
+@@ -1,4 +1,5 @@
+ #include
++#include
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aamoureg.c
+===
+--- aalib-1.4p5.orig/src/aamoureg.c
aalib-1.4p5/src/aamoureg.c
+@@ -1,4 +1,5 @@
+ #include
++#include
+ #include "config.h"
+ #include "aalib.h"
+ #include "aaint.h"
+Index: aalib-1.4p5/src/aatest.c
+===
+--- aalib-1.4p5.orig/src/aatest.c
aalib-1.4p5/src/aatest.c
+@@ -1,3 +1,5 @@
++#include
++#include
+ #include "aalib.h"
+ int main(int argc, char **argv)
+ {
+Index: aalib-1.4p5/src/aafire.c
+===
+--- aalib-1.4p5.orig/src/aafire.c
aalib-1.4p5/src/aafire.c
+@@ -1,4 +1,5 @@
+ #include
++#include
+ #include "aalib.h"
+
+ #define XSIZ aa_imgwidth(context)
+Index: aalib-1.4p5/src/aasavefont.c
+===
+--- aalib-1.4p5.orig/src/aasavefont.c
aalib-1.4p5/src/aasavefont.c
+@@ -1,3 +1,4 @@
++#include
+ #include "aalib.h"
+ int main(int argc, char **argv)
+ {
diff -Nru aalib-1.4p5/debian/patches/series aalib-1.4p5/debian/patches/series
--- aalib-1.4p5/debian/patches/series 2024-01-25 20:07:26.0 +0500
+++ aalib-1.4p5/debian/patches/series 2024-03-13 22:10:58.0 +0500
@@ -14,3 +14,4 @@
fix-wording
fix-netscape-typo
fix-ftbfs-incomplete-typedef
+fix-implicit-function-declaration.patch
signature.asc
Description: PGP signature
Processed: Re: Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open
Processing control commands: > forcemerge 1066137 1066744 Bug #1066137 [src:gnupg2] gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open Bug #1066744 [src:gnupg2] gnupg2: FTBFS: dh_install: error: missing files, aborting Added tag(s) experimental. Bug #1066137 [src:gnupg2] gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open Added tag(s) ftbfs. Merged 1066137 1066744 > found 1066137 2.4.3-2 Bug #1066137 [src:gnupg2] gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open Bug #1066744 [src:gnupg2] gnupg2: FTBFS: dh_install: error: missing files, aborting Marked as found in versions gnupg2/2.4.3-2. Marked as found in versions gnupg2/2.4.3-2. -- 1066137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066137 1066744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open
Control: forcemerge 1066137 1066744 Control: found 1066137 2.4.3-2 On 2024-03-12 Thorsten Glaser wrote: > Source: gnupg2 > Version: 2.2.40-1.1 > Severity: serious > Justification: ftbfs > X-Debbugs-Cc: t...@mirbsd.de > Trying to binNMU gnupg2 to make it installable during t64 transition, > I notice the following configury output: > […] > checking for library containing dn_skipname... none required > checking whether the resolver is usable... yes > checking whether LDAP via "-lldap" is present and sane... no [...] I am going to take a look at this. I am also marking this as applying to experimental, too. I have not done a test-build yet but ldap.m4 looks similar. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: Re: Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-fu
Processing control commands: > forwarded -1 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569 Bug #1066382 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declaration] Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569'. -- 1066382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat
Control: forwarded -1
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569
On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:
> Source: xserver-xorg-video-nouveau
> Version: 1:1.0.17-2
> 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../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2
>> -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1
>> -I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/libdrm
>> -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2
>> -Werror=implicit-function-declaration
>> -ffile-prefix-map=/<>=. -fstack-protector-strong
>> -fstack-clash-protection -Wformat -Werror=format-security
>> -fcf-protection -Wall -minline-all-stringops -I/usr/include/xorg
>> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri
>> -I/usr/include/libdrm -c -o nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c
>> ../../src/nv_driver.c: In function ‘NVScreenInit’:
>> ../../src/nv_driver.c:1451:23: error: implicit declaration of
>> function ‘wfbScreenInit’; did you mean ‘fbScreenInit’?
>> [-Werror=implicit-function-declaration]
>> 1451 | ret = wfbScreenInit(pScreen, FBStart,
>> pScrn->virtualX,
>> | ^
>> | fbScreenInit
This has already been reported upstream, unfortunately without a
followup so far. Adding -DFB_ACCESS_WRAPPER to CPPFLAGS lets the build
succeed, but I have not tested the resulting binary package yet. See
commit d7ba24fb6e4f ("wfb: Fix missing init function decls behind
FB_ACCESS_WRAPPER") which noticed and fixed the missing function
declaration, but got reverted in commit ca13913aaf7e.
Cheers,
Sven
Bug#1066214: cyrus-sasl2: FTBFS: gssapi.c:1600:9: error: implicit declaration of function ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:36:37PM +0100, Lucas Nussbaum wrote: > > gssapi.c:1600:9: error: implicit declaration of function > > ‘gsskrb5_register_acceptor_identity’ [-Werror=implicit-function-declaration] > > 1600 | gsskrb5_register_acceptor_identity(keytab_path); > > | ^~ The function should be declared in , in this case it's /usr/include/heimdal/gssapi/gssapi_krb5.h from heimdal-multidev, but build-heimdal/config.h defines HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY but doesn't define HAVE_GSSAPI_GSSAPI_KRB5_H, so is not included but the code is compiled. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1066494: marked as done (wmrack: FTBFS: wmrack.c:1295:29: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 16:59:23 + with message-id and subject line Bug#1066494: fixed in wmrack 1.4-7 has caused the Debian Bug report #1066494, regarding wmrack: FTBFS: wmrack.c:1295:29: error: implicit declaration of function ‘time’ [-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.) -- 1066494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmrack Version: 1.4-6 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 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o wmrack.o wmrack.c > make[2]: Leaving directory '/<>/XPM' > wmrack.c: In function ‘redrawDisplay’: > wmrack.c:1238:12: warning: type defaults to ‘int’ in declaration of ‘flash’ > [-Wimplicit-int] > 1238 | static flash = 0; > |^ > wmrack.c:1295:29: error: implicit declaration of function ‘time’ > [-Werror=implicit-function-declaration] > 1295 | time_t flash_time = time (NULL); > | ^~~~ > wmrack.c:39:1: note: ‘time’ is defined in header ‘’; did you forget > to ‘#include ’? >38 | #include "library.h" > +++ |+#include >39 | > echo "Done" > .depend > cc1: some warnings being treated as errors > make[1]: *** [: wmrack.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/wmrack_1.4-6_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: wmrack Source-Version: 1.4-7 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of wmrack, 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. Doug Torrance (supplier of updated wmrack 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 12:36:39 -0400 Source: wmrack Built-For-Profiles: noudeb Architecture: source Version: 1.4-7 Distribution: unstable Urgency: medium Maintainer: Debian Window Maker Team Changed-By: Doug Torrance Closes: 1066494 Changes: wmrack (1.4-7) unstable; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Repository, Repository-Browse. . [ Doug Torrance ] * debian/control - Update my email address in Uploaders (now a Debian Developer). - Bump Standards-Version to 4.6.2. * debian/copyright - Add myself to copyright holders for debian directory. * debian/patches/* - Update my email address in Author fields. * debian/patches/implicit_declaration.patch - New patch; fix implicit declaration error (Closes: #1066494). Checksums-Sha1: 1b2db6ac9165033caccf0e9d9d008739cb9
Bug#1066312: marked as done (wims: FTBFS: canvasdraw.c:3239:17: error: implicit declaration of function ‘strcasestr’; did you mean ‘strparstr’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 16:59:13 +
with message-id
and subject line Bug#1066312: fixed in wims 2:4.27b+dfsg1-2
has caused the Debian Bug report #1066312,
regarding wims: FTBFS: canvasdraw.c:3239:17: error: implicit declaration of
function ‘strcasestr’; did you mean ‘strparstr’?
[-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.)
--
1066312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wims
Version: 2:4.27a+dfsg1-3
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 -o canvasdraw.o -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -c canvasdraw.c
> canvasdraw.c: In function ‘main’:
> canvasdraw.c:3239:17: error: implicit declaration of function ‘strcasestr’;
> did you mean ‘strparstr’? [-Werror=implicit-function-declaration]
> 3239 | if( strcasestr(temp,"NOCONTROLS") ){
> | ^~
> | strparstr
> canvasdraw.c: In function ‘getMML’:
> canvasdraw.c:6341:3: warning: ignoring return value of ‘fgets’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 6341 | fgets(buffer, MAX_BUFFER, stream);
> | ^
> canvasdraw.c: In function ‘getSVGMOL’:
> canvasdraw.c:6383:5: warning: ignoring return value of ‘read’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 6383 | read(link[0],buffer, 1+sizeof(buffer));
> | ^~
> canvasdraw.c:6383:5: warning: ‘read’ writing 65538 bytes into a region of
> size 65537 overflows the destination [-Wstringop-overflow=]
> 6383 | read(link[0],buffer, 1+sizeof(buffer));
> | ^~
> canvasdraw.c:6367:8: note: destination object ‘buffer’ of size 65537
> 6367 | char buffer[MAX_BUFFER+1];
> |^~
> In file included from /usr/include/unistd.h:1214,
> from ../../Lib/../includes.h:27,
> from ../../Lib/libwims.h:21,
> from canvasdraw.h:2,
> from canvasdraw.c:12:
> /usr/include/x86_64-linux-gnu/bits/unistd.h:36:1: note: in a call to function
> ‘read’ declared with attribute ‘access (write_only, 2, 3)’
>36 | read (int __fd, void *__buf, size_t __nbytes)
> | ^~~~
> In file included from /usr/include/features.h:490,
> from /usr/include/assert.h:35,
> from canvasdraw.h:1:
> In function ‘read’,
> inlined from ‘getSVGMOL’ at canvasdraw.c:6383:5:
> /usr/include/x86_64-linux-gnu/bits/unistd.h:38:10: warning: call to
> ‘__read_chk_warn’ declared with attribute warning: read called with bigger
> length than size of the destination buffer [-Wattribute-warning]
>38 | return __glibc_fortify (read, __nbytes, sizeof (char),
> | ^~~
> cc1: some warnings being treated as errors
> make[5]: *** [Makefile:22: canvasdraw.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/wims_4.27a+dfsg1-3_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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 Mess
Bug#1066747: marked as done (rasterio: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Wed, 13 Mar 2024 16:56:13 +
with message-id
and subject line Bug#1066747: fixed in rasterio 1.3.9-4
has caused the Debian Bug report #1066747,
regarding rasterio: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 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 ow...@bugs.debian.org
immediately.)
--
1066747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rasterio
Version: 1.3.9-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test
> I: pybuild pybuild:308: cp -r /<>/tests
> /<>/.pybuild/cpython3_3.12_rasterio/build
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_rasterio/build; python3.12 -m pytest
> --ignore tests/test_env.py --ignore tests/test_io.py --ignore
> tests/test_merge.py --ignore tests/test_rio_blocks.py --ignore
> tests/test_rio_bounds.py --ignore tests/test_rio_calc.py --ignore
> tests/test_rio_clip.py --ignore tests/test_rio_convert.py --ignore
> tests/test_rio_edit_info.py --ignore tests/test_rio_gcp.py --ignore
> tests/test_rio_helpers.py --ignore tests/test_rio_info.py --ignore
> tests/test_rio_insp.py --ignore tests/test_rio_main.py --ignore
> tests/test_rio_mask.py --ignore tests/test_rio_merge.py --ignore
> tests/test_rio_options.py --ignore tests/test_rio_overview.py --ignore
> tests/test_rio_rasterize.py --ignore tests/test_rio_rm.py --ignore
> tests/test_rio_sample.py --ignore tests/test_rio_shapes.py --ignore
> tests/test_rio_stack.py --ignore tests/test_rio_warp.py --ignore
> tests/test_session.py --ignore tests/test_warp.py --ignore
> tests/test_warpedvrt.py
> Test data present.
> = test session starts
> ==
> platform linux -- Python 3.12.2, pytest-8.0.2, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_rasterio/build
> configfile: pyproject.toml
> plugins: hypothesis-6.98.15
> collected 1086 items / 1 skipped
>
> tests/test__env.py . [
> 1%]
> tests/test__version.py . [
> 2%]
> tests/test_band.py . [
> 2%]
> tests/test_band_masks.py ... [
> 3%]
> tests/test_blocks.py ... [
> 5%]
> tests/test_boundless_read.py .XX...X..XX.[
> 6%]
> tests/test_checksum.py ..[
> 6%]
> tests/test_cli_main.py ..[
> 7%]
> tests/test_colorinterp.py .xx... [
> 9%]
> tests/test_colormap.py ..[
> 9%]
> tests/test_complex_dtypes.py . [
> 9%]
> tests/test_coords.py .. [
> 10%]
> tests/test_creation_options.py . [
> 10%]
> tests/test_crs.py .. [
> 15%]
> .[
> 20%]
> tests/test_data_paths.py .. [
> 21%]
> tests/test_dataset.py . [
> 24%]
> tests/test_dataset_mask.py [
> 25%]
> tests/test_dataset_rw.py ... [
> 25%]
> tests/test_deprecated.py . [
> 25%]
> tests/test_descriptions.py [
> 26%]
> tests/test_driver_management.py [
> 26%]
> tests/test_driver_policy.py .. [
> 26%]
> tests/test_dtypes.py .. [
> 29%]
> tests/test_enums.py ...
Bug#1066707: marked as done (ifupdown-ng: FTBFS: libifupdown/interface.c:28:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 16:52:08 + with message-id and subject line Bug#1066707: fixed in ifupdown-ng 0.12.1-4 has caused the Debian Bug report #1066707, regarding ifupdown-ng: FTBFS: libifupdown/interface.c:28:9: 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.) -- 1066707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ifupdown-ng Version: 0.12.1-3 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): > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -Wextra -Werror -Wmissing-declarations -Wmissing-prototypes > -Wcast-align -Wpointer-arith -Wreturn-type -isystem /usr/include/bsd > -DLIBBSD_OVERLAY -Wdate-time -D_FORTIFY_SOURCE=2 -I. > -DINTERFACES_FILE=\"/etc/network/interfaces\" -DSTATE_FILE=\"/run/ifstate\" > -DCONFIG_FILE=\"/etc/network/ifupdown-ng.conf\" > -DPACKAGE_NAME=\"ifupdown-ng\" -DPACKAGE_VERSION=\"0.12.1\" > -DPACKAGE_BUGREPORT=\"https://github.com/ifupdown-ng/ifupdown-ng/issues/new\; > -DEXECUTOR_PATH=\"/usr/libexec/ifupdown-ng\" -DCONFIG_YAML -c -o > libifupdown/environment.o libifupdown/environment.c > libifupdown/interface.c: In function ‘lif_address_parse’: > libifupdown/interface.c:28:9: error: implicit declaration of function > ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] >28 | strlcpy(buf, presentation, sizeof buf); > | ^~~ > | strncpy > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -Wextra -Werror -Wmissing-declarations -Wmissing-prototypes > -Wcast-align -Wpointer-arith -Wreturn-type -isystem /usr/include/bsd > -DLIBBSD_OVERLAY -Wdate-time -D_FORTIFY_SOURCE=2 -I. > -DINTERFACES_FILE=\"/etc/network/interfaces\" -DSTATE_FILE=\"/run/ifstate\" > -DCONFIG_FILE=\"/etc/network/ifupdown-ng.conf\" > -DPACKAGE_NAME=\"ifupdown-ng\" -DPACKAGE_VERSION=\"0.12.1\" > -DPACKAGE_BUGREPORT=\"https://github.com/ifupdown-ng/ifupdown-ng/issues/new\; > -DEXECUTOR_PATH=\"/usr/libexec/ifupdown-ng\" -DCONFIG_YAML -c -o > libifupdown/execute.o libifupdown/execute.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -Wextra -Werror -Wmissing-declarations -Wmissing-prototypes > -Wcast-align -Wpointer-arith -Wreturn-type -isystem /usr/include/bsd > -DLIBBSD_OVERLAY -Wdate-time -D_FORTIFY_SOURCE=2 -I. > -DINTERFACES_FILE=\"/etc/network/interfaces\" -DSTATE_FILE=\"/run/ifstate\" > -DCONFIG_FILE=\"/etc/network/ifupdown-ng.conf\" > -DPACKAGE_NAME=\"ifupdown-ng\" -DPACKAGE_VERSION=\"0.12.1\" > -DPACKAGE_BUGREPORT=\"https://github.com/ifupdown-ng/ifupdown-ng/issues/new\; > -DEXECUTOR_PATH=\"/usr/libexec/ifupdown-ng\" -DCONFIG_YAML -c -o > libifupdown/lifecycle.o libifupdown/lifecycle.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -Wextra -Werror -Wmissing-declarations -Wmissing-prototypes > -Wcast-align -Wpointer-arith -Wreturn-type -isystem /usr/include/bsd > -DLIBBSD_OVERLAY -Wdate-time -D_FORTIFY_SOURCE=2 -I. > -DINTERFACES_FILE=\"/etc/network/interfaces\" -DSTATE_FILE=\"/run/ifstate\" > -DCONFIG_FILE=\"/etc/network/ifupdown-ng.con
Bug#1066476: marked as done (conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met)
Your message dated Wed, 13 Mar 2024 16:50:20 + with message-id and subject line Bug#1066476: fixed in conntrack-tools 1:1.4.8-2 has caused the Debian Bug report #1066476, regarding conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met 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.) -- 1066476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: conntrack-tools Version: 1:1.4.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for byacc... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for rpc/rpc_msg.h... no > checking for libtirpc... no > configure: error: Package requirements (libtirpc) were not met > > Package 'libtirpc', required by 'virtual:world', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS > and LIBTIRPC_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: conntrack-tools Source-Version: 1:1.4.8-2 Done: Jeremy Sowden We believe that the bug you reported is fixed in the latest version of conntrack-tools, 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. Jeremy Sowden (supplier of updated conntrack-tools 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 12:31:21 + Source: conntrack-tools Architecture: source Version: 1:1.4.8-2 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Jeremy Sowden Closes: 1066476 Changes: conntrack-tools (1:1.4.8-2) unstable; urgency=medium . * [bdf7032] d/control: add missing build-dep on libtirpc-dev (Closes: #1066476) Checksums-Sha1: 1ae4a03acc00516ad3f4711bbe23e9d8e9a70bec 2767 conntrack-tools_1.4.8-2.dsc a90d8f0a26b4db99c8b49df0cf96814a71fc0fec 13564 conntrack-tools_1.4.8-2.debian.tar.xz 9ea9c46bb00a6e662746632f087971e013d1a0f8 8419 conntrack-tools_1.4.8-2_amd64.buildinfo Checksums-Sha256: 66d8e1dc048e0562da0750bbc96e50b5387a897ae1c1eedfb57e6b36f2edf9e5 2767 conntrack-tools_1.4.8-2.dsc 6627325fd0ac090556bc1da73b08d47dc7de80d72a6bc6153d9feb7afc5f8b0b 13564 conntrack-tools_1.4.8-2.debian.tar.xz 7643a90ac0a4c92f561bc8b42b4439b23f59600344f9fc6be054c0b07446c815 8419 conntrack-tools_1.4.8-2_amd64.buildinfo Files: 2b5046665cda9123d8b34c7210c50579 2767 net optional conntrack-tools_1.4.8-2.dsc 4e08fe9b41736e18b046cb03d9fcc58d 13564 net optional conntrack-tools_1.4.8-2.debian.tar.xz 9b121a416ddfe95cedd7a020ee8e2ad7 8419 net optional conntrack-tools_1.4.8-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEbB20U2PvQDe9VtUXKYasCr3xBA0FAmXxyJYSHGF6YXplbEBk ZWJpYW4ub3JnAAoJECmGrAq98QQNts0P+wZ0zXFNpPOzsq85K1uTnyNmroetugF7
Bug#1066427: marked as done (atlas-ecmwf: FTBFS: Library.cc:63:10: fatal error: ectrans/transi.h: No such file or directory)
Your message dated Wed, 13 Mar 2024 16:50:46 + with message-id and subject line Bug#1066427: fixed in ectrans 1.3.0-2 has caused the Debian Bug report #1066427, regarding atlas-ecmwf: FTBFS: Library.cc:63:10: fatal error: ectrans/transi.h: No such file or directory 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.) -- 1066427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atlas-ecmwf Version: 0.36.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/debian/build/atlas_io/tests && /usr/bin/c++ > -I/<>/atlas_io/src -I/<>/debian/build/atlas_io/src > -I/usr/include/x86_64-linux-gnu/eckit -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -std=gnu++17 -fPIE -MD -MT > atlas_io/tests/CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o -MF > CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o.d -o > CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o -c > /<>/atlas_io/tests/test_io_record.cc > /<>/src/atlas/library/Library.cc:63:10: fatal error: > ectrans/transi.h: No such file or directory >63 | #include "ectrans/transi.h" > | ^~ > compilation terminated. > make[3]: *** [src/atlas/CMakeFiles/atlas_ecmwf.dir/build.make:93: > src/atlas/CMakeFiles/atlas_ecmwf.dir/library/Library.cc.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/atlas-ecmwf_0.36.0-2_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=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=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: ectrans Source-Version: 1.3.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of ectrans, 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. Alastair McKinstry (supplier of updated ectrans 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: Wed, 13 Mar 2024 16:08:43 + Source: ectrans Architecture: source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1066427 Changes: ectrans (1.3.0-2) unstable; urgency=medium . * Ship real header files; build shipped broken symlinks. Closes: #1066427 Checksums-Sha1: 07f1f0b3bd71689767732eb830743ad47e05880c 2321 ectrans_1.3.0-2.dsc 807b7db7ddfaab1b177fae742644913b6272432c 4504 ectrans_1.3.0-2.debian.tar.xz Checksums-Sha256: 1dcebf26ed258630fd68b26c64b776a3b8ffc6eaf21a15cf8c0b247a260a 2321 ectrans_1.3.0-2.dsc 5a681cf512817962280f2282d01883581216d54155de779655ed141a7ba38422 4504 ectrans_1.3.0-2.debian.tar.xz Files: 3cf26a056e060b64d40778eb7eaf8f48 2321 science optional ectrans_1.3.0-2.dsc c3e1a602c201ada5b153c35a4a7edb4b 4504 science optional ectrans_1.3.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmXx1WsACgkQy+a7Tl2a 06VGyhAApARHww9ue9BOLOQQ3GG5NcGeZXNlNGPvjB8D1gR0/pgKi51aYLP5K9f6 JLH3lV7/0yfcRGZs9t1lHG+P
Bug#1066233: libmpeg3: FTBFS: audio/synthesizers.c:36:9: error: implicit declaration of function ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:41:13PM +0100, Lucas Nussbaum wrote: > > audio/synthesizers.c: In function ‘mpeg3audio_synth_stereo’: > > audio/synthesizers.c:36:9: error: implicit declaration of function > > ‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’? > > [-Werror=implicit-function-declaration] > >36 | mpeg3audio_dct64(buf[1] + ((audio->bo + 1) & 0xf), buf[0] + > > audio->bo, bandPtr); > > | ^~~~ > > | mpeg3audio_dopcm mpeg3audio_dct64() is defined in audio/dct.c and there is no header with its prototype. -- WBR, wRAR signature.asc Description: PGP signature
Processed: forcibly merging 1066233 1065781
Processing commands for cont...@bugs.debian.org:
> forcemerge 1066233 1065781
Bug #1066233 [src:libmpeg3] libmpeg3: FTBFS: audio/synthesizers.c:36:9: error:
implicit declaration of function ‘mpeg3audio_dct64’; did you mean
‘mpeg3audio_dopcm’? [-Werror=implicit-function-declaration]
Bug #1065781 [src:libmpeg3] libmpeg3: FTBFS on arm{el,hf}:
audio/synthesizers.c:36:9: error: implicit declaration of function
‘mpeg3audio_dct64’; did you mean ‘mpeg3audio_dopcm’?
[-Werror=implicit-function-declaration]
Added tag(s) trixie and sid.
Merged 1065781 1066233
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065781
1066233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
