Bug#1060540: thinkfan: Please switch Build-Depends to systemd-dev

[Petter Reinholdtsen]

[Michael Biebl]
> your package thinkfan declares a Build-Depends on systemd and/or
> udev.

As far as I can tell, this issue was fixed in version 1.3.1-4.  Perhaps
this issue should be closed before the package is removed from testing?

-- 
Happy hacking
Petter Reinholdtsen

Bug#1043686: Please provide a proper download location for beads

[Andreas Tille]

Hi Filippo,

Am Wed, May 22, 2024 at 09:29:30PM +0200 schrieb Filippo Rusconi:
> On Wednesday, 22 May 2024 07:22:32 CEST you wrote:
> > Hi Filippo,
> > 
> > ping again.  The currently packaged beads is not at the location
> > you wrote.  Please fix the watch file to report latest version.
> > 
> > Thanks a lot
> >Andreas.
> 
> The git commit that seems to fix the bug is located at 
> 
> https://salsa.debian.org/med-team/beads/-/tree/1.1.22-1?ref_type=tags
> 
> To me it looks like it is the HEAD of the master branch.
> 
> Could you confirm this is correct ?

If I run

  uscan --verbose --report

I get

...
$newversion  = 1.1.20
$lastversion = 1.1.22
uscan info: Matching target for downloadurlmangle: 
https://forgemia.inra.fr/pappso/beads/-/archive/1.1.20/beads-1.1.20.tar.gz
uscan info: Upstream URL(+tag) to download is identified as
https://forgemia.inra.fr/pappso/beads/-/archive/1.1.20/beads-1.1.20.tar.gz
uscan info: Filename (filenamemangled) for downloaded file: beads-1.1.20.tar.gz
uscan info: Newest version of beads on remote site is 1.1.20, local version is 
1.1.22
uscan info:  => Only older package available from:
 => 
https://forgemia.inra.fr/pappso/beads/-/archive/1.1.20/beads-1.1.20.tar.gz
uscan info: Scan finished
Exit code:   1 

This was the reason for my mail.

Kind regards
   Andreas.

-- 
https://fam-tille.de

Bug#1071654: screenkey: Enable Salsa-CI

[Otto Kekäläinen]

Package: screenkey
Severity: normal
Tags: patch
X-Debbugs-CC: wav...@thregr.org

This bug report is filed to notify that
https://salsa.debian.org/georgesk/screenkey/-/merge_requests/2.patch is
available.

Personally I would prefer all feedback to be posted at
https://salsa.debian.org/georgesk/screenkey/-/merge_requests/2 as
bugs.debian.org is very inefficient as a code review platform and you
can't see the CI results in the bug report anyway, and this patch is
to improve the CI.
From 79d1281af8236beeb08bdfa17615ecce91b872e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Otto=20Kek=C3=A4l=C3=A4inen?= 
Date: Sat, 3 Jun 2023 16:37:51 -0700
Subject: [PATCH] Enable Salsa-CI

This will help ensure easily machine detectable regressions don't slip
into the code base.

This also makes any future contribution process faster and more
reliable, as any contributor submitting a Merge Request will get
immediate feedback, and the maintainers save time by not having to point
out basic mistakes.
---
 debian/salsa-ci.yml | 9 +
 1 file changed, 9 insertions(+)
 create mode 100644 debian/salsa-ci.yml

diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
new file mode 100644
index 000..3de2c8b
--- /dev/null
+++ b/debian/salsa-ci.yml
@@ -0,0 +1,9 @@
+---
+include:
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+# If Salsa-CI is not running at
+# https://salsa.debian.org/%{project_path}/-/pipelines, ensure that
+# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has in field "CI/CD
+# configuration file" filename "debian/salsa-ci.yml"
-- 
GitLab

Bug#1071653: frr: Debian package is missing pim6d binary

[Scoopta]

Package: frr
Version: 10.0-2
Severity: wishlist

Dear Maintainer,

The pim6d binary is missing in the package however it can still be 
enabled via /etc/frr/daemons. This is a feature request to build and 
ship pim6d in the debian frr package.


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

Kernel: Linux 6.9.1 (SMP w/32 CPU threads; PREEMPT)
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 frr depends on:
ii adduser 3.137
ii iproute2 6.9.0-1
ii libc6 2.38-11
ii libcap2 1:2.66-5
ii libcares2 1.28.1-1
ii libcrypt1 1:4.4.36-4
ii libjson-c5 0.17-1+b1
ii libpam0t64 [libpam0g] 1.5.3-4
ii libprotobuf-c1 1.4.1-1+b2
ii libreadline8t64 8.2-4
ii libunwind8 1.6.2-3+b1
ii libyang2t64 2.1.148-0.1
ii logrotate 3.21.0-2
ii lsof 4.95.0-1.1

Versions of packages frr recommends:
pn frr-pythontools 

Versions of packages frr suggests:
pn frr-doc 

-- Configuration Files:
/etc/frr/daemons [Errno 13] Permission denied: '/etc/frr/daemons'
/etc/frr/frr.conf [Errno 13] Permission denied: '/etc/frr/frr.conf'
/etc/frr/support_bundle_commands.conf [Errno 13] Permission denied: 
'/etc/frr/support_bundle_commands.conf'

/etc/frr/vtysh.conf [Errno 13] Permission denied: '/etc/frr/vtysh.conf'

-- no debconf information




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069210: dh-elpa: Support nested directory in elpa installation

[Xiyue Deng]

I made another change to dh-elpa enabling better back trace for
buttercup tests, so here is the refreshed patchset.  TIA!

-- 
Xiyue Deng

From cc40a88155029834673a944e1a822ff3b97613ca Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Mon, 20 May 2024 00:49:52 -0700
Subject: [PATCH 1/4] Don't recursively add elpa path to match package.el
 behavior

* Add .nosearch to `/usr/share/emacs/site-lisp/elpa{,-src}' using
triggers in dh-elpa, which will disable subdirs.el from processing
those directories.
---
 debian/dh-elpa.postinst | 35 +++
 debian/dh-elpa.triggers |  2 ++
 2 files changed, 37 insertions(+)
 create mode 100644 debian/dh-elpa.postinst
 create mode 100644 debian/dh-elpa.triggers

diff --git a/debian/dh-elpa.postinst b/debian/dh-elpa.postinst
new file mode 100644
index 000..7f2e52d
--- /dev/null
+++ b/debian/dh-elpa.postinst
@@ -0,0 +1,35 @@
+#!/bin/sh
+
+set -e
+
+ensure_nosearch_in_elpa_directories() {
+# Currently there is subdirs.el in `/usr/share/emacs/site-lisp' which causes
+# all subdirectories to be added to `load-path' including elpa installation
+# directories.  This differs from how package.el handles ELPA packages which
+# only adds the installation root directory.  Here we add `.nosearch' to
+# elpa directories to let subdirs.el skip them to follow the package.el
+# behavior.
+SITE_LISP_DIR=/usr/share/emacs/site-lisp
+ELPA_SRC_NOSEARCH=${SITE_LISP_DIR}/elpa-src/.nosearch
+ELPA_NOSEARCH=${SITE_LISP_DIR}/elpa/.nosearch
+[ -f ${ELPA_SRC_NOSEARCH} ] || touch ${ELPA_SRC_NOSEARCH}
+[ -f ${ELPA_NOSEARCH} ] || touch ${ELPA_NOSEARCH}
+}
+
+case "$1" in
+configure)
+;;
+
+triggered)
+ensure_nosearch_in_elpa_directories
+;;
+
+*)
+echo "postinit called with argument \`$1' which is ignored." >&2
+exit 1
+;;
+esac
+
+#DEBHELPER#
+
+exit 0
diff --git a/debian/dh-elpa.triggers b/debian/dh-elpa.triggers
new file mode 100644
index 000..ef84cb6
--- /dev/null
+++ b/debian/dh-elpa.triggers
@@ -0,0 +1,2 @@
+interest /usr/share/emacs/site-lisp/elpa-src
+interest /usr/share/emacs/site-lisp/elpa
-- 
2.39.2

From 111a07a86a3aa163d6e4da51c3e6389516f2b985 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Mon, 15 Apr 2024 13:03:16 -0700
Subject: [PATCH 2/4] Byte compile recursively during install to handle nested
 directories

* This handles addons that have source files under nested directories
in ELPA install directories.
---
 helper/install | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/helper/install b/helper/install
index 39db695..eb68ef5 100755
--- a/helper/install
+++ b/helper/install
@@ -58,7 +58,8 @@ echo "install/${ELPA_DIR}: byte-compiling for ${FLAVOR}"
  ${FLAVOR} --quick --batch -l package \
