Bug#1069361:

[Michael Hudson-Doyle]

This is because America/Godthab was renamed to America/Nuuk in tz 2020a and
the former is now only in tzdata-legacy.

Adding tzdata-legacy to build depends fixes the build but a better fix is
probably to update libgweather4's data to follow the tz database changes.

I filed https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311
upstream about this.

Bug#1066260: mrtdreader: FTBFS: mrtdreader.c:95:41: error: implicit declaration of function ‘isprint’ [-Werror=implicit-function-declaration]

[Michael Hudson-Doyle]

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]

[Michael Hudson-Doyle]

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#1066505: epic5: FTBFS: functions.c:7547:15: error: implicit declaration of function ‘strptime’; did you mean ‘strftime’? [-Werror=implicit-function-declaration]

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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]

[Michael Hudson-Doyle]

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#1067076: x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’

[Michael Hudson-Doyle]

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(&ev.time, NULL);
++  clock_gettime(CLOCK_REALTIME, &tv);
++  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(&ev.time, NULL);
++  clock_gettime(CLOCK_REALTIME, &tv);
++  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(&ev, 0, sizeof(ev));
+-  gettimeofday(&ev.time, NULL);
++  clock_gettime(CLOCK_REALTIME, &tv);
++  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(&ev, 0, sizeof(ev));
+-  gettimeofday(&ev.time, NULL);
++clock_gettime(CLOCK_REALTIME, &tv);
++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-se

Bug#1066794:

[Michael Hudson-Doyle]

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 *)’

[Michael Hudson-Doyle]

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]

[Michael Hudson-Doyle]

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#1067203: user-session-migration: fix ftbfs on architectures affected by t64 transition

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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#1061493: consolekit: install PAM module and udev files into /usr

[Michael Hudson-Doyle]

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#1065278: gtkmm3.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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#1065284: lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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#1065265: glade: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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#1065252: glibmm2.68: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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#1065277: gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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#1065269: glibmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

Thanks for being so accommodating! A lot of disruption to go around...

Bug#1062545:

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

