Bug#1024020: net-snmp: CVE-2022-44792 CVE-2022-44793

[Salvatore Bonaccorso]

Hi,

On Sun, Nov 13, 2022 at 08:35:33PM +0100, Moritz Mühlenhoff wrote:
> Source: net-snmp
> X-Debbugs-CC: t...@security.debian.org
> Severity: important
> Tags: security
> 
> Hi,
> 
> The following vulnerabilities were published for net-snmp.
> 
> CVE-2022-44792[0]:
> | handle_ipDefaultTTL in agent/mibgroup/ip-mib/ip_scalars.c in Net-SNMP
> | 5.8 through 5.9.3 has a NULL Pointer Exception bug that can be used by
> | a remote attacker (who has write access) to cause the instance to
> | crash via a crafted UDP packet, resulting in Denial of Service.
> 
> https://github.com/net-snmp/net-snmp/issues/474
> https://gist.github.com/menglong2234/b7bc13ae1a144f47cc3c95a7ea062428
> 
> CVE-2022-44793[1]:
> | handle_ipv6IpForwarding in agent/mibgroup/ip-mib/ip_scalars.c in Net-
> | SNMP 5.4.3 through 5.9.3 has a NULL Pointer Exception bug that can be
> | used by a remote attacker to cause the instance to crash via a crafted
> | UDP packet, resulting in Denial of Service.
> 
> https://github.com/net-snmp/net-snmp/issues/475
> https://gist.github.com/menglong2234/d07a65b5028145c9f4e1d1db8c4c202f
> 
> If you fix the vulnerabilities please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2022-44792
> https://www.cve.org/CVERecord?id=CVE-2022-44792
> [1] https://security-tracker.debian.org/tracker/CVE-2022-44793
> https://www.cve.org/CVERecord?id=CVE-2022-44793
> 
> Please adjust the affected versions in the BTS as needed.

Upstream has addressed both issues with
https://github.com/net-snmp/net-snmp/commit/be804106fd0771a7d05236cff36e199af077af57
.

Regards,
Salvatore

Bug#919058: its-tool: crashes when freeing bad xmlDocs

[Paul Gevers]

Hi Lars,

On Thu, 25 Apr 2019 02:03:01 +0200 Lars Skovlund  
wrote:

So far, there is no response on either the RedHat bug or on the
respective GitHub issues. There is a new itstool version available,
but it only includes the fixes that we've had available as long as this
bug has been open.


itstool in Debian is newer now that at the time of this discussion. From 
reading, it's not clear if you expect this bug to be closed now. Could 
you please check if this issue still exists in unstable and bookworm?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027309: jetty9: dpkg-source died

[sun min]

Package: jetty9
Version: 9.4.49-1.1
Severity: normal
Tags: ftbfs

Dear Maintainer,

I cloned the jetty9 repo from https://salsa.debian.org/java-team/jetty9.git.

I did not change anything and tried to build the package from source,it 
complains:

https://salsa.debian.org/java-team/jetty9.gitdpkg-source: warning: extracting 
unsigned source package (jetty9_9.4.50-1.dsc)
dpkg-source: info: extracting jetty9 in /<>
dpkg-source: info: unpacking jetty9_9.4.50.orig.tar.bz2
dpkg-source: info: unpacking jetty9_9.4.50-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 01-maven-bundle-plugin-version.patch
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B 
.pc/01-maven-bundle-plugin-version.patch/ --reject-file=- < 
/<>/debian/patches/01-maven-bundle-plugin-version.patch subprocess 
returned exit status 1
patching file pom.xml
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch '01-maven-bundle-plugin-version.patch' is correctly 
applied by quilt, use 'quilt refresh' to update it
dpkg-source: info: if the file is present in the unpacked source, make sure it 
is also present in the orig tarball
E: FAILED [dpkg-source died]

+--+
| Cleanup  |
+--+

Purging /<>
Not cleaning session: cloned chroot in use
E: FAILED [dpkg-source died]

+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: full
Build-Space: 114756
Build-Time: 0
Distribution: unstable
Fail-Stage: unpack
Host Architecture: amd64
Install-Time: 1769
Job: /home/sunmin/src/java-jetty9/salsa-fork/jetty9_9.4.50-1.dsc
Machine Architecture: amd64
Package: jetty9
Package-Time: 0
Source-Version: 9.4.50-1
Space: 114756
Status: given-back
Version: 9.4.50-1

Finished at 2022-12-30T02:22:39Z
Build needed 00:00:00, 114756k disk space
E: FAILED [dpkg-source died]

I'm sure the patch files do exist and this error is strange, please help 
resolve it.

Thanks!

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: riscv64