--eval "(setq package-user-dir \"/nonexistent\")" \
--eval "(add-to-list 'package-directory-list \"$src_dir\")" \
-   -f package-initialize -f batch-byte-compile ./*.el > Install.log 2>&1
+   -f package-initialize \
+   --eval "(byte-recompile-directory \".\" 0)" > Install.log 2>&1
  if test $? -ne 0
  then
cat Install.log
-- 
2.39.2

From 795c82f5c80fc5665905d3763163bef03e8854ca Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 17 Apr 2024 14:06:42 -0700
Subject: [PATCH 3/4] Create symlink from elpa-src to elpa recursively

* Instead of using `ln -s', use `cp -rs' so that directories are
handled recursively.
* In remove we use `rmdir --ignore-fail-on-non-empty' so this was
handled automatically as well.
---
 helper/install | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/helper/install b/helper/install
index eb68ef5..8d748c8 100755
--- a/helper/install
+++ b/helper/install
@@ -50,7 +50,7 @@ echo "install/${ELPA_DIR}: byte-compiling for ${FLAVOR}"
 # policy).  This makes complation easy, and also allows find-function
 # and find-library to work properly.  Also link all other top level
 # files and directories into the flavor directory
-(cd "${elc_dir}" && ln -sf "${el_dir}"* .)
+(cd "${elc_dir}" && cp -rsf "${el_dir}"* .)
 
 # Byte compile them
 (cd "${elc_dir}"
-- 
2.39.2

From 374983204ec273c557306821bfce0cbfb0950722 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 17 Apr 2024 14:17:41 -0700
Subject: [PATCH 4/4] Update d/changelog

---
 debian/changelog | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index be10246..e385f81 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,12 @@ dh-elpa (2.1.2) UNRELEASED; urgency=medium
   * dh_elpa_test: Don't rename files under test/, tests/ (Closes:
 #1069326).
   * Use `pretty' stack frame style in buttercup for full back trace.
+  * Add support for nested directory in elpa installation (Closes:
+#1069210).
+- Don't recursively add elpa path to match package.el behavior.
+- Byte compile recursively during install to handle nested
+  directories.
+- 

Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail

[Don Armstrong]

On Tue, 21 May 2024, Don Armstrong wrote:
> Thanks for the reports; I note that around this time the systems were
> upgraded. It's possible that this finally broke bug mail, which was
> using a totally unsupported out of date version of EOC.

Looking at it, this is definitely a casualty of python2->python3. I'm
working with Liw to get the most-recent version of EoC (2010!) and I'll
do the tweaks to make it work on python3.

Look for me to have it working again this weekend.

-- 
Don Armstrong  https://www.donarmstrong.com

Science is a way of trying not to fool yourself. The first principle
is that you must not fool yourself, and you are the easiest person to
fool.
 -- Richard Feynman "What is and What Should be the Role of Scientific
Culture in Modern Society"; 1964

Bug#1071652: As a matter of fact

[Dan Jacobson]

As a matter of fact, the solution I posted doesn't work either.

Therefore, be sure on the man page, to mention the true sequence needed:

# debootstrap 
(missing step goes here)
# debootstrap --second-stage

Bug#1071652: Man page forgets to mention actual --second-stage usage

[jidanni]

Package: debootstrap
Version: 1.0.128+nmu2+deb12u1

Man page says:
   --second-stage
  Complete  the bootstrapping process.  Other arguments are 
generally not needed.

Well one cannot just run these two in sequence:
SYNOPSIS
   debootstrap [OPTION...]  SUITE TARGET [MIRROR [SCRIPT]]
   debootstrap [OPTION...]  --second-stage

On https://unix.stackexchange.com/a/355197/179494 we see the answer.
Therefore the man page must kindly also mention: "to run the second stage,
chroot to where you've unpacked the archive, and run
/debootstrap/debootstrap --second-stage
"

Bug#1054028: (no subject)

[wuruilong]

Dear Maintainer,

I also verified the patch and it compiles the package successfully, can 
the maintainer merge the patch?


wuruilong

Bug#1066182: (no subject)

[wuruilong]

Dear Maintainer,

Can someone please merge this patch?

wuruilong

Bug#1070673: azure-cli: contains telemetry

[Luca Boccassi]

Control: tags -1 wontfix
Control: close -1

On Mon, 6 May 2024 21:50:40 + "brian m. carlson"
 wrote:
> Source: azure-cli
> Version: 2.50.0-2
> Severity: normal
> 
> The documentation in this package indicates that telemetry collection
is
> on by default, and I don't see any patches that indicate that that
has
> been removed.
> 
> Debian should not ship software that sends telemetry by default
because
> it violates the privacy of users, and it is typically only in the
> interest of the maintainer, not the users.  It's not reasonable to
> expect users to configure every package they might install separately
> not to send telemetry, since that's impractical and it's nearly
> impossible to configure every piece of software to do so, especially
in
> environments like containers where users' settings are often not
> persisted.
> 
> Please remove the telemetry functionality from the package or ensure
> that it is rendered completely nonfunctional, and add a note to the
> README.Debian indicating this change so that users can feel more
> confident in using the package.

The entire and sole purpose of this package is to interact with a
public cloud, using your account and your internet connection. If you
are afraid of some unspecified telemetry, you really should not be
using a public cloud in the first place.

-- 
Kind regards,
Luca Boccassi


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

Bug#1071651: debootstrap --print-debs jumbled output

[jidanni]

Package: debootstrap
Version: 1.0.128+nmu2+deb12u1
Severity: minor

With --print-debs first there are packages on single lines. Then,
without even a newline, comes one long line of packages.
$ sudo debootstrap --print-debs sid /home/sid-chroot 
http://opensource.nchc.org.tw/debian/
...
tzdata
usr-is-merged
util-linux
zlib1g adduser apt-utils cpio cron cron-daemon-common...

P.S., on the bottom of the man page is a twenty-year old date...

Bug#1069125: zfs-dkms: Update stable version to fix data corruption bug

[Jacob Kauffmann]

Hi,

While checking this again (as I've also been awaiting a fix), I noticed that in 
addition to having version 2.2.3-2 packaged in bookworm-backports, a patch set 
containing the fix was also pushed to the bookworm branch on top of the 
released 2.1.11 version: ff4499f12efeb0d48899c686b26450bb060abbf0 

However, that commit-- which states that it closes #1056752, which was actually 
archived without a resolution in Debian stable-- has not been released yet, 
either. This seems like a policy issue rather than an issue of doing the work, 
since packages for newer upstream versions and a patched downstream version 
exist on Debian Salsa. Is there a reason why none of these can be moved forward?

This bug was seen as fairly low-priority on most real-world systems partially 
because it didn't affect most 8.x (and older) versions of coreutils, but Debian 
stable does contain coreutils 9.1.

- Jacob Kauffmann

Bug#940960: ITP: linenoise -- Minimal replacement for readline

[Blair Noctis]

On 2024-05-05 07:33, Maytham Alsudany wrote:
Hi, Any progress on getting linenoise packaged? This is urgently 
needed to devendor linenoise in the redict package (a new fork of 
redis). If you've lost interest, I'm happy to take over this ITP. Kind 
regards, Maytham 


Hi, sorry for the delay. Please feel free to take over.

--
Sdrager,
Blair Noctis

Bug#1071650: Please provide new upstream version 3.0.0

[Matthias Geiger]

Package: gtklock
Severity: wishlist
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Maytham,

thanks for maintaining gtklock. Please consider pacakging the new 3.0
upstream release.

best,

werdahias


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

Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

Versions of packages gtklock depends on:
ii  libc62.38-11
ii  libglib2.0-0t64  2.80.2-1
ii  libgtk-3-0t643.24.41-4
pn  libgtk-layer-shell0  
ii  libpam0g 1.5.3-7
ii  libwayland-client0   1.22.0-2.1+b1

gtklock recommends no packages.

gtklock suggests no packages.

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmZOfVMVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1MX4QAK/68+1E8v/hZSXfWrj6amYrVksD
nE67SLPqfXx7IZXBHTSwYv0VBSHJOlRABK8yVXJcGj1qhA/QTydZ4FQlWMebmKuV
C4a3sMMF3OnFU9Nyw60B45B6EoR7GxUQWji49S5765qjxZ4+EDTpw9l5eMkhC4Be
DbHM9TI7aUT1LWXz+zUZWJSPZwJjET2EnW0js9M+x4S3IITngQZN//qJu0m6nY7j
N8EeLAsizct6el60qLR0Tc2Xe7cQfITVVZKTngrmlXVQpEJmsvFstGu4RmhPU+O+
m3AKFkYWrG4ZweiJjLMskfQFWKEUVK2i3j1ljB7o0SNh+MM4LdeCequACvPZPK2q
lXgADQUROocnIbKu1iTz3z+tlQy9C+ThuB81lTpEhEg6YI1LFih/6GaTy0UtxJrY
mO5TGegjAv9Hf9WliClqUnDK8p9ZXieht40KtFxPjL0aNRrhGXV4tG/N7UMvE1NS
fWx4gx9z3k7hhwPYtVeHX4k/T9FHAlAe9jOtFAmLPaSoEPNqiiZAFGIvPz/ij2vb
mi75wfzZ+KaOekwsNYuC7tstOfoM8pTT0ixS/o8LaxObXhgvLV2XR5asIfayJI6f
j/72gX4LNeQPbcIYaLMQW/RPezeE4QhyIaQnMEsznAG3t928Gx2+Z5Hju/QUP4oc
Sv3+d4RB0FwKz1Pa
=xlVl
-END PGP SIGNATURE-

Bug#1071648: FTBFS with Linux 6.8+

[Tianon Gravi]

On Wed, 22 May 2024 at 16:09, Tianon Gravi  wrote:
> The recent upload of src:linux to 6.8+ (specifically 6.8.9-1,
> ironicially uploaded around the same time as the last busybox upload)
> causes src:busybox to FTBFS (logs from reproducible-builds):
>
> ...
>
> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/busybox_1.36.1-7.rbuild.log.gz

Full build log now attached (apologies for not including it in the
original submission).

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


busybox_1.36.1-7.rbuild.log.gz
Description: application/gzip

Bug#1071649: mflua.1: some remarks and editorial changes for this man page

[Bjarni Ingi Gislason]

Package: texlive-binaries
Version: 2023.20230311.66589-9+b2
Severity: minor
Tags: patch

Dear Maintainer,

  here are some notes and editorial fixes for the manual.

The patch is in the attachment.

-.-

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "

instead of "nroff -man"

  Add the option "-t", if the file contains a table.

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual for warnings,
the following must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint mflua.1": (possibly shortened list)

mandoc: mflua.1:4:145: STYLE: input text line longer than 80 bytes: mflua, 
mflua-nowin, ...

-.-.

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

7:[\fI\,OPTION\/\fR]... [\fI\,MFNAME\/\fR[\fI\,.mf\/\fR]] [\fI\,COMMANDS\/\fR]
10:[\fI\,OPTION\/\fR]... \fI\,\FIRST-LINE\/\fR
13:[\fI\,OPTION\/\fR]... \fI\, ARGS\/\fR
28:next word is taken as the BASE to read, overriding all else. Any
69:Copyright 2020 L. Scarso.
78:Primary author of MFLua: L. Scarso.

-.-.

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

mflua.1: line 2 length 83
.TH MFLUA "1" "September 2020" "MFLua Metafont integrated with Lua" "User 
Commands"

mflua.1: line 4 length 145
mflua, mflua-nowin, mfluajit, mfluajit-nowin \- implementation of META-FONT 
with Lua embedded for better extraction of information from METAFONT.

mflua.1: line 33 length 81
\fB\-base\fR=\fI\,BASENAME\/\fR use BASENAME instead of program name or a %& 
line

mflua.1: line 39 length 95
\fB\-ini\fR be inimf, for dumping bases; this is implicitly true if the program 
name is `inimf'

mflua.1: line 41 length 113
\fB\-interaction\fR=\fI\,STRING\/\fR set interaction mode 
(STRING=batchmode/nonstopmode/scrollmode/errorstopmode)

mflua.1: line 45 length 108
\fB\-kpathsea\-debug\fR=\fI\,NUMBER\/\fR  set path searching debugging flags 
according to the bits of NUMBER

mflua.1: line 49 length 93
\fB\-output\-directory\fR=\fI\,DIR\/\fR   use existing DIR as the directory to 
write files in

mflua.1: line 51 length 83
\fB[\-no]\-parse\-first\-line\fR disable/enable parsing of first line of input 
file

-.-.

Protect a period (.) or an apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line
(by splitting the line into more lines).

20:If the first line of MFNAME is %, and BASE is an existing .base file,

-.-.

Start a sentence in parenthesis on a new line.

mflua.1:40:\fB\-interaction\fR=\fI\,STRING\/\fR set interaction mode 
(STRING=batchmode/nonstopmode/scrollmode/errorstopmode)

-.-.

Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z -K utf8":
troff: backtrace: file '':10
troff::10: error: no font family named 'I' exists



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

Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages texlive-binaries depends on:
ii  libc62.38-11
ii  libcairo21.18.0-3+b1
ii  libfontconfig1   2.15.0-1.1
ii  libfreetype6 2.13.2+dfsg-1+b4
ii  libgcc-s114-20240330-1
ii  libgraphite2-3   1.3.14-2
ii  libharfbuzz0b8.3.0-2+b1
ii  libicu72 72.1-4+b1
ii  libkpathsea6 2023.20230311.66589-9+b2
ii  libmpfr6 4.2.1-1+b1
ii  libpaper11.1.29+b1
ii  libpixman-1-00.42.2-1+b1
ii  libpng16-16t64   1.6.43-5
ii  libpotrace0  1.16-2+b1
ii  libptexenc1  2023.20230311.66589-9+b2
ii  libstdc++6   14-20240330-1
ii  libsynctex2  2023.20230311.66589-9+b2
ii  libteckit0   2.5.12+ds1-1
ii  libtexlua53-52023.20230311.66589-9+b2
ii  

Bug#1071648: FTBFS with Linux 6.8+

[Tianon Gravi]

Source: busybox
Version: 1:1.36.1-7
Severity: serious
Tags: ftbfs upstream
X-Debbugs-Cc: tia...@debian.org

The recent upload of src:linux to 6.8+ (specifically 6.8.9-1,
ironicially uploaded around the same time as the last busybox upload)
causes src:busybox to FTBFS (logs from reproducible-builds):

| /build/reproducible-path/busybox-1.36.1/networking/tc.c: In function 
'cbq_print_opt':
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:237:27: error: 
'TCA_CBQ_MAX' undeclared (first use in this function); did you mean 
'TCA_CBS_MAX'?
|   237 | struct rtattr *tb[TCA_CBQ_MAX+1];
|   |   ^~~
|   |   TCA_CBS_MAX
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:237:27: note: each 
undeclared identifier is reported only once for each function it appears in
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:250:16: error: 
'TCA_CBQ_RATE' undeclared (first use in this function); did you mean 
'TCA_TBF_RATE64'?
|   250 | if (tb[TCA_CBQ_RATE]) {
|   |^~~~
|   |TCA_TBF_RATE64
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:256:16: error: 
'TCA_CBQ_LSSOPT' undeclared (first use in this function)
|   256 | if (tb[TCA_CBQ_LSSOPT]) {
|   |^~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:257:61: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_lssopt'
|   257 | if (RTA_PAYLOAD(tb[TCA_CBQ_LSSOPT]) < sizeof(*lss))
|   | ^
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:262:16: error: 
'TCA_CBQ_WRROPT' undeclared (first use in this function)
|   262 | if (tb[TCA_CBQ_WRROPT]) {
|   |^~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:263:61: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_wrropt'
|   263 | if (RTA_PAYLOAD(tb[TCA_CBQ_WRROPT]) < sizeof(*wrr))
|   | ^
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:268:16: error: 
'TCA_CBQ_FOPT' undeclared (first use in this function)
|   268 | if (tb[TCA_CBQ_FOPT]) {
|   |^~~~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:269:59: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_fopt'
|   269 | if (RTA_PAYLOAD(tb[TCA_CBQ_FOPT]) < sizeof(*fopt))
|   |   ^

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/busybox_1.36.1-7.rbuild.log.gz

This has been reported upstream[1][2] (back in January), but with no
upstream resolution yet.

[1]: https://bugs.busybox.net/show_bug.cgi?id=15931
[2]: https://bugs.busybox.net/show_bug.cgi?id=15934


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

Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash

Bug#1071563: emacs: Don't let test suite failures block the build

[Sean Whitton]

Hello,

On Tue 21 May 2024 at 11:20am +01, Sean Whitton wrote:

> Source: emacs
> Version: 1:29.3+1-3
>
> Hello,
>
> I propose that we make test suite failures non-fatal to the build.
>
> The test suite has got quite flaky in recent years, and uploading Emacs
> often requires issuing several giveback requests for random failures.
>
> Patching individual tests to mark them as flaky does not scale.

I think we should move the tests to run under autopkgtest, rather than
during the build.  Debian's autopkgtest infrastructure, with things like
blocking migration, is by now quite sophisticated.

On IRC it's also been suggested that we also

- mark dired-test-bug27243-02 as flaky (thanks Arto Jantunen); and

- in the new autopkgtest, don't run the tests in parallel.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1071647: mendex.1: some remarks and editorial changes for this man page

[Bjarni Ingi Gislason]

Package: texlive-binaries
Version: 2023.20230311.66589-9+b2
Severity: minor
Tags: patch

Dear Maintainer,

  here are some notes and editorial fixes for the manual.

The patch is in the attachment.

-.-

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "

instead of "nroff -man"

  Add the option "-t", if the file contains a table.

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual for warnings,
the following must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint mendex.1": (possibly shortened list)

mandoc: mendex.1:1:2: WARNING: missing date, using "": TH
mandoc: mendex.1:14:2: WARNING: skipping paragraph macro: PP after SH
mandoc: mendex.1:20:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:23:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:26:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:78:99: STYLE: input text line longer than 80 bytes: (the next 
odd page t...
mandoc: mendex.1:259:87: STYLE: input text line longer than 80 bytes: Same as 
\fBlethead_f...
mandoc: mendex.1:350:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:360:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:369:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:434:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:470:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:472:2: WARNING: skipping paragraph macro: PP after SH
mandoc: mendex.1:476:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:482:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:482:2: WARNING: skipping paragraph macro: br before sp
mandoc: mendex.1:499:87: STYLE: input text line longer than 80 bytes: The 
delimiter betwee...
mandoc: mendex.1:500:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:515:85: STYLE: input text line longer than 80 bytes: Though 
some kanji wo...
mandoc: mendex.1:516:146: STYLE: input text line longer than 80 bytes: (ex. 
\[u300C]\[u3072...
mandoc: mendex.1:518:132: STYLE: input text line longer than 80 bytes: in kana 
expression (...
mandoc: mendex.1:519:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:521:81: STYLE: input text line longer than 80 bytes: by 
setting the file ...
mandoc: mendex.1:524:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:526:2: WARNING: skipping paragraph macro: PP after SH
mandoc: mendex.1:530:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:531:84: STYLE: input text line longer than 80 bytes: Even when 
sort by ch...
mandoc: mendex.1:533:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:551:2: ERROR: skipping end of block that is not open: RE
mandoc: mendex.1:561:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:564:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:577:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:580:2: WARNING: skipping paragraph macro: PP empty
mandoc: mendex.1:585:2: WARNING: skipping paragraph macro: PP empty

-.-.

Change two HYPHEN-MINUSES (code 0x2D) to an em-dash (\(em),
if one is intended.  An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.
"man" (1 byte characters in input) transforms an en-dash (\(en) to one
HYPHEN-MINUS,
and an em-dash to two HYPHEN-MINUSES without considering the space
around it.
If "--" are two single "-" (end of options) then use "\-\-".

mendex.1:12:\fBmendex\fR [-ilqrcgfEJSU] [\fB-s\fI sty\fR] [\fB-d\fI dic\fR] 
[\fB-o\fI ind\fR] [\fB-t\fI log\fR] [\fB-p\fI no\fR] [\fB-I\fI enc\fR] 
[\fB--help\fR] [\fB--\fR] [\fI idx0 idx1 idx2 ...\fR]
mendex.1:97:\fB--help\fR
mendex.1:100:\fB--\fR
mendex.1:101:Arguments after \fB--\fR are not taken as options.
mendex.1:332:"--"

-.-.

Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.

When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.

This marking is robust, and independent of the position on the line.

It corresponds to "\ " in TeX, and to "@:" in Texinfo.


42:(e.g. 1\(en5).
515:Though some kanji words (ex. 「表」) may have more than one Yomi\'s
516:(ex. 「ひょう」 and 「おもて」), only one of them can be 
registered in the dictionary.
518:in kana expression (ex. 

Bug#1071646: shotcut: Any option for packaging Glaxnimate with Shotcut?

[david]

Package: shotcut
Version: 24.04.28+ds-1
Severity: wishlist

Dear Maintainer,

Tar package of Shotcut from home web includes the application Glaxnimate,
a vector animation sorftware that integrates well with Shotcut. Perhaps it can
be packaged with it or in another package?

Thank you.

-- 
David

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 shotcut depends on:
ii  frei0r-plugins   1.8.0-1+b2
ii  libc62.38-11
ii  libfftw3-double3 3.3.10-1+b2
ii  libgcc-s114-20240330-1
ii  libjs-three  111+dfsg1-3
ii  libmlt++77.24.0-1
ii  libmlt7  7.24.0-1
ii  libqt6charts66.4.2-5+b2
ii  libqt6core6t64   6.4.2+dfsg-21.1+b1
ii  libqt6gui6t646.4.2+dfsg-21.1+b1
ii  libqt6multimedia66.4.2-11+b2
ii  libqt6network6t646.4.2+dfsg-21.1+b1
ii  libqt6opengl6t64 6.4.2+dfsg-21.1+b1
ii  libqt6qml6   6.4.2+dfsg-4+b2
ii  libqt6quick6 6.4.2+dfsg-4+b2
ii  libqt6quickcontrols2-6   6.4.2+dfsg-4+b2
ii  libqt6quickwidgets6  6.4.2+dfsg-4+b2
ii  libqt6sql6t646.4.2+dfsg-21.1+b1
ii  libqt6widgets6t646.4.2+dfsg-21.1+b1
ii  libqt6xml6t646.4.2+dfsg-21.1+b1
ii  libstdc++6   14-20240330-1
ii  melt 7.24.0-1
ii  qml6-module-qt-labs-animation6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-folderlistmodel  6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-lottieqt 6.4.2-3+b2
ii  qml6-module-qt-labs-platform 6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-qmlmodels6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-settings 6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-sharedimage  6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-wavefrontmesh6.4.2+dfsg-4+b2
ii  qml6-module-qtcore   6.4.2+dfsg-4+b2
ii  qml6-module-qtqml6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-models 6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-statemachine   6.4.2-4+b2
ii  qml6-module-qtqml-workerscript   6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-xmllistmodel   6.4.2+dfsg-4+b2
ii  qml6-module-qtquick  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-controls 6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-dialogs  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-layouts  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-localstorage 6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-nativestyle  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-particles6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-shapes   6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-templates6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-timeline 6.4.2-2+b2
ii  qml6-module-qtquick-tooling  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-virtualkeyboard  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-window   6.4.2+dfsg-4+b2
ii  shotcut-data 24.04.28+ds-1

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information

Bug#1059857: discrepancy between upstream and downstream .service files

[Luca Boccassi]

On Tue, 2 Jan 2024 18:49:59 +0100 Chris Hofstaedtler 
wrote:
> Hi!
> 
> On Tue, Jan 02, 2024 at 02:19:39PM +0100, Michael Biebl wrote:
> > today I wanted to enable the iSCSI test in systemd:
> >
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/test/TEST-64-UDEV-STORAGE/test.sh?ref_type=heads#L29-34
> > 
> > For that I added test dependency on open-iscsi and tgt.
> > Unfortunately, this failed:
> > ```
> > W: Failed to install '/usr/lib/systemd/system/iscsi-init.service'
> > I: Skipping program /usr/lib/systemd/system/iscsi-init.service as
it cannot be found and is flagged to be optional
> > W: Failed to install '/usr/lib/systemd/system/iscsi-onboot.service'
> > I: Skipping program /usr/lib/systemd/system/iscsi-onboot.service as
it cannot be found and is flagged to be optional
> > W: Failed to install '/usr/lib/systemd/system/iscsi-
shutdown.service'
> > I: Skipping program /usr/lib/systemd/system/iscsi-shutdown.service
as it cannot be found and is flagged to be optional
> > W: Failed to install '/usr/lib/systemd/system/iscsi.service'
> > F: Failed to install /usr/lib/systemd/system/iscsi.service
> > make: Leaving directory '/tmp/autopkgtest.yvEXDQ/build.n6X/real-
tree/test/TEST-64-UDEV-STORAGE'
> > [13:12:37] --x-- Result of TEST-64-UDEV-STORAGE: 2 --x--
> > ```
> > 
> > I notice that the Debian open-iscsi package ships custom service
files
> > with a custom naming:
> [..]
> > 
> > Would it be possible to use the upstream service files or at least
align
> > the names?
> 
> As noted briefly on IRC, TTBOMK each distro has its own service
> files, and upstream has yet another set of them. The names referend
> in your systemd test output look Fedora-specific to me.
> 
> IMO these things would be interesting to consider (in any order):
> *) teach systemd tests about the Debian/Ubuntu setup
> *) try to converge more towards the upstream set, if that one is
> actually complete.

Note that you don't need to rename them, just add aliases - assuming
they provide similar enough functionality of course.

-- 
Kind regards,
Luca Boccassi


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

Bug#1071645: Text: Rich option is not available in Shotcut Debian package

[david]

Package: shotcut
Version: 24.04.28+ds-1
Severity: normal

Dear Maintainer,

Shotcut has two filters for including text in a video: Simple and Rich. For
some reason, the second option is not available in Debian. I don't know why,
but I asume that this is an error, compile omision or something else.

If I download compiled tar package from Shotcut web, the missed option is
available.

Thank you.

-- 
David

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 shotcut depends on:
ii  frei0r-plugins   1.8.0-1+b2
ii  libc62.38-11
ii  libfftw3-double3 3.3.10-1+b2
ii  libgcc-s114-20240330-1
ii  libjs-three  111+dfsg1-3
ii  libmlt++77.24.0-1
ii  libmlt7  7.24.0-1
ii  libqt6charts66.4.2-5+b2
ii  libqt6core6t64   6.4.2+dfsg-21.1+b1
ii  libqt6gui6t646.4.2+dfsg-21.1+b1
ii  libqt6multimedia66.4.2-11+b2
ii  libqt6network6t646.4.2+dfsg-21.1+b1
ii  libqt6opengl6t64 6.4.2+dfsg-21.1+b1
ii  libqt6qml6   6.4.2+dfsg-4+b2
ii  libqt6quick6 6.4.2+dfsg-4+b2
ii  libqt6quickcontrols2-6   6.4.2+dfsg-4+b2
ii  libqt6quickwidgets6  6.4.2+dfsg-4+b2
ii  libqt6sql6t646.4.2+dfsg-21.1+b1
ii  libqt6widgets6t646.4.2+dfsg-21.1+b1
ii  libqt6xml6t646.4.2+dfsg-21.1+b1
ii  libstdc++6   14-20240330-1
ii  melt 7.24.0-1
ii  qml6-module-qt-labs-animation6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-folderlistmodel  6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-lottieqt 6.4.2-3+b2
ii  qml6-module-qt-labs-platform 6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-qmlmodels6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-settings 6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-sharedimage  6.4.2+dfsg-4+b2
ii  qml6-module-qt-labs-wavefrontmesh6.4.2+dfsg-4+b2
ii  qml6-module-qtcore   6.4.2+dfsg-4+b2
ii  qml6-module-qtqml6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-models 6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-statemachine   6.4.2-4+b2
ii  qml6-module-qtqml-workerscript   6.4.2+dfsg-4+b2
ii  qml6-module-qtqml-xmllistmodel   6.4.2+dfsg-4+b2
ii  qml6-module-qtquick  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-controls 6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-dialogs  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-layouts  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-localstorage 6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-nativestyle  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-particles6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-shapes   6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-templates6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-timeline 6.4.2-2+b2
ii  qml6-module-qtquick-tooling  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-virtualkeyboard  6.4.2+dfsg-4+b2
ii  qml6-module-qtquick-window   6.4.2+dfsg-4+b2
ii  shotcut-data 24.04.28+ds-1

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information

Bug#1071644: Thumbnails of wallpapers missing due to incompatible python3-pil version

[Nils Kanning]

Package: hydrapaper
Version: 3.3.1-2

Hi,

in HydraPaper 3.3.1-2 running on Debian testing/trixie, the thumbnails
of wallpapers are not displayed and I get the following error:

AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
Exception in thread Thread-19 (af):
Traceback (most recent call last):
  File "/usr/lib/python3.11/threading.py", line 1045, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.11/threading.py", line 982, in run
self._target(*self._args, **self._kwargs)
  File
"/usr/lib/python3/dist-packages/hydrapaper/wallpaper_flowbox_item.py",
line 114, in af
self.make_wallpaper_thumb(self.cache_path)
  File
"/usr/lib/python3/dist-packages/hydrapaper/wallpaper_flowbox_item.py",
line 150, in make_wallpaper_thumb
thumb.thumbnail((250, 250), Image.ANTIALIAS)

The problem appears to be that Image.ANTIALIAS was removed from
python3-pil starting at version 10.0.0 as mentioned in
https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#constants.
I am using python3-pil 10.3.0-2, the version currently in trixie.

There is the new HydraPaper release 3.3.2 available upstream, which
seems to fix this issue via
https://gitlab.gnome.org/GabMus/HydraPaper/-/commit/780a7a8cba48219e1226b773d426bb8fcad8a1ce.
Would it be possible to update the Debian package to this version?

Best regards,
Nils

Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev

[Adrian Bunk]

Source: horizon-eda
Version: 2.6.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=horizon-eda=2.6.0-2

...
Has header "zmq.hpp" : NO 

../meson.build:46:8: ERROR: Problem encountered: cppzmq not found



I haven't checked whether this is the only missing build dependency.

BTW:
The build dependency on libzmq5 looks wrong and is already covered
by the build dependency on libzmq3-dev, please remove libzmq5 since
this will break with the next soname change of libzmq.

Bug#1067023: ITP: vaultwarden -- Bitwarden compatible server written in Rust

[Bernhard Dick]

Hi,

currently I'm working on getting the rust libraries from the dependency 
tree from vaultwarden into Debian. This is a requirement to build the 
final binary "the Debian way".
Help on that side would be very much appreciated as there is a high 
amount of packages needed. So please let me know if you want to build 
part of that tree.
Problems with the approach in the referenced buildspecs are now already 
answered by the maintainer within the issue you mentioned.


  Best Regards,
Bernhard

Bug#995514: O: lua-lpeg -- LPeg library for the Lua language

[Alexandre Detiste]

I just cannot get this to work.

Bug#1071082: NMU pushed to DELAYED/10

[Pierre Gruet]

Dear Maintainer,

I have just uploaded fixes for bugs 1048703 and 1071082 to DELAYED/10.
This is to prevent testing autoremoval of plm on June, 11th.

Enclosed is the source debdiff of this NMU. It is strictly based upon 
the patches I submitted in the two bug logs.


Please tell me if I should delay or cancel the foreseen NMU.

Best wishes,

--
Pierre
diff -Nru plm-2.9.2/debian/changelog plm-2.9.2/debian/changelog
--- plm-2.9.2/debian/changelog	2020-10-11 21:54:58.0 +0200
+++ plm-2.9.2/debian/changelog	2024-05-22 21:50:25.0 +0200
@@ -1,3 +1,11 @@
+plm (2.9.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Solving FTBFS against jgit/6.7.0 (Closes: #1071082)
+  * Allowing source package to be built twice in a row (Closes: #1048703)
+
+ -- Pierre Gruet   Wed, 22 May 2024 21:50:25 +0200
+
 plm (2.9.2-1) unstable; urgency=medium
 
   * New upstream release: The Portuguese release (new complete translation)
diff -Nru plm-2.9.2/debian/control plm-2.9.2/debian/control
--- plm-2.9.2/debian/control	2020-10-11 21:54:58.0 +0200
+++ plm-2.9.2/debian/control	2024-05-22 21:49:05.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Martin Quinson 
 Build-Depends: debhelper-compat (= 12), javahelper (>= 0.32), ant, quilt
 Build-Depends-Indep: default-jdk, scala, libmiglayout-java, librsyntaxtextarea-java,
-  junit4, libgettext-commons-java, libjson-simple-java, libhttpclient-java, libhttpmime-java, libjgit-java,
+  junit4, libgettext-commons-java, libjson-simple-java, libhttpclient-java, libhttpmime-java, libjgit-java (>= 6.7.0),
   jython, libgettext-ant-tasks-java, imagemagick,
   libmockito-java
 Standards-Version: 4.5.0
diff -Nru plm-2.9.2/debian/patches/jgit_6.7.0.patch plm-2.9.2/debian/patches/jgit_6.7.0.patch
--- plm-2.9.2/debian/patches/jgit_6.7.0.patch	1970-01-01 01:00:00.0 +0100
+++ plm-2.9.2/debian/patches/jgit_6.7.0.patch	2024-05-22 21:50:16.0 +0200
@@ -0,0 +1,26 @@
+Description: replacing methods removed in jgit 6.7.0
+ The method getRef in Repository had been deprecated in previous versions, and
+ is now removed.
+Author: Pierre Gruet 
+Forwarded: no
+Last-Update: 2024-05-03
+
+--- a/src/plm/core/model/tracking/GitUtils.java
 b/src/plm/core/model/tracking/GitUtils.java
+@@ -126,7 +126,7 @@
+ 	
+ 	public void mergeRemoteIntoLocalBranch(String userBranchHash) throws Exception {
+ 		try {
+-			MergeResult res = git.merge().setCommit(true).setFastForward(MergeCommand.FastForwardMode.FF).setStrategy(MergeStrategy.RECURSIVE).include(git.getRepository().getRef("refs/remotes/origin/"+userBranchHash)).call();
++			MergeResult res = git.merge().setCommit(true).setFastForward(MergeCommand.FastForwardMode.FF).setStrategy(MergeStrategy.RECURSIVE).include(git.getRepository().findRef("refs/remotes/origin/"+userBranchHash)).call();
+ 			
+ 			if(res.getMergeStatus() == MergeResult.MergeStatus.FAST_FORWARD) {
+ System.out.println(Game.i18n.tr("last session data successfully retrieved"));
+@@ -376,6 +376,6 @@
+ 	}
+ 	
+ 	public Ref getRepoRef(String branch) throws IOException {
+-		return git.getRepository().getRef(branch);
++		return git.getRepository().findRef(branch);
+ 	}
+ }
diff -Nru plm-2.9.2/debian/patches/series plm-2.9.2/debian/patches/series
--- plm-2.9.2/debian/patches/series	2020-10-11 21:54:58.0 +0200
+++ plm-2.9.2/debian/patches/series	2024-05-22 21:49:40.0 +0200
@@ -3,4 +3,4 @@
 no-github
 jython-fixes
 json-simple-3.patch
-
+jgit_6.7.0.patch
diff -Nru plm-2.9.2/debian/rules plm-2.9.2/debian/rules
--- plm-2.9.2/debian/rules	2020-10-11 21:54:58.0 +0200
+++ plm-2.9.2/debian/rules	2024-05-22 21:48:32.0 +0200
@@ -26,11 +26,28 @@
 %:
 	dh $@   --with javahelper
 
+execute_before_dh_auto_configure:
+	# Making backups of files that will be altered during the build
+	for F in $$(find l10n/engine -name "*.po" -o -name "*.pot") lib/resources/plm.configuration.properties; do \
+	cp $$F $${F}.save ;\
+	done
+
 override_dh_auto_clean:
 	dh_auto_clean
 	find . -type f -name \*.java.json-simple \
 	  -exec sh -c 'file={} && mv $$file $${file%.json-simple}' \; -print
 
+override_dh_clean:
+	dh_clean
+	# Removing files left there by the build system.
+	find . -name "*.jar" -delete
+	-rm dist/*.tar.bz2
+	-rm errors-*.txt
+	# Restoring files that were altered during the build
+	for F in $$(find . -name "*.save") ; do \
+	mv $$F $${F%.save} ;\
+	done
+
 override_dh_auto_build:
 	find . -type f -name \*.java -exec grep -q 'import @JSON_SIMPLE_PACKAGE@' {} \; \
 	  -exec sed -i.json-simple \


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#996202: EFI Secure Boot for systemd-boot

[Luca Boccassi]

On Fri, 10 May 2024 at 15:51, Luca Boccassi  wrote:
>
> On Fri, 10 May 2024 at 15:49, Steve McIntyre  wrote:
> >
> > On Fri, May 10, 2024 at 03:44:35PM +0100, Luca Boccassi wrote:
> > >On Fri, 10 May 2024 at 15:36, Steve McIntyre  wrote:
> > >> On Fri, May 10, 2024 at 04:29:00PM +0200, Ansgar  wrote:
> > >>
> > >> >Maybe we should use a non-trusted cert for the initial setup and only
> > >> >switch to a proper cert once everything is confirmed to be working as
> > >> >expected?
> > >>
> > >> Hmmm, maybe? Luca?
> > >
> > >What do you mean precisely here? A DSA-managed cert used by FTP to
> > >sign but that doesn't chain to the Debian CA? Or to do something
> > >completely local to the systemd-boot package?
> >
> > Exactly the former - we can use a test key for signing systemd-boot to
> > start with. Once we're happy all round, we can switch to a cert in the
> > chain.
> >
> > >I am fine with any approach that lets us move forward, if that needs
> > >to be some intermediate testing stage that's fine by me.
> >
> > Cool.
>
> Ok, sounds good to me, thanks.
>
> DSA, now that FTP Team has acked with this suggestion to use a test
> cert first, are you happy to proceed or is there anything else you
> need from me? Thanks!

As suggested by DSA, I filed a ticket on RT about this:

https://rt.debian.org/Ticket/Display.html?id=9506

Bug#1070770: lintian: check for testing presence of "nodocs" in DEB_BUILD_OPTIONS

[Nilesh Patra]

Hi Julian!

On Sun, May 19, 2024 at 01:48:17PM +0100, Julian Gilbey wrote:
> But here I'd suggest doing the
> opposite: checking for valid build options (and note: this is a check
> for DEB_BUILD_OPTIONS, not for DEB_BUILD_PROFILES).  There is a very
> short list of standard build options: those listed in
> dpkg-buildpackage(1) (parallel=n, nocheck, noopt, nostrip, terse,
> hardening=..., reproducible=..., abi=..., future=..., qa=...,
> optimize=..., sanitize=...) and
> https://wiki.debian.org/BuildProfileSpec: nodoc

I concur. Thanks also to Andrius for +1. If Pollo/Andrius would like to work on
it and/or open a MR, I will be happy to review (and merge).

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1071596: apache2: envvars evaluates string in conditional instead of testing for empty string

[Mark Hedges]

Weird.  I'll have to reinstall apache2.  Maybe I edited it long ago to
debug it, forgot a space, and it got stuck by debconf picking my
version on upgrades instead of the package maintainer's.  Thanks.


On Wed, May 22, 2024 at 12:38 PM Stefan Fritsch  wrote:
>
> Hi Mark,
>
> Am 21.05.24 um 22:30 schrieb Mark Hedges:
> > Package: apache2
> > Version: 2.4.59-1~deb12u1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > `envvars` evaluates string in conditional instead of testing for empty 
> > string.
> >
> > `apachectl` calls `envvars` which shows a syntax error despite working:
> >
> >   root@nodeo:/etc/letsencrypt# apachectl configtest
> >   /usr/sbin/apachectl: 6: [: /etc/apache2: unexpected operator
> >   Syntax OK
> >
> > If I change this line in `envvars`:
> >
> >   if [ "${APACHE_CONFDIR}" == "" ]; then
> >export APACHE_CONFDIR=/etc/apache2
> >   fi
>
> This snippet is not in the original file from the apache2 package.
> Compare to
> https://salsa.debian.org/apache-team/apache2/-/blob/master/debian/config-dir/envvars?ref_type=heads
>
> Either you or some package or script has changed the file. If you have
> etckeeper you could dig in the logs.
>
> Cheers,
> Stefan
>
> >
> > to this:
> >
> >   if [ -z ${APACHE_CONFDIR} ]; then
> >export APACHE_CONFDIR=/etc/apache2
> >   fi
> >
> > ... then it works.
> >
> > It's trying to evaluate `/etc/apache2` as a command?  Weird.
> >
> > PATH seems totally normal.
> >
> > Mark
> >
> > -- Package-specific info:
> >
> > -- System Information:
> > Debian Release: 12.5
> >APT prefers stable-updates
> >APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> > 'stable')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 6.1.0-21-amd64 (SMP w/1 CPU thread; PREEMPT)
> > 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 apache2 depends on:
> > ii  apache2-bin2.4.59-1~deb12u1
> > ii  apache2-data   2.4.59-1~deb12u1
> > ii  apache2-utils  2.4.59-1~deb12u1
> > ii  init-system-helpers1.65.2
> > ii  lsb-base   11.6
> > ii  media-types10.0.0
> > ii  perl   5.36.0-7+deb12u1
> > ii  procps 2:4.0.2-3
> > ii  sysvinit-utils [lsb-base]  3.06-4
> >
> > Versions of packages apache2 recommends:
> > ii  ssl-cert  1.1.2
> >
> > Versions of packages apache2 suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  chromium [www-browser]   125.0.6422.60-1~deb12u1
> >
> > Versions of packages apache2-bin depends on:
> > ii  libapr1  1.7.2-3
> > ii  libaprutil1  1.6.3-1
> > ii  libaprutil1-dbd-sqlite3  1.6.3-1
> > ii  libaprutil1-ldap 1.6.3-1
> > ii  libbrotli1   1.0.9-2+b6
> > ii  libc62.36-9+deb12u7
> > ii  libcrypt11:4.4.33-2
> > ii  libcurl4 7.88.1-10+deb12u5
> > ii  libjansson4  2.14-2
> > ii  libldap-2.5-02.5.13+dfsg-5
> > ii  liblua5.3-0  5.3.6-2
> > ii  libnghttp2-141.52.0-1+deb12u1
> > ii  libpcre2-8-0 10.42-1
> > ii  libssl3  3.0.11-1~deb12u2
> > ii  libxml2  2.9.14+dfsg-1.3~deb12u1
> > ii  perl 5.36.0-7+deb12u1
> > ii  zlib1g   1:1.2.13.dfsg-1
> >
> > Versions of packages apache2-bin suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  chromium [www-browser]   125.0.6422.60-1~deb12u1
> >
> > Versions of packages apache2 is related to:
> > ii  apache2  2.4.59-1~deb12u1
> > ii  apache2-bin  2.4.59-1~deb12u1
> >
> > -- Configuration Files:
> > /etc/apache2/apache2.conf changed:
> > DefaultRuntimeDir ${APACHE_RUN_DIR}
> > PidFile ${APACHE_PID_FILE}
> > Timeout 300
> > KeepAlive On
> > MaxKeepAliveRequests 100
> > KeepAliveTimeout 5
> > User ${APACHE_RUN_USER}
> > Group ${APACHE_RUN_GROUP}
> > HostnameLookups Off
> > ErrorLog ${APACHE_LOG_DIR}/error.log
> > LogLevel warn
> > IncludeOptional mods-enabled/*.load
> > IncludeOptional mods-enabled/*.conf
> > Include ports.conf
> > 
> >   Options FollowSymLinks
> >   AllowOverride None
> >   Require all denied
> > 
> > 
> >   AllowOverride None
> >   Require all granted
> > 
> > 
> >   Options Indexes FollowSymLinks
> >   AllowOverride None
> >   Require all granted
> > 
> > AccessFileName .htaccess
> > 
> >   Require all denied
> > 
> > LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" 
> > \"%{User-Agent}i\"" vhost_combined
> > LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" 
> > combined
> > LogFormat 

Bug#1018597: Bugs is forwarded to upstream

[Patrick Winnertz]

Control: tags -1 + upstream
Control: forwarded -1 https://github.com/Yubico/python-yubico/issues/60

As this is a upstream issue, I've forwarded the bug to upstream.

Greetings
Patrick

--
 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  win...@debian.org/patr...@winnertz.eu
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 8D208172388840811B85DA1CC6D50A4188C70E43
 ⠈⠳⣄

The people who refer to the pandemic in the past tense and climate 
change in the future tense are the reason everything is going to shit.


OpenPGP_0xC6D50A4188C70E43.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058474: gubbins: please (temporarily) drop python3-numba dependencies

[Étienne Mollier]

Control: tags -1 - wontfix
Control: tags -1 + confirmed
Control: severity -1 serious

Hi,

I've had a fresh look at this, and if I understand correctly,
the situation is still problematic today.  Gubbins is not
operating properly without python3-numba in testing, but it is
still installable because python3-numba is only recommended.
The autopkgtest suite does not run without python3-numba, and
indeed it is forcefully pulled by the debian/tests/control file.

All that being said, numba provides a just-in-time compiler to
accelerate decorated Python functions, so removing temporarily
dependency on numba simply consists in removing the decorators.
Fortunately, only the pyjar.py script makes use of numba, which
greatly facilitates the removal.  I have some changes almost
ready to be uploaded.  The only adverse effect of the removal
that I foresee, is that removing numba may lead to performance
reduction of the functions that were previously decorated.  The
removal should have no influence on functionalities or results.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/0, please excuse my verbosity
   `-on air: Legacy Pilots - The Squad Is Back


signature.asc
Description: PGP signature

Bug#1070095: RFS: sslscan/2.1.3-1 -- Tests SSL/TLS enabled services to discover supported cipher suites

[Alejo Marín]

tags 1070095 - moreinfo
thanks

-- 
*Jhon Alejandro Marín Rodríguez*

Bug#1071596: apache2: envvars evaluates string in conditional instead of testing for empty string

[Stefan Fritsch]

Hi Mark,

Am 21.05.24 um 22:30 schrieb Mark Hedges:

Package: apache2
Version: 2.4.59-1~deb12u1
Severity: normal

Dear Maintainer,

`envvars` evaluates string in conditional instead of testing for empty string.

`apachectl` calls `envvars` which shows a syntax error despite working:

  root@nodeo:/etc/letsencrypt# apachectl configtest
  /usr/sbin/apachectl: 6: [: /etc/apache2: unexpected operator
  Syntax OK

If I change this line in `envvars`:

  if [ "${APACHE_CONFDIR}" == "" ]; then
 export APACHE_CONFDIR=/etc/apache2
  fi


This snippet is not in the original file from the apache2 package. 
Compare to 
https://salsa.debian.org/apache-team/apache2/-/blob/master/debian/config-dir/envvars?ref_type=heads


Either you or some package or script has changed the file. If you have 
etckeeper you could dig in the logs.


Cheers,
Stefan



to this:

  if [ -z ${APACHE_CONFDIR} ]; then
 export APACHE_CONFDIR=/etc/apache2
  fi

... then it works.

It's trying to evaluate `/etc/apache2` as a command?  Weird.

PATH seems totally normal.

Mark

-- Package-specific info:

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

Kernel: Linux 6.1.0-21-amd64 (SMP w/1 CPU thread; PREEMPT)
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 apache2 depends on:
ii  apache2-bin2.4.59-1~deb12u1
ii  apache2-data   2.4.59-1~deb12u1
ii  apache2-utils  2.4.59-1~deb12u1
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  media-types10.0.0
ii  perl   5.36.0-7+deb12u1
ii  procps 2:4.0.2-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   125.0.6422.60-1~deb12u1

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.2-3
ii  libaprutil1  1.6.3-1
ii  libaprutil1-dbd-sqlite3  1.6.3-1
ii  libaprutil1-ldap 1.6.3-1
ii  libbrotli1   1.0.9-2+b6
ii  libc62.36-9+deb12u7
ii  libcrypt11:4.4.33-2
ii  libcurl4 7.88.1-10+deb12u5
ii  libjansson4  2.14-2
ii  libldap-2.5-02.5.13+dfsg-5
ii  liblua5.3-0  5.3.6-2
ii  libnghttp2-141.52.0-1+deb12u1
ii  libpcre2-8-0 10.42-1
ii  libssl3  3.0.11-1~deb12u2
ii  libxml2  2.9.14+dfsg-1.3~deb12u1
ii  perl 5.36.0-7+deb12u1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   125.0.6422.60-1~deb12u1

Versions of packages apache2 is related to:
ii  apache2  2.4.59-1~deb12u1
ii  apache2-bin  2.4.59-1~deb12u1

-- Configuration Files:
/etc/apache2/apache2.conf changed:
DefaultRuntimeDir ${APACHE_RUN_DIR}
PidFile ${APACHE_PID_FILE}
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
HostnameLookups Off
ErrorLog ${APACHE_LOG_DIR}/error.log
LogLevel warn
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
Include ports.conf

Options FollowSymLinks
AllowOverride None
Require all denied


AllowOverride None
Require all granted


Options Indexes FollowSymLinks
AllowOverride None
Require all granted

AccessFileName .htaccess

Require all denied

LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" 
vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" 
combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
IncludeOptional conf-enabled/*.conf
IncludeOptional sites-enabled/*.conf

/etc/apache2/envvars changed:
unset HOME
if [ -z "${APACHE_CONFDIR}" ]; then
export APACHE_CONFDIR=/etc/apache2
fi
if [ "${APACHE_CONFDIR##/etc/apache2-}" != "${APACHE_CONFDIR}" ] ; then
SUFFIX="-${APACHE_CONFDIR##/etc/apache2-}"
else
SUFFIX=
fi
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
export APACHE_PID_FILE=/var/run/apache2$SUFFIX/apache2.pid
export APACHE_RUN_DIR=/var/run/apache2$SUFFIX
export APACHE_LOCK_DIR=/var/lock/apache2$SUFFIX
export APACHE_LOG_DIR=/var/log/apache2$SUFFIX
export LANG=C
export LANG


-- no debconf information

Bug#1071420: linux-image-6.8.9-1-amd64: cannot mount btrfs root partition

[Matteo Settenvini]

Thanks Bastian,

I was able to reproduce this only with dracut, using a virtual machine
I tried both dracut and initramfs.

There seems to be a different problem at play indeed:

mag 22 21:44:12 rosebud systemd-journald[358]: Journal started
mag 22 21:44:12 rosebud systemd-journald[358]: Runtime Journal
(/run/log/journal/022ce7df193548d6ab2007cb814f1d04) is 8.0M, max
640.1M, 632.1M free.
mag 22 21:44:12 rosebud systemd-modules-load[359]: Inserted module
'msr'
mag 22 21:44:12 rosebud systemd-modules-load[359]: Inserted module
'bfq'
mag 22 21:44:12 rosebud dracut-cmdline[387]: dracut-dracut-060+5-8
mag 22 21:44:12 rosebud dracut-cmdline[387]: Using kernel command line
parameters:  rd.driver.pre=btrfs rd.luks.uuid=luks-13bd3015-55c4-40d3-
a805-4d5f2b90ac1f root=/dev/mapper/root rootfstype=btrfs
rootflags=rw,noatime,compress=zstd:3,ssd,space_cache=v2,subvolid=608,su
bvol=/rootfs,subvol=rootfs   BOOT_IMAGE=/vmlinuz-6.8.9-amd64
root=UUID=6fd6a999-b02d-4856-8412-64dff369d45f ro 
rootflags=subvol=rootfs rd.luks.name=13bd3015-55c4-40d3-a805-
4d5f2b90ac1f=root rd.luks.allow-discards quiet splash
mag 22 21:44:12 rosebud systemd[1]: Starting systemd-tmpfiles-
setup.service - Create Volatile Files and Directories...
mag 22 21:44:12 rosebud systemd[1]: Started systemd-journald.service -
Journal Service.
mag 22 21:44:12 rosebud dracut-cmdline[444]:
//lib/dracut/hooks/cmdline/00-parse-root.sh: line 28:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f6fd6a999-b02d-4856-8412-64dff369d45f.sh: Read-only file system
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/00-parse-root.sh: line 38:
/lib/dracut/hooks/emergency/80-\x2fdev\x2fdisk\x2fby-uuid\x2f6fd6a999-
b02d-4856-8412-64dff369d45f.sh: Read-only file system
mag 22 21:44:12 rosebud systemd[1]: Finished systemd-tmpfiles-
setup.service - Create Volatile Files and Directories.
mag 22 21:44:12 rosebud systemd-escape[471]: Input 'root' is not an
absolute file system path, escaping is likely not going to be
reversible.
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/30-parse-crypt.sh: line 169:
/lib/dracut/hooks/initqueue/finished/90-crypt.sh: Read-only file system
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/30-parse-crypt.sh: line 126:
/lib/dracut/hooks/emergency/90-crypt.sh: Read-only file system
mag 22 21:44:12 rosebud systemd[1]: Finished dracut-cmdline.service -
dracut cmdline hook.
mag 22 21:44:12 rosebud systemd[1]: Starting dracut-pre-udev.service -
dracut pre-udev hook...
...
mag 22 21:44:16 rosebud dracut-initqueue[752]: rm: cannot remove
'/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f09CB-D388.sh': Read-only file system
mag 22 21:44:16 rosebud dracut-initqueue[754]: rm: cannot remove
'/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f469f76d8-6293-4fd4-ad46-180c7bd186f4.sh': Read-only file system

I apologize for the confusion. 

I kindly ask you to close this bug as invalid.

Thanks again,
Matteo


Il giorno dom, 19/05/2024 alle 21.24 +0200, Bastian Blank ha scritto:
> Control: tags -1 moreinfo
> Control: severity -1 important
> 
> On Sat, May 18, 2024 at 10:25:14PM +0200, Matteo Settenvini wrote:
> > booting kernel 6.8.9-1 with dracut, systemd, and btrfs as the root
> > device fails
> > to mount the root partition. I just tried the kernel from sid and
> > it seems indeed \
> > affected. The 6.7 kernel from trixie is instead booting fine even
> > after
> > regenerating all initrds.
> 
> Please provide proper error messages.
> 
> Also dracut is not the default option, so please check with
> initramfs-tools as well.
> 
> Bastian

Bug#1071582: ip: Poor color choice for dark background

[Gedalya]

I'm trying ...

https://lore.kernel.org/netdev/2c0a1779713b5bdd443a8e8258c7d...@manjaro.org/

https://lore.kernel.org/netdev/e1s9rpa-0006jy7-1...@ws2.gedalya.net/

Bug#1068250: dracut: Consider switching to the fork dracut-ng

[Thomas Lange]

Yes, I already got this information.

I think I will also prepare dracut-ng to Debian. It then has to go
through the NEW queue. And currently I don't know, when I will start
this.


> On Wed, 22 May 2024 20:54:38 +0200, Evgeni Golov  said:

> FWIW, Fedora switched to this fork starting with Fedora 40 [1].
> [1] https://src.fedoraproject.org/rpms/dracut/

-- 
viele Grüße Thomas

Bug#1071642: javatools: Build-Depends on orphaned, RC-buggy markdown

[Bastian Germann]

Source: javatools
Version: 0.79
Severity: important
X-Debbugs-Cc: tmanc...@debian.org, ebo...@apache.org

The package Build-Depends on markdown, which is orphaned and RC-buggy.
javatools makes it a key package, which is the reason for it not being 
auto-removed.
Please consider applying the attached patch to depend on python3-markdown 
instead.diff -Nru javatools-0.79/debian/changelog javatools-0.79+nmu1/debian/changelog
--- javatools-0.79/debian/changelog 2023-07-29 05:15:46.0 +
+++ javatools-0.79+nmu1/debian/changelog2024-05-22 19:34:53.0 
+
@@ -1,3 +1,10 @@
+javatools (0.79+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Replace orphaned Build-Depends: markdown with python3-markdown
+
+ -- Bastian Germann   Wed, 22 May 2024 19:34:53 +
+
 javatools (0.79) unstable; urgency=medium
 
   [ Vladimir Petko ]
diff -Nru javatools-0.79/debian/control javatools-0.79+nmu1/debian/control
--- javatools-0.79/debian/control   2023-07-29 05:15:46.0 +
+++ javatools-0.79+nmu1/debian/control  2024-05-22 19:32:21.0 +
@@ -11,7 +11,7 @@
  libtest-minimumversion-perl,
  libtest-perl-critic-perl,
  libtest-strict-perl,
- markdown,
+ python3-markdown,
  perl
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
diff -Nru javatools-0.79/debian/rules javatools-0.79+nmu1/debian/rules
--- javatools-0.79/debian/rules 2023-07-29 05:15:46.0 +
+++ javatools-0.79+nmu1/debian/rules2024-05-22 19:30:19.0 +
@@ -38,7 +38,7 @@
# jarwrapper pod-based manpages
$(POD2MAN) -s 1 jarwrapper.pod tmp.jarwrapper/jarwrapper.1
$(POD2MAN) -s 1 jardetector.pod tmp.jarwrapper/jardetector.1
-   markdown --html4tags tutorial.txt | \
+   markdown_py -o html tutorial.txt | \
cat tutorial-header.html - tutorial-footer.html > tutorial.html
 
 runtests: jh_lib.sh

Bug#1071641: openscap: requires internet during build

[Gianfranco Costamagna]

Package: openscap
Version: 1.3.10+dfsg-2
Severity: Serious

Hello, I found the package to require internet in one test, and this can be 
seen in Ubuntu
builders, where internet is more strictly forbidden

test 5
  Start  5: curl/test_curl_encoding.sh

5: Test command: /<>/tests/curl/test_curl_encoding.sh
5: Working Directory: /<>/build-py3.12/tests/curl
5: Environment variables:
5:  srcdir=/<>/tests/curl
5:  top_srcdir=/<>
5:  builddir=/<>/build-py3.12
5: Test timeout computed to be: 1000
5: + cURL: Accept-Encoding
5: TEST: cURL: Accept-Encoding
5: OK
5: Couldn't assert gzip encoding in the log:
 5/37 Test  #5: curl/test_curl_encoding.sh .***Failed
0.15 sec
+ cURL: Accept-Encoding
TEST: cURL: Accept-Encoding
OK
Couldn't assert gzip encoding in the log:

test 6
  Start  6: CPE/all.sh



some tests, e.g. test-curl-encoding, clearly needs internet to run

function curl_accept_encoding {
# --fetch-remote-resources uses internet
require_internet || return 255

local DF="${srcdir}/ds.xml"
local RF="results.xml"
local LOG="verbose.log"

$OSCAP xccdf --verbose=DEVEL eval --fetch-remote-resources --results $RF $DF 
2>$LOG || echo "OK"

case $(uname) in
FreeBSD)
grep -iE "Accept-Encoding.*gzip" "$LOG"
;;
*)
grep -iP "Accept-Encoding.*gzip" "$LOG"
;;
esac || die "Couldn't assert gzip encoding in the log: $(grep -i 'curl 
header' $LOG)"

return 0
}

test_init

test_run "cURL: Accept-Encoding" curl_accept_encoding

test_exit



probably also
function test_ds_error_remote_resources() {
# --fetch-remote-resources uses internet
require_internet || return 255

local DS="${srcdir}/$1"
local PROFILE="$2"
local result=$(mktemp)
local stderr=$(mktemp)

$OSCAP xccdf eval --fetch-remote-resources --profile "$PROFILE" --results "$result" 
"$DS" 2>"$stderr" || ret=$?
grep -q "Downloading: https://www.example.com/security/data/oval/oval.xml.bz2 ... 
error" "$stderr"
grep -q "OpenSCAP Error: Download failed" "$stderr"

rm -f "$result" "$stderr"
}


needs patching.

thanks for having a look

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1043686: Please provide a proper download location for beads

[Filippo Rusconi]

Greetings, Andreas,


On Wednesday, 22 May 2024 07:22:32 CEST you wrote:
> Hi Filippo,
> 
> ping again.  The currently packaged beads is not at the location
> you wrote.  Please fix the watch file to report latest version.
> 
> Thanks a lot
>Andreas.

The git commit that seems to fix the bug is located at 

https://salsa.debian.org/med-team/beads/-/tree/1.1.22-1?ref_type=tags

To me it looks like it is the HEAD of the master branch.

Could you confirm this is correct ?

Sincerely,
Filippo

-- 

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Researcher at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
  http://www.debian.org


book: 
https://secure-web.cisco.com/1rOI-jxZ3pHmntG8CeBzZB7C1WY6J_W-bEUQKfWvBM52xQkrS9G3LLdll5yB9Z6lZnNexBedjl_8xQw-OJ7U34MaXpZNzuYZg_T-6EyAn5Uv94srVliNsTf7bTM9OVtBPgS0yoMVFgOSvSVkJM0BgIJ8ZgDBnQ4Ner5zNf_TfvkDOIBCNBemN6oEX7FBzYhReS6VQoTRE7GIA6ms1ttkdWwunTLbP63T3LszdQjEfQwIdcdVlQ80cAVR8YWH7R5124D4a6ax3IRYoI7wIiUjazQxrdBG6U448ZGTBBjJm6IVIcZk10dWanxiIjgrkOcsGblaawDenkL-eagMfPBgXajPel2vXznVJ0l8ePjzFFhG1zoubeVy0gjIQERL2MNtPsz7_yx7InqLEgT2pv13mR1j0p5j41OZlcwdQnMvCg9Q/https%3A%2F%2Fwww.lavoisier.fr%2Flivre%2Fchimie%2Fmanuel-de-spectrometrie-de-masse-a-l-usage-des-biochimistes%2Frusconi%2Fdescriptif-9782743013417%3Fcombien%3D1
http://books.google.fr/books?
id=2NmguxmEI1sC=frontcover=rusconi+f+lavoisier=fr=X=nGGOUt2SH_Ly0gX0uIHoBQ=0CDUQ6AEwAA#v=onepage=false

Institut Diversité, Écologie et Évolution du Vivant
Unité Génétique Quantitative et Évolution
Plateforme PAPPSO

Université Paris-Saclay, INRAE, UMR CNRS 8120, AgroParisTech
12, route 128, Bâtiment 680
91272 Gif-sur-Yvette
France

http://moulon.inrae.fr/ & http://pappso.inrae.fr/
Tel : +33 (0)1 69 33 23 54
Fax : +33 (0)1 69 33 23 40

Bug#996759: ITA: python-yubico for pkg-auth Team

[Patrick Winnertz]

Control: retitle -1 ITA: python-yubico -- Tools for Yubico YubiKeys
Control: owner -1 !


I started to update all yubico related packages within the pgk-auth team 
recently. The last upstream release is already 4 years ago, but till now 
there is no official obsolesence of that python library - thus I'll give 
the package a little bit love.


With best regards
Patrick

--
 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  win...@debian.org/patr...@winnertz.eu
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 8D208172388840811B85DA1CC6D50A4188C70E43
 ⠈⠳⣄

The people who refer to the pandemic in the past tense and climate 
change in the future tense are the reason everything is going to shit.

Bug#1070852: transition: gdal

[Sebastiaan Couwenberg]

On 5/22/24 8:40 AM, Emilio Pozuelo Monfort wrote:

Go ahead.


Thanks. gdal (3.9.0+dfsg-1) has been uploaded to unstable and is now 
built & installed on all release architectures.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1068250: dracut: Consider switching to the fork dracut-ng

[Evgeni Golov]

On Tue, Apr 02, 2024 at 09:31:55PM GMT, Thomas Lange wrote:
> > On Tue, 02 Apr 2024 19:59:57 +0200, Jörg Behrmann 
> >  said:
> 
> 
> > Activity in dracut upstream has died down recently and though there is 
> a version
> > 60 of dracut in sid, upstream has not tagged such a release.
> The upstream release process changed, so they do not tag the releases
> any more.
> 
> 
> > A fork of dracut has been started by some dracut developers at
> > https://github.com/dracut-ng/dracut-ng
> > It should be evaluated to switch to this fork.
> Thanks for the info. I will carefully watch the work on this fork.

FWIW, Fedora switched to this fork starting with Fedora 40 [1].

[1] https://src.fedoraproject.org/rpms/dracut/

Bug#1071597: rust-laurel - autopkgtest failure on s390x

[Hilko Bengen]

* Peter Green:

> When preparing the upload of 0.6.2-1, Hilko once again
> dropped the patch with a changelog entry of
> "Drop unneeded patches".
>
> So that brings us to where we are now, the package
> fails it's autopkgtests on s390x and I do not feel
> it's appropriate to reinstate the patch for the second
> time without first trying to get some feedback from
> the maintainer.

I am sorry for causing work and frustration on your side. I had thought
that I had fixed the test upstream, but I had neglected to double-check
on an actual big-endian porterbox.

Looking at the commit history, it is unclear to me where the belief that
things were fixed had come from. In any case the test has now been fixed
so that it passes on big-endian and little-endian architectures. I'll
add this commit to the rust-laurel package.

Also, thanks for reminding me that looking at buildd output is not
enough.

Cheers,
-Hilko

Bug#1059462: gcc-13: another potential user of gcc-13 on bookworm

[David Heidelberg]

Package: gcc-13
Version: 13.2.0-25
Followup-For: Bug #1059462


Dear Maintainer,

for the Mesa3D CI (where we use both gcc/clang) we would be very grateful if 
there would be also a GCC 13 option, so we could keep up testing with recent 
GCC versions rather than 12.
   
If you asking why not use a more recent version (trixie) - we stay with
the stable, so we can be sure no regressions are getting in between 
rebuilds (we're a very flake-prone environment).

I tried to search for a drop-in reliable solution, but what I found was
only people asking, if there is available gcc-13 for Debian.

Thank you for your hard work maintaining GCC!

David


-- System Information:

-- no debconf information

Bug#1071640: mitmproxy: Error prevents the program to starts

[cage]

Package: mitmproxy
Version: 8.1.1-2
Severity: important
X-Debbugs-Cc: cage-...@twistfold.it

Dear Maintainer,

starting the program leads to an unrecoverable error, a backtrace is printed on 
the console and the error is:

"ModuleNotFoundError: No module named 'blinker._saferef'"

than the process ends and we get back to the shell.

Bye!
C.

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

Kernel: Linux 6.7.12-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 mitmproxy depends on:
ii  dpkg  1.22.6
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-4.1
ii  python3   3.11.8-1
ii  python3-asgiref   3.8.1-1
ii  python3-blinker   1.8.2-1
ii  python3-brotli1.1.0-2+b3
ii  python3-certifi   2023.11.17-1
ii  python3-cryptography  42.0.5-2
ii  python3-flask 3.0.3-1
ii  python3-h11   0.14.0-1
ii  python3-h24.1.0-4
ii  python3-hyperframe6.0.0-1
ii  python3-kaitaistruct  0.10-1
ii  python3-ldap3 2.9.1-2
ii  python3-msgpack   1.0.3-3+b1
ii  python3-openssl   24.1.0-1
ii  python3-passlib   1.7.4-4
ii  python3-pkg-resources 68.1.2-2
ii  python3-protobuf  3.21.12-8.2
ii  python3-publicsuffix2 2.20191221-3
ii  python3-pyparsing 3.1.2-1
ii  python3-pyperclip 1.8.2-2
ii  python3-ruamel.yaml   0.18.6+ds-3
ii  python3-sortedcontainers  2.4.0-2
ii  python3-tornado   6.4.0-1
ii  python3-urwid 2.6.10-1
ii  python3-wsproto   1.2.0-1
ii  python3-zstandard 0.22.0-1+b1

mitmproxy recommends no packages.

mitmproxy suggests no packages.

-- no debconf information

Bug#1071639: /usr/bin/rpmsign: Documentation bug: rpmsign vs rpm

[Jon Daley]

Package: rpm
Version: 4.18.0+dfsg-1+deb12u1
Severity: minor
File: /usr/bin/rpmsign
Tags: upstream

Upstream documentation bug:

~>man rpmsign
   rpm --addsign|--resign [rpmsign-options] PACKAGE_FILE ...
   rpmsign-options
   [--rpmv3] [--fskpath KEY] [--signfiles]

~>rpm --addsign --rpmv3
rpm: --rpmv3: unknown option
~>rpm --addsign --fskpath asdasd --signfiles asd
rpm: --fskpath: unknown option
~>rpm --addsign --signfiles asd
rpm: --signfiles: unknown option

All of these rpmsign-options can only work when running rpmsign as opposed to 
rpm.

This bug also applies to Centos 7 and Oracle Linux 9, where I've been doing 
some testing.  It looks like it was introduced between Centos 6 and 7, if that 
helps anyone.


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

Kernel: Linux 6.1.0-19-amd64 (SMP w/8 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 rpm depends on:
ii  debugedit 1:5.0-5
ii  libc6 2.36-9+deb12u7
ii  libelf1   0.188-2.1
ii  libpopt0  1.19+dfsg-1
ii  libreadline8  8.2-1.3
ii  librpm9   4.18.0+dfsg-1+deb12u1
ii  librpmbuild9  4.18.0+dfsg-1+deb12u1
ii  librpmio9 4.18.0+dfsg-1+deb12u1
ii  librpmsign9   4.18.0+dfsg-1+deb12u1
ii  perl  5.36.0-7+deb12u1
ii  rpm-common4.18.0+dfsg-1+deb12u1
ii  rpm2cpio  4.18.0+dfsg-1+deb12u1

rpm recommends no packages.

Versions of packages rpm suggests:
ii  alien 8.95.6
pn  elfutils  
ii  python3   3.11.2-1+b1
pn  rpm-i18n  
pn  rpmlint   

-- no debconf information

Bug#1071592: fails to enable LVM on crypt during boot, rendering the system unbootable

[Evgeni Golov]

On Wed, May 22, 2024 at 05:58:50PM +0200, Evgeni Golov wrote:
> On Tue, May 21, 2024 at 10:10:02PM -0700, Benjamin Lee wrote:
> > > It's probably the same issue with missing libraries, but I do not use
> > > either dracut nor LVM so I cannot help, reassigning to dracut so that
> > > you might get some help with debugging and finding out what the actual
> > > issue is
> 
> I am rather sure it's not the libraries, as I have dracut -8.
> > 
> > It seems like the issue is that systemd 256 now makes /usr read-only in the
> > initrd environment, but dracut depends on writing to /usr.
> > 
> > One workaround is to set ProtectSystem=no in the initrd, so that /usr is
> > writable again.  I got my system (also LVM on LUKS) booting with a dracut
> > module to write system.conf:
> > 
> > blee@r8 /usr/lib/dracut/modules.d/99local $ cat module-setup.sh
> > #!/bin/bash
> > 
> > # called by dracut
> > install() {
> > printf "[Manager]\nProtectSystem=no\n" >> 
> > "${initdir}/etc/systemd/system.conf"
> > }
> 
> Thanks! That worked, even if it looks like a gross hack. :)
> 
> In the meantime, I have found [1] over at Fedora, which I am going to
> try next (as it is supposed to fix the same thing, but cleaner).

It does fix the issue!

I've opened an MR against the dracut package [2] and uploaded built
packages at [3] if anyone wants to try :)

Thanks for hinting me in the right direction!

Evgeni

[2] https://salsa.debian.org/debian/dracut/-/merge_requests/36
[3] https://people.debian.org/~evgeni/dracut-systemd-ro-usr/

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Moritz Muehlenhoff]

On Wed, May 22, 2024 at 02:42:58PM -0300, Leandro Cunha wrote:
> Hi everyone,
> 
> On Wed, May 22, 2024 at 12:39 PM Moritz Mühlenhoff  wrote:
> >
> > Am Wed, Mar 06, 2024 at 06:39:01AM -0300 schrieb Leandro Cunha:
> > > Hi Christoph Berg,
> > >
> > > On Wed, Mar 6, 2024 at 5:42 AM Christoph Berg  wrote:
> > > >
> > > > Re: Leandro Cunha
> > > > > The
> > > > > next job would be to make it available through backports and I would
> > > > > choose to remove this package from stable. But I would only leave
> > > > > bookworm backports due to other bugs found (this CVEs too) and fixed
> > > > > in 7.14.7.
> > > > > I have to search about the status of backports to oldstable. But I'm
> > > > > also studying the possibility of working with patches for these two
> > > > > versions.
> > > >
> > > > Why would you want to remove it from stable? In closed environments,
> > > > CVEs are often not a problem.
> > > >
> > > > Christoph
> > >
> > > In addition to the CVEs, phppgadmin which is present in stable does
> > > not connect to PostgreSQL 15 and 16 without a patch I inserted in
> > > 7.13.0+dfsg-3, but I can add the same patch by reopening bug #1029516
> > > or opening another important bug (I am aware that the bug must have a
> > > severity greater than important)[3] for the stable and submission of
> > > new bug to the release team for approval. That way it would be
> > > released in a future release a version with this issue fixed (if
> > > approved). But CVE-2023-40619 is treated with critical severity and
> > > CVE-2019-10784 is also critical according to the NVD[1][2]. The Debian
> > > LTS team handled this with DLA-3644-1 (CVE-2023-40619)[4] in buster
> > > (oldoldstable) and of OpenSUSE team also handled both CVEs in
> > > Leap[5][6].
> > > Removing this package in stable will not leave users without them and
> > > we can release it in backports.
> > > I can treat this as a job of ensuring the quality of what is
> > > distributed by Debian.
> >
> > Agreed, if the package is actually broken with the version of PostgreSQL
> > in stable and if there's no sensible backport for the open security issues,
> > then let's rather remove it by the next point release.
> >
> > Cheers,
> > Moritz
> 
> It's the best thing to do, the package with the necessary corrections
> is already present in bookworm-backports and the user just needs to
> run apt install -t bookworm-backports phppgadmin[1][2][3] with
> sponsorship of Christoph Berg (thank you for that) and thanks also to
> the Debian Security Team.

Ack, will you do the removal request? You can do that with
"reportbug release.debian.org" and then selecting the
"rm stable/testing removal requests" option.

Cheers,
Moritz

Bug#1071373: ITS: hardinfo

[Boyuan Yang]

Hi Simon,

On Wed, 2024-05-22 at 16:38 +, Simon Quigley wrote:
> Hello,
> 
> Firstly, I would like to thank you and others for your persistence in 
> this effort. I am glad that there is interest in this package again.
> 
> My original interest in maintaining hardinfo was due to its inclusion in 
> Lubuntu, prior to our switch to LXQt. It was one of the first packages I 
> worked on as an "up and coming" Debian Developer, and to my 
> understanding, the packaging as of 2018 was fully up to date and 
> standards-compliant.
> 
> That being said, I no longer have as much interest in this package as I 
> used to. Boyuan, please go ahead and take over maintainership if you are 
> interested. My only request is that I stay as a co-maintainer, since 
> this package has sentimental value to me.
> 
> Thank you again for your efforts. Proceed.

Thank you for the detailed reply. I will proceed with package uploads
and keep your name in the uploader list. Thank you for all your past
work!

Best,
Boyuan Yang


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

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Leandro Cunha]

Hi everyone,

On Wed, May 22, 2024 at 12:39 PM Moritz Mühlenhoff  wrote:
>
> Am Wed, Mar 06, 2024 at 06:39:01AM -0300 schrieb Leandro Cunha:
> > Hi Christoph Berg,
> >
> > On Wed, Mar 6, 2024 at 5:42 AM Christoph Berg  wrote:
> > >
> > > Re: Leandro Cunha
> > > > The
> > > > next job would be to make it available through backports and I would
> > > > choose to remove this package from stable. But I would only leave
> > > > bookworm backports due to other bugs found (this CVEs too) and fixed
> > > > in 7.14.7.
> > > > I have to search about the status of backports to oldstable. But I'm
> > > > also studying the possibility of working with patches for these two
> > > > versions.
> > >
> > > Why would you want to remove it from stable? In closed environments,
> > > CVEs are often not a problem.
> > >
> > > Christoph
> >
> > In addition to the CVEs, phppgadmin which is present in stable does
> > not connect to PostgreSQL 15 and 16 without a patch I inserted in
> > 7.13.0+dfsg-3, but I can add the same patch by reopening bug #1029516
> > or opening another important bug (I am aware that the bug must have a
> > severity greater than important)[3] for the stable and submission of
> > new bug to the release team for approval. That way it would be
> > released in a future release a version with this issue fixed (if
> > approved). But CVE-2023-40619 is treated with critical severity and
> > CVE-2019-10784 is also critical according to the NVD[1][2]. The Debian
> > LTS team handled this with DLA-3644-1 (CVE-2023-40619)[4] in buster
> > (oldoldstable) and of OpenSUSE team also handled both CVEs in
> > Leap[5][6].
> > Removing this package in stable will not leave users without them and
> > we can release it in backports.
> > I can treat this as a job of ensuring the quality of what is
> > distributed by Debian.
>
> Agreed, if the package is actually broken with the version of PostgreSQL
> in stable and if there's no sensible backport for the open security issues,
> then let's rather remove it by the next point release.
>
> Cheers,
> Moritz

It's the best thing to do, the package with the necessary corrections
is already present in bookworm-backports and the user just needs to
run apt install -t bookworm-backports phppgadmin[1][2][3] with
sponsorship of Christoph Berg (thank you for that) and thanks also to
the Debian Security Team.

[1] https://packages.debian.org/bookworm-backports/phppgadmin
[2] https://backports.debian.org/Instructions/
[3] https://tracker.debian.org/pkg/phppgadmin

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa

Bug#1071638: sa-update calls “GET /MIRRORED.BY%20https://spamassassin.apache.org/updates/MIRRORED.BY HTTP/1.1\r\n”

[Дилян Палаузов]

Package: Spamassassin
Version: 4.0.0-6

Hello,

as described at https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8255 , after 
calling

strace -s2048 -f sa-update -D --httputil wget

on Debian Bookworm with perl 5.36.0 is executed

execve("/usr/bin/wget", ["/usr/bin/wget", "-q", "--max-redirect=2", 
"--tries=3", "--dns-timeout=20", "--connect-timeout=30", "--read-timeout=300", 
"-O", "MIRRORED.BY", "-U", "sa-update/4.0.0 / svn1900642/4.0.0", "--", 
"http://sa-update.spamassassin.org/MIRRORED.BY 
https://spamassassin.apache.org/updates/MIRRORED.BY;], 0x55be2543f8a0 /* 16 
vars */) = 0

