Bug#1056645: mold: Please consider updating mold to version 2.3.3
Source: mold Version: 2.3.2+dfsg-1 Severity: normal Dear Maintainer, Please consider updating mold to 2.3.3 [1]. It fixes the build on i386, which is blocking migration. Thank you! [1] - https://github.com/rui314/mold/releases/tag/v2.3.3
Bug#1050371: djbdns: Fix for tests with new glibc 2.38
Source: djbdns Version: 1:1.05-15ubuntu1 Severity: normal Dear Maintainer, djbdns is failing autopkgtests with the glibc 2.38. This is the error: "/usr/sbin/tinydns: error while loading shared libraries: libc.so.6: cannot map zero-fill pages\n" Please, find a proposed fix in my Salsa clone repository https://salsa.debian.org/danilogondolfo/djbdns/-/tree/glibc_2_38_fixes I'd submit a merge request but this repository appears to not accept it. I'm also including a fix for auto autopkgtest timeouts we are observing on Ubuntu on arm64 and armhf. It would be great to have them included. Thank you! -- System Information: Debian Release: trixie/sid APT prefers mantic APT policy: (500, 'mantic'), (100, 'mantic-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-7-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1043009: lcovutil.pm is missing
Package: lcov Version: 2.0-1 Severity: important Dear Maintainer, The new version of the lcov package (2.0-1) is not installing the file lib/lcovutil.pm. This file didn't exist in the previous version so I guess it's just a matter of updating d/rules accordingly. When I call lcov I'm getting a "Can't locate lcovutil.pm". Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic APT policy: (500, 'mantic'), (100, 'mantic-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-7-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lcov depends on: ii gcc 4:13.1.0-4ubuntu2 ii libjson-perl 4.1-1 ii libperlio-gzip-perl 0.20-1build1 ii perl 5.36.0-7ubuntu1 Versions of packages lcov recommends: ii libgd-perl [libgd-gd2-perl] 2.76-4build1 lcov suggests no packages. -- no debconf information
Bug#1037185: bpftrace: Fix FTBFS on armhf
On 07/06/2023 22:09, Vincent Bernat wrote: On 2023-06-07 12:07, Danilo Egea Gondolfo wrote: * What led up to the situation? The build is failing on armhf because cmake is not detecting the architecture correctly as we cross compile on arm64. Also, after fixing the cmake part, the build will fail in src/triggers.h due to the attribute used when it build on arm 32-bit. It might be a bug on gcc but I'm not sure (clang++ doesn't throw the same error). Shouldn't all this be fixed upstream? Both problems were fixed upstream https://github.com/iovisor/bpftrace/issues/2654
Bug#1040916: diffoscope: FTBFS with new android-platform-tools (33.0.3-1)
Source: diffoscope Version: 243 Severity: normal Dear Maintainer, diffoscope FTBFS with the new version of android-platform-tools. Some tests from tests/comparators are failing due to differences in the expected result. It's failing on both Debian and Ubuntu. Thank you! -- System Information: Debian Release: trixie/sid APT prefers mantic APT policy: (500, 'mantic'), (100, 'mantic-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-7-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1037185: bpftrace: Fix FTBFS on armhf
On 07/06/2023 22:09, Vincent Bernat wrote: On 2023-06-07 12:07, Danilo Egea Gondolfo wrote: * What led up to the situation? The build is failing on armhf because cmake is not detecting the architecture correctly as we cross compile on arm64. Also, after fixing the cmake part, the build will fail in src/triggers.h due to the attribute used when it build on arm 32-bit. It might be a bug on gcc but I'm not sure (clang++ doesn't throw the same error). Shouldn't all this be fixed upstream? Hi, I've started a discussion here https://github.com/iovisor/bpftrace/pull/2360 It appears to be a bug in GCC. One of the developers replied with a nice explanation on why this code is required and suggested that building the entire package using the ARM ISA could be a good solution.
Bug#1037007: libopenmpt: failing autopkgtests with 0.7.0
Package: libopenmpt
Version: 0.7.0-1
Followup-For: Bug #1037007
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
Please, find attached a small patch to address this issue.
* debian/tests/build: do not emit deprecation warnings.
It's causing autopkgtest failures due to the stderr output
Thanks for considering the patch.
*** /tmp/tmp_eonmzfe/libopenmpt_0.7.0-1ubuntu1.debdiff
diff -Nru libopenmpt-0.7.0/debian/tests/build
libopenmpt-0.7.0/debian/tests/build
--- libopenmpt-0.7.0/debian/tests/build 2023-05-07 14:01:57.0 +0100
+++ libopenmpt-0.7.0/debian/tests/build 2023-06-09 16:50:17.0 +0100
@@ -28,9 +28,9 @@
}
# Build programs
-${CROSS_COMPILE}gcc -Wall -o "$AUTOPKGTEST_TMP/pattern-dump-c1"
pattern-dump-c.c -lopenmpt
+${CROSS_COMPILE}gcc -Wall -o "$AUTOPKGTEST_TMP/pattern-dump-c1"
pattern-dump-c.c -lopenmpt -Wno-deprecated-declarations
echo "build1: OK"
-${CROSS_COMPILE}gcc -Wall -o "$AUTOPKGTEST_TMP/pattern-dump-c2"
pattern-dump-c.c $(${CROSS_COMPILE}pkg-config --cflags --libs libopenmpt)
+${CROSS_COMPILE}gcc -Wall -o "$AUTOPKGTEST_TMP/pattern-dump-c2"
pattern-dump-c.c $(${CROSS_COMPILE}pkg-config --cflags --libs
libopenmpt) -Wno-deprecated-declarations
echo "build2: OK"
${CROSS_COMPILE}g++ -Wall -o "$AUTOPKGTEST_TMP/pattern-dump-cpp1"
pattern-dump-cpp.cpp -lopenmpt
-- System Information:
Debian Release: bookworm/sid
APT prefers mantic
APT policy: (500, 'mantic'), (100, 'mantic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.2.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1037227: ctffind: Fix build on non-x86 architectures
Package: ctffind
Version: 4.1.14-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Dear Maintainer,
* What led up to the situation?
This software uses x86 inline assembly and fails to build on other archs.
* What exactly did you do (or not do) that was effective (or ineffective)?
With this patch it will call sinf() and cosf() from the libc on non-x86
systems.
* What was the outcome of this action?
Now it builds on non-x86 systems.
*** /tmp/tmp0oj8o0mu/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
to get is building on non-x86 systems.
* d/p/src-core-matrix: fix build on non-x86 architectures.
Stop using x86 inline assembly on non-x86 architecture and call sinf()
and cosf() functions from the libc.
Thanks for considering the patch.
*** /tmp/tmp0oj8o0mu/ctffind_4.1.14-1ubuntu1.debdiff
diff -Nru ctffind-4.1.14/debian/patches/series
ctffind-4.1.14/debian/patches/series
--- ctffind-4.1.14/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ ctffind-4.1.14/debian/patches/series 2023-06-08 12:14:33.0 +0100
@@ -0,0 +1 @@
+src-core-matrix
diff -Nru ctffind-4.1.14/debian/patches/src-core-matrix
ctffind-4.1.14/debian/patches/src-core-matrix
--- ctffind-4.1.14/debian/patches/src-core-matrix 1970-01-01
01:00:00.0 +0100
+++ ctffind-4.1.14/debian/patches/src-core-matrix 2023-06-08
12:14:33.0 +0100
@@ -0,0 +1,18 @@
+Description: Don't use inline assembly on non-x86 architectures
+
+Bug-Ubuntu: https://launchpad.net/bugs/2023288
+
+--- a/src/core/matrix.cpp
b/src/core/matrix.cpp
+@@ -4,7 +4,11 @@
+ // think i got it from a book i had about game programming in c.. it's
probably slower than what the compiler would do these days.
+
+ #define AL_PI 3.14159265358979323846
++#if defined(__i386__) || defined(__x86_64__)
+ #define _AL_SINCOS(x, s, c) __asm__ ("fsincos" : "=t" (c), "=u" (s) :
"0" (x))
++#else
++#define _AL_SINCOS(x, s, c) s = sinf(x); c = cosf(x)
++#endif
+ #define FLOATSINCOS(x, s, c) _AL_SINCOS((x) * AL_PI / 128.0, s ,c)
+
+ #define MAKE_ROTATION_f(x, y, z) \
-- System Information:
Debian Release: bookworm/sid
APT prefers mantic
APT policy: (500, 'mantic'), (100, 'mantic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.2.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1037185: bpftrace: Fix FTBFS on armhf
Package: bpftrace
Version: 0.17.0-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Dear Maintainer,
* What led up to the situation?
The build is failing on armhf because cmake is not detecting the
architecture correctly as we cross compile on arm64.
Also, after fixing the cmake part, the build will fail in src/triggers.h
due to the attribute used when it build on arm 32-bit. It might be a bug
on gcc but I'm not sure (clang++ doesn't throw the same error).
* What exactly did you do (or not do) that was effective (or ineffective)?
Patched debian/rules
* What was the outcome of this action?
The build is working on armhf and bpftrace works as expected.
*** /tmp/tmpyvgtuueq/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
* Fix FTBFS on armhf.
As we cross compile bpftrace for armhf on arm64, cmake is not detecting
the architecture correctly.
It will also set the ISA explicitly to ARM to fix a problem in
src/triggers.h caused by the target("arm") attribute where the g++
compiler fails with "invalid conversion from ‘void (*)()’ to ‘void (*)()’"
Thanks for considering the patch.
*** /tmp/tmpyvgtuueq/bpftrace_0.17.0-2ubuntu1.debdiff
diff -Nru bpftrace-0.17.0/debian/rules bpftrace-0.17.0/debian/rules
--- bpftrace-0.17.0/debian/rules 2023-04-10 11:59:06.0 +0100
+++ bpftrace-0.17.0/debian/rules 2023-06-06 18:54:52.0 +0100
@@ -1,10 +1,20 @@
#!/usr/bin/make -f
+ifeq ($(DEB_HOST_ARCH), armhf)
+ # When cross compiling on arm64 for armhf, cmake will detect the
architecture as armv8l.
+ # The CMAKE_SYSTEM_NAME appears to be required so cmake will actually
use CMAKE_SYSTEM_PROCESSOR
+ # -marm is used so the build will not fail due to the
__attribute__((target("arm")) in src/triggers.h
+ # when compiling with -mthumb. The g++ compiler will error out with:
+ # "invalid conversion from ‘void (*)()’ to ‘void (*)()’"
+ # See https://github.com/iovisor/bpftrace/commit/56106a650a8
+ ARMHF_FLAGS=-DCMAKE_SYSTEM_PROCESSOR:STRING="armv7-a"
-DCMAKE_SYSTEM_NAME:STRING=Linux -DCMAKE_CXX_FLAGS:STRING=-marm
+endif
+
%:
dh $@
override_dh_auto_configure:
- dh_auto_configure -- -DBUILD_TESTING:BOOL=OFF -DUSE_SYSTEM_BPF_BCC=1
+ dh_auto_configure -- ${ARMHF_FLAGS} -DBUILD_TESTING:BOOL=OFF
-DUSE_SYSTEM_BPF_BCC=1
STRIP_CMD=strip --keep-symbol=BEGIN_trigger --keep-symbol=END_trigger
--remove-section=.comment --remove-section=.note
override_dh_strip:
-- System Information:
Debian Release: bookworm/sid
APT prefers mantic
APT policy: (500, 'mantic'), (100, 'mantic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.2.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1033414: tgt: localtgt autopkgtest depends on fio-examples
Package: tgt Version: 1:1.0.85-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar ubuntu-patch Dear Maintainer, please consider adding "fio-examples" as a dependency of the localtgt autopkgtest. It is required by the test. With the new "fio" package (our version is 3.33-3), the tgt's localtgt autopkgtest requires "fio-examples" to work. Apparently this test is being skipped on Debian, but it's executed on Ubuntu. Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers lunar-proposed APT policy: (990, 'lunar-proposed'), (500, 'lunar') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-18-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru tgt-1.0.85/debian/tests/control tgt-1.0.85/debian/tests/control --- tgt-1.0.85/debian/tests/control 2023-01-09 11:58:58.0 -0300 +++ tgt-1.0.85/debian/tests/control 2023-03-23 16:46:49.0 -0300 @@ -6,5 +6,5 @@ Restrictions: needs-root isolation-container allow-stderr Tests: localtgt -Depends: tgt, open-iscsi, fio +Depends: tgt, open-iscsi, fio, fio-examples Restrictions: needs-root isolation-machine allow-stderr
Bug#1031764: markdown-it-py: Please consider upgrading to version 2.2.0 due to security issues
Source: markdown-it-py Version: 2.1.0-4 Severity: normal Dear Maintainer, markdown-it-py released a new version today that addresses a recent CVE, among other fixes. Please, consider upgrading to version 2.2.0. Thanks! -- System Information: Debian Release: bookworm/sid APT prefers lunar-proposed APT policy: (990, 'lunar-proposed'), (500, 'lunar') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-14-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1031703: rich: Missing dh-python in Build-Depends
Source: rich Version: 13.3.1-1 Severity: normal Dear Maintainer, as this package depends on dh-python helpers to be built, should dh-python be added to Build-Depends like other python-based packages? -- System Information: Debian Release: bookworm/sid APT prefers lunar-proposed APT policy: (990, 'lunar-proposed'), (500, 'lunar') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-14-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1029581: python-typing-extensions: Please package recent version 4.4.0
Source: python-typing-extensions Version: 4.3.0-2 Severity: wishlist Dear Maintainer, upstream has release a new version (4.4.0) few months ago. Please consider packaging the most recent version. Thanks! -- System Information: Debian Release: bookworm/sid APT prefers kinetic-updates APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 'kinetic'), (100, 'kinetic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-29-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