Kernel: Linux 5.10.102.1-microsoft-standard-WSL2+ (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages jetty9 depends on:
ii  adduser   3.128
ii  apache2-utils 2.4.54-4
ii  default-jre-headless [java8-runtime-headless] 2:1.11-72
ii  libecj-java   3.16.0-1
ii  libjetty9-extra-java  9.4.49-1.1
ii  libjetty9-java9.4.49-1.1
ii  lsb-base  11.2
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.17+8-2

Versions of packages jetty9 recommends:
ii  authbind  2.1.3

jetty9 suggests no packages.

-- no debconf information

Bug#1027308: chezdav: should probably depend on or recommend avahi-daemon

[Andres Salomon]

Package: chezdav
Version: 2.5-1
Severity: normal

I installed chezdav on a bullseye server, and here's what got installed:

dilinger@hm90:~$ sudo apt-get install chezdav
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  dbus dbus-user-session dconf-gsettings-backend dconf-service glib-networking 
glib-networking-common
  glib-networking-services gsettings-desktop-schemas libavahi-client3 
libavahi-common-data
  libavahi-common3 libavahi-glib1 libavahi-gobject0 libdconf1 libpam-systemd 
libphodav-2.0-0
  libphodav-2.0-common libproxy1v5 libsoup2.4-1
The following NEW packages will be installed:
  chezdav dbus dbus-user-session dconf-gsettings-backend dconf-service 
glib-networking
  glib-networking-common glib-networking-services gsettings-desktop-schemas 
libavahi-client3
  libavahi-common-data libavahi-common3 libavahi-glib1 libavahi-gobject0 
libdconf1 libpam-systemd
  libphodav-2.0-0 libphodav-2.0-common libproxy1v5 libsoup2.4-1
0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
[...]

Note that avahi-daemon was not already installed on the server. When I
attemped to run it:


dilinger@hm90:~$ chezdav -P /srv/shared/
phodav: mDNS failed: Failed to create avahi client: Daemon not running


After installing avahi-daemon, the command worked successfully. It should
probably either depend upon or recommend avahi-daemon.



-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable'), (100, 'bullseye-fasttrack')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chezdav depends on:
pn  libavahi-gobject0  
ii  libc6  2.31-13+deb11u5
ii  libglib2.0-0   2.66.8-1
pn  libphodav-2.0-0
ii  libsoup2.4-1   2.72.0-2

chezdav recommends no packages.

chezdav suggests no packages.

Bug#1026933: Transition Qt 6.4.2

[Patrick Franz]

Hi,

Qt 6.4.2~rc1 has now been built successfully on every architecture 
except s390x where the builds have been queued. However, we don't see a 
reason why 6.4.2 couldn't be built on s390x.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1027307: spamd: /etc/default/spamd is declared as /etc/default/spamassassin

[Vincent Lefevre]

Package: spamd
Version: 4.0.0-1
Severity: minor

The first line of /etc/default/spamd is

# /etc/default/spamassassin

instead of

# /etc/default/spamd

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages spamd depends on:
ii  init-system-helpers  1.64
ii  rsyslog [system-log-daemon]  8.2212.0-1
ii  spamassassin 4.0.0-1
ii  systemd  252.4-1

spamd recommends no packages.

spamd suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS

[Konomi]

I just did another round of updates and rebooted and could not
reproduce the bug so I leave it to more experienced users to determine
what should be done.

Bug#1027306: linux-kbuild-6.0: missing `resolve_btfids` and some scripts

[ms23a28926]

Package: linux-kbuild-6.0
Version: 6.0.12-1~bpo11+1
Severity: important
Tags: patch

Dear Maintainer,

I tried to build my out-of-tree kernel module and noticed a message:
`Skipping BTF generation for PATH_TO_KO due to unavailability of vmlinux`.
After copying `/sys/kernel/btf/vmlinux` to corresponding position and with
`dwarves` installed, building the kernel module throws a error: 
`/bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found`.

Besides I find that some useful scripts are not included in `linux-kbuild`
package such as `clang-tools/gen_compile_commands.py`, and I had to copy
it from kernel source tree.

I patched build scripts to contain those components locally with
following patches.

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-kbuild-6.0 depends on:
ii  libc6  2.31-13+deb11u5
ii  libelf10.183-1
ii  libssl1.1  1.1.1n-0+deb11u3

linux-kbuild-6.0 recommends no packages.

linux-kbuild-6.0 suggests no packages.

-- no debconf information
>From 1b9e5fa40cc29bd9a8af9cd3355e65d88cd19a8e Mon Sep 17 00:00:00 2001
From: ur4t <46435411+u...@users.noreply.github.com>
Date: Thu, 29 Dec 2022 19:10:37 +0800
Subject: [PATCH 1/2] linux-kbuild: Add tools/bpf/resolve_btfids/resolve_btfids

This is a new dependency of OOT module builds with BTF enabled.
---
 debian/rules.d/tools/bpf/resolve_btfids/Makefile | 7 +++
 debian/rules.real| 2 ++
 2 files changed, 9 insertions(+)
 create mode 100644 debian/rules.d/tools/bpf/resolve_btfids/Makefile

diff --git a/debian/rules.d/tools/bpf/resolve_btfids/Makefile 
b/debian/rules.d/tools/bpf/resolve_btfids/Makefile
new file mode 100644
index 00..8f5e4e0cb5
--- /dev/null
+++ b/debian/rules.d/tools/bpf/resolve_btfids/Makefile
@@ -0,0 +1,7 @@
+include $(top_rulesdir)/Makefile.inc
+
+all:
+   $(MAKE) -C $(top_srcdir)/tools/bpf/resolve_btfids O=$(CURDIR)
+
+install:
+   install -D -m755 resolve_btfids $(DESTDIR)/$(installdir)/resolve_btfids
diff --git a/debian/rules.real b/debian/rules.real
index 9bb0c617bd..98e8dd7999 100644
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -560,6 +560,7 @@ build_kbuild: $(STAMPS_DIR)/build-tools-headers
$(call make-tools,certs)
$(call make-tools,scripts)
$(call make-tools,tools/objtool)
+   $(call make-tools,tools/bpf/resolve_btfids)
 
 binary_kbuild: PREFIX_DIR = /usr/lib/$(PACKAGE_NAME)
 binary_kbuild: build_kbuild
@@ -569,6 +570,7 @@ binary_kbuild: build_kbuild
$(call make-tools,certs) install prefix=$(PREFIX_DIR)
$(call make-tools,scripts) install prefix=$(PREFIX_DIR)
$(call make-tools,tools/objtool) install prefix=$(PREFIX_DIR)
+   $(call make-tools,tools/bpf/resolve_btfids) install DESTDIR=$(DIR) 
prefix=$(PREFIX_DIR)
dh_link $(PREFIX_DIR) /usr/src/$(PACKAGE_NAME)
dh_installchangelogs
 ifeq (,$(filter nodoc,$(DEB_BUILD_PROFILES)))
-- 
2.30.2

>From fc0c873389031d1e2e068658d5464e7d70b6f142 Mon Sep 17 00:00:00 2001
From: ur4t <46435411+u...@users.noreply.github.com>
Date: Thu, 29 Dec 2022 19:19:08 +0800
Subject: [PATCH 2/2] linux-kbuild: Add missing upstream scripts

---
 debian/rules.d/scripts/Makefile | 47 +
 debian/rules.d/scripts/clang-tools/Makefile |  4 ++
 2 files changed, 34 insertions(+), 17 deletions(-)
 create mode 100644 debian/rules.d/scripts/clang-tools/Makefile

diff --git a/debian/rules.d/scripts/Makefile b/debian/rules.d/scripts/Makefile
index bbfe9c0d10..2e803d1c9f 100644
--- a/debian/rules.d/scripts/Makefile
+++ b/debian/rules.d/scripts/Makefile
@@ -7,37 +7,50 @@ PROGS = \
 
 DATA = \
Kbuild.include \
-   Makefile.* \
+   Makefile* \
mkversion \
module-common.lds \
subarch.include
 
-SCRIPTS =  \
-   checkincludes.pl \
+SCRIPTS = \
+   *.pl \
+   *.py \
+   *.sh \
+   Lindent \
+   bloat-o-meter \
check-local-export \
-   checkstack.pl \
-   checkversion.pl \
-   depmod.sh \
-   gcc-*.sh \
-   gen_initramfs_list.sh \
-   headers_install.sh \
+   check-sysctl-docs \
+   cleanfile \
+   cleanpatch \
+   coccicheck \
+   config \
+   decodecode \
+   diffconfig \
+   documentation-file-ref-check \
+   extract-ikconfig \
+   extract-vmlinux \
+   faddr2line \
+   get_dvb_firmware \
+   gfp-translate \
+   jobserver-exec \
kernel-doc \
-   ld-version.sh \
-   Lindent \
makelst \
+   mkcompile_h \
mksysmap \
-   mkuboot.sh \
-   modules-check.sh \
-  

Bug#1027305: python3-pyglossary: crashes with ModuleNotFoundError

[Raul Benencia]

Package: python3-pyglossary
Version: 3.2.1-1.1
Severity: grave
Justification: renders package unusable

Hi,

pyglossary is crashing with a simple invocation:

$ pyglossary

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/pyglossary/plugins/babylon_bgl/bgl_reader.py", 
line 30, in 
GzipFile = __import__(
ModuleNotFoundError: No module named 'pyglossary.plugin_lib.py310'
If things didn't work well with BGL files, install Python 3.5 to 3.7 and try 
again
Traceback (most recent call last):
  File "/usr/share/pyglossary/pyglossary.pyw", line 215, in 
log.setVerbosity(args.verbosity)
AttributeError: 'RootLogger' object has no attribute 'setVerbosity'

- exit 1

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pyglossary depends on:
ii  python3  3.10.6-3+b1

Versions of packages python3-pyglossary recommends:
ii  gir1.2-gtk-3.03.24.35-3
ii  python3-gi3.42.2-3
ii  python3-gi-cairo  3.42.2-3
ii  python3-html5lib  1.1-3
ii  python3-icu   2.10.2-1+b2
ii  python3-jinja23.0.3-2
ii  python3-lxml  4.9.1-1+b2
ii  python3-lzo   1.14-1+b2

python3-pyglossary suggests no packages.

Regards,
--
Raul Benencia

Bug#1027304: linux-kbuild-6.0: missing `resolve_btfids` and some scripts

[ms23a28926]

Package: linux-kbuild-6.0
Version: 6.0.12-1~bpo11+1
Severity: important
Tags: patch
X-Debbugs-Cc: u...@protonmail.com

Dear Maintainer,

I tried to build my out-of-tree kernel module and noticed a message:
`Skipping BTF generation for PATH_TO_KO due to unavailability of vmlinux`.
After copying `/sys/kernel/btf/vmlinux` to corresponding position and with
`dwarves` installed, building the kernel module throws a error: 
`/bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found`.

Besides I find that some useful scripts are not included in `linux-kbuild`
package such as `clang-tools/gen_compile_commands.py`, and I had to copy
it from kernel source tree.

I patched build scripts to contain those components locally with
following patches.

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-kbuild-6.0 depends on:
ii  libc6  2.31-13+deb11u5
ii  libelf10.183-1
ii  libssl1.1  1.1.1n-0+deb11u3

linux-kbuild-6.0 recommends no packages.

linux-kbuild-6.0 suggests no packages.

-- no debconf information

Bug#1027303: gnuplot-doc: The Info manual contains a spurious Texinfo comment "@c <3 [...]"

[Vincent Lefevre]

Package: gnuplot-doc
Version: 5.4.4+dfsg1-2
Severity: minor
Tags: upstream patch
Forwarded: https://sourceforge.net/p/gnuplot/bugs/2576/

The generated Info manual (gnuplot.info) contains a spurious Texinfo
comment "@c <3 - all terminal stuff is pulled from the .trm files" in
Section 4.1 (complete list of terminals).

What happens is that the docs/doc2texi.el converter transforms the
line starting with "<3" into a Texinfo comment by inserting "@c "
at the beginning of the line (function d2t-get-terminals) with the
intent that this line will not appear in the Info manual (as being
a Texinfo comment). However, the input has not been converted to
the Texinfo format yet, so that function d2t-braces-atsigns
(consisting in the first step of the conversion to Texinfo), which
is called later, assumes that "@c" is real text and adds a "@" in
front of it (to escape the "@" since it is regarded as real text).
As a consequence, one gets a line

  @@c <3 -- all terminal stuff is pulled from the .trm files

in the generated Texinfo file gnuplot.texi, and this line will be
rendered as

  @c <3 -- all terminal stuff is pulled from the .trm files

in the Info manual.

I'm attaching a patch that makes doc2texi.el remove this <3 line
instead of attempting to comment it out.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: Remove spurious Texinfo comment from gnuplot.info.
  The docs/doc2texi.el converter transforms the line starting
  with "<3" into a Texinfo comment by inserting "@c " at the
  beginning of the line (function d2t-get-terminals). However,
  the input has not been converted to the Texinfo format yet,
  so that function d2t-braces-atsigns, which is called later,
  assumes that "@c" is real text and adds a @ in front of it.
  As a consequence, one gets a line
@@c <3 -- all terminal stuff is pulled from the .trm files
  in the generated Texinfo file gnuplot.texi, and this line
  will be rendered as
@c <3 -- all terminal stuff is pulled from the .trm files
  in the Info manual.
  This patch makes doc2texi.el remove the "<3" line instead of
  attempting to comment it out.
Author: Vincent Lefevre 
Bug: https://sourceforge.net/p/gnuplot/bugs/2576/
Last-Update: 2022-12-30

Index: gnuplot-5.4.4+dfsg1/docs/doc2texi.el
===
--- gnuplot-5.4.4+dfsg1.orig/docs/doc2texi.el
+++ gnuplot-5.4.4+dfsg1/docs/doc2texi.el
@@ -482,8 +482,8 @@ the end of `d2t-get-terminals'.")
 (save-excursion
   (when (re-search-forward "^<3" (point-max) t)
 	(beginning-of-line)
-	(insert "@c ")
-	(forward-line 1)
+	(let ((eol (save-excursion (end-of-line) (point-marker
+	  (delete-region (point-marker) eol))
 	(dolist (elem list)
   (and d2t-verbose (message "%s ..." elem))
   (setq file (concat d2t-terminal-directory elem ".trm"))

Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS

[Konomi]

> I wonder if Konomi can reproduce this?

I haven't been able to reproduce it so far, but I haven't rebooted my
computer yet. I still have the video of the error though so it's
definitely an issue.

> Is this possible to reassign this report to console-setup?

I think this would be a good idea to investigate further, who knows if
this bug will cause actual problems later.

Bug#1027302: [Bug report] Dependencies issue for package lxd

[Mcgiwer]

Package: lxd
OS version: bullseye

I want report dependencies issues for the lxd package that prevent lxd from 
becoming installed.

The libraries libxtables12 and libip4tc2 are required to be exact in version 
1.8.7-1 and if the installed ones are newer then that, lxd installation is 
beeing aborted.


Proposed fix:



In the dependencies, replace all "= version" with ">= version"



With regards,
Mcgiwer

signature.asc
Description: OpenPGP digital signature

Bug#1026254: Transition KDE PIM 22.12

[Patrick Franz]

Control: tags -1 - moreinfo

Hi,

On Sun, 18 Dec 2022 13:01:08 +0100 Sebastian Ramacher 
> Please remove the moreinfo tag once the transition is staged in
> experimental.

KDE PIM was uploaded to experimental a week ago and has been built 
successfully on all architectures except s390x where some packages are 
still queued. However, I don't a see a reason why the builds should 
fail.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1027301: desktop-base: Positioning of the "Debian 12" logo on GRUB2 splashscreen makes GRUB2 text hard to read

[Jason Lee Quinn]

Package: desktop-base
Version: 12.0.2
Severity: important
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

While the GRUB2 menu is being displayed, there's a "Debian 12" logo
on the splashscreen in the lower lefthand corner. GRUB2 however
displays text there (including the countdown timer message) and
it is very hard to read because of the logo. This may depend
on the user's screen resolution. I'm using 1440p and the
the positioning conflict is maximally bad there.

The logo would be much better positioned if it were on the
lower LEFT-hand side.

Cheers,
Jason

PS I used yesterday's daily Bookworm net installer so the
issue is as current as it could be.

PPS I noticed below in the auto generated message from
reportbug that desktop-base is suggesting xfce 4.16.
That should also be changed because we recently updated
testing to 4.18.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages desktop-base depends on:
ii  fonts-quicksand  0.2016-2.1
ii  librsvg2-common  2.54.5+dfsg-1

Versions of packages desktop-base recommends:
ii  plymouth-label  22.02.122-2

Versions of packages desktop-base suggests:
ii  xfce4  4.16

-- no debconf information

Bug#1005899: mplayer: should not release with bookworm

[Sebastian Ramacher]

On 2022-12-30 01:48:56 +0100, Lorenzo wrote:
> Hi Sebastian,
> 
> Could you please clarify if this package should be maintained inside the
> Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer?

Whatever the new maintainer prefers. The multimedia team always is happy
to welcome new contributors.

Cheers
-- 
Sebastian Ramacher

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

[Stefan Pietsch]

On 07.06.20 08:48, Stefan Pietsch wrote:

On 2020-06-01 20:44, Stefan Pietsch wrote:


Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and 
linux-image-5.6.0-2-amd64 (5.6.14-1).


This also affects 5.5.0-rc5-amd64.

(https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/linux/)

The kernel boot option "intel_iommu=igfx_off" prevents the error message.


This seems to be resolved in newer kernel versions.
I'm not able to reproduce this with kernel version 5.14.0-4-amd64 (5.14.16-1).


Regards,
Stefan

Bug#1005899: mplayer: should not release with bookworm

[Lorenzo]

Hi Sebastian,

Could you please clarify if this package should be maintained inside the
Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer?

Regards,
Lorenzo

On Wed, 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher
 wrote:
> Source: mplayer
> Version: 2:1.4+ds1-3
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> Tags: sid bookworm
> 
> Let's stop pretending that mplayer is maintained. The upstream mailing
> list infrastructure is gone and development has been minimal over the
> last couple of months and years. So I think we should not include
> mplayer in bookworm. mpv is a worthy replacement for mplayer.
> 
> Cheers
> -- 
> Sebastian Ramacher

Bug#953790: quassel-client: Typo in spanish translation

[Diederik de Haas]

On Fri, 13 Mar 2020 10:31:57 -0300 Lisandro Damián Nicanor Pérez Meyer 
 wrote:
> Package: quassel-client
> Version: 1:0.13.1-3
> 
> Hi! In the spanish translation there is a typo: it says mesnaje instead of
> mensaje.
> 
> I've tried creating a pull request on quassel's github only to be closed and
> redirected to an even more proprietary system for doing translations on

Could you try again at https://github.com/quassel/quassel-i18n/pulls ?
They recently did merge an update to German translation there.

signature.asc
Description: This is a digitally signed message part.

Bug#931216: less: Ctrl-C has no effect with -c (--clear-screen) and process substitution

[Vincent Lefevre]

Control: tags -1 - patch + fixed-upstream

This is normally fixed in less 617 (see upstream bug).

After a few tests with the current version from Git, I can confirm
that this is fixed. And this is even better, with a message

  Waiting for data... (^X or interrupt to abort)

Both Ctrl-C (interrupt) and Ctrl-X work.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1027300: RFS: runit-services/0.5.3 -- UNIX init scheme with service supervision (services)

[Lorenzo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "runit-services":

 * Package name : runit-services
   Version  : 0.5.3
   Upstream contact : [fill in name and email of upstream]
 * URL  : [fill in URL of upstream's web site]
 * License  : BSD-3-Clause, CC0-1.0
 * Vcs  :
   https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services Section
  : admin

The source builds the following binary packages:

  runit-services - UNIX init scheme with service supervision (services)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/runit-services/

Alternatively, you can download the package with 'dget' using this
command:

  dget -x
  
https://mentors.debian.net/debian/pool/main/r/runit-services/runit-services_0.5.3.dsc

Git repo:

  https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/tree/next

Changes since the last upload:

 runit-services (0.5.3) unstable; urgency=medium
 .
   * update Readme
   * runit-services: depends on runit >= 2.1.2-51
   * Bump Standards-Version
   * bump B-D dh-runit >= 2.15.2, to get rid of
  duplicates metafiles
   * release to unstable

Regards,
Lorenzo Puliti

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

Control: severity 1027176 serious

On 2022-12-28, Vagrant Cascadian wrote:
> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
> commit triggering the issue has been identified as:
>
>   a9bf024b2933bba0e23038892970a18b72dfaeb4
>   efi_loader: disk: a helper function to create efi_disk objects from
>   udevice
>
> Workarounds I've heard are to disable EFI support for that board, or to
> boot using EFI rather than boot scripts or syslinux/extlinux style
> menus.

Bumped the severity to serious, as this breaks booting.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

[Joshua McNeil]

On Thu, 8 Dec 2022 13:05:48 +0100 Bastian Blank  wrote:
>
> The current default is suitable.  Hibernation does not work on any
> modern x86 machine and you don't want to have huge swap on desktop
> machines as it only adds latency.
>
> Bastian
>

I recently ran into this issue while considering Debian for desktop and
laptop usage and would also like to request increasing the swap default to
at least the size of RAM.

Hibernation works just fine on all of my modern x86_64 machines when the
swap space is sufficient. Could you elaborate on why you believe it doesn't?

If the primary objective was reducing memory latency I would suggest
instead modifying the default vm.swappiness which would actually affect how
often swap is used. I agree that in many cases swap causes degraded
performance for modern systems. However, hibernation is a good use for it.

In my experience when hibernation fails Debian appears less battery
efficient on laptops due to the need to retain power to memory when the lid
is closed. Ensuring the default  swap size is sufficient to support
hibernation helps improve this experience.

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Samuel Thibault]

Παύλος Γκέσος, le jeu. 29 déc. 2022 23:37:21 +0200, a ecrit:
> > Ah, you mean that currently, shift-w produces Sigma, but that's not
> > actually useful, so we can just make it a dead key for ̈́?
> 
> Exactly!
> This is what Microsoft Windows does.
> Probably the Windows kernel has the same limitation too :-)

That's very probable, yes.

Thanks for your very precise reports :)
Samuel

Bug#1027299: cryptsetup: on buster with linux-image-5.10-686-pae aes-xts-plain is not available

[Łukasz Stelmach]

Package: cryptsetup-initramfs
Version: 2:2.1.0-5+deb10u2
Severity: important
X-Debbugs-Cc: none, Łukasz Stelmach 

Dear Maintainer,

The version of cryptsetup-initramfs in buster is affected by
#959423[1]. Although it works with the default 4.19 kernel[2] it fails with
5.10 which is available from the main suite and NOT from
buster-backports. Installing cryptsetup-initramfs from buster-backports
helps.

IMHO the version of cryptsetup-initramfs in buster or buster-updates
should support 5.10 kernels.

I am upgrading from jessie to bullseye and need 5.10 kernel before the
last upgrade.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423#10
-- 
Miłego dnia,
Łukasz Stelmach

Bug#1027298: bullseye-pu: package libreoffice/1:7.0.4-4+deb11u5

[Rene Engelhard]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Hi,

follow up to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016037.

[ Reason ]
As said, Croatia joins the Eurozone on Jan, 1 2023, i.e. in to days.

That upload added support for Euro in Croatia. This upload switches the
default.

Something for stable-updates given the next point release is only
mid-Feb?

(Explain what the reason for the (old-)stable update is. I.e.
what is the bug, when was it introduced, is this a regression
with respect to the previous (old-)stable.)

[ Impact ]
Wrong currency default. Users might change it from the default to Euro,
but...

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Upstream fix added 1:1.

Full debdiff:

diff -Nru libreoffice-7.0.4/debian/changelog libreoffice-7.0.4/debian/changelog
--- libreoffice-7.0.4/debian/changelog  2022-09-06 18:54:37.0 +0200
+++ libreoffice-7.0.4/debian/changelog  2022-11-27 19:37:58.0 +0100
@@ -1,3 +1,9 @@
+libreoffice (1:7.0.4-4+deb11u5) bullseye; urgency=medium
+
+  * debian/patches/hrk-euro-default.diff: default to EUR for .hr 
+
+ -- Rene Engelhard   Sun, 27 Nov 2022 19:37:58 +0100
+
 libreoffice (1:7.0.4-4+deb11u4) bullseye-security; urgency=high
 
   * debian/patches/ZDI-CAN-17859.diff: fix ZDI-CAN-17859/CVE-2022-3140
diff -Nru libreoffice-7.0.4/debian/patches/hrk-euro-default.diff 
libreoffice-7.0.4/debian/patches/hrk-euro-default.diff
--- libreoffice-7.0.4/debian/patches/hrk-euro-default.diff  1970-01-01 
01:00:00.0 +0100
+++ libreoffice-7.0.4/debian/patches/hrk-euro-default.diff  2022-11-27 
19:37:48.0 +0100
@@ -0,0 +1,42 @@
+From c698c75adc32e04521d182c409c3401370190efe Mon Sep 17 00:00:00 2001
+From: Eike Rathke 
+Date: Sun, 27 Nov 2022 17:11:49 +0100
+Subject: [PATCH] Resolves: tdf#150011 Switch default currency HRK Croatian
+ Kuna to EUR Euro
+
+HR will join Euro area on 2023-01-01.
+
+Change-Id: I3836804ff68419550091826ea2414bc0edd55a84
+Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143346
+Reviewed-by: Eike Rathke 
+Tested-by: Jenkins
+(cherry picked from commit c58bc31ece80ccdfc88bd043787869c5e460dbd8)
+---
+ i18npool/source/localedata/data/hr_HR.xml | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/i18npool/source/localedata/data/hr_HR.xml 
b/i18npool/source/localedata/data/hr_HR.xml
+index 4de83e5535cd..1d29f1f2e0e6 100644
+--- a/i18npool/source/localedata/data/hr_HR.xml
 b/i18npool/source/localedata/data/hr_HR.xml
+@@ -414,15 +414,14 @@
+ 
+   
+   
+-
++
+   HRK
+   kn
+   HRK
+   Hrvatska Kuna
+   2
+ 
+-
+-
++
+   EUR
+   €
+   EUR
+-- 
+2.30.2
+
diff -Nru libreoffice-7.0.4/debian/patches/series 
libreoffice-7.0.4/debian/patches/series
--- libreoffice-7.0.4/debian/patches/series 2022-09-03 17:17:12.0 
+0200
+++ libreoffice-7.0.4/debian/patches/series 2022-11-27 19:37:58.0 
+0100
@@ -64,3 +64,4 @@
 0004-CVE-2022-2630-6-7-add-infobar-to-prompt-to-refresh-t.patch
 fix-e_book_client_connect_direct_sync-sig.diff
 ZDI-CAN-17859.diff
+hrk-euro-default.diff

[ Other info ]
I just uploaded the sid fix (>= 7.4.4 rc1 have it for sid) and thus also
could upload this now. Filing this bug for documentation purposes for
stable.

Regards,

Rene

Bug#1027297: u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in

[Vagrant Cascadian]

Package: u-boot
Version: 2022.04+dfsg-2
Severity: serious
Control: fixed -1 2022.10+dfsg-2
X-Debbugs-Cc: vagr...@debian.org, m...@drkrebs.de, t...@cyrius.com, 
i...@debian.org

At least two people have reported the same issue on sheevaplug and
guruplug failing to boot with a message "FDT and ATAGS support not
compiled in".

I suspect this was fixed in 2022.10-rc5 upstream with this commit:

  
https://source.denx.de/u-boot/u-boot/-/commit/a8a0c55f9d1cd0f4618288b25f63857373015391

  arm: kirkwood: Add CONFIG_SUPPORT_PASSING_ATAGS

Both tests confirm it working again with u-boot 2022.10+dfsg-2 and
2023.01~rc4+dfsg-1 from Debian.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027296: ruby3.0: do not release with bookworm

[Sebastian Ramacher]

Source: ruby3.0
Version: 3.0.4-8
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Following the transition to ruby3.1 as only supported ruby version,
let's get ruby3.0 removed from bookworm.

Cheers
-- 
Sebastian Ramacher

Bug#1027295: test-network-panel times out on riscv64

[Gunnar Hjalmarsson]

Package: src:gnome-control-center
Version: 1:43.2-1
Severity: important
Tags: ftbfs
X-Debbugs-CC: gunna...@debian.org

g-c-c 1:43.2-1 fails to build on riscv64:

https://buildd.debian.org/status/logs.php?pkg=gnome-control-center=riscv64

It's some kind of test timeout for test-network-panel.

While this is not an RC bug — riscv64 is not an official arch in Debian 
— it's a regression from g-c-c 1:43.1-2, so it may be worth looking at 
if we want to keep g-c-c available on riscv64. (FWIW it builds on 
riscv64 in Ubuntu.)

Bug#1027294: ITP: posixsignalmanager -- posix signal handling for qt

[Christoph Hueffelmann]

X-Debbugs-Cc: debian-de...@lists.debian.org, textsh...@uchuujin.de
Subject: ITP: posixsignalmanager -- posix signal handling for qt
Package: wnpp
Owner: Christoph Hueffelmann 
Severity: wishlist

* Package name: posixsignalmanager
  Version : 0.3
  Upstream Author : Martin Hostettler 
* URL : https://github.com/textshell/posixsignalmanager
* License : BSL-1.0
  Programming Lang: C++
  Description : posix signal handling for qt - shared library

Library safe, synchronous and asynchronous handling of posix signals
for Qt applications and libraries.

We need this package to close the bug #1027293.

And I would need a sponsor to upload my package.

Bug#1027293: ITP: tuiwidgets -- QtCore based terminal widget toolkit

[Christoph Hueffelmann]

X-Debbugs-Cc: debian-de...@lists.debian.org, textsh...@uchuujin.de
Subject: ITP: tuiwidgets -- QtCore based terminal widget toolkit
Package: wnpp
Owner: Christoph Hueffelmann 
Severity: wishlist

* Package name: tuiwidgets
  Version : 0.2.0
  Upstream Author : Martin Hostettler 
* URL : https://github.com/tuiwidgets/tuiwidgets
* License : BSL-1.0
  Programming Lang: C++
  Description : QtCore based terminal widget toolkit - shared library

This library provides a toolkit for fullscreen teminal user interfaces 
inspired by qt and using QtCore as base.


Its look and feel is similar to graphical applications or classic full 
screen terminal applications from the PC world of the 90s.


It uses the Qt event loop and object model and provides widgets for text 
entry, checkboxes, buttons, layout managers, menus and more.


It uses termpaint for terminal IO.

I would need a sponsor to upload my package.

Bug#1010608: openldap: Flaky test test063-delta-multiprovider

[Ryan Tandy]

On Wed, Dec 28, 2022 at 10:32:30PM +0100, Paul Gevers wrote:
Then not running the script at all is an improvement over the current 
situation. Flaky tests are bad. Until a better solution is found, how 
about skipping the test?


Not ideal, but yeah, probably an improvement over shipping a flaky test 
in stable. Thanks for the reminder, I'll try to upload it soon.

Bug#1027065: Clarification

[Ludovic Brenta]

On bookworm (testing) I get:

$ gm2 --version
gm2 (Debian 12.2.0-10) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gm2 hello.mod
hello.mod:1:2: error: expecting one of: ‘IMPLEMENTATION’ ‘MODULE’ ‘DEFINITION’
1 | FROM StrIO IMPORT WriteString, WriteLn;
  |  ^~~~
hello.mod:1:2: error: compilation failed

Adding a first line, "MODULE hello;" makes the program legal but then I
get the same symptoms as in the original bug report.

Adding -fpim2 or -fpim3 to the compiler command line has no effect.

Adding -fiso silences the compiler even though StrIO is not an ISO
module.  Therefore a complete workaround is:

$ cat hello.mod
MODULE hello;
FROM StrIO IMPORT WriteString, WriteLn;
BEGIN
 WriteString('hello world');
 WriteLn
END hello.
$ gm2 -fiso hello.mod -o hello
$ ./hello
hello world

It seems that libm2pim.so lacks some necessary functions which
libm2iso.so has.

-- 
Ludovic Brenta.

Bug#1000770: perfect-scrollbar: please make the build reproducible

[Vagrant Cascadian]

Control: tags 1000770 pending

On 2021-11-28, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> perfect-scrollbar could not be built reproducibly.
>
> This is because a copyright notice embeds the current build year.

I have uploaded an NMU to DELAYED/10 fixing this issue:

diff -Nru perfect-scrollbar-1.5.2+ds/debian/changelog 
perfect-scrollbar-1.5.2+ds/debian/changelog
--- perfect-scrollbar-1.5.2+ds/debian/changelog 2021-10-08 15:10:40.0 
-0700
+++ perfect-scrollbar-1.5.2+ds/debian/changelog 2022-12-29 14:26:32.0 
-0800
@@ -1,3 +1,12 @@
+perfect-scrollbar (1.5.2+ds-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Chris Lamb ]
+  * Make the build reproducible (Closes: #1000770)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 
14:26:32 -0800
+
 perfect-scrollbar (1.5.2+ds-1) unstable; urgency=medium
 
   * Initial release.
diff -Nru 
perfect-scrollbar-1.5.2+ds/debian/patches/make-the-build-reproducible-closes-10007.patch
 
perfect-scrollbar-1.5.2+ds/debian/patches/make-the-build-reproducible-closes-10007.patch
--- 
perfect-scrollbar-1.5.2+ds/debian/patches/make-the-build-reproducible-closes-10007.patch
1969-12-31 16:00:00.0 -0800
+++ 
perfect-scrollbar-1.5.2+ds/debian/patches/make-the-build-reproducible-closes-10007.patch
2022-12-29 14:26:32.0 -0800
@@ -0,0 +1,19 @@
+From: Chris Lamb 
+Date: Sun, 28 Nov 2021 11:39:34 -0800
+X-Dgit-Generated: 1.5.2+ds-1.1 8b2d1ce6fccd1839a5e8717b9e3469f413ef18b3
+Subject: Make the build reproducible (Closes: #1000770)
+
+
+---
+
+--- perfect-scrollbar-1.5.2+ds.orig/rollup.config.js
 perfect-scrollbar-1.5.2+ds/rollup.config.js
+@@ -7,7 +7,7 @@ const version = require('./package.json'
+ const banner =
+   `/*!
+  * perfect-scrollbar v${version}
+- * Copyright ${new Date().getFullYear()} Hyunje Jun, MDBootstrap and 
Contributors
++ * Copyright ${(new Date(process.env.SOURCE_DATE_EPOCH ? 
(process.env.SOURCE_DATE_EPOCH * 1000) : new Date().getTime())).getFullYear()} 
Hyunje Jun, MDBootstrap and Contributors
+  * Licensed under MIT
+  */
+ `;
diff -Nru perfect-scrollbar-1.5.2+ds/debian/patches/series 
perfect-scrollbar-1.5.2+ds/debian/patches/series
--- perfect-scrollbar-1.5.2+ds/debian/patches/series2021-10-08 
15:10:40.0 -0700
+++ perfect-scrollbar-1.5.2+ds/debian/patches/series2022-12-29 
14:26:32.0 -0800
@@ -1 +1,2 @@
 do-not-use-rollup-minify.patch
+make-the-build-reproducible-closes-10007.patch


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027291: RFS: dh-sysuser/1.3.8+really1.4.2 -- debhelper addon to handle creation of system users

[Lorenzo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "dh-sysuser":

 * Package name : dh-sysuser
   Version  : 1.3.8+really1.4.2
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://salsa.debian.org/debian/dh-sysuser
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/debian/dh-sysuser
   Section  : admin

The source builds the following binary packages:

  dh-sysuser - debhelper addon to handle creation of system users
  sysuser-helper - dh-sysuser implementation detail

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/dh-sysuser/

Alternatively, you can download the package with 'dget' using this
command:

  dget -x
  
https://mentors.debian.net/debian/pool/main/d/dh-sysuser/dh-sysuser_1.3.8+really1.4.2.dsc

Git repo:

  https://salsa.debian.org/debian/dh-sysuser/-/tree/next

Changes since the last upload:

 dh-sysuser (1.3.8+really1.4.2) unstable; urgency=medium
 .
   * No longer impose a strictly minor version for
  sysuser-helper: it doesn't save the need for a
  transition in case of a major version bump and
  it also forces the use of +really in package version
   * bump Standards-Version to 4.6.2
   * dh_sysuser: declare our $VERSION

Regards,
Lorenzo Puliti

Bug#1027292: lintian: Test "very-long-line-length-in-source-file" does not generate always reproducible results

[Hilmar Preusse]

Package: lintian
Version: 2.115.3
Severity: normal

Dear Maintainer,

I was wondering, why my lintian overrides did not work as expected. Then I
found out that the named test does not generate reproducible results.

Test suite:

hille@sid-amd64:~$ dget -d 
https://deb.debian.org/debian/pool/main/t/texinfo/texinfo_7.0.1-2.dsc

All files validated successfully.
hille@sid-amd64:~$ lintian --tag-display-limit 0 --pedantic -I 
texinfo_7.0.1-2.dsc > ttt1
hille@sid-amd64:~$ lintian --tag-display-limit 0 --pedantic -I 
texinfo_7.0.1-2.dsc > ttt2
hille@sid-amd64:~$ diff ttt1 ttt2 |wc -l
8
hille@sid-amd64:~$ diff ttt1 ttt2
33c33
< P: texinfo source: very-long-line-length-in-source-file 1493 > 512 
[tp/t/results/formats_encodings/at_commands_in_refs_utf8.pl:17317]
---
> P: texinfo source: very-long-line-length-in-source-file 1493 > 512 
> [tp/t/results/formats_encodings/at_commands_in_refs_utf8.pl:16903]
72c72
< P: texinfo source: very-long-line-length-in-source-file 617 > 512 
[tp/t/results/sectioning/section_in_unnumbered_info.pl:6548]
---
> P: texinfo source: very-long-line-length-in-source-file 617 > 512 
> [tp/t/results/sectioning/section_in_unnumbered_info.pl:6098]

Hilmar

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils2.39.50.20221224-1
ii  bzip2   1.0.8-5+b1
ii  diffstat1.64-1
ii  dpkg1.21.13
ii  dpkg-dev1.21.13
ii  file1:5.41-4
ii  gettext 0.21-10
ii  gpg 2.2.40-1
ii  intltool-debian 0.35.0+20060710.6
ii  iso-codes   4.12.0-1
ii  libapt-pkg-perl 0.1.40+b2
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-2+b1
ii  libcapture-tiny-perl0.48-2
ii  libclass-xsaccessor-perl1.19-4+b1
ii  libclone-perl   0.46-1
ii  libconfig-tiny-perl 2.28-2
ii  libconst-fast-perl  0.014-2
ii  libcpanel-json-xs-perl  4.32-1+b1
ii  libdata-dpath-perl  0.58-2
ii  libdata-validate-domain-perl0.10-1.1
ii  libdata-validate-uri-perl   0.07-2
ii  libdevel-size-perl  0.83-2+b1
pn  libdigest-sha-perl  
ii  libdpkg-perl1.21.13
ii  libemail-address-xs-perl1.05-1+b1
ii  libencode-perl  3.19-1+b1
ii  libfile-basedir-perl0.09-2
ii  libfile-find-rule-perl  0.34-3
ii  libfont-ttf-perl1.06-2
ii  libhtml-html5-entities-perl 0.004-3
ii  libhtml-tokeparser-simple-perl  3.16-4
ii  libio-interactive-perl  1.023-2
ii  libipc-run3-perl0.048-3
ii  libjson-maybexs-perl1.004004-1
ii  liblist-compare-perl0.55-2
ii  liblist-someutils-perl  0.58-3
ii  liblist-utilsby-perl0.12-2
ii  libmldbm-perl   2.05-4
ii  libmoo-perl 2.005004-3
ii  libmoox-aliases-perl0.001006-2
ii  libnamespace-clean-perl 0.27-2
ii  libpath-tiny-perl   0.124-1
ii  libperlio-gzip-perl 0.20-1+b1
ii  libperlio-utf8-strict-perl  0.010-1
ii  libproc-processtable-perl   0.634-1+b2
ii  libregexp-wildcards-perl1.05-3
ii  libsereal-decoder-perl  5.001+ds-1+b1
ii  libsereal-encoder-perl  5.001+ds-2
ii  libsort-versions-perl   1.62-3
ii  libsyntax-keyword-try-perl  0.28-1
ii  libterm-readkey-perl2.38-2+b1
ii  libtext-levenshteinxs-perl  0.03-5+b1
ii  libtext-markdown-discount-perl  0.13-2
ii  libtext-xslate-perl 3.5.9-1+b2
ii  libtime-duration-perl   1.21-2
ii  libtime-moment-perl 0.44-2+b1
ii  libtimedate-perl2.3300-2
ii  libunicode-utf8-perl0.62-2
ii  liburi-perl 5.17-1
ii  libwww-mechanize-perl   2.15-1
ii  libwww-perl 6.67-1
ii  libxml-libxml-perl  2.0207+dfsg+really+2.0134-1+b1
ii  libyaml-libyaml-perl0.84+ds-1+b1
ii  lzip [lzip-decompressor]1.23-4
ii  lzop1.04-2
ii  man-db  2.11.1-1
ii  patchutils  0.4.2-1
ii  perl [libencode-perl]   5.36.0-6
ii  t1utils 1.41-4
ii  unzip   6.0-27
ii  xz-utils5.4.0-0.1

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch 
pn  libtext-template-perl  

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

[Scott Talbert]

On Thu, 29 Dec 2022, Scott Kitterman wrote:


On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:

Control: tags -1 help

Hi,

I wonder whether someone might suggest a fix for


==
FAIL: test_schema_compatibility_type_mismatch
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
ype_mismatch)
--
Traceback (most recent call last):
  File
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
/test_compatibility.py", line 1039, in
test_schema_compatibility_type_mismatch self.assertIn(message,
result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not
found in {'reader type: SchemaType.NULL not compatible with writer type:
SchemaType.INT'}

--
Ran 421 tests in 8.358s

FAILED (failures=1, skipped=3)


Otherwise I will probably exclude Python3.11 from the build to fix this bug.


That's not an actual solution.  If you close the bug on this basis it will
hide the issue and make it appear we are more ready to move to Python 3.11 as
the default (and probably only) Python version for Bookworm.

I didn't look at the actual code.  Typically when something comes up Null is
means that something was not found.  I would look at the code where SchemaType
is determined to see how it might come up with no SchemaType.


It looks like this has already been fixed upstream (although with a 
non-obvious commit message):


https://github.com/apache/avro/commit/432f073c3cfb8ac7edb2793b797ab855c5a978dd

I just uploaded a fix.

Scott T.

Bug#1027290: lintian: false positive missing-build-dependency-for-dh_-command dh_nodejs_autodocs when build-depends on dh-sequence-nodejs

[Julian Gilbey]

Package: lintian
Version: 2.115.3
Severity: normal

My package-in-progress node-webfont declares Build-Depends:
dh-sequence-nodejs, which is (only) provided by dh-nodejs.  It uses
dh_nodejs_autodocs, and lintian reports:

E: node-webfont source: missing-build-dependency-for-dh_-command 
dh_nodejs_autodocs (does not satisfy dh-nodejs:any) [debian/rules]

I suggest that this is a false positive.

Best wishes,

   Julian

Bug#1027289: transition: libcamera

[Dylan Aïssi]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear Release Team,

Please schedule a transition slot for libcamera.

The auto-generated ben tracker looks good:
https://release.debian.org/transitions/html/auto-libcamera.html

The unique reverse dep (pipewire 0.3.63-1) builds fine with the
new libcamera in experimental.

Thanks,
Dylan

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Παύλος Γκέσος]

> Ah, you mean that currently, shift-w produces Sigma, but that's not
> actually useful, so we can just make it a dead key for ̈́?

Exactly!
This is what Microsoft Windows does.
Probably the Windows kernel has the same limitation too :-)

Bug#992061: surgescript: please make the build reproducible

[Vagrant Cascadian]

Control: tags 992061 pending

On 2021-08-10, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> surgescript could not be built reproducibly.
>
> This is because CMake's RPATH is not stripped, needing us to avoid
> it being set with -DCMAKE_SKIP_RPATH=ON.

Uploaded an NMU fixing this issue to DELAYED/10:

diff -Nru surgescript-0.5.4.4/debian/changelog 
surgescript-0.5.4.4/debian/changelog
--- surgescript-0.5.4.4/debian/changelog2020-12-09 20:26:49.0 
-0800
+++ surgescript-0.5.4.4/debian/changelog2022-12-29 13:18:46.0 
-0800
@@ -1,3 +1,13 @@
+surgescript (0.5.4.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Chris Lamb ]
+  * debian/rules: Pass -DCMAKE_SKIP_RPATH=ON to dh_auto_configure.
+(Closes: #992061)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 
13:18:46 -0800
+
 surgescript (0.5.4.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru surgescript-0.5.4.4/debian/rules surgescript-0.5.4.4/debian/rules
--- surgescript-0.5.4.4/debian/rules2020-12-09 20:26:49.0 -0800
+++ surgescript-0.5.4.4/debian/rules2022-12-29 13:18:46.0 -0800
@@ -15,7 +15,8 @@
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DLIB_SUFFIX=/$(DEB_HOST_MULTIARCH)
+   -DLIB_SUFFIX=/$(DEB_HOST_MULTIARCH) \
+   -DCMAKE_SKIP_RPATH=ON
 
 override_dh_compress:
dh_compress -X.ss


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

[Scott Kitterman]

On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:
> Control: tags -1 help
> 
> Hi,
> 
> I wonder whether someone might suggest a fix for
> 
> 
> ==
> FAIL: test_schema_compatibility_type_mismatch
> (avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
> ype_mismatch)
> --
> Traceback (most recent call last):
>   File
> "/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
> /test_compatibility.py", line 1039, in
> test_schema_compatibility_type_mismatch self.assertIn(message,
> result.messages)
> AssertionError: 'reader type: null not compatible with writer type: int' not
> found in {'reader type: SchemaType.NULL not compatible with writer type:
> SchemaType.INT'}
> 
> --
> Ran 421 tests in 8.358s
> 
> FAILED (failures=1, skipped=3)
> 
> 
> Otherwise I will probably exclude Python3.11 from the build to fix this bug.

That's not an actual solution.  If you close the bug on this basis it will 
hide the issue and make it appear we are more ready to move to Python 3.11 as 
the default (and probably only) Python version for Bookworm.

I didn't look at the actual code.  Typically when something comes up Null is 
means that something was not found.  I would look at the code where SchemaType 
is determined to see how it might come up with no SchemaType.

Scott K

signature.asc
Description: This is a digitally signed message part.

Bug#1021505: mir: FTBFS on hppa - symbols

[John David Anglin]

On 2022-12-28 3:21 p.m., Mike Gabriel wrote:

The .symbols have now been updated. Should be resolved with the just uploaded 
version.

Still lots of problems:
https://buildd.debian.org/status/fetch.php?pkg=mir=hppa=1.8.2%2Bdfsg-5=1672271857=0

Dave

--
John David Anglin  dave.ang...@bell.net

Bug#1027284: mpfr_custom_get_kind broken in current 4.1.1

[Vincent Lefevre]

Control: tags -1 upstream fixed-upstream

On 2022-12-29 19:22:12 +0100, Yuri D'Elia wrote:
> According to https://github.com/CGAL/cgal/issues/7064 mpfr 4.1.1 was
> updated after-the-fact without a version bump.

I'm wondering what you mean by "version bump".

> mpfr 4.1.1 in debian has a broken macro definition of
> mpfr_custom_get_kind that prevents building against CGAL.
> 
> Looks like the package needs to be refreshed with the updated upstream's
> version or apply the patch[0] independently.
> 
> [0] 
> https://github.com/BrianGladman/mpfr/commit/0ce17bae34a6c54de31b126f969d3ddd72c6bc37

There's no newer version for the 4.1 branch. So I suggest one of
these 3 possibilities:

1. Apply the patch available on https://www.mpfr.org/mpfr-4.1.1/#bugs

2. Apply the patch from the git commit 0ce17bae34a6c54de31b126f969d3ddd72c6bc37

3. Upgrade to 4.2.0-rc1 (this version is ABI and API compatible and
has the fix for this bug). I will do the release in a few days, as
everything seems fine (there's only a possible failure on m68k with
QEMU, but after investigation, this is due to a QEMU bug, and the
generated code should be correct; BTW, the 4.1.* versions also have
the concerned test).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Samuel Thibault]

Παύλος Γκέσος, le jeu. 29 déc. 2022 23:08:23 +0200, a ecrit:
> > There is a workaround then.
> > The Microsoft Windows workaround:
> >
> > Press key combination Shift-w (dead key for ΅)
> > Press key y or i to get characters ΰ or ΐ.
> 
> To certify what I said about Shift-w:
> http://kbdlayout.info/kbdhe

Ah, you mean that currently, shift-w produces Sigma, but that's not
actually useful, so we can just make it a dead key for ̈́?

Samuel

Bug#1027127: transition: zxing-cpp

[Sebastian Ramacher]

Hi

On 2022-12-29 20:51:28 +0100, Johannes Schauer Marin Rodrigues wrote:
> Quoting Sebastian Ramacher (2022-12-29 10:30:42)
> > > > Is it too late before the freeze to do this?
> > > 
> > > It's not too late, but we need to finish the qtbase-opensource-src
> > > transition first.
> > 
> > Please go ahead.
> 
> zxing-cpp 1.4.0-1 is now in unstable and the transition underway:

Looks like the uploaded included binaries. Please perform a source-only
upload.

Cheers

> 
> https://release.debian.org/transitions/html/auto-zxing-cpp.html
> 
> In case anything FTBFS I'll file bugs and patches as required.
> 
> Boyuan, I tried to merge the unstable and experimental branches as best I
> could. I hope I didn't forget anything. If I messed something up, please tell
> and I'll take care to repair it.
> 
> Dennis, in #1021686 you expressed that you wanted 1.4.0 for mediastreamer2 
> 5.2.
> I wanted to notify you, that the version is now available for you in unstable.
> 
> Thanks!
> 
> cheers, josch
> 

-- 
Sebastian Ramacher

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Samuel Thibault]

Hello,

Παύλος Γκέσος, le jeu. 29 déc. 2022 23:02:55 +0200, a ecrit:
> > Yes, unfortunately that's something that the Linux kernel does not
> > support currently. It only supports one dead key press at a time.
> 
> I never imagined that for dead keys there is code in the kernel.

The whole Linux console is supported by the Linux kernel, there is no
userland code involved except for loading fonts & keyboard layouts into
the kernel.

> There is a workaround then.
> The Microsoft Windows workaround:
> 
> Press key combination Shift-w (dead key for ΅)
> Press key y or i to get characters ΰ or ΐ.
> 
> These characters are very useful in the Greek language.
> Also the implementation with the Shift-w key combination does not
> break anything as:
> key s gives char σ
> key combination Shift-s gives char Σ
> key w gives char ς
> key combination Shift-w gives char Σ again

I don't understand: in what you described, shift-w is used both for dead
key for ΅ and for producing Σ ?

Or did you mean shift-; above?

Samuel

Bug#992060: pytsk: please make the build reproducible

[Vagrant Cascadian]

On 2022-12-29, Hilko Bengen wrote:
> * Vagrant Cascadian:
>
>> I have uploaded an NMU to DELAYED/10 applying the patch included
>> upstream:
>
> Looks good to me. Feel free to reschedule the upload to hit unstable
> immediately.

Thanks... rescheduled!

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#992060: pytsk: please make the build reproducible

[Hilko Bengen]

* Vagrant Cascadian:

> I have uploaded an NMU to DELAYED/10 applying the patch included
> upstream:

Looks good to me. Feel free to reschedule the upload to hit unstable
immediately.

Cheers,
-Hilko

Bug#995647: cfi: reproducible builds: Embedded timestamps in .dvi file

[Vagrant Cascadian]

Control: tags 995647 pending

On 2021-10-03, Vagrant Cascadian wrote:
> The build timestamp is embedded in various .dvi files:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/cfi.html
>
>   ./usr/share/doc/cfi-sv/cfi.dvi.gz
>
>   ··TeX·output·2022.
> vs.
>   ··TeX·output·2021.
> 0020:·3039·2e32·373a·3139·3439·8b00··0100
>
>   ··09.27:1949..
> vs.
>   ··08.26:1527..
>
> The attached patch fixes this by setting FORCE_SOURCE_DATE=1 in
> debian/rules, which texlive needs in order to respect SOURCE_DATE_EPOCH,

Uploaded an NMU fixing this issue to DELAYED/10:

diff -Nru cfi-3.0/debian/changelog cfi-3.0/debian/changelog
--- cfi-3.0/debian/changelog2021-01-05 07:09:27.0 -0800
+++ cfi-3.0/debian/changelog2022-12-29 12:47:39.0 -0800
@@ -1,3 +1,11 @@
+cfi (3.0-10.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Export FORCE_SOURCE_DATE=1 in order for texlive to
+respect SOURCE_DATE_EPOCH when generating .dvi file. (Closes: #995647)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 
12:47:39 -0800
+
 cfi (3.0-10.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru cfi-3.0/debian/rules cfi-3.0/debian/rules
--- cfi-3.0/debian/rules2012-11-10 12:28:46.0 -0800
+++ cfi-3.0/debian/rules2022-12-29 12:47:39.0 -0800
@@ -3,6 +3,9 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+# Ensure texlive respects SOURCE_DATE_EPOCH
+export FORCE_SOURCE_DATE=1
+
 build: build-arch build-indep
 build-arch: build-stamp
 build-indep: build-stamp


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

[Andreas Tille]

Control: tags -1 help

Hi,

I wonder whether someone might suggest a fix for


==
FAIL: test_schema_compatibility_type_mismatch 
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_type_mismatch)
--
Traceback (most recent call last):
  File 
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test/test_compatibility.py",
 line 1039, in test_schema_compatibility_type_mismatch
self.assertIn(message, result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not 
found in {'reader type: SchemaType.NULL not compatible with writer type: 
SchemaType.INT'}

--
Ran 421 tests in 8.358s

FAILED (failures=1, skipped=3)


Otherwise I will probably exclude Python3.11 from the build to fix this bug.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Παύλος Γκέσος]

> There is a workaround then.
> The Microsoft Windows workaround:
>
> Press key combination Shift-w (dead key for ΅)
> Press key y or i to get characters ΰ or ΐ.

To certify what I said about Shift-w:
http://kbdlayout.info/kbdhe

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Παύλος Γκέσος]

> Yes, unfortunately that's something that the Linux kernel does not
> support currently. It only supports one dead key press at a time.

I never imagined that for dead keys there is code in the kernel.

There is a workaround then.
The Microsoft Windows workaround:

Press key combination Shift-w (dead key for ΅)
Press key y or i to get characters ΰ or ΐ.

These characters are very useful in the Greek language.
Also the implementation with the Shift-w key combination does not
break anything as:
key s gives char σ
key combination Shift-s gives char Σ
key w gives char ς
key combination Shift-w gives char Σ again (this duplication does not
exist on Microsoft Windows as it is a dead key)

Advantages:
- Very useful Greek keyboard characters will be implemented.
Everything is better than nothing.
- Only one dead key, as the kernel permits.
- It will not create significant confusion for users because it is the
same keyboard layout as the equivalent of Microsoft Windows.

Disadvantages:
- X has another key combination: ; Shift-; y instead of Shit-w y. This
will be a bit confusing for users, but consider that now these useful
characters are not EVEN available in tty!

Any thoughts?

Bug#1027288: tigervnc-common: orphaned alternatives (vncpasswd, vncpasswd.1.gz)

[Jakub Wilk]

Package: tigervnc-common
Version: 1.12.0+dfsg-7

tigervnc-common used to install alternatives for "vncpasswd" and 
"vncpasswd.1.gz". Now it no longer does, but it didn't clean up the old 
ones:


   $ file /usr/bin/vncp* /usr/share/man/man*/vncp* | grep -w broken
   /usr/bin/vncpasswd: broken symbolic link to 
/etc/alternatives/vncpasswd
   /usr/share/man/man1/vncpasswd.1.gz: broken symbolic link to 
/etc/alternatives/vncpasswd.1.gz


-- System Information:
Architecture: i386

Versions of packages tigervnc-common depends on:
ii  libc6   2.36-7
ii  libgcc-s1   12.2.0-11
ii  libstdc++6  12.2.0-11
ii  libx11-62:1.8.3-3

--
Jakub Wilk

Bug#1027234: sarsen: autopkgtest fail with numpy/1.24.1

[Antonio Valentino]

Hi,
the source of the issue seems to be in python-numpy-groupies

regards
--
Antonio Valentino

Bug#1027196: flox: autopkgtest fail with numpy/1.24.1

[Antonio Valentino]

Hi Sandro,
the source of the issue seems to be in python-numpy-groupies

regards
--
Antonio Valentino

Bug#1026333: ITP rustup

[matthias . geiger1024]

Update on the missing deps:

- effective-limits is NEW
- download: needs async-compression (for the reqwest features ) which needs xz2
- xz2: merged. needs lzma-sys (merged)
- zstd: merged. (thanks noctis :) )
- git testament: See https://github.com/kinnison/git-testament/issues/19

Cheers

werdahias

Bug#1023750: Fixes for CVE-2022-45059 and CVE-2022-45060 for bookworm?

[Salvatore Bonaccorso]

Hi Varnish maintainers, hi Stig

There are yet open CVEs for varnish affecting upcoming bookworm. Any
chance you could upload 7.1.2 for unstable to make sure the fixes
enter testing and are included in bookworm?

Regards,
Salvatore

Bug#1026539: theano: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

[Andreas Tille]

Hi Rebecca,

given that there were some uploads to experimental I'm wondering what
might be the best strategy to fix the bug - either in the version in
unstable or in 1.1.2 and upload this to unstable.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'

[Olek Wojnar]

Control: tag -1 moreinfo

Hi Sebastian and thanks for the bug report.


On 12/27/22 18:15, Sebastian Ramacher wrote:

Source: bazel-bootstrap
Version: 4.2.3+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap=amd64=4.2.3%2Bds-1%2Bb1=1671977092=0

␛[1A␛[K␛[31m␛[1mERROR: ␛[0m/<>/src/main/cpp/BUILD:91:10: Linking 
src/main/cpp/client failed: (Exit 1): gcc failed: error executing command
   (cd /tmp/bazel_hloBSNSM/out/execroot/io_bazel && \
   exec env - \
 CCACHE_DISABLE=1 \
 CCACHE_TEMPDIR=/<>/debian/ccachetmp \
 LC_ALL=C \
 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \
 PWD=/proc/self/cwd \
   /usr/bin/gcc @bazel-out/k8-dbg/bin/src/main/cpp/client-2.params)
Execution platform: //:default_host_platform
␛[32m[111 / 127]␛[0m 3 actions running
 //src/main/java/com/google/devtools/build/lib/bazel:BazelServer; 5s local
 JavacBootstrap .../devtools/build/singlejar/libbootstrap.jar; 2s local
 JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 2s local

␛[1A␛[K
␛[1A␛[K
␛[1A␛[K
␛[1A␛[K/usr/include/grpcpp/completion_queue.h:119: error: undefined reference 
to 'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 
'absl::debian3::Mutex::Lock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 
'absl::debian3::Mutex::Lock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
collect2: error: ld returned 1 exit status
␛[32m[111 / 127]␛[0m 3 actions running



I'm talking to László about this because it seems to be connected to the 
ongoing grpc transition. Hopefully we can figure something out soon!



-Olek

Bug#1027287: bookworm: Segfaults when trying to use basic buttons

[Gunnar Wolf]

Package: bookworm
Version: 1.1.2+git20210715-2
Severity: important

I am trying to read my first epub book with bookworm. Whenever I press
either the "Library", "Table of contents" or "Reading preferences"
buttons, bookworm unceremoniously dies with a segmentation fault.

I cannot share the ebook I'm trying to read to the BTS, as it's a
copyrighted book; I can privately share it to the maintainer if it's
for debugging purposes, in case you think it's necessary to pinpoint
the bug.

In case it's relevant, I'm running under the Sway Wayland compositor,
and bookworm does open as a Sway client (no xwayland emulation).

Thanks!

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bookworm depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  html2text1.3.2a-28
ii  libc62.36-6
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
pn  libgee-0.8-2 
ii  libglib2.0-0 2.74.3-1
pn  libgranite6  
ii  libgtk-3-0   3.24.35-3
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpoppler-glib8 22.08.0-2.1
ii  libsoup2.4-1 2.74.3-1
ii  libsqlite3-0 3.40.0-1
ii  libwebkit2gtk-4.0-37 2.38.2-1+b1
ii  libxml2  2.9.14+dfsg-1.1+b2
ii  poppler-utils22.08.0-2.1
ii  python3  3.10.6-3
ii  unar 1.10.7+ds1+really1.10.1-2+b1
ii  unzip6.0-27

bookworm recommends no packages.

bookworm suggests no packages.

Bug#1027127: transition: zxing-cpp

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Sebastian Ramacher (2022-12-29 10:30:42)
> > > Is it too late before the freeze to do this?
> > 
> > It's not too late, but we need to finish the qtbase-opensource-src
> > transition first.
> 
> Please go ahead.

zxing-cpp 1.4.0-1 is now in unstable and the transition underway:

https://release.debian.org/transitions/html/auto-zxing-cpp.html

In case anything FTBFS I'll file bugs and patches as required.

Boyuan, I tried to merge the unstable and experimental branches as best I
could. I hope I didn't forget anything. If I messed something up, please tell
and I'll take care to repair it.

Dennis, in #1021686 you expressed that you wanted 1.4.0 for mediastreamer2 5.2.
I wanted to notify you, that the version is now available for you in unstable.

Thanks!

cheers, josch

Bug#1027286: bookworm: Please provide a symlink to the binary with a more memorable name (i.e. /usr/bin/bookworm)

[Gunnar Wolf]

Package: bookworm
Version: 1.1.2+git20210715-2
Severity: wishlist
Tags: patch

I understand the reasons why Bookworm's binary must have the
unconventional long name "com.github.babluboy.bookworm" name, given
several language ecosystems insist on encoding the component's Web
locations as part of their names. However, on a Debian system, we have
grown used to just "apt install pkgname" and expect to find a
"pkgname" binary to launch it with.

Could you provide a symlink named /usr/bin/bookworm to
/usr/bin/com.github.babluboy.bookworm for it to be more easy to
launch?

Of course, the patch is trivial, but provided nevertheless:

diff --git a/debian/bookworm.links b/debian/bookworm.links
new file mode 100644
index 000..e1aa0a4
--- /dev/null
+++ b/debian/bookworm.links
@@ -0,0 +1 @@
+/usr/bin/com.github.babluboy.bookworm /usr/bin/bookworm

Thanks!

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bookworm depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  html2text1.3.2a-28
ii  libc62.36-6
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
pn  libgee-0.8-2 
ii  libglib2.0-0 2.74.3-1
pn  libgranite6  
ii  libgtk-3-0   3.24.35-3
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpoppler-glib8 22.08.0-2.1
ii  libsoup2.4-1 2.74.3-1
ii  libsqlite3-0 3.40.0-1
ii  libwebkit2gtk-4.0-37 2.38.2-1+b1
ii  libxml2  2.9.14+dfsg-1.1+b2
ii  poppler-utils22.08.0-2.1
ii  python3  3.10.6-3
ii  unar 1.10.7+ds1+really1.10.1-2+b1
ii  unzip6.0-27

bookworm recommends no packages.

bookworm suggests no packages.

Bug#1026986: console-setup: "Dead" keys do not work for Greek keyboard layout in tty

[Samuel Thibault]

Hello,

Παύλος Γκέσος, le mar. 27 déc. 2022 11:08:02 +0200, a ecrit:
> The following functionality is not fixed:
> 
> WHAT MUST HAPPEN:
> Type KEY   ; (in Greek is the CHAR "'") - This is a
> "dead" key and nothing happens
> Type KEY COMBINATION Shift-; (in Greek is the CHAR """) - This is a
> "dead" key and nothing happens
> Type KEY   y (in Greek is the CHAR "υ"). The CHAR "ΰ"
> must appear in tty (you have it with Alt+0944 key combination)

Yes, unfortunately that's something that the Linux kernel does not
support currently. It only supports one dead key press at a time.

Samuel

Bug#992060: pytsk: please make the build reproducible

[Vagrant Cascadian]

Control: tags 992060 pending

On 2021-08-10, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> pytsk could not be built reproducibly.
>
> This is because it generated a pytsk3.c file in a nondeterministic
> manner, specifically by naively iterating over a Python set()
> structure.

I have uploaded an NMU to DELAYED/10 applying the patch included
upstream:

diff -Nru pytsk-20200117/debian/changelog pytsk-20200117/debian/changelog
--- pytsk-20200117/debian/changelog 2021-01-27 06:48:04.0 -0800
+++ pytsk-20200117/debian/changelog 2022-12-29 11:12:45.0 -0800
@@ -1,3 +1,13 @@
+pytsk (20200117-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Chris Lamb ]
+  * debian/patches: Changes to generation of pytsk3.c for reproducible
+build (Closes: #992060)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 
11:12:45 -0800
+
 pytsk (20200117-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru 
pytsk-20200117/debian/patches/changes-to-generation-of-pytsk3.c-for-re.patch 
pytsk-20200117/debian/patches/changes-to-generation-of-pytsk3.c-for-re.patch
--- 
pytsk-20200117/debian/patches/changes-to-generation-of-pytsk3.c-for-re.patch
1969-12-31 16:00:00.0 -0800
+++ 
pytsk-20200117/debian/patches/changes-to-generation-of-pytsk3.c-for-re.patch
2022-12-29 11:12:45.0 -0800
@@ -0,0 +1,27 @@
+From: Chris Lamb 
+Date: Tue, 10 Aug 2021 11:57:34 +0100
+X-Dgit-Generated: 20200117-3.1 986f3e5bd0dd74f93dca15637e2c1242c6546d76
+Subject: Changes to generation of pytsk3.c for reproducible build
+
+(Closes: #992060)
+
+Merged upstream as
+https://github.com/py4n6/pytsk/commit/f2b9ffa642a83127eb0e517a1f0ed4a22a99199a
+in pull request https://github.com/py4n6/pytsk/pull/81
+
+---
+
+--- pytsk-20200117.orig/class_parser.py
 pytsk-20200117/class_parser.py
+@@ -913,8 +913,9 @@ uint64_t integer_object_copy_to_uint64(P
+ for class_name in self.classes.keys():
+ self.initialise_class(class_name, out, done)
+ 
+-# Add the constants in here
+-for constant, type in self.constants:
++# Add the constants here. Make sure they are sorted so builds
++# of pytsk3.c are reproducible.
++for constant, type in sorted(self.constants):
+ if type == "integer":
+ out.write(
+ "tmp = PyLong_FromUnsignedLongLong((uint64_t) 
{0:s});\n".format(constant))
diff -Nru pytsk-20200117/debian/patches/series 
pytsk-20200117/debian/patches/series
--- pytsk-20200117/debian/patches/series2021-01-27 06:48:04.0 
-0800
+++ pytsk-20200117/debian/patches/series2022-12-29 11:12:45.0 
-0800
@@ -1,2 +1,3 @@
 0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
 change-lexer.patch
+changes-to-generation-of-pytsk3.c-for-re.patch


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027285: matplotlib: axes3d.quiver() fails when providing args to Line3DCollection

[Drew Parsons]

Source: matplotlib
Version: 3.6.2-3
Severity: serious
Justification: debci
Control: forwarded -1 https://github.com/matplotlib/matplotlib/issues/24842
Control: block 1027170 by -1

mplot3d.axes3d.quiver() accepts boths args and kwargs in its function
definition.

Both args (any remaining after the first 6 values) and kwargs are
passed onwards to art3d.Line3DCollection at
matplotlib/lib/mpl_toolkits/mplot3d/axes3d.py Line 2655 in 3393a4f:

  linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs) 

But arguments for Line3DCollection are passed directly to
LineCollection. In matplotlib PR#23076 appearing in matplotlib 3.6,
LineCollection was changed so that it no longer accepts positional
args. All excess arguments must now be provided in kwargs.

This means axes3d.quiver() now fails with matplotlib 3.6. An example
failure is in 3D plot tests from dolfin.

The python backtrace running* this demo script (on a debian system)
looks like

Traceback (most recent call last):
  File 
"/projects/fenics/build/tests/dolfin/demo-python/undocumented/curl-curl/demo_curl-curl.py",
 line 172, in 
plot(J)
  File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", 
line 440, in plot
return _plot_matplotlib(object, mesh, kwargs)
  File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", 
line 306, in _plot_matplotlib
return mplot_function(ax, obj, **kwargs)
  File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", 
line 218, in mplot_function
return ax.quiver3D(*args, length=length, **kwargs)
  File "/usr/lib/python3/dist-packages/matplotlib/__init__.py", line 1427, in 
inner
return func(ax, *map(sanitize_sequence, args), **kwargs)
  File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/axes3d.py", line 
2567, in quiver
linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs)
TypeError: LineCollection.__init__() takes 2 positional arguments but 3 were 
given

The TypeError occurs because of the use of args, which, to reiterate,
was removed in matplotlib 3.6 PR#23076.

I gather that any options which were previously provided to
axes3d.quiver and intended for use in Line3DCollection must now be
provided in kwargs instead. quiver should no longer use args at all at
l.2655.


* Note, to run that dolfin demo to reproduce the error,
dolfin/common/plotting.py also needed updating for matplotlib 3.6 near
l.279:
-ax = plt.gca(projection='3d')
+ax = plt.axes(projection='3d')
This patch will be applied to dolfin to close Bug#1027170.


For matplotlib itself, I propose simply removing the use of args in
axes3d.py l.2655:

-  linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs) 
+  linec = art3d.Line3DCollection(lines, **kwargs) 

Bug#1017218: ruby-parallel: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Paul Gevers]

Hi,

On Sun, 14 Aug 2022 09:20:57 +0200 Lucas Nussbaum  wrote:

Source: ruby-parallel
Version: 1.22.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  # ./spec/spec_helper.rb:9:in `block (2 levels) in '
> 
> Finished in 1 minute 44.28 seconds (files took 0.10294 seconds to load)

> 152 examples, 1 failure, 4 pending
> 
> Failed examples:
> 
> rspec './spec/parallel_spec.rb[1:10:30]' # Parallel.each does not call the finish hook when a worker fails with ractors
> 
> /usr/bin/ruby3.0 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed

> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.0" failed. Exiting.
> dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-parallel returned exit code 1
> make: *** [debian/rules:7: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
> E: Build killed with signal TERM after 150 minutes of inactivity


While trying to find out which test was the potential culprit of this 
issue (I guess something kept running instead of being killed/closed), I 
ran into multiple different failures depending on my retry attempt (see 
some below). So, it seems these tests are particularly sensitive to the 
load of the system (I regularly hit timeouts). I think it's best to 
disable the build test (and potentially also the autopkgtest, albeit I 
haven't seen that fail very often yet).


Paul
PS, I tried the attached patch, but that seems to have pushed some times 
out of reasonable limits as I was getting very different errors.


E.g. currently on reproducible-builds.org:
https://tests.reproducible-builds.org/debian/logs/bookworm/amd64/ruby-parallel_1.22.1-1.build2.log.gz

Failures:

  1) Parallel.in_processes kills the processes when the main process 
gets killed through ctrl+c

 Failure/Error:
   time_taken do
 result = execute_start_and_kill "PROCESS", 0
 result.should_not include "FINISHED"
   end.should be <= 3

   expected: <= 3
got:3.4196298122406006
 # ./spec/parallel_spec.rb:103:in `block (3 levels) in (required)>'

 # ./spec/spec_helper.rb:9:in `block (2 levels) in '

  2) Parallel.in_processes kills the processes when the main process 
gets killed through a custom interrupt

 Failure/Error:
   lambda {
 t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb 
#{command} 2>&1 && echo 'FINISHED'") }

 sleep 1.5

kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
 sleep 1
   }.should change { `ps`.split("\n").size }.by amount

   expected ``ps`.split("\n").size` to have changed by 0, but was 
changed by 19

 # ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
 # ./spec/parallel_spec.rb:111:in `block (4 levels) in (required)>'

 # ./spec/parallel_spec.rb:11:in `time_taken'
 # ./spec/parallel_spec.rb:110:in `block (3 levels) in (required)>'

 # ./spec/spec_helper.rb:9:in `block (2 levels) in '

  3) Parallel.in_processes kills the threads when the main process gets 
killed through ctrl+c

 Failure/Error:
   lambda {
 t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb 
#{command} 2>&1 && echo 'FINISHED'") }

 sleep 1.5

kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
 sleep 1
   }.should change { `ps`.split("\n").size }.by amount

   expected ``ps`.split("\n").size` to have changed by 0, but was 
changed by -20

 # ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
 # ./spec/parallel_spec.rb:117:in `block (4 levels) in (required)>'

 # ./spec/parallel_spec.rb:11:in `time_taken'
 # ./spec/parallel_spec.rb:116:in `block (3 levels) in (required)>'

 # ./spec/spec_helper.rb:9:in `block (2 levels) in '

  4) Parallel.in_processes does not kill processes when the main 