and then the HTTP server receives

GET /MIRRORED.BY%20https://spamassassin.apache.org/updates/MIRRORED.BY 
HTTP/1.1\r\n

which cannot work (In theorly this GET /… can work, but in practice it fails).  
wget and thus sa-update return error.

Kind regards
  Дилян

Bug#1071592: fails to enable LVM on crypt during boot, rendering the system unbootable

[Evgeni Golov]

On Tue, May 21, 2024 at 10:10:02PM -0700, Benjamin Lee wrote:
> > It's probably the same issue with missing libraries, but I do not use
> > either dracut nor LVM so I cannot help, reassigning to dracut so that
> > you might get some help with debugging and finding out what the actual
> > issue is

I am rather sure it's not the libraries, as I have dracut -8.
> 
> It seems like the issue is that systemd 256 now makes /usr read-only in the
> initrd environment, but dracut depends on writing to /usr.
> 
> One workaround is to set ProtectSystem=no in the initrd, so that /usr is
> writable again.  I got my system (also LVM on LUKS) booting with a dracut
> module to write system.conf:
> 
> blee@r8 /usr/lib/dracut/modules.d/99local $ cat module-setup.sh
> #!/bin/bash
> 
> # called by dracut
> install() {
> printf "[Manager]\nProtectSystem=no\n" >> 
> "${initdir}/etc/systemd/system.conf"
> }

