Bug#1067830: gri: diff for NMU version 2.12.27-1.2
Control: tags 1067830 + patch Dear maintainer, I've prepared an NMU for gri (versioned as 2.12.27-1.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru gri-2.12.27/debian/changelog gri-2.12.27/debian/changelog --- gri-2.12.27/debian/changelog 2022-08-25 18:33:47.0 +0200 +++ gri-2.12.27/debian/changelog 2024-04-11 23:23:28.0 +0200 @@ -1,3 +1,11 @@ +gri (2.12.27-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: Apply upstream patch to fix build with 64 bit time_t on +armel and armhf. (Closes: #1067830) + + -- Sebastian Ramacher Thu, 11 Apr 2024 23:23:28 +0200 + gri (2.12.27-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gri-2.12.27/debian/patches/fix-build-with-t64.patch gri-2.12.27/debian/patches/fix-build-with-t64.patch --- gri-2.12.27/debian/patches/fix-build-with-t64.patch 1970-01-01 01:00:00.0 +0100 +++ gri-2.12.27/debian/patches/fix-build-with-t64.patch 2024-04-11 23:22:33.0 +0200 @@ -0,0 +1,40 @@ +From 4d93a4e76543b914400d9e425e7c2de5c9dbb58d Mon Sep 17 00:00:00 2001 +From: dankelley +Date: Fri, 5 Apr 2024 07:10:17 -0300 +Subject: [PATCH] possibly fix debian error on time_t + +I am a bit concerned that this may break gri on other platforms, but not +really very concerned, since this fiddling with time types is likely +irrelevant to modern machines. And I doubt that anybody is building gri +on some of the platforms for which the code is making special cases. + +Please note that I do not have access to a machine that reproduces the +error message. I am on macos, and don't want to break my toolchain by +over-writing my C++ compilers, etc., to try to reproduce the bug. + +Lacking access to any type of linux machine, I am not able to test +whether my change fixes the problem. But the `git diff` is only one line +long, so hopefully if there is still a problem on debian, someone can +tell me a preprocesser symbol that I can use (and perhaps a header.h +file I can specify) to define the `time_t` type. + +Sorry for the hassles. + +Dan Kelley +--- + src/gr.hh | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/src/gr.hh b/src/gr.hh +index 6ff2f20..97b1756 100644 +--- a/src/gr.hh b/src/gr.hh +@@ -395,7 +395,7 @@ double lapse_rate(double S, double t, double p); + #if defined(__DECCXX) + #define SECOND_TYPE int + #else +-#define SECOND_TYPE long ++#define SECOND_TYPE time_t + #endif + #endif + diff -Nru gri-2.12.27/debian/patches/series gri-2.12.27/debian/patches/series --- gri-2.12.27/debian/patches/series 2022-08-25 18:33:47.0 +0200 +++ gri-2.12.27/debian/patches/series 2024-04-11 23:22:47.0 +0200 @@ -1 +1,2 @@ imagemagick.patch +fix-build-with-t64.patch
Bug#1067654: tpm2-abrmd: diff for NMU version 3.0.0-1.1
Dear maintainer, I've prepared an NMU for tpm2-abrmd (versioned as 3.0.0-1.1). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru tpm2-abrmd-3.0.0/debian/changelog tpm2-abrmd-3.0.0/debian/changelog --- tpm2-abrmd-3.0.0/debian/changelog 2022-12-12 00:47:34.0 +0100 +++ tpm2-abrmd-3.0.0/debian/changelog 2024-04-11 23:12:31.0 +0200 @@ -1,3 +1,13 @@ +tpm2-abrmd (3.0.0-1.1) unstable; urgency=medium + + * Non-maintainer upload + + [ Michael Hudson-Doyle ] + * Disable testsuite on armhf for now (the mocking the test harness +does fails when _FILE_BITS == 64) (Closes: #1067654). + + -- Sebastian Ramacher Thu, 11 Apr 2024 23:12:31 +0200 + tpm2-abrmd (3.0.0-1) unstable; urgency=low [ Debian Janitor ] diff -Nru tpm2-abrmd-3.0.0/debian/rules tpm2-abrmd-3.0.0/debian/rules --- tpm2-abrmd-3.0.0/debian/rules 2022-12-12 00:42:50.0 +0100 +++ tpm2-abrmd-3.0.0/debian/rules 2024-04-11 23:12:31.0 +0200 @@ -4,9 +4,14 @@ export DEB_CFLAGS_MAINT_APPEND = -Wall # Some variables: +DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) +ifneq (,$(filter armhf armel,$(DEB_HOST_ARCH))) +DEB_BUILD_OPTIONS+=nocheck +endif + %: dh $@ --exclude=.la --with autoreconf
Bug#1067418: tpm2-tss: diff for NMU version 4.0.1-7.2
Control: tags 1067418 + patch
Dear maintainer,
I've prepared an NMU for tpm2-tss (versioned as 4.0.1-7.2). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru tpm2-tss-4.0.1/debian/changelog tpm2-tss-4.0.1/debian/changelog
--- tpm2-tss-4.0.1/debian/changelog 2024-02-29 19:28:02.0 +0100
+++ tpm2-tss-4.0.1/debian/changelog 2024-04-11 23:02:54.0 +0200
@@ -1,3 +1,11 @@
+tpm2-tss (4.0.1-7.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Apply upstream patch to skip tests which fail on 32-bit
+with _FILE_BITS=64 (Closes: #1067418)
+
+ -- Sebastian Ramacher Thu, 11 Apr 2024 23:02:54 +0200
+
tpm2-tss (4.0.1-7.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru tpm2-tss-4.0.1/debian/patches/series tpm2-tss-4.0.1/debian/patches/series
--- tpm2-tss-4.0.1/debian/patches/series 2024-01-25 14:46:19.0 +0100
+++ tpm2-tss-4.0.1/debian/patches/series 2024-04-11 23:02:01.0 +0200
@@ -4,3 +4,4 @@
0004-tss2-tcti-tcti-libtpms-fix-test-failure-on-big-endia.patch
fix-tcti-spi-helper-big-endian.patch
disable-tests-on-big-endian.patch
+skip-tests-which-fail-on-32-bit.patch
diff -Nru tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch
--- tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch 1970-01-01 01:00:00.0 +0100
+++ tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch 2024-04-11 23:02:09.0 +0200
@@ -0,0 +1,120 @@
+From 932b1e78047ed0ddc09fcb06bff2e7cf96406976 Mon Sep 17 00:00:00 2001
+From: Juergen Repp
+Date: Sun, 17 Mar 2024 10:43:19 +0100
+Subject: [PATCH] unit tests: skip tests which fail on 32-bit with
+ _FILE_BITS=64
+
+Tests file the unit tests are compiled with _FILE_BITS is set to 64.
+The tests work without problems if _FILE_BITS is not set.
+Addresses: #2786
+
+Signed-off-by: Juergen Repp
+---
+ MAINTAINERS.md | 2 +-
+ test/unit/fapi-io.c | 7 +++
+ test/unit/tcti-device.c | 11 +++
+ test/unit/tcti-libtpms.c | 8
+ test/unit/tcti-pcap.c| 11 +++
+ 5 files changed, 38 insertions(+), 1 deletion(-)
+
+--- a/test/unit/fapi-io.c
b/test/unit/fapi-io.c
+@@ -28,6 +28,7 @@
+ #define LOGMODULE tests
+ #include "util/log.h"
+
++#define EXIT_SKIP 77
+ /*
+ * The unit tests will simulate error codes which can be returned by the
+ * system calls for file system IO.
+@@ -364,6 +365,12 @@
+ int
+ main(int argc, char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ };
+ return cmocka_run_group_tests(tests, NULL, NULL);
+--- a/test/unit/tcti-device.c
b/test/unit/tcti-device.c
+@@ -25,6 +25,11 @@
+ #include "tss2-tcti/tcti-common.h"
+ #include "tss2-tcti/tcti-device.h"
+
++#define LOGMODULE tests
++#include "util/log.h"
++
++#define EXIT_SKIP 77
++
+ /*
+ * Size of the TPM2 buffer used in these tests. In some cases this will be
+ * the command sent (transmit tests) and in others it's used as the response
+@@ -443,6 +448,12 @@
+ int
+ main(int argc, char* argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ cmocka_unit_test (tcti_device_init_all_null_test),
+ cmocka_unit_test(tcti_device_init_size_test),
+--- a/test/unit/tcti-libtpms.c
b/test/unit/tcti-libtpms.c
+@@ -28,6 +28,8 @@
+ #define LOGMODULE test
+ #include "util/log.h"
+
++#define EXIT_SKIP 77
++
+ #define LIBTPMS_DL_HANDLE 0x12345678
+ #define STATEFILE_PATH "statefile.bin"
+ #define STATEFILE_FD 0xAABB
+@@ -1612,6 +1614,12 @@
+ main(int argc,
+ char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ cmocka_unit_test(tcti_libtpms_init_all_null_test),
+ cmocka_unit_test(tcti_libtpms_init_dlopen_fail_test),
+--- a/test/unit/tcti-pcap.c
b/test/unit/tcti-pcap.c
+@@ -27,6 +27,11 @@
+ #include "tss2-tcti/tcti-common.h"
+ #include "tss2-tcti/tcti-pcap.h"
+
++#define LOGMODULE tests
++#include "util/log.h"
++
++#define EXIT_SKIP 77
++
+ #if (__BYTE_ORDER__ == __ORDER_BIG_ENDIAN__)
+ #define _LE32TOH(a,b,c,d) d,c,b,a
+ #define _LE16TOH(a,b) b,a
+@@ -726,6 +731,12 @@
+ main (int argc,
+ char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produ
Bug#1068840: llvm-toolchain-14: FTBFS on mips64el: /<>/compiler-rt/lib/builtins/clear_cache.c:97:3: error: implicit declaration of function 'syscall' is invalid in C99 [-Werror,-Wimplicit
iltins/divtc3.c ninja: build stopped: subcommand failed. FAILED: runtimes/builtins-stamps/builtins-build /<>/build-llvm/runtimes/builtins-stamps/builtins-build cd /<>/build-llvm/runtimes/builtins-bins && /usr/bin/cmake --build . ninja: build stopped: subcommand failed. make[1]: *** [debian/rules:713: debian-full-build] Error 1 Cheers -- Sebastian Ramacher
Bug#1067957: [EXTERNAL] Re: [[maude-bugs]] Maude fails to build on armhf
Hi Steven On 2024-04-08 15:38:50 -0700, Steven Eker wrote: > Hi Nilish, > > I don't have a 32-bit machine to test on, but my understanding is that Linux > has moved to a 64-bit signed integer for time_t and this is a long long on > 32-bit machines which is explicitly not supported by GMP's C++ API. This sounds like it needs to fixed in GMP then. > > https://en.wikipedia.org/wiki/Year_2038_problem > https://gmplib.org/manual/C_002b_002b-Interface-Integers > > I'm not happy converting a signed value to an unsigned value for all > architectures. But > > mpz_class nanoSeconds(static_cast(timeValue.tv_sec)); > > should fix the problem, at least until 2038. Can you check that this works? > If so I'll put it in the next public alpha. And this does not sound like a fix which we want. Best Sebastian -- Sebastian Ramacher
Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed
Source: cfengine3 Version: 3.21.4-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=cfengine3=armel=3.21.4-1=1712477798=0 == Starting test: files_interfaces_test.c == test_cfreadline_valid: Starting test test_cfreadline_valid: Test completed successfully. test_cfreadline_corrupted: Starting test test_cfreadline_corrupted: Test completed successfully. All 2 tests passed PASS: files_interfaces_test 1 != 3 ERROR: connection_management_test.c:39 Failure! 1 != 2 ERROR: connection_management_test.c:69 Failure! 1 != 2 ERROR: connection_management_test.c:99 Failure! 1 != 2 ERROR: connection_management_test.c:129 Failure! 4 out of 4 tests failed! test_purge_old_connections_nochange test_purge_old_connections_purge_first test_purge_old_connections_purge_middle test_purge_old_connections_purge_last == Starting test: connection_management_test.c == test_purge_old_connections_nochange: Starting test test_purge_old_connections_nochange: Test failed. test_purge_old_connections_purge_first: Starting test test_purge_old_connections_purge_first: Test failed. test_purge_old_connections_purge_middle: Starting test test_purge_old_connections_purge_middle: Test failed. test_purge_old_connections_purge_last: Starting test test_purge_old_connections_purge_last: Test failed. FAIL: connection_management_test Cheers -- Sebastian Ramacher
Bug#1068666: haskell-fold-debounce: FTBFS on arm{el,hf}: 14 examples, 2 failures
Source: haskell-fold-debounce
Version: 0.2.0.11-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=haskell-fold-debounce=armel=0.2.0.11-1%2Bb2=1712466208=0
Failures:
test/Control/FoldDebounceSpec.hs:81:40:
1) Control.FoldDebounce.Trigger emits the output event 'delay' interval after
the first input event (alwaysResetTimer = False)
expected: Just [10,20,30,40,50]
but got: Just [10,20,30]
To rerun use: --match "/Control.FoldDebounce/Trigger/emits the output event
'delay' interval after the first input event (alwaysResetTimer = False)/"
test/Control/FoldDebounceSpec.hs:143:21:
2) Control.FoldDebounce.Trigger emits output events even if input events are
coming intensely
predicate failed on: ["abc"]
To rerun use: --match "/Control.FoldDebounce/Trigger/emits output events even
if input events are coming intensely/"
Randomized with seed 1347232098
Finished in 2.9315 seconds
14 examples, 2 failures
Test suite spec-threaded: FAIL
Test suite logged to: dist-ghc/test/fold-debounce-0.2.0.11-spec-threaded.log
0 of 2 test suites (0 of 2 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 692
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1068664: haskell-filestore: FTBFS on arm{el,hf}: Total Cases: 42 Tried: 42 Errors: 1 Failures: 1
Source: haskell-filestore
Version: 0.6.5-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
Running 1 test suites...
Test suite test-filestore: RUNNING...
Cases: 21 Tried: 0 Errors: 0 Failures: 0
Cases: 21 Tried: 1 Errors: 0 Failures: 0
Cases: 21 Tried: 2 Errors: 0 Failures: 0
Cases: 21 Tried: 3 Errors: 0 Failures: 0
Cases: 21 Tried: 4 Errors: 0 Failures: 0
Cases: 21 Tried: 5 Errors: 0 Failures: 0
Cases: 21 Tried: 6 Errors: 0 Failures: 0
Cases: 21 Tried: 7 Errors: 0 Failures: 0
Cases: 21 Tried: 8 Errors: 0 Failures: 0
Cases: 21 Tried: 9 Errors: 0 Failures: 0
Cases: 21 Tried: 10 Errors: 0 Failures: 0
Cases: 21 Tried: 11 Errors: 0 Failures: 0
Cases: 21 Tried: 12 Errors: 0 Failures: 0
Cases: 21 Tried: 13 Errors: 0 Failures: 0
Cases: 21 Tried: 14 Errors: 0 Failures: 0
Cases: 21 Tried: 15 Errors: 0 Failures: 0
Cases: 21 Tried: 16 Errors: 0 Failures: 0
Cases: 21 Tried: 17 Errors: 0 Failures: 0
Cases: 21 Tried: 18 Errors: 0 Failures: 0
### Failure in: 18:Git (history and revision)
tests/Tests.hs:335
history from now + 1 day onwards is empty
Cases: 21 Tried: 19 Errors: 0 Failures: 1
Cases: 21 Tried: 20 Errors: 0 Failures: 1
Cases: 21 Tried: 21 Errors: 0 Failures: 1
Cases: 21 Tried: 0 Errors: 0 Failures: 0
Cases: 21 Tried: 1 Errors: 0 Failures: 0
Cases: 21 Tried: 2 Errors: 0 Failures: 0
Cases: 21 Tried: 3 Errors: 0 Failures: 0
Cases: 21 Tried: 4 Errors: 0 Failures: 0
Cases: 21 Tried: 5 Errors: 0 Failures: 0
Cases: 21 Tried: 6 Errors: 0 Failures: 0
Cases: 21 Tried: 7 Errors: 0 Failures: 0
Cases: 21 Tried: 8 Errors: 0 Failures: 0
Cases: 21 Tried: 9 Errors: 0 Failures: 0
Cases: 21 Tried: 10 Errors: 0 Failures: 0
Cases: 21 Tried: 11 Errors: 0 Failures: 0
Cases: 21 Tried: 12 Errors: 0 Failures: 0
Cases: 21 Tried: 13 Errors: 0 Failures: 0
Cases: 21 Tried: 14 Errors: 0 Failures: 0
Cases: 21 Tried: 15 Errors: 0 Failures: 0
Cases: 21 Tried: 16 Errors: 0 Failures: 0
Cases: 21 Tried: 17 Errors: 0 Failures: 0
Cases: 21 Tried: 18 Errors: 0 Failures: 0
### Error in: 18:Mercurial (history and revision)
UnknownError: mercurial log returned error status.
hg: parse error: invalid date: '134982229649-07-10 23:17:33'
Cases: 21 Tried: 19 Errors: 1 Failures: 0
Cases: 21 Tried: 20 Errors: 1 Failures: 0
Cases: 21 Tried: 21 Errors: 1 Failures: 0
Total Cases: 42 Tried: 42 Errors: 1 Failures: 1
Test suite test-filestore: FAIL
Test suite logged to: dist-ghc/test/filestore-0.6.5-test-filestore.log
0 of 1 test suites (0 of 1 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 692
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1068663: zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined
Source: zzuf Version: 0.15-3 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=zzuf=armhf=0.15-3=1712473020=0 In file included from /usr/include/arm-linux-gnueabihf/sys/cdefs.h:24, from libzzuf/lib-mem.c:24: /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" | ^~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DLIBZZUF -I./libzzuf -I./common -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -g -O2 -Wall -W -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c libzzuf/lib-signal.c -o libzzuf/la-lib-signal.o >/dev/null 2>&1 /tmp/ccnMZahz.s: Assembler messages: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined /tmp/ccnMZahz.s:4926: Error: symbol `lseek64' is already defined make[3]: *** [Makefile:708: libzzuf/la-lib-fd.lo] Error 1 make[3]: *** Waiting for unfinished jobs /tmp/ccKhQeYR.s: Assembler messages: /tmp/ccKhQeYR.s:1867: Error: symbol `mmap64' is already defined Cheers -- Sebastian Ramacher
Bug#1068660: mpv: No sound. Please backport upstream patch.
Control: severity -1 minor On 2024-04-08 23:06:17 +0300, Roman Lebedev wrote: > Package: mpv > Version: 0.37.0-1+b1 > Severity: important > Tags: upstream > X-Debbugs-Cc: maril...@deb-multimedia.org > > Dear maintainers, > an upstream fix for https://github.com/mpv-player/mpv/pull/13665 > which was not yet released in any mpv version needs to be backported > to the current mpv version, looks like the problematic ffmpeg version > is finally in debian (or deb-multimedia, but still.), resulting in no audio: This version is only in experimental and mpv has not been rebuilt against ffmpeg 7.0. As you have dmo enabled, you get to keep the pieces. Keeping the bug open for the transiton to ffmpeg 7.0. Cheers > ``` > AO: [pipewire] 48000Hz 5.1(side) 6ch floatp > VO: [gpu] 1920x960 yuv420p10 > [ffmpeg] SWR: Input channel layout "" is invalid or unsupported. > [swresample] Cannot open Libavresample context. > [swresample] libswresample failed to initialize. > Cannot convert decoder/filter output to any format supported by the > output. > Audio: no audio > ``` > > Roman. > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.7.9-amd64 (SMP w/32 CPU threads; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages mpv depends on: > ii libarchive13t64 3.7.2-2 > ii libasound2t64 1.2.11-1+b1 > ii libass9 2:0.17.1-dmo1 > ii libavcodec60 10:6.1.1-dmo4 > ii libavdevice60 10:6.1.1-dmo4 > ii libavfilter9 10:6.1.1-dmo4 > ii libavformat60 10:6.1.1-dmo4 > ii libavutil58 10:6.1.1-dmo4 > ii libbluray22:1.3.4-dmo2 > ii libc6 2.37-15.1 > ii libcaca0 0.99.beta20-4+b1 > ii libcdio-cdda2t64 10.2+2.0.1-1.1 > ii libcdio-paranoia2t64 10.2+2.0.1-1.1 > ii libcdio19t64 1:2.1.0-dmo5 > ii libdrm2 2.4.120-2 > ii libdvdnav46.1.1-3 > ii libegl1 1.7.0-1 > ii libgbm1 24.0.4-1 > ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3+b3 > ii libjpeg62-turbo 1:2.1.5-2+b2 > ii liblcms2-22.14-2+b1 > ii liblua5.2-0 5.2.4-3+b2 > ii libmujs3 1.3.3-3+b2 > ii libpipewire-0.3-0t64 1.0.4-3 > ii libplacebo338 2:6.338.2-dmo2 > ii libpulse0 16.1+dfsg1-5 > ii librubberband21:3.3.0-dmo1 > ii libsdl2-2.0-0 2.30.1+dfsg-4 > ii libsixel1 1.10.3-3 > ii libswresample410:6.1.1-dmo4 > ii libswscale7 10:6.1.1-dmo4 > ii libuchardet0 0.0.8-1+b1 > ii libva-drm22.20.0-2 > ii libva-wayland22.20.0-2 > ii libva-x11-2 2.20.0-2 > ii libva22.20.0-2 > ii libvdpau1 1.5-2 > ii libvulkan11.3.275.0-1 > ii libwayland-client01.22.0-2.1+b1 > ii libwayland-cursor01.22.0-2.1+b1 > ii libwayland-egl1 1.22.0-2.1+b1 > ii libx11-6 2:1.8.7-1 > ii libxext6 2:1.3.4-1+b1 > ii libxkbcommon0 1.6.0-1 > ii libxpresent1 1.0.0-2+b10 > ii libxrandr22:1.5.4-1 > ii libxss1 1:1.2.3-1 > ii libxv12:1.0.11-1.1 > ii libzimg2 1:3.0.5-dmo1 > ii zlib1g1:1.3.dfsg-3.1 > > Versions of packages mpv recommends: > ii xdg-utils 1.1.3-4.1 > ii yt-dlp 1:2024.03.10-dmo1 > > Versions of packages mpv suggests: > pn libcuda1 > > -- no debconf information > > -- Sebastian Ramacher
Bug#1068580: collected: FTBFS on arm{el,hf}: configure: error: "Some plugins are missing dependencies - see the summary above for details"
Hi Bernd On 2024-04-07 21:47:58 +0200, Bernd Zeimetz wrote: > Hi Sebastian, > > https://buildd.debian.org/status/package.php?p=grpc > > its just not built on armel yet and the old version is most likely not > installable anymore due to the time_t change. The last build of grpc was done successfully on April 1st. See https://buildd.debian.org/status/fetch.php?pkg=grpc=armel=1.51.1-4.1%2Bb1=1711980213=0 Also reverse dependencies were rebuilt with 64-bit time_t-aware grpc packages in the past. See https://release.debian.org/transitions/html/auto-grpc.html. The logs also have: configure:26065: checking for grpc++/grpc++.h configure:26065: arm-linux-gnueabi-g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -Wno-error=deprecated-declarations -std=c++11 -DNOMINMAX -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/debian/include -UCONFIGFILE -DCONFIGFILE='"/etc/collectd/collectd.conf"' conftest.cpp >&5 In file included from /usr/include/absl/base/config.h:86, from /usr/include/absl/base/const_init.h:25, from /usr/include/absl/synchronization/mutex.h:67, from /usr/include/grpcpp/impl/codegen/sync.h:32, from /usr/include/grpcpp/completion_queue.h:41, from /usr/include/grpcpp/channel.h:25, from /usr/include/grpcpp/grpcpp.h:52, from /usr/include/grpc++/grpc++.h:26, from conftest.cpp:167: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." 79 | #error "C++ versions less than C++14 are not supported." | ^ So somewhere there is a -std=c++14 missing. Cheers > > Bernd > > On Sun, 2024-04-07 at 14:48 +0200, Sebastian Ramacher wrote: > > Source: collectd > > Version: 5.12.0-17.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=collectd=armhf=5.12.0-17.1=1712493429=0 > > > > > > Configuration: > > Build: > > Platform . . . . . . Linux > > Compiler vendor . . . gnu > > CC . . . . . . . . . arm-linux-gnueabihf-gcc > > CFLAGS . . . . . . . -Wall -Werror -g -O2 -Werror=implicit- > > function-declaration -ffile-prefix-map=/<>=. -fstack- > > protector-strong -fstack-clash-protection -Wformat -Werror=format- > > security -Wall -Wno-error=deprecated-declarations -Wno-error=address- > > of-packed-member -Wno-stringop-truncation -Wno-cpp -Wno-error=format- > > truncation > > CXXFLAGS . . . . . . -Wall -Werror -g -O2 -ffile-prefix- > > map=/<>=. -fstack-protector-strong -fstack-clash- > > protection -Wformat -Werror=format-security -Wall -Wno- > > error=deprecated-declarations > > CPP . . . . . . . . . arm-linux-gnueabihf-gcc -E > > CPPFLAGS . . . . . . -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 - > > I/<>/debian/include -UCONFIGFILE - > > DCONFIGFILE='"/etc/collectd/collectd.conf"' > > GRPC_CPP_PLUGIN . . . /usr/bin/grpc_cpp_plugin > > LD . . . . . . . . . /usr/bin/ld > > LDFLAGS . . . . . . . -Wl,-z,relro -Wl,-z,now > > PROTOC . . . . . . . /usr/bin/protoc > > YACC . . . . . . . . bison -y > > YFLAGS . . . . . . . > > > > Libraries: > > intel mic . . . . . . no (MicAccessApi not found) > > libaquaero5 . . . . . no (libaquaero5.h not found) > > libatasmart . . . . . yes > > libcurl . . . . . . . yes > > libdbi . . . . . . . yes > > libdpdk . . . . . . . no (rte_config.h not found) > > libesmtp . . . . . . yes > > libganglia . . . . . no (gm_protocol.h not found) > > libgcrypt . . . . . . yes > > libgps . . . . . . . yes > > libgrpc++ . . . . . . no ( not found) > > libhiredis . . . . . yes > > libi2c-dev . . . . . yes > > libiokit . . . . . . no > > libiptc . . . . . . . yes > > libjansson . . . . . yes > > libjevents . . . . . no (jevents.h not found) > > libjvm . . . . . . . yes > > libkstat . . . . . . no (Solaris only) > > libkvm . . . . . . . no > > libldap . . . . . . . yes > > liblua . . . . . . . yes > > libmemcached . . . . yes > > libmicrohttpd . . . . yes > > libmnl . . . . . . . yes > >
Bug#1068584: RM: libgav1 [s390x] -- ROM; no longer builds on big-endian architectures
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: libg...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:libgav1 User: ftp.debian@packages.debian.org Usertags: remove The new upstream release of libgav1 no longer supports big-endian architectures (see #1068583). Builds failed in the same way on the other big-endian architectures on the ports. I have uploaded a new version of libavif (1.0.4-2) to disable the dependency on s390. After it built, libgav1 can be removed from s390x. Cheers -- Sebastian Ramacher
Bug#1068583: libgav1: FTBFS on s390x: test failures
Source: libgav1 Version: 0.19.0-2 Severity: important 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=libgav1=s390x=0.19.0-2=1712030294=0 The following tests FAILED: 8 - film_grain_test (Failed) 20 - average_blend_test (Failed) 22 - cdef_test (Failed) 23 - convolve_test (Failed) 28 - distance_weighted_blend_test (Failed) 31 - intrapred_cfl_test (Failed) 32 - intrapred_directional_test (Failed) 33 - intrapred_filter_test (Failed) 34 - intrapred_test (Failed) 35 - intra_edge_test (Failed) 38 - loop_filter_test (Failed) 39 - loop_restoration_test (Failed) 40 - mask_blend_test (Failed) 41 - motion_field_projection_test (Failed) 42 - motion_vector_search_test (Failed) 43 - obmc_test (Failed) 45 - post_filter_test (Failed) 52 - super_res_test (Failed) 54 - warp_test (Failed) Errors while running CTest Cheers -- Sebastian Ramacher
Bug#1067957: FTBFS: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is ambiguous
Control: reopen -1 On 2024-03-29 18:17:53 +0500, Andrey Rakhmatullin wrote: > Source: maude > Version: 3.2-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=maude=armhf=3.2-2%2Bb1=1711717901=0 > > In file included from timeManagerSymbol.cc:64: > timeActions.cc: In member function ‘void > TimeManagerSymbol::getTimeSinceEpoch(FreeDagNode*, > ObjectSystemRewritingContext&)’: > timeActions.cc:43:41: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is > ambiguous >43 | mpz_class nanoSeconds(timeValue.tv_sec); > | ^ It failed the same way with 3.4-1: https://buildd.debian.org/status/fetch.php?pkg=maude=armhf=3.4-1=1712489526=0 Cheers -- Sebastian Ramacher
Bug#1068580: collected: FTBFS on arm{el,hf}: configure: error: "Some plugins are missing dependencies - see the summary above for details"
. . . . . . . yes xmms . . . . . . . . no (disabled on command line) zfs_arc . . . . . . . yes zone . . . . . . . . no (disabled on command line) zookeeper . . . . . . yes configure: error: "Some plugins are missing dependencies - see the summary above for details" Cheers -- Sebastian Ramacher
Bug#1068572: tgt: ceph no longer supports 32 bit architectures
Source: tgt Version: 1:1.0.85-1.1 Severity: serious Control: block #1065470 by -1 X-Debbugs-Cc: sramac...@debian.org ceph no longer supports 32 bit architectures. Please stop build depending on librbd-dev on 32 bit architectures and please also stop building tgt-rbd on 32 bit architectures. Cheers -- Sebastian Ramacher
Bug#1068569: RM: nfs-ganesha-ceph [armel armhf i386] -- NBS; ceph dropped 32 bit support
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: nfs-gane...@packages.debian.org, sramac...@debian.org User: ftp.debian@packages.debian.org Usertags: remove Control: affects -1 + src:nfs-ganesha Control: block 1065470 by -1 Control: clone -1 -2 Control: clone -1 -3 Control: retitle -2 RM: nfs-ganesha-grace [armel armhf i386] -- NBS; ceph dropped 32 bit support Control: retitle -3 RM: nfs-ganesha-rgw [armel armhf i386] -- NBS; ceph dropped 32 bit support nfs-ganesha (4.3-6) unstable; urgency=medium . * only configure with ceph for some 64bit archs So please remove the old nfs-ganesha-ceoph, nfs-ganesha-rados-grace, and nfs-genesha-rgw binaries from armel, armhf and i386. Cheers -- Sebastian Ramacher
Bug#1068568: RM: libvirt-daemon-driver-storage-rbd [armel armhf i386] -- NBS; ceph dropped 32 bit support
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: libv...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:libvirt Control: block 1065470 by -1 User: ftp.debian@packages.debian.org Usertags: remove libvirt (9.8.0-1) unstable; urgency=medium . [ Pino Toscano ] * [a3a1f2e] Enable the rbd/ceph storage driver only on 64bit architectures - Closes: #1053168 Please remove the old libvirt-daemon-driver-storage-rbd binaries from armel, armhf and i386. Cheers -- Sebastian Ramacher
Bug#1068566: RM: uwsgi-plugin-rados [armel armhf i386] -- NBS; ceph dropped 32 bit support
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: uw...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:uwsgi Control: block 1065470 by -1 User: ftp.debian@packages.debian.org Usertags: remove uwsgi (2.0.24-3) unstable; urgency=medium . [ Alexandre Rossi ] * disable rados plugin on 32 bits archs; So please remove the old uwsgi-plugin-rados binaries from armel, armhf and i386. Cheers -- Sebastian Ramacher
Bug#1068540: chromium: depends on pre-t64 library
Source: chromium Version: 123.0.6312.105-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org chromium has a hard-coded dependency on libgtk-3-0 which changed the package name as part of the time_t transition. Please update the dependency accordingly - or even better - derive the dependency from the corresponding -dev package installed during the build. Cheers -- Sebastian Ramacher
Bug#1068538: ruby-ffi-libarchive: arch:all package depends on pre-t64 library
Source: ruby-ffi-libarchive Version: 1.0.1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org ruby-ffi-libarchive builds an Architecture: all package that depends on a library involved in the time_t transition (libarchive13). Please ensure that the package wroks with the library using the new time_t ABI and update the dependencies accordingly. Cheers -- Sebastian Ramacher
Bug#1068537: ruby-ethon: arch:all package depends on pre-t64 library
Source: ruby-ethon Version: 0.16.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org ruby-ethon builds an Architecture: all package that depends on a library that is involved in the t64 package (libcurl4). Please make sure that the packages works with the package using the new 64 time_t ABI and update the dependencies accordingly. Cheers -- Sebastian Ramacher
Bug#1068513: dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API
Source: dablin Version: 1.15.0-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=dablin=armel=1.15.0-1%2Bb2=1712391165=0 [ 97%] Linking CXX executable dablin cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/dablin.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z now -rdynamic CMakeFiles/dablin.dir/sdl_output.cpp.o CMakeFiles/dablin.dir/dabplus_decoder.cpp.o CMakeFiles/dablin.dir/ensemble_source.cpp.o CMakeFiles/dablin.dir/ensemble_player.cpp.o CMakeFiles/dablin.dir/edi_source.cpp.o CMakeFiles/dablin.dir/edi_player.cpp.o CMakeFiles/dablin.dir/eti_source.cpp.o CMakeFiles/dablin.dir/eti_player.cpp.o CMakeFiles/dablin.dir/dab_decoder.cpp.o CMakeFiles/dablin.dir/fic_decoder.cpp.o CMakeFiles/dablin.dir/pcm_output.cpp.o CMakeFiles/dablin.dir/tools.cpp.o CMakeFiles/dablin.dir/version.cpp.o CMakeFiles/dablin.dir/dablin.cpp.o -o dablin ../fec/libfec.a /usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123 -lSDL2 -lfaad -lc -lm /usr/bin/ld: CMakeFiles/dablin.dir/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status make[3]: *** [src/CMakeFiles/dablin.dir/build.make:313: src/dablin] Error 1 make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[2]: *** [CMakeFiles/Makefile2:263: src/CMakeFiles/dablin.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable dablin_gtk cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/dablin_gtk.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z now -rdynamic CMakeFiles/dablin_gtk.dir/sdl_output.cpp.o CMakeFiles/dablin_gtk.dir/dabplus_decoder.cpp.o CMakeFiles/dablin_gtk.dir/ensemble_source.cpp.o CMakeFiles/dablin_gtk.dir/ensemble_player.cpp.o CMakeFiles/dablin_gtk.dir/edi_source.cpp.o CMakeFiles/dablin_gtk.dir/edi_player.cpp.o CMakeFiles/dablin_gtk.dir/eti_source.cpp.o CMakeFiles/dablin_gtk.dir/eti_player.cpp.o CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o CMakeFiles/dablin_gtk.dir/fic_decoder.cpp.o CMakeFiles/dablin_gtk.dir/pcm_output.cpp.o CMakeFiles/dablin_gtk.dir/tools.cpp.o CMakeFiles/dablin_gtk.dir/version.cpp.o CMakeFiles/dablin_gtk.dir/mot_manager.cpp.o CMakeFiles/dablin_gtk.dir/pad_decoder.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk_dl_plus.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk_sls.cpp.o -o dablin_gtk ../fec/libfec.a /usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123 -lSDL2 -lfaad -lc -lgtkmm-3.0 -latkmm-1.6 -lgdkmm-3.0 -lgiomm-2.4 -lgtk-3 -lgdk-3 -lz -latk-1.0 -lcairo-gobject -lgio-2.0 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -lcairo -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lm /usr/bin/ld: CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status make[3]: *** [src/CMakeFiles/dablin_gtk.dir/build.make:377: src/dablin_gtk] Error 1 This is caused by #define MPG123_NO_LARGENAME // disable large file API here in src/dab_decoder.h Cheers -- Sebastian Ramacher
Bug#1068512: welle.io: FTBFS on arm{el,hf}: manually disables mpg123's LFS API
Source: welle.io Version: 2.4+ds-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=welle.io=armel=2.4%2Bds-2%2Bb3=1712391447=0 [ 99%] Linking CXX executable welle-io /usr/bin/cmake -E cmake_link_script CMakeFiles/welle-io.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic "CMakeFiles/welle-io.dir/welle-io_autogen/mocs_compilation.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/main.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/audio_output.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mot_image_provider.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/gui_helper.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/radio_controller.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris_mp2.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris_mp2_player.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/debug_output.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/waterfallitem.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab-audio.cpp.o" "CMakeFiles/welle-io.dir/src/backend/decoder_adapter.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dabplus_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/charsets.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab-constants.cpp.o" "CMakeFiles/welle-io.dir/src/backend/mot_manager.cpp.o" "CMakeFiles/welle-io.dir/src/backend/pad_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/eep-protection.cpp.o" "CMakeFiles/welle-io.dir/src/backend/fib-processor.cpp.o" "CMakeFiles/welle-io.dir/src/backend/fic-handler.cpp.o" "CMakeFiles/welle-io.dir/src/backend/msc-handler.cpp.o" "CMakeFiles/welle-io.dir/src/backend/freq-interleaver.cpp.o" "CMakeFiles/welle-io.dir/src/backend/ofdm-decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/ofdm-processor.cpp.o" "CMakeFiles/welle-io.dir/src/backend/phasereference.cpp.o" "CMakeFiles/welle-io.dir/src/backend/phasetable.cpp.o" "CMakeFiles/welle-io.dir/src/backend/tii-decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/protTables.cpp.o" "CMakeFiles/welle-io.dir/src/backend/radio-receiver.cpp.o" "CMakeFiles/welle-io.dir/src/backend/tools.cpp.o" "CMakeFiles/welle-io.dir/src/backend/uep-protection.cpp.o" "CMakeFiles/welle-io.dir/src/backend/viterbi.cpp.o" "CMakeFiles/welle-io.dir/src/various/Socket.cpp.o" "CMakeFiles/welle-io.dir/src/various/Xtan2.cpp.o" "CMakeFiles/welle-io.dir/src/various/channels.cpp.o" "CMakeFiles/welle-io.dir/src/various/fft.cpp.o" "CMakeFiles/welle-io.dir/src/various/profiling.cpp.o" "CMakeFiles/welle-io.dir/src/various/wavfile.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/decode_rs_char.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/encode_rs_char.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/init_rs_char.c.o" "CMakeFiles/welle-io.dir/src/input/input_factory.cpp.o" "CMakeFiles/welle-io.dir/src/input/null_device.cpp.o" "CMakeFiles/welle-io.dir/src/input/raw_file.cpp.o" "CMakeFiles/welle-io.dir/src/input/rtl_tcp.cpp.o" "CMakeFiles/welle-io.dir/src/input/rtl_sdr.cpp.o" "CMakeFiles/welle-io.dir/src/input/airspy_sdr.cpp.o" "CMakeFiles/welle-io.dir/src/input/soapy_sdr.cpp.o" "CMakeFiles/welle-io.dir/welle-io_autogen/MOX6SOXE6H/qrc_resources.cpp.o" -o welle-io -lrtlsdr -lairspy -lfftw3f -lfaad /usr/lib/arm-linux-gnueabi/libSoapySDR.so.0.8.1 -lmpg123 /usr/lib/arm-linux-gnueabi/libQt5Multimedia.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Charts.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5QuickControls2.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5DBus.so.5.15.10 -pthread /usr/lib/arm-linux-gnueabi/libQt5Widgets.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Quick.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5QmlModels.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Qml.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Network.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Gui.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Core.so.5.15.10 /usr/bin/ld: CMakeFiles/welle-io.dir/src/backend/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/./src/backend/dab_decoder.cpp:168:(.text+0x1c6c): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status This is caused by #define MPG123_NO_LARGENAME // disable large file API here in src/dab_decoder.h Cheers -- Sebastian Ramacher
Bug#1068366: nmu: gyoto_2.0.2-1.1
Control: tags -1 moreinfo On 2024-04-04 09:27:06 +0100, plugwash wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > It seems that the new version of gyoto was built a bit too early and, on most > architectures, picked up a dependency on libcfitsio10 rather than > libcfitsio10t64. > > nmu gyoto_2.0.2-1.1 . ANY . unstable . -m "Rebuild against libcfitsio10t64 > for time64 transition." gyoto currently FTBFS, see #1067562. If this bug was fixed, please fix its metadata. Otherwise it will need an upload anyway. Cheers -- Sebastian Ramacher
Bug#1068367: squashfuse: diff for NMU version 0.5.2-0.2
Package: squashfuse Version: 0.5.2-0.1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for squashfuse (versioned as 0.5.2-0.2) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru squashfuse-0.5.2/debian/changelog squashfuse-0.5.2/debian/changelog --- squashfuse-0.5.2/debian/changelog 2024-04-01 23:09:03.0 +0200 +++ squashfuse-0.5.2/debian/changelog 2024-04-04 10:21:39.0 +0200 @@ -1,3 +1,10 @@ +squashfuse (0.5.2-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Link with libatomic on armel + + -- Sebastian Ramacher Thu, 04 Apr 2024 10:21:39 +0200 + squashfuse (0.5.2-0.1) unstable; urgency=medium * Non-maintainer upload diff -Nru squashfuse-0.5.2/debian/rules squashfuse-0.5.2/debian/rules --- squashfuse-0.5.2/debian/rules 2023-11-02 09:42:28.0 +0100 +++ squashfuse-0.5.2/debian/rules 2024-04-04 10:21:39.0 +0200 @@ -1,8 +1,13 @@ #!/usr/bin/make -f -DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH). +DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) export DEB_BUILD_MAINT_OPTIONS=hardening=+all +ifeq ($(DEB_HOST_ARCH),armel) +export DEB_LDFLAGS_MAINT_APPEND=-latomic +endif + %: dh $@
Bug#1063140: mpg123: NMU diff for 64-bit time_t transition
lframe_64@Base 1.13.7 mpg123_timeframe64@Base 1.32.3 - mpg123_timeframe@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_timeframe_32@Base 1.13.7 +#MISSING: 1.32.6~dev+20240403022201-1# mpg123_timeframe@Base 1.6.2 +#MISSING: 1.32.6~dev+20240403022201-1# (arch-bits=32|arch=!x32)mpg123_timeframe_32@Base 1.13.7 mpg123_timeframe_64@Base 1.13.7 mpg123_tpf@Base 1.6.2 mpg123_volume@Base 1.6.2 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsyn123-0/DEBIAN/symbols doesn't match completely debian/libsyn123-0.symbols --- debian/libsyn123-0.symbols (libsyn123-0_1.32.6~dev+20240403022201-1_armhf) +++ dpkg-gensymbols0VudKK 2024-04-03 09:52:13.071134835 + @@ -32,15 +32,15 @@ syn123_resample_incount@Base 1.26.0 syn123_resample_inexpect@Base 1.26.0 syn123_resample_intotal64@Base 1.32.3 - syn123_resample_intotal@Base 1.26.2 - (arch-bits=32|arch=!x32)syn123_resample_intotal_32@Base 1.26.2 +#MISSING: 1.32.6~dev+20240403022201-1# syn123_resample_intotal@Base 1.26.2 +#MISSING: 1.32.6~dev+20240403022201-1# (arch-bits=32|arch=!x32)syn123_resample_intotal_32@Base 1.26.2 syn123_resample_intotal_64@Base 1.26.0 syn123_resample_maxincount@Base 1.26.0 syn123_resample_maxrate@Base 1.26.0 syn123_resample_out@Base 1.32.3 syn123_resample_total64@Base 1.32.3 - syn123_resample_total@Base 1.26.2 - (arch-bits=32|arch=!x32)syn123_resample_total_32@Base 1.26.2 +#MISSING: 1.32.6~dev+20240403022201-1# syn123_resample_total@Base 1.26.2 +#MISSING: 1.32.6~dev+20240403022201-1# (arch-bits=32|arch=!x32)syn123_resample_total_32@Base 1.26.2 syn123_resample_total_64@Base 1.26.0 syn123_setup_filter@Base 1.26.0 syn123_setup_geiger@Base 1.26.0 dh_makeshlibs: error: failing due to earlier errors >From your explanation above, this is what I expected. The builds on 64 bit architectures and i386 are unaffected. > It's up to you (Debian) to decide what to do with binary package naming > for the transition (it is your business anyway;-), but I feel strongly > about the change to avoid an existing symbol changing ABI with subtle > breakage. If you feel strongly about this, I think the best option would be to bump SONAME of the libraries upstream … but this can be done later during the release cycle and we do the package rename for now to move the transition along. Cheers -- Sebastian Ramacher
Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library
On 2024-04-03 23:46:43 +0200, Andrea Bolognani wrote:
> On Tue, Apr 02, 2024 at 12:02:53AM +0200, Sebastian Ramacher wrote:
> > On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> > > The problem with it, and the reason why a manual dependency is used
> > > in that case, is that ${shlib:Depends} will not pick it up, since
> > > it's dlopen()ed rather than linked against.
> > >
> > > Do you have any suggestions on how to handle this in a way that plays
> > > well with the 64-bit time_t transition?
> >
> > You could derive it from the the dependencies of libxt-dev during the
> > build or for the time being simply change the dependency based on the
> > rename of the libxt6 -- provided that spectrwm is compatible with the
> > new ABI.
>
> I just created [1] which should take care of the issue. It would be
> nice if you could take a look.
I have no idea what spectrwm is doing, so I am probably not the best one
to ask. From the time_t transition perspective, it is an improvement.
> To be honest, I haven't followed the 64-bit time_t transition very
> closely. Do I understand correctly that the SONAME has been changed
> without renaming the files on disk at the same time? That feels kinda
> weird, but I guess it has the nice side-effect of not breaking [2],
> so that's good :)
>
> I also see that libxt6t64 Provides: libxt6, so I'm not sure why the
> dependency on the old name would be a problem? Wasn't that introduced
> specifically to take care of this sort of things?
The libxt6 Provides is only available on architectures where the ABI did
not change. On armhf and armel, the Provides is not present and so the
dependency is not satisfiable.
Cheers
--
Sebastian Ramacher
Bug#1068299: macaulay2: FTBFS: failed assertion `i.exp() <= fq_nmod_ctx_degree(ctx)'
Source: macaulay2 Version: 1.23+ds-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=macaulay2=amd64=1.23%2Bds-1=1712102097=0 -- capturing check(23, "PrimaryDecomposition")error: convertFacCF2Fq_nmod_t: element is not reduced FLINTconvert.cc:466: In function `void convertFacCF2Fq_nmod_t(nmod_poly_struct*, const CanonicalForm&, const fq_nmod_ctx_struct*)': failed assertion `i.exp() <= fq_nmod_ctx_degree(ctx)' Aborted make[4]: *** [Makefile:50: check-PrimaryDecomposition] Error 134 Cheers -- Sebastian Ramacher
Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf
Source: openjdk-21 Version: 21.0.3~7ea-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, debian-...@lists.debian.org Hi Matthias, hi arm* porters building openjdk-21 is currently still stuck on openjdk-21 build-depending on itself: https://buildd.debian.org/status/package.php?p=openjdk-21 Dependency installability problem for openjdk-21 on armel: openjdk-21 build-depends on: - libcups2-dev:armel libcups2-dev depends on: - libcups2t64:armel (= 2.4.7-1.2) openjdk-21 build-depends on: - openjdk-21-jdk-headless:armel openjdk-21-jdk-headless depends on: - openjdk-21-jre-headless:armel (= 21.0.2+13-2) openjdk-21-jre-headless depends on: - libcups2:armel libcups2t64 conflicts with: - libcups2:armel (< 2.4.7-1.2) Dependency installability problem for openjdk-21 on armhf: openjdk-21 build-depends on: - libcups2-dev:armhf libcups2-dev depends on: - libcups2t64:armhf (= 2.4.7-1.2) openjdk-21 build-depends on: - openjdk-21-jdk-headless:armhf openjdk-21-jdk-headless depends on: - openjdk-21-jre-headless:armhf (= 21.0.2+13-2) openjdk-21-jre-headless depends on: - libcups2:armhf libcups2t64 conflicts with: - libcups2:armhf (< 2.4.7-1.2) Somebody did the work to provide boostrap builds of openjdk-17 on armel and armhf. We need the same for openjdk-21. Cheers -- Sebastian Ramacher
Bug#1068265: RM: flint-arb -- RoQA; merged into flint
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: flint-...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:flint-arb User: ftp.debian@packages.debian.org Usertags: remove flint-arb has been merged into flint. See #1058814 Please remove flint-arb from the archive. Cheers -- Sebastian Ramacher
Bug#1068264: avfs: FTBFS on armel: ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'
Source: avfs Version: 1.1.5-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=avfs=armel=1.1.5-1=1691158944=0 /bin/bash ../libtool --tag=CC --mode=link arm-linux-gnueabi-gcc -I../include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE -I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse -D_FILE_OFFSET_BITS=64-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z,relro -Wl,-z,now -lpthread -ldl -lneon-gnutls -llzma -lzstd -Wl,-z,relro -Wl,-z,now -o runtest runtest.o ../lib/libavfs_static.la -lpthread -ldl -lneon-gnutls -llzma -lzstd libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE -I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o gzip_multimember_test gzip_multimember_test.o ../lib/.libs/libavfs_static.a -lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma -lzstd libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE -I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o testread testread.o ../lib/.libs/libavfs_static.a -lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma -lzstd /usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function `xzfile_decompress': ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8' libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE -I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o runtest runtest.o ../lib/.libs/libavfs_static.a -lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma -lzstd collect2: error: ld returned 1 exit status make[2]: *** [Makefile:401: gzip_multimember_test] Error 1 make[2]: *** Waiting for unfinished jobs /usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function `xzfile_decompress': ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:409: testread] Error 1 /usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function `xzfile_decompress': ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:405: runtest] Error 1 Cheers -- Sebastian Ramacher
Bug#1068262: RM: libapache-mod-auth-kerb -- RoQA; not in (old)stable, security issues
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: libapache-mod-auth-k...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:libapache-mod-auth-kerb User: ftp.debian@packages.debian.org Usertags: remove #976156 states "libapache-mod-auth-kerb probably shouldn't be released in its current form" and there is no action from anyone that is interested in the package. So please remove the package from the archive. Cheers -- Sebastian Ramacher
Bug#1068260: RM: lix -- RoQA; RC buggy, unmaintained
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: l...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:lix User: ftp.debian@packages.debian.org Usertags: remove Fails to build since 2021 (#999750). Please remove it from the archive. Cheers -- Sebastian Ramacher
Bug#1068259: RM: kinput2 -- RoQA; dead upstream, RC buggy, orphaned
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: kinp...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:kinput2 User: ftp.debian@packages.debian.org Usertags: remove Orphaned since 2013 and now RC buggy (#1066714). Please remove it from the archive. Cheers -- Sebastian Ramacher
Bug#1068258: RM: libauthen-krb5-perl -- RoQA; dead upstream, RC buggy
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: libauthen-krb5-p...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:libauthen-krb5-perl User: ftp.debian@packages.debian.org Usertags: remove >From #1065768: Russ Allbery wrote: > Authen::Krb5 has a bunch of stuff that dates from the pre-GSS-API era of > Kerberos, and there were other things that at one point got me to start > writing my own version of the same idea (although alas I never finished). > In theory, one could delete the pieces of the module that try to do things > that no one should really be doing from Perl and the rest of it remains > somewhat useful, but given that upstream has archived the project, I would > go ahead and remove it. Cheers -- Sebastian Ramacher
Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'
On 2024-04-02 07:13:38 +0100, Alastair McKinstry wrote: > > On 01/04/2024 23:25, Sebastian Ramacher wrote: > > > There is a transition to openmpi-5 / mpi-defaults which is stalled by the > > > t64 transition. > > > > > > It drops 32-bit support from OpenMPI. > > > > > > Because of this, I don't think the solution is to port 32-bit atomics for > > > armel/armhf, as it will be removed in a few weeks/months. > > > > > > While we didn't want the transitions to be done simultaneously, it might > > > be > > > the best answer. > > > > > > > > > What does the release team think? > > Adding another transition on top will just delay the time_t transition > > even more. So if we can avoid that, I'd prefer to not do this transition > > now. Unfortunately, uploads such as the one of pmix that no dropped > > support for 32 bit architectures (#1068211) are not really helpful. > > > > Also, #1064810 has no information on test builds with the new > > mpi-defaults on a 32 bit architecture. So has this transition been > > tested? > > > > Cheers > > OpenMPI 5 drops 32-bit support, but otherwise does not change the API/ABI. > So it is technically not a transition, but breaks 32-bit builds. Doesn't make it better. This is not the time to do that without tests builds and bugs filed. > The solution is changing mpi-defaults to MPICH for 32-bit archs. MPICH > builds on all archs, but testing all dependencies of the change has not been > tested, and I don't know how you would do that - setting up eg ratt to > rebuild all on 32-bit archs (as everything on 64-bit will not have changed.) Beside the easy part of chaning mpi-defaults, I count 30 something packages that have explicit build dependencies on libopenmpi-dev. None of those packages has bugs filed to change to mpich on 32 bit architectures. To be honest, I don't see these two changes (changing mpi-defaults to mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32 bit until the time_t transition is done. Cheers -- Sebastian Ramacher
Bug#1067953: transition: flint
Control: tags -1 confirmed On 2024-03-29 12:46:50 +, Torrance, Douglas wrote: > Package: release.debian.org > Control: affects -1 + src:flint > X-Debbugs-Cc: fl...@packages.debian.org > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: dtorra...@piedmont.edu > Severity: normal > > Dear Release Team, > > I would like to request a transition slot for flint. The recent upstream > release 3.1.0 introduced the new soversion flint 19. A new binary package, > libflint19, was introduced in the source package flint 3.1.2-1~exp1, which > cleared the NEW queue on March 28 and is now in experimental. > > flint 3.1.1-1 already exists in unstable, which ships libflint.so.19 in > the libflint18t64 binary package. However, flint 3.0.1-3.1 had been > previously uploaded for the t64 transition, shipping libflint.so.18 in > the same binary package. This is RC bug #1067226 and has resulted in > several other RC bugs in reverse dependencies. Please go ahead so that reverse dpeendencies can actually build again. > An auto-flint tracker already exists for the t64 transition, but it doesn't > take the new libflint19 package into account. (Although perhaps this will > update automatically at some point?) > > binNMU's should be sufficient for each of flint's reverse dependencies: > > * e-antic > * gyoto > * macaulay2 > * msolve > * normaliz > * polymake > * singular Please perform test builds or track the rebuilds for build failures. Cheers > > Ben file: > > title = "flint"; > is_affected = (.build-depends ~ /\blibflint-dev\b/) | (.depends ~ > /\blibflint(?:18|18t64|19)\b/); > is_good = .depends ~ /\blibflint19\b/; > is_bad = .depends ~ /\blibflint18(?:t64)?\b/; > > Thank you! -- Sebastian Ramacher
Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:
ons/extractdebbuild.py > -@@ -35,7 +35,7 @@ def getdebbuildflags(): > +--- a/site_scons/extractdebbuild.py > b/site_scons/extractdebbuild.py > +@@ -35,7 +35,7 @@ > mycflags=None > mycxxflags=None > try: > @@ -17,11 +15,9 @@ > except OSError: > return [] > res=[] > -Index: python-escript-5.6/site_scons/dependencies.py > -=== > python-escript-5.6.orig/site_scons/dependencies.py > -+++ python-escript-5.6/site_scons/dependencies.py > -@@ -122,7 +122,7 @@ def call_python_config(bin=None): > +--- a/site_scons/dependencies.py > b/site_scons/dependencies.py > +@@ -122,7 +122,7 @@ > cmd+=' > sp=subprocess.Popen([pythonroot+"python"+pyversion+"-config","--ldflags"], > stdout=subprocess.PIPE)\n' > cmd+='d=sp.stdout.readline().split()\n' > cmd+="libdirs=[z[2:] for z in d if z.startswith(b'-L')]\n" > @@ -30,7 +26,7 @@ > cmd+="target=''\n" > cmd+="libname=''\n" > cmd+="for d in libdirs:\n" > -@@ -162,7 +162,7 @@ def call_python_config(bin=None): > +@@ -162,7 +162,7 @@ > libname=sp.stdout.readline().strip() > ver=sp.stdout.readline().strip() > pinc=sp.stdout.readline().strip() > @@ -39,7 +35,7 @@ > > def checkPython(env): > # First we check to see if the config file has specified > -@@ -177,7 +177,7 @@ def checkPython(env): > +@@ -177,7 +177,7 @@ > python_libs=['python%s%s'%(sys.version_info[0], > sys.version_info[1])] > verstring=".".join([str(i) for i in sys.version_info[:3]]) > else: > @@ -48,7 +44,7 @@ > > # if we want to use a python other than the one scons is running > # Note: we assume scons is running python 2 in the following. > -@@ -793,6 +793,7 @@ def checkOptionalLibraries(env): > +@@ -793,6 +793,7 @@ > else: > which = Popen(['which', 'gmsh'], stdout=PIPE) > path,_ = which.communicate() > diff -Nru python-escript-5.6/debian/patches/series > python-escript-5.6/debian/patches/series > --- python-escript-5.6/debian/patches/series 2023-12-10 16:25:14.0 > +0800 > +++ python-escript-5.6/debian/patches/series 2024-04-02 17:51:27.0 > +0800 > @@ -12,3 +12,4 @@ > make.patch > ignore-flags.patch > which.patch > +fix-dpkg-buildflags-on-c-c++.patch > diff -Nru python-escript-5.6/debian/rules python-escript-5.6/debian/rules > --- python-escript-5.6/debian/rules 2023-12-10 16:25:14.0 +0800 > +++ python-escript-5.6/debian/rules 2024-04-02 18:08:31.0 +0800 > @@ -13,7 +13,7 @@ > > #export DEB_CXXFLAGS_MAINT_APPEND = -Wno-maybe-uninitialized > #export DEB_CFLAGS_MAINT_APPEND = -Wno-maybe-uninitialized > -export DEB_CXXFLAGS_MAINT_APPEND = -Wno-uninitialized > +export DEB_CXXFLAGS_MAINT_APPEND = -Wno-uninitialized > -Werror=implicit-function-declaration > export DEB_CFLAGS_MAINT_APPEND = -Wno-uninitialized > > DPKG_EXPORT_BUILDFLAGS = 1 -- Sebastian Ramacher
Bug#1068213: gnome-remote-desktop: hard-coded dependency on pre-t64 library
Source: gnome-remote-desktop Version: 44.2-7 Severity: serious X-Debbugs-Cc: sramac...@debian.org gnome-remote-desktop builds a binary pckage with a hard-coded dependy on libmutter-12-0. This library was renamed as part of the time_t 64 transition. Please update the dependencies accordingly. Cheers -- Sebastian Ramacher
Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'
On 2024-04-01 12:05:30 +0100, Alastair McKinstry wrote: > > On 23/03/2024 01:58, Thorsten Glaser wrote: > > Andrey Rakhmatullin dixit: > > > > > OPAL_THREAD_ADD_FETCH64 is defined under #if OPAL_HAVE_ATOMIC_MATH_64 > > > And I assume this arch doesn't have 64-bit atomics. > > No native ones, yes. > > > > I *think* either libatomic or libatomic_ops(?) make them > > available, but very slowly, using a syscall to guarantee > > atomicity (those systems are normally uniprocessor) on > > m68k. > > > > If possible, avoiding them would be preferrable. (For > > example, in some cases, like reading a 64-bit timestamp, > > if the writing direction is known and stable, reading > > twice then comparing is a possible alternative at least > > for some architectures (e.g. I know BSD code for sparc > > does it that way). > > > > I guess you’ll have to ask the porters of 32-bit arches > > with no native 64-bit atomics for details. > > > > Though I had thought GCC’s builtin atomics use the > > aforementioned kernel-based workaround from that library > > these days? > > There is a transition to openmpi-5 / mpi-defaults which is stalled by the > t64 transition. > > It drops 32-bit support from OpenMPI. > > Because of this, I don't think the solution is to port 32-bit atomics for > armel/armhf, as it will be removed in a few weeks/months. > > While we didn't want the transitions to be done simultaneously, it might be > the best answer. > > > What does the release team think? Adding another transition on top will just delay the time_t transition even more. So if we can avoid that, I'd prefer to not do this transition now. Unfortunately, uploads such as the one of pmix that no dropped support for 32 bit architectures (#1068211) are not really helpful. Also, #1064810 has no information on test builds with the new mpi-defaults on a 32 bit architecture. So has this transition been tested? Cheers -- Sebastian Ramacher
Bug#1068211: pmix: FTBFS on 32 bit architectures: configure: WARNING: PMIx does not support 32 bit builds.
Source: pmix Version: 5.0.2-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=pmix=armel=5.0.2-1=1711406265=0 checking size of _Bool... 1 checking size of short... 2 checking size of int... 4 checking size of long... 4 checking size of void *... 4 configure: WARNING: PMIx does not support 32 bit builds. configure: error: Cannot continue -- Sebastian Ramacher
Bug#1068210: fricas: FTBFS on arm{el,hf}: /<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? [-Werror=
Source: fricas Version: 1.3.10-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=fricas=armhf=1.3.10-1%2Bb2=1711729211=0 /<>/src/lisp/fricas-lisp.c: In function ‘sock_get_string_buf_wrapper’: /<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? [-Werror=implicit-function-declaration] 1750 | return sock_get_string_buf(i, x->st.st_self, j); } | ^~~ | sock_send_string_len cc1: some warnings being treated as errors Correctable error: Fast links are on: do (si::use-fast-links nil) for debugging Signalled by COMPILE-FILE. If continued: Continues anyway.SIMPLE-ERROR: (SYSTEM "/usr/bin/gcc -c -g -Werror=implicit-function-declaration -ffile-prefix-map=/<>/gcl-2.6.14=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fsigned-char -pipe -fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -Wall -Wno-empty-body -Wno-unused-but-set-variable -fdollars-in-identifiers -g -I/usr/include/tirpc -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/lib/gcl-2.6.14/unixport/../h -O2 -c /<>/src/lisp/fricas-lisp.c -o /<>/src/lisp/fricas-lisp.o ") returned a non-zero value 1 0. Broken at COMPILE-FILE. Type :H for Help. 1 (continue) Continues anyway. 2 Return to top level. BOOTTRAN>> The compiler was called recursively. Cannot compile primitives.lisp. NIL NIL NIL BOOTTRAN>>make[3]: *** [Makefile:249: do_it.gcl] Error 255 Cheers -- Sebastian Ramacher
Bug#1068209: libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing
Source: libgtkada Version: 24.0.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org mkdir -p debian/tmp/usr/share/doc/gtkada/gtkada_ug cp --reflink=auto -aftdebian/tmp/usr/share/doc/gtkada/gtkada_ug \ docs/gtkada_ug/_build/html/* \ docs/gtkada_ug/_build/latex/GtkAda.pdf make[1]: Leaving directory '/<>' dh_install -i dh_installdocs -i dh_sphinxdoc -i dh_installchangelogs -i dh_installexamples -i dh_installman -i dh_ada_library -i dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing Cheers -- Sebastian Ramacher
Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library
Hi
On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> On Mon, Apr 01, 2024 at 10:37:03PM +0200, Sebastian Ramacher wrote:
> > Source: spectrwm
> > Version: 3.5.1-1
> > Severity: serious
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > spectrwm builds a packages with a hard-coded dependency on a library
> > package involved in the time_t 64 transition. This dependency needs to
> > be updated.
>
> It would be useful if you could be more specific. I guess you're
> talking about the dependency on libxt6?
Yes.
>
> The problem with it, and the reason why a manual dependency is used
> in that case, is that ${shlib:Depends} will not pick it up, since
> it's dlopen()ed rather than linked against.
>
> Do you have any suggestions on how to handle this in a way that plays
> well with the 64-bit time_t transition?
You could derive it from the the dependencies of libxt-dev during the
build or for the time being simply change the dependency based on the
rename of the libxt6 -- provided that spectrwm is compatible with the
new ABI.
Cheers
--
Sebastian Ramacher
Bug#1067010: squashfuse: diff for NMU version 0.5.2-0.1
Control: tags 1067010 + patch
Control: tags 1067010 + pending
Dear maintainer,
I've prepared an NMU for squashfuse (versioned as 0.5.2-0.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru squashfuse-0.5.0/.cirrus.yml squashfuse-0.5.2/.cirrus.yml
--- squashfuse-0.5.0/.cirrus.yml 2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.cirrus.yml 2024-02-22 16:19:33.0 +0100
@@ -3,12 +3,12 @@
freebsd_task:
freebsd_instance:
-image_family: freebsd-12-3
+image_family: freebsd-14-0
setup_script:
- pkg install -y autoconf automake libtool pkgconf fusefs-libs
- pkg install -y lzo2 liblz4 zstd
- pkg install -y squashfs-tools coreutils
-- kldload fuse
+- kldload fusefs
- sysctl vfs.usermount=1
build_script:
- ./autogen.sh
diff -Nru squashfuse-0.5.0/configure.ac squashfuse-0.5.2/configure.ac
--- squashfuse-0.5.0/configure.ac 2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/configure.ac 2024-02-22 16:19:33.0 +0100
@@ -1,4 +1,4 @@
-AC_INIT([squashfuse], [0.5.0], [d...@vasilevsky.ca])
+AC_INIT([squashfuse], [0.5.2], [d...@vasilevsky.ca])
AC_CONFIG_MACRO_DIR([m4])
AC_CONFIG_AUX_DIR([build-aux])
AC_CONFIG_HEADERS([config.h])
@@ -91,6 +91,7 @@
AC_SUBST([sq_mksquashfs_compressors])
AC_CONFIG_FILES([tests/ll-smoke.sh],[chmod +x tests/ll-smoke.sh])
+AC_CONFIG_FILES([tests/ll-smoke-singlethreaded.sh],[chmod +x tests/ll-smoke-singlethreaded.sh])
AC_CONFIG_FILES([tests/umount-test.sh],[chmod +x tests/umount-test.sh])
diff -Nru squashfuse-0.5.0/debian/changelog squashfuse-0.5.2/debian/changelog
--- squashfuse-0.5.0/debian/changelog 2023-11-02 09:42:28.0 +0100
+++ squashfuse-0.5.2/debian/changelog 2024-04-01 23:02:32.0 +0200
@@ -1,3 +1,11 @@
+squashfuse (0.5.2-0.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload
+ * New upstream release
+- Fix pointer types on 32 bit architectures (Closes: #1067010)
+
+ -- Sebastian Ramacher Mon, 01 Apr 2024 23:02:32 +0200
+
squashfuse (0.5.0-2) unstable; urgency=medium
* Fix "needed headers (e.g. config.h) are not shipped"
diff -Nru squashfuse-0.5.0/.github/workflows/ci.yml squashfuse-0.5.2/.github/workflows/ci.yml
--- squashfuse-0.5.0/.github/workflows/ci.yml 2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.github/workflows/ci.yml 2024-02-22 16:19:33.0 +0100
@@ -17,6 +17,8 @@
os: ubuntu-latest
disable_fuse: "--disable-fuse"
check_features: demo
+ - name: distcheck
+os: ubuntu-latest
- name: Old distro
os: ubuntu-20.04
- name: Mac
@@ -29,6 +31,7 @@
uses: actions/checkout@v2
- name: apt dependencies
run: >
+ sudo apt-get update &&
sudo apt-get install -y automake autoconf libtool pkg-config
zlib1g-dev liblzo2-dev liblzma-dev liblz4-dev libzstd-dev
fio
@@ -46,17 +49,20 @@
brew install autoconf automake libtool pkgconfig squashfs coreutils
brew install --cask macfuse
if: runner.os == 'macOS'
- - name: build
+ - name: configure
run: |
./autogen.sh
CPPFLAGS="-Werror" ./configure $DISABLE_FUSE
+ - name: build
+run: |
make -j2 V=1
+if: matrix.name != 'distcheck'
- name: test
run: |
make check
diff -u ci/expected-features/${CHECK_FEATURES:-all} ci/features
-if: runner.os != 'macOS'
- - name: test
+if: runner.os != 'macOS' && matrix.name != 'distcheck'
+ - name: test mac
run: |
# On macOS loading the macfuse extension is needed. This
# command should load it without rebooting, except System
@@ -68,8 +74,13 @@
diff -u ci/expected-features/${CHECK_FEATURES:-all} ci/features
fi
if: runner.os == 'macOS'
+ - name: distcheck
+run: |
+ make distcheck
+if: matrix.name == 'distcheck'
- name: install
run: sudo make install
+if: matrix.name != 'distcheck'
- name: output
run: |
cp /tmp/*.log . || true
diff -Nru squashfuse-0.5.0/.gitignore squashfuse-0.5.2/.gitignore
--- squashfuse-0.5.0/.gitignore 2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/.gitignore 2024-02-22 16:19:33.0 +0100
@@ -33,4 +33,5 @@
ci/features
tests/lib.sh
tests/ll-smoke.sh
+tests/ll-smoke-singlethreaded.sh
tests/umount-test.sh
diff -Nru squashfuse-0.5.0/ll.c squashfuse-0.5.2/ll.c
--- squashfuse-0.5.0/ll.c 2023-09-13 16:50:21.0 +0200
+++ squashfuse-0.5.2/ll.c 2024-02-22 16:19:33.0 +0100
@@ -410,7 +410,12 @@
}
void sqfs_ll_op_forget(fuse_req_t req, fuse_ino_t ino,
- unsigned long nlookup) {
+#ifdef HAVE_FUSE_LL_FORGET_OP_64T
+ uint64_t nlookup
+#else
+ uns
Bug#1068205: gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7
Source: gauche Version: 0.9.14-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=gauche=armhf=0.9.14-2=1711974534=0 gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include `./get-atomic-ops-flags.sh .. .. --cflags` -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 -Wall -Wextra -Wno-unused-label -fPIC -fomit-frame-pointer -c test-extra.c gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include `./get-atomic-ops-flags.sh .. .. --cflags` -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 -Wall -Wextra -Wno-unused-label -fPIC -fomit-frame-pointer -c libextra.c TARGETLIB="`pwd`" gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -Wextra -Wno-unused-label -fPIC -Wl,--rpath="`pwd`" -L. -Wl,-z,relro -rdynamic -o test-extra test-extra.o libextra.o -lgauche-0.98 -lmbedtls -lcrypt -lrt -lm -lpthread make[3]: Leaving directory '/<>/src' make[3]: Entering directory '/<>/lib' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/lib' make[3]: Entering directory '/<>/ext' (cd util; make default) make[4]: Entering directory '/<>/ext/util' "../../src/gosh" -ftest "../../lib/tools/precomp" -e -P -o util--match ../../libsrc/util/match.scm "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7 make[4]: *** [Makefile:26: util--match.c] Error 1 make[4]: Leaving directory '/<>/ext/util' make[3]: *** [Makefile:38: util] Error 2 make[3]: Leaving directory '/<>/ext' make[2]: *** [Makefile:47: all] Error 1 make[2]: Leaving directory '/<>' dh_auto_build: error: make -j1 returned exit code 2 make[1]: *** [debian/rules:23: override_dh_auto_build] Error 255 Cheers -- Sebastian Ramacher
Bug#1068204: pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.
Source: pdl Version: 1:2.086-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=pdl=i386=1%3A2.086-1=1712002199=0 not ok 569 - col=0 not ok 570 - col=1 ... Test Summary Report --- t/pdl_from_string.t (Wstat: 0 Tests: 144 Failed: 0) TODO passed: 60-62 t/primitive-random.t (Wstat: 0 Tests: 3 Failed: 0) TODO passed: 1 t/slice.t(Wstat: 512 (exited 2) Tests: 602 Failed: 2) Failed tests: 569-570 Non-zero exit status: 2 Files=45, Tests=2262, 56 wallclock secs ( 0.48 usr 0.12 sys + 54.74 cusr 5.00 csys = 60.34 CPU) Result: FAIL Failed 1/45 test programs. 2/2262 subtests failed. make[2]: *** [Makefile:1077: test_dynamic] Error 255 Cheers -- Sebastian Ramacher
Bug#1068203: spectrwm: hard-coded dependency on pre-t64 library
Source: spectrwm Version: 3.5.1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org spectrwm builds a packages with a hard-coded dependency on a library package involved in the time_t 64 transition. This dependency needs to be updated. Cheers -- Sebastian Ramacher
Bug#1068202: bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
Source: bazel-bootstrap Version: 4.2.3+ds-9 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=bazel-bootstrap=amd64=4.2.3%2Bds-9%2Bb2=1711976723=0 /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g '-std=c++0x' -Wdate-time '-D_FORTIFY_SOURCE=2' -g -O2 '-ffile-prefix-map=/<>=.' -fstack-protector-strong -fstack-clash-protection -Wformat '-Werror=format-security' -fcf-protection -MD -MF bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.d '-frandom-seed=bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.o' -fPIC '-DGRPC_USE_PROTO_LITE=ON' -iquote . -iquote bazel-out/k8-dbg/bin -iquote external/debian_cc_deps -iquote bazel-out/k8-dbg/bin/external/debian_cc_deps -iquote external/debian_proto_deps -iquote bazel-out/k8-dbg/bin/external/debian_proto_deps -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.cc -o bazel-out/k8-dbg/bin/src/main/protobuf/_objs/command_server_cc_grpc/command_server.grpc.pb.pic.o) Execution platform: //:default_host_platform ␛[32m[256 / 1,677]␛[0m 5 actions running JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 18s local Compiling src/main/cpp/blaze.cc; 3s local @debian_proto_deps//:descriptor_proto; 3s local Compiling src/main/protobuf/command_server.pb.cc; 3s local Compiling src/main/cpp/option_processor.cc; 1s local ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K ␛[1A␛[KIn file included from /usr/include/absl/base/config.h:86, from /usr/include/absl/base/const_init.h:25, from /usr/include/absl/synchronization/mutex.h:67, from /usr/include/grpcpp/impl/codegen/sync.h:32, from /usr/include/grpcpp/client_context.h:46, from /usr/include/grpcpp/impl/call_op_set.h:29, from /usr/include/grpcpp/support/server_callback.h:27, from /usr/include/grpcpp/impl/codegen/server_callback.h:24, from /usr/include/grpcpp/impl/codegen/server_callback_handlers.h:25, from /usr/include/grpcpp/generic/async_generic_service.h:24, from bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.h:31, from bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.cc:6: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." 79 | #error "C++ versions less than C++14 are not supported." | ^ Cheers -- Sebastian Ramacher
Bug#1068194: pcsx2: FTBFS: /<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: ‘system_error’ in namespace ‘std’ does not name a type
Source: pcsx2
Version: 1.6.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=pcsx2=i386=1.6.0%2Bdfsg-2%2Bb10=1711729892=0
[ 7%] Generating ../tr_TR__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet
--update --backup=none -s /<>/locales/tr_TR/pcsx2_Main.po
/<>/locales/templates/pcsx2_Main.pot
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘bool
StartKeepAliveThread()’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error:
‘system_error’ in namespace ‘std’ does not name a type
143 | } catch (std::system_error &) {
| ^~~~
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘s32
CDVDopen(const char*)’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:188:19: error:
‘runtime_error’ in namespace ‘std’ does not name a type
188 | } catch (std::runtime_error ) {
| ^
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:22:1: note:
‘std::runtime_error’ is defined in header ‘’; did you forget to
‘#include ’?
21 | #include "svnrev.h"
+++ |+#include
22 |
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o
/<>/obj-i686-linux-gnu/tr_TR__pcsx2_Main.gmo
/<>/locales/tr_TR/pcsx2_Main.po
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:189:15: error: ‘ex’ was not
declared in this scope
189 | fputs(ex.what(), stdout);
| ^~
[ 8%] Generating ../zh_CN__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet
--update --backup=none -s /<>/locales/zh_CN/pcsx2_Main.po
/<>/locales/templates/pcsx2_Main.pot
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o
/<>/obj-i686-linux-gnu/zh_CN__pcsx2_Main.gmo
/<>/locales/zh_CN/pcsx2_Main.po
[ 8%] Generating ../zh_TW__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet
--update --backup=none -s /<>/locales/zh_TW/pcsx2_Main.po
/<>/locales/templates/pcsx2_Main.pot
make[3]: ***
[plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/build.make:79:
plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/CDVD.cpp.o] Error 1
Cheers
--
Sebastian Ramacher
Bug#1068193: rust-reqwest: please package 0.12
Source: rust-reqwest Version: 0.11.24-1 Severity: wishlist X-Debbugs-Cc: sramac...@debian.org As $subject. rust-drt-tools will require reqest 0.12 with the next release. Cheers -- Sebastian Ramacher
Bug#1059535: transition: abseil
On 2024-04-01 10:39:08 -0400, Benjamin Barenblat wrote: > On Monday, April 1, 2024, at 2:57 PM +0200, Sebastian Ramacher wrote: > > Could you please re-add the build dependency on dpkg-dev (>= 1.22.5) to > > ensure that the build with the new armel/armhf ABI only migrates when > > the time_t transition is ready to advance? > > Yes! I am going to wait for the current upload (20230802.1-3) to finish > building on RISC-V, just to make sure the FTBFS is fixed. (It’s already > 11 hours in; it can’t take too much longer.) Once that’s done, I’ll > upload a new 20230802.1-4 with a Build-Depends: dpkg-dev (>= 1.22.5). > (If you’d prefer that I preempt the current build and upload > 20230802.1-4 right now, just let me know.) Sounds good. Let's wait for -3 to finish building on riscv64. Cheers -- Sebastian Ramacher
Bug#1068190: telegram-desktop: FTBFS with abseil 20230802: (.text+0x270): undefined reference to `absl::debian3::base_internal::ThrowStdOutOfRange(char const*)'
Source: telegram-desktop Version: 4.14.9+ds-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=telegram-desktop=arm64=4.14.9%2Bds-1%2Bb2=1711978921=0 cd /<>/obj-aarch64-linux-gnu/Telegram && /usr/bin/cmake -E cmake_link_script CMakeFiles/Telegram.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -ftemplate-backtrace-limit=0 -Wdate-time -D_FORTIFY_SOURCE=2 -Werror=invalid-pch -Wl,-z,relro -Wl,-z,now -Wno-alloc-size-larger-than -Wno-stringop-overflow -Wno-odr -Wno-inline -pthread -Wl,--as-needed @CMakeFiles/Telegram.dir/objects1.rsp -o ../telegram-desktop liblib_tgcalls_legacy.a liblib_tgcalls.a lib_base/liblib_base.a lib_ui/liblib_ui.a lib_spellcheck/liblib_spellcheck.a lib_webview/liblib_webview.a liblib_tgvoip_bundled.a /usr/lib/aarch64-linux-gnu/libminizip.so liblib_tgcalls.a /usr/lib/aarch64-linux-gnu/libopenal.so /usr/lib/aarch64-linux-gnu/libtg_owt.a /usr/lib/aarch64-linux-gnu/libsrtp2.so /usr/lib/aarch64-linux-gnu/libprotobuf.so /usr/lib/aarch64-linux-gnu/libssl.so /usr/lib/aarch64-linux-gnu/libcrypto.so /usr/lib/aarch64-linux-gnu/libopus.so /usr/lib/aarch64-linux-gnu/libabsl_flags_parse.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_usage.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_usage_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_marshalling.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_reflection.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cord.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_info.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cord_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_functions.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_cordz_handle.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_cord_state.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc32c.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_str_format_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_crc_cpu_detect.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_raw_hash_set.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_hash.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_city.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_low_level_hash.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_hashtablez_sampler.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_exponential_biased.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_config.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_private_handle_accessor.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_commandlineflag_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_flags_program_name.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_bad_optional_access.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_synchronization.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_graphcycles_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_kernel_timeout_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_stacktrace.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_symbolize.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_malloc_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_debugging_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_demangle_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_time.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_strings.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_string_view.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_throw_delegate.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_strings_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_base.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_spinlock_wait.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_int128.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_civil_time.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_time_zone.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_bad_variant_access.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_raw_logging_internal.so.20230802.0.1 /usr/lib/aarch64-linux-gnu/libabsl_log_severity.so.20230802.0.1 -Wl,--push-state,--as-needed -latomic -Wl,--pop-state /usr/lib/aarch64-linux-gnu/libvpx.so /usr/lib/aarch64-linux-gnu/libm.so /usr/lib/aarch64-linux-gnu/libyuv.so /usr/lib/aarch64-linux-gnu/libX11.so /usr/lib/aarch64-linux-gnu/libXcomposite.so /usr/lib/aarch64-linux-gnu/libXdamage.so /usr/lib/aarch64-linux-gnu/libXext.so /usr/lib/aarch64-linux-gnu/libXfixes.so
Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared
Source: mozc
Version: 2.28.4715.102+dfsg-2.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=mozc=amd64=2.28.4715.102%2Bdfsg-2.2%2Bb5=1711976888=0
[57/144] /usr/bin/g++ -MMD -MF obj/base/base_core.init_mozc.o.d -DOS_LINUX
-DMOZC_BUILD -DCHANNEL_DEV -DENABLE_GTK_RENDERER
'-DMOZC_SERVER_DIR="/usr/lib/mozc"'
'-DMOZC_DOCUMENT_DIR="/usr/lib/mozc/documents"' -DNDEBUG -DQT_NO_DEBUG
-DMOZC_NO_LOGGING -DIGNORE_HELP_FLAG -DIGNORE_INVALID_FLAG
'-I/<>/src' -Igen -I../../third_party/abseil-cpp -Igen/proto_out
-fmessage-length=0 -fno-strict-aliasing -funsigned-char -pipe -pthread
-fno-omit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -Wall
-Wno-char-subscripts -Wno-sign-compare -Wno-deprecated-declarations
-Wwrite-strings -Wno-unknown-warning-option -Wno-inconsistent-missing-override
-fPIC -fno-exceptions -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated -c ../../base/init_mozc.cc -o
obj/base/base_core.init_mozc.o
FAILED: obj/base/base_core.init_mozc.o
/usr/bin/g++ -MMD -MF obj/base/base_core.init_mozc.o.d -DOS_LINUX -DMOZC_BUILD
-DCHANNEL_DEV -DENABLE_GTK_RENDERER '-DMOZC_SERVER_DIR="/usr/lib/mozc"'
'-DMOZC_DOCUMENT_DIR="/usr/lib/mozc/documents"' -DNDEBUG -DQT_NO_DEBUG
-DMOZC_NO_LOGGING -DIGNORE_HELP_FLAG -DIGNORE_INVALID_FLAG
'-I/<>/src' -Igen -I../../third_party/abseil-cpp -Igen/proto_out
-fmessage-length=0 -fno-strict-aliasing -funsigned-char -pipe -pthread
-fno-omit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -Wall
-Wno-char-subscripts -Wno-sign-compare -Wno-deprecated-declarations
-Wwrite-strings -Wno-unknown-warning-option -Wno-inconsistent-missing-override
-fPIC -fno-exceptions -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated -c ../../base/init_mozc.cc -o
obj/base/base_core.init_mozc.o
../../base/init_mozc.cc: In function ‘void
mozc::{anonymous}::ParseCommandLineFlags(int, char**)’:
../../base/init_mozc.cc:90:29: error:
‘absl::debian5::flags_internal::ArgvListAction’ has not been declared
90 | absl::flags_internal::ArgvListAction::kRemoveParsedArgs,
| ^~
Cheers
--
Sebastian Ramacher
Bug#1068185: llvm-toolchain-16: FTBFS on armel: cxa_guard.cpp:(.text.unlikely.__cxa_guard_acquire+0xc): undefined reference to `__atomic_load_1'
bi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_stdexcept.cpp.o: in function `std::logic_error::~logic_error()': stdlib_stdexcept.cpp:(.text._ZNSt11logic_errorD2Ev+0x28): undefined reference to `__atomic_fetch_add_4' /usr/bin/arm-linux-gnueabi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_stdexcept.cpp.o: in function `std::runtime_error::~runtime_error()': stdlib_stdexcept.cpp:(.text._ZNSt13runtime_errorD2Ev+0x28): undefined reference to `__atomic_fetch_add_4' /usr/bin/arm-linux-gnueabi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception.cpp.o: in function `__cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Control_Block*)': cxa_exception.cpp:(.text._ZN10__cxxabiv1L22exception_cleanup_funcE19_Unwind_Reason_CodeP21_Unwind_Control_Block+0x1c): undefined reference to `__atomic_fetch_add_4' /usr/bin/arm-linux-gnueabi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception.cpp.o: in function `__cxa_end_catch': cxa_exception.cpp:(.text.__cxa_end_catch+0xe8): undefined reference to `__atomic_fetch_add_4' /usr/bin/arm-linux-gnueabi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception.cpp.o: in function `__cxa_decrement_exception_refcount': cxa_exception.cpp:(.text.__cxa_decrement_exception_refcount+0x1c): undefined reference to `__atomic_fetch_add_4' /usr/bin/arm-linux-gnueabi-ld: libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception.cpp.o:cxa_exception.cpp:(.text.__cxa_increment_exception_refcount+0x14): more undefined references to `__atomic_fetch_add_4' follow clang++: error: linker command failed with exit code 1 (use -v to see invocation) Cheers -- Sebastian Ramacher
Bug#1059535: transition: abseil
On 2024-03-29 17:27:58 -0400, Benjamin Barenblat wrote: > On Friday, March 29, 2024, at 1:02 PM +0100, Sebastian Ramacher wrote: > > Since the version in unstable fails to build on armel and armhf and > > blocks the time_t transition, but the version in experimental builds > > fine, let's do this transition now. > > > > With the upload to unstable, please check the FTBFS issue on risc64, > > though. > > Sounds good. I never did get around to uploading 20240116 to > experimental. I’ll upload 20230802 to unstable this weekend, and I’ll > come back for 20240116 later. Thanks! Could you please re-add the build dependency on dpkg-dev (>= 1.22.5) to ensure that the build with the new armel/armhf ABI only migrates when the time_t transition is ready to advance? Cheers -- Sebastian Ramacher
Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Control: affects -1 src:polymake On 2024-04-01 08:46:44 -0300, David Bremner wrote: > Control: reassign -1 flint > > Sebastian Ramacher writes: > > > Source: polymake > > Version: 4.11-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=polymake=amd64=4.11-2%2Bb4=1711743555=0 > > As I said the previous two times this bug was reported, as far as I know > this has to be a bug (uncoordinated transition) in flint. Let's make sure that it is visible for polymake then. Otherwise I'll file it a third time ;) Cheers -- Sebastian Ramacher
Bug#1068170: rust-apr: FTBFS: error[E0308]: arguments to this function are incorrect
.1.9/target/aarch64-unknown-linux-gnu/debug/build/apr-31713c0a7d8c7f0e/out/generated.rs:3:150377 | 3 | ...eme\n @return The default port for this scheme"] pub fn apr_uri_port_of_scheme (scheme_str : * const :: std :: os :: raw :: c_char) ->... | ^^ For more information about this error, try `rustc --explain E0308`. error: could not compile `apr` due to 15 previous errors Caused by: process didn't exit successfully: `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=apr CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Jelmer Vernooij ' CARGO_PKG_DESCRIPTION='Rust bindings for Apache Portable Runtime' CARGO_PKG_HOMEPAGE='https://github.com/jelmer/apr-rs' CARGO_PKG_LICENSE=Apache-2.0 CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=apr CARGO_PKG_REPOSITORY='https://github.com/jelmer/apr-rs.git' CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.1.9 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=9 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' OUT_DIR=/<>/target/aarch64-unknown-linux-gnu/debug/build/apr-31713c0a7d8c7f0e/out rustc --crate-name apr --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test -C metadata=42f81f2ed7c5c884 -C extra-filename=-42f81f2ed7c5c884 --out-dir /<>/target/aarch64-unknown-linux-gnu/debug/deps --target aarch64-unknown-linux-gnu -C incremental=/<>/target/aarch64-unknown-linux-gnu/debug/incremental -L dependency=/<>/target/aarch64-unknown-linux-gnu/debug/deps -L dependency=/<>/target/debug/deps --extern ctor=/<>/target/debug/deps/libctor-a676964fa629fc80.so -C debuginfo=2 --cap-lints warn -C linker=aarch64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<>=/usr/share/cargo/registry/apr-0.1.9 --remap-path-prefix /<>/debian/cargo_registry=/usr/share/cargo/registry -L native=/usr/lib/aarch64-linux-gnu -l apr-1 -l aprutil-1 -l ldap -l lber -l apr-1 --cfg system_deps_have_apr_1 --cfg system_deps_have_apr_util_1` (exit status: 1) dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 Cheers -- Sebastian Ramacher
Bug#1068160: haskell-gi-glib: FTBFS on mips64el: couldn't find API description for GLib.time_t
Source: haskell-gi-glib
Version: 2.0.29-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=haskell-gi-glib=mips64el=2.0.29-1%2Bb2=1711923103=0
Running debian/hlibrary.setup configure --ghc -v2
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
--builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
--haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.29/ --datasubdir=gi-glib
--htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling
Non-zero exit code 1.
Using Parsec parser
␛[1;91mERROR: ␛[97mcouldn't find API description for GLib.time_t␛[22;94m
Please report this at https://github.com/haskell-gi/haskell-gi/issues␛[0m
CallStack (from HasCallStack):
error, called at lib/Data/GI/CodeGen/Util.hs:126:6 in
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.Util
terror, called at lib/Data/GI/CodeGen/Code.hs:556:13 in
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.Code
findAPIByName, called at lib/Data/GI/CodeGen/GObject.hs:17:44 in
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.GObject
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1
Cheers
--
Sebastian Ramacher
Bug#1068159: openjfx: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
~~^~~ ../../../gstreamer-lite/gstreamer/gst/gst.c: In function ‘init_pre’: ../../../gstreamer-lite/gstreamer/gst/gst.c:563:10: warning: unused variable ‘libdir’ [-Wunused-variable] 563 | gchar *libdir; | ^~ ../../../gstreamer-lite/gstreamer/gst/gst.c:560:28: warning: unused parameter ‘context’ [-Wunused-parameter] 560 | init_pre (GOptionContext * context, GOptionGroup * group, gpointer data, | ~^~~ ../../../gstreamer-lite/gstreamer/gst/gst.c:560:52: warning: unused parameter ‘group’ [-Wunused-parameter] 560 | init_pre (GOptionContext * context, GOptionGroup * group, gpointer data, | ~~~^ ../../../gstreamer-lite/gstreamer/gst/gst.c:560:68: warning: unused parameter ‘data’ [-Wunused-parameter] 560 | init_pre (GOptionContext * context, GOptionGroup * group, gpointer data, | ~^~~~ ../../../gstreamer-lite/gstreamer/gst/gst.c:561:15: warning: unused parameter ‘error’ [-Wunused-parameter] 561 | GError ** error) | ~~^ ../../../gstreamer-lite/gstreamer/gst/gst.c: In function ‘init_post’: ../../../gstreamer-lite/gstreamer/gst/gst.c:668:29: warning: unused parameter ‘context’ [-Wunused-parameter] 668 | init_post (GOptionContext * context, GOptionGroup * group, gpointer data, |~^~~ ../../../gstreamer-lite/gstreamer/gst/gst.c:668:53: warning: unused parameter ‘group’ [-Wunused-parameter] 668 | init_post (GOptionContext * context, GOptionGroup * group, gpointer data, | ~~~^ ../../../gstreamer-lite/gstreamer/gst/gst.c:668:69: warning: unused parameter ‘data’ [-Wunused-parameter] 668 | init_post (GOptionContext * context, GOptionGroup * group, gpointer data, |~^~~~ ../../../gstreamer-lite/gstreamer/gst/gst.c:669:15: warning: unused parameter ‘error’ [-Wunused-parameter] 669 | GError ** error) | ~~^ ../../../gstreamer-lite/gstreamer/gst/gst.c: In function ‘gst_deinit’: ../../../gstreamer-lite/gstreamer/gst/gst.c:1128:47: warning: cast between incompatible function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’ [-Wcast-function-type] 1128 | g_slist_foreach (_priv_gst_preload_plugins, (GFunc) g_free, NULL); | ^ ../../../gstreamer-lite/gstreamer/gst/gst.c:1133:43: warning: cast between incompatible function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’ [-Wcast-function-type] 1133 | g_list_foreach (_priv_gst_plugin_paths, (GFunc) g_free, NULL); | ^ make[2]: *** [Makefile:262: /<>/modules/javafx.media/build/native/linux/Release/obj/gstreamer-lite/gstreamer/gst/gst.o] Error 1 :media:buildLinuxGStreamer FAILED :media:buildLinuxGStreamer (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 0.929 secs. FAILURE: Build failed with an exception. Cheers -- Sebastian Ramacher
Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:
Source: python-escript
Version: 5.6-6
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=python-escript=arm64=5.6-6%2Bb3=1711889068=0
mkdir -p /<>/debian/stage3
scons -j4 cc_optim=' -O3 ' build_dir=/<>/debian/tmp3
verbose=on prefix=/<>/debian/stage3
options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.11.8 (main, Mar 26 2024, 12:04:57) [GCC 13.2.0]
RuntimeError: We do not current support different different dpkg-buildflags for
C vs C++:
File "/<>/SConstruct", line 172:
env = Environment(tools = ['default'], options = vars,
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1231:
variables.Update(self)
File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
exec(contents, {}, values)
File "", line 84:
File "/<>/site_scons/extractdebbuild.py", line 61:
raise RuntimeError("We do not current support different different
dpkg-buildflags for C vs C++")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
Cheers
--
Sebastian Ramacher
Bug#1068156: RM: tk707 -- RoQA; unmainained, RC-buggy, dead upstream
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: tk...@packages.debian.org, sramac...@debian.org Control: affects -1 + src:tk707 User: ftp.debian@packages.debian.org Usertags: remove tk707 is orphaned for many years (#831657) and dead upstream (last commit 15 years ago). It also fails to build (#1066230), so please remove it from the archive. Cheers -- Sebastian Ramacher
Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT
Source: siridb-server Version: 2.0.51-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=siridb-server=2.0.51-2%2Bb3=armhf=1711922161 Testing expr␛[32mOK␛[0m (8.519 ms) ==3276877== ==3276877== Process terminating with default action of signal 11 (SIGSEGV) ==3276877== Access not within mapped region at address 0xFEC4F704 ==3276877==at 0x495F6F0: pcre2_compile_8 (in /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2) ==3276877== If you believe this happened as a result of a stack ==3276877== overflow in your program's main thread (unlikely but ==3276877== possible), you can try to increase the size of the ==3276877== main thread stack using the --main-stacksize= flag. ==3276877== The main thread stack size used in this run was 8388608. ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT Cheers -- Sebastian Ramacher
Bug#1056893: uvloop: diff for NMU version 0.19.0+ds1-2.1
Control: tags 1056893 + pending
Dear maintainer,
I've prepared an NMU for uvloop (versioned as 0.19.0+ds1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru uvloop-0.19.0+ds1/debian/changelog uvloop-0.19.0+ds1/debian/changelog
--- uvloop-0.19.0+ds1/debian/changelog 2023-11-16 13:16:10.0 +0100
+++ uvloop-0.19.0+ds1/debian/changelog 2024-03-31 23:47:16.0 +0200
@@ -1,3 +1,14 @@
+uvloop (0.19.0+ds1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+
+ [ Graham Inggs ]
+ * Include proposed patch for compatibility with Cython 3 (Closes: #1056893)
+(LP: #2051150)
+ * Skip tests failing with libuv 1.48.0
+
+ -- Sebastian Ramacher Sun, 31 Mar 2024 23:47:16 +0200
+
uvloop (0.19.0+ds1-2) unstable; urgency=medium
* Add 0003-Fix-unit-tests-on-IPv6-only-hosts patch. Thanks to Dale Richards!
diff -Nru uvloop-0.19.0+ds1/debian/patches/cython3.patch uvloop-0.19.0+ds1/debian/patches/cython3.patch
--- uvloop-0.19.0+ds1/debian/patches/cython3.patch 1970-01-01 01:00:00.0 +0100
+++ uvloop-0.19.0+ds1/debian/patches/cython3.patch 2024-03-26 18:29:47.0 +0100
@@ -0,0 +1,556 @@
+Description: Updates for Cython3
+ Remove SSL depreciation warnings
+Forwarded: https://github.com/MagicStack/uvloop/pull/587
+Author: Alan Brooks <12380017+alan-bro...@users.noreply.github.com>
+Last-Update: 2023-12-28
+
+--- a/Makefile
b/Makefile
+@@ -9,7 +9,7 @@
+
+
+ clean:
+- rm -fr dist/ doc/_build/ *.egg-info uvloop/loop.*.pyd
++ rm -fr dist/ doc/_build/ *.egg-info uvloop/loop.*.pyd uvloop/loop_d.*.pyd
+ rm -fr uvloop/*.c uvloop/*.html uvloop/*.so
+ rm -fr uvloop/handles/*.html uvloop/includes/*.html
+ find . -name '__pycache__' | xargs rm -rf
+--- a/setup.py
b/setup.py
+@@ -144,7 +144,9 @@
+ self.distribution.ext_modules[:] = cythonize(
+ self.distribution.ext_modules,
+ compiler_directives=directives,
+-annotate=self.cython_annotate)
++annotate=self.cython_annotate,
++compile_time_env=dict(DEFAULT_FREELIST_SIZE=250, SSL_READ_MAX_SIZE=256 * 1024),
++emit_linenums=True)
+
+ super().finalize_options()
+
+--- a/tests/test_process.py
b/tests/test_process.py
+@@ -912,7 +912,7 @@
+ stdin=subprocess.PIPE,
+ stdout=subprocess.PIPE,
+ stderr=subprocess.PIPE,
+-__uvloop_sleep_after_fork=True))
++uvloop_sleep_after_fork=True))
+ self.assertIsNot(transport, None)
+ self.assertEqual(transport.get_returncode(), 0)
+ self.assertEqual(
+@@ -931,7 +931,7 @@
+ stdin=None,
+ stdout=subprocess.PIPE,
+ stderr=subprocess.PIPE,
+-__uvloop_sleep_after_fork=True))
++uvloop_sleep_after_fork=True))
+ self.assertIsNot(transport, None)
+ self.assertEqual(transport.get_returncode(), 0)
+ self.assertEqual(
+--- a/tests/test_tcp.py
b/tests/test_tcp.py
+@@ -1630,17 +1630,22 @@
+ self.fail("unexpected call to connection_made()")
+
+ def test_ssl_connect_accepted_socket(self):
+-if hasattr(ssl, 'PROTOCOL_TLS'):
+-proto = ssl.PROTOCOL_TLS
++if hasattr(ssl, 'PROTOCOL_TLS_SERVER'):
++server_proto = ssl.PROTOCOL_TLS_SERVER
++client_proto = ssl.PROTOCOL_TLS_CLIENT
+ else:
+-proto = ssl.PROTOCOL_SSLv23
+-server_context = ssl.SSLContext(proto)
++if hasattr(ssl, 'PROTOCOL_TLS'):
++client_proto = server_proto = ssl.PROTOCOL_TLS
++else:
++client_proto = server_proto = ssl.PROTOCOL_SSLv23
++
++server_context = ssl.SSLContext(server_proto)
+ server_context.load_cert_chain(self.ONLYCERT, self.ONLYKEY)
+ if hasattr(server_context, 'check_hostname'):
+ server_context.check_hostname = False
+ server_context.verify_mode = ssl.CERT_NONE
+
+-client_context = ssl.SSLContext(proto)
++client_context = ssl.SSLContext(client_proto)
+ if hasattr(server_context, 'check_hostname'):
+ client_context.check_hostname = False
+ client_context.verify_mode = ssl.CERT_NONE
+@@ -2233,7 +2238,7 @@
+ sslctx.use_privatekey_file(self.ONLYKEY)
+ sslctx.use_certificate_chain_file(self.ONLYCERT)
+ client_sslctx = self._create_client_ssl_context()
+-if hasattr(ssl, 'OP_NO_TLSv1_3'):
++if sys.version_info < (3, 8) and hasattr(ssl, 'OP_NO_TLSv1_3'):
+ client_sslctx.options |= ssl.OP_NO_TLSv1_3
+
+ def server(sock):
+@@ -2592,7 +2597,7 @@
+ sslctx_openssl.use_privatekey_file(self.ONLYKEY)
+ sslctx_openssl.use_certificate_chain_file(self.ONLYCERT)
+ client_sslctx = self._create_client_ssl_context()
+-
Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)
Source: lmms Version: 1.2.2+dfsg1-6 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=lmms=i386=1.2.2%2Bdfsg1-6%2Bb3=1711724261=0 -- Installing: /<>/debian/tmp/usr/share/lmms/wavetables/tri.bin Installing bash completion... Bash completion for lmms has been installed to /<>/debian/tmp/usr/share/bash-completion/completions/lmms make[1]: Leaving directory '/<>/obj-i686-linux-gnu' dh_install -a dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) dh_install: warning: lmms-vst-server missing files: usr/lib/*/lmms/libvestige.so dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvst*" (tried in ., debian/tmp) dh_install: warning: lmms-vst-server missing files: usr/lib/*/lmms/libvst* dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/RemoteVstPlugin*" (tried in ., debian/tmp) dh_install: warning: lmms-vst-server missing files: usr/lib/*/lmms/RemoteVstPlugin* dh_install: error: missing files, aborting Cheers -- Sebastian Ramacher
Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Source: polymake Version: 4.11-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=polymake=amd64=4.11-2%2Bb4=1711743555=0 dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11) Hint: check if the library actually comes from a package. dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libpolymake4.11.substvars debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps.so.4.11 debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps-rt.so.4.11 debian/libpolymake4.11/usr/lib/libpolymake.so.4.11 returned exit code 25 dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/polymake/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so) Hint: check if the library actually comes from a package. dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/polymake.substvars debian/polymake/usr/lib/polymake/lib/tropical.so debian/polymake/usr/lib/polymake/lib/topaz.so debian/polymake/usr/lib/polymake/lib/polytope.so debian/polymake/usr/lib/polymake/lib/matroid.so debian/polymake/usr/lib/polymake/lib/ideal.so debian/polymake/usr/lib/polymake/lib/group.so debian/polymake/usr/lib/polymake/lib/graph.so debian/polymake/usr/lib/polymake/lib/fulton.so debian/polymake/usr/lib/polymake/lib/fan.so debian/polymake/usr/lib/polymake/lib/common.so debian/polymake/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so returned exit code 25 dh_shlibdeps: error: Aborting due to earlier error make: *** [debian/rules:35: binary-arch] Error 25 Cheers -- Sebastian Ramacher
Bug#1068138: halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed)
Source: halide Version: 17.0.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=halide=amd64=17.0.1-1%2Bb2=1711572233=0 The following tests FAILED: 676 - python_correctness_atomics (Failed) 677 - python_correctness_autodiff (Failed) Errors while running CTest make[2]: *** [debian/rules:118: perform_stage_build] Error 8 Cheers -- Sebastian Ramacher
Bug#1068135: gtk-sharp3: arch:all package depends on pre-t64 library
Source: gtk-sharp3 Version: 2.99.3-4.1 Severity: serious X-Debbugs-Cc: sramac...@debian.org gtk-sharp3 builds an Architecture: all packages depending on a library package involved in the time_t 64 transition. This dependency needs to be updated. Cheers -- Sebastian Ramacher
Bug#1068134: globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library
Source: globus-gram-job-manager-scripts Version: 7.3-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org globus-gram-job-manager-scripts builds an Architecture: all packages depending on a library package involved in the time_t 64 transition. This dependency needs to be updated. Cheers -- Sebastian Ramacher
Bug#1068133: globus-gram-audit: arch:all package depends on pre-t64 library
Source: globus-gram-audit Version: 5.1-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org globus-gram-audit builds an Architecture: all packages depending on a library package involved in the time_t 64 transition. This dependency needs to be updated. Cheers -- Sebastian Ramacher
Bug#1068121: python-fusepy: hard-coded dependencies on pre-t64 libraries
Source: python-fusepy Version: 3.0.1-4 Severity: serious X-Debbugs-Cc: sramac...@debian.org python-fusepy builds binary packages with hardcoded dependencies on shared library packages that were renamed as part of the time_t 64 transition. The dependencies need to be updated for this change - or if possible - changed to be generated by debhelper. There's a patch available from Ubuntu: https://patches.ubuntu.com/p/python-fusepy/python-fusepy_3.0.1-4ubuntu1.patch Cheers -- Sebastian Ramacher
Bug#1068120: mergerfs: builds binary packages with hardcoded dependencies on pre-t64 libraries
Source: mergerfs Version: 2.33.5-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org mergerfs builds binary packages with hardcoded dependencies on shared library packages that were renamed as part of the time_t 64 transition. The dependencies need to be updated for this change - or if possible - changed to be generated by debhelper. Cheers -- Sebastian Ramacher
Bug#1068119: s390-tools: FTBFS: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [-Werror=array-bounds=]
Source: s390-tools Version: 2.16.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=s390-tools=s390x=2.16.0-2%2Bb4=1711742603=0 gcc -I ../../include -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -fno-pie -Os -g -I../..//zipl/boot -I../..//zipl/include -I../..//include -DENABLE_SCLP_ASCII=1 -DS390_TOOLS_RELEASE=2.16.0-build-20240329 -fno-builtin -ffreestanding -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-stack-protector -fexec-charset=IBM1047 -m64 -mpacked-stack -mstack-size=4096 -mstack-guard=128 -msoft-float -Wall -Wformat-security -Wextra -Werror -c stage3a.c -o stage3a.o In file included from stage3a.c:14: In function ‘__test_facility’, inlined from ‘test_facility’ at ../../include/boot/s390.h:428:9, inlined from ‘start’ at stage3a.c:42:7: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [-Werror=array-bounds=] 418 | return (*ptr & (0x80 >> (nr & 7))) != 0; | ^~~~ In function ‘start’: cc1: note: source object is likely at address zero cc1: all warnings being treated as errors make[4]: *** [../../common.mak:253: stage3a.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1068116: python-pylibdmtx: depends on pre-t64 packages
Source: python-pylibdmtx Version: 0.1.10-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org python3-pylibdtmtx depends on a package that was renamed for the time_t 64 transition. The dependency needs to be updated to the new package name. Cheers -- Sebastian Ramacher
Bug#1068115: tardy: FTBFS on arm{el,hf}: ./tardy/main.cc:282:(.text.startup+0x578): undefined reference to `tardy_mtime(long)'
race.o libtardy/versi_stamp.o libtardy/version.o ranlib libtardy/libtardy.a mkdir bin chmod 0755 bin g++ -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 -o bin/tardy tardy/arglex/tardy.o tardy/ifmt.o tardy/main.o tardy/ofmt.o tardy/tardy.o libtardy/libtardy.a \ -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lexplain -lz /usr/bin/ld: tardy/main.o: in function `main': ./tardy/main.cc:282:(.text.startup+0x578): undefined reference to `tardy_mtime(long)' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:1722: bin/tardy] Error 1 Cheers -- Sebastian Ramacher
Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec
Hi gregor On 2024-03-14 17:36:11 +0100, gregor herrmann wrote: > On Sat, 09 Mar 2024 21:29:26 +0100, Sebastian Ramacher wrote: > > > Source: libauthen-krb5-perl > > Version: 1.9-6 > > 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=libauthen-krb5-perl=armhf=1.9-6%2Bb3=1709893977=0 > > > > Krb5.xs:1040:17: error: implicit declaration of function > > ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? > > [-Werror=implicit-function-declaration] > > 1040 | krb5_free_address(context,addr); > > | ^ > > | krb5_free_addresses > > Not sure there are many chances to fix this (short of disabling > -Werror=implicit-function-declaration). Cf. also in Fedora: > https://src.fedoraproject.org/rpms/perl-Authen-Krb5/commits/rawhide > https://bugzilla.redhat.com/show_bug.cgi?id=2172836 So should it be removed? Cheers -- Sebastian Ramacher
Bug#1059535: transition: abseil
Control: tags -1 confirmed Hi Benjamin On 2024-02-14 21:01:40 +0100, Sebastian Ramacher wrote: > On 2024-02-14 14:48:49 -0500, Benjamin Barenblat wrote: > > I’d like to alter this transition request. Instead of transitioning to > > version 20230802, I’d like to transition to version 20240116, which > > upstream recently released. > > > > Is that okay? If so, I’ll upload 20240116 to experimental and reexamine > > reverse dependencies. If not, please let me know how to proceed; a > > 20230802 -> 20240116 upgrade would require a second transition, and I > > don’t want to create extra work. > > That's okay. There is enough time to prepare a tranistion to 20240116 > until we have finished the time_t transition. Since the version in unstable fails to build on armel and armhf and blocks the time_t transition, but the version in experimental builds fine, let's do this transition now. With the upload to unstable, please check the FTBFS issue on risc64, though. See https://buildd.debian.org/status/fetch.php?pkg=abseil=riscv64=20230802.1-2=1703403912=0 Cheers -- Sebastian Ramacher
Bug#1067943: nmu: qtbase-opensource-src_5.15.10+dfsg-7
Control: reopen -1 On 2024-03-29 12:15:11 +0100, Sebastian Ramacher wrote: > On 2024-03-29 11:17:25 +0100, Bas Couwenberg wrote: > > Package: release.debian.org > > Severity: normal > > X-Debbugs-Cc: qtbase-opensource-...@packages.debian.org > > Control: affects -1 + src:qtbase-opensource-src > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > nmu qtbase-opensource-src_5.15.10+dfsg-7 . armel armhf . unstable . -m > > "Rebuild for time_t" > > Scheduled Ah, no, it was not on my list for the last mass-binNMU. Cheers -- Sebastian Ramacher
Bug#1036884: more trackers
On 2024-03-29 00:39:02 +0500, Andrey Rakhmatullin wrote: > Some additional smaller trackers that apparently didn't have binNMUs: > https://release.debian.org/transitions/html/auto-ogre-1.12.html > https://release.debian.org/transitions/html/auto-ros-ros-comm.html > https://release.debian.org/transitions/html/auto-octomap.html > https://release.debian.org/transitions/html/auto-poppler.html > https://release.debian.org/transitions/html/auto-freerdp2.html Scheduled > Not sure if it's possible to find more of those without checking all > auto-* trackers. I wrote a script to schedule all remaining binNMUs. We then hopefully only have to sort out the remaining FTBFS issues, hardcoded dependencies and Architecture: all binaries. Cheers -- Sebastian Ramacher
Bug#1064726: Should I upload 0ad involved in wxwidgets3.2 migration?
On 2024-03-27 15:51:22 +0100, Ludovic Rousseau wrote: > Hello Debian Release team, > > 0ad has a FTBFS bug #1064726. > I have a new version with the fix ready for upload. > > But when trying to upload I get: > - > $ dupload --to debian-ssh *_source.changes --no > dupload note: no announcement will be sent. > Checking OpenPGP signatures before upload..signatures are ok > Checking Debian transitions... > > Warning: Source package 0ad is part of ongoing transitions: > > <https://release.debian.org/transitions/html/auto-curl> > <https://release.debian.org/transitions/html/auto-libpng1.6> > <https://release.debian.org/transitions/html/auto-wxwidgets3.2> > > If the upload does not solve issues caused by these transitions, then it > might disrupt them by adding delays or entangling them. For more information, > please read: > > <https://wiki.debian.org/Teams/ReleaseTeam/TransitionUploadHook> > > Note: If you are aware of this and do not want to be warned, you can disable > this hook from the configuration file, skip it with --skip-hooks or set the > one-off environment variable DUPLOAD_SKIP_HOOKS, or alternatively you can > reply to the following prompt. > > Continue anyway? (yes/NO) > - > > I see 0ad listed in > https://release.debian.org/transitions/html/auto-wxwidgets3.2.html > Of course the rebuild failed because the FTBFS fix is not yet in unstable. > > Should I upload a new version of 0ad to help the wxwidgets3.2 migration? Yes, please. The upload is necessary to rebuild 0ad for these transitions. Cheers > Should I wait for 0ad to be removed from testing (planned in 5 days)? > > Please Cc: me on reply. > > Thanks > > -- > Dr. Ludovic Rousseau > -- Sebastian Ramacher
Bug#1067830: gri: FTBFS on arm{el,hf}: gr.cc:426:22: error: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’}
Source: gri
Version: 2.12.27-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=gri=armel=2.12.27-1.1%2Bb2=1711504387=0
g++ -DDEFAULT_GRI_DIR=\"/usr/share/gri/2.12.27/\" -DPACKAGE_NAME=\"gri\"
-DPACKAGE_TARNAME=\"gri\" -DPACKAGE_VERSION=\"2.12.27\" -DPACKAGE_STRING=\"gri\
2.12.27\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"gri\"
-DVERSION=\"2.12.27\" -DGRI_IS_BIG_ENDIAN=1 -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_UNISTD_H=1 -DHAVE_LIBNETCDF=1 -DHAVE_LIBREADLINE=1 -DHAVE_ISNAN=1
-DHAVE_ISINF=1 -DHAVE_ACOSH=1 -DHAVE_GETCWD=1 -DHAVE_POPEN=1 -DHAVE_MKSTEMP=1
-DHAVE_TMPNAM=1 -DHAVE_TEMPNAM=1 -DHAVE_GETHOSTNAME=1 -DHAVE_ACCESS=1
-DHAVE_LSTAT=1 -DHAVE_STAT=1 -DHAVE_STRERROR=1 -DHAVE_GETENV=1 -DHAVE_DRAND48=1
-I. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -DCPLUSPLUSNEW -I/usr/include -O2 -c -o gr.o gr.cc
gr.cc: In function ‘void insert_ps_header(FILE*, bool)’:
gr.cc:426:22: error: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long
int*’}
426 | time();
| ^~~~
| |
| long int*
In file included from /usr/include/features.h:490,
from /usr/include/ctype.h:25,
from gr.cc:31:
/usr/include/time.h:86:15: note: initializing argument 1 of ‘time_t
time(time_t*)’
86 | extern time_t __REDIRECT_NTH (time, (time_t *__timer), __time64);
| ^~
gr.cc:427:71: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const
long long int*’}
427 | fprintf(fp, "CreationDate: %s",
asctime(localtime()));
|
^~~~
| |
|
long int*
/usr/include/time.h:141:19: note: initializing argument 1 of ‘tm*
localtime(const time_t*)’
141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
| ^~
make[2]: *** [Makefile:610: gr.o] Error 1
Cheers
--
Sebastian Ramacher
Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Source: nfs-utils
Version: 1:2.6.4-3
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=nfs-utils=armel=1%3A2.6.4-3%2Bb2=1711452552=0
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c xml.c -fPIC -DPIC -o .libs/xml.o
export-cache.c: In function ‘junction_flush_exports_cache’:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
| ~~^ ~~~
| | |
| | time_t {aka
long long int}
| long int
| %lld
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c display.c -o display.o >/dev/null 2>&1
cc1: some warnings being treated as errors
make[3]: *** [Makefile:489: export-cache.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
Cheers
--
Sebastian Ramacher
Bug#1067828: tlog: FTBFS on arm{el,hf}: FAIL: 3
^ ^
^^^ ^^ ^^^
^^^ ^^^
^
result hex:
7b 22 76 65 72 22 3a 22 32 2e 33 22 2c 22 68 6f
73 74 22 3a 22 6c 6f 63 61 6c 68 6f 73 74 22 2c
22 72 65 63 22 3a 22 72 65 63 2d 31 22 2c 22 75
73 65 72 22 3a 22 75 73 65 72 22 2c 22 74 65 72
6d 22 3a 22 78 74 65 72 6d 22 2c 22 73 65 73 73
69 6f 6e 22 3a 31 2c 22 69 64 22 3a 31 2c 22 70
6f 73 22 3a 30 2c 22 74 69 6d 65 22 3a 30 2e 30
30 30 2c 22 74 69 6d 69 6e 67 22 3a 22 !22 !2c !22
!69 !6e !5f !74 !78 !74 !22 !3a !22 !28 !6e !75 !6c !6c !29 !22
!2c !22 !69 !6e !5f !62 !69 !6e !22 !3a !5b !28 !6e !75 !6c !6c
!29 !5d !2c !22 !6f !75 !74 !5f !74 !78 !74 !22 !3a !22 !28 !6e
!75 !6c !6c !29 !22 !2c !22 !6f !75 !74 !5f !62 69 6e !22 !3a
!5b !28 !6e !75 !6c !6c !29 !5d !7d !0a !7b !22 !76 !65 !72 !22
!3a !22 !32 !2e !33 !22 !2c !22 !68 !6f !73 !74 !22 !3a 22 !6c
!6f !63 !61 !6c !68 !6f !73 !74 22 !2c !22 !72 !65 !63 !22 !3a
!22 !72 !65 !63 !2d !31 !22 !2c !22 !75 !73 !65 !72 !22 !3a !22
!75 !73 !65 !72 !22 !2c !22 !74 !65 !72 !6d !22 !3a !22 !78 !74
65 !72 !6d !22 !2c !22 !73 !65 !73 !73 !69 !6f !6e !22 !3a !31
!2c 22 !69 !64 !22 !3a !32 !2c 22 !70 !6f !73 !22 !3a !30 !2c
!22 !74 !69 !6d 65 !22 !3a !30 !2e !30 !30 !30 !2c !22 !74 !69
!6d !69 !6e !67 !22 !3a !22 !22 !2c !22 !69 !6e !5f !74 !78 !74
22 3a !22 !28 !6e !75 !6c !6c !29 22 !2c !22 !69 !6e !5f !62
!69 !6e !22 !3a !5b !28 6e !75 !6c !6c !29 !5d !2c !22 !6f !75
!74 !5f !74 !78 !74 !22 !3a !22 !28 !6e !75 !6c !6c !29 !22 !2c
!22 !6f !75 !74 !5f !62 !69 !6e !22 !3a !5b !28 !6e !75 !6c !6c
!29 !5d !7d !0a ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! ! !
FAIL tltest-json-sink.c:161 window_chunk_overflow
window_merging: output mismatch:
expected str:
{"ver":"2.3","host":"localhost","rec":"rec-1","user":"user","term":"xterm","session":1,"id":1,"pos":0,"time":0.000,"timing":"=100x100+2=200x200","in_txt":"","in_bin":[],"out_txt":"","out_bin":[]}
^^ ^^^
^^ ^
expected hex:
7b 22 76 65 72 22 3a 22 32 2e 33 22 2c 22 68 6f
73 74 22 3a 22 6c 6f 63 61 6c 68 6f 73 74 22 2c
22 72 65 63 22 3a 22 72 65 63 2d 31 22 2c 22 75
73 65 72 22 3a 22 75 73 65 72 22 2c 22 74 65 72
6d 22 3a 22 78 74 65 72 6d 22 2c 22 73 65 73 73
69 6f 6e 22 3a 31 2c 22 69 64 22 3a 31 2c 22 70
6f 73 22 3a 30 2c 22 74 69 6d 65 22 3a 30 2e 30
30 30 2c 22 74 69 6d 69 6e 67 22 3a 22 !3d !31 !30
!30 !78 !31 !30 !30 !2b !32 !3d !32 !30 !30 !78 !32 !30 !30 22
2c 22 69 6e 5f !74 !78 !74 22 3a !22 !22 !2c !22 !69 !6e
!5f !62 !69 !6e !22 !3a !5b !5d !2c !22 !6f !75 !74 !5f !74 !78
!74 !22 !3a !22 22 2c 22 6f 75 74 5f 62 69 6e 22 3a
5b !5d !7d !0a ! ! ! ! ! !
result str:
{"ver":"2.3","host":"localhost","rec":"rec-1","user":"user","term":"xterm","session":1,"id":1,"pos":0,"time":0.000,"timing":"","in_txt":"(null)","in_bin":[(null)],"out_txt":"(null)","out_bin":[(null)]}
^^ ^^^
^^ ^
result hex:
7b 22 76 65 72 22 3a 22 32 2e 33 22 2c 22 68 6f
73 74 22 3a 22 6c 6f 63 61 6c 68 6f 73 74 22 2c
22 72 65 63 22 3a 22 72 65 63 2d 31 22 2c 22 75
73 65 72 22 3a 22 75 73 65 72 22 2c 22 74 65 72
6d 22 3a 22 78 74 65 72 6d 22 2c 22 73 65 73 73
69 6f 6e 22 3a 31 2c 22 69 64 22 3a 31 2c 22 70
6f 73 22 3a 30 2c 22 74 69 6d 65 22 3a 30 2e 30
30 30 2c 22 74 69 6d 69 6e 67 22 3a 22 !22 !2c !22
!69 !6e !5f !74 !78 !74 !22 !3a !22 !28 !6e !75 !6c !6c !29 22
2c 22 69 6e 5f !62 !69 !6e 22 3a !5b !28 !6e !75 !6c !6c
!29 !5d !2c !22 !6f !75 !74 !5f !74 !78 !74 !22 !3a !22 !28 !6e
!75 !6c !6c !29 22 2c 22 6f 75 74 5f 62 69 6e 22 3a
5b !28 !6e !75 !6c !6c !29 !5d !7d !0a
FAIL tltest-json-sink.c:185 window_merging
window_not_merging: output mismatch:
expected str:
{"ver":"2.3","host":"localhost","rec":"rec-1","user":"user","term":"xterm","session":1,"id":1,"pos":0,"time":0.000,"timing":"=100x100+1=200x200+1=100x100","in_txt":"","in_bin":[],"out_txt":"","out_bin":[]}
^
^^^
expected hex:
7b 22 76 65 72 22 3a 22 32 2e 33 22 2c 22 68 6f
73 74 22 3a 22 6c 6f 63 61 6c 68 6f 73 74 22 2c
22 72 65 63 22 3a 22 72 65 63 2d 31 22 2c 22 75
73 65 72 22 3a 22 75 73 65 72 22 2c 22 74 65 72
6d 22 3a 22 78 74 65 72 6d 22 2c 22 73 65 73 73
69 6f 6e 22 3a 31 2c 22 69 64 22 3a 31 2c 22 70
6f 73 22 3a 30 2c 22 74 69 6d 65 22 3a 30 2e 30
30 30 2c 22 74 69 6d 69 6e 67 22 3a 22 !3d !31 !30
!30 !78 !31 !30 !30 !2b !31 !3d !32 !30 !30 !78 !32 !30 !30 !2b
!31 !3d !31 !30 !30 !78 !31 !30 !30 !22 !2c !22 !69 !6e !5f !74
!78 !74 !22 !3a !22 !22 !2c !22 !69 !6e !5f !62 !69 !6e !22 !3a
!5b !5d !2c !22 !6f !75 !74 !5f !74 !78 !74 !22 !3a !22 22 !2c
!22 !6f !75 !74 !5f !62 !69 !6e !22 !3a !5b !5d !7d !0a
result str:
{"ver":"2.3","host":"localhost","rec":"rec-1","user":"user","term":"xterm","session":1,"id":1,"pos":0,"time":0.000,"timing":"","in_txt":"(null)","in_bin":[(null)],"out_txt":"(null)","out_bin":[(null)]}
^
^^^
result hex:
7b 22 76 65 72 22 3a 22 32 2e 33 22 2c 22 68 6f
73 74 22 3a 22 6c 6f 63 61 6c 68 6f 73 74 22 2c
22 72 65 63 22 3a 22 72 65 63 2d 31 22 2c 22 75
73 65 72 22 3a 22 75 73 65 72 22 2c 22 74 65 72
6d 22 3a 22 78 74 65 72 6d 22 2c 22 73 65 73 73
69 6f 6e 22 3a 31 2c 22 69 64 22 3a 31 2c 22 70
6f 73 22 3a 30 2c 22 74 69 6d 65 22 3a 30 2e 30
30 30 2c 22 74 69 6d 69 6e 67 22 3a 22 !22 !2c !22
!69 !6e !5f !74 !78 !74 !22 !3a !22 !28 !6e !75 !6c !6c !29 !22
!2c !22 !69 !6e !5f !62 !69 !6e !22 !3a !5b !28 !6e !75 !6c !6c
!29 !5d !2c !22 !6f !75 !74 !5f !74 !78 !74 !22 !3a !22 !28 !6e
!75 !6c !6c !29 !22 !2c !22 !6f !75 !74 !5f !62 !69 !6e 22 !3a
!5b !28 !6e !75 !6c !6c !29 !5d !7d !0a ! ! ! !
FAIL tltest-json-sink.c:196 window_not_merging
FAIL tltest-json-sink (exit status: 139)
FAIL: tltest-timespec
=
Cheers
--
Sebastian Ramacher
Bug#1067827: nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate memory
Multimedia -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtQml -isystem /usr/include/arm-linux-gnueabihf/qt5/QtQuickControls2 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtQuick -isystem /usr/include/arm-linux-gnueabihf/qt5/QtQmlModels -isystem /usr/include/arm-linux-gnueabihf/qt5/QtQuickWidgets -isystem /usr/include/gstreamer-1.0 -isystem /usr/include/glib-2.0 -isystem /usr/lib/arm-linux-gnueabihf/glib-2.0/include -isystem /usr/include/orc-0.4 -isystem /usr/include/libmount -isystem /usr/include/blkid -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -pedantic -fsized-deallocation-Wunreachable-code -Wno-attributes -O2 -g -DNDEBUG -std=gnu++20 -fPIE -fPIC -DCPPHTTPLIB_OPENSSL_SUPPORT -DCPPHTTPLIB_ZLIB_SUPPORT -DCPPHTTPLIB_BROTLI_SUPPORT -pthread -Winvalid-pch -include "/<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx" -MD -MT CMakeFiles/nheko.dir/src/ui/UIA.cpp.o -MF CMakeFiles/nheko.dir/src/ui/UIA.cpp.o.d -o CMakeFiles/nheko.dir/src/ui/UIA.cpp.o -c "/<>/src/ui/UIA.cpp" virtual memory exhausted: Cannot allocate memory make[4]: *** [CMakeFiles/nheko.dir/build.make:558: CMakeFiles/nheko.dir/src/timeline/EventStore.cpp.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1067825: dub: FTBFS on armhf, mips64el, ppc64el
Source: dub Version: 1.36.0-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=dub=armhf=1.36.0-1=1708295658=0 /usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: scope variable ‘this’ assigned to non-scope parameter ‘e’ calling ‘put’ 258 | put(writer, trailing[0 .. i]); | ^ source/dub/internal/configy/Exceptions.d:335:31: warning: ‘@safe’ function ‘formatMessage’ calling ‘formattedWrite’ [-Wdeprecated] 335 | formattedWrite(sink, fmt, this.fieldNames.length, this.fieldNames); | ^ /usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/write.d:537:34: note: which calls ‘std.format.spec.FormatSpec!char.FormatSpec.writeUpToNextSpec!(void delegate(in char[]) @safe).writeUpToNextSpec’ 537 | while (spec.writeUpToNextSpec(w)) | ^ /usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: which would be ‘@system’ because of: 258 | put(writer, trailing[0 .. i]); | ^ /usr/lib/gcc/arm-linux-gnueabihf/13/include/d/std/format/spec.d:258:33: note: scope variable ‘this’ assigned to non-scope parameter ‘e’ calling ‘put’ 258 | put(writer, trailing[0 .. i]); | ^ virtual memory exhausted: Cannot allocate memory make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1 https://buildd.debian.org/status/fetch.php?pkg=dub=mips64el=1.36.0-1=1708295519=0 gdmd -run /<>/build.d \ -g -O -wi -release Wrote version_.d` file with version: 1.36.0-1 No compiler has been found in the PATH. Attempted values: ["dmd", "ldmd2", "gdmd"] Make sure one of those is in the PATH, or set the `DMD` variable make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1 https://buildd.debian.org/status/fetch.php?pkg=dub=ppc64el=1.36.0-1=1708295464=0 gdmd -run /<>/build.d \ -g -O -wi -release /<>/build.d:23:8: error: unable to read module ‘algorithm’ 23 | import std.algorithm; |^ /<>/build.d:23:8: note: Expected 'std/algorithm.d' or 'std/algorithm/package.d' in one of the following import paths: 23 | import std.algorithm; |^ import path[0] = /usr/lib/gcc/powerpc64le-linux-gnu/13/include/d make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1 Cheers -- Sebastian Ramacher
Bug#1036884: libgpgme11t64 binNMUs
On 2024-03-26 20:30:12 +0500, Andrey Rakhmatullin wrote: > The next good target for binNMUs that wasn't done yet (AFAICS) is > https://release.debian.org/transitions/html/auto-gpgme1.0.html Scheduled Cheers -- Sebastian Ramacher
Bug#1036884: transition: time64_t -> sphinxbase
On 2024-03-26 13:56:26 +, Simon McVittie wrote: > I think binNMUs for packages involved in > https://release.debian.org/transitions/html/auto-sphinxbase.html > would be useful. If I'm reading correctly, that would unblock ffmpeg > on armel/armhf (or at least get some way towards it), and ffmpeg is > involved in a bunch of other sub-transitions. Scheduled, thanks. > (I hope this is an OK format to make suggestions in?) Yes, it is. Cheers -- Sebastian Ramacher
Bug#1065308: RM: libtirpc-common [all] -- ROP; decruft for debootstrap installability
Hi Samuel On 2024-03-02 14:36:13 +0100, Samuel Thibault wrote: > Package: ftp.debian.org > Severity: normal > X-Debbugs-Cc: libti...@packages.debian.org > Control: affects -1 + src:libtirpc > User: ftp.debian@packages.debian.org > Usertags: remove > > Hello, > > Sorry I wasn't sure how to specify it exactly, but basically, could you > please remove > > libtirpc-common_1.3.4+ds-1 from unstable for arch:all > > ? (now that libtirpc 1.3.4+ds-1.1 was built for all archs) > > Currently debootstrap fails to create a chroot for various reasons, one > of which being that we currently have both libtirpc-common_1.3.4+ds-1 > and libtirpc-common_1.3.4+ds-1.1 in unstable, and debootstrap isn't > smart enough to determine that it's the latter that it should install, > since libtirpc3t64_1.3.4+ds-1.1 depends on that one. Unfortunately > debootstrap ends up choosing to install libtirpc-common_1.3.4+ds-1, and > when libtirpc3t64_1.3.4+ds-1.1 is being configured we end up with > > dpkg: dependency problems prevent configuration of libtirpc3t64:hurd-i386: > libtirpc3t64:hurd-i386 depends on libtirpc-common (>= 1.3.4+ds-1.1); however: > Version of libtirpc-common on system is 1.3.4+ds-1. > > (here on hurd-i386, but other archs will have the same issue) FWIW, the implementation of this removal also removed libtirp-common 1.3.4+ds-1.1 from the archive. I have uploaded -1.2 without any changes to reintroduce the package and make libirpc3t64 installable again. Cheers -- Sebastian Ramacher
Bug#1066277: accountsservice: diff for NMU version 23.13.9-6.1
Control: tags 1066277 + patch
Dear maintainer,
I've prepared an NMU for accountsservice (versioned as 23.13.9-6.1). The diff
is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru accountsservice-23.13.9/debian/changelog accountsservice-23.13.9/debian/changelog
--- accountsservice-23.13.9/debian/changelog 2024-01-31 12:30:27.0 +0100
+++ accountsservice-23.13.9/debian/changelog 2024-03-25 22:57:03.0 +0100
@@ -1,3 +1,11 @@
+accountsservice (23.13.9-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Fix implicit function declarations in mocklibc. (Closes:
+#1066277)
+
+ -- Sebastian Ramacher Mon, 25 Mar 2024 22:57:03 +0100
+
accountsservice (23.13.9-6) unstable; urgency=medium
* Team upload
diff -Nru accountsservice-23.13.9/debian/patches/implicit-funcs.patch accountsservice-23.13.9/debian/patches/implicit-funcs.patch
--- accountsservice-23.13.9/debian/patches/implicit-funcs.patch 1970-01-01 01:00:00.0 +0100
+++ accountsservice-23.13.9/debian/patches/implicit-funcs.patch 2024-03-25 22:53:41.0 +0100
@@ -0,0 +1,22 @@
+--- a/subprojects/mocklibc.wrap
b/subprojects/mocklibc.wrap
+@@ -8,3 +8,5 @@
+ patch_url = https://wrapdb.mesonbuild.com/v1/projects/mocklibc/1.0/2/get_zip
+ patch_filename = mocklibc-1.0-2-wrap.zip
+ patch_hash = 0280f96a2eeb3c023e5acf4e00cef03d362868218d4a85347ea45137c0ef6c56
++
++diff_files = mocklibc-implicit-declarations.patch
+--- /dev/null
b/subprojects/packagefiles/mocklibc-implicit-declarations.patch
+@@ -0,0 +1,11 @@
++--- mocklibc-1.0/src/netgroup-debug.c.orig 2024-03-25 22:48:31.515887807 +0100
+ mocklibc-1.0/src/netgroup-debug.c 2024-03-25 22:46:27.311037804 +0100
++@@ -21,6 +21,8 @@
++ #include
++ #include
++
+++extern void print_indent(FILE *stream, unsigned int indent);
+++
++ void netgroup_debug_print_entry(struct entry *entry, FILE *stream, unsigned int indent) {
++ print_indent(stream, indent);
++
diff -Nru accountsservice-23.13.9/debian/patches/series accountsservice-23.13.9/debian/patches/series
--- accountsservice-23.13.9/debian/patches/series 2024-01-31 12:30:27.0 +0100
+++ accountsservice-23.13.9/debian/patches/series 2024-03-25 22:49:52.0 +0100
@@ -2,3 +2,4 @@
git_default_gdm.patch
0002-create-and-manage-groups-like-on-a-debian-system.patch
no-check-format.patch
+implicit-funcs.patch
Bug#1067712: rust-stacker: FTBFS on mips64el: process didn't exit successfully: `/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1` (signal: 11, SIGSEGV: invali
Source: rust-stacker Version: 0.1.15-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=rust-stacker=mips64el=0.1.15-1=1710415379=0 running 1 test test foo ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.61s Running `/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1` running 5 tests error: test failed, to rerun pass `--test smoke` Caused by: process didn't exit successfully: `/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1` (signal: 11, SIGSEGV: invalid memory reference) dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 Cheers -- Sebastian Ramacher
Bug#1063140: mpg123: NMU diff for 64-bit time_t transition
Hi Thomas
On 2024-03-23 15:24:58 +0100, Thomas Orgis wrote:
> Hi Sebastian,
>
>
> Am Sat, 23 Mar 2024 10:40:43 +0100
> schrieb Sebastian Ramacher :
>
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_decode_frame_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_feedseek_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1#
> > (arch-bits=32|arch=!x32)mpg123_framebyframe_decode_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_framelength_32@Base
> > 1.23.8
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_framepos_32@Base
> > 1.14.0
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_index_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_length_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_open_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_open_fd_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_open_fixed_32@Base
> > 1.26.0
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_open_handle_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_position_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1#
> > (arch-bits=32|arch=!x32)mpg123_replace_reader_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1#
> > (arch-bits=32|arch=!x32)mpg123_replace_reader_handle_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_seek_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_seek_frame_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_set_filesize_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_set_index_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tell_32@Base 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tell_stream_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tellframe_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_timeframe_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1#
> > (arch-bits=32|arch=!x32)syn123_resample_intotal_32@Base 1.26.2
> > +#MISSING: 1.32.5-1+b1#
> > (arch-bits=32|arch=!x32)syn123_resample_total_32@Base 1.26.2
> > Do you know what's happenig here?
>
> This looks just like the list of wrapper functions offered for
> applications that do not enable LFS (_FILE_OFFSET_BITS unset or 32).
>
> Steve mentioned this:
>
> > (you can't enable 64-bit time_t compatibility to use the other
> > libraries it calls, without also turning on LFS).
>
> So I take it you build mpg123 with enforced LFS so that the build does
> not detect ambiguity in off_t and hence doesn't offer 32 bit wrappers.
On all 32 bit architectures except i386 we are now building with
-D_FILE_OFFSET_BITS=64 and -D_TIME_BITS=64. Both gcc and dpkg now set
both flags. So unless the build system of a package forcibly unsets
_FILE_OFFSET_BITS and _TIME_BITS, all Debian release architectures
(except i386) now build with with 64 bit time_t and off_t.
i386 stays unchanged for historic reasons.
> I recently took pains to make the actual library code independent of
> LFS choice, using explicit 64 bit API. But If you build with
> -D_FILE_OFFSET_BITS=64 enforced, mpg123's configure will _not_ set
>
> lfs_sensitive=yes
> AC_DEFINE(LFS_SENSITIVE, 1, [ System redefines off_t when defining
> _FILE_OFFSET_BITS to 64. ])
>
> as defining the offset bits to 64 doesn't change the size of off_t, so
> it looks like a pure 64 bit offset system. But this doesn't control the
> symbols, only usage of libmpg123 API by the mpg123 application.
>
> That happens in src/libmpg123/lfs_wrap.c:
>
> off_t attribute_align_arg mpg123_tell(mpg123_handle *mh)
> {
> int64_t pos = mpg123_tell64(mh);
> OFF_RETURN(pos, mh)
> }
>
> #if SIZEOF_OFF_T == 4
>
> int attribute_align_arg mpg123_open_32(mpg123_handle *mh, const char *path)
> {
> return mpg123_open(mh, path);
> }
>
> #endif
>
> #if defined(LFS_LARGEFILE_64) || (SIZEOF_OFF_T == 8)
>
> #ifdef LFS_LARGEFILE_64
> #define OFF64 off64_t
> #else
> #define OFF64 off_t
> #endif
>
> OFF64 attribute_align_arg mpg123_tell_64(mpg123_handle *mh)
> {
> return mpg123_tell64(mh);
> }
>
> #endif
>
> So, there is the new portable mpg123_tell64 which works with int64_t,
> always. There is a 'native' off_t wrapper over this with no suffix. If
> the 'native' off_t is 32 bits, an _32 alias to that is added
Bug#1063140: mpg123: NMU diff for 64-bit time_t transition
123_replace_reader_handle@Base 1.12.1 - (arch-bits=32|arch=!x32)mpg123_replace_reader_handle_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_replace_reader_handle_32@Base 1.13.7 mpg123_replace_reader_handle_64@Base 1.13.7 mpg123_reset_eq@Base 1.6.2 mpg123_resize_string@Base 1.6.2 @@ -136,19 +136,19 @@ mpg123_scan@Base 1.6.2 mpg123_seek64@Base 1.32.3 mpg123_seek@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_seek_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_seek_32@Base 1.13.7 mpg123_seek_64@Base 1.13.7 mpg123_seek_frame64@Base 1.32.3 mpg123_seek_frame@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_seek_frame_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_seek_frame_32@Base 1.13.7 mpg123_seek_frame_64@Base 1.13.7 mpg123_set_filesize64@Base 1.32.3 mpg123_set_filesize@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_set_filesize_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_set_filesize_32@Base 1.13.7 mpg123_set_filesize_64@Base 1.13.7 mpg123_set_index64@Base 1.32.3 mpg123_set_index@Base 1.10.0 - (arch-bits=32|arch=!x32)mpg123_set_index_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_set_index_32@Base 1.13.7 mpg123_set_index_64@Base 1.13.7 mpg123_set_moreinfo@Base 1.26.0 mpg123_set_string@Base 1.6.2 @@ -161,19 +161,19 @@ mpg123_supported_decoders@Base 1.6.2 mpg123_tell64@Base 1.32.3 mpg123_tell@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_tell_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tell_32@Base 1.13.7 mpg123_tell_64@Base 1.13.7 mpg123_tell_stream64@Base 1.32.3 mpg123_tell_stream@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_tell_stream_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tell_stream_32@Base 1.13.7 mpg123_tell_stream_64@Base 1.13.7 mpg123_tellframe64@Base 1.32.3 mpg123_tellframe@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_tellframe_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_tellframe_32@Base 1.13.7 mpg123_tellframe_64@Base 1.13.7 mpg123_timeframe64@Base 1.32.3 mpg123_timeframe@Base 1.6.2 - (arch-bits=32|arch=!x32)mpg123_timeframe_32@Base 1.13.7 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_timeframe_32@Base 1.13.7 mpg123_timeframe_64@Base 1.13.7 mpg123_tpf@Base 1.6.2 mpg123_volume@Base 1.6.2 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsyn123-0/DEBIAN/symbols doesn't match completely debian/libsyn123-0.symbols --- debian/libsyn123-0.symbols (libsyn123-0_1.32.5-1+b1_armhf) +++ dpkg-gensymbolssjxz5P 2024-03-22 22:23:13.452408667 + @@ -33,14 +33,14 @@ syn123_resample_inexpect@Base 1.26.0 syn123_resample_intotal64@Base 1.32.3 syn123_resample_intotal@Base 1.26.2 - (arch-bits=32|arch=!x32)syn123_resample_intotal_32@Base 1.26.2 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)syn123_resample_intotal_32@Base 1.26.2 syn123_resample_intotal_64@Base 1.26.0 syn123_resample_maxincount@Base 1.26.0 syn123_resample_maxrate@Base 1.26.0 syn123_resample_out@Base 1.32.3 syn123_resample_total64@Base 1.32.3 syn123_resample_total@Base 1.26.2 - (arch-bits=32|arch=!x32)syn123_resample_total_32@Base 1.26.2 +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)syn123_resample_total_32@Base 1.26.2 syn123_resample_total_64@Base 1.26.0 syn123_setup_filter@Base 1.26.0 syn123_setup_geiger@Base 1.26.0 dh_makeshlibs: error: failing due to earlier errors Do you know what's happenig here? Best Sebastian -- Sebastian Ramacher
Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’
On 2024-03-22 10:35:06 -0400, Ben Westover wrote: > Sebastian, > > I can't seem to reproduce this on an armhf chroot, VM, or actual hardware > (all unstable). When were you last able to reproduce this? It's possible > (since unstable has changed rapidly in recent days) that the problem was > something external that fixed itself between then and now. I reproduced the issues a minute ago with current unstable. Please check the versions in your build with the linked build log in the initial mail. Cheers -- Sebastian Ramacher
Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’
Hi Ben On 2024-03-20 22:54:58 -0400, Ben Westover wrote: > Hello, > > The package builds fine on my armhf VM as well as a Raspberry Pi 2 running > armhf Debian bare metal. Maybe some transitioning library caused this issue? > If xmrig gets binNMU'd, it will probably build successfully. I would do it, > but I'm not a Debian Developer. Could you do it? This bug was discovered becauce of a binNMU of xmrig. I can also reproduce it locally in an unstable armhf chroot. If this is caused by a build dependency, please reassign accordingly. Cheers -- Sebastian Ramacher
Bug#1067084: ruby-sigar: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
^ linux_sigar.c: In function ‘proc_net_read’: linux_sigar.c:1947:5: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1947 | fgets(buffer, sizeof(buffer), fp); /* skip header */ | ^ linux_sigar.c: In function ‘sigar_arp_list_get’: linux_sigar.c:2428:11: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 2428 | (void)fgets(buffer, sizeof(buffer), fp); /* skip header */ | ^ make[1]: *** [Makefile:246: linux_sigar.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1067083: python-uinput: FTBFS on arm{el,hf}: libsuinput/src/suinput.c:48:28: error: ‘struct input_event’ has no member named ‘time’
Source: python-uinput Version: 1.0.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=python-uinput=armhf=1.0.1-1=1710718026=0 arm-linux-gnueabihf-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c libsuinput/src/suinput.c -o build/temp.linux-armv7l-cpython-311/libsuinput/src/suinput.o libsuinput/src/suinput.c: In function ‘suinput_emit’: libsuinput/src/suinput.c:48:28: error: ‘struct input_event’ has no member named ‘time’ 48 | gettimeofday(, 0); |^ error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 ERROR Backend subprocess exited when trying to invoke build_wheel E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 Cheers -- Sebastian Ramacher
Bug#1067076: x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’
Source: x11vnc Version: 0.9.16-9 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=x11vnc=armhf=0.9.16-9%2Bb1=1710639780=0 gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -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 -o x11vnc-user.o `test -f 'user.c' || echo './'`user.c uinput.c: In function ‘ptr_move’: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’ 723 | gettimeofday(, NULL); | ^ uinput.c: In function ‘ptr_abs’: uinput.c:776:25: error: ‘struct input_event’ has no member named ‘time’ 776 | gettimeofday(, NULL); | ^ uinput.c: In function ‘button_click’: uinput.c:962:25: error: ‘struct input_event’ has no member named ‘time’ 962 | gettimeofday(, NULL); | ^ uinput.c: In function ‘uinput_key_command’: uinput.c:1256:25: error: ‘struct input_event’ has no member named ‘time’ 1256 | gettimeofday(, NULL); | ^ Cheers -- Sebastian Ramacher
Bug#1067077: frr: FTBFS on armel: /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8'
Source: frr Version: 9.1-0.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=frr=armel=9.1-0.1=1710631814=0 libtool: link: gcc -fms-extensions -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wformat-nonliteral -Wformat-security -Wswitch-enum -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wundef -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -g -o bgpd/.libs/bgpd bgpd/bgp_main.o yang/frr-bgp-types.yang.o yang/frr-bgp.yang.o yang/frr-bgp-common-structure.yang.o yang/frr-bgp-common.yang.o yang/frr-bgp-common-multiprotocol.yang.o yang/frr-bgp-neighbor.yang.o yang/frr-bgp-peer-group.yang.o yang/frr-bgp-bmp.yang.o yang/frr-bgp-rpki.yang.o yang/frr-deviations-bgp-datacenter.yang.o yang/frr-bgp-filter.yang.o yang/frr-bgp-route-map.yang.o -Wl,--export-dynamic bgpd/libbgp.a bgpd/rfp-example/librfp/librfp.a lib/.libs/libfrr.so -lyang -lcap -lm -ljson-c -lrt -Wl,-rpath -Wl,/usr/lib/arm-linux-gnueabi/frr /usr/bin/ld: /usr/bin/ld: bgpd/libbgp.a(bgp_vty.o): in function `bgp_show_peer': ./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to `__atomic_load_8' /usr/bin/ld: ./build/../bgpd/bgp_vty.c:13686:(.text+0x1d9bc): undefined reference to `__atomic_load_8' /usr/bin/ld: ./build/../bgpd/bgp_vty.c:13778:(.text+0x1ed90): undefined reference to `__atomic_load_8' bgpd/libbgp.a(bgp_vty.o): in function `bgp_show_peer': ./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to `__atomic_load_8' /usr/bin/ld: ./build/../bgpd/bgp_vty.c:13686:(.text+0x1d9bc): undefined reference to `__atomic_load_8' /usr/bin/ld: ./build/../bgpd/bgp_vty.c:13778:(.text+0x1ed90): undefined reference to `__atomic_load_8' /usr/bin/ld: bgpd/libbgp.a(bgp_packet.o): in function `bgp_update_receive': ./build/../bgpd/bgp_packet.c:2328:(.text+0x5fac): undefined reference to `__atomic_store_8' /usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_stop': ./build/../bgpd/bgp_fsm.c:1549:(.text+0x7dc): undefined reference to `__atomic_store_8' /usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_adjust_routeadv': ./build/../bgpd/bgp_fsm.c:984:(.text+0x3700): undefined reference to `__atomic_load_8' /usr/bin/ld: bgpd/libbgp.a(bgp_io.o): in function `bgp_write': ./build/../bgpd/bgp_io.c:471:(.text+0x3e8): undefined reference to `__atomic_store_8' /usr/bin/ld: ./build/../bgpd/bgp_io.c:471:(.text+0x4f4): undefined reference to `__atomic_store_8' /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8' /usr/bin/ld: bgpd/libbgp.a(bgp_packet.o): in function `bgp_update_receive': ./build/../bgpd/bgp_packet.c:2328:(.text+0x5fac): undefined reference to `__atomic_store_8' /usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_stop': ./build/../bgpd/bgp_fsm.c:1549:(.text+0x7dc): undefined reference to `__atomic_store_8' /usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_adjust_routeadv': ./build/../bgpd/bgp_fsm.c:984:(.text+0x3700): undefined reference to `__atomic_load_8' /usr/bin/ld: bgpd/libbgp.a(bgp_io.o): in function `bgp_write': ./build/../bgpd/bgp_io.c:471:(.text+0x3e8): undefined reference to `__atomic_store_8' /usr/bin/ld: ./build/../bgpd/bgp_io.c:471:(.text+0x4f4): undefined reference to `__atomic_store_8' /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:8013: bgpd/bgp_btoa] Error 1 Cheers -- Sebastian Ramacher
Bug#1067075: openvas-scanner: FTBFS on arm{el,hf}: /<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long
Source: openvas-scanner
Version: 22.7.9-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=openvas-scanner=armhf=22.7.9-1%2Bb1=1710667919=0
[ 89%] Building C object src/CMakeFiles/openvas.dir/pluginload.c.o
cd /<>/obj-arm-linux-gnueabihf/src && /usr/bin/cc
-DNVT_TIMEOUT=320 -DOPENVAS_CONF=\"/etc/openvas/openvas.conf\"
-DOPENVAS_DATA_DIR=\"/usr/share/openvas\"
-DOPENVAS_FEED_LOCK_PATH=\"/var/lib/openvas/feed-update.lock\"
-DOPENVAS_NVT_DIR=\"/var/lib/openvas/plugins\" -DOPENVAS_RUN_DIR=\"/run/ospd\"
-DOPENVAS_STATE_DIR=\"/var/lib/openvas\" -DOPENVAS_SYSCONF_DIR=\"/etc/openvas\"
-DOPENVAS_VERSION=\"22.7.9\" -DPREFIX=\"/usr\" -DSCANNER_NVT_TIMEOUT=36000
-DSYSCONFDIR=\"/etc\" -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gvm -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64
-DLARGEFILE_SOURCE=1 -std=c11
-Wall -Wextra
-Werror -Wpedantic
-Wmissing-prototypes -Wshadow
-Wsequence-point
-D_BSD_SOURCE -D_ISOC11_SOURCE
-D_SVID_SOURCE -D_DEFAULT_SOURCE
-O3 -DNDEBUG -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector
-MD -MT src/CMakeFiles/openvas.dir/pluginload.c.o -MF
CMakeFiles/openvas.dir/pluginload.c.o.d -o
CMakeFiles/openvas.dir/pluginload.c.o -c /<>/src/pluginload.c
In file included from /usr/include/glib-2.0/glib.h:64,
from /<>/src/../misc/scanneraux.h:14,
from /<>/src/attack.h:16,
from /<>/src/attack.c:13:
/<>/src/attack.c: In function ‘attack_network’:
/<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of
type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long int’}
[-Werror=format=]
1617 | g_message ("Vulnerability scan %s finished in %ld seconds: "
|^
1618 |"%d alive hosts of %d",
1619 |globals->scan_id, now.tv_sec - then.tv_sec,
|
| |
| __time64_t {aka long long
int}
/usr/include/glib-2.0/glib/gmessages.h:350:32: note: in definition of macro
‘g_message’
350 |__VA_ARGS__)
|^~~
/<>/src/attack.c:1617:53: note: format string is defined here
1617 | g_message ("Vulnerability scan %s finished in %ld seconds: "
| ~~^
| |
| long int
| %lld
/<>/src/attack.c:1622:16: error: format ‘%ld’ expects argument of
type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long int’}
[-Werror=format=]
1622 | g_message ("Vulnerability scan %s finished in %ld seconds: %d
hosts",
|^
1623 |globals->scan_id, now.tv_sec - then.tv_sec,
|
| |
| __time64_t {aka long long
int}
/usr/include/glib-2.0/glib/gmessages.h:350:32: note: in definition of macro
‘g_message’
350 |__VA_ARGS__)
|^~~
/<>/src/attack.c:1622:53: note: format string is defined here
1622 | g_message ("Vulnerability scan %s finished in %ld seconds: %d
hosts",
| ~~^
| |
| long int
| %lld
Cheers
--
Sebastian Ramacher