process gets sent an interrupt besides the custom interrupt

 Failure/Error:
   lambda {
 t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb 
#{command} 2>&1 && echo 'FINISHED'") }

 sleep 1.5

kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
 sleep 1
   }.should change { `ps`.split("\n").size }.by amount

   expected ``ps`.split("\n").size` to have changed by 4, but was 
changed by -18

 # ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
 # ./spec/parallel_spec.rb:124:in `block (4 levels) in (required)>'

 # ./spec/parallel_spec.rb:11:in `time_taken'
 # ./spec/parallel_spec.rb:123:in `block (3 levels) in (required)>'

 # 

Bug#991181: cmocka: reproducible builds: Embeds build path in documentation

[Vagrant Cascadian]

Control: tags 991181 pending

On 2021-07-16, Vagrant Cascadian wrote:
> The build path is embedded in various documentation files:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/cmocka.html
>
>   ./usr/share/doc/cmocka-doc/html/cmocka_8h_source.html
>
>   cmocka:·/build/1st/cmocka-1.1.5/include/cmocka.h·Source·File
>   vs.
>   
> cmocka:·/build/2/cmocka-1.1.5/2nd/include/cmocka.h·Source·File
>
> The attached patch fixes this by setting configuration options in
> doc/CMakeLists.txt to pass FULL_PATH_NAMES = NO in the doxygen
> configuration used to generate the documentation.