Thanks! That worked, even if it looks like a gross hack. :)

In the meantime, I have found [1] over at Fedora, which I am going to
try next (as it is supposed to fix the same thing, but cleaner).

Evgeni

[1] 
https://src.fedoraproject.org/rpms/dracut/blob/rawhide/f/0019-fix-dracut-move-hooks-directory-from-usr-lib-to-var-.patch

Bug#1071637: masakari: please remove extraneous python3-mock build dependency

[Alexandre Detiste]

Source: masakari
Version: 17.0.0-1
Severity: normal

Dear Maintainers,

This project has already switched to unittest.mock
from the standard library.

debian/control: python3-mock,
debian/control: python3-requests-mock,
masakari/test.py:from unittest import mock  # noqa: E402
masakari/tests/unit/api/openstack/ha/test_extension_info.py:from unittest 
import mock
masakari/tests/unit/api/openstack/ha/test_hosts.py:from unittest import mock
masakari/tests/unit/api/openstack/ha/test_notifications.py:from unittest import 
mock
masakari/tests/unit/api/openstack/ha/test_segments.py:from unittest import mock
masakari/tests/unit/api/openstack/ha/test_versions.py:from unittest import mock
...

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Christoph Berg]

Re: Moritz Mühlenhoff
> Agreed, if the package is actually broken with the version of PostgreSQL
> in stable and if there's no sensible backport for the open security issues,
> then let's rather remove it by the next point release.

