Bug#1071933: libccrtp: diff for NMU version 2.0.9-4.1

[Andreas Metzler]

Control: tags 1071933 + patch
Control: tags 1071933 + pending

Dear maintainer,

I've prepared an NMU for libccrtp (versioned as 2.0.9-4.1) and
uploaded it to unstable.

Regards.
diff -Nru libccrtp-2.0.9/debian/changelog libccrtp-2.0.9/debian/changelog
--- libccrtp-2.0.9/debian/changelog	2024-05-03 20:35:11.0 +0200
+++ libccrtp-2.0.9/debian/changelog	2024-07-09 13:14:07.0 +0200
@@ -1,3 +1,12 @@
+libccrtp (2.0.9-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Delete outdated (and renamed) copy of libgcrypt.m4 and use upstream macro
+instead to fix FTBFS against libgcrypt without libgcrypt-config.
+Closes: #1071933
+
+ -- Andreas Metzler   Tue, 09 Jul 2024 13:14:07 +0200
+
 libccrtp (2.0.9-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff
--- libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff	1970-01-01 01:00:00.0 +0100
+++ libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff	2024-07-09 13:14:07.0 +0200
@@ -0,0 +1,117 @@
+Description: Delete outdated (and renamed) copy of libgcrypt.m4 to fix FTBFS
+ against libgcrypt without libgcrypt-config.
+Author: Andreas Metzler 
+Bug-Debian: https://bugs.debian.org/1071933
+Last-Update: 2024-07-09
+
+--- libccrtp-2.0.9.orig/m4/libgcrypt_local.m4
 /dev/null
+@@ -1,108 +0,0 @@
+-dnl Autoconf macros for libgcrypt
+-dnl   Copyright (C) 2002, 2004 Free Software Foundation, Inc.
+-dnl
+-dnl This file is free software; as a special exception the author gives
+-dnl unlimited permission to copy and/or distribute it, with or without
+-dnl modifications, as long as this notice is preserved.
+-dnl
+-dnl This file is distributed in the hope that it will be useful, but
+-dnl WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
+-dnl implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+-
+-
+-dnl AM_PATH_LIBGCRYPT([MINIMUM-VERSION,
+-dnl   [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
+-dnl Test for libgcrypt and define LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS.
+-dnl MINIMUN-VERSION is a string with the version number optionalliy prefixed
+-dnl with the API version to also check the API compatibility. Example:
+-dnl a MINIMUN-VERSION of 1:1.2.5 won't pass the test unless the installed 
+-dnl version of libgcrypt is at least 1.2.5 *and* the API number is 1.  Using
+-dnl this features allows one to prevent build against newer versions of libgcrypt
+-dnl with a changed API.
+-dnl
+-AC_DEFUN([AM_PATH_LIBGCRYPT_CCRTP],
+-[ AC_ARG_WITH(libgcrypt-prefix,
+-AC_HELP_STRING([--with-libgcrypt-prefix=PFX],
+-   [prefix where LIBGCRYPT is installed (optional)]),
+- libgcrypt_config_prefix="$withval", libgcrypt_config_prefix="")
+-  if test x$libgcrypt_config_prefix != x ; then
+- if test x${LIBGCRYPT_CONFIG+set} != xset ; then
+-LIBGCRYPT_CONFIG=$libgcrypt_config_prefix/bin/libgcrypt-config
+- fi
+-  fi
+-
+-  AC_PATH_PROG(LIBGCRYPT_CONFIG, libgcrypt-config, no)
+-  tmp=ifelse([$1], ,1:1.2.0,$1)
+-  if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
+- req_libgcrypt_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
+- min_libgcrypt_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
+-  else
+- req_libgcrypt_api=0
+- min_libgcrypt_version="$tmp"
+-  fi
+-
+-  AC_MSG_CHECKING(for LIBGCRYPT - version >= $min_libgcrypt_version)
+-  ok=no
+-  if test "$LIBGCRYPT_CONFIG" != "no" ; then
+-req_major=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-req_minor=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
+-req_micro=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
+-libgcrypt_config_version=`$LIBGCRYPT_CONFIG --version`
+-major=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
+-minor=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
+-micro=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
+-if test "$major" -gt "$req_major"; then
+-ok=yes
+-else 
+-if test "$major" -eq "$req_major"; then
+-if test "$minor" -gt "$req_minor"; then
+-   ok=yes
+-else
+-   if test "$minor" -eq "$req_minor"; then
+-   if test "$micro" -ge "$req_micro"; then
+- ok=yes
+-  

Bug#1070905: collectd: diff for NMU version 5.12.0-18.1

[Andreas Metzler]

Control: tags 1070905 + patch
Control: tags 1070905 + pending

Dear maintainer,

I've prepared an NMU for collectd (versioned as 5.12.0-18.1) and
uploaded it to unstable.

Regards
Andreas
diff -Nru collectd-5.12.0/debian/changelog collectd-5.12.0/debian/changelog
--- collectd-5.12.0/debian/changelog	2024-04-20 00:49:01.0 +0200
+++ collectd-5.12.0/debian/changelog	2024-07-07 18:42:43.0 +0200
@@ -1,3 +1,12 @@
+collectd (5.12.0-18.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Invoke ./configure with --with-libgcrypt=/usr GCRYPT_LIBS=-lgcrypt
+to sidestep ./configure's reliance on libgcrypt-config to locate
+libgcrypt. Closes: #1070905
+
+ -- Andreas Metzler   Sun, 07 Jul 2024 18:42:43 +0200
+
 collectd (5.12.0-18) unstable; urgency=medium
 
   * [e3c9674] add .gitignore to ignore swp files
diff -Nru collectd-5.12.0/debian/.gitignore collectd-5.12.0/debian/.gitignore
--- collectd-5.12.0/debian/.gitignore	2024-04-20 00:49:01.0 +0200
+++ collectd-5.12.0/debian/.gitignore	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-*.swp
diff -Nru collectd-5.12.0/debian/rules collectd-5.12.0/debian/rules
--- collectd-5.12.0/debian/rules	2024-04-20 00:49:01.0 +0200
+++ collectd-5.12.0/debian/rules	2024-07-07 18:42:43.0 +0200
@@ -57,7 +57,9 @@
 			--without-libstatgrab \
 			--disable-static \
 			--disable-silent-rules \
-			--enable-all-plugins
+			--enable-all-plugins \
+			--with-libgcrypt=/usr \
+			GCRYPT_LIBS=-lgcrypt
 
 # java doesn't link on i386. (see blocking bug for #1057712)
 ifeq ($(DEB_HOST_ARCH),i386)


signature.asc
Description: PGP signature

Bug#1071951: poldi: diff for NMU version 0.4.2+git20161115.553060d-1.4

[Andreas Metzler]

Control: tags 1071951 + pending

Dear maintainer,

I've prepared an NMU for poldi (versioned as 0.4.2+git20161115.553060d-1.4) and
uploaded it to sid. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru poldi-0.4.2+git20161115.553060d/debian/changelog poldi-0.4.2+git20161115.553060d/debian/changelog
--- poldi-0.4.2+git20161115.553060d/debian/changelog	2024-05-25 01:20:00.0 +0200
+++ poldi-0.4.2+git20161115.553060d/debian/changelog	2024-07-07 16:03:11.0 +0200
@@ -1,3 +1,11 @@
+poldi (0.4.2+git20161115.553060d-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Delete outdated local copy of libgcrypt.m4 which relies on
+libgcrypt-config. (Closes: #1071951)
+
+ -- Andreas Metzler   Sun, 07 Jul 2024 16:03:11 +0200
+
 poldi (0.4.2+git20161115.553060d-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru poldi-0.4.2+git20161115.553060d/debian/patches/05-delete-outdated-libgcrypt.m4.diff poldi-0.4.2+git20161115.553060d/debian/patches/05-delete-outdated-libgcrypt.m4.diff
--- poldi-0.4.2+git20161115.553060d/debian/patches/05-delete-outdated-libgcrypt.m4.diff	1970-01-01 01:00:00.0 +0100
+++ poldi-0.4.2+git20161115.553060d/debian/patches/05-delete-outdated-libgcrypt.m4.diff	2024-07-07 16:03:05.0 +0200
@@ -0,0 +1,116 @@
+Description: Delete outdated local copy of libgcrypt.m4 which relies on libgcrypt-config.
+Author: Andreas Metzler 
+Bug-Debian: https://bugs.debian.org/1071951
+Last-Update: 2024-07-07
+
+--- poldi-0.4.2+git20161115.553060d.orig/m4/libgcrypt.m4
 /dev/null
+@@ -1,108 +0,0 @@
+-dnl Autoconf macros for libgcrypt
+-dnl   Copyright (C) 2002, 2004 Free Software Foundation, Inc.
+-dnl
+-dnl This file is free software; as a special exception the author gives
+-dnl unlimited permission to copy and/or distribute it, with or without
+-dnl modifications, as long as this notice is preserved.
+-dnl
+-dnl This file is distributed in the hope that it will be useful, but
+-dnl WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
+-dnl implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+-
+-
+-dnl AM_PATH_LIBGCRYPT([MINIMUM-VERSION,
+-dnl   [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
+-dnl Test for libgcrypt and define LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS.
+-dnl MINIMUN-VERSION is a string with the version number optionalliy prefixed
+-dnl with the API version to also check the API compatibility. Example:
+-dnl a MINIMUN-VERSION of 1:1.2.5 won't pass the test unless the installed 
+-dnl version of libgcrypt is at least 1.2.5 *and* the API number is 1.  Using
+-dnl this features allows to prevent build against newer versions of libgcrypt
+-dnl with a changed API.
+-dnl
+-AC_DEFUN([AM_PATH_LIBGCRYPT],
+-[ AC_ARG_WITH(libgcrypt-prefix,
+-AC_HELP_STRING([--with-libgcrypt-prefix=PFX],
+-   [prefix where LIBGCRYPT is installed (optional)]),
+- libgcrypt_config_prefix="$withval", libgcrypt_config_prefix="")
+-  if test x$libgcrypt_config_prefix != x ; then
+- if test x${LIBGCRYPT_CONFIG+set} != xset ; then
+-LIBGCRYPT_CONFIG=$libgcrypt_config_prefix/bin/libgcrypt-config
+- fi
+-  fi
+-
+-  AC_PATH_PROG(LIBGCRYPT_CONFIG, libgcrypt-config, no)
+-  tmp=ifelse([$1], ,1:1.2.0,$1)
+-  if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
+- req_libgcrypt_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
+- min_libgcrypt_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
+-  else
+- req_libgcrypt_api=0
+- min_libgcrypt_version="$tmp"
+-  fi
+-
+-  AC_MSG_CHECKING(for LIBGCRYPT - version >= $min_libgcrypt_version)
+-  ok=no
+-  if test "$LIBGCRYPT_CONFIG" != "no" ; then
+-req_major=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-req_minor=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
+-req_micro=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
+-libgcrypt_config_version=`$LIBGCRYPT_CONFIG --version`
+-major=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
+-minor=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
+-micro=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
+-if test "$major" -gt "$req_major"; then
+-ok=yes
+-else 
+-if test "$major" -eq "$req_major"; then
+-if test "$minor" -gt "$req_minor"; then
+-  

Bug#1071862: gfsecret: diff for NMU version 0.5.0-2.1

[Andreas Metzler]

Control: tags 1071862 + pending

Dear maintainer,

I've prepared an NMU for gfsecret (versioned as 0.5.0-2.1) and
uploaded it to sid.

Regards.
diff -Nru gfsecret-0.5.0/debian/changelog gfsecret-0.5.0/debian/changelog
--- gfsecret-0.5.0/debian/changelog	2023-12-03 16:20:38.0 +0100
+++ gfsecret-0.5.0/debian/changelog	2024-07-07 15:51:49.0 +0200
@@ -1,3 +1,11 @@
+gfsecret (0.5.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Delete outdated copy of libgcrypt.m4 which requires libgcrypt-config.
+Closes: #1071862
+
+ -- Andreas Metzler   Sun, 07 Jul 2024 15:51:49 +0200
+
 gfsecret (0.5.0-2) unstable; urgency=medium
 
   * debian/control: Bump Standards-Version to 4.6.2 (no changes needed)
diff -Nru gfsecret-0.5.0/debian/patches/0003-Delete-outdated-libgcrypt.m4.diff gfsecret-0.5.0/debian/patches/0003-Delete-outdated-libgcrypt.m4.diff
--- gfsecret-0.5.0/debian/patches/0003-Delete-outdated-libgcrypt.m4.diff	1970-01-01 01:00:00.0 +0100
+++ gfsecret-0.5.0/debian/patches/0003-Delete-outdated-libgcrypt.m4.diff	2024-07-07 15:51:49.0 +0200
@@ -0,0 +1,175 @@
+Description: Delete outdated libgcrypt.m4 which requires libgcrypt-config.
+Author: Andreas Metzler 
+Bug-Debian: https://bugs.debian.org/1071862
+Last-Update: 2024-07-07
+
+--- gfsecret-0.5.0.orig/m4/libgcrypt.m4
 /dev/null
+@@ -1,167 +0,0 @@
+-# libgcrypt.m4 - Autoconf macros to detect libgcrypt
+-# Copyright (C) 2002, 2003, 2004, 2011, 2014, 2018 g10 Code GmbH
+-#
+-# This file is free software; as a special exception the author gives
+-# unlimited permission to copy and/or distribute it, with or without
+-# modifications, as long as this notice is preserved.
+-#
+-# This file is distributed in the hope that it will be useful, but
+-# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
+-# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+-#
+-# Last-changed: 2018-11-13
+-
+-
+-dnl AM_PATH_LIBGCRYPT([MINIMUM-VERSION,
+-dnl   [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
+-dnl Test for libgcrypt and define LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS.
+-dnl MINIMUN-VERSION is a string with the version number optionalliy prefixed
+-dnl with the API version to also check the API compatibility. Example:
+-dnl a MINIMUN-VERSION of 1:1.2.5 won't pass the test unless the installed
+-dnl version of libgcrypt is at least 1.2.5 *and* the API number is 1.  Using
+-dnl this features allows to prevent build against newer versions of libgcrypt
+-dnl with a changed API.
+-dnl
+-dnl If a prefix option is not used, the config script is first
+-dnl searched in $SYSROOT/bin and then along $PATH.  If the used
+-dnl config script does not match the host specification the script
+-dnl is added to the gpg_config_script_warn variable.
+-dnl
+-AC_DEFUN([AM_PATH_LIBGCRYPT],
+-[ AC_REQUIRE([AC_CANONICAL_HOST])
+-  AC_ARG_WITH(libgcrypt-prefix,
+-AC_HELP_STRING([--with-libgcrypt-prefix=PFX],
+-   [prefix where LIBGCRYPT is installed (optional)]),
+- libgcrypt_config_prefix="$withval", libgcrypt_config_prefix="")
+-  if test x"${LIBGCRYPT_CONFIG}" = x ; then
+- if test x"${libgcrypt_config_prefix}" != x ; then
+-LIBGCRYPT_CONFIG="${libgcrypt_config_prefix}/bin/libgcrypt-config"
+- fi
+-  fi
+-
+-  use_gpgrt_config=""
+-  if test x"${LIBGCRYPT_CONFIG}" = x -a x"$GPGRT_CONFIG" != x -a "$GPGRT_CONFIG" != "no"; then
+-if $GPGRT_CONFIG libgcrypt --exists; then
+-  LIBGCRYPT_CONFIG="$GPGRT_CONFIG libgcrypt"
+-  AC_MSG_NOTICE([Use gpgrt-config as libgcrypt-config])
+-  use_gpgrt_config=yes
+-fi
+-  fi
+-  if test -z "$use_gpgrt_config"; then
+-if test x"${LIBGCRYPT_CONFIG}" = x ; then
+-  case "${SYSROOT}" in
+- /*)
+-   if test -x "${SYSROOT}/bin/libgcrypt-config" ; then
+- LIBGCRYPT_CONFIG="${SYSROOT}/bin/libgcrypt-config"
+-   fi
+-   ;;
+- '')
+-   ;;
+-  *)
+-   AC_MSG_WARN([Ignoring \$SYSROOT as it is not an absolute path.])
+-   ;;
+-  esac
+-fi
+-AC_PATH_PROG(LIBGCRYPT_CONFIG, libgcrypt-config, no)
+-  fi
+-
+-  tmp=ifelse([$1], ,1:1.2.0,$1)
+-  if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
+- req_libgcrypt_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
+- min_libgcrypt_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
+-  else
+- req_libgcrypt_api=0
+- min_libgcrypt_version="$tmp"
+-  fi
+-
+-  AC_MSG_CHECKING(for LIBGCRYPT - version >= $min_libgcrypt_version)
+-  ok=no
+-  if test "$LIBGCRYPT_CONFIG" != "no" ; then
+-req_major=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-r

Bug#1070904: bitlbee: Please use pkg-config instead of libgcrypt-config to locate libgcrypt

[Andreas Metzler]

Control: tags -1 pending

See 
https://github.com/bitlbee/bitlbee/commit/684aca266fad3fe7793fe637a71b095500c35998

cu Andreas


signature.asc
Description: PGP signature

Bug#1070903: axc: diff for NMU version 0.3.7-1.1

[Andreas Metzler]

Control: tags 1070903 + pending

Dear maintainer,

I've prepared an NMU for axc (versioned as 0.3.7-1.1) and
uploaded it to sid

Regards.
diff -Nru axc-0.3.7/debian/changelog axc-0.3.7/debian/changelog
--- axc-0.3.7/debian/changelog	2022-01-31 21:42:23.0 +0100
+++ axc-0.3.7/debian/changelog	2024-07-07 15:34:28.0 +0200
@@ -1,3 +1,10 @@
+axc (0.3.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use pkg-config to locate libgcrypt. Closes: #1070903
+
+ -- Andreas Metzler   Sun, 07 Jul 2024 15:34:28 +0200
+
 axc (0.3.7-1) unstable; urgency=medium
 
   * New upstream version 0.3.7
diff -Nru axc-0.3.7/debian/patches/01_locate_gcrypt_with_pkg-config.diff axc-0.3.7/debian/patches/01_locate_gcrypt_with_pkg-config.diff
--- axc-0.3.7/debian/patches/01_locate_gcrypt_with_pkg-config.diff	1970-01-01 01:00:00.0 +0100
+++ axc-0.3.7/debian/patches/01_locate_gcrypt_with_pkg-config.diff	2024-07-07 15:34:28.0 +0200
@@ -0,0 +1,20 @@
+Description: Use pkg-config to locate libgcrypt
+ libgcrypt-config is scheduled for removal.
+Author: Andreas Metzler 
+Origin: vendor
+Last-Update: 2024-05-11
+Bug-Debian: https://bugs.debian.org/1070903
+
+--- axc-0.3.7.orig/Makefile
 axc-0.3.7/Makefile
+@@ -24,8 +24,8 @@ SQLITE3_LDFLAGS ?= $(shell $(PKG_CONFIG)
+ SIGNAL_CFLAGS ?= $(shell $(PKG_CONFIG) --cflags libsignal-protocol-c)
+ SIGNAL_LDFLAGS ?= $(shell $(PKG_CONFIG) --libs libsignal-protocol-c)
+ 
+-LIBGCRYPT_CONFIG ?= libgcrypt-config
+-LIBGCRYPT_LDFLAGS ?= $(shell $(LIBGCRYPT_CONFIG) --libs)
++LIBGCRYPT_CFLAGS ?= $(shell $(PKG_CONFIG) --cflags libgcrypt)
++LIBGCRYPT_LDFLAGS ?= $(shell $(PKG_CONFIG) --libs libgcrypt)
+ 
+ 
+ SDIR = src
diff -Nru axc-0.3.7/debian/patches/series axc-0.3.7/debian/patches/series
--- axc-0.3.7/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ axc-0.3.7/debian/patches/series	2024-07-07 15:34:28.0 +0200
@@ -0,0 +1 @@
+01_locate_gcrypt_with_pkg-config.diff


signature.asc
Description: PGP signature

Bug#1071837: chntpw: diff for NMU version 140201-1.1

[Andreas Metzler]

Control: tags 1071837 + pending

Dear maintainer,

I've prepared an NMU for chntpw (versioned as 140201-1.1) and
uploaded it to sid

Regards.
diff -Nru chntpw-140201/debian/changelog chntpw-140201/debian/changelog
--- chntpw-140201/debian/changelog	2022-01-20 22:35:49.0 +0100
+++ chntpw-140201/debian/changelog	2024-07-07 14:07:39.0 +0200
@@ -1,3 +1,11 @@
+chntpw (140201-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use pkg-config instead of libgcrypt-config to locate libgcrypt.
+Closes: #1071837
+
+ -- Andreas Metzler   Sun, 07 Jul 2024 14:07:39 +0200
+
 chntpw (140201-1) unstable; urgency=medium
 
   [ Fabio Fantoni ]
diff -Nru chntpw-140201/debian/control chntpw-140201/debian/control
--- chntpw-140201/debian/control	2022-01-20 22:35:49.0 +0100
+++ chntpw-140201/debian/control	2024-07-07 14:07:39.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Javier Fernández-Sanguino Peña 
-Build-Depends: debhelper-compat (= 13), libgcrypt20-dev | libgcrypt-dev, sharutils, quilt, dpkg-dev ( >= 1.16.1~)
+Build-Depends: debhelper-compat (= 13), libgcrypt20-dev | libgcrypt-dev, sharutils, quilt, dpkg-dev ( >= 1.16.1~), pkgconf
 Standards-Version: 4.5.1
 Homepage: http://pogostick.net/~pnh/ntpasswd/
 Vcs-Git: https://salsa.debian.org/debian/chntpw.git
diff -Nru chntpw-140201/debian/patches/16_gcry-pkg-config.diff chntpw-140201/debian/patches/16_gcry-pkg-config.diff
--- chntpw-140201/debian/patches/16_gcry-pkg-config.diff	1970-01-01 01:00:00.0 +0100
+++ chntpw-140201/debian/patches/16_gcry-pkg-config.diff	2024-07-07 14:06:13.0 +0200
@@ -0,0 +1,15 @@
+--- chntpw-140201.orig/Makefile
 chntpw-140201/Makefile
+@@ -6,10 +6,10 @@
+ CC=gcc
+ 
+ # Force 32 bit
+-CFLAGS= -DUSELIBGCRYPT -I. $(shell libgcrypt-config --cflags) -Wall -m32
++CFLAGS= -DUSELIBGCRYPT -I. $(shell pkg-config --cflags libgcrypt) -Wall -m32
+ OSSLLIB=$(OSSLPATH)/lib
+ 
+-LIBS=$(shell libgcrypt-config --libs)
++LIBS=$(shell pkg-config --libs libgcrypt)
+ 
+ 
+ all: chntpw cpnt reged samusrgrp sampasswd samunlock
diff -Nru chntpw-140201/debian/patches/series chntpw-140201/debian/patches/series
--- chntpw-140201/debian/patches/series	2022-01-20 22:35:49.0 +0100
+++ chntpw-140201/debian/patches/series	2024-07-07 14:06:53.0 +0200
@@ -13,3 +13,4 @@
 13_write_to_hive
 14_improve_description
 15_added_samunlock_binary
+16_gcry-pkg-config.diff


signature.asc
Description: PGP signature

Bug#1073339: abiword: FTBFS: ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’?

[Andreas Metzler]

Control: tags -1 patch
On 2024-06-16 Lucas Nussbaum  wrote:
> Source: abiword
> Version: 3.0.5~dfsg-3.2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie

> Hi,

> During a rebuild of all packages in sid, your package failed to build
> on amd64.


> Relevant part (hopefully):
[...]
> > ut_stringbuf.cpp: In member function ‘void UT_UTF8Stringbuf::escapeURL()’:
> > ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; 
> > did you mean ‘xmlFreeURI’?
> >   578 | xmlFree(uri);
> >   | ^~~
> >   | xmlFreeURI
> > make[7]: *** [Makefile:831: ut_stringbuf.lo] Error 1

Hello,

this worked for me:
--- abiword-3.0.5~dfsg.orig/src/af/util/xp/ut_stringbuf.cpp
+++ abiword-3.0.5~dfsg/src/af/util/xp/ut_stringbuf.cpp
@@ -26,6 +26,7 @@
 #include 

 #include 
+#include 

 #include 

cu Andreas

Bug#1071860: not fixed in 7.0-005-2

[Andreas Metzler]

Control: tags -1 pending

On 2024-06-23 Andreas Metzler  wrote:
[...]
> I will give it a litte bit of time to check whether somebody else from
> -med picks this up and will NMU otherwise.

Hello,

I have now uploaded a NMU to delayed/7-days using the attached patch. I
have gone for the mininal change, dropping the respective code instead
of switching to pkgconf. It simpler, does not make a difference on
Debian systems and the whole thing does not make sense to me.

cu Andreas
diff -Nru fis-gtm-7.0-005/debian/changelog fis-gtm-7.0-005/debian/changelog
--- fis-gtm-7.0-005/debian/changelog	2024-06-22 21:59:20.0 +0200
+++ fis-gtm-7.0-005/debian/changelog	2024-06-29 15:41:01.0 +0200
@@ -1,3 +1,12 @@
+fis-gtm (7.0-005-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS without libgcrypt-config by simply dropping the respective code
+on Debian. libgcrypt headers are installed to /usr/include on Debian
+Closes: #1071860
+
+ -- Andreas Metzler   Sat, 29 Jun 2024 15:41:01 +0200
+
 fis-gtm (7.0-005-2) unstable; urgency=medium
 
   * Build-Depends: s/libgcrypt20-dev | //, pkgconf
diff -Nru fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff
--- fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff	1970-01-01 01:00:00.0 +0100
+++ fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff	2024-06-29 15:40:24.0 +0200
@@ -0,0 +1,50 @@
+Description: Drop unnecessary call to libgcrypt-config
+ libgcrypt-config has been dropped in libgcrypt 1.11, the call here is
+ unnecessary on Debian (headers in /usr/include).
+ .
+ The whole code snippet is a little bit strange since it allows searching for
+ libgcrypt headers in a standard location while requiring that the library
+ itself can be found in a standard location.
+Author: Andreas Metzler 
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/1071860
+Last-Update: 2024-06-29
+
+--- fis-gtm-7.0-005.orig/CMakeLists.txt
 fis-gtm-7.0-005/CMakeLists.txt
+@@ -523,20 +523,21 @@ add_custom_command(
+ add_custom_target(gen_tls_options
+   DEPENDS ${GTM_BINARY_DIR}/gen_tls_options.h ${GTM_BINARY_DIR}/gen_tls_verify_options.h)
+ 
+-# Locate libgcrypt's header files (assumption: all others headers are found in the same location)
+-find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
+-if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
+-	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
+-else()
+-	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
+-	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
+-	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
+-	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
+-	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
+-		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
+-		include_directories(${LIBGCRYPT_INCLUDES})
+-	endif()
+-endif()
++# Disabled - Debian's libgcrypt header are installed in standard paths.
++# # Locate libgcrypt's header files (assumption: all others headers are found in the same location)
++# find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
++# if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
++# 	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
++# else()
++# 	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
++# 	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
++# 	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
++# 	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
++# 	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
++# 		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
++# 		include_directories(${LIBGCRYPT_INCLUDES})
++# 	endif()
++# endif()
+ 
+ # Building the three encryption libraries could by a loop of some sort, but
+ # manually creating each target is way easier.
diff -Nru fis-gtm-7.0-005/debian/patches/series fis-gtm-7.0-005/debian/patches/series
--- fis-gtm-7.0-005/debian/patches/series	2024-06-22 21:59:20.0 +0200
+++ fis-gtm-7.0-005/debian/patches/series	2024-06-29 15:40:57.0 +0200
@@ -1,2 +1,3 @@
 upstream_disable_autorelink
 upstream_donot_deploy_all_encryption_libs
+do-not-use_libgcrypt-config.diff


signature.asc
Description: PGP signature

Bug#1073828: libuim-data update fails due to undefined symbol

[Andreas Metzler]

Control: tags -1 patch

On 2024-06-19 "Gustavo R. Montesino"  wrote:
> Package: libuim-data
> Version: 1:1.8.8-9.4
> Severity: serious
> Justification: Policy 8.6

> Hello,

> Can't upate libuim-data due to undefined symbol in uim-module-manager:

> Configurando libuim-data (1:1.8.8-9.4) ...
> uim-module-manager: symbol lookup error: uim-module-manager: undefined 
> symbol: uim_internal_strlcpy

Hello,

The latest iteration of 
https://salsa.debian.org/debian/uim/-/merge_requests/15#note_501667
is intended to fix this.

cu Andreas

Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-

[Andreas Metzler]

Control: tags -1 patch
On 2024-06-23 Andreas Tille  wrote:
> Control: tags -1 help

> Hi Andreas,

> strange, it has build for me.

Very strange, perhaps you did not build against the libgcrypt package in
experimental.

> Am Sun, Jun 23, 2024 at 08:03:30AM +0200 schrieb Andreas Metzler:
> > Control: reopen 1071860
> > ...
> > CMake Error at CMakeLists.txt:529 (message):
> >   FATAL: libgcrypt-config not found (LIBGCRYPT_CONFIG_SCRIPT-NOTFOUND)
> > [...]

> I admit I currently have no time to track this down.  It might make
> sense to upgrade to latest upstream which might have been adapted to
> work without libgcrypt-config.   Tagging the bug help since I have no
> capacity to work on this.

Fair enough.

The respective part of the CMake setup is unchanged in 7.1-003.
Attached patch works for me.

Upstream's build system is rather strange. - It requires libgcrypt itself
to be in the standard search but allows the headers to be hidden away:

8X
# Iterate over the list of GPG related libraries
foreach(gpglib gpg-error gpgme gcrypt config)
  # For each library, we need a new CMake variable, hence GPGLIB_${gpglib}
  find_library(GPGLIB_${gpglib} NAME ${gpglib} PATHS ${CMAKE_LIBRARY_PATH})
  # Append the found library to the list
  set(GPG_LIBRARIES ${GPG_LIBRARIES} ${GPGLIB_${gpglib}})
endforeach()
[...]
# Locate libgcrypt's header files (assumption: all others headers are found in 
the same location)
find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
message(FATAL_ERROR "FATAL: libgcrypt-config not found 
(${LIBGCRYPT_CONFIG_SCRIPT})")
else()
[...]
8X

A Debian specific patch could simply drop the whole block
find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
[...]
endif()

I will give it a litte bit of time to check whether somebody else from
-med picks this up and will NMU otherwise.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
From: Andreas Metzler 
Date: Sun, 23 Jun 2024 13:26:46 +0200
Subject: Use pkg-config to locate gcrypt include path instead of
 libgcrypt-config

---
 CMakeLists.txt | 16 +++-
 1 file changed, 3 insertions(+), 13 deletions(-)

diff --git a/CMakeLists.txt b/CMakeLists.txt
index cd06044..c9e57f4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -524,19 +524,9 @@ add_custom_target(gen_tls_options
   DEPENDS ${GTM_BINARY_DIR}/gen_tls_options.h ${GTM_BINARY_DIR}/gen_tls_verify_options.h)
 
 # Locate libgcrypt's header files (assumption: all others headers are found in the same location)
-find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
-if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
-	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
-else()
-	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
-	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
-	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
-	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
-	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
-		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
-		include_directories(${LIBGCRYPT_INCLUDES})
-	endif()
-endif()
+include(FindPkgConfig)
+pkg_check_modules(LIBGCRYPT REQUIRED libgcrypt)
+include_directories(${LIBGCRYPT_INCLUDE_DIRS})
 
 # Building the three encryption libraries could by a loop of some sort, but
 # manually creating each target is way easier.

Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-

[Andreas Metzler]

Control: reopen 1071860

On 2024-06-22 Debian Bug Tracking System  wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:fis-gtm package:

> #1071860: fis-gtm: Searches for libgcrypt with libgcrypt-config

> It has been closed by Debian FTP Masters  
> (reply to Andreas Tille ).
[...]
>  fis-gtm (7.0-005-2) unstable; urgency=medium
>  .
>* Build-Depends: s/libgcrypt20-dev | //, pkgconf
>  Closes: #1071860
[...]

> From: Andreas Metzler 
> To: Debian Bug Tracking System 
> Subject: fis-gtm: Searches for libgcrypt with libgcrypt-config
> Message-ID: 
[...]
> fis-gtm relies on libgcrypt-config to locate libgcrypt. libgcrypt-config
> is scheduled for removal and will be dropped in libgcrypt 1.11. Please
> use pkg-config/pkgconf instead.

Hello,

This is unfixed, trying to rebuild fis-gtm (7.0-005-2) without
/usr/bin/libgcrypt-config results in:

make[1]: Entering directory '/tmp/fis-gtm-7.0-005'
dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V7.0-005_x86_64 
-DCMAKE_BUILD_TYPE=Release
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V7.0-005_x86_64 
-DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is GNU 13.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/lib/ccache/cc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib/ccache/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
--> OS = Linux / ARCH = x86_64
-- Bootstraping from pre-generated sources.
INFO: Using ssl.h /usr/include/openssl/ssl.h
CMake Error at CMakeLists.txt:529 (message):
  FATAL: libgcrypt-config not found (LIBGCRYPT_CONFIG_SCRIPT-NOTFOUND)
[...]

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1072642: curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest)

[Andreas Metzler]

On 2024-06-07 Carlos Henrique Lima Melara  wrote:
> On Wed, 5 Jun 2024 18:39:40 +0200 Andreas Metzler  wrote:
[...] 
>> TESTFAIL: These test cases failed: 241 507

> Were you able to consistently get those exact failures? We are getting
> some random and unreproducible failures since we have enabled parallel
> tests - but the speed up is jaw dropping.

> We have reported it to upstream already [1], but it's not very easy to
> debug. I also tried to build locally with sbuild and using debci [2] and
> they have succeeded, so maybe it's just a hicup.

> If you were able to consistently reproduce this, please let us know more
> about your build environment.
[...]

Hello Carlos,

at the specific point in time I looked into this I was getting exactly
these errors (241 507) both for a rebuild and when running
autopkgtest --no-built-binaries --output-dir=/tmp/CURL/ci-out -- null
in a regular sid chroot (using schroot). The ci-test produced these errors
both for the openssl and the gnutls subtest.

I will give rebuilding another shot and report back.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1072642: curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest)

[Andreas Metzler]

Package: curl
Version: 8.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello,

I did a local rebuild on sid which failed:
srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35 
~300 ~301 ~303 ~304 ~306 ~309 ~310 ~325 ~364 ~400 ~401 ~403 ~406 ~407 ~408 ~409 
~410 ~414 ~417 ~560 ~678 ~987 ~988 ~989 ~1112 ~1272 ~1470 ~1561 ~1562 ~1630 
~1631 ~1632 ~2034 ~2037 ~2041 ~3000 ~3001 ~3102
Using curl: ../src/curl
[...]
test 0241...[HTTP-IPv6 GET (using ip6-localhost)]

 241: protocol FAILED!
 There was no content at all in the file log/5/server.input.
 Server glitch? Total curl failure? Returned: 7
== Contents of files in the log/5/ dir after test 241
=== Start of file http_ipv6_server.log
 16:19:15.385882 Running HTTP IPv6 version on port 36339
 16:19:15.385966 Wrote pid 68256 to log/5/server/http_ipv6_server.pid
 16:19:15.385990 Wrote port 36339 to log/5/server/http_ipv6_server.port
 16:19:16.348256 > Client connect
 16:19:16.348285 accept_connection 3 returned 4
 16:19:16.348310 accept_connection 3 returned 0
 16:19:16.348377 Read 88 bytes
 16:19:16.348397 Process 88 bytes request
 16:19:16.348427 Got request: GET /verifiedserver HTTP/1.1
 16:19:16.348443 Are-we-friendly question received
 16:19:16.348471 Wrote request (88 bytes) input to log/5/server.input
 16:19:16.348499 Identifying ourselves as friends
 16:19:16.348570 Response sent (56 bytes) and written to log/5/server.response
 16:19:16.348589 special request received, no persistency
 16:19:16.348604 > Client disconnect 0
=== End of file http_ipv6_server.log
=== Start of file http_ipv6_verify.log
 *   Trying [::1]:36339...
 * Connected to ::1 (::1) port 36339
 > GET /verifiedserver HTTP/1.1
 > Host: [::1]:36339
 > User-Agent: curl/8.8.0
 > Accept: */*
 > 
 * Request completely sent off
 < HTTP/1.1 200 OK
 < Content-Length: 17
 < 
 { [17 bytes data]
 * Connection #0 to host ::1 left intact
=== End of file http_ipv6_verify.log
=== Start of file http_ipv6_verify.out
 WE ROOLZ: 68256
=== End of file http_ipv6_verify.out
=== Start of file server.cmd
 Testnum 241
=== End of file server.cmd
=== Start of file server.response
 HTTP/1.1 200 OK
 Content-Length: 17
 WE ROOLZ: 68256
=== End of file server.response
=== Start of file stderr241
   % Total% Received % Xferd  Average Speed   TimeTime Time  Current
  Dload  Upload   Total   SpentLeft  Speed
 
   0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
   0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
 curl: (7) Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't 
connect to server
=== End of file stderr241
=== Start of file trace241
 16:19:16.524170 == Info: Host ip6-localhost:36339 was resolved.
 16:19:16.524215 == Info: IPv6: (none)
 16:19:16.524217 == Info: IPv4: 31.15.64.248
 16:19:16.524231 == Info:   Trying 31.15.64.248:36339...
 16:19:16.567508 == Info: connect to 31.15.64.248 port 36339 from 
192.168.178.20 port 40168 failed: Connection refused
 16:19:16.567523 == Info: Failed to connect to ip6-localhost port 36339 after 
106 ms: Couldn't connect to server
 16:19:16.567663 == Info: Closing connection
=== End of file trace241
[...]
test 0507...[multi interface get with non-existing host name]

lib507 returned 0, when expecting 6
 507: exit FAILED
== Contents of files in the log/31/ dir after test 507
=== Start of file server.cmd
 Testnum 507
=== End of file server.cmd
=== Start of file stderr507
 URL: http://non-existing-host.haxx.se/
 Test ended with result 0
=== End of file stderr507
=== Start of file stdout507
 HTTP/1.1 200 OK
 Date: Wed, 05 Jun 2024 16:19:18 GMT
 Server: Apache/2.4.59 (Debian)
 Last-Modified: Sun, 14 Feb 2016 17:00:04 GMT
 ETag: "0-52bbdd4e2cd00"
 Accept-Ranges: bytes
 Content-Length: 0
 Content-Type: text/html
=== End of file stdout507
[...]
2)
TESTDONE: 1700 tests were considered during 522 seconds.
TESTINFO: 195 tests were skipped due to these restraints:
TESTINFO: "curl lacks debug support" 99 times (159, 356, 358, 359, 363, 412, 
413, 437, 438 and 90 more)
TESTINFO: "curl lacks unittest support" 49 times (1300, 1302, 1303, 1304, 1305, 
1306, 1308, 1309, 1323 and 40 more)
TESTINFO: "configured as DISABLED" 16 times (323, 594, 836, 882, 938, 1182, 
1184, 1209, 1211 and 7 more)
TESTINFO: "failed starting HTTP/2 server" 7 times (1700, 1701, 1702, 2402, 
2403, 2404, 2405)
TESTINFO: "curl lacks Schannel support" 6 times (2033, 2070, 2079, 2087, 3023, 
3024)
TESTINFO: "no gnutls-serv (with SRP support)" 4 times (320, 321, 322, 324)
TESTINFO: "curl lacks http/3 support" 3 times (2500, 2502, 2503)
TESTINFO: "curl has idn support" 3 times (959, 960, 961)
TESTINFO: "curl lacks TrackMemory support" 2 times (96, 558)
TESTINFO: "curl has ipv6 support" 1 time (1454)
TESTINFO: "curl has threaded-resolver support" 1 time (506)
TESTINFO: "curl has proxy support" 1 time (375)

Bug#1071552: Bug#1071552: gnupg: Please upgrade GnuPG >= 2.4.4, current GnuPG break Emacs's EasyPG

[Andreas Metzler]

On 2024-05-27 Daniel Kahn Gillmor  wrote:
[...]
> Would anyone be willing to try to backport the patches from upstream's
> fixes for T6481 to the 2.2.x series?

Hello Daniel,

the issue report refers to two patches, one of these is already part of
2.2.43. The other one[1] seemed pretty straightforward to backport
(functions moved to other files and cipher_filter_ocb instead of
cipher_filter_aead). I would appreciate a second pair of eyes.

cu Andreas
[1] https://dev.gnupg.org/rG2f872fa68c6576724b9dabee9fb0844266f55d0d
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
>From 2f872fa68c6576724b9dabee9fb0844266f55d0d Mon Sep 17 00:00:00 2001
From: NIIBE Yutaka 
Date: Wed, 24 May 2023 10:36:04 +0900
Subject: [PATCH] gpg: Report BEGIN_* status before examining the input.

* common/miscellaneous.c (is_openpgp_compressed_packet)
(is_file_compressed): Moved to ...
* common/iobuf.c: ... in this file.
(is_file_compressed): Change the argument to INP, the iobuf.
* common/util.h (is_file_compressed): Remove.
* common/iobuf.h (is_file_compressed): Add.
* g10/cipher-aead.c (write_header): Don't call write_status_printf
here.
(cipher_filter_aead): Call write_status_printf when called with
IOBUFCTRL_INIT.
* g10/cipher-cfb.c (write_header): Don't call write_status_printf
here.
(cipher_filter_cfb): Call write_status_printf when called with
IOBUFCTRL_INIT.
* g10/encrypt.c (encrypt_simple): Use new is_file_compressed function,
after call of iobuf_push_filter.
(encrypt_crypt): Likewise.
* g10/sign.c (sign_file): Likewise.

--

GnuPG-bug-id: 6481

--- a/common/iobuf.c
+++ b/common/iobuf.c
@@ -2750,5 +2750,125 @@ iobuf_skip_rest (iobuf_t a, unsigned lon
   remaining -= count;
 	}
 	}
 }
 }
+
+
+/* Check whether (BUF,LEN) is valid header for an OpenPGP compressed
+ * packet.  LEN should be at least 6.  */
+static int
+is_openpgp_compressed_packet (const unsigned char *buf, size_t len)
+{
+  int c, ctb, pkttype;
+  int lenbytes;
+
+  ctb = *buf++; len--;
+  if (!(ctb & 0x80))
+return 0; /* Invalid packet.  */
+
+  if ((ctb & 0x40)) /* New style (OpenPGP) CTB.  */
+{
+  pkttype = (ctb & 0x3f);
+  if (!len)
+return 0; /* Expected first length octet missing.  */
+  c = *buf++; len--;
+  if (c < 192)
+;
+  else if (c < 224)
+{
+  if (!len)
+return 0; /* Expected second length octet missing. */
+}
+  else if (c == 255)
+{
+  if (len < 4)
+return 0; /* Expected length octets missing */
+}
+}
+  else /* Old style CTB.  */
+{
+  pkttype = (ctb>>2)&0xf;
+  lenbytes = ((ctb&3)==3)? 0 : (1<<(ctb & 3));
+  if (len < lenbytes)
+return 0; /* Not enough length bytes.  */
+}
+
+  return (pkttype == 8);
+}
+
+
+/*
+ * Check if the file is compressed, by peeking the iobuf.  You need to
+ * pass the iobuf with INP.  Returns true if the buffer seems to be
+ * compressed.
+ */
+int
+is_file_compressed (iobuf_t inp)
+{
+  int i;
+  char buf[32];
+  int buflen;
+
+  struct magic_compress_s
+  {
+byte len;
+byte extchk;
+byte magic[5];
+  } magic[] =
+  {
+   { 3, 0, { 0x42, 0x5a, 0x68, 0x00 } }, /* bzip2 */
+   { 3, 0, { 0x1f, 0x8b, 0x08, 0x00 } }, /* gzip */
+   { 4, 0, { 0x50, 0x4b, 0x03, 0x04 } }, /* (pk)zip */
+   { 5, 0, { '%', 'P', 'D', 'F', '-'} }, /* PDF */
+   { 4, 1, { 0xff, 0xd8, 0xff, 0xe0 } }, /* Maybe JFIF */
+   { 5, 2, { 0x89, 'P','N','G', 0x0d} }  /* Likely PNG */
+  };
+
+  if (!inp)
+return 0;
+
+  for ( ; inp->chain; inp = inp->chain )
+;
+
+  buflen = iobuf_ioctl (inp, IOBUF_IOCTL_PEEK, sizeof buf, buf);
+  if (buflen < 0)
+{
+  buflen = 0;
+  log_debug ("peeking at input failed\n");
+}
+
+  if ( buflen < 6 )
+{
+  return 0;  /* Too short to check - assume uncompressed.  */
+}
+
+  for ( i = 0; i < DIM (magic); i++ )
+{
+  if (!memcmp( buf, magic[i].magic, magic[i].len))
+{
+  switch (magic[i].extchk)
+{
+case 0:
+  return 1; /* Is compressed.  */
+case 1:
+  if (buflen > 11 && !memcmp (buf + 6, "JFIF", 5))
+return 1; /* JFIF: this likely a compressed JPEG.  */
+  break;
+case 2:
+  if (buflen > 8
+  && buf[5] == 0x0a && buf[6] == 0x1a && buf[7] == 0x0a)
+return 1; /* This is a PNG.  */
+  break;
+default:
+  break;
+}
+}
+}
+
+  if (buflen >= 6 && is_openpgp_compressed_packet (buf, buflen))
+{
+  return 1; /* Already compressed.  */
+}
+
+  return 0;  /* Not detected as compressed.  */
+}
--- a/common/iobuf.h
+++ b/common/iobuf.h
@@ -595,10 +595,13 @@ void iobuf_set_partial_body_length_mode
Recall: a filter can return EOF.  In this case, it and all

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Andreas Metzler]

Control: tags -1 fixed-upstream

On 2024-05-05 Andreas Metzler  wrote:
> On 2024-05-04 Santiago Vila  wrote:
> > found 1064486 0.16.3-1
> > tags 1064486 + ftbfs bookworm trixie sid
> > thanks

> > El 20/4/24 a las 14:12, Andreas Metzler escribió:
> > > FWIW I also get testsuite errors on current sid on amd64
> > > The following tests FAILED:
> > >   83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
> > >   90 - rnp_tests.test_ffi_security_profile (Failed)
> > >  174 - rnp_tests.test_key_add_userid (Failed)
> > >  254 - cli_tests-EncryptElgamal (Failed)

> > Hello. This is also happening in bookworm, I assume that for the same 
> > underlying reason,
> > so I'm adding the bookworm version.
> [...]

> Hmm. Perhaps a timebomb, i.e. one of the keys used in the testsuite
> expired.


Hello,

Indeed it is a timebomb. Since 0.17.1 works I had a look at
git log src/tests/key-add-userid.cpp
and found

commit 07745e2e5fa6078b95fb5c24575929eb2a19ca03
Author: Nickolay Olshevsky 
Date:   Fri Jan 19 16:05:32 2024 +0200

Update tests to match SHA1 cutoff date for key signatures.
[...]
 selfsig0.primary = false;
+auto curtime = global_ctx.time();
+global_ctx.set_time(curtime > SHA1_KEY_FROM ? SHA1_KEY_FROM - 100 : 0);


SHA1_KEY_FROM is #defined in src/tests/support.h to 1705629600, which
was Fri Jan 19 03:00:00 CET 2024.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Andreas Metzler]

On 2024-05-04 Santiago Vila  wrote:
> found 1064486 0.16.3-1
> tags 1064486 + ftbfs bookworm trixie sid
> thanks

> El 20/4/24 a las 14:12, Andreas Metzler escribió:
> > FWIW I also get testsuite errors on current sid on amd64
> > The following tests FAILED:
> >   83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
> >   90 - rnp_tests.test_ffi_security_profile (Failed)
> >  174 - rnp_tests.test_key_add_userid (Failed)
> >  254 - cli_tests-EncryptElgamal (Failed)

> Hello. This is also happening in bookworm, I assume that for the same 
> underlying reason,
> so I'm adding the bookworm version.
[...]


Hmm. Perhaps a timebomb, i.e. one of the keys used in the testsuite
expired.

cu Andreas

Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29

[Andreas Metzler]

On 2024-04-20 Lucas Nussbaum  wrote:
> Source: libsoup2.4
> Version: 2.74.3-7
> Severity: serious
> Justification: FTBFS
[...]
> > (hsts-test:547071): GLib-Net-WARNING **: 04:03:06.247: Failed to load TLS 
> > database: System trust contains zero trusted certificates; please 
> > investigate your GnuTLS configuration

FWIW I could not reproduce this on amdahl.debian.org, the build
succeeded.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1067915: veusz: diff for NMU version 3.6.2-1.1

[Andreas Metzler]

Control: tags 1067915 + patch
Control: tags 1067915 + pending

Dear maintainer,

I've prepared an NMU for veusz (versioned as 3.6.2-1.1) and
uploaded it to DELAYED/00.

kind regards Andreas
diff -Nru veusz-3.6.2/debian/changelog veusz-3.6.2/debian/changelog
--- veusz-3.6.2/debian/changelog	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/changelog	2024-04-21 14:19:21.0 +0200
@@ -1,3 +1,10 @@
+veusz (3.6.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop runtime library packages (not -dev) from b-d. Closes: #1067915
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 14:19:21 +0200
+
 veusz (3.6.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru veusz-3.6.2/debian/control veusz-3.6.2/debian/control
--- veusz-3.6.2/debian/control	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/control	2024-04-21 14:18:16.0 +0200
@@ -6,12 +6,6 @@
 Build-Depends: debhelper-compat (= 13),
dh-exec,
dh-python,
-   libqt5core5a,
-   libqt5dbus5,
-   libqt5gui5,
-   libqt5svg5,
-   libqt5widgets5,
-   libqt5xml5,
python3-all,
python3-all-dev,
python3-astropy,


signature.asc
Description: PGP signature

Bug#1068224: deepin-movie-reborn: diff for NMU version 5.10.8-2.1

[Andreas Metzler]

Control: tags 1068224 + patch
Control: tags 1068224 + pending

Dear maintainer,

I've prepared an NMU for deepin-movie-reborn (versioned as 5.10.8-2.1) and
uploaded it to DELAYED/00.

kind regards
Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru deepin-movie-reborn-5.10.8/debian/changelog deepin-movie-reborn-5.10.8/debian/changelog
--- deepin-movie-reborn-5.10.8/debian/changelog	2022-12-01 00:12:34.0 +0100
+++ deepin-movie-reborn-5.10.8/debian/changelog	2024-04-21 13:23:59.0 +0200
@@ -1,3 +1,11 @@
+deepin-movie-reborn (5.10.8-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Change hardcoded dependency to libqt5concurrent5t64 instead of
+libqt5concurrent5. Closes: #1068224
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 13:23:59 +0200
+
 deepin-movie-reborn (5.10.8-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru deepin-movie-reborn-5.10.8/debian/control deepin-movie-reborn-5.10.8/debian/control
--- deepin-movie-reborn-5.10.8/debian/control	2022-11-30 23:22:11.0 +0100
+++ deepin-movie-reborn-5.10.8/debian/control	2024-04-21 13:23:54.0 +0200
@@ -55,7 +55,7 @@
  libgstreamer1.0-0,
  libmpris-qt5-1 (>= 0.1.0.1),
  libpulse0,
- libqt5concurrent5,
+ libqt5concurrent5t64,
  va-driver-all,
  ${libmpv:Depends},
  ${misc:Depends},
@@ -99,7 +99,7 @@
  libgstreamer-plugins-base1.0-0,
  libmpris-qt5-1 (>= 0.1.0.1),
  libpulse0,
- libqt5concurrent5,
+ libqt5concurrent5t64,
  ${libmpv:Depends},
  ${misc:Depends},
  ${shlibs:Depends},


signature.asc
Description: PGP signature

Bug#1068226: trantor: diff for NMU version 1.5.12+ds-1.1

[Andreas Metzler]

Control: tags 1068226 + patch
Control: tags 1068226 + pending

Dear maintainer,

I've prepared an NMU for trantor (versioned as 1.5.12+ds-1.1) and
uploaded it to DELAYED/00.

kind regards
Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru trantor-1.5.12+ds/debian/changelog trantor-1.5.12+ds/debian/changelog
--- trantor-1.5.12+ds/debian/changelog	2023-09-13 13:45:24.0 +0200
+++ trantor-1.5.12+ds/debian/changelog	2024-04-21 12:04:17.0 +0200
@@ -1,3 +1,12 @@
+trantor (1.5.12+ds-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Pull fix from Ubuntu by Michael Hudson-Doyle:
++ Drop spurious Depends on libssl3 as package is currently built with no
+  TLS provider. Closes: #1068226
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 12:04:17 +0200
+
 trantor (1.5.12+ds-1) unstable; urgency=medium
 
   * New upstream release 1.5.12+ds (Closes: #1042181)
diff -Nru trantor-1.5.12+ds/debian/control trantor-1.5.12+ds/debian/control
--- trantor-1.5.12+ds/debian/control	2023-06-13 14:51:48.0 +0200
+++ trantor-1.5.12+ds/debian/control	2024-04-21 12:04:17.0 +0200
@@ -11,7 +11,7 @@
 
 Package: libtrantor1
 Architecture: any
-Depends: libssl3, libc-ares2, ${misc:Depends}, ${shlibs:Depends}
+Depends: libc-ares2, ${misc:Depends}, ${shlibs:Depends}
 Description: Non-blocking I/O cross-platform TCP network library
  Trantor is a non-blocking I/O cross-platform TCP network library, using C++14.
  Drawing on the design of Muduo Library


signature.asc
Description: PGP signature

Bug#1068608: tfortune dependencies unsatisfiable on 32-bit non-i386 architectures.

[Andreas Metzler]

On 2024-04-08 Andre Noll  wrote:
> On Sun, Apr 07, 22:02, Peter Michael Green wrote:

> > After being rebuilt for the time64 transition, tfortune
> > depends on both liblopsub1 and liblopsub1t64. As a
> > result it is uninstallable on architectures that are undergoing
> > the time64 transition (armel, armhf and some debian-ports
> > architectures).
> > 
> > Ubuntu has already fixed this issue by removing the hardcoded
> > dependency on liblopsub1.
> > 
> > https://launchpadlibrarian.net/720835658/tfortune_1.0.1-1build1_1.0.1-1ubuntu1.diff.gz

> This was fixed already on February 2nd as suggested by Steve, see
> upstream commit f40f0aae211f. Please let me know if any further action
> is required on my part.

Hello Andre,

Well, it needs to be uploaded.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#1068689: urfkill: diff for NMU version 0.5.0-7.2

[Andreas Metzler]

Control: tags 1068689 + patch
Control: tags 1068689 + pending

Dear maintainer,

I've prepared an NMU for urfkill (versioned as 0.5.0-7.2) and
uploaded it to DELAYED/00.

Regards Andreas
diff -Nru urfkill-0.5.0/debian/changelog urfkill-0.5.0/debian/changelog
--- urfkill-0.5.0/debian/changelog	2023-09-06 15:48:31.0 +0200
+++ urfkill-0.5.0/debian/changelog	2024-04-21 11:43:27.0 +0200
@@ -1,3 +1,10 @@
+urfkill (0.5.0-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop hardcoded dependency on libglib2.0-0. Closes: #1068689
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 11:43:27 +0200
+
 urfkill (0.5.0-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru urfkill-0.5.0/debian/control urfkill-0.5.0/debian/control
--- urfkill-0.5.0/debian/control	2023-09-06 15:47:18.0 +0200
+++ urfkill-0.5.0/debian/control	2024-04-21 11:42:51.0 +0200
@@ -10,7 +10,7 @@
 Architecture: linux-any
 Multi-Arch: foreign
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, libglib2.0-0, libdbus-1-3, libdbus-glib-1-2, dbus, libgudev-1.0-0, libpolkit-gobject-1-0, libexpat1, default-logind | logind
+Depends: ${shlibs:Depends}, ${misc:Depends}, libdbus-1-3, libdbus-glib-1-2, dbus, libgudev-1.0-0, libpolkit-gobject-1-0, libexpat1, default-logind | logind
 Description: wireless killswitch management daemon for laptops
  The urfkill daemon allow managing the rfkill-related hotkeys
  and the killswitches in a more configurable way for the common RF


signature.asc
Description: PGP signature

Bug#1069307: FTBFS: configure: error: must specify --with-locking-method option

[Andreas Metzler]

Control: tags -1 patch

On 2024-04-19 Andrey Rakhmatullin  wrote:
> Source: courier
> Version: 1.0.16-3.2
> Severity: serious
> Tags: ftbfs

> https://buildd.debian.org/status/fetch.php?pkg=courier=armel=1.0.16-3.2%2Bb4=1712019536=0

> checking for locking method... configure: error: must specify --with-locking-
> method option
> configure: error: ./configure failed for libs/liblock
[...]

Multiple autoconf tests are thrown by
-Wno-error=implicit-function-declaration.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Fixx FTBFS due to implicit declarations in autoconf tests.
Author: Andreas Metzler 
Bug-Debian: https://bugs.debian.org/1069307
Origin: vendor
Last-Update: 2024-04-20

--- a/libs/ldapaddressbook/configure.ac
+++ b/libs/ldapaddressbook/configure.ac
@@ -52,10 +52,11 @@ then
 	AC_TRY_LINK([
 #include 
 #if HAVE_LBER_H
 #include 
 #endif
+#define LDAP_DEPRECATED 1
 #include 
 ],
 [
 	LDAP *p=NULL;
 
--- a/libs/liblock/locktest.c
+++ b/libs/liblock/locktest.c
@@ -15,10 +15,13 @@
 #endif
 #include	
 #include	
 #include	
 #include	
+#include	
+#include	
+
 
 int main()
 {
 #define FILENAME	"courier-imap.locktest.XX"
 int	fd[2];
--- a/libs/tcpd/configure.ac
+++ b/libs/tcpd/configure.ac
@@ -221,10 +221,11 @@ AC_TRY_RUN(
 
 changequote(<<,>>)
 
 #include	
 #include	
+#include	
 
 int main(int argc, char **argv)
 {
 int	pipefd[2];
 char	c;
--- a/libs/waitlib/confwait.c
+++ b/libs/waitlib/confwait.c
@@ -22,10 +22,12 @@
 #include	
 
 #define	INCLUDED_FROM_CONFIGURE
 #include	"waitlib.c"
 
+#include	
+
 #define	NUMPROCS	10
 
 static int numterminated=0;
 
 

Bug#1066396: lftp: diff for NMU version 4.9.2-2.1

[Andreas Metzler]

Control: tags 1066396 + pending

Dear maintainer,

I've prepared an NMU for lftp (versioned as 4.9.2-2.1) and uploaded it
to unstable. This the implements the minimal fix I sent to this bug
almost a month ago.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru lftp-4.9.2/debian/changelog lftp-4.9.2/debian/changelog
--- lftp-4.9.2/debian/changelog	2022-07-16 12:24:04.0 +0200
+++ lftp-4.9.2/debian/changelog	2024-04-20 14:28:35.0 +0200
@@ -1,3 +1,14 @@
+lftp (4.9.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Minimal change to fix FTBFS with -Werror=implicit-function-declaration
++ ftbfs_implicit.diff - Fixup configure*.
++ Use selective touch in debian/rules to allow changing configure*
+  without using dh_autoreconf.
+Closes: #1066396
+
+ -- Andreas Metzler   Sat, 20 Apr 2024 14:28:35 +0200
+
 lftp (4.9.2-2) unstable; urgency=medium
 
   * lftp.tech domain doesn't work anymore; switch back to lftp.yar.ru
diff -Nru lftp-4.9.2/debian/patches/ftbfs_implicit.diff lftp-4.9.2/debian/patches/ftbfs_implicit.diff
--- lftp-4.9.2/debian/patches/ftbfs_implicit.diff	1970-01-01 01:00:00.0 +0100
+++ lftp-4.9.2/debian/patches/ftbfs_implicit.diff	2024-04-20 14:24:10.0 +0200
@@ -0,0 +1,20 @@
+--- lftp-4.9.2.orig/configure
 lftp-4.9.2/configure
+@@ -57429,6 +57429,7 @@ else
+   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+ /* end confdefs.h.  */
+ 
++	#include 
+ 	 int main()
+ 	 {
+ 	unsigned long long x=0,x1;
+--- lftp-4.9.2.orig/m4/needtrio.m4
 lftp-4.9.2/m4/needtrio.m4
+@@ -9,6 +9,7 @@ AC_DEFUN([LFTP_NEED_TRIO],[
+   else
+ 
+   AC_RUN_IFELSE([AC_LANG_SOURCE([[
++	#include 
+ 	 int main()
+ 	 {
+ 	unsigned long long x=0,x1;
diff -Nru lftp-4.9.2/debian/patches/series lftp-4.9.2/debian/patches/series
--- lftp-4.9.2/debian/patches/series	2022-07-16 12:24:04.0 +0200
+++ lftp-4.9.2/debian/patches/series	2024-04-20 14:27:34.0 +0200
@@ -1,3 +1,4 @@
 config-dns-inet6_before_inet.patch
 lftp_sys-stdint-kfreebsd.patch
 lftp_gnutls_certificate_verify_peers2-verify_server_certificates.patch
+ftbfs_implicit.diff
diff -Nru lftp-4.9.2/debian/rules lftp-4.9.2/debian/rules
--- lftp-4.9.2/debian/rules	2018-09-17 09:33:33.0 +0200
+++ lftp-4.9.2/debian/rules	2024-04-20 14:27:19.0 +0200
@@ -19,6 +19,9 @@
 
 #configure: configure-stamp
 configure-stamp:
+	# Avoid autoconf rebuild due to patching input files.
+	touch --reference=aclocal.m4 configure m4/needtrio.m4
+	touch --reference=Makefile.am m4/needtrio.m4
 	dh_testdir
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \


signature.asc
Description: PGP signature

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Andreas Metzler]

On 2024-02-23 Bo YU  wrote:
> Source: rnp
> Version: 0.17.0-3
> Severity: serious 

> Dear Maintainer,

> The package has a ftbfs issue on my local amd64 build:

> ```
> 260/260 Test #255: cli_tests-Encryption 
> ..   Passed   60.86 
> sec

> 98% tests passed, 6 tests failed out of 260

> Total Test time (real) =  71.61 sec

> The following tests FAILED:
>  90 - rnp_tests.test_ffi_security_profile (Failed)
> 159 - rnp_tests.test_rnp_access (Failed)
> 166 - rnp_tests.rnpkeys_generatekey_verifykeyHomeDirNoPermission 
> (Failed)
> 174 - rnp_tests.test_key_add_userid (Failed)
> 258 - cli_tests-EncryptElgamal (Failed)
> 259 - cli_tests-Misc (Failed)

FWIW I also get testsuite errors on current sid on amd64
The following tests FAILED:
 83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
 90 - rnp_tests.test_ffi_security_profile (Failed)
174 - rnp_tests.test_key_add_userid (Failed)
254 - cli_tests-EncryptElgamal (Failed)

Upstream's GIT head does not fail. I tried bisecting but gave up, there
are too many errors, especially when gtest was integrated and tried to
build itself with -Werror. Ouch.

cu Andreas

Bug#1065538: bind9-libs hard-codes a dependency on libuv1

[Andreas Metzler]

On 2024-03-06 Ondřej Surý  wrote:
>> On 6. 3. 2024, at 12:45, Matthias Klose  wrote:
 
>> Package: bind9-libs
>> Version: 1:9.19.21-1
>> Severity: serious
>> Tags: sid trixie

>> bind9-libs hard-codes a dependency on libuv1, that should be
>> libuv1t64 now. But better derive it form the libuv1-dev dependency.

> The reason why we do so is that libuv has some changes between version
> that don’t propagate to ABI. I might be able to drop this in unstable
> though and just keep it for backports.

Hello,

does the reported issue actually exist?

I just cannot find the hardcoded dependency in the source package.

ametzler@argenau:/dev/shm//bind9-9.19.21$ dpkg-parsechangelog -SVersion
1:9.19.21-1
ametzler@argenau:/dev/shm//bind9-9.19.21$ grep -r libuv1 debian/
debian/changelog:  * Add libuv1-dev, libcmocka-dev, libedit-dev and zlib1g-dev 
to B-D
debian/control:   libuv1-dev,
(sid)ametzler@argenau:/dev/shm//bind9-9.19.21$ apt-cache show bind9-libs | 
grep -E '^Version|^Dep'
Version: 1:9.19.21-1+b1
Depends: libc6 (>= 2.34), libfstrm0 (>= 0.2.0), libgssapi-krb5-2 (>= 1.17), 
libjemalloc2 (>= 4.0.0), libjson-c5 (>= 0.15), libkrb5-3 (>= 1.6.dfsg.2), 
liblmdb0 (>= 0.9.7), libmaxminddb0 (>= 1.3.0), libnghttp2-14 (>= 1.12.0), 
libprotobuf-c1 (>= 1.0.1), libssl3t64 (>= 3.0.0), liburcu8t64 (>= 0.13.0), 
libuv1t64 (>= 1.38.0), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init'

[Andreas Metzler]

On 2024-03-23 Diederik de Haas  wrote:
[...]
> 2) near the end of your build log is the following message:
> "../os/meson.build:63:8: ERROR: Problem encountered: secure-rpc requested, 
> but 
> neither libtirpc or libc RPC support were found"
> And that matches the build issue mentioned in #1065184.

> If you agree, please merge these two bugs.
> FTR: Bug #1065184 is already fixed in git.

FWIW I can cobnfirm that xwayland builds successfully if libtirpc-dev is
installed.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066010: dvdisaster: diff for NMU version 0.79.10-3.1

[Andreas Metzler]

Control: tags 1066010 + patch
Control: tags 1066010 + pending

Dear maintainer,

I've prepared an NMU for dvdisaster (versioned as 0.79.10-3.1) and
uploaded it to DELAYED/00.

Kind regards
Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru dvdisaster-0.79.10/debian/changelog dvdisaster-0.79.10/debian/changelog
--- dvdisaster-0.79.10/debian/changelog	2024-01-13 16:05:58.0 +0100
+++ dvdisaster-0.79.10/debian/changelog	2024-04-07 18:38:18.0 +0200
@@ -1,3 +1,10 @@
+dvdisaster (0.79.10-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration Closes: #1066010
+
+ -- Andreas Metzler   Sun, 07 Apr 2024 18:38:18 +0200
+
 dvdisaster (0.79.10-3) unstable; urgency=medium
 
   * Team upload
diff -Nru dvdisaster-0.79.10/debian/patches/38-ftbfs-implicit-functions.diff dvdisaster-0.79.10/debian/patches/38-ftbfs-implicit-functions.diff
--- dvdisaster-0.79.10/debian/patches/38-ftbfs-implicit-functions.diff	1970-01-01 01:00:00.0 +0100
+++ dvdisaster-0.79.10/debian/patches/38-ftbfs-implicit-functions.diff	2024-04-07 18:37:13.0 +0200
@@ -0,0 +1,33 @@
+Description: Fix FTBFS with -Werror=implicit-function-declaration
+Author: Andreas Metzler 
+Bug-Debian: https://bugs.debian.org/1066010
+Origin: vendor
+Forwarded: no
+Last-Update: 2024-04-07
+
+--- dvdisaster-0.79.10.orig/scripts/bash-based-configure
 dvdisaster-0.79.10/scripts/bash-based-configure
+@@ -1188,6 +1188,7 @@ function REQUIRE_MOTIF()
+ 
+cat >conftest.c <
++#include 
+ int main()
+ {  printf("%d.%d.%d\n",XmVERSION,XmREVISION,XmUPDATE_LEVEL);
+ }
+@@ -1215,6 +1216,7 @@ EOF
+ 
+cat >conftest.c <
++#include 
+ int main()
+ {  printf("%s\n",LesstifVERSION_STRING);
+ }
+@@ -1373,6 +1375,7 @@ EOF
+ 
+cat >conftest.c <
++#include 
+ int main(int argc, char *argv[])
+ { g_malloc(1024); 
+ 
diff -Nru dvdisaster-0.79.10/debian/patches/series dvdisaster-0.79.10/debian/patches/series
--- dvdisaster-0.79.10/debian/patches/series	2024-01-13 16:05:58.0 +0100
+++ dvdisaster-0.79.10/debian/patches/series	2024-04-07 18:35:42.0 +0200
@@ -17,3 +17,4 @@
 36-fix-parallelism.patch
 37-suggest-dvdisaster-doc.patch
 0032-Fix-for-compilation-error-under-gcc-10.patch
+38-ftbfs-implicit-functions.diff


signature.asc
Description: PGP signature

Bug#1068219: chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.

[Andreas Metzler]

Control: tags -1 patch

On 2024-04-02 Peter Michael Green  wrote:
> Package: chatty
> Version: 0.8.2-1
> Severity: serious
> User: debian-...@lists.debian.org
> Usertag: time-t

> After being rebuilt for the time64 transition, chatty depends
> on both libpurple0 and libpurple0t64. As a
> result it is uninstallable on architectures that are undergoing
> the time64 transition (armel, armhf and some debian-ports
> archictures).

Hello,

This is caused by
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ head debian/shlibs.local
libjabber 0 libpurple0
and 
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ objdump -p 
chatty-0.8.2/debian/chatty/usr/bin/chatty  | grep NEEDE | grep jab
  NEEDED   libjabber.so.0
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ ldd -r 
chatty-0.8.2/debian/chatty/usr/bin/chatty | grep jabb
libjabber.so.0 => /usr/lib/arm-linux-gnueabihf/purple-2/libjabber.so.0 
(0xb69b6000)
(It uses an rpath to find it.)

So afaiui this could be fixed by pointing to libpurple0t64 in
debian/shlibs.local.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066005: epic4: FTBFS on arm{el,hf}: gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration]

[Andreas Metzler]

Control: tags -1 fixed-upstream

On 2024-03-10 Sebastian Ramacher  wrote:
> Source: epic4
> Version: 1:2.10.10-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org

> https://buildd.debian.org/status/fetch.php?pkg=epic4=armhf=1%3A2.10.10-1%2Bb5=1709806588=0

> gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  
> -I./../include -I../include -c gailib.c
> gailib.c: In function ‘get_name’:
> gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you 
> mean ‘strncpy’? [-Werror=implicit-function-declaration]
>95 | strlcpy((ai)->ai_canonname, (str), strlen(str) + 1);\
>   | ^~~

This is fixed in 2.10.11.

cu Andreas

Bug#1066115: mpg321: diff for NMU version 0.3.2-3.2

[Andreas Metzler]

Control: tags 1066115 + pending

Dear maintainer,

I've prepared an NMU for mpg321 (versioned as 0.3.2-3.2) and
uploaded it to DELAYED/00.

Kind regards
Andreas
diff -Nru mpg321-0.3.2/debian/changelog mpg321-0.3.2/debian/changelog
--- mpg321-0.3.2/debian/changelog	2020-07-23 17:22:42.0 +0200
+++ mpg321-0.3.2/debian/changelog	2024-03-27 15:40:50.0 +0100
@@ -1,3 +1,11 @@
+mpg321 (0.3.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * 14_ftbfs_implicit.diff: Fix build error with
+-Wno-error=implicit-function-declaration. Closes: #1066115
+
+ -- Andreas Metzler   Wed, 27 Mar 2024 15:40:50 +0100
+
 mpg321 (0.3.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mpg321-0.3.2/debian/patches/ftbfs_implicit.diff mpg321-0.3.2/debian/patches/ftbfs_implicit.diff
--- mpg321-0.3.2/debian/patches/ftbfs_implicit.diff	1970-01-01 01:00:00.0 +0100
+++ mpg321-0.3.2/debian/patches/ftbfs_implicit.diff	2024-03-27 15:39:14.0 +0100
@@ -0,0 +1,34 @@
+Description: Fix build error with -Wno-error=implicit-function-declaration
+Author: Andreas Metzler 
+Origin: vendor
+Forwarded: no
+Last-Update: 2024-03-27
+Bug-Debian: https://bugs.debian.org/1066115
+
+
+--- mpg321-0.3.2.orig/mpg321.h
 mpg321-0.3.2/mpg321.h
+@@ -242,7 +242,7 @@ typedef struct {
+ } fft_state;
+ 
+ typedef short int sound_sample;
+-//void fft_perform(const sound_sample *input, double *output, fft_state *state);
++void fft_perform(const sound_sample *input, double *output, fft_state *state);
+ 
+ fft_state *fft_init(void);
+ 
+@@ -290,6 +290,14 @@ output_frame *Output_Queue;
+ /* Shared total decoded frames */
+ decoded_frames *Decoded_Frames;
+ 
++int init_alsa_volume_control(char *name);
++int calc_http_length(buffer *buf);
++long mpg321_alsa_get_volume();
++void mpg321_alsa_set_volume(long value);
++void do_basicauth();
++ao_device *open_ao_playdevice_buffer(struct mad_header const *header);
++int check_default_play_device_buffer();
++
+ #if defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
+ /* */
+ #else
diff -Nru mpg321-0.3.2/debian/patches/series mpg321-0.3.2/debian/patches/series
--- mpg321-0.3.2/debian/patches/series	2019-03-13 15:57:59.0 +0100
+++ mpg321-0.3.2/debian/patches/series	2024-03-27 15:37:21.0 +0100
@@ -1 +1,2 @@
 handle_illegal_bitrate_value.patch
+ftbfs_implicit.diff

Bug#1066115: mpg123: FTBFS: error: implicit declaration of function ‘mpg321_alsa_get_volume’ [-Werror=implicit-function-declaration]

[Andreas Metzler]

On 2024-03-26 Joachim Reichel  wrote:
> Hi Andreas,

> usually I would have implemented your suggestion (and I don't mind anyone
> implementing it), but I'm not really keen on investing in a dependency that
> hasn't seen a single upstream release in 12 years and where the last upload
> was an NMU four years ago from myself dealing with a similar problem. I hope
> that explains why I took the route of this suboptimal shortcut.

OK, I will probably do a superceding NMU then. (And try to get this
removed from sid in the longer term.)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066115: mpg123: FTBFS: error: implicit declaration of function ‘mpg321_alsa_get_volume’ [-Werror=implicit-function-declaration]

[Andreas Metzler]

On 2024-03-22 Joachim Reichel  wrote:
> tag 1066115 + patch
> thanks

> Hi,

> attached is the debdiff for the NMU, uploaded to delayed/10. Similar to the
> previous NMU it adds -Wno-error=implicit-function-declaration to downgrade
> these errors back into warnings again.
[...]

That seems to be suboptimal. How about adding the missing declarations
instead?

cu Andreas

--- mpg321-0.3.2.orig/mpg321.h
+++ mpg321-0.3.2/mpg321.h
@@ -242,7 +242,7 @@ typedef struct {
 } fft_state;
 
 typedef short int sound_sample;
-//void fft_perform(const sound_sample *input, double *output, fft_state *state);
+void fft_perform(const sound_sample *input, double *output, fft_state *state);
 
 fft_state *fft_init(void);
 
@@ -290,6 +290,14 @@ output_frame *Output_Queue;
 /* Shared total decoded frames */
 decoded_frames *Decoded_Frames;
 
+int init_alsa_volume_control(char *name);
+int calc_http_length(buffer *buf);
+long mpg321_alsa_get_volume();
+void mpg321_alsa_set_volume(long value);
+void do_basicauth();
+ao_device *open_ao_playdevice_buffer(struct mad_header const *header);
+int check_default_play_device_buffer();
+
 #if defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
 /* */
 #else

Bug#1067664: FTBFS: dh_installdocs: error: Requested unknown package libspf2-2 via --link-doc

[Andreas Metzler]

Source: libspf2
Version: 1.2.10-8.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Even with fixing the -Werror=implicit-function-declaration build error
libspf2 also fails to build (dpkg-buildpackage -b) at dh_installdocs
with:

mv debian/spfquery/usr/sbin/spfd debian/spfquery/usr/sbin/spfd.libspf2
dh_installdocs -a --link-doc=libspf2-2
dh_installdocs: error: Requested unknown package libspf2-2 via --link-doc, 
expected one of: libspf2-2t64 libspf2-dev spfquery libmail-spf-xs-perl
make: *** [debian/rules:68: binary-arch] Error 25

I think this will also be fixed by the change in #1067204 but filing for
completeness sake.

I inted to fix this by NMU.

cu Andreas

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

[Andreas Metzler]

Control: tags -1 patch

On 2024-03-24 Andrey Rakhmatullin  wrote:
> On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote:
> > > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> > >  2540 | # include "trio.h"
> > >   |   ^~~~
> (this suggests that using trio is not actually supported but that's
> irrelevant)
> This is caused by the stdio detection failing and should be fixed by
> adding #include  to the test case code in m4/needtrio.m4 but this
> package doesn't run autoreconf so fixing d/rules to at least do that is
> also needed.
[...]

As a hotfix touch-magic can also be used.

cu Andreas

diff --git a/debian/rules b/debian/rules
index e0872ed..ab41336 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,6 +19,9 @@ CFLAGS += -g -Wall
 
 #configure: configure-stamp
 configure-stamp:
+	# Avoid autoconf rebuild due to patching input files.
+	touch --reference=aclocal.m4 configure m4/needtrio.m4
+	touch --reference=Makefile.am m4/needtrio.m4
 	dh_testdir
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \
--- lftp-4.9.2.orig/configure
+++ lftp-4.9.2/configure
@@ -57429,6 +57429,7 @@ else
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
+	#include 
 	 int main()
 	 {
 	unsigned long long x=0,x1;
--- lftp-4.9.2.orig/m4/needtrio.m4
+++ lftp-4.9.2/m4/needtrio.m4
@@ -9,6 +9,7 @@ AC_DEFUN([LFTP_NEED_TRIO],[
   else
 
   AC_RUN_IFELSE([AC_LANG_SOURCE([[
+	#include 
 	 int main()
 	 {
 	unsigned long long x=0,x1;

Bug#1066375: canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

[Andreas Metzler]

On 2024-03-13 Lucas Nussbaum  wrote:
> Source: canna
> Version: 3.7p3-20
> Severity: serious
[...]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Hello,

I started working on this, but stopped. There are dozens of instances of
implicit internal[1] function references without prototype. The whole thing
looks very dated.

I cannot judge how important canna is, popcon is low (29 installations).
It might be time to drop canna, Fedora already did, there has not been
upstream work for more almost 20 years, also it has been maintained with
QA uploads and NMUs since 2008

Cc-ing packages with b-d on libcanna1g-dev to perhaps get some further
input.

cu Andreas


[1] defined without prototype in foo.c, also used in bar.c
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066433: uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type

[Andreas Metzler]

Control: tags -1 patch

On 2024-03-13 Lucas Nussbaum  wrote:
> Source: uim
> Version: 1:1.8.8-9.2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie

> Hi,

> During a rebuild of all packages in sid, your package failed to build
> on amd64.


> Relevant part (hopefully):
[...]
> > bsd-snprintf.c: In function ‘dopr’:
> > bsd-snprintf.c:104:38: error: assignment to expression with array type
> >   104 | #   define VA_COPY(dest, src) (dest) = (src)
> >   |  ^
> > bsd-snprintf.c:186:9: note: in expansion of macro ‘VA_COPY’
> >   186 | VA_COPY(args, args_in);
> >   | ^~~
[...]

I intend to fix this by NMU.

cu Andreas
Avoid an undeclared exit function call in the snprintf configure check.
This improves compatibility with strict(er) C99 compilers, which may
not support implicit function declarations because they were removed
from the C language in 1999.

Submitted upstream: 

diff --git a/configure.ac b/configure.ac
index 042d68927b76435c..84fcd38c9d3245db 100644
--- a/configure.ac
+++ b/configure.ac
@@ -595,7 +595,7 @@ if test "x$ac_cv_func_snprintf" = xyes; then
 	AC_RUN_IFELSE(
 		[AC_LANG_SOURCE([[
 #include 
-int main(void){char b[5];snprintf(b,5,"123456789");exit(b[4]!='\0');}
+int main(void){char b[5];snprintf(b,5,"123456789");return b[4]!='\0';}
 		]])],
 		[AC_MSG_RESULT(yes)],
 		[

Bug#1066963: xmorph: FTBFS with -Werror=implicit-function-declaration

[Andreas Metzler]

Source: xmorph
Version: 1:20150712-5
Severity: serious
Tags: ftbfs

Hello,

there are multiple implicit function errors when trying to build
xmorph, some trivial, but also an API issue:
8X--
In file included from RgbaImage.c:935:
RgbaImage.c: In function 'rgbaImageWarp':
warp.h:19:20: error: implicit declaration of function 'warp_image_inv_new'; did 
you mean 'warp_image_inv_old'? [-Werror=implicit-function-declaration]
   19 | #define warp_image warp_image_inv_new
  |^~
RgbaImage.c:963:3: note: in expansion of macro 'warp_image'
  963 |   warp_image(img_orig->ri, img_warp->ri, img_orig->ncols,
  |   ^~
8X--

warp.h contains
#define warp_image warp_image_inv_new
with warp_image_inv_new being defined in warp2.h. i.e. #include 
without including warp2.h first triggers an implicit declaration of
function error. OTOH warp2.h #includes warp.h so if everything switched
to warp.h we would be fine, but then there is no point in  having a
separate warp.h.

Perhaps the proper fix would be to stop shipping an (unused) library.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066137: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Andreas Metzler]

On 2024-03-13 Thorsten Glaser  wrote:
[...]
> >It is fixed in 2.4 and I am very reluctant to backport major packaging
> >updates to 2.2

> For some values of major; Helmut already verified that the resulting
> binary packages are identical, and…

> >since I think we will need to ship some kind of 2.4 in trixie.

> … this massively helps with the current transition in unstable,
> which has to come before thinking of trixie.
[...]

Good morning,

Afaict ghostscript/fig2dev have stopped being blockers so I do not plan
on doing another upload (with more work for the other autobuilders) just
to temporarily disable these b-ds.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066137: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Andreas Metzler]

Control: notfound 1066137 2.4.3-2
Control: close 1066137 2.4.3-2

On 2024-03-14 Sune Stolborg Vuorela  wrote:
> On Wednesday, March 13, 2024 7:10:13 PM CET Andreas Metzler wrote:
>> I have upload a fix for 2.2, probably will not be able to spend any time
>> on 1.x or 2.4 before the weekend.

> Looks like 2.4 is fixed upstream a couple of years
> https://dev.gnupg.org/rGddc6f7d194918791ac9dff0e5af4b80933189afd

Thanks for the pointer.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066138: gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration

[Andreas Metzler]

On 2024-03-13 Thorsten Glaser  wrote:
> clone 1066137 -1
> reassign -1 gnupg1 1.4.23-1.1
> retitle -1 gnupg1: fails to build gpgkeys_ldap, probably due to 
> -Werror=implicit-function-declaration
> thanks

> Dixi quod…

> >This matches the following failure mode at the end of the build:

> Same for gnupg1 according to the buildd page:
> https://buildd.debian.org/status/package.php?p=gnupg1

Hello Thorsten,
I have upload a fix for 2.2, probably will not be able to spend any time
on 1.x or 2.4 before the weekend.

> >Trying to binNMU gnupg2 to make it installable during t64 transition,

> Please do also reduce the B-D as Helmut noted in #980768; specifically,
> dropping ghostscript, imagemagick, libcurl4-gnutls-dev and transfig
> from src:gnupg2 produces identical binary packages according to his
> analysis. Perhaps some of that applies to gnupg1 as well. This will
> help tremendously.

It is fixed in 2.4 and I am very reluctant to backport major packaging
updates to 2.2 since I think we will need to ship some kind of 2.4 in
trixie.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open

[Andreas Metzler]

Control: forcemerge 1066137 1066744
Control: found 1066137 2.4.3-2

On 2024-03-12 Thorsten Glaser  wrote:
> Source: gnupg2
> Version: 2.2.40-1.1
> Severity: serious
> Justification: ftbfs
> X-Debbugs-Cc: t...@mirbsd.de

> Trying to binNMU gnupg2 to make it installable during t64 transition,
> I notice the following configury output:

> […]
> checking for library containing dn_skipname... none required
> checking whether the resolver is usable... yes
> checking whether LDAP via "-lldap" is present and sane... no
[...]

I am going to take a look at this.

I am also marking this as applying to experimental, too. I have not
done a test-build yet but ldap.m4 looks similar.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1063316: marked as pending in xmorph

[Andreas Metzler]

Control: tag -1 pending

Hello,

Bug #1063316 in xmorph 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/debian-phototools-team/xmorph/-/commit/f7dfca3f49f85a978900b9a4438cbdc316a6eefc


Tighten xmorph/libmorph dependency.

libmorph has no other reverse dependencies but is involved in the t64
transition. Closes: #1063316


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063316

Bug#1065772: freewnn: FTBFS on arm{el,hf}:

[Andreas Metzler]

On 2024-03-09 Sebastian Ramacher  wrote:
> Source: freewnn
> Version: 1.1.1~a021+cvs20130302-7.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org

> https://buildd.debian.org/status/fetch.php?pkg=freewnn=armel=1.1.1%7Ea021%2Bcvs20130302-7.1=1709116867=0

> /bin/bash ../../libtool --mode=compile gcc -c -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -Dlinux -D_GNU_SOURCE 
> -D_POSIX_SOURCE -D_BSD_SOURCE  -DHAVE_CONFIG_H -I../../Wnn/include -I../.. 
> -DLIBDIR=\"/usr/share/wnn\" -DJAPANESE -DCHINESE -DKOREAN -DLATIN 
> -DWRITE_CHECK  ../../Wnn/etc/`basename bcopy.o .o`.c
> In file included from js.c:97:
> ../etc/pwd.c: In function ‘new_pwd’:
> ../etc/pwd.c:78:7: error: implicit declaration of function ‘time’ 
> [-Werror=implicit-function-declaration]
>78 |   x = time (NULL);
>   |   ^~~~
[...]

I will take a look at this bug, will do a QA-upload.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1064282: poppler: NMU diff for 64-bit time_t transition

[Andreas Metzler]

On 2024-03-01 Daniel Serpell  wrote:
> Source: poppler
> Followup-For: Bug #1064282
> Control: reopen 1064282

> As reported in bug 1065155, the provided patch was incorrect, the
> X-Time64-Compat header is set incorrectly to libpoppler-cpp0v5 for all
> the library packages.

Good Morning,

Also afaict (from browsing GIT history) the build-dependencies are
insufficient, X-Time64-Compat was initially added in debhelper 13.12.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1065107: exim4: FTBFS: missing build-dep on libnsl-dev

[Andreas Metzler]

On 2024-02-29 Aurelien Jarno  wrote:
> Source: exim4
> Version: 4.97-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: debian-gl...@lists.debian.org
> Usertags: libnsl-dev

> Dear maintainer,

> Starting with glibc 2.31, support for NIS (libnsl library) has been
> moved to a separate libnsl2 package. In order to allow a smooth
> transition, a libnsl-dev has been added to the libc6-dev package.

> This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
> part of the 64-bit time_t transition. This causes exim4 to FTBFS in sid
> with:
[...]
> This could be fixed by adding an explicit Build-Depends on libnsl-dev.
> The glibc change will likely be reverted in the short term, but given
> its a change we want to do for Trixie, this will only lower the severity
> of the bug.

Thanks, noted. I cannot fix it now though since sid seems to be broken
due to t64 with regards to pam, there is back and forth of package
renames and util-linux 2.39.3-6.1 pre-depends on both libpam0g and
libpam0t64.

cu Andreas

Bug#1064553: libgdiplus: build-error on current sid (all warnings being treated as errors)

[Andreas Metzler]

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

libgdiplus FTBFS on current sid:

make[7]: Entering directory '/dev/shm/x/libgdiplus-6.1+dfsg/gtest_build'
[ 12%] Building CXX object googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
In file included from 
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-all.cc:42:
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:
 In function 'bool testing::internal::StackGrowsDown()':
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1301:24:
 error: 'dummy' may be used uninitialized [-Werror=maybe-uninitialized]
 1301 |   StackLowerThanAddress(, );
  |   ~^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1290:13:
 note: by argument 1 of type 'const void*' to 'void 
testing::internal::StackLowerThanAddress(const void*, bool*)' declared here
 1290 | static void StackLowerThanAddress(const void* ptr, bool* result) {
  | ^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1299:7:
 note: 'dummy' declared here
 1299 |   int dummy;
  |   ^
cc1plus: all warnings being treated as errors
make[7]: *** [googletest/CMakeFiles/gtest.dir/build.make:76: 
googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o] Error 1

cu Andreas

Bug#1063403: libeegdev-dev,libeegdev0t64: both ship /usr/share/doc/libeegdev0/changelog.gz

[Andreas Metzler]

Comtrol: tags -1 patch

On 2024-02-07 Andreas Beckmann  wrote:
> Package: libeegdev-dev,libeegdev0t64
[...]
> Something weird happened after the package rename:

>   /usr/share/doc/libeegdev0/changelog.Debian.gz
>   /usr/share/doc/libeegdev0/changelog.gz

> Are now shipped by libeegdev-dev and libeegdev0t64 while they should be
> in none of these packages.
[...]
> Control files: lines which differ (wdiff format)
> 
> Depends: {+libeegdev0t64 (= 0.2-8.1~exp1),+} libeegdev0 (= [-0.2-8)-] 
> {+0.2-8.1~exp1)+}
> Installed-Size: [-71-] {+87+}
> Version: [-0.2-8-] {+0.2-8.1~exp1+}

> Also the libeegdev0 dependency is still there ...

Hello,

This is another instance (well, the second one ;-) ) of not changing the
dh_installdocs --link-doc= argument in debian/rules. dh_installdocs also
generates the dependency.

-dh_installdocs --link-doc=libeegdev0
+dh_installdocs --link-doc=libeegdev0t64

cu Andreas

Bug#1063401: atm-tools: has gained /usr/share/doc/libatm1/changelog.*

[Andreas Metzler]

Control: tags -1 patch

On 2024-02-07 Andreas Beckmann  wrote:
> Package: atm-tools
> Version: 1:2.5.1-5.1~exp1
[...]
> atm-tools/experimental has gained two unexpected files, causing file
> conflicts on upgrades:
[...]
> There is still an libatm1 dependency, and the new libatm1t64 dependency
> seems to miss the epoch.

Hello,

Both issues are fixed by a one-line-change, a dh_lintian call should
also be added.

diff -Nru linux-atm-2.5.1/debian/rules linux-atm-2.5.1/debian/rules
--- linux-atm-2.5.1/debian/rules2019-07-19 11:14:25.0 +0200
+++ linux-atm-2.5.1/debian/rules2024-02-10 13:31:02.0 +0100
@@ -72,7 +72,7 @@
dh_testroot
dh_install --sourcedir=debian/tmp
rm debian/atm-tools/usr/share/man/man8/br2684ctl.8
-   dh_installdocs --link-doc=libatm1
+   dh_installdocs --link-doc=libatm1t64
dh_installinit --init-script=atm
dh_installsystemd --name=atm
dh_installman
@@ -80,6 +80,7 @@
dh_link
dh_strip
dh_compress
+   dh_lintian
dh_fixperms
dh_makeshlibs -- -c4
dh_installdeb

cu Andreas

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

[Andreas Metzler]

On 2024-02-06 Helmut Grohne  wrote:
> Package: libselinux1t64

[...]> This looks fairly innocuous. We create a minimal sid chroot and install
> libselinux1t64 using apt. What could possibly go wrong? Well, apt thinks
> that it would be a good idea to avoid coinstalling breaking packages and
> first removes libselinux1 before proceeding to install libselinux1t64.
> Unfortunately, libselinux1 is transitively essential and dpkg links it,
[...]
> both dpkg and tar are now broken. This is pretty bad. To make matters
> worse, the situation arises from the combination of Breaks + Provides
[...]

Hello,

color me stupid but isn't this fishy?

Package: libselinux1t64
Replaces: libselinux1
Provides: libselinux1 (= 3.5-2.1~exp1)
Breaks: libselinux1 (<< 3.5-2.1~exp1)

Afaiui libselinux1t64 must not fullfill dpkg 1.22.4's dependency on
"libselinux1 (>= 3.1~)". dpkg needs to be rebuilt and the rebuilt
version gets a dep on "libselinux1t64 (>= 3.5)".

Will ${t64:Provides} stop expanding to "libselinux1 = ${binary:Version
for real t64-builds? (The ones in experimental are not.) If that is case
this bug and this way of testing does not make sense.

Otherwise the plan looks flawed.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1063170: nettle: NMU diff for 64-bit time_t transition

[Andreas Metzler]

On 2024-02-05 Niels Möller  wrote:
> Graham Inggs  writes:

>> we have identified nettle as a source package shipping runtime
>> libraries whose ABI either is affected by the change in size of
>> time_t, or could not be analyzed via abi-compliance-checker (and
>> therefore to be on the safe side we assume is affected).

[...]
> However, this code is in the *libhogweed* so-file, so transitioning
> *libnettle* is probably not needed.
[...]

The analysis looked at the headers and ...
|  In multi-library packages, there is no reliable way to map from a set of
|  headers in a dev package to specific shared libraries in a runtime library
|  package that's not additionally computationally prohibitive; we therefore
|  conservatively assume that if any headers from a source package show
|  time_t ABI changes, all the runtime library packages from the source
|  package are affected by the transition.

cu Andreas

Bug#1061667: netpbm: ppmtowinicon crash makes kcemu FTBFS

[Andreas Metzler]

On 2024-01-28 Adrian Bunk  wrote:
> ppmtowinicon -andpgms \
>   kcemu-winicon_16x16.ppm kcemu-winicon_16x16.alpha.pgm \
>   kcemu-winicon_32x32.ppm kcemu-winicon_32x32.alpha.pgm \
>   kcemu-winicon_48x48.ppm kcemu-winicon_48x48.alpha.pgm \
>   > kcemu-winicon.ico
> malloc(): invalid size (unsorted)
> /bin/bash: line 5: 3775943 Aborted ppmtowinicon -andpgms 
> kcemu-winicon_16x16.ppm kcemu-winicon_16x16.alpha.pgm kcemu-winicon_32x32.ppm 
> kcemu-winicon_32x32.alpha.pgm kcemu-winicon_48x48.ppm 
> kcemu-winicon_48x48.alpha.pgm > kcemu-winicon.ico
> make[2]: *** [Makefile:929: kcemu-winicon.ico] Error 134

lets save a copy of the failing input set.

cu Andreas

Bug#1042659: closed by Debian FTP Masters (reply to Félix Sipma ) (Bug#1042659: fixed in restic 0.16.0-1)

[Andreas Metzler]

On 2023-11-01 Debian Bug Tracking System  wrote:
[...]
> #1042659: restic: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all 
> arguments converted during string formatting

> It has been closed by Debian FTP Masters  
> (reply to Félix Sipma ).
[...]
>* New upstream version 0.16.0 (Closes: #1031235, #1042659)
[...]

In future could we pretty pretty pretty please have a minimum amount of
communication? If you sent something like "I am working on this" or
"going to work on this in the next days" to the bug report I would not
have wasted time and effort on diagnosing the issue, digging out the
patch and preparing and testing a NMU.

TIA, cu andreas

Bug#1042659: restic: diff for NMU version 0.14.0-1.1

[Andreas Metzler]

Control: tags 1042659 + pending

Dear maintainer,

I've prepared an NMU for restic (versioned as 0.14.0-1.1) and uploaded
it to DELAYED/10. (Autoremoval from testing is scheduled on Nov 14)
Please feel free to tell me if I should delay it longer.

Kind regards

Andreas
diff -Nru restic-0.14.0/debian/changelog restic-0.14.0/debian/changelog
--- restic-0.14.0/debian/changelog	2022-08-27 12:48:55.0 +0200
+++ restic-0.14.0/debian/changelog	2023-11-01 13:49:52.0 +0100
@@ -1,3 +1,11 @@
+restic (0.14.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 0002-doc-fix-building-with-Sphinx-6.patch from upstream to fix
+FTBFS against sphinx >= 6. Closes: #1042659
+
+ -- Andreas Metzler   Wed, 01 Nov 2023 13:49:52 +0100
+
 restic (0.14.0-1) unstable; urgency=medium
 
   * New upstream version 0.14.0 (Closes: #1018154)
diff -Nru restic-0.14.0/debian/patches/0002-doc-fix-building-with-Sphinx-6.patch restic-0.14.0/debian/patches/0002-doc-fix-building-with-Sphinx-6.patch
--- restic-0.14.0/debian/patches/0002-doc-fix-building-with-Sphinx-6.patch	1970-01-01 01:00:00.0 +0100
+++ restic-0.14.0/debian/patches/0002-doc-fix-building-with-Sphinx-6.patch	2023-11-01 13:47:00.0 +0100
@@ -0,0 +1,23 @@
+From c4e6b198ae535eeac711fdd424ee20b367fd5624 Mon Sep 17 00:00:00 2001
+From: Michael Eischer 
+Date: Sun, 12 Mar 2023 11:45:26 +0100
+Subject: [PATCH] doc: fix building with Sphinx 6
+
+---
+ doc/conf.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/doc/conf.py b/doc/conf.py
+index 3c0af927b..3fd8dc119 100644
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -106,5 +106,5 @@ html_static_path = ['_static']
+ htmlhelp_basename = 'resticdoc'
+ 
+ extlinks = {
+-'issue': ('https://github.com/restic/restic/issues/%s', '#'),
++'issue': ('https://github.com/restic/restic/issues/%s', '#%s'),
+ }
+-- 
+2.42.0
+
diff -Nru restic-0.14.0/debian/patches/series restic-0.14.0/debian/patches/series
--- restic-0.14.0/debian/patches/series	2022-08-27 12:48:55.0 +0200
+++ restic-0.14.0/debian/patches/series	2023-11-01 13:47:04.0 +0100
@@ -1 +1,2 @@
 0001-privacy-breach.patch
+0002-doc-fix-building-with-Sphinx-6.patch


signature.asc
Description: PGP signature

Bug#1053310: Fixes for stable/oldstable?

[Andreas Metzler]

On 2023-10-31 Tomas Pospisek  wrote:
[...]
> PS: I'd prefer this bugreport to be open as long as the stable and
> oldstable packages are still vulnerable...

Hello Thomas,
The Debian BTS does not use a simple open/close logic, it tracks which
specific versions a bug applies to. If you look at
https://bugs.debian.org/cgi-bin/1053310 there is both textual info
("Found in version exim4/4.94.2-7 Fixed in version exim4/4.97~RC2-2")
and a nice graph in red and green to display this and the overview pages
can also show bugs applying to specific distributions. (Menu items at
the bottom of the page.) e.g. 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=stable;package=exim4-base
does not show this bug under "Resolved bugs".

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1053310: Fixes for stable/oldstable?

[Andreas Metzler]

On 2023-10-31 Tomas Pospisek  wrote:
> On Tue, 31 Oct 2023, Salvatore Bonaccorso wrote:
[...]
>> Fixes for CVE-2023-42117 and CVE-2023-42119 are right now considered
>> no-dsa (see comment on the security-tracker about it), and are going
>> to be fixed in the next point releases.

> The notes say:

> ***
> [bookworm] - exim4  (Only an issue if Exim4 run behind an
>  untrusted proxy-protocol proxy)
[...]
> So I think I can parse from those that CVE-2023-42117 is only critical when
> exim is run behind a "untrusted proxy-protocol proxy".

> Questions if you will:

> * what does "no-dsa" mean? DSA seems to mean Debian Security Announce.
>   Does it mean there is no DSA for that problem yet? What does it mean
>   when a CVE is considered "no-dsa" then? That no DSA will be released for
>   it?

Hello Thomas,

Exactly. The severity was judged to be very low, not "worth" the effort
of a DSA.

> * what is a "untrusted proxy-protocol proxy" in the context of a mail
>   transport agent? So exim shouldn't be used behind an untrusted socks
>   proxy? Well I have no real control who connects how to a public MTA...
>   anybody can connect to it to try his luck sending me email. That
>   includes untrusted socks proxies...

This
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-proxies.html
or more precisely part "1. Inbound proxies".

You need to explicitely configure exim to tell it that specific hosts
are acting as load-balancing proxy sitting in front of exim. I cannot
think of a szenario where these load-balancing proxies would not be
trusted machines. The issue is about weakening the chain a little bit -
take over the proxy first and then do something to the exim machines
behind.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1042659: restic: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting

[Andreas Metzler]

Colntrol: tags -1 patch

On 2023-07-30 Lucas Nussbaum  wrote:
> Source: restic
[...]
> restic fails to build with Sphinx 7.1 and docutils 0.20, both of which
> are currently available in experimental.

> Relevant part (hopefully):
[...]
> > 
> > Exception occurred:
> >   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, 
> > in role
> > title = caption % part
> > ^~
[...]
> Some notable changes in Sphinx 6 and Sphinx 7:
[...]
> - For packages using the extlinks extension, the caption should contain
>   exactly one "%s" placeholder (if caption is not None).


Hello,

fixed in upstream GIT.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
>From c4e6b198ae535eeac711fdd424ee20b367fd5624 Mon Sep 17 00:00:00 2001
From: Michael Eischer 
Date: Sun, 12 Mar 2023 11:45:26 +0100
Subject: [PATCH] doc: fix building with Sphinx 6

---
 doc/conf.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/conf.py b/doc/conf.py
index 3c0af927b..3fd8dc119 100644
--- a/doc/conf.py
+++ b/doc/conf.py
@@ -106,5 +106,5 @@ html_static_path = ['_static']
 htmlhelp_basename = 'resticdoc'
 
 extlinks = {
-'issue': ('https://github.com/restic/restic/issues/%s', '#'),
+'issue': ('https://github.com/restic/restic/issues/%s', '#%s'),
 }
-- 
2.42.0

Bug#1054786: gpgme1.0: FTBFS: dh_install: error: missing files, aborting

[Andreas Metzler]

Contol: tags 1039724 - pending
Contol: tags 1039724 - wontfix

On 2023-10-27 Lucas Nussbaum  wrote:
> Source: gpgme1.0
> Version: 1.18.0-3
[...]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

> Relevant part (hopefully):
[...]
> > dh_install: warning: Cannot find (any matches for) 
> > "debian/tmp/usr/lib/python3*/site-packages/gpg*.egg-info" (tried in ., 
> > debian/tmp)
[...]

Hello,

this is essentially a duplicate of #1039724.

However it cannot be hotfixed anymore by build-conflicting with
python3-setuptools since dh-python now depends on python3-setuptools
(Since 6.20231025).

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1053870: CVE-2023-42118 and perceived impact

[Andreas Metzler]

On 2023-10-20 Jeremy Stanley  wrote:
> It looks to me like the default Exim config in Debian explicitly
> calls /usr/bin/spfquery.mail-spf-perl from the spf-tools-perl
> package, not the libspf2 implementation supplied by the spfquery
> package. Also spf-tools-perl is suggested by exim4-base, while
> neither spfquery nor any other packages built from libspf2 seem to
> be referenced by any of the exim4 packages.
 [...]

Hello,

You seem to be looking at old packages, perhaps oldstable?
exim4-daemon-heavy in Debian 12 (bookworm) is linked against libspf2
and the default configuration has hooks to enable SPF lookups via
libsp2, not spf-tools-perl.

cu Andreas

Bug#1041731: Hyphens in man pages

[Andreas Metzler]

On 2023-10-15 Wookey  wrote:
[...]
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.

> However despite reading it all, and especially this bit:
> "Whenever I've maintained man pages in roff I tend to be precise in
> > the usage of - and \-, but TBH this has seemed like a lost battle,"

> I was left not actually know what - and \- represent, nor which one I
> _should_ be using in my man pages. And that seems to be the one thing
> we should be telling the 'average maintainer'.
[...]

Hello,

a pretty good guidance[1] is to

use "\-" whenever it refers to option ("-h", --help"), argument ("find
-mmin -2") or something else that is not natural language but something
that might be pasted, like a command-name ("ssh-add" or "dpkg-source")

and "-" everywhere else.

cu Andreas

[1] Well it is "guidance": pasting will work, but there might still be
places in the prose where a dash would be typographically correct. Some
of these typographical conventions are langauage specific. All this
familiar to LaTeX users.
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1053310: exim4-base: Various severe CVE reports are outstanding

[Andreas Metzler]

On 2023-10-01 Andreas Metzler  wrote:
> On 2023-10-01 Rainer Dorsch  wrote:
[...]
> > It would help if there would be a statement by the Debian exim
> > maintainer team, by when updates are expected to arrive.

> > This would at least help to judge, if I should migrate my systems to
> > postfix or if I can wait for a bugfix.
> [...]

> Hello Rainer,

> Upstream is coordinating with various Linux distribution on the timing
> of the update. I cannot publish these confidential communications.

Tentative timeline: tomorrow (Monday).

Further details on the bugs' scope and mitigations:
https://www.openwall.com/lists/oss-security/2023/10/01/4

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1053310: exim4-base: Various severe CVE reports are outstanding

[Andreas Metzler]

On 2023-10-01 Rainer Dorsch  wrote:
> Package: exim4-base
> Version: 4.94.2-7
> Severity: critical
> Justification: breaks the whole system

> Dear Maintainer,

> *** Reporter, please consider answering these questions, where appropriate ***

> There are various CVE report with a rating of 9.8/10.

> CVE-2023-42119
> CVE-2023-42118
> CVE-2023-42117
> CVE-2023-42116
> CVE-2023-42115
> CVE-2023-42114

> It would help if there would be a statement by the Debian exim
> maintainer team, by when updates are expected to arrive.

> This would at least help to judge, if I should migrate my systems to
> postfix or if I can wait for a bugfix.
[...]

Hello Rainer,

Upstream is coordinating with various Linux distribution on the timing
of the update. I cannot publish these confidential communications.

cu Andreas

Bug#1052649: libflann-dev: Stray semicolon in pkg-config file

[Andreas Metzler]

Package: libflann-dev
Version: 1.9.2+dfsg-1
Severity: serious

flann.pc looks broken:

Libs: -L${libdir} -L/usr/lib/x86_64-linux-gnu;-llz4 -lflann -lflann_cpp
^^^
cu Andreas

Bug#1052219: unrecognized option '--insert-timestamp=1686475264'

[Andreas Metzler]

On 2023-09-19 Shengjing Zhu  wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler  wrote:
[...]
> > Looking at the changelog entry
> >   * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not make any sense at all, since the
> > --insert-timestamp support is now supposed to be available upstream?
> > Since binutils-mingw-w64-i686 is reported to be 2.41 the support should
> > be available. So is binutils-mingw-w64-i686 actually 2.41 and if yes,
> > why does "applied upstream" not hold?

> Upstream implements it in a different way, it doesn't take argument in
> --insert-timestamp option, it just looks SOURCE_DATE_EPOCH implicitly.
> Ref 
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=6badd1020f5bebd3f60a780b8e41a1b581046087

Thanks for the explanation.

cu Andreas

Bug#1052219: unrecognized option '--insert-timestamp=1686475264'

[Andreas Metzler]

Control: tags 1052219 moreinfo

On 2023-09-19 Shengjing Zhu  wrote:
> On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu  wrote:
> > Package: binutils-mingw-w64-i686
> > Version: 2.41-4+11+nmu1
[...]
>> The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
>> It causes libgcrypt20, gcc-mingw-w64 FTBFS.
>>
>> These packages use options like --insert-timestamp=1686475264,
>> which is not supported in upstream implementation.
>>
>> I find such option is mentioned on
>> https://wiki.debian.org/ReproducibleBuilds/TimestampsInPEBinaries
>> It looks like Debian specific behaviour.

> Asking libgcrypt20 and gcc-mingw-w64 to stop using this option makes more 
> sense.


Looking at the changelog entry
  * Drop specify-timestamp.patch, applied upstream in binutils 2.41
(Closes: #1042734)
changing the rdeps does not make any sense at all, since the
--insert-timestamp support is now supposed to be available upstream?
Since binutils-mingw-w64-i686 is reported to be 2.41 the support should
be available. So is binutils-mingw-w64-i686 actually 2.41 and if yes,
why does "applied upstream" not hold?

Nicholas (as NMUer) - can you explain?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[Andreas Metzler]

On 2023-09-15 "László Böszörményi (GCS)"  wrote:
[...]
>  There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?

> I don't know why this is happening, as if I check the intermediate dot
> file then only the node font settings cause this error. Other uses of
> the Helvetica font are fine. As per source change, you will need this
> patch for enblend-enfuse.
> Please check if the resulting package works as you expected or not and
> report back your findings.
[...]

except for the expect font difference (Times) this seems to work ok. -
Thanks.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[Andreas Metzler]

Hello,

I tried to do a test build of enblend against graphviz 8.1.0 from
experimental. I had no luck, since dot seems to be built without support
for png output:

/usr/bin/m4 --fatal-warnings --prefix-builtins --synclines 
--define='dot_output_type=png' ../../doc/uml-dot.m4 
../../doc/external-mask-workflow.dot | \
/usr/bin/dot  -Tpng -Gbgcolor=transparent -Gresolution=600 | \
/usr/bin/convert png:- -transparent white -resize $(( ((96 * 1000) 
/ 600) / 10 ))% external-mask-workflow.png
Format: "png" not recognized. Use one of: canon cmap cmapx cmapx_np dot 
dot_json eps fig gv imap imap_np ismap json json0 mp pic plain plain-ext pov ps 
ps2 svg svgz tk xdot xdot1.2 xdot1.4 xdot_json
convert: improper image header 
`/dev/shm/magick-u_9y0p39jcrUpQwvjHcDxiLBtxK8jlEu' @ 
error/png.c/ReadPNGImage/4107.
[...]

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[Andreas Metzler]

Control: reassign -1 graphviz 2.42.2-7

On 2023-08-27 Aurelien Jarno  wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)

> Dear maintainer,

> enblend-enfuse fails to build from source. From my build log on amd64:

[...]
> | /usr/bin/dot  -Teps -Gsize=4.75,8.5 -oexternal-mask-workflow.eps
> | failed at node 36[0]
> | dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.
> | /bin/bash: line 2: 2820245 Done/usr/bin/m4 
> --fatal-warnings --prefix-builtins --synclines --define='dot_output_type=eps' 
> ../../doc/uml-dot.m4 ../../doc/external-mask-workflow.dot
> |  2820246 Aborted (core dumped) | /usr/bin/dot -Teps 
> -Gsize=4.75,8.5 -oexternal-mask-workflow.eps
[...]
> A full build log on riscv64 is also available:
> https://buildd.debian.org/status/fetch.php?pkg=enblend-enfuse=riscv64=4.2-10=1693064284=0

Reassigning to the core-dumping package.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1043417: libwraster6: libwraster ABI breakage

[Andreas Metzler]

On 2023-08-10 "Torrance, Douglas"  wrote:
[...]
> I've applied the patch that you submitted upstream [1] to the package.  I
> think this should fix the issue.  See the latest draft in Salsa [2].

> Does this look okay?

Thank you, yes. (As you are no doubt aware) there is a functionally
identally  (but different) patch in upstream GIT, let's go with this
one. (Please tell me if I should make an upload.)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1043417: libwraster6: libwraster ABI breakage

[Andreas Metzler]

Package: libwraster6
Version: 0.96.0-1
Severity: grave
Tags: upstream
Justification: Policy 8.6.2

Hello,

already communicated upstream, lets add a blocker bug. The new release
bumped the symbol version of all symbols from LIBWRASTER6 to
LIBWRASTER7, i.e. we have got total ABI breakage, none of the previously
exported symbols are exported anymore.
-
ametzler@argenau:~$ wmweather+ ; echo $?
wmweather+: /lib/x86_64-linux-gnu/libwraster.so.6: version `LIBWRASTER6' not 
found (required by wmweather+)
1
-

Upstream had introduced a script for automatic symbol versioning,
however given a libtool version string current:revision:age it
constructs the symbol versioning from $current instead of the soname.
libwraster went from 6:0:0 to 7:0:1 (no soname change).

cu Andreas

Bug#1043134: guile-gnutls: FTBFS against gnutls28 3.8.1

[Andreas Metzler]

Package: guile-gnutls
Version: 3.7.12
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

I have already forwarded this upstream
https://gitlab.com/gnutls/guile/-/issues/15

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-04 Ted  wrote:
> The only software which has ever run here is from a bookworm or vscodim
> repo so i will just wait for bookworm to stabilize and hope i can abandon
> the workarounds in the future.

Hello,

You were right all the time. python3-setuptools is the culprit,
installing it breaks the build.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1040316: python3-minimal fails to install

[Andreas Metzler]

On 2023-07-04 Blair Noctis  wrote:
> On Tue, 04 Jul 2023 14:37:49 +0300 Adrian Bunk  wrote:
[...]
> > result = self._execute('import importlib; 
> > print(importlib.util.MAGIC_NUMBER)', version)
> >  
> > ^^
> >   File "/usr/share/python3/debpython/interpreter.py", line 359, in _execute
> > raise Exception('{} failed with status code {}'.format(command, 
> > output['returncode']))
> > Exception: ('python3.11', '-c', 'import importlib; 
> > print(importlib.util.MAGIC_NUMBER)') failed with status code 1
[...]
> `import importlib` doesn't bring in `importlib.util`, need `import 
> importlib.util`.

> IDK if that's the cause though.

Hello,

patching as suggested ...

--- /tmp/interpreter.py 2023-07-04 19:06:11.131647132 +0200
+++ /chroots/sid/usr/share/python3/debpython/interpreter.py 2023-07-04 
19:06:48.915235377 +0200
@@ -230,7 +230,7 @@ class Interpreter:
 version = Version(version or self.version)
 if self.impl == 'cpython' and version << Version('3'):
 return ''
-result = self._execute('import importlib; 
print(importlib.util.MAGIC_NUMBER)', version)
+result = self._execute('import importlib.util; 
print(importlib.util.MAGIC_NUMBER)', version)
 return eval(result)

 def magic_tag(self, version=None):

... seems to work.

cu Andreas


-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-03 Ted  wrote:
> Just to keep updated, I checked if all build deps have updates in
> bookworm-updates and bookworm-security, but didn't find anything. I also
> checked to make sure that the package versions i'm using for all build
> dependencies are equal to the latest in bookworm.

You will need to search for local python stuff (e.g. /usr/local or
in the home directory, not packaged ones.

Please keep this discussion on the bug tracker, do not only mail me
directly.

cu Andreas

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-03 Andreas Metzler  wrote:
[...]
> As I wrote before I /suspect/ because you have some outdated locally
> installed python modules and have configured the system to use them in
> preference to the system installed ones.

To provide some more detail: Your buildlogs lack this exact warning:

gpgme1.0-1.18.0/build/lang/python/setup.py:21: DeprecationWarning: The 
distutils package is deprecated and slated for removal in Python 3.12. Use 
setuptools or check PEP 632 for potential alternatives

This warning was added in python3.10.

I think that is very strong indication that something outdated is
used.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-03 Ted  wrote:
> On Sun, Jul 2, 2023 at 8:08 PM Ted  wrote:
[...]
> > If I want to ensure that my packages build well, I can use a chroot, but
> > this is not actually something that a package should assume. Chroots are a
> > way to mitigate broad sources of brittleness, but we shouldn't be brittle.
> > How do we ensure this source package has no spurious imports from the
> > environment?

> Or more specifically, why does the debian source package occasionally make
> the incorrect decision to build differently and use the deprecated path?

As I wrote before I /suspect/ because you have some outdated locally
installed python modules and have configured the system to use them in
preference to the system installed ones.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-01 Ted  wrote:
> Build still fails under debuild with no funny flags. Here's log.
[...]

Hello,

Looking at the log it looks like your are overriding CFLAGS somewhere
(-g -O2 -ffile-prefix-map=/... is missing).

This warning is missing in your log:
[BUILDPATH]/gpgme1.0-1.18.0/build/lang/python/setup.py:21: DeprecationWarning: 
The distutils package is deprecated and slated for removal in Python 3.12. Use 
setuptools or check PEP 632 for potential alternatives
  from distutils.core import setup, Extension

So I think you are running with an unclean environment which causes the
build to either use locally installed (older) python modules or which
causes the python modules to behave differently.

printenv might be enlightening.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

Control: tags -1 - patch
Control: tags -1 moreinfo

On 2023-06-28 Theodoric Stier  wrote:
> Package: gpgme
> Severity: serious
> Tags: ftbfs patch
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: kerd...@gmail.com

> Dear Maintainer,

> Trying to build bookworm from source under bookworm, this package fails owing 
> to subject matter.
> I run the following before debuild and it works.

> sed -i 
> 's/gpg\*.egg-info/EGG-INFO\/\*/g;s/lib\/python3\*\/site-packages/local\/lib\/python3\*\/dist-packages\/gpg-\*-py3\*.egg/g'
>  debian/python3-gpg.install

> I don't know why the behavior differs from what the .install file expects.
> I'm not sure if this is the right thing to do.

Good morning,

I cannot reproduce in a clean bookworm chroot. Could post a full
buildlog?

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server

[Andreas Metzler]

On 2023-06-14 Andreas Metzler  wrote:
> On 2023-06-14 Andreas Beckmann  wrote:
[...]
> > after building gnutls28/experimental with pbuilder, there are a lot of
> > gnutls-serv and a few openssl s_server processes running, preventing
> > pbuilder to cleanup the chroot.

> This was caused by the changes related to fixing #1031553 (supporting
> either datefudge or faketime.

The reasons for breakage are twofold:

when using a wrapper shell-function instead of an executable like this:

wrapme() {
foo "$@"
}

This kind of code breaks

wrapme server &
PID=$!
...
kill $PID

since PID will contain the process ID of the currently running script
instead of "foo server".

The second one is a similar one. While
datefudge ... server
gives you one process - the server one (datefudge is a shell script
which sets some environment variables and exec-s the a binary.) OTOH
faketime  ... server
starts a faketime process and a forked "server" as child process and
killing faketime does not kill the child process (Reported as
https://github.com/wolfcw/libfaketime/issues/428 ). This also breaks the
idiom mentioned above.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server

[Andreas Metzler]

Control: found -1 3.8.0+git20230413-1

On 2023-06-14 Andreas Beckmann  wrote:
> Source: gnutls28
> Version: 3.8.0+git20230529-1
> Severity: serious

> Hi,

> after building gnutls28/experimental with pbuilder, there are a lot of
> gnutls-serv and a few openssl s_server processes running, preventing
> pbuilder to cleanup the chroot.

Hello,

This was caused by the changes related to fixing #1031553 (supporting
either datefudge or faketime. I think
tests/ocsp-tests/ocsp-tls-connection.sh or
tests/ocsp-tests/ocsp-must-staple-connection.sh triggers this.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

[Andreas Metzler]

Hello,

if you have not got time for an upload I can look into it.

cu Andreas

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

[Andreas Metzler]

On 2023-05-24 Mathieu Malaterre  wrote:
> On Wed, May 24, 2023 at 6:21 PM Andreas Metzler  wrote:
[...]
> > Correct patch attached. Stuff was built but the respective dh_install
> > call was shadowed and therefore content was not shipped in the package.

> [...]
> -override_dh_install-indep:
> - dh_install -p$(pkg_doc) debian/tmp/usr/share/doc
> -
> [...]

> Isn't this going to break the openjpeg-doc package ?

Hello Mathieu,

No, replaced by the second part of the patch

8X---
--- openjpeg2-2.5.0/debian/openjpeg-doc.install 1970-01-01 01:00:00.0 
+0100
+++ openjpeg2-2.5.0/debian/openjpeg-doc.install 2023-05-24 12:45:48.0 
+0200
@@ -0,0 +1 @@
+usr/share/doc
8X---

| ametzler@argenau:/dev/shm/JPI$ debdiff openjpeg-doc_2.5.0-{1,2}_all.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Version: [-2.5.0-1-] {+2.5.0-2+}

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

[Andreas Metzler]

Control: retitle -1 libopenjpip-viewer is basically empty

On 2023-05-23 Mathieu Malaterre  wrote:
> On Tue, May 23, 2023 at 10:46 AM Mathieu Malaterre  wrote:
> >
> > Control: retitle -1 No java compiler found. Won't be able to build java 
> > viewer
> >
> > openjpeg2/java compilation appears to be broken:
[...]

> default-jdk is defined in B-D-I which looks wrong IMHO:

> * 
> https://salsa.debian.org/debian-phototools-team/openjpeg2/-/blob/master/debian/control#L16

> [...]
> Build-Depends-Indep: default-jdk,
> [...]

Why does this look wrong? libopenjpip-viewer is arch-all.

Correct patch attached. Stuff was built but the respective dh_install
call was shadowed and therefore content was not shipped in the package.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru openjpeg2-2.5.0/debian/changelog openjpeg2-2.5.0/debian/changelog
--- openjpeg2-2.5.0/debian/changelog	2022-06-20 16:05:24.0 +0200
+++ openjpeg2-2.5.0/debian/changelog	2023-05-24 12:45:48.0 +0200
@@ -1,3 +1,10 @@
+openjpeg2 (2.5.0-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Fix broken symlink. Closes: #1036584
+
+ -- Andreas Metzler   Wed, 24 May 2023 12:45:48 +0200
+
 openjpeg2 (2.5.0-1) unstable; urgency=medium
 
   * New upstream version 2.5.0
diff -Nru openjpeg2-2.5.0/debian/openjpeg-doc.install openjpeg2-2.5.0/debian/openjpeg-doc.install
--- openjpeg2-2.5.0/debian/openjpeg-doc.install	1970-01-01 01:00:00.0 +0100
+++ openjpeg2-2.5.0/debian/openjpeg-doc.install	2023-05-24 12:45:48.0 +0200
@@ -0,0 +1 @@
+usr/share/doc
diff -Nru openjpeg2-2.5.0/debian/rules openjpeg2-2.5.0/debian/rules
--- openjpeg2-2.5.0/debian/rules	2022-06-20 16:01:30.0 +0200
+++ openjpeg2-2.5.0/debian/rules	2023-05-24 12:45:48.0 +0200
@@ -50,9 +50,6 @@
 pkg_vwr = libopenjpip-viewer
 pkg_dsrv = libopenjpip-dec-server
 
-override_dh_install-indep:
-	dh_install -p$(pkg_doc) debian/tmp/usr/share/doc
-
 override_dh_install-arch:
 	# annoying cmake-fatal-error export stuff:
 	sed -i -e "s/FATAL_ERROR/STATUS/g" debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/openjpeg-2.5/OpenJPEGTargets*.cmake

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

[Andreas Metzler]

On 2023-05-20 Christopher Obbard  wrote:
[...] 
> > I've prepared an NMU for rkdeveloptool (versioned as
> > 1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1.
[...]
> Thank you for your contribution, but it seems like there is some
> parallel work (this morning in fact).

> I am currently in the process of uploading and the fixes for this
> package. Is it possible to skip this delayed version in favour of the
> version I am about to upload ?

Hello Christopher,

if you upload before the NMU is accepted the NMU will simply be
rejected because there is already a higher numbered version of the
package in the archive. I can also simply cancel the NMU or bump the
delay if you want me to. - Just tell me what your preference is.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

[Andreas Metzler]

Control tags -1 - patch - pending

On 2023-05-20 Rene Engelhard  wrote:
> Hi,

> Am 20.05.23 um 11:38 schrieb Andreas Metzler:
> > I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
> > uploaded it to DELAYED/1. Please feel free to tell me if I
> > should delay it longer.

> How is it unclear that noone seriously cares about this package?

> Old upstream version, popcon 4, ignored by the maintainer. The fix is clear,
> I just want to get it AUTORMed. How difficult is it to understand that?

How hard is it to communicate? Why didn't you simply write to the
bugreport that you wanted the pkg to be autormed instead of letting
me waste my time?

I have removed the upload.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#965794: python-ooolib: diff for NMU version 0.0.22-5.1

[Andreas Metzler]

Control: tags -1 patch  pending

Dear maintainer,

I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Kind regards
Andreas
diff -u python-ooolib-0.0.22/debian/changelog python-ooolib-0.0.22/debian/changelog
--- python-ooolib-0.0.22/debian/changelog
+++ python-ooolib-0.0.22/debian/changelog
@@ -1,3 +1,12 @@
+python-ooolib (0.0.22-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh v11 compat level. Closes: #965794
+  * Add missing build-indep and build-arch targets.
+Closes: #998940
+
+ -- Andreas Metzler   Sat, 20 May 2023 11:31:16 +0200
+
 python-ooolib (0.0.22-5) unstable; urgency=medium
 
   * remove obsolete debian/pycompat and Python-Provides:
reverted:
--- python-ooolib-0.0.22/debian/compat
+++ python-ooolib-0.0.22.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u python-ooolib-0.0.22/debian/control python-ooolib-0.0.22/debian/control
--- python-ooolib-0.0.22/debian/control
+++ python-ooolib-0.0.22/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian LibreOffice Team 
 Uploaders: Rene Engelhard , Chris Halls 
-Build-Depends: debhelper (>= 5), python3-all, python3, dh-python
+Build-Depends: debhelper-compat (= 11), python3-all, python3, dh-python
 Standards-Version: 3.7.2
 
 Package: python3-ooolib
diff -u python-ooolib-0.0.22/debian/rules python-ooolib-0.0.22/debian/rules
--- python-ooolib-0.0.22/debian/rules
+++ python-ooolib-0.0.22/debian/rules
@@ -17,6 +17,10 @@
 
 build: build-stamp
 
+build-indep: build-stamp
+
+build-arch: build-stamp
+
 build-stamp: configure-stamp 
 	dh_testdir
 	touch $@


signature.asc
Description: PGP signature

Bug#1035436: rkdeveloptool: diff for NMU version 1.32+git20210408.46bb4c0-2.1

[Andreas Metzler]

Control: tags 1035436 + patch
Control: tags 1035436 + pending

Dear maintainer,

I've prepared an NMU for rkdeveloptool (versioned as
1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1. Please feel
free to tell me if I should delay it longer.

kind regards

Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog
--- rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog	2022-10-31 13:04:40.0 +0100
+++ rkdeveloptool-1.32+git20210408.46bb4c0/debian/changelog	2023-05-20 11:03:08.0 +0200
@@ -1,3 +1,10 @@
+rkdeveloptool (1.32+git20210408.46bb4c0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing depends on adduser. Closes: #1035436
+
+ -- Andreas Metzler   Sat, 20 May 2023 11:03:08 +0200
+
 rkdeveloptool (1.32+git20210408.46bb4c0-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru rkdeveloptool-1.32+git20210408.46bb4c0/debian/control rkdeveloptool-1.32+git20210408.46bb4c0/debian/control
--- rkdeveloptool-1.32+git20210408.46bb4c0/debian/control	2022-10-31 13:03:52.0 +0100
+++ rkdeveloptool-1.32+git20210408.46bb4c0/debian/control	2023-05-20 11:03:01.0 +0200
@@ -14,7 +14,8 @@
 
 Package: rkdeveloptool
 Architecture: any
-Depends: ${shlibs:Depends},
+Depends: adduser,
+ ${shlibs:Depends},
  ${misc:Depends},
 Description: tools for working with Rockchip processors
  This package provides tools to communicate with various Rockchip processors


signature.asc
Description: PGP signature

Bug#1035450: mcpl: diff for NMU version 1.3.2-3.1

[Andreas Metzler]

Control: tags 1035450 + patch
Control: tags 1035450 + pending

Dear maintainer,

I've prepared an NMU for mcpl (versioned as 1.3.2-3.1) and
uploaded it to DELAYED/1.
kind regards

Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru mcpl-1.3.2/debian/changelog mcpl-1.3.2/debian/changelog
--- mcpl-1.3.2/debian/changelog	2022-02-16 20:32:02.0 +0100
+++ mcpl-1.3.2/debian/changelog	2023-05-20 06:57:53.0 +0200
@@ -1,3 +1,11 @@
+mcpl (1.3.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libmcpl-dev: missing Depends on runtime library packages.
+Closes: #1035450
+
+ -- Andreas Metzler   Sat, 20 May 2023 06:57:53 +0200
+
 mcpl (1.3.2-3) unstable; urgency=medium
 
   * Source-only upload for migration to testing.
diff -Nru mcpl-1.3.2/debian/control mcpl-1.3.2/debian/control
--- mcpl-1.3.2/debian/control	2022-02-01 17:32:55.0 +0100
+++ mcpl-1.3.2/debian/control	2023-05-20 06:57:26.0 +0200
@@ -21,7 +21,10 @@
 
 Package: libmcpl-dev
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: libmcpl1 (= ${binary:Version}),
+ libphitsmcpl1 (= ${binary:Version}),
+ libsswmcpl1 (= ${binary:Version}),
+ ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
 Description: Monte Carlo Particle Lists - development files
  This package includes the shared library for reading and writing
  *.mcpl files, a binary format with lists of particle state


signature.asc
Description: PGP signature

Bug#1034915: Going to reschedule NMU

[Andreas Metzler]

Hello,

having read up on the current NMU timing guidance in developers
reference I will reschedule these to 1-day.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#1034951: ktexteditor: diff for NMU version 5.103.0-1.1

[Andreas Metzler]

Control: tags 1034951 + patch
Control: tags 1034951 + pending

Dear maintainer,

I've prepared an NMU for ktexteditor (versioned as 5.103.0-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

kind regards
Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru ktexteditor-5.103.0/debian/changelog ktexteditor-5.103.0/debian/changelog
--- ktexteditor-5.103.0/debian/changelog	2023-02-12 21:44:34.0 +0100
+++ ktexteditor-5.103.0/debian/changelog	2023-05-18 18:20:13.0 +0200
@@ -1,3 +1,11 @@
+ktexteditor (5.103.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Breaks/Replaces of ktexteditor-data against
+libkf5texteditor-dev. Closes: #1034951
+
+ -- Andreas Metzler   Thu, 18 May 2023 18:20:13 +0200
+
 ktexteditor (5.103.0-1) unstable; urgency=medium
 
   [ Aurélien COUDERC ]
diff -Nru ktexteditor-5.103.0/debian/control ktexteditor-5.103.0/debian/control
--- ktexteditor-5.103.0/debian/control	2023-02-11 21:14:01.0 +0100
+++ ktexteditor-5.103.0/debian/control	2023-05-18 18:19:30.0 +0200
@@ -40,8 +40,8 @@
 Package: ktexteditor-data
 Section: kde
 Architecture: all
-Breaks: libkf5texteditor5 (<< 5.74),
-Replaces: libkf5texteditor5 (<< 5.74),
+Breaks: libkf5texteditor5 (<< 5.74), libkf5texteditor-dev (<< 5.90.0-1),
+Replaces: libkf5texteditor5 (<< 5.74), libkf5texteditor-dev (<< 5.90.0-1),
 Depends: ${misc:Depends},
 Multi-Arch: foreign
 Description: provide advanced plain text editing services


signature.asc
Description: PGP signature

Bug#1034921: colord-gtk: diff for NMU version 0.3.0-3.1

[Andreas Metzler]

Control: tags 1034921 + patch
Control: tags 1034921 + pending

Dear maintainer,

I've prepared an NMU for colord-gtk (versioned as 0.3.0-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

kind regards
Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru colord-gtk-0.3.0/debian/changelog colord-gtk-0.3.0/debian/changelog
--- colord-gtk-0.3.0/debian/changelog	2022-03-31 20:12:29.0 +0200
+++ colord-gtk-0.3.0/debian/changelog	2023-05-18 14:17:42.0 +0200
@@ -1,3 +1,10 @@
+colord-gtk (0.3.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix typo "Replacs" in debian/control. Closes: #1034921
+
+ -- Andreas Metzler   Thu, 18 May 2023 14:17:42 +0200
+
 colord-gtk (0.3.0-3) unstable; urgency=medium
 
   * Source-only rebuild
diff -Nru colord-gtk-0.3.0/debian/control colord-gtk-0.3.0/debian/control
--- colord-gtk-0.3.0/debian/control	2022-03-31 20:12:29.0 +0200
+++ colord-gtk-0.3.0/debian/control	2023-05-18 14:17:32.0 +0200
@@ -107,7 +107,7 @@
 Depends: ${shlibs:Depends},
  ${misc:Depends},
 Breaks: libcolord-gtk-dev (<< 0.3.0-2~)
-Replacs: libcolord-gtk-dev (<< 0.3.0-2~)
+Replaces: libcolord-gtk-dev (<< 0.3.0-2~)
 Suggests: libcolord-gtk4-dev | libcolord-gtk-dev
 Description: GTK convenience library for interacting with colord - headers
  colord is a system service that makes it easy to manage, install and generate


signature.asc
Description: PGP signature

Bug#1034915: vdr-plugin-xineliboutput: diff for NMU version 2.2.0+git20211212-2.2

[Andreas Metzler]

Control: tags 1034915 + patch
Control: tags 1034915 + pending

Dear maintainer,

I've prepared an NMU for vdr-plugin-xineliboutput (versioned as
2.2.0+git20211212-2.2) and uploaded it to DELAYED/10. Please feel free
to tell me if I should delay it longer.

Kind regards
Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog	2022-01-25 19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog	2023-05-18 13:40:36.0 +0200
@@ -1,3 +1,11 @@
+vdr-plugin-xineliboutput (2.2.0+git20211212-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Breaks/Replaces for correction of xineliboutput-fbfe desktop
+icon. Closes: #1034915
+
+ -- Andreas Metzler   Thu, 18 May 2023 13:40:36 +0200
+
 vdr-plugin-xineliboutput (2.2.0+git20211212-2.1) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control	2022-01-25 19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control	2023-05-18 13:39:22.0 +0200
@@ -54,6 +54,8 @@
 Package: xineliboutput-fbfe
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libxine2-xvdr (= ${binary:Version}), libxine2-console
+Breaks: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
+Replaces: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
 Description: Remote Framebuffer frontend for vdr-plugin-xineliboutput
  This frambuffer remote frontend plays back streams provided by
  vdr-plugin-xineliboutput.


signature.asc
Description: PGP signature

Bug#1034931: flex: diff for NMU version 2.6.4-8.2

[Andreas Metzler]

Control: tags 1034931 + patch
Control: tags 1034931 + pending

Dear maintainer,

I've prepared an NMU for flex (versioned as 2.6.4-8.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

kind regards

Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -u flex-2.6.4/debian/changelog flex-2.6.4/debian/changelog
--- flex-2.6.4/debian/changelog
+++ flex-2.6.4/debian/changelog
@@ -1,3 +1,14 @@
+flex (2.6.4-8.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix package-relationships with flex-old:
++ Add flex Conflicts/Replaces flex-old
++ Change versioned libfl2-dev Replaces/Breaks against flex-old (<=
+  2.5.4a-10) to unversioned Conflicts/Replaces flex-old.
+Closes: #1034931
+
+ -- Andreas Metzler   Thu, 18 May 2023 11:33:49 +0200
+
 flex (2.6.4-8.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u flex-2.6.4/debian/control flex-2.6.4/debian/control
--- flex-2.6.4/debian/control
+++ flex-2.6.4/debian/control
@@ -16,6 +16,8 @@
 Architecture: any
 Pre-Depends: debconf | debconf-2.0
 Depends: ${shlibs:Depends}, m4, ${misc:Depends}
+Conflicts: flex-old
+Replaces: flex-old
 Recommends: gcc | c-compiler, libfl-dev
 Suggests: bison, build-essential, flex-doc
 Multi-Arch: foreign
@@ -70,8 +72,9 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, flex (= ${binary:Version}), libfl2 (= ${binary:Version})
-Replaces: flex (<< 2.5.39), flex-old (<= 2.5.4a-10)
-Breaks: flex (<< 2.5.39), flex-old (<= 2.5.4a-10)
+Replaces: flex (<< 2.5.39), flex-old
+Breaks: flex (<< 2.5.39)
+Conflicts: flex-old
 Description: static library for flex (a fast lexical analyzer generator)
  Flex is a tool for generating scanners: programs which recognized lexical
  patterns in text. It reads the given input files for a description of a


signature.asc
Description: PGP signature

Bug#1034931: libfl-dev: missing Breaks+Replaces for flex-old when upgrading from bullseye

[Andreas Metzler]

On 2023-04-27 Helmut Grohne  wrote:
> Package: libfl-dev
> Version: 2.6.4-8.1
> Severity: serious
> Justification: dpkg unpack error

> Attempting to unpack libfl-dev/2.6.4-8.1 from Debian bookworm
> on a minimal Debian bullseye with flex-old/2.5.4a-10.1
> installed, causes an unpack error from dpkg due to
> /usr/include/FlexLexer.h being contained in both packages.
[...]
> Please ensure that libfl-dev has sufficient Breaks and Replaces declarations.

Hello,

we currently have:

Package: libfl-dev
Replaces: flex (<< 2.5.39), flex-old (<= 2.5.4a-10)
Breaks: flex (<< 2.5.39), flex-old (<= 2.5.4a-10)

However afaict there are no plans for splitting flex-old into flex-old
and libfl-old-dev so this file conflict is permanent, i.e. libfl-dev should
use unversioned Conflicts instead of versioned Breaks.

On sidenote I think flex should Conflict with flex-old like flex-old
does.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

[Andreas Metzler]

On 2023-05-07 Andreas Metzler  wrote:
[...]
> The only proper fix would be to use versioned symbols for libpoppler
> (and libpoppler-glib while we are at it). This should not be rocket
> science, just tie it to the soname.

> But that needs to happen upstream.

Something like attached patch.
cu Andreas
Description: Use symbol versioning for libpoppler
 .
 This needs to be applied upstream when the soname is bumped.
Author: Andreas Metzler 
Origin: vendor
Bug-Debian: https://bugs.debian.org/969907
Forwarded: no
Last-Update: 2023-05-14

--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -572,16 +572,31 @@ ADD_GPERF_FILE(TimesBoldWidths)
 ADD_GPERF_FILE(TimesBoldItalicWidths)
 ADD_GPERF_FILE(TimesItalicWidths)
 ADD_GPERF_FILE(TimesRomanWidths)
 ADD_GPERF_FILE(ZapfDingbatsWidths)
 
+set(POPPLER_SOVERSION_NUMBER "126")
+
+set(LINKER_SCRIPT "${CMAKE_BINARY_DIR}/libpoppler.map")
+configure_file(
+"${CMAKE_SOURCE_DIR}/poppler/libpoppler.map.in"
+${LINKER_SCRIPT})
+
 if(MSVC)
 add_definitions(-D_CRT_SECURE_NO_WARNINGS)
 endif()
-add_library(poppler ${poppler_SRCS})
+add_library(poppler ${poppler_SRCS} ${LINKER_SCRIPT})
 generate_export_header(poppler BASE_NAME poppler-private EXPORT_FILE_NAME "${CMAKE_CURRENT_BINARY_DIR}/poppler_private_export.h")
-set_target_properties(poppler PROPERTIES VERSION 126.0.0 SOVERSION 126)
+set_target_properties(poppler PROPERTIES
+	VERSION ${POPPLER_SOVERSION_NUMBER}.0.0
+	SOVERSION ${POPPLER_SOVERSION_NUMBER})
+
+if(UNIX AND (NOT APPLE))
+	set_target_properties(poppler PROPERTIES
+		LINK_OPTIONS LINKER:--version-script=${LINKER_SCRIPT})
+endif()
+
 if(MINGW AND BUILD_SHARED_LIBS)
 get_target_property(POPPLER_SOVERSION poppler SOVERSION)
 set_target_properties(poppler PROPERTIES SUFFIX "-${POPPLER_SOVERSION}${CMAKE_SHARED_LIBRARY_SUFFIX}")
 endif()
 target_link_libraries(poppler LINK_PRIVATE ${poppler_LIBS})
--- /dev/null
+++ b/poppler/libpoppler.map.in
@@ -0,0 +1,4 @@
+POPPLER_@POPPLER_SOVERSION_NUMBER@ {
+  global:
+*;
+};

Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

[Andreas Metzler]

On 2021-02-18 Simon McVittie  wrote:
[...]
> So elpa-pdf-tools-server is linked to libpoppler-glib, and because the
> (parts of the) libpoppler-glib API that it uses has not changed for a
> while, it is happy with an old version; but then during a partial
> upgrade, it can get this

> elpa-pdf-tools-server
> \- old libpoppler-glib
> |   \- libpoppler95
> \- libpoppler102

> and the two copies of libpoppler fight?

> That seems entirely plausible, and I don't immediately see a way to
> fix it without adding Breaks (which would force a lockstep upgrade,
> somewhat defeating the purpose of SONAMEs).
[...]

Hello,

The only proper fix would be to use versioned symbols for libpoppler
(and libpoppler-glib while we are at it). This should not be rocket
science, just tie it to the soname.

But that needs to happen upstream.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1034895: pcp: diff for NMU version 6.0.3-1.1

[Andreas Metzler]

Control: tags -1 pending

Dear maintainer,

I've prepared an NMU for pcp (versioned as 6.0.3-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

kind regards

Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru pcp-6.0.3/debian/changelog pcp-6.0.3/debian/changelog
--- pcp-6.0.3/debian/changelog	2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/changelog	2023-05-07 11:36:37.0 +0200
@@ -1,3 +1,18 @@
+pcp (6.0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing replaces on pcp (<< 5.3.0):
++ pcp-export-pcp2elasticsearch Closes: #1034998
++ pcp-export-pcp2json Closes: #1034983
++ pcp-export-pcp2spark Closes: #1034932
++ pcp-export-pcp2xml Closes: #1034922
++ pcp-export-pcp2zabbix Closes: #1034973
++ pcp-doc Closes: #1034966
++ pcp-zeroconf Closes: #1034895
++ pcp-export-pcp2xlsx (unfiled)
+
+ -- Andreas Metzler   Sun, 07 May 2023 11:36:37 +0200
+
 pcp (6.0.3-1) unstable; urgency=low
 
   * New release (full details in CHANGELOG).
diff -Nru pcp-6.0.3/debian/control pcp-6.0.3/debian/control
--- pcp-6.0.3/debian/control	2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/control	2023-05-07 07:37:15.0 +0200
@@ -385,6 +385,7 @@
 Package: pcp-export-pcp2elasticsearch
 Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to Elasticsearch
  Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -409,6 +410,7 @@
 Package: pcp-export-pcp2json
 Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to JSON
  Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -417,6 +419,7 @@
 Package: pcp-export-pcp2spark
 Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to Apache Spark
  Performance Co-Pilot (PCP) front-end tools for exporting metric values
@@ -425,6 +428,7 @@
 Package: pcp-export-pcp2xml
 Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to XML
  Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -433,6 +437,7 @@
 Package: pcp-export-pcp2zabbix
 Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to Zabbix
  Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -449,7 +454,7 @@
 Section: doc
 Depends: ${misc:Depends}
 Breaks: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
-Replaces: pcp-gui (<< 1.5.13)
+Replaces: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
 Suggests: pcp, pcp-gui
 Architecture: all
 Description: Documentation and tutorial for the Performance Co-Pilot
@@ -462,6 +467,7 @@
 Package: pcp-zeroconf
 Depends: ${misc:Depends}, ${shlibs:Depends}, pcp (= ${binary:Version})
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Performance Co-Pilot (PCP) Zeroconf Package
  Contains configuration tweaks and files that increase metrics gathering
@@ -511,6 +517,7 @@
 Package: pcp-export-pcp2xlsx
 Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
 Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
 Architecture: any
 Description: Tool for exporting data from PCP to Excel spreadsheets
  Performance Co-Pilot (PCP) front-end tool for exporting data from PCP


signature.asc
Description: PGP signature

Bug#1034959: libwmf: diff for NMU version 0.2.12-5.1

[Andreas Metzler]

Control: tags 1034959 + patch
Control: tags 1034959 + pending

Dear maintainer,

I've prepared an NMU for libwmf (versioned as 0.2.12-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Kind regards

Andreas
diff -Nru libwmf-0.2.12/debian/changelog libwmf-0.2.12/debian/changelog
--- libwmf-0.2.12/debian/changelog	2022-01-25 09:16:35.0 +0100
+++ libwmf-0.2.12/debian/changelog	2023-05-06 18:19:26.0 +0200
@@ -1,3 +1,11 @@
+libwmf (0.2.12-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Breaks/Replaces on libwmf0.2-7-gtk to libwmf-0.2-7-gtk.
+Closes: #1034959
+
+ -- Andreas Metzler   Sat, 06 May 2023 18:19:26 +0200
+
 libwmf (0.2.12-5) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru libwmf-0.2.12/debian/control libwmf-0.2.12/debian/control
--- libwmf-0.2.12/debian/control	2022-01-25 09:16:35.0 +0100
+++ libwmf-0.2.12/debian/control	2023-05-06 18:17:54.0 +0200
@@ -53,8 +53,8 @@
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${shlibs:Depends}, libwmf-0.2-7 (= ${binary:Version})
-Breaks: libwmf0.2-7 (<< 0.2.8.4-12)
-Replaces: libwmf0.2-7 (<< 0.2.8.4-12)
+Breaks: libwmf0.2-7 (<< 0.2.8.4-12), libwmf0.2-7-gtk (<< 0.2.12-1)
+Replaces: libwmf0.2-7 (<< 0.2.8.4-12), libwmf0.2-7-gtk (<< 0.2.12-1)
 Description: Windows metafile conversion GTK pixbuf plugin
  Windows metafile (WMF) is a picture format used by many Windows
  programs, e.g. Microsoft Word.  libwmf is a library for interpreting


signature.asc
Description: PGP signature

Bug#1034986: marked as pending in xmorph

[Andreas Metzler]

Control: tag -1 pending

Hello,

Bug #1034986 in xmorph 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/debian-phototools-team/xmorph/-/commit/e0fb1effa938c273dcbd593564f5d7d0afc1892b


add missing Breaks+Replaces

Closes: #1034986


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034986