I have uploaded an NMU fixing this issue and including pending changes
in git from Debian Janitor, and pushed the new changes to git.

diff -Nru cmocka-1.1.5/debian/changelog cmocka-1.1.5/debian/changelog
--- cmocka-1.1.5/debian/changelog   2019-08-10 20:34:42.0 -0700
+++ cmocka-1.1.5/debian/changelog   2022-12-29 10:55:47.0 -0800
@@ -1,3 +1,22 @@
+cmocka (1.1.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Debian Janitor ]
+  * Remove constraints unnecessary since buster
+  * Bump debhelper from old 12 to 13.
+  * Remove obsolete fields Contact, Name from debian/upstream/metadata
+(already present in machine-readable debian/copyright).
+  * Update standards version to 4.6.0, no changes needed.
+  * Fix field name case in debian/control (Build-Depends-indep =>
+Build-Depends-Indep).
+
+  [ Vagrant Cascadian ]
+  * debian/patches: Disable embedding of full path names in documentation
+generated by doxygen. (Closes: #991181)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 
10:55:47 -0800
+
 cmocka (1.1.5-2) unstable; urgency=medium
 
   * Upload to unstable now that buster has been released
diff -Nru cmocka-1.1.5/debian/control cmocka-1.1.5/debian/control
--- cmocka-1.1.5/debian/control 2019-08-10 20:33:57.0 -0700
+++ cmocka-1.1.5/debian/control 2022-12-29 10:45:43.0 -0800
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: David Prévot 
 Uploaders: Sandro Knauß 
-Build-Depends: cmake (>= 3.10), debhelper-compat (= 12)
-Build-Depends-indep: doxygen
-Standards-Version: 4.4.0
+Build-Depends: cmake, debhelper-compat (= 13)
+Standards-Version: 4.6.0
 Homepage: https://cmocka.org/
 Vcs-Git: https://salsa.debian.org/debian/cmocka.git
 Vcs-Browser: https://salsa.debian.org/debian/cmocka
+Build-Depends-Indep: doxygen
 
 Package: cmocka-doc
 Section: doc
diff -Nru 
cmocka-1.1.5/debian/patches/0001-doc-CMakeLists.txt-Disable-embedding-of-full-path-na.patch
 
cmocka-1.1.5/debian/patches/0001-doc-CMakeLists.txt-Disable-embedding-of-full-path-na.patch
--- 
cmocka-1.1.5/debian/patches/0001-doc-CMakeLists.txt-Disable-embedding-of-full-path-na.patch
 1969-12-31 16:00:00.0 -0800
+++ 
cmocka-1.1.5/debian/patches/0001-doc-CMakeLists.txt-Disable-embedding-of-full-path-na.patch
 2022-12-29 10:50:33.0 -0800
@@ -0,0 +1,26 @@
+From 54c4c552b27e180256593a019718b1a886dd31f7 Mon Sep 17 00:00:00 2001
+From: Vagrant Cascadian 
+Date: Fri, 16 Jul 2021 15:13:48 +
+Subject: [PATCH] doc/CMakeLists.txt: Disable embedding of full path names in
+ documentation generated by doxygen. (Closes: #991181)
+
+https://reproducible-builds.org/docs/build-path/
+---
+ doc/CMakeLists.txt | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt
+index 6ac7494..9d4e7b5 100644
+--- a/doc/CMakeLists.txt
 b/doc/CMakeLists.txt
+@@ -31,6 +31,7 @@ if (DOXYGEN_FOUND)
+  
${CMAKE_CURRENT_SOURCE_DIR}/that_style/img/folderclosed.svg
+  
${CMAKE_CURRENT_SOURCE_DIR}/that_style/img/folderopen.svg
+  
${CMAKE_CURRENT_SOURCE_DIR}/that_style/js/striped_bg.js)
++set(DOXYGEN_FULL_PATH_NAMES no)
+ 
+ set(_doxyfile_template "${CMAKE_BINARY_DIR}/CMakeDoxyfile.in")
+ set(_target_doxyfile "${CMAKE_CURRENT_BINARY_DIR}/Doxyfile.docs")
+-- 
+2.30.2
+
diff -Nru cmocka-1.1.5/debian/patches/series cmocka-1.1.5/debian/patches/series
--- cmocka-1.1.5/debian/patches/series  1969-12-31 16:00:00.0 -0800
+++ cmocka-1.1.5/debian/patches/series  2022-12-29 10:50:54.0 -0800
@@ -0,0 +1 @@
+0001-doc-CMakeLists.txt-Disable-embedding-of-full-path-na.patch
diff -Nru cmocka-1.1.5/debian/upstream/metadata 
cmocka-1.1.5/debian/upstream/metadata
--- cmocka-1.1.5/debian/upstream/metadata   2019-08-10 20:33:56.0 
-0700
+++ cmocka-1.1.5/debian/upstream/metadata   1969-12-31 16:00:00.0 
-0800
@@ -1,2 +0,0 @@
-Name: CMocka
-Contact: Andreas Schneider 


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#979019: fixed upstream

[Holger Levsen]

hi,

the fix for https://sourceforge.net/p/lirc/git/merge-requests/36/ has been
merged upstream.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

People call vaccine mandates "Orwellian" even though Orwell died at 46 of
tuberculosis, which is now preventable with a vaccine.


signature.asc
Description: PGP signature

Bug#1027284: mpfr_custom_get_kind broken in current 4.1.1

[Yuri D'Elia]

Package: libmpfr-dev
Version: 4.1.1-1
Severity: important

According to https://github.com/CGAL/cgal/issues/7064 mpfr 4.1.1 was
updated after-the-fact without a version bump.

mpfr 4.1.1 in debian has a broken macro definition of
mpfr_custom_get_kind that prevents building against CGAL.

Looks like the package needs to be refreshed with the updated upstream's
version or apply the patch[0] independently.

[0] 
https://github.com/BrianGladman/mpfr/commit/0ce17bae34a6c54de31b126f969d3ddd72c6bc37

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmpfr-dev:amd64 depends on:
ii  libgmp-dev  2:6.2.1+dfsg1-1.1
ii  libmpfr64.1.1-1

libmpfr-dev:amd64 recommends no packages.

Versions of packages libmpfr-dev:amd64 suggests:
pn  libmpfr-doc  

Bug#991180: NMU fixing reproducible builds and cross-building bugs

[Vagrant Cascadian]

Control: tags 991180 pending
Control: tags 986704 pending

I have uploaded an NMU to DELAYED/10 fixing reproducible builds and
cross-building issues, as well as some pending issues already merged in
git found by Debian Janitor.

Merge request also available:

  https://salsa.debian.org/debian/xaw3dg/-/merge_requests/3

Full debdiff follows (including changes already in git, in particular,
whitespace changes):

diff -Nru xaw3d-1.5+F/debian/changelog xaw3d-1.5+F/debian/changelog
--- xaw3d-1.5+F/debian/changelog2021-01-07 10:57:42.0 -0800
+++ xaw3d-1.5+F/debian/changelog2022-12-29 10:16:57.0 -0800
@@ -1,3 +1,20 @@
+xaw3d (1.5+F-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Debian Janitor ]
+  * Trim trailing whitespace.
+  * Update standards version to 4.6.1, no changes needed.
+
+  [ Vagrant Cascadian ]
+  * debian/rules: Pass CFLAGS with file-prefix-map in dh_auto_build.
+(Closes: #991180)
+
+  [ Nilesh Patra ]
+  * Fix cross-building. (Closes: #986704)
+
+ -- Vagrant Cascadian   Thu, 29 Dec 2022 10:16:57 -0800
+
 xaw3d (1.5+F-1) unstable; urgency=medium
 
   * Reassembled original tarball to cope with dquilt.
@@ -13,7 +30,7 @@
 
   * Non-maintainer upload.
   * debian/control: Drop explicit Pre-Depends on multiarch-support (Closes:
-#870564). 
+#870564).
 
  -- Aurelien Jarno   Sat, 20 Jan 2018 14:50:00 +0100
 
@@ -42,7 +59,7 @@
   * Added patch XawIm.c to prevent gv segfaulting.
 (closes: #573474)
   * Added ${misc:Depends} to both binary packages to make lintian happy.
-  * Added xaw3dg.lintian-overrides to override the 
+  * Added xaw3dg.lintian-overrides to override the
 package-name-doesnt-match-sonames lintian warning.
   * Added debian/README.source.
 
@@ -50,8 +67,8 @@
 
 xaw3d (1.5+E-17) unstable; urgency=low
 
-  * Bumped replace to conflicts with pre -16 version. That's needed for 
-moving of the .so link 
+  * Bumped replace to conflicts with pre -16 version. That's needed for
+moving of the .so link
(closes: #492302)
 
  -- Francesco Paolo Lovergine   Fri, 25 Jul 2008 09:47:14 
+0200
@@ -99,7 +116,7 @@
   * Removed libxaw8-dev fake dependency, because it has been dropped in xorg
 roadmap.
   * Removed all X11 -dev dependencies in xaw3dg-dev, and the old
-libc-dev|libc6-dev now superfluous dependency too. Packages now have to 
+libc-dev|libc6-dev now superfluous dependency too. Packages now have to
 declare explicitly their own -dev build-deps.
 (closes: #241280)
 
@@ -107,7 +124,7 @@
 
 xaw3d (1.5+E-11) unstable; urgency=low
 
-  * Changed to xorg 7 conformancy in paths: 
+  * Changed to xorg 7 conformancy in paths:
/usr/X11R6/lib -> /usr/lib
 /usr/X11R6/include -> /usr/include
 (closes: #362074, #363578)
@@ -189,8 +206,8 @@
 
 xaw3d (1.5+E-1) unstable; urgency=low
 
-  * Ready for unstable. 
-Changing release version for a smooth upgrading from experimental. 
+  * Ready for unstable.
+Changing release version for a smooth upgrading from experimental.
 (closes: #117325,#196439,#144877)
 
  -- Francesco Paolo Lovergine   Tue, 19 Aug 2003 00:35:30 
+0200
@@ -295,12 +312,12 @@
 xaw3d (1.5-15) unstable; urgency=low
 
   * Added -DARROW_SCROLLBAR in rules file for EXTRA_DEFINES.
-The trick described in old scrollbars doc is no longer working due 
+The trick described in old scrollbars doc is no longer working due
 to changes in rules file: EXTRA_DEFINES in lib/Xaw3d/Imakefile are ignored.
 That obsolete document has been removed.
 Emacs folks will be happy :)
 
-This seems also closing an old bug report about scrolling in 
+This seems also closing an old bug report about scrolling in
 emacs21 and xterm. Or hope so. I'll see if I could get some better
 patches to have a rock solid correction.
 (closes: #36736)
@@ -370,7 +387,7 @@
   * The xaw3dg preinst did return an error when the "medium" debconf
 note wasn't displayed. I added " || true" to fix this.
 (closes: #86599)
-  * debian/shlibs: Generate a dependency on xaw3dg (>= 1.5-6). 
+  * debian/shlibs: Generate a dependency on xaw3dg (>= 1.5-6).
 
  -- Adrian Bunk   Tue, 20 Feb 2001 14:21:24 +0100
 
@@ -486,7 +503,7 @@
 
   * Non-maintainer upload
   * Handle ld.so.conf properly in postrm as well
-  
+
  -- Wichert Akkerman   Tue, 21 Dec 1999 23:54:45 +0100
 
 xaw3d (1.3-6.6) unstable; urgency=low
@@ -554,13 +571,13 @@
   * now uses libc6
   * included a shlibs file
   * added xaw-wrappers file for axe
-  
+
  -- joost witteveen   Sun,  3 Aug 1997 20:31:18 
+0200
 
 xaw3d (1.3-5) unstable; urgency=low
 
   * Compiled with -D_REENTRANT
-  * uses new, unreleased ld.so-1.8.9, so that the soname now can be 
+  * uses new, unreleased ld.so-1.8.9, so that the soname now can be
 libxaw3d, making everything somewhat easier.
 
  -- joost witteveen   Sun, 9 Feb 1997 10:56:39 
+0100
@@ -584,7 +601,7 @@
   * Changed /sbin/ldconfig to ldconfig in postinst, prerm.
   * 

Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"

[Carsten Schoenert]

Hello Andreas,

Am 29.12.22 um 18:00 schrieb Andreas Metzler:

(Ideally the cmake setup should check wxWidgets's EGL-status and set
KICAD_USE_EGL accordingly instead of failing at build-time.)


KiCad upstream did have the same idea some time ago and added a wishlist 
report against wxWidgets.


https://github.com/wxWidgets/wxWidgets/issues/22325

But given the development dynamics of wxWidgets I do not expect a quick 
solution for this.


--
Regards
Carsten

Bug#1027070: linux-image-amd64: resume from hibernate fails, no keyboard or mouse, no screen or frozen screen

[Wolf-Dieter Groll]

In order to get a possibly more consistent system, I switched to Debian 
12 in the meantime.

This uses the kernel 6.0.12-1 as well.

   apt list linux-image-amd64
   Auflistung… Fertig
   linux-image-amd64/testing,now 6.0.12-1 amd64  [installiert]

The behavior has not changed, the system does seem to wake up when a key 
is pressed, the hard drive and fan start, the status LED is permanently 
on instead of blinking, but the system remains unusable. No further 
response to keyboard or mouse, and the network has not been reactivated 
either, no response to a ping.


The PC is based on an Asus A68HM-PLUS with UEFI BIOS V. 2011-x64 10/17/2018.


On Tue, 27 Dec 2022 16:30:12 +0100 Diederik de Haas 
 wrote:

> Control: reassign -1 src:linux 6.0.3-1~bpo11+1
>
> On Tuesday, 27 December 2022 15:42:31 CET Wolf-Dieter Groll wrote:
> > Package: linux-image-amd64
> > Version: 6.0.3-1~bpo11+1
>
> Stable backports now has 6.0.12-1~bpo11+1, could you try that too?



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1026499: rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859']

[s3v]

Dear Maintainer,

After adding python3-magic to B-D (and d/t/control Depends), your package
builds fine in my sid chroot environment.

Kind Regards

Bug#1025782: Info received (gpg-wks-server not build with sendmail)

[Andrew Gallagher]

I have opened a related ticket upstream (https://dev.gnupg.org/T6321), however 
Debian should still fix their build.


signature.asc
Description: Message signed with OpenPGP

Bug#1022167: angelfish: Search engine hard-coded, and having Internet-based home-page is against Debian policy.

[Nilesh Patra]

Control: tags -1 moreinfo

Hi Shawn,

Sorry it took long to reply back. Reply inline:

On Fri, 21 Oct 2022 03:39:17 -0700 Shawn Landden  
wrote:
> Package: angelfish
> Version: 22.06-1
> Severity: normal

> If I change /usr/share/config.kcfg/angelfishsettings.kcfg to point to a search
> engine other than DuckDuckGo, it still goes to this site, and the settings do 
> not appear to
> do anything.

And I suppose you shouldn't be doing this at all, anyway.

> It is also impossible to change the homepage from 
> https://start.duckduckgo.com/
> which means that this package calls home. It will go to this url even if the 
> configuration
> file is changed.

I tried this: Open browser, click on top right (three bars for settings) > 
Choose Settings > Toolbars

In Toolbars, I am able to set my desired homepage, as well as new tab page. and 
it works.

And there is also an option for search engine selection in the same search 
window, which seems to 
work just fine.

Could you confirm this is working for you?

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1018954: Can't open perl script "/usr/share/vtk9/doxygen//doc_header2doxygen.pl": No such file or directory

[Mathieu Malaterre]

On Thu, Dec 29, 2022 at 5:10 PM Paul Gevers  wrote:
>
> Hi,
>
> On Fri, 2 Sep 2022 15:15:50 +0200 Mathieu Malaterre 
> wrote:
> > Source: vtk9
> > Version: 9.1.0+really9.1.0+dfsg2-4
> >
> > This is yet the same issue again, gdcm will need the file 
> > doc_header2doxygen.pl
> >
> > In vtk7 it could be found in two locations:
> >
> > % dpkg -S /usr/share/vtk-7.1/doxygen/doc_header2doxygen.pl
> > libvtk7-dev: /usr/share/vtk-7.1/doxygen/doc_header2doxygen.pl
> > % dpkg -S /usr/share/doc/vtk7/doxygen/doc_header2doxygen.pl.gz
> > vtk7-doc: /usr/share/doc/vtk7/doxygen/doc_header2doxygen.pl.gz
> >
> > Please provide at least one in vtk9* packages.
>
> It seems that file has been dropped from the upstream vtk* sources (at
> least I couldn't find it anymore in vtk9 salsa git archive). So I guess
> that if gdcm needs it for its build, it's better if gdcm took the copy
> on board.

Oh right! It seems this file was removed in commit
f4902fe5e342e12a4859a490e825ef75d199

I'll remove the code in GDCM asap.

Thanks !

Bug#1025782: gpg-wks-server not build with sendmail

[Andrew Gallagher]

I have reproduced this bug. gpg-wks-server is currently unusable on bullseye.


signature.asc
Description: Message signed with OpenPGP

Bug#914035: Adopt influxdb (and friends) packages

[Ludovic Rousseau]

Le 29/12/2022 à 18:21, Ludovic Rousseau a écrit :

Le 16/11/2022 à 22:56, Ludovic Rousseau a écrit :

I am *completely* new to Go. So maybe this error is easy to fix.
Before I adopt influxdb I would need some help from knowledgeable people :-)

Can you help me?


After some tries and the help of the Go packaging team [1] I was able to 
rebuild version 1.6 (current version in Debian).

I then tried to upgrade to version 1.8.10 (or even version 2.6.0) but I have Go 
errors.
I am not ready to invest a huge amount of time into learning Go.
I give up trying to package influxdb.


In case it can be used, my current patches are available at
https://salsa.debian.org/rousseau/influxdb

Bye

--
Dr. Ludovic Rousseau

Bug#1027283: transition: tiff

[GCS]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi RMs,

Unplanned transition of tiff as its new release is just recently out.
The API seems to be the same, but the ABI is changed. Basic reason is
that its behaviour is changed and returns quicker from processing
invalid images.
While it's a big transition, nine levels deep, test rebuilds show in
the first five levels only two package self-testing breaks. I've
already patched one of them. Currently it only hard breaks hylafax
which seems to be a dead project since 2012; a memory corruption and a
security fix was committed to it, but even those happened in 2018 or
earlier. Anyway, I've notified tiff upstream and will act accordingly.

As tiff is used commonly and has security issues from time to time it
would be good to have its latest release in Debian. I don't know if
the old version will get any fixes or not.

Regards,
Laszlo/GCS

Bug#914035: Adopt influxdb (and friends) packages

[Ludovic Rousseau]

Le 16/11/2022 à 22:56, Ludovic Rousseau a écrit :

I am *completely* new to Go. So maybe this error is easy to fix.
Before I adopt influxdb I would need some help from knowledgeable people :-)

Can you help me?


After some tries and the help of the Go packaging team [1] I was able to 
rebuild version 1.6 (current version in Debian).

I then tried to upgrade to version 1.8.10 (or even version 2.6.0) but I have Go 
errors.
I am not ready to invest a huge amount of time into learning Go.
I give up trying to package influxdb.

The package is still available for adoption.

Bye

[1] https://lists.debian.org/debian-go/2022/11/msg00052.html

--
Dr. Ludovic Rousseau

Bug#1018265: Info received (Bug#1018265 closed by Brian Potkin (cups picks manual tray on HP Color LaserJet M252dw))

[Steinar Bang]

To summarize for a future googler that ends up here.

The printer in question is an HP Color LaserJet from 2014, with dual
sided printing and colour.  The printer has an onboard NIC and natively
supports PostScript and IPP.

Windows PCs and iDevices can print directly to this network printer and
do not need to use the CUPS printer, so there is no need to export the
printer from CUPS.

Tip: it might be an idea to lock the printer's MAC addres to a fixed
IPv4 address in your router's DHCP server (otherwise you may have to
reinstall the printer on windows machines, because windows printer
drivers are locked to a particular IP address and stops working if the
printer gets a new address).

With CUPS it is possible to use two drivers for this printer
 1. "driverless"[1] (part of the cups-filters-core-drivers package[2])
 2. "hplip"[3]

To summarize:
 1. The driverless driver sort, of, kind of works, but doesn't support
PostScript and sometimes picks the wrong tray (the manual feed
slot), and there is no way to select what tray to use. But colour
and dual sided printing both works
 2. The hplip driver works, lets you select the tray and prints dual
sided.  But the hplip printer doesn't print colour from a webkit
based browser (chromium and vivaldi on my debian system).  The hplip
printer prints colour fine from the Atril PDF viewer, from firefox
and from libreoffice 

The driverless driver builds and regenerates the PPD from the networked
printer itself.  So any edits you try to make to the PPD is overwritten
(I found an edit of the tray names in the PPD when googling for similar
problems and found out that the edit I tried to make just disappeared).

The driverless printer installs itself, sort of.  Or at least it
reinstalls itself when deleted, once installed.

On my computer the driverless printer shows up in printer dialogs, as:
 HP_Color_LaserJet_Pro_M252dw_501595_

The hplip driver shows up in printer dialogs, as:
 HP_Color_LaserJet_Pro_M252dw

The installation of the hplip printer was as follows:
 1. Clicked on "Find New Printer"
 2. 3 printers appeared:
1. Virtual Braille BRF Printer (CUPS-BRF)
2. Hewlett-Packard HP Color LaserJet Pro M252dw (Hewlett-Packard HP Color 
LaserJet Pro M252dw (driverless))
3. HP Color LaserJet Pro M252dw (HP Color LaserJet Pro M252dw)
 3. Clicked on "Add This Printer" next to "HP Color LaserJet Pro M252dw (HP 
Color LaserJet Pro M252dw)"
 4. Added name, description and location
 5. Under "Make" selected "HP" and clicked "Continue"
 6. Under "Model" there were 13 lines of "HP Color LaserJet PRO M252 Postscript 
(recommended) (en)"
 7. Selected the first to the 13 lines and clicked on "Add Printer"
 8. Changed "Printer Options" from
  | Media size | Letter|
  | Two-sided  | off   |
  | Paper feed | Automatic |
to
  | Media size | A4|
  | Two-sided  | Long-edge binding |
  | Paper feed | Automatic |
 9. Seleced the tab "Options Installed" and switched "Duplex Unit" to "on"
10. Clicked "Set Default Options"


References
 [1] 
 [2] 
 [3] 

Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

[Ian Campbell]

On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
> jetson-tk1

 testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2 ok
 exp: 2023.01~rc4+dfsg-1 ok

> Bananapi

I don't seem to have a working setup for this any more, sorry.

> Cubieboard2 

 testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2 ok
 exp: 2023.01~rc4+dfsg-1 ok

I mentioned those successes on the wiki.

Bug#964985: libpcap0.8: build with rpcap support (--enable-remote)

[Romain Francoise]

Hi,

On Thu, Dec 29, 2022 at 11:42 AM Peter Vanpoucke  wrote:
> Could this get picked up? I've used a port for Linux separately before,
> but that one will no longer be maintained:
> .

I will look into it.

Thanks.

Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"

[Andreas Metzler]

Control: tags -1 patch

On 2022-12-28 Sebastian Ramacher  wrote:
> Source: kicad
> Version: 6.0.10+dfsg-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=kicad=amd64=6.0.10%2Bdfsg-1%2Bb2=1672197224=0
[...]
> /<>/include/gal/opengl/kiglew.h:47:14: error: #error 
> "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL 
> canvas"
>47 | #error "KICAD_USE_EGL can only be used when wxWidgets is 
> compiled with the EGL canvas"
>   |  ^

Hello,

wxWidgets has recently switched back to non-EGL (See
https://bugs.debian.org/1024147 and https://bugs.debian.org/1020640),
for kicad the build error is trivially fixable by changing 
-DKICAD_USE_EGL=ON \
back to
-DKICAD_USE_EGL=OFF \

(Ideally the cmake setup should check wxWidgets's EGL-status and set
KICAD_USE_EGL accordingly instead of failing at build-time.)

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#1025975: RFP: deepin-log-viewer -- Useful tool for viewing system logs

[Thomas Uhle]

On Thu, 29 Dec 2022, Arun Kumar Pariyar wrote:

The package deepin-log-viewer was already uploaded and available in Debian 
[1]. That is why I am closing this bug.


1. https://tracker.debian.org/pkg/deepin-log-viewer

Regards,
~ Arun Kumar Pariyar



I haven't noticed that. So sorry for this ticket and thank you for the hint.

Best regards,

Thomas Uhle

Bug#1027173: dh-python: dh_python3 no longer generates correct package dependencies

[Drew Parsons]

On 2022-12-29 17:27, Stefano Rivera wrote:

Reassign: -1 src:python-meshio

...

You'll also see this warning:
* Building wheel...
/tmp/build-env-t5py7ec_/lib/python3.10/site-packages/setuptools/config/_apply_pyprojecttoml.py:196:
UserWarning: `install_requires` overwritten in `pyproject.toml`
(dependencies)
  warnings.warn(msg)

That points to the problem. The pyproject declares dependencies, but
leaves out rich.



Thanks for the analysis, Stefano.  I'll review documentation for 
pyproject.toml and make a patch inside meshio then.


Drew

Bug#1027173: dh-python: dh_python3 no longer generates correct package dependencies

[Stefano Rivera]

Reassign: -1 src:python-meshio

Hi Drew (2022.12.28_09:14:53_+)
> I'm seeing the problem in python3-meshio 7.0.0-2, which depends on
> python3-rich.  The dependency was located for 7.0.0-1,
> cf. https://packages.debian.org/bookworm/python3-meshio
> but is no longer generated for 7.0.0-2,
> see https://packages.debian.org/unstable/python3-meshio
> 
> The package is the same, only a minor update (and updating to
> Standards-Version: 4.6.2).  The dependency on rich is declared in
> setup.cfg.

If you build a wheel, you'll see this in the METADATA:
Requires-Dist: numpy (>=1.20.0)
Requires-Dist: importlib-metadata ; python_version < "3.8"
Provides-Extra: all
Requires-Dist: netCDF4 ; extra == 'all'
Requires-Dist: h5py ; extra == 'all'

No sign of rich.

You'll also see this warning:
* Building wheel...
/tmp/build-env-t5py7ec_/lib/python3.10/site-packages/setuptools/config/_apply_pyprojecttoml.py:196:
 UserWarning: `install_requires` overwritten in `pyproject.toml` (dependencies)
  warnings.warn(msg)

That points to the problem. The pyproject declares dependencies, but
leaves out rich.

So, I think a new version of setuptools prioritized that over setup.cfg.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1027282: rust-prettytable-rs: RUSTSEC-2022-0074

[Salvatore Bonaccorso]

Source: rust-prettytable-rs
Version: 0.8.0-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

There is a RUSTSEC advisory affecting rust-prettytable-rs:

https://rustsec.org/advisories/RUSTSEC-2022-0074.html

Patched in 0.10.0. Filling it in the BTS for crossreference.

Regards,
Salvatore

Bug#1018954: Can't open perl script "/usr/share/vtk9/doxygen//doc_header2doxygen.pl": No such file or directory

[Paul Gevers]

Hi,

On Fri, 2 Sep 2022 15:15:50 +0200 Mathieu Malaterre  
wrote:

Source: vtk9
Version: 9.1.0+really9.1.0+dfsg2-4

This is yet the same issue again, gdcm will need the file doc_header2doxygen.pl

In vtk7 it could be found in two locations:

% dpkg -S /usr/share/vtk-7.1/doxygen/doc_header2doxygen.pl
libvtk7-dev: /usr/share/vtk-7.1/doxygen/doc_header2doxygen.pl
% dpkg -S /usr/share/doc/vtk7/doxygen/doc_header2doxygen.pl.gz
vtk7-doc: /usr/share/doc/vtk7/doxygen/doc_header2doxygen.pl.gz

Please provide at least one in vtk9* packages.


It seems that file has been dropped from the upstream vtk* sources (at 
least I couldn't find it anymore in vtk9 salsa git archive). So I guess 
that if gdcm needs it for its build, it's better if gdcm took the copy 
on board.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1026722: gst-python1.0: FTBFS: dh_install: error: missing files, aborting

[Andreas Rönnquist]

usr/lib/python* in .install misses items that now are installed to
/usr/local/lib/*.

This is #1026312.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312

-- Andreas Rönnquist
gus...@debian.org

Bug#1027003: gnome-control-center: Pls consider keyboard patches from upstream MR

[Gunnar Hjalmarsson]

I'm about to update g-c-c to version 43.2, and will then include 
keyboard-Allow-disabling-alternate-characters-key.patch.


Let's consider this bug fixed with that. If somebody wants to improve 
the "Alternate Characters Key" control further through the other two 
patches, that can be done later.


--
Gunnar

Bug#1026984: Possible fix for pan crash

[piorunz]

Hello Dominique,

Fix 100% fixed this problem, I can browse this particular group again :)

On 29/12/2022 10:14, Dominique Dumont wrote:

Hi

piorunz, could you try the fix proposed there:

https://gitlab.gnome.org/GNOME/pan/-/merge_requests/41

All the best

Dod




--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1026976: Upcoming test suite regression due to changes in file/libmagic

[Christoph Biedl]

Chris Lamb wrote...

> Thanks again for the "new version of file in experimental" bugs; very
> much appreciated.

You're welcome. Given file's volatility, I guess this will not be the
last conversation in that regard ...

> > - a /usr/bin/python3 script executable (binary data)
> > + Zip archive, with extra data prepended
> >
> > Now that looks a bit delicate ... if you think this is something that
> > should be handled in file/libmagic, let me know.
>
> Naturally, as one of the maintainers of strip-nondeterminism, I am
> inclined to believe that this is a minor regression in file. :)

This indeed was the rare where I think a change in file(1), while done
with best intentions, caused more harm than benefit.

> However, this "extra data prepended" doesn't fit well under the rubric
> of "data". Yes, this "#!/usr/bin/python3\n" shebang is definitely
> "data" of a kind, but a shebang isn't really data in that way given
> the special-treatment afforded to it by UNIX systems. Even if this
> noun was replaced by the more general "bytes", the magic nature of the
> shebang would still remain… as would the desire to discriminate
> between pyzip files and other ZIP files with prepended data.
>
> Could another — different — string be emitted in the case that these
> prepended bytes are a shebang? We could potentially look for the file
> starting with #! and for that to take precedence over this new case.

After some more thinking: I suggest you do nothing for the time being
while I take this to upstream. If all else fails, I'll revert the change
for the next upload. By the way, that will be 1:5.44-1, but the changes
to 1:5.43-3 are minimal.

Christoph


signature.asc
Description: PGP signature

Bug#1027281: RM: python-congressclient -- ROM; deprecated upstream, RC buggy

[Thomas Goirand]

Package: ftp.debian.org
Severity: normal

Hi,

The Congress project is abandonned usptream, so is its client. Please
remove this package from Debian.

Cheers,

Thomas Goirand (zigo)

Bug#1016963: Please test with helping rpi_arm64

[Denis Pynkin]

Hi,

On 12/29/22 00:55, Vagrant Cascadian wrote:

On 2022-12-28, Vagrant Cascadian wrote:

I have not received many test results for current or even remotely
recent u-boot platforms in Debian, and u-boot has been blocked from
migration to testing partly because of this.

As the bookworm freeze approaches, this is getting to be... worrysome!

If you have access to any of these boards, please consider testing
u-boot versions as packaged in debian for versions from debian stable
(2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
(2023.01-rc*) and updating the wiki page if successful and/or replying
to 1016...@bugs.debian.org with a positive confirmation...

rpi_arm64


Tested `rpi_arm64` target with RPi 3 B 1GB and RPi 4 B 2GB.

Tested versions below are able to work with USB keyboard, serial, hdmi 
output and boot the target OS to graphical UI:

- U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +)
- U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)
- U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)

With the version from stable -- no HDMI for RPi4, all works for RPi3:
- U-Boot 2021.01+dfsg-5 (May 23 2021 - 04:32:45 +)

PS Tested `rpi_arm64` boot with the daily image image from ApertisOS 
since it is using that target by default, have graphical UI and works 
both with RPi3 and RPi4,

so it is convenient to compare the U-Boot itself.

--
Denis Pynkin
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718

Bug#1024239: libequihash: baseline violation on i386 and FTBFS on !x86

[Joost van Baal-Ilić]

Thanks, after consulting with upstream this should be fixed in new upstream
https://github.com/stef/equihash/archive/refs/tags/v1.0.3.tar.gz which has
https://github.com/stef/equihash/commit/0806afadf99837519469449c55dc425763e8eef7
.  I'll upload a new package soonishlish.

Bye,

Joost


On Wed, Nov 16, 2022 at 11:37:01AM +0200, Adrian Bunk wrote:
> Source: libequihash
> Version: 1.0.2-3
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=libequihash=arm64=1.0.2-3=1668331092=0
> 
> ...
> make[1]: Entering directory '/<>'
> g++ -c -Wall -g -O3 -std=c++17 -fstack-protector-strong -D_FORTIFY_SOURCE=2 
> -fasynchronous-unwind-tables -fpic -Werror=format-security -Wl,-z,defs 
> -Wl,-z,relro -ftrapv -Wl,-z,noexecstack -march=native 
> -fstack-clash-protection -fcf-protection=full -o equihash.o equihash.cc
> cc1plus: error: ‘-fcf-protection=full’ is not supported for this target
> make[1]: *** [Makefile:16: equihash.o] Error 1
> 
> 
> -fcf-protection=full is an x86-only option not supported on
> other architectures.
> 
> -fcf-protection=full violates the i386 baseline,
> please use it only on amd64.

Bug#1027280: mldonkey-server: mldonkey is missing from the repositories.

[Sebastien CHAVAUX]

Package: mldonkey-server
Severity: wishlist
Tags: ftbfs
X-Debbugs-Cc: seb95.s...@gmail.com

Dear Maintainer,

* Mldonkey has been missing since Buster,
* It is impossible for the moment to make the package from the sources, I have
this result:

make[2]: *** [Makefile:5479: src/utils/cdk/zlibstubs.o] Error 2
make[2]: Leaving directory '/build/mldonkey-3.1.7'
make[1]: *** [debian/rules:40: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/mldonkey-3.1.7'
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
I: copying local configuration
E: Failed autobuilding of package

Could we have it for Debian 12?

Sincerely, Seb.


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-20-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1027279: RFS: python-fire/0.5.0-1 [QA] [RC] -- automatically generate CLIs from absolutely any Python object

[Bo YU]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "python-fire":

 * Package name : python-fire
   Version  : 0.5.0-1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://github.com/google/python-fire
 * License  : Apache-2.0
 * Vcs  : https://salsa.debian.org/python-team/packages/python-fire
   Section  : python

The source builds the following binary packages:

  python3-fire - automatically generate CLIs from absolutely any Python object

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/python-fire/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-fire/python-fire_0.5.0-1.dsc

Changes since the last upload:

 python-fire (0.5.0-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream version 0.5.0
   * Add patch to fix ftbfs on python3.11. (Closes: #1026619)
   * Add Rules-Requires-Root.
   * Update d/copyright

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1027278: gcc-12: change multiarch from loongarch64-linux-gnu to loongarch64-linux-gnuf64

[zhangdandan]

Package: gcc-12
Version: 12.2.0-11
Severity: wishlist
Tags: patch
User: debian-de...@lists.debian.org
Usertags: loongarch64

Dear gcc maintainers,

According to LoongArch manual: 
https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html
LoongArch need to change multiarch from loongarch64-linux-gnu to 
loongarch64-linux-gnuf64.


Please consider applying the attached patch and we could continue to 
discuss.


Thanks
Dandan Zhang

diff --git a/debian/patches/gcc-multilib-multiarch.diff b/debian/patches/gcc-multilib-multiarch.diff
index 128d6008a..bd05f757b 100644
--- a/debian/patches/gcc-multilib-multiarch.diff
+++ b/debian/patches/gcc-multilib-multiarch.diff
@@ -119,7 +119,7 @@
  # Only define MULTIARCH_DIRNAME when multiarch is enabled,
  # or it would always introduce ${target} into the search path.
 -MULTIARCH_DIRNAME = $(LA_MULTIARCH_TRIPLET)
-+MULTIARCH_DIRNAME = $(call if_multiarch,loongarch64-linux-gnu)
++MULTIARCH_DIRNAME = $(call if_multiarch,loongarch64-linux-gnuf64)
  endif
  
  # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
@@ -128,7 +128,7 @@
  MULTILIB_OSDIRNAMES = \
 -  mabi.lp64d=../lib64$\
 -  $(call if_multiarch,:loongarch64-linux-gnuf64)
-+  mabi.lp64d=../lib$(call if_multiarch,:loongarch64-linux-gnu)
++  mabi.lp64d=../lib$(call if_multiarch,:loongarch64-linux-gnuf64)
  
  MULTILIB_OSDIRNAMES += \
 -  mabi.lp64f=../lib64/f32$\