Ack.

Christoph

Bug#1071636: RM: mia/experimental -- RoQA; t64 transition not needed

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Further analysis has shown that a t64 transition is not needed for mia.

https://bugs.debian.org/1062881

Please remove the renamed packages that have been staged in experimental.

libmia-2.4-4| 2.4.7-13+b4 | unstable | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
libmia-2.4-4t64 | 2.4.7-13.1~exp1 | experimental | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
libmia-2.4-dev  | 2.4.7-13+b4 | unstable | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
libmia-2.4-dev  | 2.4.7-13.1~exp1 | experimental | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
libmia-2.4-doc  | 2.4.7-13| unstable | all
libmia-2.4-doc  | 2.4.7-13.1~exp1 | experimental | all
mia | 2.4.7-13| unstable | source
mia | 2.4.7-13.1~exp1 | experimental | source
mia-doctools| 2.4.7-13| unstable | all
mia-doctools| 2.4.7-13.1~exp1 | experimental | all
mia-tools   | 2.4.7-13+b4 | unstable | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
mia-tools   | 2.4.7-13.1~exp1 | experimental | amd64, arm64, armel, armhf, 
i386, mips64el, ppc64el, riscv64, s390x
mia-tools-doc   | 2.4.7-13| unstable | all
mia-tools-doc   | 2.4.7-13.1~exp1 | experimental | all


