Bug#1066260: mrtdreader: FTBFS: mrtdreader.c:95:41: error: implicit declaration of function ‘isprint’ [-Werror=implicit-function-declaration]
Package: mrtdreader Followup-For: Bug #1066260 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Add #include of to src/mrtdreader.c to fix build with -Werror=implicit-function-declaration. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru mrtdreader-0.1.6/debian/control mrtdreader-0.1.6/debian/control --- mrtdreader-0.1.6/debian/control 2024-04-01 09:10:39.0 +1300 +++ mrtdreader-0.1.6/debian/control 2024-04-14 11:19:27.0 +1200 @@ -1,6 +1,5 @@ Source: mrtdreader -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Ruben Undheim +Maintainer: Ruben Undheim Section: utils Priority: optional Build-Depends: dpkg-dev (>= 1.22.5), debhelper (>= 11), diff -Nru mrtdreader-0.1.6/debian/patches/missing-include.patch mrtdreader-0.1.6/debian/patches/missing-include.patch --- mrtdreader-0.1.6/debian/patches/missing-include.patch 1970-01-01 12:00:00.0 +1200 +++ mrtdreader-0.1.6/debian/patches/missing-include.patch 2024-04-14 11:19:27.0 +1200 @@ -0,0 +1,10 @@ +--- a/src/mrtdreader.c b/src/mrtdreader.c +@@ -19,6 +19,7 @@ + */ + + ++#include + #include + #include + #include diff -Nru mrtdreader-0.1.6/debian/patches/series mrtdreader-0.1.6/debian/patches/series --- mrtdreader-0.1.6/debian/patches/series 1970-01-01 12:00:00.0 +1200 +++ mrtdreader-0.1.6/debian/patches/series 2024-04-14 11:18:28.0 +1200 @@ -0,0 +1 @@ +missing-include.patch
Bug#1066285: nvi: FTBFS: ../dist/../common/options_f.c:324:16: error: implicit declaration of function 'conv_enc' [-Werror=implicit-function-declaration]
Package: nvi
Followup-For: Bug #1066285
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/patches/add-prototypes.h: add includes and prototypes for some functions
(including prototypes for some standard functions that are only accessible
if _XOPEN_SOURCE is defined, but lots of other stuff breaks if that is
defined :/).
Thanks for considering the patch.
Cheers,
mwh
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru nvi-1.81.6/debian/control nvi-1.81.6/debian/control
--- nvi-1.81.6/debian/control 2024-03-03 09:35:03.0 +1300
+++ nvi-1.81.6/debian/control 2024-04-11 14:45:28.0 +1200
@@ -1,8 +1,7 @@
Source: nvi
Section: editors
Priority: optional
-Maintainer: Ubuntu Developers
-XSBC-Original-Maintainer: Tobias Heider
+Maintainer: Tobias Heider
Standards-Version: 4.6.2
Build-Depends:
debhelper-compat (= 13),
diff -Nru nvi-1.81.6/debian/patches/add-prototypes.patch
nvi-1.81.6/debian/patches/add-prototypes.patch
--- nvi-1.81.6/debian/patches/add-prototypes.patch 1970-01-01
12:00:00.0 +1200
+++ nvi-1.81.6/debian/patches/add-prototypes.patch 2024-04-11
14:45:28.0 +1200
@@ -0,0 +1,53 @@
+--- a/common/conv.h
b/common/conv.h
+@@ -21,3 +21,6 @@
+ char2wchar_tinput2int;
+ wchar2char_tint2disp;
+ };
++
++extern int conv_enc (SCR *sp, int option, char *enc);
++extern void conv_init (SCR *orig, SCR *sp);
+--- a/cl/cl.h
b/cl/cl.h
+@@ -26,6 +26,11 @@
+ #endif
+ #endif
+
++/*
++ * for setupterm()
++ */
++#include
++
+ typedef struct _cl_private {
+ char ibuf[256]; /* Input keys. */
+
+--- a/common/multibyte.h
b/common/multibyte.h
+@@ -5,6 +5,12 @@
+ #include
+ #include
+
++/*
++ * This is declared by wchar.h, but only if _XOPEN_SOURCE is set and lots of
++ * other things break if we define that.
++ */
++extern int wcwidth (wchar_t c);
++
+ typedef wchar_t RCHAR_T;
+ #define RCHAR_T_MAX ((1 << 24)-1)
+ typedef wchar_t CHAR_T;
+--- a/cl/cl_funcs.c
b/cl/cl_funcs.c
+@@ -31,6 +31,12 @@
+ #include "../vi/vi.h"
+ #include "cl.h"
+
++/*
++ * This is declared by ncurses.h, but only if _XOPEN_SOURCE is set and lots of
++ * other things break if we define that.
++ */
++extern int waddnwstr (WINDOW *,const wchar_t *,int);
++
+ static void cl_rdiv __P((SCR *));
+
+ static int
diff -Nru nvi-1.81.6/debian/patches/series nvi-1.81.6/debian/patches/series
--- nvi-1.81.6/debian/patches/series2024-02-14 02:52:27.0 +1300
+++ nvi-1.81.6/debian/patches/series2024-04-11 14:44:02.0 +1200
@@ -36,3 +36,4 @@
upstream/0036-Fix-how-keywords-are-picked-up.patch
upstream/0037-New-macro-MEMPCPY.patch
upstream/0038-Fix-A-word-search-for-keywords-starting-with-a-non-w.patch
+add-prototypes.patch
Bug#1068789: nsis: build fails if version number has buildX or ubuntuX suffix
Package: nsis Version: build fails if version number has buildX or ubuntuX suffix Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Dear Maintainer, In Ubuntu we don't do binNMUs, we build sourceful changes with buildX appended to the version number. This breaks with the current code in d/rules which passes the whole version number to scons. The attached patch is not very clean but it does fix the build for me: * d/rules: strip off ubuntuX, buildX from package version before feeding it to scons as VERSION. Thanks for considering it! Cheers, mwh -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru nsis-3.09/debian/control nsis-3.09/debian/control --- nsis-3.09/debian/control2024-04-01 20:02:28.0 +1300 +++ nsis-3.09/debian/control2024-04-11 14:22:37.0 +1200 @@ -1,6 +1,5 @@ Source: nsis -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Thomas Gaugler +Maintainer: Thomas Gaugler Section: devel Priority: optional Build-Depends: docbook-xsl-ns, diff -Nru nsis-3.09/debian/rules nsis-3.09/debian/rules --- nsis-3.09/debian/rules 2024-03-02 21:11:24.0 +1300 +++ nsis-3.09/debian/rules 2024-04-11 14:22:12.0 +1200 @@ -11,7 +11,8 @@ # Enable hardening export DEB_BUILD_MAINT_OPTIONS=hardening=+all -VERSION=$(DEB_VERSION) +VERSION=$(shell echo $(DEB_VERSION) | sed -Ee s/\(build\|ubuntu\)[0-9]+//) + PREFIX=/usr DATADIR=$(PREFIX)/share/nsis DOCDIR=$(PREFIX)/share/doc/nsis
Bug#1068782: libesmtp: fixes for t64 and new glibc
Package: libesmtp
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Dear Maintainer,
Apologies for submitting this as only one report. libesmtp was failing
on Ubuntu on armhf only because although strlcpy is now in glibc, the
declaration is only found if _DEFAULT_SOURCE or _BSD_SOURCE is defined.
While looking at this I saw some scary warnings about the date handling
in headers.c which I fixed the easy bits of.
In Ubuntu, the attached patch was applied to achieve the following:
* d/patches/time64: cast time_t values to long long before passing to
*printf functions (code storing time_t values in void* variables will
still break in 2038).
* d/patches/default-source: define _DEFAULT_SOURCE to get access to
prototype of strlcpy.
Thanks for considering the patch.
Cheers,
mwh
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libesmtp-1.1.0/debian/patches/default-source
libesmtp-1.1.0/debian/patches/default-source
--- libesmtp-1.1.0/debian/patches/default-source1970-01-01
12:00:00.0 +1200
+++ libesmtp-1.1.0/debian/patches/default-source2024-04-11
11:37:59.0 +1200
@@ -0,0 +1,10 @@
+--- a/meson.build
b/meson.build
+@@ -30,6 +30,7 @@
+
+ cflags = [
+ '-D_POSIX_C_SOURCE=200809L',
++ '-D_DEFAULT_SOURCE',
+ ]
+
+ cflags_warnings = [
diff -Nru libesmtp-1.1.0/debian/patches/series
libesmtp-1.1.0/debian/patches/series
--- libesmtp-1.1.0/debian/patches/series2023-08-19 22:04:32.0
+1200
+++ libesmtp-1.1.0/debian/patches/series2024-04-11 11:37:24.0
+1200
@@ -1 +1,3 @@
meson-build-soname
+time64
+default-source
diff -Nru libesmtp-1.1.0/debian/patches/time64
libesmtp-1.1.0/debian/patches/time64
--- libesmtp-1.1.0/debian/patches/time641970-01-01 12:00:00.0
+1200
+++ libesmtp-1.1.0/debian/patches/time642024-04-11 11:37:18.0
+1200
@@ -0,0 +1,16 @@
+--- a/headers.c
b/headers.c
+@@ -170,11 +170,11 @@
+ {
+ #ifdef HAVE_GETTIMEOFDAY
+ if (gettimeofday (, NULL) != -1) /* This shouldn't fail ... */
+- snprintf (buf, sizeof buf, "%ld.%ld.%d@%s", tv.tv_sec, tv.tv_usec,
++snprintf (buf, sizeof buf, "%lld.%lld.%d@%s", (long
long)tv.tv_sec, (long long)tv.tv_usec,
+ getpid (), message->session->localhost);
+ else /* ... but if it does fall back to using time() */
+ #endif
+- snprintf (buf, sizeof buf, "%ld.%d@%s", time (NULL),
++ snprintf (buf, sizeof buf, "%lld.%d@%s", (long long)time (NULL),
+ getpid (), message->session->localhost);
+ message_id = buf;
+ }
Bug#1066505: epic5: FTBFS: functions.c:7547:15: error: implicit declaration of function ‘strptime’; did you mean ‘strftime’? [-Werror=implicit-function-declaration]
Package: epic5
Followup-For: Bug #1066505
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/patches/define-xopen-bsd-source.patch: #define _XOPEN_SOURCE and
_BSD_SOURCE to get access to the declaration of strptime, strlcat and some
other symbols.
Thanks for considering the patch.
Cheers,
mwh
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru epic5-2.1.6/debian/patches/define-xopen-bsd-source.patch
epic5-2.1.6/debian/patches/define-xopen-bsd-source.patch
--- epic5-2.1.6/debian/patches/define-xopen-bsd-source.patch1970-01-01
12:00:00.0 +1200
+++ epic5-2.1.6/debian/patches/define-xopen-bsd-source.patch2024-04-10
14:07:56.0 +1200
@@ -0,0 +1,17 @@
+--- a/include/irc_std.h
b/include/irc_std.h
+@@ -12,6 +12,14 @@
+ #include "defs.h"
+
+ /*
++ * Define _XOPEN_SOURCE to get access to prototype of strptime() and
++ * _BSD_SOURCE to get access to prototype of strl{cat,cpy} and declaration of
++ * h_errno.
++ */
++#define _XOPEN_SOURCE 700
++#define _BSD_SOURCE
++
++/*
+ * Try to turn back the IPv6 monster at the gate
+ */
+ #ifdef DO_NOT_USE_IPV6
diff -Nru epic5-2.1.6/debian/patches/series epic5-2.1.6/debian/patches/series
--- epic5-2.1.6/debian/patches/series 2021-10-10 00:04:08.0 +1300
+++ epic5-2.1.6/debian/patches/series 2024-04-10 14:07:56.0 +1200
@@ -2,3 +2,4 @@
manual.patch
path.patch
reproducible-build.patch
+define-xopen-bsd-source.patch
Bug#1067654: tpm2-abrmd: Tests fail on 32-bit t64 arches
Package: tpm2-abrmd Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Disable testsuite on armhf for now (the mocking the test harness does fails when _FILE_BITS == 64). This is very similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067418 Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru tpm2-abrmd-3.0.0/debian/control tpm2-abrmd-3.0.0/debian/control 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 12:42:50.0 +1300 +++ tpm2-abrmd-3.0.0/debian/rules 2024-03-25 20:21:21.0 +1300 @@ -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) +ifeq ($(DEB_HOST_ARCH),armhf) +DEB_BUILD_OPTIONS+=nocheck +endif + %: dh $@ --exclude=.la --with autoreconf
Bug#1067474: gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built
Package: gxr-openvr Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * s/libgxr-0.15-0/libgxr-dev/ in Build-Depends. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gxr-openvr-0.15.1/debian/control gxr-openvr-0.15.1/debian/control --- gxr-openvr-0.15.1/debian/control2024-03-08 18:00:00.0 +1300 +++ gxr-openvr-0.15.1/debian/control2024-03-22 18:20:57.0 +1300 @@ -1,8 +1,7 @@ Source: gxr-openvr Section: contrib/libs Priority: optional -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Andrew Lee (李健秋) +Maintainer: Andrew Lee (李健秋) Uploaders: Héctor Orón Martínez Build-Depends: debhelper (>= 11), @@ -12,7 +11,7 @@ gtk-doc-tools, libgtk-3-dev (>= 3.22), libgulkan-dev (>= 0.15.0), - libgxr-0.15-0, + libgxr-dev, libjson-glib-dev, libopenvr-dev, mesa-common-dev,
Bug#1067473: gambas3: ftbfs on time64 arches
Package: gambas3 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * s/libdumb1/libdump1t64/ in Build-Depends. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gambas3-3.19.0/debian/control gambas3-3.19.0/debian/control --- gambas3-3.19.0/debian/control 2024-01-05 12:31:10.0 +1300 +++ gambas3-3.19.0/debian/control 2024-03-22 16:46:35.0 +1300 @@ -17,7 +16,7 @@ libcrypt-dev, libcurl4-gnutls-dev | libcurl-ssl-dev, libdbus-1-dev, - libdumb1, + libdumb1t64, libffi-dev, libglew-dev, libgmime-3.0-dev,
Bug#1066292: createrepo-c: FTBFS: xml_file.c:338:36: error: implicit declaration of function ‘rasprintf’; did you mean ‘g_sprintf’? [-Werror=implicit-function-declaration]
Package: createrepo-c
Followup-For: Bug #1066292
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Fix printing time_t and missing prototypes.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru createrepo-c-0.17.3/debian/patches/ftbfs.patch
createrepo-c-0.17.3/debian/patches/ftbfs.patch
--- createrepo-c-0.17.3/debian/patches/ftbfs.patch 1970-01-01
12:00:00.0 +1200
+++ createrepo-c-0.17.3/debian/patches/ftbfs.patch 2024-03-22
15:53:53.0 +1300
@@ -0,0 +1,21 @@
+--- a/src/xml_dump_repomd.c
b/src/xml_dump_repomd.c
+@@ -143,7 +143,7 @@
+BAD_CAST repomd->revision);
+ } else {
+ // Use the current time if no revision was explicitly specified
+-gchar *rev = g_strdup_printf("%ld", time(NULL));
++gchar *rev = g_strdup_printf("%lld", (long long)time(NULL));
+ xmlNewChild(root, NULL, BAD_CAST "revision", BAD_CAST rev);
+ g_free(rev);
+ }
+--- a/src/xml_file.c
b/src/xml_file.c
+@@ -20,6 +20,7 @@
+ #include
+ #include
+ #include
++#include
+ #include "xml_file.h"
+ #include
+ #include "error.h"
diff -Nru createrepo-c-0.17.3/debian/patches/series
createrepo-c-0.17.3/debian/patches/series
--- createrepo-c-0.17.3/debian/patches/series 2023-01-06 11:16:32.0
+1300
+++ createrepo-c-0.17.3/debian/patches/series 2024-03-22 15:52:17.0
+1300
@@ -1,3 +1,4 @@
python-path.patch
python-skbuild-path.patch
python-platlib-debian.patch
+ftbfs.patch
Bug#1067403: perdition: definition of strcasestr clashes with that of glibc
Package: perdition
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/patches/remove-strcasestr.patch: remove implementation of strcasestr
that conflicts with that provided by glibc.
which causes a ftbfs in Ubuntu. I'm not sure why Debian is not affected
-- we have a newer version of glibc though, so it's probably that.
Thanks for considering the patch. I doubt upstream would be happy with
it!
Cheers,
mwh
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru perdition-2.2/debian/patches/remove-strcasestr.patch
perdition-2.2/debian/patches/remove-strcasestr.patch
--- perdition-2.2/debian/patches/remove-strcasestr.patch1970-01-01
12:00:00.0 +1200
+++ perdition-2.2/debian/patches/remove-strcasestr.patch2024-03-21
16:23:27.0 +1300
@@ -0,0 +1,68 @@
+--- a/perdition/str.c
b/perdition/str.c
+@@ -705,37 +705,6 @@
+ }
+
+ /**
+- * strcasestring
+- * Find the first occurrence of string in a string, case insensitively
+- * pre: haystack: string to search in
+- * needle: string to search for
+- * return: pointer to the first occurrence of needle
+- * NULL on error
+- *
+- * Note: returns a const char* rather than a char * like strstr().
+- * This seems more logical given the type of the inputs.
+- *
+- * strcasestr() exists in gcc (and returns char *) but this
+- * is a GNU extension. As an implementation is needed for when
+- * perdition is compiled against other libcs, it may as be used all
+- * the time.
+- **/
+-
+-const char *strcasestr(const char *haystack, const char *needle)
+-{
+- size_t i, haystack_len, needle_len;
+-
+- haystack_len = strlen(haystack);
+- needle_len = strlen(needle);
+-
+- for (i = 0; haystack_len - i >= needle_len; i++)
+- if (!strcasecmp(haystack + i, needle))
+- return haystack + i;
+-
+- return NULL;
+-}
+-
+-/**
+ * strcasedelimword
+ * Find the first occurrence of a word in a string
+ * That is, find a needle in a haystack and make sure that;
+--- a/perdition/str.h
b/perdition/str.h
+@@ -335,25 +335,6 @@
+ char *str_replace(char *str, size_t n, ...);
+
+ /**
+- * strcasestring
+- * Find the first occurrence of string in a string, case insensitively
+- * pre: haystack: string to search in
+- * needle: string to search for
+- * return: pointer to the first occurrence of needle
+- * NULL on error
+- *
+- * Note: returns a const char* rather than a char * like strstr().
+- * This seems more logical given the type of the inputs.
+- *
+- * strcasestr() exists in gcc (and returns char *) but this
+- * is a GNU extension. As an implementation is needed for when
+- * perdition is compiled against other libcs, it may as be used all
+- * the time.
+- **/
+-
+-const char *strcasestr(const char *haystack, const char *needle);
+-
+-/**
+ * strcasedelimword
+ * Find the first occurrence of a word in a string
+ * That is, find a needle in a haystack and make sure that;
diff -Nru perdition-2.2/debian/patches/series
perdition-2.2/debian/patches/series
--- perdition-2.2/debian/patches/series 2019-08-02 23:10:52.0 +1200
+++ perdition-2.2/debian/patches/series 2024-03-21 16:23:13.0 +1300
@@ -1 +1,2 @@
fix-build.patch
+remove-strcasestr.patch
Bug#1067076: x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’
Package: x11vnc
Followup-For: Bug #1067076
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/0007-use-clock_gettime-to-replace-gettimeofday.patch:
Use clock_gettime to replace gettimeofday.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru
x11vnc-0.9.16/debian/patches/0007-use-clock_gettime-to-replace-gettimeofday.patch
x11vnc-0.9.16/debian/patches/0007-use-clock_gettime-to-replace-gettimeofday.patch
---
x11vnc-0.9.16/debian/patches/0007-use-clock_gettime-to-replace-gettimeofday.patch
1970-01-01 12:00:00.0 +1200
+++
x11vnc-0.9.16/debian/patches/0007-use-clock_gettime-to-replace-gettimeofday.patch
2024-03-21 15:26:54.0 +1300
@@ -0,0 +1,86 @@
+Description: Use clock_gettime to replace gettimeofday
+ So that the program is compatible with 64-bit time_t types on 32-bit systems
+Author: Zixing Liu
+Forwarded: no
+Last-Update: 2024-03-21
+
+Index: x11vnc/src/uinput.c
+===
+--- x11vnc.orig/src/uinput.c
x11vnc/src/uinput.c
+@@ -710,6 +710,7 @@ void parse_uinput_str(char *in) {
+ static void ptr_move(int dx, int dy) {
+ #ifdef UINPUT_OK
+ struct input_event ev;
++ struct timespec tv;
+ int d = direct_rel_fd < 0 ? fd : direct_rel_fd;
+
+ if (injectable && strchr(injectable, 'M') == NULL) {
+@@ -720,7 +721,9 @@ static void ptr_move(int dx, int dy) {
+
+ if (db) fprintf(stderr, "ptr_move(%d, %d) fd=%d\n", dx, dy, d);
+
+- gettimeofday(, NULL);
++ clock_gettime(CLOCK_REALTIME, );
++ ev.input_event_sec = tv.tv_sec;
++ ev.input_event_usec = tv.tv_nsec / 1000;
+ ev.type = EV_REL;
+ ev.code = REL_Y;
+ ev.value = dy;
+@@ -755,6 +758,7 @@ static void apply_tslib(int *x, int *y)
+ static void ptr_abs(int x, int y, int p) {
+ #ifdef UINPUT_OK
+ struct input_event ev;
++ struct timespec tv;
+ int x0, y0;
+ int d = direct_abs_fd < 0 ? fd : direct_abs_fd;
+
+@@ -773,7 +777,9 @@ static void ptr_abs(int x, int y, int p)
+
+ if (db) fprintf(stderr, "ptr_abs(%d, %d => %d %d, p=%d) fd=%d\n", x0,
y0, x, y, p, d);
+
+- gettimeofday(, NULL);
++ clock_gettime(CLOCK_REALTIME, );
++ ev.input_event_sec = tv.tv_sec;
++ ev.input_event_usec = tv.tv_nsec / 1000;
+ ev.type = EV_ABS;
+ ev.code = ABS_Y;
+ ev.value = y;
+@@ -950,6 +956,7 @@ if (0) {usleep(100*1000) ;}
+ static void button_click(int down, int btn) {
+ #ifdef UINPUT_OK
+ struct input_event ev;
++ struct timespec tv;
+ int d = direct_btn_fd < 0 ? fd : direct_btn_fd;
+
+ if (injectable && strchr(injectable, 'B') == NULL) {
+@@ -959,7 +966,9 @@ static void button_click(int down, int b
+ if (db) fprintf(stderr, "button_click: btn %d %s fd=%d\n", btn, down ?
"down" : "up", d);
+
+ memset(, 0, sizeof(ev));
+- gettimeofday(, NULL);
++ clock_gettime(CLOCK_REALTIME, );
++ ev.input_event_sec = tv.tv_sec;
++ ev.input_event_usec = tv.tv_nsec / 1000;
+ ev.type = EV_KEY;
+ ev.value = down;
+
+@@ -1230,6 +1239,7 @@ void uinput_pointer_command(int mask, in
+ void uinput_key_command(int down, int keysym, rfbClientPtr client) {
+ #ifdef UINPUT_OK
+ struct input_event ev;
++ struct timespec tv;
+ int scancode;
+ allowed_input_t input;
+ int d = direct_key_fd < 0 ? fd : direct_key_fd;
+@@ -1253,7 +1263,9 @@ void uinput_key_command(int down, int ke
+ if (db) fprintf(stderr, "uinput_key_command: %d -> %d %s fd=%d\n",
keysym, scancode, down ? "down" : "up", d);
+
+ memset(, 0, sizeof(ev));
+- gettimeofday(, NULL);
++clock_gettime(CLOCK_REALTIME, );
++ev.input_event_sec = tv.tv_sec;
++ev.input_event_usec = tv.tv_nsec / 1000;
+ ev.type = EV_KEY;
+ ev.code = (unsigned char) scancode;
+ ev.value = down;
diff -Nru x11vnc-0.9.16/debian/patches/series
x11vnc-0.9.16/debian/patches/series
--- x11vnc-0.9.16/debian/patches/series 2020-12-02 20:57:42.0 +1300
+++ x11vnc-0.9.16/debian/patches/series 2024-03-21 15:26:54.0 +1300
@@ -5,3 +5,4 @@
0004-x11vnc.ftbfs-gcc10.patch
0005-scan-limit-access-to-shared-memory-segments-to-curre.patch
Bug#1067401: trantor: libtrantor1 has spurious depends on libssl3
Package: trantor
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Drop spurious Depends on libssl3 as package is currently built with no TLS
provider.
The libssl3 package is being renamed to libssl3t64 as part of the time_t
transition so this is blocking various things on armhf and other
affected arches.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru trantor-1.5.12+ds/debian/control trantor-1.5.12+ds/debian/control
--- trantor-1.5.12+ds/debian/control2024-03-05 15:07:38.0 +1300
+++ trantor-1.5.12+ds/debian/control2024-03-21 15:06:24.0 +1300
@@ -12,7 +11,7 @@
Package: libtrantor1
Architecture: any
-Depends: libssl3, libc-ares2, ${misc:Depends}, ${shlibs:Depends}
+Depends: libc-ares2, ${misc:Depends}, ${shlibs:Depends}
Description: Non-blocking I/O cross-platform TCP network library
Trantor is a non-blocking I/O cross-platform TCP network library, using C++14.
Drawing on the design of Muduo Library
Bug#1067391: bitlbee-facebook: redundant dependency on libglib2.0-0
Package: bitlbee-facebook
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Remove explicit depedency on libglib2.0-0.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru bitlbee-facebook-1.2.2/debian/control
bitlbee-facebook-1.2.2/debian/control
--- bitlbee-facebook-1.2.2/debian/control 2024-03-08 16:56:22.0
+1300
+++ bitlbee-facebook-1.2.2/debian/control 2024-03-21 10:47:15.0
+1300
@@ -17,7 +16,6 @@
Architecture: any
Depends:
bitlbee (>= 3.4) | bitlbee-libpurple (>= 3.4),
- libglib2.0-0 (>= 2.28),
libjson-glib-1.0-0 (>= 0.14),
${misc:Depends},
${shlibs:Depends},
Bug#1066794:
It's hard to see from the log but the failures that are causing issues are the "path_info" gitweb tests such as expecting success of 9500.70 'path_info: project': gitweb_run "" "/.git" not ok 70 - path_info: project # gitweb_run "" "/.git" It's *impossible* to see from the log afaict but the reason this fails is because something has caused gitweb.perl to emit warnings like [Wed Mar 20 02:04:51 2024] gitweb.perl: Use of uninitialized value $my_url in substitution (s///) at /build/git-VGz7d1/git-2.43.0/gitweb/gitweb.perl line 70. This might be because of a new version of libcgi-pm-perl, but downgrading that package does not make every failure go, leaving warnings like [Wed Mar 20 02:07:53 2024] gitweb.perl: Use of uninitialized value $base in open at /build/git-VGz7d1/git-2.43.0/gitweb/gitweb.perl line 2886. Which still cause a failure. Has perl itself changed in behaviour here?
Bug#1064772: pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’
Package: pymupdf Followup-For: Bug #1064772 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Remove prototype that now clashes with version in mupdf's headers. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size --- pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size1970-01-01 12:00:00.0 +1200 +++ pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size2024-03-20 14:23:27.0 +1300 @@ -0,0 +1,17 @@ +Description: Remove incorrect prototype for function now declared in mupdf's headers. +Author: Michael Hudson-Doyle +Origin: vendor +Forwarded: no +Last-Update: 2024-03-20 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/fitz/fitz.i b/fitz/fitz.i +@@ -155,7 +155,6 @@ + // additional headers -- + pdf_obj *pdf_lookup_page_loc(fz_context *ctx, pdf_document *doc, int needle, pdf_obj **parentp, int *indexp); + fz_pixmap *fz_scale_pixmap(fz_context *ctx, fz_pixmap *src, float x, float y, float w, float h, const fz_irect *clip); +-int fz_pixmap_size(fz_context *ctx, fz_pixmap *src); + void fz_subsample_pixmap(fz_context *ctx, fz_pixmap *tile, int factor); + void fz_copy_pixmap_rect(fz_context *ctx, fz_pixmap *dest, fz_pixmap *src, fz_irect b, const fz_default_colorspaces *default_cs); + static const float JM_font_ascender(fz_context *ctx, fz_font *font); diff -Nru pymupdf-1.23.7+ds1/debian/patches/series pymupdf-1.23.7+ds1/debian/patches/series --- pymupdf-1.23.7+ds1/debian/patches/series2023-12-17 03:32:08.0 +1300 +++ pymupdf-1.23.7+ds1/debian/patches/series2024-03-20 14:22:54.0 +1300 @@ -1,2 +1,3 @@ docs fiximport +fz_pixmap_size
Bug#1065792: libspf2: FTBFS on arm{el,hf}: spf_utils.c:207:9: error: implicit declaration of function ‘memset’ [-Werror=implicit-function-declaration]
Package: libspf2 Followup-For: Bug #1065792 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Control: tags -1 patch Dear Maintainer, In Ubuntu, I just uploaded the following rather than try to be in any way clever: * d/patches/fix-include.patch: Include string.h in spf_utils.c to get a declaration for memset(). (Closes: #1065792, #1066276) Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libspf2-1.2.10/debian/patches/fix-include.patch libspf2-1.2.10/debian/patches/fix-include.patch --- libspf2-1.2.10/debian/patches/fix-include.patch 1970-01-01 12:00:00.0 +1200 +++ libspf2-1.2.10/debian/patches/fix-include.patch 2024-03-20 13:27:19.0 +1300 @@ -0,0 +1,10 @@ +--- a/src/libspf2/spf_utils.c b/src/libspf2/spf_utils.c +@@ -19,6 +19,7 @@ + #ifdef STDC_HEADERS + # include /* malloc / free */ + # include/* isupper / tolower */ ++# include/* memset */ + #endif + + #ifdef HAVE_MEMORY_H diff -Nru libspf2-1.2.10/debian/patches/series libspf2-1.2.10/debian/patches/series --- libspf2-1.2.10/debian/patches/series2023-10-23 05:33:14.0 +1300 +++ libspf2-1.2.10/debian/patches/series2024-03-20 13:27:01.0 +1300 @@ -7,3 +7,4 @@ Fixed-reverse-macro-modifier.patch no-libreplace.patch spf_compile.c-more-correct-size-of-ds_avail.patch +fix-include.patch
Bug#1067204: libspf2-dev depends on both libspf2-2t64 and libspf2-2
Package: libspf2 Version: 1.2.10-8.1 Severity: important Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Dear Maintainer, This prevents installation on a system that has been affected by the t64 transition. In Ubuntu, the attached patch was applied to achieve the following: * d/rules: Update LIB_PACKAGE to libspf2-2t64. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libspf2-1.2.10/debian/rules libspf2-1.2.10/debian/rules --- libspf2-1.2.10/debian/rules 2023-10-23 05:33:14.0 +1300 +++ libspf2-1.2.10/debian/rules 2024-03-20 13:02:44.0 +1300 @@ -1,7 +1,7 @@ #!/usr/bin/make -f SOURCE_PACKAGE = libspf2 -LIB_PACKAGE = libspf2-2 +LIB_PACKAGE = libspf2-2t64 DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
Bug#1067203: user-session-migration: fix ftbfs on architectures affected by t64 transition
Package: user-session-migration
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Do not use "%ld" specifier to print time_t timestamp.
This fixes a test failure (and misbehaviour) on systems where time_t is
64-bit and long is 32-bit.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru user-session-migration-0.4.1ubuntu1/src/user-session-migration.c
user-session-migration-0.4.1ubuntu2/src/user-session-migration.c
--- user-session-migration-0.4.1ubuntu1/src/user-session-migration.c
2023-04-10 06:06:15.0 +1200
+++ user-session-migration-0.4.1ubuntu2/src/user-session-migration.c
2024-03-20 12:29:27.0 +1300
@@ -277,7 +277,7 @@
filename = get_migration_filename();
keyfile = g_key_file_new ();
- str = g_strdup_printf ("%ld", time (NULL));
+ str = g_strdup_printf ("%lld", (long long)time (NULL));
g_key_file_set_string (keyfile,
"State", "timestamp", str);
g_free (str);
Bug#1065951: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined
Package: vde2 Version: 2.3.2+r586-9.1 Followup-For: Bug #1065951 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Undefine _FILE_OFFSET_BITS and _TIME_BITS in libvdetap.c so the library's interposition of open/open64 still works. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch --- vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch 1970-01-01 12:00:00.0 +1200 +++ vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch 2024-03-20 09:33:55.0 +1300 @@ -0,0 +1,22 @@ +Description: Undo lfs/time64 defines in libvdetap.c + Building with these macros defines interferes with this files attempt to + interpose both open and open64 +Author: Michael Hudson-Doyle +Forwarded: no +Last-Update: 2024-03-20 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/src/vdetaplib/libvdetap.c b/src/vdetaplib/libvdetap.c +@@ -1,6 +1,11 @@ + /* Copyright 2004 Renzo Davoli + * Reseased under the GPLv2 */ + ++/* Building with these macros defines interferes with this files attempt to ++ interpose both open and open64 */ ++#undef _FILE_OFFSET_BITS ++#undef _TIME_BITS ++ + #define _GNU_SOURCE + #include + #include diff -Nru vde2-2.3.2+r586/debian/patches/series vde2-2.3.2+r586/debian/patches/series --- vde2-2.3.2+r586/debian/patches/series 2020-01-31 00:43:23.0 +1300 +++ vde2-2.3.2+r586/debian/patches/series 2024-03-20 09:33:55.0 +1300 @@ -5,3 +5,4 @@ vdeterm_terminal_reset.patch fix_qtime_hash_gc_race_condition.patch vde_cryptcab-compile-against-openssl-1.1.0.patch +interposition-vs-lfs.patch
Bug#1067125: RM: consolekit2/experimental -- ROM; t64 transition not needed
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: michael.hud...@ubuntu.com A month or so ago I NMUed consolekit2 1.2.6-3.1~exp1 to experimental, which ftbfs and turned out to be unnecessary. The package can be removed. Cheers, mwh
Bug#1061493: consolekit: install PAM module and udev files into /usr
On Fri, 15 Mar 2024 at 08:51, Mark Hindley wrote: > Control: notfound -1 1.2.6-3 > > On Wed, Mar 13, 2024 at 10:40:40PM +0100, Andreas Beckmann wrote: > > Followup-For: Bug #1061493 > > Control: found -1 1.2.6-3.1~exp1 > > Control: severity -1 serious > > Control: tag -1 ftbfs > > > > This change causes consolekit2 to to FTBFS in experimental: > > Indeed. As it was an NMU, I think the etiquette is for the NMUer to fix. > Apologies for the disruption. > In sid consolekit2 still builds cleanly. Therefore, marking notfound there. > Michael, perhaps you would fix your NMU, or provide a better patch? > I thought I had uploaded a fix for this but in any case it was determined that consolekit2 did not need to be part of the transition so the package can be removed from experimental. I'll file a removal request in a moment, or you can just upload over it. Cheers, mwh
Bug#1065454: libcanberra: Correct dpkg-dev build dependency
Source: libcanberra Version: 0.30-10ubuntu4 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libcanberra-0.30/debian/changelog libcanberra-0.30/debian/changelog --- libcanberra-0.30/debian/changelog 2024-03-04 23:41:54.0 +1300 +++ libcanberra-0.30/debian/changelog 2024-03-05 10:55:23.0 +1300 @@ -1,3 +1,10 @@ +libcanberra (0.30-12.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:55:23 +1300 + libcanberra (0.30-12.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libcanberra-0.30/debian/control libcanberra-0.30/debian/control --- libcanberra-0.30/debian/control 2024-03-04 23:41:54.0 +1300 +++ libcanberra-0.30/debian/control 2024-03-05 10:55:23.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Josselin Mouette , Laurent Bigonville , Marco Trevisan (Treviño) , Sjoerd Simons -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), libltdl-dev | libltdl7-dev (>= 2.2.6), libasound2-dev [linux-any],
Bug#1065453: orc: Correct dpkg-dev build dependency
Source: orc Version: 1:0.4.34-3 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru orc-0.4.34/debian/changelog orc-0.4.34/debian/changelog --- orc-0.4.34/debian/changelog 2024-03-04 23:40:36.0 +1300 +++ orc-0.4.34/debian/changelog 2024-03-05 10:54:56.0 +1300 @@ -1,3 +1,10 @@ +orc (1:0.4.34-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:54:56 +1300 + orc (1:0.4.34-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru orc-0.4.34/debian/control orc-0.4.34/debian/control --- orc-0.4.34/debian/control 2024-03-04 23:40:36.0 +1300 +++ orc-0.4.34/debian/control 2024-03-05 10:54:56.0 +1300 @@ -4,7 +4,7 @@ Maintainer: Maintainers of GStreamer packages Uploaders: Sebastian Dröge , Sjoerd Simons -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), meson, pkg-config,
Bug#1065451: glibmm2.4: Correct dpkg-dev build dependency
Source: glibmm2.4 Version: 2.66.6-2 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru glibmm2.4-2.66.6/debian/changelog glibmm2.4-2.66.6/debian/changelog --- glibmm2.4-2.66.6/debian/changelog 2024-03-04 23:39:52.0 +1300 +++ glibmm2.4-2.66.6/debian/changelog 2024-03-05 10:51:53.0 +1300 @@ -1,3 +1,10 @@ +glibmm2.4 (2.66.6-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:51:53 +1300 + glibmm2.4 (2.66.6-3.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru glibmm2.4-2.66.6/debian/control glibmm2.4-2.66.6/debian/control --- glibmm2.4-2.66.6/debian/control 2024-03-04 23:39:52.0 +1300 +++ glibmm2.4-2.66.6/debian/control 2024-03-05 10:51:53.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), doxygen, glib-networking ,
Bug#1065452: gtkmm3.0: Correct dpkg-dev build dependency
Source: gtkmm3.0 Version: 3.24.8-2 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gtkmm3.0-3.24.8/debian/changelog gtkmm3.0-3.24.8/debian/changelog --- gtkmm3.0-3.24.8/debian/changelog2024-03-04 23:41:24.0 +1300 +++ gtkmm3.0-3.24.8/debian/changelog2024-03-05 10:53:03.0 +1300 @@ -1,3 +1,10 @@ +gtkmm3.0 (3.24.8-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:53:03 +1300 + gtkmm3.0 (3.24.8-3.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gtkmm3.0-3.24.8/debian/control gtkmm3.0-3.24.8/debian/control --- gtkmm3.0-3.24.8/debian/control 2024-03-04 23:41:24.0 +1300 +++ gtkmm3.0-3.24.8/debian/control 2024-03-05 10:53:03.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), doxygen, graphviz,
Bug#1065450: glibmm2.68: Correct dpkg-dev build dependency
Source: glibmm2.68 Version: 2.78.0-1 Severity: important X-Debbugs-Cc: michael.hud...@ubuntu.com Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru glibmm2.68-2.78.1/debian/changelog glibmm2.68-2.78.1/debian/changelog --- glibmm2.68-2.78.1/debian/changelog 2024-03-04 23:35:03.0 +1300 +++ glibmm2.68-2.78.1/debian/changelog 2024-03-05 10:49:44.0 +1300 @@ -1,3 +1,10 @@ +glibmm2.68 (2.78.1-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 10:49:44 +1300 + glibmm2.68 (2.78.1-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru glibmm2.68-2.78.1/debian/control glibmm2.68-2.78.1/debian/control --- glibmm2.68-2.78.1/debian/control2024-03-04 23:35:03.0 +1300 +++ glibmm2.68-2.78.1/debian/control2024-03-05 10:49:44.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Michael Biebl -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), doxygen, glib-networking ,
Bug#1065444: gegl: Correct dpkg-dev build dependency
Source: gegl Version: 1:0.4.44-3ubuntu1 Severity: important Dear maintainer, Yesterday I uploaded an NMU of this package to unstable to add a build dependency on dpkg-dev but I made a mistake in my script and the package is now BD-Uninstallable. I am uploading a fix to unstable now. Apologies for the disruption. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gegl-0.4.48/debian/changelog gegl-0.4.48/debian/changelog --- gegl-0.4.48/debian/changelog2024-03-04 23:38:29.0 +1300 +++ gegl-0.4.48/debian/changelog2024-03-05 09:37:53.0 +1300 @@ -1,3 +1,10 @@ +gegl (1:0.4.48-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build depedency on dpkg-dev to use >= not >> (sorry). + + -- Michael Hudson-Doyle Tue, 05 Mar 2024 09:37:53 +1300 + gegl (1:0.4.48-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gegl-0.4.48/debian/control gegl-0.4.48/debian/control --- gegl-0.4.48/debian/control 2024-03-04 23:38:29.0 +1300 +++ gegl-0.4.48/debian/control 2024-03-05 09:37:53.0 +1300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha , Josselin Mouette -Build-Depends: dpkg-dev (>> 1.22.5), +Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), dh-sequence-gir, dh-sequence-gnome,
Bug#1065284: lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru lucene++-3.0.9/debian/changelog lucene++-3.0.9/debian/changelog --- lucene++-3.0.9/debian/changelog 2024-02-29 00:10:42.0 +1300 +++ lucene++-3.0.9/debian/changelog 2024-03-04 23:42:22.0 +1300 @@ -1,3 +1,11 @@ +lucene++ (3.0.9-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065284) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:42:22 +1300 + lucene++ (3.0.9-3) unstable; urgency=medium * Upload to sid diff -Nru lucene++-3.0.9/debian/control lucene++-3.0.9/debian/control --- lucene++-3.0.9/debian/control 2024-02-29 00:09:37.0 +1300 +++ lucene++-3.0.9/debian/control 2024-03-04 23:42:21.0 +1300 @@ -2,7 +2,8 @@ Priority: optional Maintainer: Łukasz 'sil2100' Zemczak Uploaders: Gianfranco Costamagna -Build-Depends: cmake, +Build-Depends: dpkg-dev (>> 1.22.5), + cmake, debhelper-compat (= 13), libboost-date-time-dev, libboost-filesystem-dev,
Bug#1065279: libcanberra: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libcanberra-0.30/debian/changelog libcanberra-0.30/debian/changelog --- libcanberra-0.30/debian/changelog 2024-02-29 09:08:28.0 +1300 +++ libcanberra-0.30/debian/changelog 2024-03-04 23:41:54.0 +1300 @@ -1,3 +1,11 @@ +libcanberra (0.30-12.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065279) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:41:54 +1300 + libcanberra (0.30-12) unstable; urgency=medium * Stop using debian/control.in and dh-sequence-gnome diff -Nru libcanberra-0.30/debian/control libcanberra-0.30/debian/control --- libcanberra-0.30/debian/control 2024-02-29 09:08:28.0 +1300 +++ libcanberra-0.30/debian/control 2024-03-04 23:41:54.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Josselin Mouette , Laurent Bigonville , Marco Trevisan (Treviño) , Sjoerd Simons -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), libltdl-dev | libltdl7-dev (>= 2.2.6), libasound2-dev [linux-any], libvorbis-dev,
Bug#1065278: gtkmm3.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gtkmm3.0-3.24.8/debian/changelog gtkmm3.0-3.24.8/debian/changelog --- gtkmm3.0-3.24.8/debian/changelog2024-02-29 09:04:43.0 +1300 +++ gtkmm3.0-3.24.8/debian/changelog2024-03-04 23:41:24.0 +1300 @@ -1,3 +1,11 @@ +gtkmm3.0 (3.24.8-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065278) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:41:24 +1300 + gtkmm3.0 (3.24.8-3) unstable; urgency=medium * Use upstream patch to fix GdkRGBA test on i386 diff -Nru gtkmm3.0-3.24.8/debian/control gtkmm3.0-3.24.8/debian/control --- gtkmm3.0-3.24.8/debian/control 2024-02-29 09:04:43.0 +1300 +++ gtkmm3.0-3.24.8/debian/control 2024-03-04 23:41:24.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), doxygen, graphviz, libgtk-3-dev (>= 3.24.0),
Bug#1065265: glade: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru glade-3.40.0/debian/changelog glade-3.40.0/debian/changelog --- glade-3.40.0/debian/changelog 2024-02-28 15:41:41.0 +1300 +++ glade-3.40.0/debian/changelog 2024-03-04 23:38:30.0 +1300 @@ -1,3 +1,11 @@ +glade (3.40.0-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065265) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:38:30 +1300 + glade (3.40.0-4) unstable; urgency=medium * Release to unstable (Closes: #1062127) diff -Nru glade-3.40.0/debian/control glade-3.40.0/debian/control --- glade-3.40.0/debian/control 2024-02-28 15:41:41.0 +1300 +++ glade-3.40.0/debian/control 2024-03-04 23:38:30.0 +1300 @@ -6,8 +6,9 @@ Section: gnome Priority: optional Maintainer: Debian GNOME Maintainers -Uploaders: Emilio Pozuelo Monfort , Laurent Bigonville , Marco Trevisan (Treviño) , Michael Biebl -Build-Depends: at-spi2-core , +Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha , Laurent Bigonville , Marco Trevisan (Treviño) , Michael Biebl +Build-Depends: dpkg-dev (>> 1.22.5), + at-spi2-core , dbus , debhelper-compat (= 13), dh-sequence-gir, diff -Nru glade-3.40.0/debian/control.in glade-3.40.0/debian/control.in --- glade-3.40.0/debian/control.in 2024-02-28 15:41:41.0 +1300 +++ glade-3.40.0/debian/control.in 2024-03-04 23:38:30.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: @GNOME_TEAM@ -Build-Depends: at-spi2-core , +Build-Depends: dpkg-dev (>> 1.22.5), + at-spi2-core , dbus , debhelper-compat (= 13), dh-sequence-gir,
Bug#1065277: gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gtkmm2.4-2.24.5/debian/changelog gtkmm2.4-2.24.5/debian/changelog --- gtkmm2.4-2.24.5/debian/changelog2024-02-29 04:22:27.0 +1300 +++ gtkmm2.4-2.24.5/debian/changelog2024-03-04 23:40:46.0 +1300 @@ -1,3 +1,11 @@ +gtkmm2.4 (1:2.24.5-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065277) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:40:46 +1300 + gtkmm2.4 (1:2.24.5-5) unstable; urgency=medium [ Jeremy Bícha ] diff -Nru gtkmm2.4-2.24.5/debian/control gtkmm2.4-2.24.5/debian/control --- gtkmm2.4-2.24.5/debian/control 2024-02-29 04:22:27.0 +1300 +++ gtkmm2.4-2.24.5/debian/control 2024-03-04 23:40:46.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), libgtk2.0-dev (>= 2.24.0), libglibmm-2.4-dev (>= 2.27.93), libpangomm-1.4-dev (>= 2.27.1),
Bug#1065272: orc: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru orc-0.4.34/debian/changelog orc-0.4.34/debian/changelog --- orc-0.4.34/debian/changelog 2024-02-29 01:51:27.0 +1300 +++ orc-0.4.34/debian/changelog 2024-03-04 23:40:36.0 +1300 @@ -1,3 +1,11 @@ +orc (1:0.4.34-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065272) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:40:36 +1300 + orc (1:0.4.34-4) unstable; urgency=medium * Team upload diff -Nru orc-0.4.34/debian/control orc-0.4.34/debian/control --- orc-0.4.34/debian/control 2024-02-29 01:51:27.0 +1300 +++ orc-0.4.34/debian/control 2024-03-04 23:40:36.0 +1300 @@ -4,7 +4,8 @@ Maintainer: Maintainers of GStreamer packages Uploaders: Sebastian Dröge , Sjoerd Simons -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), meson, pkg-config, gtk-doc-tools
Bug#1065271: gsound: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gsound-1.0.3/debian/changelog gsound-1.0.3/debian/changelog --- gsound-1.0.3/debian/changelog 2024-02-29 03:29:46.0 +1300 +++ gsound-1.0.3/debian/changelog 2024-03-04 23:40:14.0 +1300 @@ -1,3 +1,11 @@ +gsound (1.0.3-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065271) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:40:14 +1300 + gsound (1.0.3-3) unstable; urgency=medium * Stop using debian/control.in and dh-sequence-gnome diff -Nru gsound-1.0.3/debian/control gsound-1.0.3/debian/control --- gsound-1.0.3/debian/control 2024-02-29 03:29:46.0 +1300 +++ gsound-1.0.3/debian/control 2024-03-04 23:40:14.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Laurent Bigonville -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), dh-sequence-gir, gtk-doc-tools, libcanberra-dev,
Bug#1065252: glibmm2.68: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru glibmm2.68-2.78.1/debian/changelog glibmm2.68-2.78.1/debian/changelog --- glibmm2.68-2.78.1/debian/changelog 2024-02-28 15:49:12.0 +1300 +++ glibmm2.68-2.78.1/debian/changelog 2024-03-04 23:35:03.0 +1300 @@ -1,3 +1,11 @@ +glibmm2.68 (2.78.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065252) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:35:03 +1300 + glibmm2.68 (2.78.1-2) unstable; urgency=medium * Release to unstable (Closes: #1062137) diff -Nru glibmm2.68-2.78.1/debian/control glibmm2.68-2.78.1/debian/control --- glibmm2.68-2.78.1/debian/control2024-02-28 15:49:12.0 +1300 +++ glibmm2.68-2.78.1/debian/control2024-03-04 23:35:03.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha , Michael Biebl -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), doxygen, glib-networking , graphviz,
Bug#1065269: glibmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru glibmm2.4-2.66.6/debian/changelog glibmm2.4-2.66.6/debian/changelog --- glibmm2.4-2.66.6/debian/changelog 2024-02-28 15:45:03.0 +1300 +++ glibmm2.4-2.66.6/debian/changelog 2024-03-04 23:39:52.0 +1300 @@ -1,3 +1,11 @@ +glibmm2.4 (2.66.6-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065269) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:39:52 +1300 + glibmm2.4 (2.66.6-3) unstable; urgency=medium * Stop using debian/control.in and dh-sequence-gnome diff -Nru glibmm2.4-2.66.6/debian/control glibmm2.4-2.66.6/debian/control --- glibmm2.4-2.66.6/debian/control 2024-02-28 15:45:03.0 +1300 +++ glibmm2.4-2.66.6/debian/control 2024-03-04 23:39:52.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Jeremy Bícha -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), doxygen, glib-networking , graphviz,
Bug#1065260: gegl: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition
Dear maintainer, Please find attached a patch to add the dependency on dpkg-dev for the time_t transition. This patch is being uploaded to unstable. Thanks! -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gegl-0.4.48/debian/changelog gegl-0.4.48/debian/changelog --- gegl-0.4.48/debian/changelog2024-02-28 15:37:42.0 +1300 +++ gegl-0.4.48/debian/changelog2024-03-04 23:38:29.0 +1300 @@ -1,3 +1,11 @@ +gegl (1:0.4.48-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition. +(Closes: #1065260) + + -- Michael Hudson-Doyle Mon, 04 Mar 2024 23:38:29 +1300 + gegl (1:0.4.48-2) unstable; urgency=medium * Release to unstable (Closes: #1062066) diff -Nru gegl-0.4.48/debian/control gegl-0.4.48/debian/control --- gegl-0.4.48/debian/control 2024-02-28 15:37:42.0 +1300 +++ gegl-0.4.48/debian/control 2024-03-04 23:38:29.0 +1300 @@ -3,7 +3,8 @@ Priority: optional Maintainer: Debian GNOME Maintainers Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha , Josselin Mouette -Build-Depends: debhelper-compat (= 13), +Build-Depends: dpkg-dev (>> 1.22.5), + debhelper-compat (= 13), dh-sequence-gir, dh-sequence-gnome, gir1.2-babl-0.1-dev,
Bug#1062364:
Thanks for being so accommodating! A lot of disruption to go around...
Bug#1061961:
On Thu, 29 Feb 2024 at 17:11, Sebastiaan Couwenberg wrote: > On 2/28/24 8:33 PM, Michael Hudson-Doyle wrote: > > Hi, thanks for taking the NMU. Unfortunately it looks like you uploaded > > just slightly too early and the package was built with 32 bit time_t on > ARM > > That's odd, because gcc-13 and dpkg were already built & installed on > armel & armhf. > Hmm well maybe I'm just confused about everything. But this log https://buildd.debian.org/status/fetch.php?pkg=fyba=armhf=4.1.1-9=1709134774=0 Looks like it was built with "dev_1.22.4 gcc-13_13.2.0-13" which I think are the pre-time64 abi ones. > I also didn't start my builds until I saw a whole bunch by vorlon in the > transition tracker. Those should have the same issue then. > The script we've been using to upload the NMUs adds a versioned build-dep on dpkg-dev which should have avoided this. But maybe we should check...
Bug#1062545:
I'm going to upload a change to add versioned build-dependency on the version of dpkg-dev that enables the time64 abi for armhf and other architectures. Patch attached, which will close this bug. diff -Nru falcosecurity-libs-0.14.1/debian/changelog falcosecurity-libs-0.14.1/debian/changelog --- falcosecurity-libs-0.14.1/debian/changelog 2024-02-03 19:44:12.0 +1300 +++ falcosecurity-libs-0.14.1/debian/changelog 2024-02-29 16:16:34.0 +1300 @@ -1,3 +1,11 @@ +falcosecurity-libs (0.14.1-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add versioned dependency on dpkg-dev to guard against accidental backports +with wrong ABI. (Closes: #1062545) + + -- Michael Hudson-Doyle Thu, 29 Feb 2024 16:16:34 +1300 + falcosecurity-libs (0.14.1-5) unstable; urgency=medium * Rename libraries for 64-bit time_t transition (Closes: #1062545) diff -Nru falcosecurity-libs-0.14.1/debian/control falcosecurity-libs-0.14.1/debian/control --- falcosecurity-libs-0.14.1/debian/control 2024-02-03 19:44:12.0 +1300 +++ falcosecurity-libs-0.14.1/debian/control 2024-02-29 16:16:34.0 +1300 @@ -2,7 +2,8 @@ Section: libdevel Priority: optional Maintainer: Dima Kogan -Build-Depends: cmake, +Build-Depends: dpkg-dev (>= 1.22.5), + cmake, debhelper-compat (= 13), libvalijson-dev (>= 0.6), libb64-dev,
Bug#1061916: cups: NMU diff for 64-bit time_t transition
(the first patch had the same number as the package I uploaded to experimental and so got rejected. oops!) On Thu, 29 Feb 2024 at 12:21, wrote: > Dear maintainer, > > Please find attached a final version of this patch for the time_t > transition. This patch is being uploaded to unstable. > > Note that this adds a versioned build-dependency on dpkg-dev, to guard > against accidental backports with a wrong ABI. > > Thanks! > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) >
Bug#1061961:
Hi, thanks for taking the NMU. Unfortunately it looks like you uploaded just slightly too early and the package was built with 32 bit time_t on ARM :(
Bug#1053111: Fwd:
(this was orignally sent to 106 by mistake)
It seems that changes are needed to account for the change in `pkg-config
--variable=udevdir udev` as well. Attaching an updated diff that does that
too.
We are going to need e2fsprogs building very soon for the time_t
transition. I wonder if I should just upload this to DELAYED/1 or something.
diff -Nru e2fsprogs-1.47.0/debian/changelog e2fsprogs-1.47.0/debian/changelog
--- e2fsprogs-1.47.0/debian/changelog 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/changelog 2023-09-27 07:57:57.0 +1300
@@ -1,3 +1,14 @@
+e2fsprogs (1.47.0-2.1) UNRELEASED; urgency=medium
+
+ [ Helmut Grohne ]
+ * Non-maintainer upload.
+ * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ [ Michael Hudson-Doyle ]
+ * Account for changes in udevudevdir as well.
+
+ -- Helmut Grohne Tue, 26 Sep 2023 20:57:57 +0200
+
e2fsprogs (1.47.0-2) unstable; urgency=medium
* Don't enable metadata_csum_seed and orhpan_file by default (Closes:
diff -Nru e2fsprogs-1.47.0/debian/control e2fsprogs-1.47.0/debian/control
--- e2fsprogs-1.47.0/debian/control 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/control 2023-09-27 07:57:57.0 +1300
@@ -2,7 +2,7 @@
Section: admin
Priority: required
Maintainer: Theodore Y. Ts'o
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], cron [linux-any]
+Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], systemd-dev [linux-any], cron [linux-any]
Rules-Requires-Root: no
Standards-Version: 4.6.2
Homepage: http://e2fsprogs.sourceforge.net
diff -Nru e2fsprogs-1.47.0/debian/e2fsprogs.install e2fsprogs-1.47.0/debian/e2fsprogs.install
--- e2fsprogs-1.47.0/debian/e2fsprogs.install 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/e2fsprogs.install 2023-09-27 07:57:57.0 +1300
@@ -49,5 +49,5 @@
usr/share/man/man8/resize2fs.8
usr/share/man/man8/tune2fs.8
etc
-[linux-any] lib/udev/rules.d
-[linux-any] lib/systemd/system
+[linux-any] ${deb_udevudevdir}/rules.d
+[linux-any] ${deb_systemdsystemunitdir}
diff -Nru e2fsprogs-1.47.0/debian/.gitignore e2fsprogs-1.47.0/debian/.gitignore
--- e2fsprogs-1.47.0/debian/.gitignore 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/.gitignore 1970-01-01 12:00:00.0 +1200
@@ -1 +0,0 @@
-!patches
diff -Nru e2fsprogs-1.47.0/debian/rules e2fsprogs-1.47.0/debian/rules
--- e2fsprogs-1.47.0/debian/rules 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/rules 2023-09-27 07:57:57.0 +1300
@@ -14,6 +14,11 @@
SKIP_FUSE2FS=yes
endif
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+export deb_udevudevdir = $(shell pkg-config pkg-config --variable=udevdir udev | sed s,^/,,)
+endif
+
ifneq ($(filter pkg.e2fsprogs.no-fuse2fs,$(DEB_BUILD_PROFILES)),)
SKIP_FUSE2FS=yes
endif
Bug#1062065:
Here is a patch with the sections that get confused by in-tree symlinks hacked out. I assume the package still ftbfs though. nmu_ceph.debdiff Description: Binary data
Bug#1062246:
Here's an updated diff that strips the abi tag rather than appending to it. nmu_libcdk5.debdiff Description: Binary data
Bug#1061863:
Additional testing showed that the previous patch was incomplete, here is an updated one. nmu_ace.debdiff Description: Binary data
Bug#1063267:
The previous patch missed a required change to debian/rules, new version attached. nmu_vtk9.debdiff Description: Binary data
Bug#1064806:
And that patch had a lot of cruft in it. On Tue, 27 Feb 2024 at 09:27, Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > Apologies, I missed some things in the first version of this patch. Here's > an update. > nmu_python3.11.debdiff Description: Binary data
Bug#1064796:
Note that this diff includes the changes attached to bug 1053111.
Bug#1060000:
It seems that changes are needed to account for the change in `pkg-config
--variable=udevdir udev` as well. Attaching an updated diff that does that
too.
We are going to need e2fsprogs building very soon for the time_t
transition. I wonder if I should just upload this to DELAYED/1 or something.
diff -Nru e2fsprogs-1.47.0/debian/changelog e2fsprogs-1.47.0/debian/changelog
--- e2fsprogs-1.47.0/debian/changelog 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/changelog 2023-09-27 07:57:57.0 +1300
@@ -1,3 +1,14 @@
+e2fsprogs (1.47.0-2.1) UNRELEASED; urgency=medium
+
+ [ Helmut Grohne ]
+ * Non-maintainer upload.
+ * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ [ Michael Hudson-Doyle ]
+ * Account for changes in udevudevdir as well.
+
+ -- Helmut Grohne Tue, 26 Sep 2023 20:57:57 +0200
+
e2fsprogs (1.47.0-2) unstable; urgency=medium
* Don't enable metadata_csum_seed and orhpan_file by default (Closes:
diff -Nru e2fsprogs-1.47.0/debian/control e2fsprogs-1.47.0/debian/control
--- e2fsprogs-1.47.0/debian/control 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/control 2023-09-27 07:57:57.0 +1300
@@ -2,7 +2,7 @@
Section: admin
Priority: required
Maintainer: Theodore Y. Ts'o
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], cron [linux-any]
+Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], systemd-dev [linux-any], cron [linux-any]
Rules-Requires-Root: no
Standards-Version: 4.6.2
Homepage: http://e2fsprogs.sourceforge.net
diff -Nru e2fsprogs-1.47.0/debian/e2fsprogs.install e2fsprogs-1.47.0/debian/e2fsprogs.install
--- e2fsprogs-1.47.0/debian/e2fsprogs.install 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/e2fsprogs.install 2023-09-27 07:57:57.0 +1300
@@ -49,5 +49,5 @@
usr/share/man/man8/resize2fs.8
usr/share/man/man8/tune2fs.8
etc
-[linux-any] lib/udev/rules.d
-[linux-any] lib/systemd/system
+[linux-any] ${deb_udevudevdir}/rules.d
+[linux-any] ${deb_systemdsystemunitdir}
diff -Nru e2fsprogs-1.47.0/debian/.gitignore e2fsprogs-1.47.0/debian/.gitignore
--- e2fsprogs-1.47.0/debian/.gitignore 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/.gitignore 1970-01-01 12:00:00.0 +1200
@@ -1 +0,0 @@
-!patches
diff -Nru e2fsprogs-1.47.0/debian/rules e2fsprogs-1.47.0/debian/rules
--- e2fsprogs-1.47.0/debian/rules 2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/rules 2023-09-27 07:57:57.0 +1300
@@ -14,6 +14,11 @@
SKIP_FUSE2FS=yes
endif
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+export deb_udevudevdir = $(shell pkg-config pkg-config --variable=udevdir udev | sed s,^/,,)
+endif
+
ifneq ($(filter pkg.e2fsprogs.no-fuse2fs,$(DEB_BUILD_PROFILES)),)
SKIP_FUSE2FS=yes
endif
Bug#1062770:
> I published an updated consolidated report this morning. As you can see, > there is an ABI change due to LFS in raft/uv.h > > https://adrien.dcln.fr/misc/armhf-time_t/2024-02-22T10%3A55%3A00/compat_reports/libraft-dev/base_to_lfs/compat_report.html > > It is possible some API is not supposed to be exposed or does not appear > in a shared library or something else, and it would therefore be safe to > ignore an ABI change that abi-compliance-checker reports. Since I don't > have specific experience with this package, I can't take such decisions > and it is ultimately your call. I think a-c-c is confused here, the symbols it is complaining about are all from libuv (maybe it got confused by multiple files called "uv.h"?). So I think this package itself is unaffected, but will require a binNMU once all the directly affected packages have been rebuilt (like ~5000 other packages or whatever it is).
Bug#1062928:
FWIW adding a quirk to the analysis confirms that this package is unaffected by both the lfs and time_t transitions.
Bug#1062744:
Sigh, attached to *this* mail nmu_libzypp.debdiff Description: Binary data
Bug#1062744:
I've just reuploaded the package to experimental, new debdiff attached.
Bug#1062744:
> There are no mentions of 'time_t' in the public headers of this > library. Uh, this is not the case? zypp-core/Date.h contains a class with public time_t members. Were you grepping the wrong library or something? The library is also affected by the off_t transition. > The logs shows that it's a false positive, as the automated > tool simply wasn't able to build it: > > https://adrien.dcln.fr/misc/armhf-time_t/2023-12-18/logs/libzypp-dev/base/log.txt This is 100% not reliable logic as demonstrated above. Adrien added a quirk to confirm that the library is affected by both transitions but I feel bad for asking him to do this as the visual inspection turned out to be trivial. > Closing as not applicable. Reopening.
Bug#1062671:
I have taken the patch from this bug, applied it to 1.3.5012+dfsg-2.1 from unstable and uploaded it to experimental. Feel free to ignore this / overwrite it if it interferes with other plans but we want to make sure it passes binary NEW before we start uploading things to unstable.
Bug#1064337: [Pkg-samba-maint] Bug#1064337:
On Wed, 21 Feb 2024 at 21:49, Michael Tokarev wrote: > 21.02.2024 11:26, Michael Hudson-Doyle wrote: > > I have prepared another patch on top of what is in experimental now > (attached as nmu_samba.debdiff), does it look better? > > > > I have also prepared a patch on top of what is currently in unstable, > attached as nmu_samba_unstable.debdiff. > > It's named nmu_samba_STABLE.debdiff, though - made me confused for a bit :) > Oops, sorry about that! > Yes, this is exactly what I had in mind, and already prepared the very > same changes > locally in the package git repository. > > > I think the ideal way forward would be to upload to experimental asap to > check it builds and to let Helmut run dumat on it and then upload the > > unstable patch when the transition starts in earnest (planned for Friday > this week). The changes are pretty orthogonal to the differences between > what > > is unstable and experimental currently afaict. > > Yes, that's what I was thinking about, too. > Still, I prefer to have 4.19 in unstable so far, not 4.20-rc. > That makes sense. We definitely do not want to have to coordinate with other transitions for this, so it sounds like we (or maybe you!) should just patch the 4.19 in unstable and then you can migrate 4.20 when it suits you. So we can either do an NMU of 4.19, based on your > nmu_samba_UNstable.debdiff, > or I can do a regular upload once the transition starts. > In some sense it would be easiest to just NMU samba like we are planning to with everything else but I don't have a strong feeling about this. > Uploading what I have for experimental now, which is essentially > the same as your nmu_samba.debdiff. > Thanks!
Bug#1064337:
I have prepared another patch on top of what is in experimental now (attached as nmu_samba.debdiff), does it look better? I have also prepared a patch on top of what is currently in unstable, attached as nmu_samba_unstable.debdiff. I think the ideal way forward would be to upload to experimental asap to check it builds and to let Helmut run dumat on it and then upload the unstable patch when the transition starts in earnest (planned for Friday this week). The changes are pretty orthogonal to the differences between what is unstable and experimental currently afaict. Cheers, mwh nmu_samba.debdiff Description: Binary data nmu_samba_stable.debdiff Description: Binary data
Bug#1064298:
Hi, thanks so much for this. I've updated the diff in bug 1064090 to include your changes (and uploaded the new package to experimental as ~exp2).
Bug#1062022: dcmtk: NMU diff for 64-bit time_t transition
On Wed, 31 Jan 2024 at 22:03, Mathieu Malaterre wrote: > Hi, > > On Wed, Jan 31, 2024 at 1:09 AM wrote: > > If you have any concerns about this patch, please reach out ASAP. > Although > > this package will be uploaded to experimental immediately, there will be > a > > Are you going to nuke my work on dcmtk 3.6.8 transition ? > Hi, Sorry for the late reply. No, we are not going to nuke your work on the transition. We still expect to NMU dcmtk to unstable along with the other packages to avoid creating a dependence on your timetable, but you should be able to ignore those changes when you do your transition in unstable. Cheers, mwh
Bug#1064378: libevolution: identified for time_t transition but no ABI in shlibs
Package: libevolution Version: 3.50.3-1 Severity: important User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies libevolution as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected (also, a quick manual peek at the headers suggests that the package very likely to be affected by the transition!) However, libevolution's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libeabutil 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libeabwidgets 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libecontacteditor 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libecontactlisteditor 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libecontactprint 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libemail-engine 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libessmime 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-addressbook-importers 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-calendar-importers 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-calendar 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-mail-composer 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-mail-formatter 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-mail-importers 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-mail 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-shell 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-smime 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libevolution-util 0 libevolution (>= 3.50.3), libevolution (<< 3.51) libgnomecanvas 0 libevolution (>= 3.50.3), libevolution (<< 3.51) $ It is therefore not obvious that we should rename the package to 'libevolution-t64' as part of this transition. Looking at the archive, the only packages that depend on this package are also built from the evolution source package. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (e.g. upgrading libevolution without also upgrading evolution-plugin-bogofilter) will result in ABI skew and may result in broken behavior. Cheers, mwh [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/evolution-dev/base/log.txt -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs
Package: tcl-expect Version: 5.45.4-2build1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies tcl-expect as an affected package, on the basis that the headers could not be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected. However, tcl-expect' shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libexpect 5.45 tcl-expect $ It is therefore not obvious that we should rename the package to 'tcp-expect-t64' as part of this transition. Looking at the archive, there is a package built from a separate source package, 'skycat', which depends on this library Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading tcl-expect without also upgrading skycat) will result in ABI skew and may result in broken behavior. Cheers, mwh [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/tcl-expect-dev/base/log.txt -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1064285: dante: NMU diff for 64-bit time_t transition
Source: dante
Version: 1.4.2+dfsg-7build8
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
dante as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for $src
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package was uploaded to experimental last week (apologies, somehow
filing the bug failed), there will be a period of several days before we
begin uploads to unstable; so if information becomes available that your
package should not be included in the transition, there is time for us
to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru dante-1.4.2+dfsg/debian/changelog dante-1.4.2+dfsg/debian/changelog
--- dante-1.4.2+dfsg/debian/changelog 2019-09-12 11:17:28.0 +
+++ dante-1.4.2+dfsg/debian/changelog 2024-02-05 02:19:17.0 +
@@ -1,3 +1,10 @@
+dante (1.4.2+dfsg-7.1~exp1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle Mon, 05 Feb 2024 02:19:17 +
+
dante (1.4.2+dfsg-7) unstable; urgency=medium
* Run dpkg-gensymbols with -c4 for more stringent checks.
diff -Nru dante-1.4.2+dfsg/debian/control dante-1.4.2+dfsg/debian/control
--- dante-1.4.2+dfsg/debian/control 2019-09-12 11:17:28.0 +
+++ dante-1.4.2+dfsg/debian/control 2024-02-05 02:19:17.0 +
@@ -10,7 +10,10 @@
Vcs-Browser: https://gitlab.com/dante/pkg-debian-full
Rules-Requires-Root: no
-Package: libsocksd0
+Package: libsocksd0t64
+Provides: ${t64:Provides}
+Replaces: libsocksd0
+Breaks: libsocksd0 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
@@ -28,7 +31,7 @@
Architecture: any
Multi-Arch: same
Section: libdevel
-Depends: libsocksd0 (= ${binary:Version}), ${misc:Depends}
+Depends: libsocksd0t64 (= ${binary:Version}), ${misc:Depends}
Description: Development files for compiling programs with SOCKS support
Dante is a circuit-level firewall/proxy that can be used to provide
convenient and secure network connectivity to a wide range of hosts
@@ -38,7 +41,10 @@
This package provides header files and instructions for compiling programs
with SOCKS support.
-Package: libdsocksd0
+Package: libdsocksd0t64
+Provides: ${t64:Provides}
+Replaces: libdsocksd0
+Breaks: libdsocksd0 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
@@ -56,7 +62,7 @@
Architecture: all
Multi-Arch: foreign
Depends: ${shlibs:Depends}, ${misc:Depends}, ${perl:Depends},
- libdsocksd0 (>= ${source:Version}), libfile-which-perl
+ libdsocksd0t64 (>= ${source:Version}), libfile-which-perl
Description: SOCKS wrapper for users behind a firewall
Dante is a circuit-level firewall/proxy that can be used to provide
convenient and secure network connectivity to a wide range of hosts
diff -Nru dante-1.4.2+dfsg/debian/libdsocksd0.install
dante-1.4.2+dfsg/debian/libdsocksd0.install
--- dante-1.4.2+dfsg/debian/libdsocksd0.install 2019-09-12 11:17:28.0
+
+++ dante-1.4.2+dfsg/debian/libdsocksd0.install 1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-usr/lib/*/libdsocksd.so.*
diff -Nru dante-1.4.2+dfsg/debian/libdsocksd0.lintian-overrides
dante-1.4.2+dfsg/debian/libdsocksd0.lintian-overrides
--- dante-1.4.2+dfsg/debian/libdsocksd0
Bug#1061063:
As speculated in the upstream report there is a new misaligned access that needs to be replaced with a memcpy. Attached is a patch that fixes the build on Ubuntu arm64 kernels. Cheers, mwh diff -Nru h5py-3.10.0/debian/changelog h5py-3.10.0/debian/changelog --- h5py-3.10.0/debian/changelog 2024-01-14 04:11:16.0 +1300 +++ h5py-3.10.0/debian/changelog 2024-02-09 15:26:59.0 +1300 @@ -1,3 +1,11 @@ +h5py (3.10.0-2) UNRELEASED; urgency=medium + + * d/patches/fix-unaligned-access.patch: update to replace an additional +unaligned access with a memcpy to fix behaviour on armhf userland / arm64 +kernels without COMPAT_ALIGNMENT_FIXUPS as found in Ubuntu. + + -- Michael Hudson-Doyle Fri, 09 Feb 2024 15:26:59 +1300 + h5py (3.10.0-1) unstable; urgency=medium * Team upload. diff -Nru h5py-3.10.0/debian/patches/fix-unaligned-access.patch h5py-3.10.0/debian/patches/fix-unaligned-access.patch --- h5py-3.10.0/debian/patches/fix-unaligned-access.patch 2024-01-14 04:11:16.0 +1300 +++ h5py-3.10.0/debian/patches/fix-unaligned-access.patch 2024-02-09 15:26:10.0 +1300 @@ -1,6 +1,22 @@ a/h5py/_conv.pyx -+++ b/h5py/_conv.pyx -@@ -869,8 +869,8 @@ +Index: h5py-3.10.0/h5py/_conv.pyx +=== +--- h5py-3.10.0.orig/h5py/_conv.pyx h5py-3.10.0/h5py/_conv.pyx +@@ -705,9 +705,10 @@ cdef int conv_vlen2ndarray(void* ipt, + vlen_t in_vlen0 + size_t size, itemsize + +-#Replaces the memcpy +-size = in_vlen0.len = in_vlen[0].len +-data = in_vlen0.ptr = in_vlen[0].ptr ++memcpy(, _vlen[0].len, sizeof(size_t)) ++memcpy(, _vlen[0].ptr, sizeof(void*)) ++in_vlen0.len = size ++in_vlen0.ptr = data + + dims[0] = size + itemsize = H5Tget_size(outtype.id) +@@ -869,8 +870,8 @@ cdef int conv_ndarray2vlen(void* ipt, H5Tconvert(intype.id, outtype.id, len, data, back_buf, H5P_DEFAULT)
Bug#1061992:
In addition to uploading a reversed debdiff, I didn't actually upload it to experimental, I'm attaching the debdiff that I just uploaded (which I realized I forgot to add the ~exp suffix to, apologies). The upload to experimental was based on the contents of unstable, which is newer that what was in experimental before. Should I force push the contents of debian/unstable to debian/experimental and then add my changes on top? > Does this mean we should hold on pushing new uploads to testing and > experimental until this is done? If so, how long will it take? I don't think new uploads to experimental incorporating these changes would be a problem. Uploading these changes to unstable would start a transition so probably best not to do that until the bulk uploads happen (in a week or so I think). Unrelated uploads to unstable shouldn't be a problem as we'll base the time_t-transitioning uploads to unstable on what is in unstable at the time rather than assuming we can just upload the packages already uploaded to experimental but, uh, it would be an inconvenient time to completely refactor the packaging I think. Cheers, mwh nmu_curl_update.debdiff Description: Binary data
Bug#1061992:
> I believe these are the two cases: > > - The public 'struct curl_fileinfo' contains a time_t struct member, used for > FTP wildcard callbacks. > > - The public API curl_getdate() takes a time_t pointer in its second argument. > > If 'time_t' changes size, those two will not be ABI compatible. Interestingly, the latter is the only one picked up by ABI compliance checker: https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/compat_reports/libcurl4-openssl-dev/lfs_to_time_t/compat_report.html And because the time_t pointer argument to getdate is unused we could _probably_ get away with ignoring that (a bit sketchy from a purity point of view but I think ok in practice). OTOH the former (presumably not found because the "curl_fileinfo" type is not found in any public ABI) looks like a genuine ABI break to me. Hopefully there are not too many "hidden" ABI breaks like this lurking!
Bug#1061901:
Apologies, previous version of patch was incorrect. nmu_compiz.debdiff Description: Binary data
Bug#1061882:
Apologies, the initial message had an incorrect debdiff attached. Here's a better one (that has been uploaded to experimental). nmu_combblas.debdiff Description: Binary data
Bug#1053470: ld.so: ignore tunables in secure mode
I think that is the sort of conclusion upstream is coming to in https://inbox.sourceware.org/libc-alpha/20231003201151.1406279-1-siddh...@sourceware.org/T/#e9123bc53d892ab6552e05109ce939d531d741092 too. In any case, the upstream bug tracker / mailing list is probably the place to start with this. On Thu, 5 Oct 2023 at 07:00, Christian Göttsche wrote: > Package: glibc > Version: 2.37-12 > > In the light of the recent privilege escalation vulnerability I'd like > to suggest disabling the support for tunables in secure mode (most > notably for setuid-binaries). > This would mitigate future regressions in the handling of the > environment variable and possible vulnerabilities caused by the > interaction of particular options with security relevant applications. > > The support could either be disabled at compile time[1] or at runtime > via a file existence check (either by reusing `/etc/suid-debug` or a > new one like `/etc/suid-tunables`). > > > [1]: > https://git.altlinux.org/gears/g/glibc.git?p=glibc.git;a=commitdiff;h=5d1686416ab766f3dd0780ab730650c4c0f76ca9 > >
Bug#984205:
This is because upstream builds with -Werror -Wall by default, and that's usually a bad idea for distro packages. I fixed this like this: .PHONY: override_dh_auto_build override_dh_auto_build: $(MAINT_SCRIPTS) -dh_auto_build +dh_auto_build -- WERROR= Not really sure if this is appropriate for Debian or not!
Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument
On Tue, 12 Jul 2022 at 04:30, Aurelien Jarno wrote: > On 2022-07-11 10:06, Michael Hudson-Doyle wrote: > > It looks like a no-change rebuild fixed this in Ubuntu fwiw. > > Thanks, I confirm that in Debian too. Do you have an idea why? It could > be a missing or too loose dependency. > No. I got as far as reading https://github.com/endrazine/wcc/blob/master/README.md and then was completely unsurprised that it depends on the details of everything. It would probably be quite fun to dig into why it's failing but I don't really have the time for that today. Cheers, mwh
Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument
It looks like a no-change rebuild fixed this in Ubuntu fwiw. On Mon, 11 Jul 2022 at 09:54, Aurelien Jarno wrote: > Source: glibc, wcc > Control: found -1 glibc/2.34-0experimental4 > Control: found -1 wcc/0.0.2+dfsg-4.1 > Severity: important > Tags: experimental > > Dear maintainers, > > The autopkgtest of wcc fails in sid on amd64 when that autopkgtest is > run with the binary packages of glibc from experimental. It passes when > run with only packages from sid. In tabular form: > >passfail > glibc from sid2.34-0experimental4 > wccfrom sid0.0.2+dfsg-4.1 > all others from sidfrom sid > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the transition to glibc 2.34. Due > to the nature of this issue, I filed this bug report against both > packages. Can you please investigate the situation and reassign the bug > to the right package? > > More information about this bug and the reason for filing it can be found > on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Regards > Aurelien > > https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wcc/23455379/log.gz > > > autopkgtest [14:35:47]: test wsh-libs.wsh: [--- > open: Invalid argument > > [1;32m[SIGSEGV] Read00700101[1;34m(address not mapped to > object) > [0mbash: line 1: 2061 Segmentation fault > /tmp/autopkgtest-lxc.yfun0_rb/downtmp/build.xHo/src/debian/tests/wsh-libs.wsh > 2> >(tee -a /tmp/autopkgtest-lxc.yfun0_rb/downtmp/wsh-libs.wsh-stderr >&2) > > >(tee -a /tmp/autopkgtest-lxc.yfun0_rb/downtmp/wsh-libs.wsh-stdout) > autopkgtest [14:35:47]: test wsh-libs.wsh: ---] > autopkgtest [14:35:47]: test wsh-libs.wsh: - - - - - - - - - - results - > - - - - - - - - - > wsh-libs.wsh FAIL non-zero exit status 139 >
Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking
On Mon, 20 Jun 2022 at 14:59, Shengjing Zhu wrote:
> On Mon, Jun 20, 2022 at 08:42:51AM +1200, Michael Hudson-Doyle wrote:
> > Ah yes but that patch doesn't actually work in practice. I've been slack
> on
> > this :(
> >
> > IIRC the problem with https://go-review.googlesource.com/c/go/+/339370
> is
> > that lto causes some of the references in the linked executable to
> > disappear, meaning cgo can't do the analysis it needs to do. It's a shame
> > because it's obviously a much cleaner patch...
> >
>
> However CL281314 has its own problem that causes several packages FTBFS
> (#982701, #982714, #982720, #982724, #982734)
>
I think that was a broken version of the patch -- the packages those bugs
affect build fine in Ubuntu now afaics -- but I haven't checked explicitly.
> If CL339370 has problem too, can we try another routine? Like disable lto
> in dh-golang?
>
> If I read doko's message right, we are only going to enable lto by default
> in dpkg-buildflags, not gcc itself. So hacking dh-golang looks more
> sensible to me.
>
> For example adding following line to dh-golang (I didn't test it though):
>
> diff --git a/lib/Debian/Debhelper/Buildsystem/golang.pm
> b/lib/Debian/Debhelper/Buildsystem/golang.pm
> index 60f725a..02f16fe 100644
> --- a/lib/Debian/Debhelper/Buildsystem/golang.pm
> +++ b/lib/Debian/Debhelper/Buildsystem/golang.pm
> @@ -369,6 +369,7 @@ sub _set_goproxy {
> sub _set_cgo_flags {
> my $bf = Dpkg::BuildFlags->new();
> $bf->load_config();
> +$bf->set_feature("optimize", "lto", 0)
>
> my @flags = ( "CFLAGS", "CPPFLAGS", "CXXFLAGS", "FFLAGS", "LDFLAGS" );
> foreach my $flag (@flags) {
>
If that works, it might be a better option for now indeed.
Cheers,
mwh
Bug#1013102: cmd/link: check CGO_CFLAGS for non -g/-I/-O options before,+ internal linking
Ah yes but that patch doesn't actually work in practice. I've been slack on this :( IIRC the problem with https://go-review.googlesource.com/c/go/+/339370 is that lto causes some of the references in the linked executable to disappear, meaning cgo can't do the analysis it needs to do. It's a shame because it's obviously a much cleaner patch... Cheers, mwh On Sat, 18 Jun 2022 at 02:51, Shengjing Zhu wrote: > On Fri, Jun 17, 2022 at 3:36 PM Matthias Klose wrote: > > > > Package: src:golang-1.18 > > Version: 1.18.3-1 > > Severity: wishlist > > Tags: patch > > > > lto support now landed in dpkg in unstable, now evaluation the > possibility to > > turn on link time optimizations by default. Currently builds fail like: > > > > [...] > > loadelf: $WORK/b101/_pkg_.a(_x001.o): 151068: sym#11 > (g_cgo_export.c.d01d1947): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x002.o): 151072: sym#11 > > (cgo_linux.cgo2.c.e1a05304): ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x003.o): 151077: sym#13 > > (cgo_resnew.cgo2.c.1f334c1b): ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x004.o): 151081: sym#11 > > (cgo_socknew.cgo2.c.00cb1c10): ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b101/_pkg_.a(_x005.o): 151086: sym#13 > (cgo_unix.cgo2.c.81407354): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x001.o): 151068: sym#11 > (g_cgo_export.c.d01d1947): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x002.o): 151093: sym#11 > (cgo.cgo2.c.547524ab): > > ignoring symbol in section 4 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x003.o): 151098: sym#13 > (gcc_context.c.0c594a6b): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x004.o): 151105: sym#16 > (gcc_fatalf.c.104c99f5): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x005.o): 151116: sym#21 > (gcc_libinit.c.57049a80): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x006.o): 151126: sym#19 > > (gcc_linux_amd64.c.7bb88008): ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x007.o): 151133: sym#16 > (gcc_mmap.c.58726c34): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x008.o): 151138: sym#13 > (gcc_setenv.c.58922dfc): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x009.o): 151143: sym#14 > (gcc_sigaction.c.8c3bca0d): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x010.o): 151148: sym#13 > (gcc_traceback.c.2a322f93): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x011.o): 151156: sym#16 > (gcc_util.c.9bbd18fc): > > ignoring symbol in section 5 (type 0) > > loadelf: $WORK/b108/_pkg_.a(_x012.o): 151161: sym#13 > (linux_syscall.c.96145c1f): > > ignoring symbol in section 5 (type 0) > > _cgo_callers: relocation target x_cgo_callers not defined > > _cgo_init: relocation target x_cgo_init not defined > > _cgo_mmap: relocation target x_cgo_mmap not defined > > _cgo_munmap: relocation target x_cgo_munmap not defined > > /usr/lib/go-1.18/pkg/tool/linux_amd64/link: too many errors > > [...] > > > > > https://patches.ubuntu.com/g/golang-1.18/golang-1.18_1.18.3-1ubuntu1.patch > > > > so please disable these for now and/or forward the issue upstream. > > The patch says it has been forwarded to > https://go-review.googlesource.com/c/go/+/281314 > And on https://go-review.googlesource.com/c/go/+/281314, the comment > says it has been obsoleted by > https://go-review.googlesource.com/c/go/+/339370 > > -- > Shengjing Zhu > >
Bug#1006579:
FWIW upstream just made a release that claims to fix this bug.
Bug#1006857: python-websockets: source package no longer contains tests
Source: python-websockets Version: 9.1-1 Severity: normal Dear Maintainer, I don't know when this started, but this package is based on the sdists from pypi which currently do not contain the tests. So the tests aren't run during build, and we don't find out that e.g. the legacy submodule is broken by Python 3.10. I think packaging from upstream git is probably the way to go here (I remember some discussion about this general issue but I don't remember the conclusion!). Cheers, mwh -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish'), (400, 'impish-proposed'), (100, 'impish-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-30-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1006627: ntpsec package depends on libssl1.1 even if built against openssl3
Source: ntpsec Version: 1.2.1+dfsg1-3 Severity: normal Dear Maintainer, The ntpsec binary package on Ubuntu still depends on libssl1.1 despite being built against openssl3. The reason for this turns out to be very mundane: mwhudson@anduril:~/src/pkg/ntpsec-1.2.1+dfsg1$ grep ssl1.1 --before 1 debian/control Depends: adduser, libssl1.1 (>= 1.1.1b), Simply dropping this line and letting dh_shlibdeps do its thing seems like it works for me but maybe there's some reason for this I don't understand. Cheers, mwh -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish'), (400, 'impish-proposed'), (100, 'impish-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-30-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#997877:
I think an update to 3.3.5 will fix this. I have no idea how hard mailman3 upstream updates are :)
Bug#994055: cunit NMU
On Thu, 11 Nov 2021 at 10:49, Paul Gevers wrote: > Hi Michael, > > On Wed, 10 Nov 2021 16:16:53 +1300 Michael Hudson-Doyle > wrote: > > Hi, thanks for this fix. I think it meets the threshold for NMU (and also > > the maintainer seems to have been awol since 2015) so I'm uploading it to > > DELAYED/10. > > I was working on this yesterday and uploaded to DELAYED too, because I > forgot to check the bug history. As I uploaded to DELAYED/2, I decided > to dcut my upload, but apparently I was able to dcut your upload... > Ha. > Log of processing your commands file /paul-1636580073.commands: > > > cancel cunit_2.1-3-dfsg-2.4_source.changes > Files removed from 10-day: cunit_2.1-3-dfsg-2.4_source.changes > cunit_2.1-3-dfsg-2.4.dsc cunit_2.1-3-dfsg-2.4.debian.tar.xz > cunit_2.1-3-dfsg-2.4_source.buildinfo > > Could you reupload your changes, or do you want me to upload mine? > If you have yours close at hand, feel free to upload them? Otherwise I think I still have the changes file around... > Sorry for the mess. > So long as we get a fixed package I'm not bothered!
Bug#994055:
Hi, thanks for this fix. I think it meets the threshold for NMU (and also the maintainer seems to have been awol since 2015) so I'm uploading it to DELAYED/10.
Bug#962510: postgresql-filedump: autopkgtest fails on big endian
Yes indeed, we dropped the Ubuntu delta at some point without me noticing and the autopkgtests have been passing fine on s390x. On Fri, 1 Oct 2021 at 01:14, Christoph Berg wrote: > Version: 13.1-1 > > Re: Michael Hudson-Doyle > > I don't think Debian currently runs autopkgtests on any big endian > > architecture but Ubuntu does (on s390x) and the postgresql-filedump > > tests fail. On inspection this is because the tests use an include > > pg_dump file, and those are endian dependent. I've uploaded the attached > > patch to Ubuntu, which just skips the test on a big endian system. > > Hi Michael, > > this should have been fixed a while back when I modified the > regression tests to look at files created on the very same > architecture. > > Please reopen if it's still a problem on s390x. (I wouldn't know where > to look for the Ubuntu autopkgtests.) > > Christoph >
Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)
On Wed, 8 Sept 2021 at 07:04, Michael Biebl wrote: > Hi Aurelien > > Am 07.09.21 um 12:41 schrieb Aurelien Jarno: > > Hi, > > > > On 2021-09-07 10:39, Michael Hudson-Doyle wrote: > > >> What's happening is that systemd is running with the old glibc, forks > and > >> then does NSS things that cause the new glibc's NSS modules to load and > >> they don't necessarily work, leading to failures in any unit that > specifies > >> User=. At least for Ubuntu's builds the NSS modules seem to be ABI > >> compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they > are > >> definitely not between 2.33 and 2.34. > > > > Thanks for this feedback and the pointer to the patch used in Ubuntu. It > > seems to be a good solution, and matches what is done for other init > > systems. > > > > On the other hand, the problem is supposed to only happen for major > > glibc version upgrade where the NSS modules might have a different ABI. > > In that regard, I would be tempted to restart it only for major versions > > upgrade like it's done for other daemons. Now if the systemd maintainers > > consider it's fine restarting it for each glibc upgrade, we should > > probably go that way. > > I guess you are in a better position to make a judgement call here. If I > read the glibc bug report correctly, there aren't strictly any > guarantees regarding NSS modules. What that means for glibc minor > updates, I'm not really in a position to tell. > I think in practice minor version updates are probably going to be fine here, but also I think careful reexecing on every update is also likely to be fine in practice. If you wanted to be suuurrr paranoid, I guess you could embed in the glibc postinst knowledge of which prior versions have binary-compatible NSS modules but that seems like a lot of work for not much benefit (would you only have to care about nss_files compatibility, or the full set?). > Fwiw, I don't have a better proposal then Michael's patch he added to > Ubuntu. We could run with that and if it causes problems, reiterate on it. > Yeah, the point where we start to offer updates to 21.10 will at the least provide some data on how safe Ubuntu's approach is... Cheers, mwh
Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)
On Tue, 7 Sept 2021 at 17:49, Michael Biebl wrote: > Control: reassign -1 libc6 > Control: found -1 2.32-1 > Control: severity -1 serious > Control: affects -1 + systemd > > Hi Michael > > Am 07.09.21 um 00:39 schrieb Michael Hudson-Doyle: > > On Tue, 7 Sept 2021 at 10:21, Michael Biebl > <mailto:bi...@debian.org>> wrote: > > > > Am 06.09.21 um 23:45 schrieb Vincent Bernat: > > > Package: systemd > > > Version: 247.9-1 > > > Severity: normal > > > > > > Hey! > > > > > > After upgrading to libc6 2.32-1, some services are unable to > restart. > > > In my case, systemd-resolved, systemd-timesyncd and colord. Using > > > "systemctl daemon-reexec" fixes the issue. Unsure if there is > really > > > something to be fixed but as I didn't find anything about that, a > bug > > > report may help others. I suppose the problem is related to NSS. > > > > > > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time > > Synchronization... > > > Sep 06 23:06:43 chocobo systemd[236983]: > > systemd-timesyncd.service: Failed to determine user credentials: No > > such process > > > Sep 06 23:06:43 chocobo systemd[236983]: > > systemd-timesyncd.service: Failed at step USER spawning > > /lib/systemd/systemd-timesyncd: No such process > > > > > > > > > > > > @libc maintainers: any ideas what could be causing this? If this is > > triggered by a libc6 update, should this be reassigned to glibc? > > > > > > We went through this in Ubuntu recently and decided that restarting > > systemd in glibc's postinst was the safest option: > > https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276 > > <https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276> > > > > What's happening is that systemd is running with the old glibc, forks > > and then does NSS things that cause the new glibc's NSS modules to load > > and they don't necessarily work, leading to failures in any unit that > > specifies User=. At least for Ubuntu's builds the NSS modules seem to be > > ABI compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but > > they are definitely not between 2.33 and 2.34. > > Thanks for this information. This is indeed an icky issue and I feel > like we are between a rock and a hard place. > Yeah. I guess one could say that having a long running process that forks and then does NSS stuff is skating on thin ice a bit. At least the changes in glibc 2.34 to move nss_files functionality into glibc itself will reduce the fallout of this considerably. > I'm not a huge fan of going back to re-exec systemd again directly in > libc6.postinst, but your proposed patch to at least check that the > systemd binary can be sucessfully executed should at least deal with the > situation sufficiently, where a library is (temporarily) missing. > I do wonder though, if this this will mean that on dist-upgrades the > daemon-reexec will be skipped. > FWIW I had a long chat with Julian (the apt maintainer) about this and he thought there were three potential situations that could be a problem: 1) a new systemd is unpacked before its Depends 2) one of systemd dependencies has a Breaks: systemd (<< new) 3) in some cases a cycle has to be broken by removing a package with --force-deps It think 1) is by some margin the most likely to actually happen, and at least in that situation systemd will be restarted shortly by its own postinst. Cheers, Michael Anyway, I think it's best to reassign this libc6 for now and mark it as > RC so the package doesn't migrate to testing for now. > > Regards, > Michael > >
Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)
On Tue, 7 Sept 2021 at 10:21, Michael Biebl wrote: > Am 06.09.21 um 23:45 schrieb Vincent Bernat: > > Package: systemd > > Version: 247.9-1 > > Severity: normal > > > > Hey! > > > > After upgrading to libc6 2.32-1, some services are unable to restart. > > In my case, systemd-resolved, systemd-timesyncd and colord. Using > > "systemctl daemon-reexec" fixes the issue. Unsure if there is really > > something to be fixed but as I didn't find anything about that, a bug > > report may help others. I suppose the problem is related to NSS. > > > > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time > Synchronization... > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service: > Failed to determine user credentials: No such process > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service: > Failed at step USER spawning /lib/systemd/systemd-timesyncd: No such process > > > > > > > @libc maintainers: any ideas what could be causing this? If this is > triggered by a libc6 update, should this be reassigned to glibc? > We went through this in Ubuntu recently and decided that restarting systemd in glibc's postinst was the safest option: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276 What's happening is that systemd is running with the old glibc, forks and then does NSS things that cause the new glibc's NSS modules to load and they don't necessarily work, leading to failures in any unit that specifies User=. At least for Ubuntu's builds the NSS modules seem to be ABI compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they are definitely not between 2.33 and 2.34. Cheers, mwh
Bug#993767: radicale: autopkgtests fail with proxy set
Source: radicale Version: 3.0.6-4 Severity: normal Tags: patch Dear Maintainer, As of version 3, the autopkgtests fail in the Ubuntu ci environment, apparently because the test suite tries to talk to the test server via the globally configured http_proxy set in this environment. Rather than being at all clever, I'm just uploading the attached patch. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0-27-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru radicale-3.0.6/debian/changelog radicale-3.0.6/debian/changelog --- radicale-3.0.6/debian/changelog 2021-08-10 00:17:56.0 +1200 +++ radicale-3.0.6/debian/changelog 2021-09-06 21:36:54.0 +1200 @@ -1,3 +1,9 @@ +radicale (3.0.6-4ubuntu1) UNRELEASED; urgency=medium + + * d/tests/control: Unset http_proxy when running tests. + + -- Michael Hudson-Doyle Mon, 06 Sep 2021 21:36:54 +1200 + radicale (3.0.6-4) unstable; urgency=medium * set LogsDirectory in systemd unit; diff -Nru radicale-3.0.6/debian/control radicale-3.0.6/debian/control --- radicale-3.0.6/debian/control 2021-04-18 21:47:42.0 +1200 +++ radicale-3.0.6/debian/control 2021-09-06 21:36:54.0 +1200 @@ -1,7 +1,8 @@ Source: radicale Section: net Priority: optional -Maintainer: Jonas Smedegaard +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Jonas Smedegaard Uploaders: Martin Stigge , Christian M. Amsüss , diff -Nru radicale-3.0.6/debian/tests/control radicale-3.0.6/debian/tests/control --- radicale-3.0.6/debian/tests/control 2021-04-18 21:43:21.0 +1200 +++ radicale-3.0.6/debian/tests/control 2021-09-06 21:17:31.0 +1200 @@ -1,5 +1,5 @@ Test-Command: - pytest-3 radicale + http_proxy= pytest-3 radicale Restrictions: allow-stderr Depends: python3-pytest,
Bug#993730: snapd: - Mount snap "core" (11606) (snap is unusable due to missing files; contact developer)
This is already fixed in testing I think. On Mon, 6 Sept 2021 at 03:45, matteo wrote: > Package: snapd > Version: 2.49-1+b5 > Severity: important > X-Debbugs-Cc: eng.matteo.nunzi...@gmail.com > > Dear Maintainer, > >* What led up to the situation? > tring to install any package with the snap command >* What exactly did you do (or not do) that was effective (or > ineffective)? > tried to install: core, hello-world, google-cloud-sdk --classic. all failed >* What was the outcome of this action? > see above >* What outcome did you expect instead? > having snap installed > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages snapd depends on: > ii adduser 3.118 > ii apparmor 3.0.3-2 > ii ca-certificates 20210119 > ii gnupg2.2.27-2 > ii gnupg1 1.4.23-1.1 > ii libapparmor1 3.0.3-2 > ii libc62.31-17 > ii libcap2 1:2.44-1 > ii libseccomp2 2.5.1-1 > ii libudev1 247.9-1 > ii openssh-client 1:8.4p1-5 > ii squashfs-tools 1:4.5-2 > ii systemd 247.9-1 > ii udev 247.9-1 > > Versions of packages snapd recommends: > ii gnupg 2.2.27-2 > > Versions of packages snapd suggests: > ii zenity 3.32.0-7 > > -- no debconf information >
Bug#992223: autopkgtests test packages from boost1.71
Source: boost1.74 Version: 1.74.0-9 X-Debbugs-CC: mwhud...@debian.org Hi, the tests for the boost1.74 source package binaries from the boost1.71 source package: https://salsa.debian.org/debian/boost/-/blob/master/debian/tests/control That can't be intended :) Cheers, mwh
Bug#988905:
I see there is a fix in the git repo now. Are you planning an upload any time soon, or only after the buster release?
Bug#988905: src:request-tracker5: ftbfs due to changes in gpg error messages
Package: src:request-tracker5 Version: 5.0.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source Dear Maintainer, As can be seen at https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/request-tracker5.html or https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1 the package fails to build with the current state of unstable / Ubuntu impish. The failures are: # Failed test at t/mail/crypt-gnupg.t line 171. # found warning: gpg: error retrieving 'keyl...@example.com' via WKD: Server indicated a failure # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data) # Failed test at t/web/crypt-gnupg.t line 358. # found warning: gpg: error retrieving 'no...@example.com' via WKD: Server indicated a failure # found warning: Recipient 'no...@example.com' is unusable, the reason is 'No specific reason given' # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data) # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable) # Failed test at t/web/crypt-gnupg.t line 380. # found warning: gpg: error retrieving 'no...@example.com' via WKD: Server indicated a failure # found warning: Recipient 'no...@example.com' is unusable, the reason is 'No specific reason given' # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data) # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable) (the messages are actually slightly different in Ubuntu). This seems pretty benign really and probably the tests should be relaxed? Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#973623:
I concocted a test case that was independent from ghc, confirmed it still reproduced with current binutils git and filed an upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=26902. I even made a little patch that fixes the problem but I don't know if it's in any way correct.
Bug#973072:
it's easy to fix the base64 related failures (patch attached) but then the build hangs for me. --- a/kubernetes/config/kube_config.py +++ b/kubernetes/config/kube_config.py @@ -97,7 +97,7 @@ if use_data_if_no_file: if self._base64_file_content: self._file = _create_temp_file_with_content( -base64.decodestring(self._data.encode())) +base64.standard_b64decode(self._data.encode())) else: self._file = _create_temp_file_with_content(self._data) if self._file and not os.path.isfile(self._file): @@ -112,7 +112,7 @@ with open(self._file) as f: if self._base64_file_content: self._data = bytes.decode( -base64.encodestring(str.encode(f.read( +base64.standard_b64encode(str.encode(f.read( else: self._data = f.read() return self._data --- a/kubernetes/config/kube_config_test.py +++ b/kubernetes/config/kube_config_test.py @@ -40,7 +40,7 @@ def _base64(string): -return base64.encodestring(string.encode()).decode() +return base64.standard_b64encode(string.encode()).decode() def _format_expiry_datetime(dt):
Bug#973061:
This trivial fix seems to fix the problem: diff -Nru nototools-0.2.13/debian/rules nototools-0.2.13/debian/rules --- nototools-0.2.13/debian/rules 2020-09-29 11:11:13.0 +1300 +++ nototools-0.2.13/debian/rules 2020-11-11 14:13:22.0 +1300 @@ -22,3 +22,4 @@ override_dh_auto_clean: dh_auto_clean rm -rf nototools.egg-info + rm nototools/_version.py But I don't really know if it's appropriate.
Bug#973623: stack overflows with ghc on ppc64el
In that case, someone should upload something like this: (master *)mwhudson@anduril:~/src/pkg/DHG_packages/p/ghc$ git diff diff --git a/p/ghc/debian/rules b/p/ghc/debian/rules index a5fd42860b..af3f8851d3 100755 --- a/p/ghc/debian/rules +++ b/p/ghc/debian/rules @@ -50,7 +50,7 @@ endif # once #901947 has been fixed. # Do the same for powerpcspe, due to https://bugs.debian.org/904915 # Do the same for sparc64, due to https://bugs.debian.org/908998 -ifneq (,$(filter mips mipsel powerpc powerpcspe sparc64, $(DEB_HOST_ARCH))) +ifneq (,$(filter mips mipsel powerpc powerpcspe ppc64el sparc64, $(DEB_HOST_ARCH))) EXTRA_CONFIGURE_FLAGS += --disable-ld-override endif but not me right now as I'm going to bed :) On Tue, 3 Nov 2020 at 20:33, Matthias Klose wrote: > the patch mentioned above is already part of bintuils 2.35.1-2. > > -- > To unsubscribe, send mail to 973623-unsubscr...@bugs.debian.org. >
Bug#973623:
I think this is a gold bug, and even better I think it is a gold bug that was fixed already, in this commit from a few weeks back: commit fa40fbe484954c560ab1c0ff4bc1b2eeb1511344 Author: Alan Modra Date: Fri Oct 9 16:56:33 2020 +1030 [GOLD] Power10 segv due to wild r2 Calling non-pcrel functions from pcrel code requires a stub to set up r2. Gold created the stub, but an "optimisation" made the stub jump to the function local entry, ie. r2 was not initialised. This patch fixes that long branch stub problem, and another that might occur for plt call stubs to local functions. bfd/ * elf64-ppc.c (write_plt_relocs_for_local_syms): Don't do local entry offset optimisation. gold/ * powerpc.cc (Powerpc_relobj::do_relocate_sections): Don't do local entry offset optimisation for lplt_section. (Target_powerpc::Branch_info::make_stub): Don't add local entry offset to long branch dest passed to add_long_branch_entry. Do pass st_other bits. (Stub_table::Branch_stub_ent): Add "other_" field. (Stub_table::add_long_branch_entry): Add "other" param, and save. (Stub_table::branch_stub_size): Adjust long branch offset. (Stub_table::do_write): Likewise. (Target_powerpc::Relocate::relocate): Likewise. In particular, it's this bit: (Target_powerpc::Branch_info::make_stub): Don't add local entry offset to long branch dest passed to add_long_branch_entry. Do pass st_other bits. Some background, if anyone cares: Most functions on ppc64 have two entry points, a global and local entry point. The global entry point is the one that is called from other shared objects, derives the "module TOC pointer" from r12 (the abi mandates that calls via a function pointer must have that pointer in r12), and stores it in r2. The local entry point assumes that r2 is already set up (and does not care about what is in r12), so most local calls look like this: 103fa688: 21 91 c0 4b bl 100037a8 <_init+0x8> (this is from __libc_csu_init from a trivial haskell executable which does not crash). But! the displacement field for the bl instruction in the ppc64 ISA is "only" 26 bits. When the target function is too far away, the linker generates a stub, like this: (gdb) disassemble 0x14dcb998 Dump of assembler code for function 0001.long_branch.10004b48: 0x14dcb990 <+0>: addis r12,r2,-1 0x14dcb994 <+4>: ld r12,32216(r12) 0x14dcb998 <+8>: mtctr r12 0x14dcb99c <+12>: bctr This derives the address of the target function from r2, puts it in r12 per abi rules and calls it. But the call to this stub in __libc_csu_init from a broken haskell executable looks like this: 0x14dc8b08 <+72>: bl 0x14dcb998 <0001.long_branch.10004b48+8> i.e. it's jumping into the middle of the stub, and so jumps straight to r12, which contains the address of __libc_csu_init itself at the moment -- and so we just recurse infinitely until we crash.
Bug#972733: python-bitstring: ftbfs now that Python 3.9 is a supported version
Source: python-bitstring Version: 3.1.5-2 Severity: normal Tags: upstream User: debian-pyt...@lists.debian.org Usertags: python3.9 Dear Maintainer, I think an upstream update will fix this. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#972730: python-mpd: merge changes from accidental NMU
Ah luckily my upload got rejected thanks to an orig mismatch. In which case please consider this bug report as a request to merge the linked branch! On Fri, 23 Oct 2020 at 15:33, Michael Hudson-Doyle wrote: > Source: python-mpd > Severity: normal > > Dear Maintainer, > > Hi, > > I got confused and thought this package was maintained by the Python > team and uploaded an autopkgtest fix. Sorry! At least the change is > hopefully non-controversial. > > I've made a merge request on salsa: > > https://salsa.debian.org/mpd-team/python-mpd/-/merge_requests/1 > > but filing the bug here to to make sure the maintainers see the change. > > Cheers, > mwh > > > -- System Information: > Debian Release: bullseye/sid > APT prefers focal-updates > APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, > 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled >
Bug#972730: python-mpd: merge changes from accidental NMU
Source: python-mpd Severity: normal Dear Maintainer, Hi, I got confused and thought this package was maintained by the Python team and uploaded an autopkgtest fix. Sorry! At least the change is hopefully non-controversial. I've made a merge request on salsa: https://salsa.debian.org/mpd-team/python-mpd/-/merge_requests/1 but filing the bug here to to make sure the maintainers see the change. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#972728: python-latexcodec: ftbfs with python 3.9 as supported version
Source: python-latexcodec Version: 1.0.7-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source User: debian-pyt...@lists.debian.org Usertags: python3.9 Dear Maintainer, I think an upstream update will fix this. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#972723: python-asttokens: fails to build from source with Python 3.9 as a supported version
Source: python-asttokens Version: 2.0.3-2 Severity: serious Tags: upstream ftbfs Justification: fails to build from source User: debian-pyt...@lists.debian.org Usertags: python3.9 Dear Maintainer, Like so: = test session starts == platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0 rootdir: /<>, inifile: setup.cfg collected 105 items tests/test_astroid.py .F...s...FF.FFF... [ 43%] tests/test_asttokens.py .. [ 49%] tests/test_line_numbers.py ... [ 52%] tests/test_mark_tokens.py ...F.F..F...FF.F.FF.FFF... [ 96%] [ 96%] tests/test_util.py [100%] === FAILURES === This is fixed in the latest upstream release but upstream has also changed some build stuff that makes an upstream update non-trivial. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#972722: pyvows: ftbfs with python 3.9
Source: pyvows Version: 3.0.0-3 Severity: serious Tags: upstream ftbfs Justification: fails to build from source User: debian-pyt...@lists.debian.org Usertags: python3.9 Dear Maintainer, Now that python 3.9 is a supported version in unstable the build fails in the following slightly alarming way: dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 in use) I: pybuild base:217: python3.9 pyvows/cli.py tests/ :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :228: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject Segmentation fault (core dumped) E: pybuild pybuild:352: test: plugin custom failed with: exit code=139: python3.9 pyvows/cli.py tests/ Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