(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#1053111: Fwd:

[Michael Hudson-Doyle]

(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#1062928:

[Michael Hudson-Doyle]

FWIW adding a quirk to the analysis confirms that this package is
unaffected by both the lfs and time_t transitions.

Bug#1062744:

[Michael Hudson-Doyle]

Sigh, attached to *this* mail


nmu_libzypp.debdiff
Description: Binary data

Bug#1062744:

[Michael Hudson-Doyle]

I've just reuploaded the package to experimental, new debdiff attached.

Bug#1062744:

[Michael Hudson-Doyle]

> 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#1064298:

[Michael Hudson-Doyle]

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#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs

[Michael Hudson-Doyle]

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#1061063:

[Michael Hudson-Doyle]

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(&size, &in_vlen[0].len, sizeof(size_t))
++memcpy(&data, &in_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:

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

> 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:

[Michael Hudson-Doyle]

Apologies, previous version of patch was incorrect.


nmu_compiz.debdiff
Description: Binary data

Bug#1061899: closing 1061899

[Michael Hudson-Doyle]

close 1061899 
thanks

Bug#1061882:

[Michael Hudson-Doyle]

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#984205:

[Michael Hudson-Doyle]

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#997877:

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

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#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

[Michael Hudson-Doyle]

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)

[Michael Hudson-Doyle]

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#988905:

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

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#973087: closing 973087

[Michael Hudson-Doyle]

close 973087 2.4.11-3
thanks

I fixed this in version 2.4.11-3 but forgot to include the bug in the
changelog.

Bug#973072:

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

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#973165: marked as pending in pyflakes

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #973165 in pyflakes reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pyflakes/-/commit/af0a78554d3b10d885446d0dea3e989c3e57f62c


d/patches/0001-Fix-test-for-nightly-Python-3.9-532.patch, 
d/patches/0002-Fix-tests-with-Python-3.9-closes-549-586.patch: Cherry pick 
fixes from upstream to fix test failures with Python 3.9 (Closes: #973165)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973165

Bug#973623: stack overflows with ghc on ppc64el

[Michael Hudson-Doyle]

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:

[Michael Hudson-Doyle]

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#972926: marked as pending in celery

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #972926 in celery reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/celery/-/commit/33e11179c542febad5d84f2ff4b2a719c35e2bf1


d/tests/upstream: Use celery pytest plugin for autopkgtest too.  (Closes: 
#972926)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/972926

Bug#972728: python-latexcodec: ftbfs with python 3.9 as supported version

[Michael Hudson-Doyle]

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

[Michael Hudson-Doyle]

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#972721: python-httpretty: ftbfs with python3.9 as supported version

[Michael Hudson-Doyle]

Source: python-httpretty
Version: 0.9.5-7
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source

Dear Maintainer,

Now that python 3.9 is a supported version, the tests fail with:

==
ERROR: fakesock.socket#makefile should set the mode, bufsize and return its 
mocked file descriptor
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
  File 
"/<>/.pybuild/cpython3_3.9_httpretty/build/tests/unit/test_core.py",
 line 256, in test_fakesock_socket_makefile
fd = socket.makefile(mode='rw', bufsize=512)
  File 
"/<>/.pybuild/cpython3_3.9_httpretty/build/httpretty/core.py", 
line 438, in makefile
if t.isAlive():
AttributeError: 'Thread' object has no attribute 'isAlive'

This appears to be fixed upstream
(https://github.com/gabrielfalcao/HTTPretty/commit/259a9a4f7514096daa008d3bf14e4b782cafae72)
and an upstream update would fix this but I haven't checked if an update
would be disruptive to other packages yet.

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

[Michael Hudson-Doyle]

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

Bug#972232:

[Michael Hudson-Doyle]

As this is blocking the Python 3.9 transition now, can the fix from
upstream be uploaded?

Bug#969596:

[Michael Hudson-Doyle]

The attached patch appears to fix the build in Ubuntu.
diff -Nru minimap2-2.17+dfsg/debian/changelog minimap2-2.17+dfsg/debian/changelog
--- minimap2-2.17+dfsg/debian/changelog	2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/changelog	2020-09-15 12:34:50.0 +1200
@@ -1,3 +1,10 @@
+minimap2 (2.17+dfsg-11ubuntu1) groovy; urgency=medium
+
+  * d/patches/python-sse4-arch.patch: Only pass -msse4.1 to the compiler on
+amd64.
+
+ -- Michael Hudson-Doyle   Tue, 15 Sep 2020 12:34:50 +1200
+
 minimap2 (2.17+dfsg-11) unstable; urgency=medium
 
   * Add lintian-override
diff -Nru minimap2-2.17+dfsg/debian/control minimap2-2.17+dfsg/debian/control
--- minimap2-2.17+dfsg/debian/control	2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/control	2020-09-15 12:34:50.0 +1200
@@ -1,5 +1,6 @@
 Source: minimap2
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Andreas Tille 
 Section: science
 Priority: optional
diff -Nru minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch
--- minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch	1970-01-01 12:00:00.0 +1200
+++ minimap2-2.17+dfsg/debian/patches/python-sse4-arch.patch	2020-09-15 12:34:50.0 +1200
@@ -0,0 +1,11 @@
+--- a/setup.py
 b/setup.py
+@@ -26,7 +26,7 @@
+ if platform.machine() in ["aarch64", "arm64"]:
+ 	include_dirs.append("sse2neon/")
+ 	extra_compile_args.extend(['-ftree-vectorize', '-DKSW_SSE2_ONLY', '-D__SSE2__'])
+-else:
++elif platform.machine() == "x86_64":
+ 	extra_compile_args.append('-msse4.1') # WARNING: ancient x86_64 CPUs don't have SSE4
+ 
+ def readme():
diff -Nru minimap2-2.17+dfsg/debian/patches/series minimap2-2.17+dfsg/debian/patches/series
--- minimap2-2.17+dfsg/debian/patches/series	2020-07-07 21:32:26.0 +1200
+++ minimap2-2.17+dfsg/debian/patches/series	2020-09-15 12:34:42.0 +1200
@@ -3,3 +3,4 @@
 simde
 ar.patch
 link_mappy_to_libminimap.patch
+python-sse4-arch.patch

Bug#952227: marked as pending in golang-gopkg-gcfg.v1

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #952227 in golang-gopkg-gcfg.v1 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-gopkg-gcfg.v1/-/commit/162c60c3cf494e6a317536d6d397420f854c6791


d/patches/fix-tests-go1.13.patch: fix tests that fail with changed 
strconv.ParseInt behavior in Go 1.13. (Closes: #952227)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952227

Bug#964047: marked as pending in golang-github-src-d-gcfg

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #964047 in golang-github-src-d-gcfg reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-src-d-gcfg/-/commit/fcdd8230a2f295ed61cabd75e46dd755cf8cb4af


d/patches/fix-tests-go1.13.patch: fix tests that fail with changed 
strconv.ParseInt behavior in Go 1.13. (Closes: #964047)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964047

Bug#959643:

[Michael Hudson-Doyle]

FWIW there is a new release (1.0.7) available and that seems to fix this
failure (in Ubuntu, anyway).

Bug#961581: pbcopper: ftbfs on ppc64el

[Michael Hudson-Doyle]

On Tue, 26 May 2020 at 23:43, Andreas Tille  wrote:

> thanks for the patch.  I've uploaded pbcopper to new since
> it needed a soname bump and thus a new binary package name.
>

Thanks. I think a fixed simde has been uploaded now, so my patch might not
be needed at all...

Bug#961581: pbcopper: ftbfs on ppc64el

[Michael Hudson-Doyle]

Source: pbcopper
Version: 1.6.0+dfsg-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

As can be seen on 

https://buildd.debian.org/status/logs.php?pkg=pbcopper&arch=ppc64el

pbcopper currently ftbfs on pcp64el. I think this is a bug in simde:

https://github.com/nemequ/simde/issues/325

but anyway, I'm attaching the workaround I just uploaded to Ubuntu.

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-31-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
--- a/src/align/cssw/ssw.c
+++ b/src/align/cssw/ssw.c
@@ -35,6 +35,9 @@
  *
  */
 
+#ifdef __powerpc64__
+#define SIMDE_NO_NATIVE
+#endif
 #define SIMDE_ENABLE_NATIVE_ALIASES
 #include "simde/x86/sse2.h"
 #include 
--- a/src/align/cssw/ssw.h
+++ b/src/align/cssw/ssw.h
@@ -11,6 +11,9 @@
 #ifndef SSW_H
 #define SSW_H
 
+#ifdef __powerpc64__
+#define SIMDE_NO_NATIVE
+#endif
 #define SIMDE_ENABLE_NATIVE_ALIASES
 #include "simde/x86/sse2.h"
 #include 

Bug#949919: libgpiod: ftbfs; needs explicit dependency on dh-python

[Michael Hudson-Doyle]

Source: libgpiod
Version: 1.4.1-3
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Hi, the package fails to build in sid. It now needs an explicit
dependency on dh-python. I'll attach a patch, but really: it's trivial.

Cheers,
mwh

-- System Information:
Debian Release: buster/sid
  APT prefers eoan-updates
  APT policy: (500, 'eoan-updates'), (500, 'eoan'), (400, 'eoan-proposed'), 
(100, 'eoan-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-26-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 libgpiod-1.4.1/debian/changelog libgpiod-1.4.1/debian/changelog
--- libgpiod-1.4.1/debian/changelog 2019-09-10 21:02:05.0 +1200
+++ libgpiod-1.4.1/debian/changelog 2020-01-27 14:14:51.0 +1300
@@ -1,3 +1,9 @@
+libgpiod (1.4.1-4) UNRELEASED; urgency=medium
+
+  * Add explicit build dependency on dh-python.
+
+ -- Michael Hudson-Doyle   Mon, 27 Jan 2020 14:14:51 +1300
+
 libgpiod (1.4.1-3) unstable; urgency=medium
 
   * d/control:
diff -Nru libgpiod-1.4.1/debian/control libgpiod-1.4.1/debian/control
--- libgpiod-1.4.1/debian/control   2019-09-10 20:50:54.0 +1200
+++ libgpiod-1.4.1/debian/control   2020-01-27 14:13:09.0 +1300
@@ -5,6 +5,7 @@
 Build-Depends: debhelper-compat (= 12),
autoconf-archive,
automake,
+   dh-python,
help2man,
pkg-config,
m4,

Bug#942757: odb-api: fails to build with multiple supported python3 versions

[Michael Hudson-Doyle]

Source: odb-api
Version: 0.18.1-7
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

odb-api fails to build when multpile python3 versions are supported, as
is the case in Ubuntu Focal currently, like this:

for f in `py3versions --supported | sed -e 's%python3.7%%'  ` ; do \
/usr/bin/make -C /<>/debian/build/$f 
DESTDIR=/<>/debian/tmp ; \
done
make[2]: Entering directory '/<>'
make[2]: *** /<>/debian/build/python3.8: No such file or 
directory.  Stop.
make[2]: Leaving directory '/<>'

(full log here:
https://launchpadlibrarian.net/447773633/buildlog_ubuntu-focal-amd64.odb-api_0.18.1-7build1_BUILDING.txt.gz)

It seems to me that the code that runs to configure the package for
other python versions is just wrong: it uses $$d in the argument to
--builddirectory which is not defined anywhere, it passed
--builddirectory to dh_auto_configure after "--" (so it is passed to the
upstream configure script, not dh) and it sets the build directory to be
a subdirectory of the "default" build directory. I don't know if this
last point is an actual problem (although it does smell funny to me),
but this patch fixes this anyway, as well as the other two problems.

Cheers,
mwh
-- System Information:
Debian Release: buster/sid
  APT prefers eoan
  APT policy: (500, 'eoan'), (400, 'eoan-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-18-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru odb-api-0.18.1/debian/rules odb-api-0.18.1/debian/rules
--- odb-api-0.18.1/debian/rules 2019-09-02 04:48:13.0 +1200
+++ odb-api-0.18.1/debian/rules 2019-10-21 14:17:49.0 +1300
@@ -55,14 +55,14 @@
done
dh_auto_configure --  ${CMAKE_CFLAGS} 
-DPYTHON_EXECUTABLE=/usr/bin/${PY3DEFAULT}
for f in ${PY3OTHERS} ; do \
-   dh_auto_configure --  ${CMAKE_CFLAGS} 
-DPYTHON_EXECUTABLE=/usr/bin/$$f \
---builddirectory=$(BUILDDIR)/$$d ; \
+   dh_auto_configure --builddirectory=$(BUILDDIR)-$$f \
+ -- ${CMAKE_CFLAGS} -DPYTHON_EXECUTABLE=/usr/bin/$$f; \
done
 
 override_dh_auto_build:
$(MAKE) -C $(BUILDDIR) DESTDIR=$(DESTDIR)
for f in ${PY3OTHERS} ; do \
-   $(MAKE) -C $(BUILDDIR)/$$f DESTDIR=$(DESTDIR) ; \
+   $(MAKE) -C $(BUILDDIR)-$$f DESTDIR=$(DESTDIR) ; \
done
 
 override_dh_auto_test:

Bug#924630: Bug #924630 in golang marked as pending

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #924630 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/commit/71582deb22213b82603e44203245ada54977355f


New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)

* New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)
* Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied
  upstream.
* Refreshed other patches.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/924630

Bug#924630: Bug #924630 in golang marked as pending

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #924630 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/commit/71582deb22213b82603e44203245ada54977355f


New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)

* New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)
* Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied
  upstream.
* Refreshed other patches.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/924630

Bug#924630: Bug #924630 in golang marked as pending

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #924630 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/commit/0c508f9cd760bd475f41b8d067359da313cbd05c


New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)

* New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)
* Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied
  upstream.
* Refreshed other patches.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/924630

Bug#924630: Bug #924630 in golang marked as pending

[Michael Hudson-Doyle]

Control: tag -1 pending

Hello,

Bug #924630 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/commit/0c508f9cd760bd475f41b8d067359da313cbd05c


New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)

* New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630)
* Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied
  upstream.
* Refreshed other patches.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/924630

Bug#917797:

[Michael Hudson-Doyle]

Ah yes this was indeed fixed by 2.37-1 or something around there but we
forgot to mention this bug in the changelog. Thanks for the reminder!

Bug#921284: build-using should only include copylefted files

[Michael Hudson-Doyle]

On Thu, 7 Feb 2019 at 04:09, Antoine Beaupré  wrote:

> On 2019-02-03 17:21:35, Antoine Beaupre wrote:
> > My first submissions for the dmarc-cat package (#920385) were refused
> > by the FTP masters because the built-using field did not respect §7.8
> > of the Debian policy.
>
> That's actually inaccurate: the package was refused because the
> dependencies specified in `built-using` were missing and indeed, one of
> the dependencies hadn't passed NEW when dmarc-cat was uploaded. For
> example, here's the last REJECTION I had:
>
> An exception was raised while processing the package:
> Traceback (most recent call last):
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 109,
> in wrapper
> function(upload, srcqueue, comments, transaction)
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 222,
> in comment_accept
> extra_archives=[upload.target_suite.archive],
>   File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 451,
> in copy_binary
> self._ensure_extra_source_exists(filename, db_source, archive,
> extra_archives=extra_archives)
>   File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 245,
> in _ensure_extra_source_exists
> raise ArchiveException('{0}: Built-Using refers to package {1} (= {2})
> not in target archive {3}.'.format(filename, source.source, source.version,
> archive.archive_name))
> ArchiveException: d/dmarc-cat/dmarc-cat_0.9.1-1_amd64.deb: Built-Using
> refers to package golang-github-ivpusic-grpool (= 1.0.0-1) not in target
> archive ftp-master.
>
> When grpool was ACCEPTED, dmarc-cat also was ACCEPTED by the
> FTP-masters. So this is not a blocker for the FTP masters.
>
> > Extract from #debian-ftp:
> >
> > 16:55:59  Built-Using is only meant to be used when the result
> is GPL/MPL/similar and you've statically linked (/bundled) another source
> package
> > 16:56:33  okay, so to comply with licensing issues?
> > 16:56:47  it also seems useful to track rdeps for golang as
> well, no?
> > 16:57:03  no, built-using is _not_ for tracking dependencies
> > 16:57:10  it is for license compliance
> > 16:57:26  and bsd licensed software does not require that
> >
> > So in the case of dmarc-cat, dependencides like
> > golang-github-stretchr-testify-dev should actually not be listed in
> > the Built-Using field.
>
> It's true, however, that the Debian policy specifies built-using is for
> copyright reasons.
>
>
> https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
>
> Specifically, the last pargraph reads:
>
> > This field should not be added solely for purposes other than
> > satisfying license or DFSG requirements to provide full source
> > code. In particular, it should not be added solely to enable finding
> > packages that should be rebuilt against newer versions of their build
> > dependencies.
>
> Yet, from what I understand, that is *exactly* how that field is used in
> the golang team. Is that correct?
>
> It should be noted this is a SHOULD NOT and not a MUST NOT, so it's a
> little more relaxed - may we are allowed to abuse it like this.
>
> I do wonder if it's deliberate, however. It seems to me this should be
> clarified, both in dh-golang and in policy, either way.
>

It's a pretty recent change in policy to clarify that how go packages use
it is not the intended use. When go packages started using Built-Using,
they were 100% compliant with the wording (if not the intent) of policy :)

Cheers,
mwh

Bug#912150: Processed: Joining with the existing scipy bug

[Michael Hudson-Doyle]

FWIW we fixed most of the problems in the scipy/imexam/s390x area on Ubuntu
by building scipy with gfortran-7 rather than gfortran-8 on s390x. AFAIK we
haven't gotten around to working out what it is gfortran-8 is doing wrong
yet.

Bug#911276: elfutils: ftbfs on arm64 with gcc-8

[Michael Hudson-Doyle]

Source: elfutils
Version: 0.170-0.4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

elfutils ftbfs on sid on arm64 currently. Current git passes, and git
bisect and logic point to the following upstream commit as fixing it:

commit f881459ffc95b6fad51aa055a158ee14814073aa
Author: Mark Wielaard 
Date:   Wed Apr 11 10:37:45 2018 +0200

aarch64: Add default cfi rule to restore SP from CFA address.

The CFA is set by default to the stack pointer of the previous frame.
So that is also how we can always restore the SP. This default aarch64
CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh
and run-backtrace-dwarf.sh testcases work.

Signed-off-by: Mark Wielaard 

so this bug can be closed either with an upstream update (this patch is
in 0.171) or a cherry pick of the above commit.

Cheers,
mwh

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (400, 'bionic-proposed'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-36-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#906198:

[Michael Hudson-Doyle]

So strangely enough, I don't see this failure on Ubuntu, the only test test
that failed for me is

__ test_gauss_center
___

def test_gauss_center():
"""Check the gaussian center fitting."""
# make a 2d dataset with a gaussian at the center
from astropy.convolution import Gaussian2DKernel
gaussian_2D_kernel = Gaussian2DKernel(10)
plots = Imexamine()
plots.set_data(gaussian_2D_kernel.array)
a, xx, yy, xs, ys = plots.gauss_center(37, 37)

amp = 0.0015915494309189533
xc = 40.0
yc = 40.0
xsig = 10.0
ysig = 10.0

>   assert_allclose(amp, a, 1e-6)
E   AssertionError:
E   Not equal to tolerance rtol=1e-06, atol=0
E
E   (mismatch 100.0%)
Ex: array(0.001592)
Ey: array(0.000447)

imexam/tests/test_imexamine.py:114: AssertionError
- Captured stdout call
-
xc=37.001304yc=37.001304

Do you have any idea what's causing this failure? :)

I say strangely because I thought Ubuntu and Debian were mostly in sync on
this stack...

Bug#897857:

[Michael Hudson-Doyle]

On Fri, 10 Aug 2018 at 09:37, Olly Betts  wrote:

> On Thu, Aug 02, 2018 at 09:23:26PM +1200, Michael Hudson-Doyle wrote:
> > upstream just "fixed" this by disabling the warning, fwiw
>
> This bug was reported in setools but reassigned to swig - I think you
> must mean "setools" by "upstream" there?
>

Ah yes. Sorry for the lack of clarity.


> I actually addressed this upstream in SWIG back in May (by fixing the
> generated code rather than disabling the warning), but there's not
> been a release in a while.  I'll take a look and see if the fix can be
> backported to the Debian package.  The potential problem is that it was
> after clean-up of support for older Python versions, and it seems
> unhelpful in the wider context for the Debian swig package to generate
> code which supports a narrower range of Python versions than the
> corresponding upstream SWIG version.
>

Hm yes. On some level it would be fine to only support versions of Python
supported by Debian, but on another that would be a bit hostile.


> Ignoring the warning is reasonable.  The code in question does invoke
> undefined behaviour, but it should be safe in practice with the calling
> conventions used on Linux.
>

I agree.


> Compiling packages with -Werror seems unwise in general, but I really
> wouldn't recommend compiling SWIG-generated code in packages with
> -Werror.
>

Totally agree! It's fine to use it during development but using it in
distributed source is just a timebomb.

Cheers,
mwh

Bug#897857:

[Michael Hudson-Doyle]

upstream just "fixed" this by disabling the warning, fwiw

Bug#902597:

[Michael Hudson-Doyle]

I cherry picked the attached patch from upstream (which tbh, is a bit
hilarious) to fix the build in Ubuntu.

I also had to add libgmock-dev to build-depends, but i don't know if that's
needed in debian.
From 5c42943e75231b79f4ffcc37a22f0077a2fb0e7d Mon Sep 17 00:00:00 2001
From: Ben Webb 
Date: Tue, 3 Jul 2018 09:51:09 -0700
Subject: [PATCH] Add Python 3.7 compatibility

Compilation of Python wrappers fails with Python 3.7 because
the Python folks changed their C API such that
PyUnicode_AsUTF8AndSize() now returns a const char* rather
than a char*. Add a patch to work around. Relates #4086.
---
 python/google/protobuf/pyext/descriptor.cc| 2 +-
 python/google/protobuf/pyext/descriptor_containers.cc | 2 +-
 python/google/protobuf/pyext/descriptor_pool.cc   | 2 +-
 python/google/protobuf/pyext/extension_dict.cc| 2 +-
 python/google/protobuf/pyext/message.cc   | 4 ++--
 5 files changed, 6 insertions(+), 6 deletions(-)

--- a/python/google/protobuf/pyext/descriptor.cc
+++ b/python/google/protobuf/pyext/descriptor.cc
@@ -54,7 +54,7 @@
   #endif
   #define PyString_AsStringAndSize(ob, charpp, sizep) \
 (PyUnicode_Check(ob)? \
-   ((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
+   ((*(charpp) = const_cast(PyUnicode_AsUTF8AndSize(ob, (sizep == NULL? -1: 0): \
PyBytes_AsStringAndSize(ob, (charpp), (sizep)))
 #endif
 
--- a/python/google/protobuf/pyext/descriptor_containers.cc
+++ b/python/google/protobuf/pyext/descriptor_containers.cc
@@ -66,7 +66,7 @@
   #endif
   #define PyString_AsStringAndSize(ob, charpp, sizep) \
 (PyUnicode_Check(ob)? \
-   ((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
+   ((*(charpp) = const_cast(PyUnicode_AsUTF8AndSize(ob, (sizep == NULL? -1: 0): \
PyBytes_AsStringAndSize(ob, (charpp), (sizep)))
 #endif
 
--- a/python/google/protobuf/pyext/descriptor_pool.cc
+++ b/python/google/protobuf/pyext/descriptor_pool.cc
@@ -47,7 +47,7 @@
   #endif
   #define PyString_AsStringAndSize(ob, charpp, sizep) \
 (PyUnicode_Check(ob)? \
-   ((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
+   ((*(charpp) = const_cast(PyUnicode_AsUTF8AndSize(ob, (sizep == NULL? -1: 0): \
PyBytes_AsStringAndSize(ob, (charpp), (sizep)))
 #endif
 
--- a/python/google/protobuf/pyext/message.cc
+++ b/python/google/protobuf/pyext/message.cc
@@ -81,7 +81,7 @@
 (PyUnicode_Check(ob)? PyUnicode_AsUTF8(ob): PyBytes_AsString(ob))
   #define PyString_AsStringAndSize(ob, charpp, sizep) \
 (PyUnicode_Check(ob)? \
-   ((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
+   ((*(charpp) = const_cast(PyUnicode_AsUTF8AndSize(ob, (sizep == NULL? -1: 0): \
PyBytes_AsStringAndSize(ob, (charpp), (sizep)))
   #endif
 #endif
@@ -1415,7 +1415,7 @@
 return NULL;
   }
 #else
-  field_name = PyUnicode_AsUTF8AndSize(arg, &size);
+  field_name = const_cast(PyUnicode_AsUTF8AndSize(arg, &size));
   if (!field_name) {
 return NULL;
   }

Bug#903525:

[Michael Hudson-Doyle]

fwiw i think the 9.0.0 release fixes this. Although it still has a stub
async.py file and I can't remember how to not bytecompile that with python
3.7 -- I know it's possible though...

Bug#903923:

[Michael Hudson-Doyle]

The fix is just to build-depend on python3-all-dev rather than python3-dev.

Bug#892088: [pkg-golang-devel] Bug#892088: golang-1.10: FTBFS on mips when built on Octeon III buildds

[Michael Hudson-Doyle]

Congrats on figuring this out and commiserations on having to do it, I
guess! Do you think this is worth an upload now or will it be OK to wait
until upstream releases 1.10.1 (assuming it gets into that)?

Cheers,
mwh

Bug#887067:

[Michael Hudson-Doyle]

This was just a test flake, a rebuild fixed it. I'll make sure upstream know!


signature.asc
Description: PGP signature

Bug#886431: snapd binary-all FTBFS: install: failed to access debian/snapd///usr/lib/snapd: No such file or directory

[Michael Hudson-Doyle]

Thanks for the report. This is fixed in git, will wait until my
gopkg.in/mgo.v2 upload for the 32 bit issues gets published before
uploading.

On 6 January 2018 at 10:59, Adrian Bunk  wrote:

> Source: snapd
> Version: 2.30-1
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=snapd&;
> arch=all&ver=2.30-1&stamp=1515103055&raw=0
>
> ...
> /usr/bin/make -C systemd install
> make[3]: Entering directory '/<>/data/systemd'
> # NOTE: old (e.g. 14.04) GNU coreutils doesn't -D with -t
> install -d -m 0755 /<>/debian/snapd//lib/systemd/system/
> install -m 0644 -t /<>/debian/snapd//lib/systemd/system/
> snapd.refresh.service snapd.core-fixup.service snapd.autoimport.service
> snapd.snap-repair.service snapd.service snapd.system-shutdown.service
> snapd.refresh.timer snapd.snap-repair.timer snapd.socket
> install -m 0755 -t /<>/debian/snapd///usr/lib/snapd
> snapd.core-fixup.sh
> install: failed to access '/<>/debian/snapd///usr/lib/snapd':
> No such file or directory
> Makefile:36: recipe for target 'install' failed
> make[3]: *** [install] Error 1
>
>

Bug#867058: [pkg-golang-devel] Bug#867058: golang-1.8 and mips*

[Michael Hudson-Doyle]

On 27 October 2017 at 22:38, James Cowgill  wrote:

> Hi,
>
> On 26/10/17 20:33, John Paul Adrian Glaubitz wrote:
> > On 10/26/2017 07:12 PM, peter green wrote:
> >> Therefore golang maintainers you have two choices.
> >>
> >> 1. Accept John's changes so that your package can be built on mips*.
> >> 2. File a removal request for the binaries uploaded by John
> >
> > I assume that gccgo on mips is still broken as this situation hasn't
> changed,
> > so I would suggest removing the packages again. I can file a bug for that
> > since I am the one who is responsible that these packages are there in
> the
> > first place.
>
> gccgo was fixed in gcc-7 a few weeks ago and I've filed a bug against
> golang-1.9 already. Since golang-defaults already points to golang-1.9
> in unstable, I am guessing that older versions are now irrelevant for mips.
>
> I suggest:
> - Apply the patch in #879764 to golang-1.9.
>

LGTM.


> - Remove the mips binaries from golang-1.8 (or remove 1.8 entirely).
>

I think we should remove the mips binaries.


> - Enable mips in golang-defaults.
>

+1


> A reply from the golang maintainers would be very helpful in all of this...
>

Sorry for the lack of response. I have to admit that I've found the whole
issue very confusing to follow but I'm very grateful to the people who've
put the effort in to make the simple patch attached to #879764 all that is
required!

Cheers,
mwh

Bug#876862:

[Michael Hudson-Doyle]

This is another of those "only happens on reproducible-builds" mysteries.
It builds fine for me.

Reducing severity to normal.

Bug#876923: closing 876923

[Michael Hudson-Doyle]

close 876923 
thanks

I uploaded 0.0+git20161208.0.20d25e2-2 before I saw this and it built fine. I
do not understand what is going on but I think it is some kind of problem with
reproducible builds rather than this package.

Bug#871344: [pkg-golang-devel] Bug#871344: golang-1.6: FTBFS: test fails

[Michael Hudson-Doyle]

On 9 August 2017 at 05:19, Tianon Gravi  wrote:

> On 7 August 2017 at 08:51, Lucas Nussbaum  wrote:
> > Source: golang-1.6
> > Version: 1.6.3-1
> > Severity: serious
> > Tags: buster sid
>
> This has me a bit confused -- there's no "golang-1.6" in sid (or
> buster) that I can find:
>
> - https://packages.debian.org/sid/source/golang-1.6
> - https://packages.debian.org/buster/source/golang-1.6
>
> Am I looking in the wrong place?  Do we need to file an RM bug?
>

We've been over this before :-)

golang-1.6 is kept in Sources by (bogus) Built-Using headers:

$ grep-dctrl -sPackage,Version,Extra-Source-Only -FPackage -w golang-1.6
 
~/.chdist/sid/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_source_Sources
Package: golang-1.6
Version: 1.6.2-1
Extra-Source-Only: yes

Package: golang-1.6
Version: 1.6.2-2
Extra-Source-Only: yes

Package: golang-1.6
Version: 1.6.3-1
Extra-Source-Only: yes

It's actually not too bad, only 16 packages left now:

$ grep-dctrl -sPackage,Version,Architecture -FBuilt-Using 'golang-1.6 (=
1.6.2-1)' --or -FBuilt-Using 'golang-1.6 (= 1.6.2-2)' --or -FBuilt-Using
'golang-1.6 (= 1.6.3-1)'
 
~/.chdist/sid/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-amd64_Packages
Package: golang-github-shiguredo-fuji-dev
Version: 1.0.2-1
Architecture: all

Package: golang-github-asaskevich-govalidator-dev
Version: 4-1
Architecture: all

Package: golang-github-fsouza-go-dockerclient-dev
Version: 0.0+git20160622-1
Architecture: all

Package: golang-github-go-ldap-ldap-dev
Version: 2.4.1-1
Architecture: all

Package: golang-github-gosimple-slug-dev
Version: 1.0.2-1
Architecture: all

Package: golang-github-kolo-xmlrpc-dev
Version: 0+git20150413.0826b98-2
Architecture: all

Package: golang-github-odeke-em-cache-dev
Version: 0.0~git20151107.0.baf8e436-1
Architecture: all

Package: golang-github-odeke-em-cli-spinner-dev
Version: 0.0~git20150423.610063b-2
Architecture: all

Package: golang-github-odeke-em-command-dev
Version: 0.0~git20151021.0.91ca5ec-1
Architecture: all

Package: golang-github-odeke-em-ripper-dev
Version: 0.0~git20150415.0.bd1a682-2
Architecture: all

Package: ripper
Version: 0.0~git20150415.0.bd1a682-2
Architecture: amd64

Package: golang-github-svent-go-flags-dev
Version: 1-1
Architecture: all

Package: golang-gopkg-mgo.v2-dev
Version: 2016.02.04-1
Architecture: all

Package: nomad
Version: 0.4.0+dfsg-1
Architecture: amd64

Package: systemd-docker
Version: 0.2.1+dfsg-2
Architecture: amd64

Package: toxiproxy-dev
Version: 2.0.0+dfsg1-3
Architecture: all

Cheers,
mwh

Bug#868905: [htcondor-debian] Bug#868905:

[Michael Hudson-Doyle]

Hi, sorry about that, it's also possible I screwed up somehow. Here it is
again.

On 26 July 2017 at 23:56, Tim Theisen  wrote:

> Hi Michael,
>
> Could you send the patch the me directly? The bug tracking system
> apparently stripped the patch from the message.
>
> Thank you for looking into this. I was about to start working on this
> problem. I'd like to get this resolved soon.
>
> ...Tim
>
> On 07/25/2017 08:48 PM, Michael Hudson-Doyle wrote:
>
> I fixed this in Ubuntu with this patch:
>
>
>
> ___
> htcondor-debian mailing 
> listhtcondor-deb...@cs.wisc.eduhttps://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian
>
>
> --
> Tim Theisen
> Release Manager
> HTCondor & Open Science Grid
> Center for High Throughput Computing
> Department of Computer Sciences
> University of Wisconsin - Madison
> 4261 Computer Sciences and Statistics
> 1210 W Dayton St
> Madison, WI 53706-1685+1 608 265 5736 <(608)%20265-5736>
>
>


fix_linker_script
Description: Binary data

Bug#868905:

[Michael Hudson-Doyle]

I fixed this in Ubuntu with this patch:

Bug#867496:

[Michael Hudson-Doyle]

I think this is all it takes to fix the build:

mwhudson@aeglos:/opt/opensource/deb/py36/morse-simulator-1.4$ cat
debian/patches/fix-ftbfs.diff
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -237,6 +237,7 @@
${CMAKE_CURRENT_SOURCE_DIR}/doc/man
${SPHINX_MAN_OUTPUT} &&
   ${GZIP} -f ${SPHINX_MAN_OUTPUT}/*.1)
+ ADD_DEPENDENCIES(man revisiontag)
  INSTALL(FILES ${SPHINX_MAN_OUTPUT}/morse.1.gz
   ${SPHINX_MAN_OUTPUT}/morse-run.1.gz
   ${SPHINX_MAN_OUTPUT}/morse-create.1.gz

I guess this should be reported upstream, will do that later today I guess.

There is still a problem though, because the orig tarball is from the git
tag not the release tarball from
ftp://ftp.openrobots.org/pub/openrobots/morse/ there is no version.py in
the orig and the version reported in version.py is bogus:

mwhudson@scw-4e4aeb:~$ cat x/usr/lib/python3/dist-packages/morse/version.py
VERSION="UNKNOWN-dirty"
PROJECT_STABLE=False

I only care about the ftbfs today though :)

Bug#865926: jsonpickle: ftbfs with python3.6, please upgrade to 0.9.4

[Michael Hudson-Doyle]

The recently released 0.9.5 does pass tests with python 3.6.

On 26 June 2017 at 10:26, Michael Hudson-Doyle 
wrote:

> Source: jsonpickle
> Version: 0.9.3-1
> Severity: normal
> User: debian-pyt...@lists.debian.org
> Usertags: python3.6
>
> Dear Maintainer,
>
> jsonpickle fails to build when Python 3.6 is a supported version, as the
> current development version of Ubuntu. The 0.9.4 upstream release builds
> fine
> though, so it would be good to update to that in preparation for the
> Python 3.6
> transition in unstable.
>
> Cheers,
> mwh
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers xenial-updates
>   APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
> 'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.4.0-81-generic (SMP w/4 CPU cores)
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>

Bug#867522:

[Michael Hudson-Doyle]

Attaching a patch to fix this.
diff -Nru pytest-pylint-0.6.0/debian/changelog 
pytest-pylint-0.6.0/debian/changelog
--- pytest-pylint-0.6.0/debian/changelog2016-08-02 17:56:04.0 
+1200
+++ pytest-pylint-0.6.0/debian/changelog2017-07-19 15:25:40.0 
+1200
@@ -1,3 +1,10 @@
+pytest-pylint (0.6.0-2) UNRELEASED; urgency=medium
+
+  * Prevent tests in the debian/$pkg directories from being collected when
+running the tests.
+
+ -- Michael Hudson-Doyle   Wed, 19 Jul 2017 
15:25:09 +1200
+
 pytest-pylint (0.6.0-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru pytest-pylint-0.6.0/debian/rules pytest-pylint-0.6.0/debian/rules
--- pytest-pylint-0.6.0/debian/rules2016-08-02 17:56:04.0 +1200
+++ pytest-pylint-0.6.0/debian/rules2017-07-19 15:25:52.0 +1200
@@ -10,7 +10,7 @@
 
 override_dh_auto_install:
dh_auto_install
-   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x" 
dh_auto_test
+   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x 
--ignore debian" dh_auto_test
# run tests after install: plugin needs to get registered by 
setup.py/entry_points
 
 override_dh_installchangelogs:

Bug#866543:

[Michael Hudson-Doyle]

uscan / uupdate and the attached patch to the debian directory fixes this
for me.
diff -Nru xcffib-0.4.2/debian/changelog xcffib-0.5.1/debian/changelog
--- xcffib-0.4.2/debian/changelog   2016-09-19 22:59:15.0 +1200
+++ xcffib-0.5.1/debian/changelog   2017-07-13 15:37:48.0 +1200
@@ -1,3 +1,11 @@
+xcffib (0.5.1-1) UNRELEASED; urgency=medium
+
+  * New upstream release. (Closes: #866543, #839314)
+  * d/patches/fix-big-endian-machines.patch: drop, included upstream.
+  * d/control: Add Build-Depends on libghc-semigroups-dev, libghc-either-dev.
+
+ -- Michael Hudson-Doyle   Thu, 13 Jul 2017 
15:14:31 +1200
+
 xcffib (0.4.2-2) unstable; urgency=medium
 
   * Removed unnecessary depends on python{3,}-cffi. (Closes: #833163)
diff -Nru xcffib-0.4.2/debian/control xcffib-0.5.1/debian/control
--- xcffib-0.4.2/debian/control 2016-09-19 22:59:15.0 +1200
+++ xcffib-0.5.1/debian/control 2017-07-13 15:28:16.0 +1200
@@ -1,7 +1,8 @@
 Source: xcffib
 Section: python
 Priority: optional
-Maintainer: Iain R. Learmonth 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Iain R. Learmonth 
 Build-Depends: debhelper (>= 9)
   , dh-python
   , pkg-config
@@ -16,8 +17,10 @@
   , libghc-optparse-applicative-dev (>= 0.5)
   , libghc-filemanip-dev
   , libghc-mtl-dev (>= 2.1)
+  , libghc-semigroups-dev
   , libghc-test-framework-hunit-dev
   , libghc-attoparsec-dev
+  , libghc-either-dev
   , python-setuptools
   , python3-setuptools
   , python-autopep8
diff -Nru xcffib-0.4.2/debian/patches/fix-big-endian-machines.patch 
xcffib-0.5.1/debian/patches/fix-big-endian-machines.patch
--- xcffib-0.4.2/debian/patches/fix-big-endian-machines.patch   2016-09-19 
22:59:15.0 +1200
+++ xcffib-0.5.1/debian/patches/fix-big-endian-machines.patch   1970-01-01 
12:00:00.0 +1200
@@ -1,47 +0,0 @@
-Description: handle endian-ness in test cases
-Author: Tycho Andersen 
-Reviewed-By: Iain R. Learmonth 
-Bug: https://github.com/tych0/xcffib/issues/77
-Last-Update: 2016-09-19
-
 xcffib-0.4.2.orig/module/__init__.py
-+++ xcffib-0.4.2/module/__init__.py
-@@ -448,7 +448,7 @@ class List(Protobj):
- 
- def to_atoms(self):
- """ A helper for converting a List of chars to an array of atoms """
--return struct.unpack("=" + "I" * (len(self) // 4), b''.join(self))
-+return struct.unpack("I" * (len(self) // 4), b''.join(self))
- 
- def buf(self):
- return b''.join(self.list)
 xcffib-0.4.2.orig/test/test_python_code.py
-+++ xcffib-0.4.2/test/test_python_code.py
-@@ -16,6 +16,7 @@
- import xcffib
- import xcffib.xproto
- import struct
-+import sys
- from xcffib.xproto import EventMask
- 
- from .testing import XcffibTest
-@@ -44,9 +45,16 @@ class TestPythonCode(XcffibTest):
- for actual, expected in zip(range(20), cm.data8):
- assert actual == expected, actual
- 
--assert cm.data32[0] == 0x03020100
--assert cm.data32[1] == 0x07060504
--assert cm.data32[2] == 0x0b0a0908
-+if sys.byteorder == "little":
-+assert cm.data32[0] == 0x03020100
-+assert cm.data32[1] == 0x07060504
-+assert cm.data32[2] == 0x0b0a0908
-+elif sys.byteorder == "big":
-+assert cm.data32[0] == 0x00010203
-+assert cm.data32[1] == 0x04050607
-+assert cm.data32[2] == 0x08090a0b
-+else:
-+raise Exception("unknown byte order?")
- 
- def test_offset_map(self):
- om = xcffib.OffsetMap({0: "Event0,0"})
diff -Nru xcffib-0.4.2/debian/patches/series xcffib-0.5.1/debian/patches/series
--- xcffib-0.4.2/debian/patches/series  2016-09-19 22:59:15.0 +1200
+++ xcffib-0.5.1/debian/patches/series  2017-07-13 15:16:09.0 +1200
@@ -1 +0,0 @@
-fix-big-endian-machines.patch

Bug#867771:

[Michael Hudson-Doyle]

Attaching a patch that takes the option of simply dropping the
python3-trollius package.
diff -Nru python-trollius-2.1~b1/debian/changelog 
python-trollius-2.1~b1/debian/changelog
--- python-trollius-2.1~b1/debian/changelog 2016-05-20 07:36:53.0 
+1200
+++ python-trollius-2.1~b1/debian/changelog 2017-07-13 14:49:30.0 
+1200
@@ -1,3 +1,9 @@
+python-trollius (2.1~b1-5) unstable; urgency=medium
+
+  * Stop building python3-trollius. (Closes: #867771)
+
+ -- Michael Hudson-Doyle   Thu, 13 Jul 2017 
14:49:06 +1200
+
 python-trollius (2.1~b1-4) unstable; urgency=medium
 
   * d/rules: Changed UPSTREAM_GIT protocol to https
diff -Nru python-trollius-2.1~b1/debian/control 
python-trollius-2.1~b1/debian/control
--- python-trollius-2.1~b1/debian/control   2016-05-20 07:36:53.0 
+1200
+++ python-trollius-2.1~b1/debian/control   2017-07-13 14:48:48.0 
+1200
@@ -33,14 +33,3 @@
  Linux, Mac OS X, FreeBSD and OpenIndiana.
  .
  This package contains the Python 2.x module.
-
-Package: python3-trollius
-Architecture: all
-Depends: ${misc:Depends},
- ${python3:Depends},
-Description: port of the Tulip project on Python 2.7 - Python 3.x
- Trollius is a portage of the Tulip project (asyncio module, PEP 3156) on
- Python 2. Trollius works on Python 2.6-3.4. It has been tested on Windows,
- Linux, Mac OS X, FreeBSD and OpenIndiana.
- .
- This package contains the Python 3.x module.

Bug#865926:

[Michael Hudson-Doyle]

retitle -1 fails tests with python 3.6

FWIW, 0.9.4 still fails tests with Python 3.6, I was initially confused
because the package does not depend on python3-all and so only runs the 3.6
tests when 3.6 is default, not merely supported (another bug, I guess!)

Bug#866551:

[Michael Hudson-Doyle]

The attached patch does not work for two reasons. One, very boring, is that
there is more code that sets PYTHONPATH in translate/storage/test_mo.py.
The other reason, sadly, is that even once that's gone the tests still fail
like this:

_
test_po_to_xliff
_
@pytest.mark.skipif('TTKIT_SKIP_COMMANDS' in os.environ,
reason='Skip testing command line tools')
def test_po_to_xliff():
OUTPUT = 'af-pootle.xlf'
>   assert call(['po2xliff', 'af-pootle.po', OUTPUT]) == 0
E   assert 1 == 0
E+  where 1 = call(['po2xliff', 'af-pootle.po', 'af-pootle.xlf'])

test_xliff_conformance.py:64: AssertionError
---
Captured stderr call
---
Traceback (most recent call last):
  File
"/build/translate-toolkit-ZSDMoF/translate-toolkit-2.0.0/debian/python3-translate/usr/bin/po2xliff",
line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3037, in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3021, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3050, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
655, in _build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
969, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
855, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'translate-toolkit==2.0.0'
distribution was not found and is required by the application

This is not so surprising when you think about it, translate-toolkit for
the default version of Python 3 is not in any sense installed so how could
pkg_resources find it?

Short of going in to bat with upstream for PYTHON35PATH, PYTHON36PATH
environment variables I don't think there's much that can be done. There is
already a debian patch to add an environment variable to allow skipping the
CLI tools (TTKIT_SKIP_COMMANDS), I guess it should be set when testing
non-default versions of Python 3?

Cheers,
mwh