Andreas

Bug#1071373: ITS: hardinfo

[Simon Quigley]

Hello,

Firstly, I would like to thank you and others for your persistence in 
this effort. I am glad that there is interest in this package again.


My original interest in maintaining hardinfo was due to its inclusion in 
Lubuntu, prior to our switch to LXQt. It was one of the first packages I 
worked on as an "up and coming" Debian Developer, and to my 
understanding, the packaging as of 2018 was fully up to date and 
standards-compliant.


That being said, I no longer have as much interest in this package as I 
used to. Boyuan, please go ahead and take over maintainership if you are 
interested. My only request is that I stay as a co-maintainer, since 
this package has sentimental value to me.


Thank you again for your efforts. Proceed.

--
Simon Quigley
si...@tsimonq2.net
@tsimonq2:ubuntu.com on Matrix
tsimonq2 on LiberaChat and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071611: conky-all: horizontal border are lost

[Vincent Cheng]

On Wed, May 22, 2024 at 4:51 AM Dieter Faulbaum
 wrote:
>
> Package: conky-all
> Version: 1.21.1-1
> Severity: minor
>
> Dear Maintainer,
>
> after upgrading to version 1.12.0 (and than to 1.21.1) the horizontal borders
> aren't shown anymore.
> The vertical borders are visible.
>
> I use cinnamon (under X). In a VM with LXDE it's the same.

This appears to be an upstream bug, please report it upstream at
https://github.com/brndnmtthws/conky/issues

Regards,
Vincent

Bug#1071547: nmu: libalien-wxwidgets-perl_0.69+dfsg-6+b7

[Scott Talbert]

Control: reopen -1

On Tue, 21 May 2024, Emilio Pozuelo Monfort wrote:


On 21/05/2024 01:20, Scott Talbert wrote:

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libalien-wxwidgets-p...@packages.debian.org
Control: affects -1 + src:libalien-wxwidgets-perl
User: release.debian@packages.debian.org
Usertags: binnmu

nmu libalien-wxwidgets-perl_0.69+dfsg-6+b7 . ANY . unstable . -m "Rebuild 
for wxwidgets3.2 (3.2.5+dfsg-1)"


(Please schedule this to rebuild with wxwidgets3.2 (3.2.5+dfsg-1))


Scheduled.


Hello,

Unfortunately, it seems this was scheduled to execute immediately, rather 
than wait for wxwidgets3.2 (3.2.5+dfsg-1).  So we're going to need another 
binNMU now that wx has been uploaded.


Regards,
Scott

Bug#779207: unzip fails to unpack filenames containing 'ä' 'ö' 'ü' -> results in "(invalid encoding)"

[Ivan Sorokin]

The built-in .zip archiver in older versions of Windows used DOS (OEM) or 
Windows (ANSI) code page corresponding to current regional settings for new 
archives. Lots of such archives still exist.
 
The correct behavior is to determine the relevant OEM or ANSI code page based 
on the system locale and use it. You can look at this PR for reference 
implementation:
https://github.com/p7zip-project/p7zip/pull/232

Sample archive showing this bug attached. It uses CP866 (often called DOS or 
OEM) for Cyrillic (Russian) letters.

 
 
 <>

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Moritz Mühlenhoff]

Am Wed, Mar 06, 2024 at 06:39:01AM -0300 schrieb Leandro Cunha:
> Hi Christoph Berg,
> 
> On Wed, Mar 6, 2024 at 5:42 AM Christoph Berg  wrote:
> >
> > Re: Leandro Cunha
> > > The
> > > next job would be to make it available through backports and I would
> > > choose to remove this package from stable. But I would only leave
> > > bookworm backports due to other bugs found (this CVEs too) and fixed
> > > in 7.14.7.
> > > I have to search about the status of backports to oldstable. But I'm
> > > also studying the possibility of working with patches for these two
> > > versions.
> >
> > Why would you want to remove it from stable? In closed environments,
> > CVEs are often not a problem.
> >
> > Christoph
> 
> In addition to the CVEs, phppgadmin which is present in stable does
> not connect to PostgreSQL 15 and 16 without a patch I inserted in
> 7.13.0+dfsg-3, but I can add the same patch by reopening bug #1029516
> or opening another important bug (I am aware that the bug must have a
> severity greater than important)[3] for the stable and submission of
> new bug to the release team for approval. That way it would be
> released in a future release a version with this issue fixed (if
> approved). But CVE-2023-40619 is treated with critical severity and
> CVE-2019-10784 is also critical according to the NVD[1][2]. The Debian
> LTS team handled this with DLA-3644-1 (CVE-2023-40619)[4] in buster
> (oldoldstable) and of OpenSUSE team also handled both CVEs in
> Leap[5][6].
> Removing this package in stable will not leave users without them and
> we can release it in backports.
> I can treat this as a job of ensuring the quality of what is
> distributed by Debian.

Agreed, if the package is actually broken with the version of PostgreSQL
in stable and if there's no sensible backport for the open security issues,
then let's rather remove it by the next point release.

Cheers,
Moritz

Bug#1071635: ITP: aioruuvigateway -- asyncio-native library for Ruuvi Gateway data requests

[Edward Betts]

Package: wnpp
Severity: wishlist
Owner: Edward Betts 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: aioruuvigateway
  Version : 0.1.0
  Upstream Author : Aarni Koskela 
* URL : https://github.com/akx/aioruuvigateway#readme
* License : MIT
  Programming Lang: Python
  Description : asyncio-native library for Ruuvi Gateway data requests

  An asyncio-native library designed to request data from a Ruuvi Gateway.
  It supports bearer token authentication and allows for efficient data
  retrieval and parsing.
  .
  The Ruuvi Gateway is a device that allows you to remotely access your Ruuvi
  sensors from anywhere in the world.
  .
  This library offers both an API and a command-line interface for accessing and
  displaying data from the Ruuvi Gateway.
  .
  Example usage:
  .
  from aioruuvigateway.api import get_gateway_history_data
 
  async with httpx.AsyncClient() as client:
  history = await get_gateway_history_data(
  client=client,
  host="192.168.1.249",
  bearer_token="your_token_here",
  )
  print(history)
 
  Command-line interface example:
  .
  python -m aioruuvigateway --host 192.168.1.249 --token bearbear --parse --json
  .
  This will output data from the gateway in JSON format, printing changed
  information every 10 seconds.

I plan to maintain this package as part of the Python team.

Bug#1071603: systemd-udevd.service: kdump : failed to call kexec_load system call : Operation not permitted

[Luca Boccassi]

Control: reassign -1 kdump-tools 1:1.8.1

On Wed, 22 May 2024 00:46:42 -0700 Yong Wang 
wrote:
> Package: udev
> Version: 252.22-1~deb12u1
> Severity: important
> X-Debbugs-Cc: yongw...@nvidia.com
> 
> Dear Maintainer,
> 
>   The error shows up every time when cpu "online" event triggers
"kdump-config try-reload", 
> with error message : "kdump-config: failed to unload kdump kernel"
(in syslog), due to 
> kexec_load system call (belongs to "@reboot" set) is missing in
whitelist i.e. "SystemCallFilter"  
> setting in systemd-udevd.service.
>   In SMP system, performing the following command can trigger cpu
"online" event:
> echo 0 > /sys/devices/system/cpu/cpu1/online
> echo 1 > /sys/devices/system/cpu/cpu1/online
>   kdump kernel is expected to be unloaded and reloaded successfully
in this scenario rather than 
> getting such error message.

There is no such rule in the udev package, it comes from kdump-tools:

https://sources.debian.org/data/main/k/kdump-tools/1%3A1.10.3/debian/kdump-tools.udev

If a package adds rules that require additional permissions, then it's
that package that needs to ship a drop-in to allow them, otherwise the
attack surface is increased even for those that don't use it.

kdump-tools maintainers, please ship a drop-in like this together with
your udev rule:

/usr/lib/systemd/system/systemd-udevd.service.d/debian-kdump-tools-
kexec.conf
[Service]
SystemCallFilter=@reboot

(note that I haven't tested this)

-- 
Kind regards,
Luca Boccassi


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

Bug#1071634: itstool: SyntaxWarnings with Python 3.12

[Simon Chopin]

Package: itstool
Version: 2.0.6-2
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com

Hi,

Since the transition to Python 3.12, it now emits SyntaxWarnings when
using unknown escape sequences, which typically happens on regexps.
itstool is impacted in its default path:

❯ itstool
/usr/bin/itstool:239: SyntaxWarning: invalid escape sequence '\s'
  if re.sub('\s+', ' ', text).strip() != '':
/usr/bin/itstool:337: SyntaxWarning: invalid escape sequence '\s'
  message = re.sub('\s+', ' ', message).strip()
/usr/bin/itstool:475: SyntaxWarning: invalid escape sequence '\s'
  return re.sub('\s+', ' ', self.locnote).strip()
/usr/bin/itstool:477: SyntaxWarning: invalid escape sequence '\s'
  return '(itstool) link: ' + re.sub('\s+', ' ', self.locnoteref).strip()
/usr/bin/itstool:891: SyntaxWarning: invalid escape sequence '\<'
  regex = re.compile('(.*) \<(.*)\>, (.*)')
/usr/bin/itstool:926: SyntaxWarning: invalid escape sequence '\s'
  if re.sub('\s+', '', prevtext) == '':
/usr/bin/itstool:1452: SyntaxWarning: invalid escape sequence '\.'
  _locale_pattern = 
re.compile('([a-zA-Z0-9-]+)(_[A-Za-z0-9]+)?(@[A-Za-z0-9]+)?(\.[A-Za-z0-9]+)?')
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2024-05-22 17:25+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

This has been reported both upstream and in Launchpad, but it seems that
upstream is somewhat unresponsive, so I think the patch posted in
https://github.com/itstool/itstool/pull/51 should be carried in Debian,
even just to reduce the amount of noise in build logs :)

I'll be posting a Salsa MR to that effect shortly.

-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble-security'), (500, 'noble')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-31-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_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)
LSM: AppArmor: enabled

Versions of packages itstool depends on:
ii  python3  3.12.3-0ubuntu1
ii  python3-libxml2  2.9.14+dfsg-1.3ubuntu3

itstool recommends no packages.

itstool suggests no packages.

-- no debconf information

Bug#1071633: libmodbus: CVE-2024-34244

[Moritz Mühlenhoff]

Source: libmodbus
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for libmodbus.

CVE-2024-34244[0]:
| libmodbus v3.1.10 is vulnerable to Buffer Overflow via the
| modbus_write_bits function. This issue can be triggered when the
| function is fed with specially crafted input, which leads to out-of-
| bounds read and can potentially cause a crash or other unintended
| behaviors.

https://github.com/stephane/libmodbus/issues/743


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-34244
https://www.cve.org/CVERecord?id=CVE-2024-34244

Please adjust the affected versions in the BTS as needed.

Bug#1071629: loginctl.1: some remarks and editorial changes for this man page

[Luca Boccassi]

Control: tags -1 -patch wontfix
Control: close -1

On Wed, 22 May 2024 15:11:06 + Bjarni Ingi Gislason
 wrote:
> Package: systemd
> Version: 255.5-1
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> 
>   here are some notes and editorial fixes for the manual
'loginctl.1'.
> 
> The patch is in the attachment.

These manpages are generated from XML, so they cannot be patched. If
you have fixes, please submit them directly upstream:

https://github.com/systemd/systemd/blob/main/man/loginctl.xml

-- 
Kind regards,
Luca Boccassi


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

Bug#1071632: node-braces: CVE-2024-4068

[Moritz Mühlenhoff]

Source: node-braces
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for node-braces.

CVE-2024-4068[0]:
| The NPM package `braces`, versions prior to 3.0.3, fails to limit
| the number of characters it can handle, which could lead to Memory
| Exhaustion. In `lib/parse.js,` if a malicious user sends "imbalanced
| braces" as input, the parsing will enter a loop, which will cause
| the program to start allocating heap memory without freeing it at
| any moment of the loop. Eventually, the JavaScript heap limit is
| reached, and the program will crash.

https://github.com/micromatch/braces/issues/35


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-4068
https://www.cve.org/CVERecord?id=CVE-2024-4068

Please adjust the affected versions in the BTS as needed.

Bug#1071631: node-micromatch: CVE-2024-4067

[Moritz Mühlenhoff]

Source: node-micromatch
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for node-micromatch.

CVE-2024-4067[0]:
| The NPM package `micromatch` is vulnerable to Regular Expression
| Denial of Service (ReDoS). The vulnerability occurs in
| `micromatch.braces()` in `index.js` because the pattern `.*` will
| greedily match anything. By passing a malicious payload, the pattern
| matching will keep backtracking to the input while it doesn't find
| the closing bracket. As the input size increases, the consumption
| time will also increase until it causes the application to hang or
| slow down. There was a merged fix but further testing shows the
| issue persists. This issue should be mitigated by using a safe
| pattern that won't start backtracking the regular expression due to
| greedy matching.

https://github.com/micromatch/micromatch/issues/243
https://github.com/micromatch/micromatch/pull/247


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-4067
https://www.cve.org/CVERecord?id=CVE-2024-4067

Please adjust the affected versions in the BTS as needed.

Bug#1071630: maxima: CVE-2024-34490

[Moritz Mühlenhoff]

Source: maxima
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for maxima.

CVE-2024-34490[0]:
| In Maxima through 5.47.0 before 51704c, the plotting facilities make
| use of predictable names under /tmp. Thus, the contents may be
| controlled by a local attacker who can create files in advance with
| these names. This affects, for example, plot2d.

https://sourceforge.net/p/maxima/bugs/3755/
https://sourceforge.net/p/maxima/code/ci/51704ccb090f6f971b641e4e0b7c1c22c4828bf7/


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-34490
https://www.cve.org/CVERecord?id=CVE-2024-34490

Please adjust the affected versions in the BTS as needed.

Bug#1071629: loginctl.1: some remarks and editorial changes for this man page

[Bjarni Ingi Gislason]

Package: systemd
Version: 255.5-1
Severity: minor
Tags: patch

Dear Maintainer,

  here are some notes and editorial fixes for the manual 'loginctl.1'.

The patch is in the attachment.

-.-

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "

instead of "nroff -man"

  Add the option "-t", if the file contains a table.

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual for warnings,
the following must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint loginctl.1": (possibly shortened list)

mandoc: loginctl.1:2:20: WARNING: missing date, using "": TH
mandoc: loginctl.1:28:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:35:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:38:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:46:384: STYLE: input text line longer than 80 bytes: Show 
terse runtime s...
mandoc: loginctl.1:55:235: STYLE: input text line longer than 80 bytes: Show 
properties of o...
mandoc: loginctl.1:61:123: STYLE: input text line longer than 80 bytes: if 
exists, and falls...
mandoc: loginctl.1:73:262: STYLE: input text line longer than 80 bytes: 
Activate a session\&...
mandoc: loginctl.1:80:223: STYLE: input text line longer than 80 bytes: 
Activates/deactivate...
mandoc: loginctl.1:94:215: STYLE: input text line longer than 80 bytes: 
Terminates a session...
mandoc: loginctl.1:105:134: STYLE: input text line longer than 80 bytes: to 
select the signal...
mandoc: loginctl.1:110:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:118:407: STYLE: input text line longer than 80 bytes: Show 
terse runtime s...
mandoc: loginctl.1:127:244: STYLE: input text line longer than 80 bytes: Show 
properties of o...
mandoc: loginctl.1:139:400: STYLE: input text line longer than 80 bytes: 
Enable/disable user ...
mandoc: loginctl.1:151:260: STYLE: input text line longer than 80 bytes: 
Terminates all sessi...
mandoc: loginctl.1:160:147: STYLE: input text line longer than 80 bytes: to 
select the signal...
mandoc: loginctl.1:165:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:173:318: STYLE: input text line longer than 80 bytes: Show 
terse runtime s...
mandoc: loginctl.1:182:244: STYLE: input text line longer than 80 bytes: Show 
properties of o...
mandoc: loginctl.1:194:108: STYLE: input text line longer than 80 bytes: 
Persistently attach ...
mandoc: loginctl.1:196:161: STYLE: input text line longer than 80 bytes: file 
system\&. To cr...
mandoc: loginctl.1:201:105: STYLE: input text line longer than 80 bytes: 
"seat"\&. To drop as...
mandoc: loginctl.1:215:147: STYLE: input text line longer than 80 bytes: 
Terminates all sessi...
mandoc: loginctl.1:220:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:230:204: STYLE: input text line longer than 80 bytes: When 
showing session...
mandoc: loginctl.1:231:95: STYLE: input text line longer than 80 bytes: 
"Sessions"\&. If spe...
mandoc: loginctl.1:236:95: STYLE: input text line longer than 80 bytes: When 
showing session...
mandoc: loginctl.1:244:107: STYLE: input text line longer than 80 bytes: When 
showing session...
mandoc: loginctl.1:260:130: STYLE: input text line longer than 80 bytes: "all", 
to select whe...
mandoc: loginctl.1:280:87: STYLE: input text line longer than 80 bytes: will 
list the known ...
mandoc: loginctl.1:282:103: STYLE: input text line longer than 80 bytes: will 
list known valu...
mandoc: loginctl.1:309:93: STYLE: input text line longer than 80 bytes: Execute 
the operatio...
mandoc: loginctl.1:310:105: STYLE: input text line longer than 80 bytes: "@", 
to connect to\&...
mandoc: loginctl.1:312:184: STYLE: input text line longer than 80 bytes: "/", 
which connects ...
mandoc: loginctl.1:318:147: STYLE: input text line longer than 80 bytes: 
Execute operation on...
mandoc: loginctl.1:322:143: STYLE: input text line longer than 80 bytes: is 
used in place of ...
mandoc: loginctl.1:327:131: STYLE: input text line longer than 80 bytes: syntax 
is used eithe...
mandoc: loginctl.1:352:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:355:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:384:196: STYLE: input text line longer than 80 bytes: There 
are two sessio...
mandoc: loginctl.1:386:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:389:179: STYLE: input text line longer than 80 bytes: The 
maximum log leve...
mandoc: loginctl.1:404:90: STYLE: input text line longer than 80 bytes: A 
boolean\&. If true...
mandoc: loginctl.1:406:87: STYLE: input 

Bug#1071628: python-pymysql: CVE-2024-36039

[Moritz Mühlenhoff]

Source: python-pymysql
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-pymysql.

We should also fix this in a DSA, could you prepare debdiffs for
bookworm-security and bullseye-security?

CVE-2024-36039[0]:
| PyMySQL through 1.1.0 allows SQL injection if used with untrusted
| JSON input because keys are not escaped by escape_dict.

https://github.com/advisories/GHSA-v9hf-5j83-6xpp
https://github.com/PyMySQL/PyMySQL/commit/521e40050cb386a499f68f483fefd144c493053c
 (v1.1.1)


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-36039
https://www.cve.org/CVERecord?id=CVE-2024-36039

Please adjust the affected versions in the BTS as needed.

Bug#1071626: ruby3.1: CVE-2024-35176

[Moritz Mühlenhoff]

Source: ruby3.1
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for ruby3.1.

CVE-2024-35176[0]:
| REXML is an XML toolkit for Ruby. The REXML gem before 3.2.6 has a
| denial of service vulnerability when it parses an XML that has many
| `<`s in an attribute value. Those who need to parse untrusted XMLs
| may be impacted to this vulnerability. The REXML gem 3.2.7 or later
| include the patch to fix this vulnerability. As a workaround, don't
| parse untrusted XMLs.

https://github.com/ruby/rexml/security/advisories/GHSA-vg3r-rm7w-2xgh
Fixed by: 
https://github.com/ruby/rexml/commit/4325835f92f3f142ebd91a3fdba4e1f1ab7f1cfb 
(v3.2.7)
https://www.ruby-lang.org/en/news/2024/05/16/dos-rexml-cve-2024-35176/


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-35176
https://www.cve.org/CVERecord?id=CVE-2024-35176

Please adjust the affected versions in the BTS as needed.

Bug#1071627: ruby3.2: CVE-2024-35176

[Moritz Mühlenhoff]

Source: ruby3.2
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for ruby3.2.

CVE-2024-35176[0]:
| REXML is an XML toolkit for Ruby. The REXML gem before 3.2.6 has a
| denial of service vulnerability when it parses an XML that has many
| `<`s in an attribute value. Those who need to parse untrusted XMLs
| may be impacted to this vulnerability. The REXML gem 3.2.7 or later
| include the patch to fix this vulnerability. As a workaround, don't
| parse untrusted XMLs.

https://github.com/ruby/rexml/security/advisories/GHSA-vg3r-rm7w-2xgh
Fixed by: 
https://github.com/ruby/rexml/commit/4325835f92f3f142ebd91a3fdba4e1f1ab7f1cfb 
(v3.2.7)
https://www.ruby-lang.org/en/news/2024/05/16/dos-rexml-cve-2024-35176/


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-35176
https://www.cve.org/CVERecord?id=CVE-2024-35176

Please adjust the affected versions in the BTS as needed.

Bug#1071579: RFS: tla/1.3.5+dfsg1-5 [QA] [RC] -- GNU Arch revision control system

[Bo YU]

Hi pere!

On Wed, May 22, 2024 at 4:15 PM Petter Reinholdtsen  wrote:
>
> If you want me to sponsor it, my preferences are listed in

Thanks for your sponsor for this package and your works on this package.

> http://www.hungry.com/~pere/debian-sponsoring.html >.

I have read the page and I agree with the statement from the page.

I am worried about one thing is whether if I should drop lintian's
error about the orphaned package to meet your sponsor standard. My
initial goal is to fix the FTBFS issue but never thought the upload
will bring lintian error. It seems the package needs to be repacked to
fix the lintian error.

Or we first upload it to fix the FTBFS issue on some arches and then
raise one serious reportbug to remind the license issue(if true).

BR,
Bo


>
> --
> Happy hacking
> Petter Reinholdtsen
>

Bug#1071625: "Error: cannot change the containment to AppletsLayout" is printed when LANG differs from en_US.UTF8

[Roberto]

Package: plasma-workspace
Version: 4:5.27.10-3+b1
Severity: normal
X-Debbugs-Cc: r087...@yahoo.it

Dear Maintainer,

plasmashell prints the error:

org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment 
to AppletsLayout

hangs for several seconds if executed with LANG=C or with LANG=it_IT.UTF8

it does not when LANG=en_US.UTF8


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

Kernel: Linux 6.6.13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]   1.15.4-1
ii  drkonqi5.27.10-1+b1
ii  frameworkintegration   5.115.0-4
ii  gdb-minimal [gdb]  13.2-1
ii  init-system-helpers1.66
ii  iso-codes  4.16.0-1
ii  kactivitymanagerd  5.27.10-1+b1
ii  kded5  5.115.0-2
ii  kinit  5.115.0-2
ii  kio5.115.0-5
ii  kpackagetool5  5.115.0-2
ii  kwin-common4:5.27.10-1+b1
ii  libappstreamqt5-3  1.0.3-1
ii  libc6  2.38-11
ii  libcolorcorrect5   4:5.27.10-3+b1
ii  libcrypt1  1:4.4.36-2
ii  libfontconfig1 2.15.0-1.1
ii  libfreetype6   2.13.2+dfsg-1+b4
ii  libgcc-s1  14-20240330-1
ii  libgps30t643.25-3+b1
ii  libice62:1.0.10-1
ii  libicu72   72.1-2
ii  libkf5activities5  5.115.0-3
ii  libkf5activitiesstats1 5.115.0-2
ii  libkf5archive5 5.115.0-2
ii  libkf5authcore55.115.0-2
ii  libkf5baloo5   5.115.0-2
ii  libkf5bookmarks5   5.115.0-2
ii  libkf5calendarevents5  5.115.0-3
ii  libkf5completion5  5.115.0-2
ii  libkf5config-bin   5.115.0-2
ii  libkf5configcore5  5.115.0-2
ii  libkf5configgui5   5.115.0-2
ii  libkf5configwidgets5   5.115.0-2
ii  libkf5coreaddons5  5.115.0-2
ii  libkf5crash5   5.115.0-2
ii  libkf5dbusaddons5  5.115.0-2
ii  libkf5declarative5 5.115.0-3
ii  libkf5globalaccel-bin  5.115.0-2
ii  libkf5globalaccel5 5.115.0-2
ii  libkf5guiaddons5   5.115.0-2
ii  libkf5holidays51:5.115.0-2
ii  libkf5i18n55.115.1-2
ii  libkf5iconthemes5  5.115.0-2
ii  libkf5idletime55.115.0-2
ii  libkf5jobwidgets5  5.115.0-2
ii  libkf5kcmutils55.115.0-3
ii  libkf5kexiv2-15.0.023.04.2-2+b1
ii  libkf5kiocore5 5.115.0-5
ii  libkf5kiofilewidgets5  5.115.0-5
ii  libkf5kiogui5  5.115.0-5
ii  libkf5kiowidgets5  5.115.0-5
ii  libkf5networkmanagerqt65.115.0-2
ii  libkf5newstuff55.115.0-2
ii  libkf5newstuffcore55.115.0-2
ii  libkf5newstuffwidgets5 5.115.0-2
ii  libkf5notifications5   5.115.0-2
ii  libkf5notifyconfig55.115.0-2
ii  libkf5package5 5.115.0-2
ii  libkf5parts5   5.115.0-2
ii  libkf5people5  5.115.0-2
ii  libkf5peoplewidgets5   5.115.0-2
ii  libkf5plasma5  5.115.0-2
ii  libkf5plasmaquick5 

Bug#1068339: gnome-terminal: Regression - long running process will eventually block when terminal is not visible

[Detlev Zundel]

Hi,

I am not sure why I did not receive the followup e-mail from 2024-04-04.
Shouldn't it automatically have been sent to me as the original
reporter?

Just today I eventually found the answer by accident and indeed, it
seems to be the same bug.

I can also confirm that the problem does not appear anymore with this package:

ii  libvte-2.91-0:amd64 0.75.92-1amd64Terminal emulator widget for 
GTK+ 3.0 - runtime files

So the bug can be closed.

Thanks!
  Detlev

Bug#1071624: diaspora-installer: fails to install: sigar_util.c:980:5: error: implicit declaration of function 'gettimeofday'

[Andreas Beckmann]

Package: diaspora-installer
Version: 0.7.18.2+debian4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

...
  current directory:
  
/var/lib/diaspora/vendor/bundle/ruby/3.1.0/gems/kostya-sigar-2.0.10/bindings/ruby
  make DESTDIR\= sitearchdir\=./.gem.20240520-1412518-aa08qy
  sitelibdir\=./.gem.20240520-1412518-aa08qy
  compiling linux_sigar.c
  linux_sigar.c: In function 'sigar_os_proc_list_get':
  linux_sigar.c:604:5: warning: 'readdir_r' is deprecated
  [-Wdeprecated-declarations]
604 | while (readdir_r(dirp, , ) == 0) {
| ^
  In file included from linux_sigar.c:19:
  /usr/include/dirent.h:185:12: note: declared here
185 | extern int readdir_r (DIR *__restrict __dirp,
|^
  linux_sigar.c: In function 'sigar_proc_port_get':
  linux_sigar.c:2492:5: warning: 'readdir_r' is deprecated
  [-Wdeprecated-declarations]
   2492 | while (readdir_r(dirp, , ) == 0) {
| ^
  /usr/include/dirent.h:185:12: note: declared here
185 | extern int readdir_r (DIR *__restrict __dirp,
|^
  linux_sigar.c:2533:9: warning: 'readdir_r' is deprecated
  [-Wdeprecated-declarations]
   2533 | while (readdir_r(fd_dirp, _dbuf, _ent) == 0) {
| ^
  /usr/include/dirent.h:185:12: note: declared here
185 | extern int readdir_r (DIR *__restrict __dirp,
|^
  linux_sigar.c: In function 'sigar_cpu_list_get':
  linux_sigar.c:440:11: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
440 | (void)fgets(cpu_total, sizeof(cpu_total), fp);
|   ^~~
  linux_sigar.c: In function 'get_iostat_procp':
  linux_sigar.c:1349:11: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   1349 | (void)fgets(buffer, sizeof(buffer), fp); /* skip header */
|   ^
  linux_sigar.c: In function 'sigar_net_route_list_get':
  linux_sigar.c:1721:11: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   1721 | (void)fgets(buffer, sizeof(buffer), fp); /* skip header */
|   ^
  linux_sigar.c: In function 'sigar_net_interface_stat_get':
  linux_sigar.c:1764:5: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   1764 | fgets(buffer, sizeof(buffer), fp);
| ^
  linux_sigar.c:1765:5: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   1765 | fgets(buffer, sizeof(buffer), fp);
| ^
  linux_sigar.c: In function 'proc_net_read':
  linux_sigar.c:1929:5: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   1929 | fgets(buffer, sizeof(buffer), fp); /* skip header */
| ^
  linux_sigar.c: In function 'sigar_arp_list_get':
  linux_sigar.c:2410:11: warning: ignoring return value of 'fgets' declared with
  attribute 'warn_unused_result' [-Wunused-result]
   2410 | (void)fgets(buffer, sizeof(buffer), fp); /* skip header */
|   ^
  linux_sigar.c: In function 'xen_vendor_parse':
  linux_sigar.c:2710:25: warning: '%s' directive output may be truncated writing
  up to 255 bytes into a region of size 246 [-Wformat-truncation=]
   2710 |  "XenServer %s",
| ^~
  In file included from /usr/include/stdio.h:964,
   from linux_sigar.c:20:
  In function 'snprintf',
  inlined from 'xen_vendor_parse' at linux_sigar.c:2708:5:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note:
  '__builtin___snprintf_chk' output between 11 and 266 bytes into a destination 
of
  size 256
 54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
|  ^~~~
 55 |__glibc_objsize (__s), __fmt,
|~
 56 |__va_arg_pack ());
|~
  linux_sigar.c: In function 'get_linux_vendor_info.isra':
  linux_sigar.c:2783:22: warning: '%s' directive output may be truncated writing
  up to 255 bytes into a region of size between 0 and 255 [-Wformat-truncation=]
   2783 |  

Bug#1071623: tree-sitter-c-src: New upstream version available

[Hilko Bengen]

Package: tree-sitter-c-src
Version: 0.20.5-2
Severity: normal
X-Debbugs-Cc: none, Hilko Bengen 

Dear Maintainer,

at the time of writing this, versions 0.20.8 and 0.21.1 of tree-sitter-c
have been released. Assuming semver, it's probably best to stay on
0.20.x as long as tree-sitter itself is on 0.20.

I stumbled across this because I ran into problems when packaging rizin
0.7.3 without relying on vendored build-dependencies.

Here's a simple debian/watch that would have found the 0.20.x updates:

,
| version=4
| opts="filenamemangle=s%(?:.*?)?v?(@ANY_VERSION@@ARCHIVE_EXT@)%@PACKAGE@-$1%" \
| https://github.com/tree-sitter/tree-sitter-c/tags \
| (?:.*?/)v?(0[.]20[.][0-9]*)@ARCHIVE_EXT@
`

Cheers,
-Hilko

Bug#1053905: Docs out of step

[Dan Jacobson]

$ apt-show-versions -r emacs
emacs:all/bookworm-backports 1:29.3+1-3~bpo12+1 uptodate
emacs-bin-common:arm64/bookworm-backports 1:29.3+1-3~bpo12+1 uptodate
emacs-common:all/bookworm-backports 1:29.3+1-3~bpo12+1 uptodate
emacs-common-non-dfsg:all/stable 1:28.2+1-2 uptodate  28!
emacs-el:all/bookworm-backports 1:29.3+1-3~bpo12+1 uptodate
emacs-pgtk:arm64/bookworm-backports 1:29.3+1-3~bpo12+1 uptodate
emacsen-common:all/stable 3.0.5 uptodate

https://unix.stackexchange.com/questions/758800/getting-emacs-common-non-dfsg-from-debian-bookworm-backports

Bug#1071622: falcosecurity-scap-dkms: missing dependency on adduser

[Andreas Beckmann]

Package: falcosecurity-scap-dkms
Version: 0.15.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up falcosecurity-scap-dkms (0.15.1-3) ...
  /var/lib/dpkg/info/falcosecurity-scap-dkms.postinst: 9: addgroup: not found
  dpkg: error processing package falcosecurity-scap-dkms (--configure):
   installed falcosecurity-scap-dkms package post-installation script 
subprocess returned error exit status 1
  Processing triggers for libc-bin (2.38-11) ...
  Errors were encountered while processing:
   falcosecurity-scap-dkms

adduser no longer gets installed transitively.


cheers,

Andreas


falcosecurity-scap-dkms_0.15.1-3.log.gz
Description: application/gzip

Bug#1071621: piuparts: fix typos in README.txt

[Carlos Henrique Lima Melara]

Package: piuparts
Severity: wishlist
Tags: patch
X-Debbugs-Cc: charlesmel...@riseup.net

Dear Maintainers, hi.

While reading the documentation, I've found some small typos. Here is a
patch to fix them. This patch is also available as a MR in salsa [1].

Cheers,
Charles

[1] https://salsa.debian.org/debian/piuparts/-/merge_requests/62
>From ba1f18fdaef1302597ffe0c1b125c55a21e37633 Mon Sep 17 00:00:00 2001
From: Carlos Henrique Lima Melara 
Date: Tue, 21 May 2024 12:04:59 -0300
Subject: [PATCH] docs: fix some typos in README.txt

---
 docs/README.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/README.txt b/docs/README.txt
index aff61a9e..2752a451 100644
--- a/docs/README.txt
+++ b/docs/README.txt
@@ -256,11 +256,11 @@ the chroot was recorded for later comparison.
 'is_testable\_' - before *installing* your package. If this script
 returns a non-zero return value, the installation of the package
 will be skipped. With a return value of 1 the test will be reported
-as successful, but with a return value if 2 it will be reported as
+as successful, but with a return value of 2 it will be reported as
 failed.
-Use this to flag packages that cannot be be tested with piuparts
+Use this to flag packages that cannot be tested with piuparts
 by design (e.g. usrmerge), require not publicly available external
-ressources (e.g. some downloader packages) or are broken beyond
+resources (e.g. some downloader packages) or are broken beyond
 repair (e.g. buggy packages in archived releases). Use the return
 value of 2 for seriously broken packages that can break piuparts.
 
-- 
2.43.0

Bug#1071276: Is 1:1.2.13.dfsg-1 affected by CVE-2023-45853, and if it is, will 1:1.3.dfsg-3.1 be backported to bookworm?

[John Waffle]

Hello,

I got a response from trivy,
https://github.com/aquasecurity/trivy/discussions/6722#discussioncomment-9518531

> Helllo @superlazyname 
> Thanks for your report!

> As you can see - we marked this vulnerability as "Status": "will_not_fix",
.
> We use will_not_fix for vulnerabilities with ignored State.
> We can't parse State description, because it deoesn't have format.

> [bookworm] - zlib (contrib/minizip not built and producing binary
packages)

> It seems that debian chose wrong state. not_affected looks more correct.
--

> Trivy supports VEX
.
> You can create VEX file to ignore this CVE.

> Regards, Dmitriy

I'll call out these particular points,

> We can't parse State description, because it doesn't have format.

> It seems that debian chose wrong state. not_affected looks more correct.

It sounds like this is some kind of incompatibility between how trivy
conceptualizes CVEs vs how Debian conceptualizes CVEs, plus a terminology
problem on the meaning of "ignored" (won't fix vs is not affected)

- Would you consider marking the vulnerability as "not_affected" instead of
"ignored"? Or does the Debian CVE tracking system not support that?

- I would agree that " [bookworm] - zlib (contrib/minizip not built and
producing binary packages)" doesn't have a standard format, but is there no
other viable way for a scanner to pick up on the CVE being ignored?

- Do you have docs to show what method should be used to properly handle
this issue being marked as "ignored"? Do you have any sample code / script
snippets you can share with me? Maybe I can submit a PR?

Maybe there is some way for trivy to notice that the issue is "ignored" and
then, for only Debian, interpret that as not_affected.

- John

On Sat, May 18, 2024 at 5:03 AM Salvatore Bonaccorso 
wrote:

> Hi John,
>
> On Fri, May 17, 2024 at 04:01:56PM -0400, John Waffle wrote:
> > This report came from a free tool, trivy, I filed a Github discussion
> about
> > it here: https://github.com/aquasecurity/trivy/discussions/6722
>
> Thanks a lot for bringing that upstream.
>
> So to add some additional datapoint: The issue araises here by maybe
> thinking zlib refers to the binary package produced. It is correct,
> for the binary package zlib then indeed you would not be vulnerable.
>
> Let me as well elaborate on the "ingored". This comes as the binary
> packages built from the *vulnerable* source, there is no point to
> force an update in bookworm and older.
>
> I hope this all get a better picture now on the CVE. If you still have
> questions feel free to ask.
>
> Regards,
> Salvatore
>

Bug#1071620: libchicken-dev: depends on obsolete libpcre3-dev package

[Emilio Pozuelo Monfort]

Package: libchicken-dev
Version: 5.3.0-1.1
Severity: serious

Hi,

pcre3 is being removed. libchicken-dev depends on libpcre3-dev, however
it looks like that dependency is unused. The headers don't mention it
and pcre3 support was removed in version 4.8.0.5-1 (bug #729144). Looks
like libpcre3-dev was only removed from build-depends but not from
libchicken-dev's depends.

Cheers,
Emilio

Bug#1071220: netplan.io: autopkgtest fails with systemd 256

[Luca Boccassi]

On Wed, 22 May 2024 12:38:37 +0100 Luca Boccassi 
wrote:
> On Wed, 22 May 2024 09:23:11 +0200 =?UTF-8?Q?Lukas_M=C3=A4rdian?=
>  wrote:
> > Hi Luca, thanks for the NMU.
> > 
> > Am 22.05.24 um 02:48 schrieb Luca Boccassi:
> > > Given this has been an issue for a week and it now stops systemd
> from
> > > migrating to test, I have uploaded to DELAYED/1 with urgency=high
a
> > > patch to disable this test. MR on Salsa:
> > > 
> > > https://salsa.debian.org/debian/netplan.io/-/merge_requests/14
> > 
> > Sorry, I was traveling and didn't have time to look into this, yet.
> > 
> > Having a closer look, this sounds like a real regression in
systemd-
> udev.
> > Did you double-check that "ReceiveChecksumOffload=" (inside a
.link)
> file
> > is working properly with systemd v256 in unstable?
> > 
> > Netplan's tests seem to work in unstable, except when the new
systemd
> is pulled in.
> > It fails for Netplan's sd-networkd & NetworkManager backends,
because
> both make use of
> > systemd-udev .link files. There's no special handling for
> NetworkManager here.
> > 
> > It's OK to have it temporarily disable to make systemd migrate, but
> I'll probably
> > revert the patch after merging your NMU in the packaging repo..
> > Please try to get this resolved in systemd, before the next upload.
> 
> If it's an actual problem please file an issue upstream with all the
> details, and a reproducer that doesn't require netplan, I don't
really
> know how these offload options are supposed to be handled.

Yu says:

> https://github.com/canonical/netplan/blob/26d2591d771cb4343c06dbb1e0eb1f3587ec910d/netplan_cli/cli/commands/apply.py#L257
> 
> Here, "--action add" is necessary, otherwise the generated .link
> files will be never applied to existing interfaces.

So it looks like a problem in netplan. If you can take care of that
today I'll cancel the NMU, otherwise if it's ok I'll let that through
to get the migration going.

-- 
Kind regards,
Luca Boccassi


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

Bug#1071391: beep.1: some remarks and editorial changes for this man page

[Hans Ulrich Niedermann]

On 2024-05-18 12:51 +, Bjarni Ingi Gislason 
wrote:

> Dear Maintainer,
> 
> here are some notes and editorial fixes for the manual.

Thank you very much!

That looks very interesting. I know a few things about writing man
pages, but you have listed many more things here which I had always
been looking for, both in how to write a man page and in which tools
can be helpful there.

I will work through the points you have raised in upstream eventually,
but that will take a bit of time due to the number of points.

I am tracking this upstream
at https://github.com/spkr-beep/beep/issues/40 but will continue to
monitor and reply via email to 1071...@bugs.debian.org.

Whenever possible, I want to upstream improvements so that all distro
packages for many distributions can benefit from them, and that is my
plan here as well.

Gruß,

Hans Ulrich Niedermann
(maintainer of beep upstream, not of the Debian package)

Bug#1071619: fortunes-it: English language fortune

[Anthony Foglia]

Package: fortunes-it
Version: 2.4-2
Severity: minor

Another English language fortune I stumbled across. In
.../fortunes/computer, line 578:

> Message from Talk_Daemon@localhost at 21:42 ...
> talk: connection requested by fortune@localhost.
> talk: respond with:  talk fortune@localhost

I get that it's pretending to be a talk message (there's even a leading ^G
to ring the terminal bell), but it's not in Italian, so it shouldn't be in
the Italian fortunes.


And randomly jumping in the file, I found another one at line 1321.

> Test.
>   -- Test

Bug#1071618: kannel-dev: depends on obsolete libpcre3-dev

[Emilio Pozuelo Monfort]

Package: kannel-dev
Version: 1.4.5-16
Severity: serious

Hi,

kannel-dev depends on libpcre3-dev, which is going to be removed. Given pcre3
support was removed in 1.4.5-13, that dependency can probably just go away.

Cheers,
Emilio

Bug#1071581: dialog: stop using libtool-bin

[Helmut Grohne]

Hi Thomas,

On Wed, May 22, 2024 at 03:53:43AM -0400, Thomas Dickey wrote:
> I don't use autoheader (though it's present in the fork I've maintained for
> about the past quarter-century).  The configure script generates the complete
> dlg_config.h without that crutch.  Attempting to bypass that will certainly
> lead to unnecessary bug reports.

I fear it occurred to me late that I should be using autoconf-dickey
instead of the standard autoconf for dialog. Hence my patch makes it
work the "wrong" autoconf and thus runs autoheader. I see how that would
not be necessary with autoconf-dickey.

> Actually it would be AC_FOREACH, which invokes AH_TEMPLATE
> 
> fwiw, CF_CURSES_FUNCS predates that stuff (1997 versus 1999),
> and there are other macros which might use those features.

Yeah. And if you make dialog work with autoconf-dickey and without
autoheader, then all of this becomes moot anyway.

Feel free to come up with a different solution as long as we stop
relying on /usr/bin/libtool as that's the component that will go away.
We now have one working solution and I'm happy if that is sufficient to
get the ball rolling for a better solution than mine.

Helmut

Bug#1071617: ITP: cached-ipaddress -- Cache construction of IP address objects

[Edward Betts]

Package: wnpp
Severity: wishlist
Owner: Edward Betts 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: cached-ipaddress
  Version : 0.3.0
  Upstream Author : J. Nick Koston 
* URL : https://github.com/bdraco/cached-ipaddress
* License : MIT
  Programming Lang: Python
  Description : Cache construction of IP address objects

  Provides a caching mechanism for Python IP address objects.  This module
  caches the construction of IP address objects and their properties, making
  it efficient when dealing with frequently encountered IP addresses.
  .
  The cache is useful for reducing the overhead associated with creating and
  accessing properties of IP address objects repeatedly.

I plan to maintain this package as part of the Python team.

Bug#1071616: RM: octave-mpi -- ROM; FTBFS; not in testing for 2 years; mostly dead upstream

[Sébastien Villemot]

Package: ftp.debian.org
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: octave-...@packages.debian.org, debian-oct...@lists.debian.org
Control: affects -1 + src:octave-mpi
User: ftp.debian@packages.debian.org
Usertags: remove

Dear ftpmasters,

Please remove octave-mpi:
– its last upstream release was in 2020;
– it has not been in testing for more than 2 years;
– it is incompatible with the last three major versions of Octave, and upstream
  has not provided a fix.

Thanks,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1071595: it was a printer firmware problem

[Sanjoy Mahajan]

I have just updated the printer's firmware (from a 2015 to a 2020 one).
Now it prints in duplex mode with no complaints.  So, it was almost
certainly a printer bug rather than a CUPS bug.

-- 
-Sanjoy

Bug#1071615: lesskey.1: some remarks and editorial changes for this man page

[Bjarni Ingi Gislason]

Package: less
Version: 643-1
Severity: minor
Tags: patch

Dear Maintainer,

  here are some notes and editorial fixes for the manual.

The patch is in the attachment.

-.-

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "

instead of "nroff -man"

  Add the option "-t", if the file contains a table.

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual for warnings,
the following must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint lesskey.1": (possibly shortened list)

mandoc: lesskey.1:14:42: STYLE: whitespace at end of input line
mandoc: lesskey.1:19:24: STYLE: whitespace at end of input line
mandoc: lesskey.1:23:24: STYLE: whitespace at end of input line
mandoc: lesskey.1:24:12: STYLE: whitespace at end of input line
mandoc: lesskey.1:32:2: WARNING: skipping paragraph macro: PP empty
mandoc: lesskey.1:129:29: STYLE: whitespace at end of input line
mandoc: lesskey.1:132:2: ERROR: skipping unknown macro: .less
mandoc: lesskey.1:371:86: STYLE: input text line longer than 80 bytes: If a 
line begins wit...
mandoc: lesskey.1:380:76: STYLE: whitespace at end of input line
mandoc: lesskey.1:383:86: STYLE: input text line longer than 80 bytes: Then the 
following l...

-.-.

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

14:This document describes the format of the 
19:In previous versions of 
23:was used to compile the 
24:.B lesskey 
129:default command keys used by 
234:## Use a long option name by starting the 
380:For example, suppose that a new command named 'sideways-search' is added in 

-.-.

Change two HYPHEN-MINUSES (code 0x2D) to an em-dash (\(em),
if one is intended.  An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.
"man" (1 byte characters in input) transforms an en-dash (\(en) to one
HYPHEN-MINUS,
and an em-dash to two HYPHEN-MINUSES without considering the space
around it.
If "--" are two single "-" (end of options) then use "\-\-".

lesskey.1:419:  ##  to separate the --color option from the -S option.)

-.-.

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

419:##  to separate the --color option from the -S option.)

-.-.

Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.

236:##   s toggle-option -log-file\en
419:##  to separate the --color option from the -S option.)

-.-.

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

385:which support it. The line would be ignored by versions earlier than 777.

-.-.

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

lesskey.1: line 85 length 101
\ek followed by a single character represents the char(s) produced when one of 
these keys is pressed:

lesskey.1: line 371 length 86
If a line begins with #version followed by a relational operator and a version 
number,

lesskey.1: line 383 length 86
Then the following line would assign the command to the Q key, but only in 
versions of

-.-

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

128:## Use a long option name by starting the 

-.-.

Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff 

Bug#1069557: libkdumpfile: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

[Petr Tesařík]

On Wed, 1 May 2024 11:59:13 -0500 Michel Lind  wrote:
> Hi Lucas,
> 
> On 4/20/24 8:23 AM, Lucas Nussbaum wrote:
> > Source: libkdumpfile
> > Version: 0.5.4-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on armel.
> Thanks for filing. I've notified upstream: 
> https://github.com/ptesarik/libkdumpfile/issues/80
> 
> and will try and reproduce and fix this.

FYI I am able to reproduce the failure, and it seems to be related to
some sort of link-time remapping of mmap() to mmap64(). I don't have
time to look into the details, but to prvent removal of the package
from Debian testing, you can add CFLAGS=-D_FILE_OFFSET_BITS=64 as
parameter to ./configure.

HTH
Petr T

Bug#1071236: general: keyboard, mouse, and trackpad behave inconsistently; seemingly phantom input device events occur unpredictably

[Ben Hutchings]

On Wed, 2024-05-22 at 00:41 +0200, Salvo Tomaselli wrote:
> Hello,
> 
> you can run "reportbug packagename" to report against a specific package.
> 
> You can find out how your kernel package is called with 
> 
> dpkg -l "linux-image-*"

That step isn't necessary because "reportbug kernel" automagically does
the right thing.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes
instead of old ones.



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

Bug#1071614: transition: libmatio13

[Sébastien Villemot]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libma...@packages.debian.org
Control: affects -1 + src:libmatio
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-libmatio.html

Dear Release Team,

Please schedule a transition for libmatio.

I’ve successfully rebuilt all reverse dependencies against the new version
(currently in experimental), except gnss-sdr and labplot which are currently
unbuildable due to the qt5 transition.

Thanks,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1071200: git-buildpackage: gbp import-orig: support filtering based on debian/clean

[Guido Günther]

Hi,
On Mon, May 20, 2024 at 04:16:49PM -0400, Daniel Kahn Gillmor wrote:
> On Sun 2024-05-19 20:43:58 +0200, Guido Günther wrote:
> > But you'd break that when filtering out files? I think what keeps me
> > confused: the tarball uploaded to Debian is the filtered one and hence
> > has a different checksum, no? 
> 
> hm, i don't think so, because we use
> import-orig.filter-pristine-tar=False.  This lets me preserve both the

Ah...now I get it. You filter the branch but let pristine-tar take care
of restoring the original tarball.

[..snip..]

> > Another reason to not parse debian/clean verbatim is that we'd also need
> > to support dh's substitution variables and would forever need to follow
> > what dh does (and we might even need to pay attention to the dh compat
> > level of the package) as otherwise things would break on people.
> 
> you've convinced me that running the clean target is better than trying
> to parse debian/clean :)

Great! Let's try that path then.

> 
> >> whether the packaging used debhelper or not.  Does that seem like a
> >> plausible way to operate gbp import-orig?
> >
> > That would be an approach. Implementation wise the "tricky" bit is
> > that you don't have debian/ on the upstream branch you want to filter so
> > dh_clean or `debian/rules clean` won't work as is . So we'd need to
> > overlay that (which is certainly doable, just wanted to point it out).
> 
> ah, yes, i see the complication here.
> 
> > So that's a lot of effort for s.th. that can already be done via either
> > gbp.conf or FilesExcluded. I'm not against it, just looking at the pros
> > and cons.
> 
> right, i see tradeoff you're describing, and if you decide this is too
> much complication for gbp, i'm willing to just keep the two lists
> (debian/clean and debian/gbp.conf's import-orig.filter) in sync more or
> less manually.

I'm fine with the complication. Just wanted to point out possible
implementation pitfalls. Just to be sure: It's unlikely that I'll be
able to look at an implementation myself near term.

> Thanks for thinking this all through with me here, Guido!

Thanks for explaining your workflow!
 -- Guido

Bug#1071613: octave-dev: Inconsistent behavior of %!error and mexErrMsgIdAndTxt on different architectures

[Rafael Laboissière]

Package: octave-dev
Version: 9.1.0-3
Severity: normal
Tags: upstream
Control: forwarded -1 https://savannah.gnu.org/bugs/?65767
Control: block 1069477 by -1

Hi,

A bug has been reported in the upstream bug system for Octave [1], 
with all the details, concerning a possible problem related to the 
compilation of MEX files. This problem probably causes the FTBFS of 
octave-stk (Bug#1069477 [2]).

Best,

Rafael Laboissière

 [1] https://savannah.gnu.org/bugs/?65767
 [2] https://bugs.debian.org/1069477

Bug#1071612: ITP: libterm-ansicolor-concise-perl -- Term::ANSIColor - Color screen output using ANSI escape sequences

[Bruno Gabriel da Fonseca]

Package: wnpp
Severity: wishlist
Owner: Bruno Gabriel da Fonseca 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: libterm-ansicolor-concise-perl
  Version : 2.06
  Upstream Contact: Kazumasa Utashiro
* URL : https://metacpan.org/pod/Term::ANSIColor::Concise
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Term::ANSIColor - Color screen output using ANSI escape 
sequences

This module provides a simple concise format to describe complicated colors and 
effects for ANSI terminals. These notations are supposed to be used in command 
line option parameters.

This module used to be a part of Getopt::EX::Colormap module, which provide 
easy handling interface for command line options.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#1071611: conky-all: horizontal border are lost

[Dieter Faulbaum]

Package: conky-all
Version: 1.21.1-1
Severity: minor

Dear Maintainer,

after upgrading to version 1.12.0 (and than to 1.21.1) the horizontal borders
aren't shown anymore.
The vertical borders are visible.

I use cinnamon (under X). In a VM with LXDE it's the same.


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

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=de_DE.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 conky-all depends on:
ii  libaudclient23.5~rc2-2+b1
ii  libc62.38-11
ii  libcairo21.18.0-3+b1
ii  libcurl3t64-gnutls   8.7.1-5
ii  libdbus-glib-1-2 0.112-3+b2
ii  libfontconfig1   2.15.0-1.1
ii  libgcc-s114-20240330-1
ii  libglib2.0-0t64  2.80.2-1
ii  libical3t64  3.0.18-1
ii  libimlib2t64 1.12.1-1.1
ii  libircclient11.9-1+b2
ii  libiw30t64   30~pre9-17
ii  liblua5.3-0  5.3.6-2+b2
ii  libncurses6  6.5-2
ii  libpango-1.0-0   1.52.2+ds-1
ii  libpangocairo-1.0-0  1.52.2+ds-1
ii  libpangoft2-1.0-01.52.2+ds-1
ii  libpulse016.1+dfsg1-5
ii  librsvg2-2   2.58.0+dfsg-1
ii  libstdc++6   14-20240330-1
ii  libtinfo66.5-2
ii  libwayland-client0   1.22.0-2.1+b1
ii  libx11-6 2:1.8.7-1+b1
ii  libxdamage1  1:1.1.6-1+b1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2+b1
ii  libxft2  2.3.6-1+b1
ii  libxinerama1 2:1.1.4-3+b1
ii  libxml2  2.9.14+dfsg-1.3+b3
ii  libxnvctrl0  535.171.04-1

conky-all recommends no packages.

Versions of packages conky-all suggests:
pn  apcupsd
ii  audacious  4.3.1-2.1+b1
pn  moc
pn  mpd

-- no debconf information