Bug#1033642: ssh: deprecated option PubkeyAcceptedKeyTypes

[Gabriel F. T. Gomes]

Thanks, Matthias,

I submitted a patch upstream to get the feedback from the upstream [1]
developers. I hope they accept it; if they do, it's easier for me to
backport. Cheers, Gabriel.

[1] https://github.com/scop/bash-completion/pull/922

On Wed, 29 Mar 2023 11:40:09 +0200
Matthias Geerdsen  wrote:

> Package: bash-completion
> Version: 1:2.11-6
> Severity: minor
> 
> Hi,
> 
> completion for the ssh command offers PubkeyAcceptedKeyTypes as an option,
> which has been renamed to PubkeyAcceptedAlgorithms in openssh 8.5
> (https://www.openssh.com/txt/release-8.5), which makes this relevant starting
> from bookworm.
> The old option is not mentioned in the manpage anymore but is still valid, so
> the bash-completion is not wrong but a bit confusing.
> 
> Thanks
> Matthias
> 
> 
> -- System Information:
> Debian Release: 12.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing'), (50, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_USER, 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
> 
> -- no debconf information

Bug#1033847: Please update to upstream sources

[Gabriel F. T. Gomes]

Hi Richard,

thanks for your report.

With respect to the package being outdated, I realize that the sources
have not been sync'd with upstream for a long while, but that's because
upstream has not released any versions (no tags) since 2.11; and I
always wait for upstream releases before syncing. From time to time, I
do some backporting (cherry-pick); though I have a somewhat long list of
request from other users that I haven't applied yet, but plan to do so
soon.

Now with respect to the problem you're getting with the readline patch,
could you provide more details about your freezes? Maybe a directory
structure and files, as well as the pattern you are trying to complete?
That would help me reproduce the problem. I don't want to remove the
patch all of a sudden, because it's been there since a long time (since
before I was the maintainer).

Best regards,
Gabriel

Bug#1034132: unblock: dpmb/0~2023.03.11

[Axel Beckert]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: d...@packages.debian.org
Control: affects -1 + src:dpmb

Please unblock package dpmb/0~2023.03.11

DPMB = Debian Packaging Management (E-)Book

[ Reason ]

Content of the e-book has been updated for the Bookworm release,
describing changes like non-free-firmware, Stretch being now ELTS,
vrms has been renamed to check-dfsg-status, etc.

Sections about package management related packages which are no more
in any supported Debian release have been removed from the book.

[ Impact ]

Without the update, changes in Bookworm won't be covered in Bookworm.

[ Tests ]

The e-book (and package) built fine on Sid in three different types of
environment: locally, local minimal pbuilder chroot as well as on the
buildd.

Buildd-built HTML, EPUB and PDF variants have been skimmed through for
proper formatting. (HTML with Chromium, EPUB and PDF with mupdf.)

The Mobi version for Kindle devices hasn't been checked as I don't
have a Kindle device. But is converted from the EPUB version using
Calibre's ebook-convert.

[ Risks ]

Other book content has been updated or expanded, too. Changed or added
content might have introduced typos or other content issues.

[ Checklist ]
  [x] all (non-content) changes are documented in the d/changelog
  [x] I made all (non-content) changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

debdiff of the non-content changes:

diff -Nru dpmb-0~2021.03.01/debian/changelog dpmb-0~2023.03.11/debian/changelog
--- dpmb-0~2021.03.01/debian/changelog  2021-03-01 00:56:34.0 +0100
+++ dpmb-0~2023.03.11/debian/changelog  2023-03-12 00:34:38.0 +0100
@@ -1,3 +1,16 @@
+dpmb (0~2023.03.11) unstable; urgency=medium
+
+  * The Debian 12 Bookworm Edition.
++ Covers non-free-firmware archive section.
++ Debian 9 Stretch is now ELTS.
+  * Bracketize sole lintian override so far.
+  * Add lintian override for very-long-line-length-in-source-file on
+binary file and handwritten Markdown files with a few long semantic
+HTML oneliners.
+  * Declare compliance with Debian Policy 4.6.2. (No changes needed.)
+
+ -- Axel Beckert   Sat, 11 Mar 2023 23:34:38 +
+
 dpmb (0~2021.03.01) unstable; urgency=medium
 
   * New snapshot
diff -Nru dpmb-0~2021.03.01/debian/control dpmb-0~2023.03.11/debian/control
--- dpmb-0~2021.03.01/debian/control2021-02-03 04:27:56.0 +0100
+++ dpmb-0~2023.03.11/debian/control2023-03-12 00:32:59.0 +0100
@@ -10,7 +10,7 @@
  dblatex,
  texlive-lang-german,
  xmlto
-Standards-Version: 4.5.1
+Standards-Version: 4.6.2
 Homepage: https://www.dpmb.org/
 Vcs-Git: https://github.com/dpmb/dpmb.git
 Vcs-Browser: https://github.com/dpmb/dpmb
diff -Nru dpmb-0~2021.03.01/debian/lintian-overrides 
dpmb-0~2023.03.11/debian/lintian-overrides
--- dpmb-0~2021.03.01/debian/lintian-overrides  2016-06-29 23:15:14.0 
+0200
+++ dpmb-0~2023.03.11/debian/lintian-overrides  2023-03-12 00:20:22.0 
+0100
@@ -1,2 +1,2 @@
 # Feature request against doc-base, see https://bugs.debian.org/730240
-debian-paketmanagement-buch: doc-base-file-unknown-format 
debian-paketmanagement-buch:14 epub
+debian-paketmanagement-buch: doc-base-file-unknown-format epub 
[usr/share/doc-base/debian-paketmanagement-buch.debian-paketmanagement-buch:14]
diff -Nru dpmb-0~2021.03.01/debian/source/lintian-overrides 
dpmb-0~2023.03.11/debian/source/lintian-overrides
--- dpmb-0~2021.03.01/debian/source/lintian-overrides   1970-01-01 
01:00:00.0 +0100
+++ dpmb-0~2023.03.11/debian/source/lintian-overrides   2023-03-12 
00:28:25.0 +0100
@@ -0,0 +1,6 @@
+# Binary file
+dpmb source: very-long-line-length-in-source-file 1296 > 512 
[praxis/apt-cache/apt-cache.dia:2]
+
+# Handwritten Markdown with a few long semantic HTML oneliners
+dpmb source: very-long-line-length-in-source-file * > 512 [README.mdwn:64]
+very-long-line-length-in-source-file * > 512 [LICENSE.md:3]

Full debdiff attached.

So please

unblock dpmb/0~2023.03.11

Thanks in advance!


dpmb_0~2021.03.01_0~2023.03.11.dsc.debdiff.xz
Description: application/xz

Bug#1034131: unblock: chromium/112.0.5615.49-2

[Andres Salomon]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: chrom...@packages.debian.org
Control: affects -1 + src:chromium

Please unblock package chromium so that it migrates to bookworm after 5 
days. The upload to unstable fixes another set of 14 CVEs.


Thanks,
Andres

Bug#1034130: unblock: wxpython4.0/4.2.0+dfsg-3

[Scott Talbert]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: wxpython...@packages.debian.org
Control: affects -1 + src:wxpython4.0

Please unblock package wxpython4.0

[ Reason ]
Remove reference to non-existent package (wx3.0-doc).

[ Impact ]
wxpython4.0 will get shipped with a Suggests for a non-existent package.

[ Tests ]
None.

[ Risks ]
Changes are trivial.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
None

unblock wxpython4.0/4.2.0+dfsg-3
diff -Nru wxpython4.0-4.2.0+dfsg/debian/changelog 
wxpython4.0-4.2.0+dfsg/debian/changelog
--- wxpython4.0-4.2.0+dfsg/debian/changelog 2023-02-23 19:34:57.0 
-0500
+++ wxpython4.0-4.2.0+dfsg/debian/changelog 2023-03-15 20:27:44.0 
-0400
@@ -1,3 +1,9 @@
+wxpython4.0 (4.2.0+dfsg-3) unstable; urgency=medium
+
+  * d/control: update wx3.0-doc Suggests to wx3.2-doc (Closes: #1032867)
+
+ -- Scott Talbert   Wed, 15 Mar 2023 20:27:44 -0400
+
 wxpython4.0 (4.2.0+dfsg-2) unstable; urgency=medium
 
   * d/control: make sip-tools requirements match python3-sipbuild
diff -Nru wxpython4.0-4.2.0+dfsg/debian/control 
wxpython4.0-4.2.0+dfsg/debian/control
--- wxpython4.0-4.2.0+dfsg/debian/control   2023-02-23 19:26:38.0 
-0500
+++ wxpython4.0-4.2.0+dfsg/debian/control   2023-03-15 20:26:03.0 
-0400
@@ -33,7 +33,7 @@
 Package: python3-wxgtk4.0
 Architecture: any
 Depends: python3-pil, python3-six, ${python3:Depends}, ${shlibs:Depends}, 
${misc:Depends}
-Suggests: wx3.0-doc
+Suggests: wx3.2-doc
 Provides: ${python3:Provides}
 Description: Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit
  wxWidgets (formerly known as wxWindows) is a class library for C++ providing

Bug#1033961: dpkg: Please add support for zstd (Zstandard) compressed packages (for stable/oldstable)

[theofficialgman]

> That commit depends on several other refactors linked to the parallel

compression support for xz

Oh I see. In any case I don't see why these changes could not be made
in the -backports repositories for the requested distros. It seems
like only the 2-3 commits before you added this commit are dependent
on it.

Bug#1034129: lomiri-action-api: reproducible-builds: build paths trigger differences

[Vagrant Cascadian]

Source: lomiri-action-api
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid, as
well as some build paths embedded in documentation:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lomiri-action-api.html

  /usr/share/doc/lomiri-action-doc/qml/lomiri-action-qml-api.index.gz

  ... 
filepath="/build/1st/lomiri-action-api-1.1.2/documentation/qml/qml-api/Action.qml
  vs.
  ... 
filepath="/build/2/lomiri-action-api-1.1.2/2nd/documentation/qml/qml-api/Action.qml

The attached patches to debian/rules fix this by passing
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override and
adds a dh_installdocs override to strip the build path from the
documentation.


With these patches applied, based on my local tests, lomiri-action-api
should build reproducibly on tests.reproducible-builds.org!


Thanks for maintaining lomiri-action-api!

live well,
  vagrant
From 84bc9ecaacf07da59a4e7e0dd7a8c60870431e91 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 9 Apr 2023 17:17:57 -0700
Subject: [PATCH 1/2] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index aacdcde..5d593a5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -16,6 +16,7 @@ include /usr/share/dpkg/buildflags.mk
 override_dh_auto_configure:
 	dh_auto_configure -- -DGENERATE_DOCUMENTATION=ON	\
 	 -Duse_libhud2=OFF			\
+	 -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON	\
 	 $(NULL)
 
 override_dh_install:
-- 
2.39.2

From a27be3c625f2103b8a7efd1718ae3455fc8bb699 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 9 Apr 2023 17:20:24 -0700
Subject: [PATCH 2/2] debian/rules: Add dh_installdocs override to remove build
 path from lomiri-action-qml-api.index.

https://reproducible-builds.org/docs/build-path/
---
 debian/rules | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index 5d593a5..2de6115 100755
--- a/debian/rules
+++ b/debian/rules
@@ -25,6 +25,11 @@ override_dh_install:
 	symlinks -rc "debian/tmp/usr/share/doc/lomiri-action-doc/"
 	dh_install
 
+override_dh_installdocs:
+	dh_installdocs
+	# Remove the build directory from the generated documentation for reproducible builds
+	sed -i -e "s,$(CURDIR),,g" debian/lomiri-action-doc/usr/share/doc/lomiri-action-doc/qml/lomiri-action-qml-api.index
+
 override_dh_missing:
 	dh_missing --fail-missing
 
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#1033961: closed by Guillem Jover (Re: Bug#1033961: dpkg: Please add support for zstd (Zstandard) compressed packages (for stable/oldstable))

[theofficialgman]

The patch contents indicate that only libzstd1 >= 1.4.0 are a requirement
for the new parallel compression support. Bullseye has version 1.4.8 in the
repos and buster-backports has version 1.4.4 which are both compatible with
these changes.

Please reconsider in light of these corrections.

On Sat, Apr 8, 2023 at 7:00 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the dpkg package:
>
> #1033961: dpkg: Please add support for zstd (Zstandard) compressed
> packages (for stable/oldstable)
>
> It has been closed by Guillem Jover .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Guillem Jover <
> guil...@debian.org> by
> replying to this email.
>
>
> --
> 1033961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033961
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Guillem Jover 
> To: theofficialgman ,
> 1033961-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 8 Apr 2023 12:57:58 +0200
> Subject: Re: Bug#1033961: dpkg: Please add support for zstd (Zstandard)
> compressed packages (for stable/oldstable)
> Control: tag -1 wontfix
>
> On Tue, 2023-04-04 at 22:34:20 -0400, theofficialgman wrote:
> > Package: dpkg
> > Severity: wishlist
>
> > Please backport these changes
> > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664
> > https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b6b)
> ) into
> > debian stable (bullseye) and debian oldstable (buster). The lack of
> > tar.zst support is critical for these releases as time goes on and
> > many popular CI systems only have Ubuntu builders. The lack of tar.zst
> > support means that for many projects providing packages for debian
> > distros is not possible or too difficult.
>
> That commit depends on several other refactors linked to the parallel
> compression support for xz. But in any case this is a significant
> change, that does not seem justifiable for a stable release update.
>
> (Also building for distribution X from distribution Y, even though
> unfortunately common, is in general frowned upon, and I'd strongly
> advise against doing that anyway.)
>
> So I'm afraid, I'll have to decline this request.
>
> Regards,
> Guillem
>
>
> -- Forwarded message --
> From: theofficialgman 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 4 Apr 2023 22:34:20 -0400
> Subject: dpkg: Please add support for zstd (Zstandard) compressed packages
> (for stable/oldstable)
>
> Package: dpkg
> Severity: wishlist
>
> Dear debian developers,
>
> Please backport these changes 
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 
> https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b) into debian 
> stable (bullseye) and debian oldstable (buster). The lack of tar.zst support 
> is critical for these releases as time goes on and many popular CI systems 
> only have Ubuntu builders. The lack of tar.zst support means that for many 
> projects providing packages for debian distros is not possible or too 
> difficult.
>
> With the ease of which the backport is achievable I am politely requesting 
> that you include it in the mentioned distros at urnest.
>
> Thanks
>
>

Bug#1034117: installation-reports: Debian testing installer doesn't prepare apt sources

[Cyril Brulebois]

Hallo Julian,

Julian Groß  (2023-04-09):
> installing the image linked below, doesn't set up the apt sources.
> /etc/apt/sources.list only contains the installation media and nothing
> else (not even comments).

That's definitely not what's supposed to happen.

> Please make sure that any installation logs that you think would
> be useful are attached to this report. (You can find them in the
> installer system in /var/log/ and later on the installed system
> under /var/log/installer.) Please compress large files using gzip.

Please share /var/log/installer/syslog (compressed), as suggested by
this part of the installation report template.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1032104: linux: ppc64el iouring corrupted read

[Otto Kekäläinen]

> > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > (or later 6.1.y series versions, which will land in bookworm). That
> > > would be valuable information to know as well to exclude we do not
> > > have the issue as well in bookworm.
> >
> > Were you able to verify this?

Yes and new kernel did not fix it.

I reviewed now all ppc64el autopkgtest runs of src:mariadb at
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/

This is still happening on latest kernel and latest src:mariadb in
bookworm. The failing test varies, but they all have in common that
they error on 'Database page corruption on disk'.

autopkgtest [20:11:55]: starting date and time: 2023-04-08 20:11:55+
autopkgtest [20:12:17]: testbed running kernel: Linux
6.1.0-7-powerpc64le #1 SMP Debian 6.1.20-1 (2023-03-19)
autopkgtest [20:12:39]: testing package mariadb version 1:10.11.2-1
Completed: Failed 6/1021 tests, 99.41% were successful.
Failing test(s): main.innodb_ext_key main.statistics_upgrade_not_done

Attached summary of downloading all recent logs and running:
$ zgrep -e 'starting date' -e 'running kernel' -e 'testing package
mariadb version' -e 'Completed: ' -e 'Failing test(s)' *.gz | tee
mariadb-autopkgtest-ppc64el-summary.txt
30542346.log.gz:autopkgtest [16:38:18]: starting date and time: 2023-01-20 
16:38:18+
30542346.log.gz:autopkgtest [16:39:14]: testbed running kernel: Linux 
5.10.0-20-powerpc64le #1 SMP Debian 5.10.158-2 (2022-12-13)
30542346.log.gz:autopkgtest [16:39:30]: testing package mariadb version 
1:10.11.1-1
30542346.log.gz:Completed: All 1016 tests were successful.

31013059.log.gz:autopkgtest [23:16:23]: starting date and time: 2023-02-03 
23:16:23+
31013059.log.gz:autopkgtest [23:16:53]: testbed running kernel: Linux 
5.10.0-20-powerpc64le #1 SMP Debian 5.10.158-2 (2022-12-13)
31013059.log.gz:autopkgtest [23:17:06]: testing package mariadb version 
1:10.11.1-2
31013059.log.gz:Completed: All 1016 tests were successful.

31114152.log.gz:autopkgtest [10:00:31]: starting date and time: 2023-02-06 
10:00:31+
31114152.log.gz:autopkgtest [10:00:57]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31114152.log.gz:autopkgtest [10:01:09]: testing package mariadb version 
1:10.11.1-3
31114152.log.gz:Completed: Failed 2/1016 tests, 99.80% were successful.
31114152.log.gz:Failing test(s): main.xa_prepared_binlog_off 
main.update_use_source

31138628.log.gz:autopkgtest [06:52:36]: starting date and time: 2023-02-07 
06:52:36+
31138628.log.gz:autopkgtest [06:53:04]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31138628.log.gz:autopkgtest [06:53:17]: testing package mariadb version 
1:10.11.1-3
31138628.log.gz:Completed: All 1016 tests were successful.

31204767.log.gz:autopkgtest [12:32:51]: starting date and time: 2023-02-10 
12:32:51+
31204767.log.gz:autopkgtest [12:33:23]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31204767.log.gz:autopkgtest [12:33:46]: testing package mariadb version 
1:10.11.1-4
31204767.log.gz:Completed: Failed 2/1016 tests, 99.80% were successful.
31204767.log.gz:Failing test(s): main.innodb_ext_key main.order_by_innodb

31253808.log.gz:autopkgtest [19:05:34]: starting date and time: 2023-02-11 
19:05:34+
31253808.log.gz:autopkgtest [19:06:15]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31253808.log.gz:autopkgtest [19:06:25]: testing package mariadb version 
1:10.11.1-4
31253808.log.gz:Completed: All 1016 tests were successful.

31452860.log.gz:autopkgtest [09:50:34]: starting date and time: 2023-02-17 
09:50:34+
31452860.log.gz:autopkgtest [09:51:00]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31452860.log.gz:autopkgtest [09:51:21]: testing package mariadb version 
1:10.11.1-5
31452860.log.gz:Completed: Failed 6/1020 tests, 99.41% were successful.
31452860.log.gz:Failing test(s): main.ctype_utf8mb4_innodb 
main.index_merge_innodb

31480673.log.gz:autopkgtest [01:00:30]: starting date and time: 2023-02-18 
01:00:30+
31480673.log.gz:autopkgtest [01:01:00]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31480673.log.gz:autopkgtest [01:01:17]: testing package mariadb version 
1:10.11.2-1
31480673.log.gz:Completed: Failed 6/1021 tests, 99.41% were successful.
31480673.log.gz:Failing test(s): main.xa_prepared_binlog_off main.range_mrr_icp

31509348.log.gz:autopkgtest [05:09:32]: starting date and time: 2023-02-19 
05:09:32+
31509348.log.gz:autopkgtest [05:10:50]: testbed running kernel: Linux 
5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21)
31509348.log.gz:autopkgtest [05:11:06]: testing package mariadb version 
1:10.11.2-1
31509348.log.gz:Completed: Failed 3/1019 tests, 99.71% were successful.
31509348.log.gz:Failing test(s): main.ctype_utf8mb4_innodb

Bug#1019140: fixed in unbound 1.17.1-2

[Thomas Deutschmann]

Hi,

any reason why you didn't apply same fix to 
|do_root_trust_anchor_updatefunction or did you just miss that function?|


|
|

|Regards,
Thomas
|

Bug#1034117: (no subject)

[Julian Groß]

Turns out that this is an “assumption” problem and not a bug.

I assumed that the default behaviour would be to set up sources.
Turns out that the default behaviour of the installer is to *not* set up 
the sources, but only set up the installation media as a source.


Having the option for that seems sane, but shouldn't setting up network 
sources be the default selection?
It seems to me that 99% of the time, people will want apt to be able to 
get packages from outside the installation media.


OpenPGP_0xAF605C87F9E5AE94.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034128: memcached breaks cachelib autopkgtest: TimeoutError

[Paul Gevers]

Source: memcached, cachelib
Control: found -1 memcached/1.6.19-1
Control: found -1 cachelib/0.9.0-1
Severity: serious
Tags: sid bookworm bookworm-ignore
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of memcached the autopkgtest of cachelib fails in 
testing when that autopkgtest is run with the binary packages of 
memcached from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
memcached  from testing1.6.19-1
cachelib   from testing0.9.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of memcached to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package? [Release Team member hat on] 
Because we're currently in the hard freeze for bookworm, I have marked 
this bug as bookworm-ignore. Targeted fixes are still welcome.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=memcached

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cachelib/32723565/log.gz

=== python3.11 ===
= test session starts 
==

platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp
plugins: xprocess-0.22.2
collected 120 items / 1 skipped

tests/test_base_cache.py  
[ 10%]
tests/test_file_system_cache.py  
[ 43%]
 
[ 50%]
tests/test_interface_uniformity.py E 
[ 50%]
tests/test_memcached_cache.py EEE 
[ 60%]
tests/test_redis_cache.py .. 
[ 78%]
tests/test_simple_cache.py .. 
[100%]


 ERRORS 

__ ERROR at setup of 
TestInterfaceUniformity.test_types_have_all_base_methods __


xprocess = 

@pytest.fixture(scope="class")
def memcached_server(xprocess):
package_name = "pylibmc"
pytest.importorskip(
modname=package_name, reason=f"could not find python 
package {package_name}"

)
class Starter(ProcessStarter):
pattern = "server listening"
args = ["memcached", "-vv"]
def startup_check(self):
out = subprocess.run(["memcached"], stderr=subprocess.PIPE)
return b"Address already" in out.stderr
>   xprocess.ensure(package_name, Starter)

tests/conftest.py:72: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/xprocess/xprocess.py:282: in ensure

if not starter.wait(log_file_handle):
/usr/lib/python3/dist-packages/xprocess/xprocess.py:399: in wait
has_match = any(std.re.search(self.pattern, line) for line in lines)
/usr/lib/python3/dist-packages/xprocess/xprocess.py:399: in 
has_match = any(std.re.search(self.pattern, line) for line in lines)
/usr/lib/python3/dist-packages/xprocess/xprocess.py:405: in 
non_empty_lines = (x for x in lines if x.strip())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = .Starter object at 0x7fe20a7de690>
log_file = <_io.TextIOWrapper 
name='/tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp/.pytest_cache/d/.xprocess/pylibmc/xprocess.log' 
mode='r' encoding='UTF-8'>


def get_lines(self, log_file):
"""Read and yield one line at a time from log_file. Will raise
TimeoutError if pattern is not matched before self.timeout
seconds."""
while True:
line = log_file.readline()
if not line:
std.time.sleep(0.1)
if datetime.now() > self._max_time:

  raise TimeoutError(

"The provided start pattern {} could not be matched \
within the specified time interval of {} 
seconds".format(

self.pattern, self.timeout
)
)
E   TimeoutError: The provided start pattern server 
listening could not be matched within the specified 
time interval of 120 seconds


/usr/lib/python3/dist-packages/xprocess/xprocess.py:422: TimeoutError
 Captured stdout setup 
-
/tmp/autopkgtest-lxc.wypz897y/downtmp/autopkgtest_tmp/.pytest_cache/d/.xprocess/redis$ 
redis-server --port 6360

process 'redis' started pid=2393
2393:C 09 Apr 2023 15:11:50.229 # oO0OoO0OoO0Oo Redis is starting 
oO0OoO0OoO0Oo


2393:C 09 Apr 2023 15:11:50.229 # Redis version=7.0.10, bits=64, 

Bug#1027429: mmdebstrap: unshare backend not working

[Andrea Pappacoda]

Il giorno gio 16 mar 2023 alle 03:57:42 +01:00:00, Johannes Schauer 
Marin Rodrigues  ha scritto:

I found another actionable in your bug report. mmdebstrap should not
automatically choose unshare mode if that cannot work on your system. 
To that

end I wrote:

https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/055e1719b95960496a0cda88535fd00e9a395516

If you like, please try that out on your system with --mode=unshare 
as well as

with --mode=auto. The messages and logic should be much better now.


Hi Josch, sorry for my super late reply and thanks for your fix! The 
error message is much cleaner now, and it gives the user a useful 
pointer so that the issue can be manually fixed/worked around.


Thanks again, keep up with the great work :D

Bug#1025069: pavucontrol

[Lucas]

I should have let you know when I created it, but I still have no feedback
from a bug report I wrote to the pipewire developers:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3131.

I guessed it was a "port detection" issue after reading this response on
the original poster's bug report:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1831991


On Sun, Apr 9, 2023 at 1:33 PM Lucas  wrote:

> On Fri, Apr 7, 2023 at 7:57 PM Alban Browaeys 
> wrote:
> >
> > Do you have jackd installed and runnning at the same time as pipewire-
> > pulse?
> > Maybe you want to try piepwire-jack instead?
> >
> > Cheers,
> > Alban
> >
>
> I appreciate the suggestion, but since I also use multiple devices
> with JACK, it's only running when I want to record and use a specific
> profile/device.  Ardour will start it using the last used (default)
> profile, but only when I've not already started JACK from qjackctl to
> use another profile.  I think having it always running may complicate
> this setup I've grown accustomed to.  Are you aware of any issues
> trying to stop JACK (to use other rates and devices) when using
> pipewire-jack?
>
> Thanks,
>   Lucas
>


-- 
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm
On a related note, also see https://www.fsf.org/campaigns/surveillance

Bug#1034126: RFP: slimevr -- VR software for using full body tracking

[uriel fontan ladino]

Package: slimevr
Severity: wishlist

This software is used for connecting SlimeVR trackers and also some other
implementations like Nintendo Switch joycons and phones. The github repo
with source code and releases is https://github.com/SlimeVR/SlimeVR-Server
One of my personal concerns is the modularity of it, it's separated in
multiple parts. The GUI is based on Tauri and it gets bundled together with
Vite and then compiled into the Tauri binary with cargo. Then you have the
server which is Java based and the Tauri binary runs it by using the first
compatible version of the JVM it can find in the OS.

Bug#1032104: linux: ppc64el iouring corrupted read

[Paul Gevers]

Hi Otto,

On 09-04-2023 03:54, Otto Kekäläinen wrote:

Paul Gevers asked if the issues are gone as well with 6.1.12-1
(or later 6.1.y series versions, which will land in bookworm). That
would be valuable information to know as well to exclude we do not
have the issue as well in bookworm.


Were you able to verify this?


No, not yet.

I have not done new uploads to experimental after the one I mentioned
and linked above from March 18th.


I don't understand this point, so I wonder if you understood my 
question. Maybe you did, but in my view no new uploads are needed to 
answer the bookworm question.



The builds for unstable are passing because I forced the tests to run
with regular fsync instead of native I/O in
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d.
I will test this again later but right now I don't want to do any
extra uploads as the package is pending unblock and inclusion in
Bullseye (Bug#1033811) and I don't want one single minor issue to
jeopardize getting fixes for multiple major issues forward.


My point was that I upgraded the ppc64el hosts where ci.debian.net runs 
the autopkgtests (so *not* the Debian build infrastructure). Since that 
upgrade, all tests on ci.debian.net *in every suite* have been using the 
bookworm (6.1.y) kernel.


E.g. in unstable MariaDb 1:10.11.2-1 (so before the "Prevent 
mariadb-test-run from using native I/O on ppc64el and s390x due to Linux 
kernel bug" change) passed on 2023-03-26 10:39 but failed on the same 
day at 14:40. Is any of the failures on ppc64el before 1:10.11.2-2 and 
after 2023-03-09 from the same kernel issue we're discussing here (and 
thus the kernel still needs fixing in bookworm). Or are all the failures 
in that time-span from something else, and thus can we conclude that the 
kernel *probably* (no proof of course) got fixed between the version of 
the kernel in bullseye and the version in bookworm.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034123: mirror submission for debian.holownych.com

[Marco d'Itri]

On Apr 09, Mike Holownych  wrote:

> Site: debian.holownych.com
This appear to be a DSL connection, even with a dynamic IP address.
Can you clarify how much bandwidth is available for this mirror?

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1025069: pavucontrol

[Lucas]

On Fri, Apr 7, 2023 at 7:57 PM Alban Browaeys  wrote:
>
> Do you have jackd installed and runnning at the same time as pipewire-
> pulse?
> Maybe you want to try piepwire-jack instead?
>
> Cheers,
> Alban
>

I appreciate the suggestion, but since I also use multiple devices
with JACK, it's only running when I want to record and use a specific
profile/device.  Ardour will start it using the last used (default)
profile, but only when I've not already started JACK from qjackctl to
use another profile.  I think having it always running may complicate
this setup I've grown accustomed to.  Are you aware of any issues
trying to stop JACK (to use other rates and devices) when using
pipewire-jack?

Thanks,
  Lucas

Bug#1034125: unblock: mbedtls/2.28.2-1

[Andrea Pappacoda]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mbed...@packages.debian.org
Control: affects -1 + src:mbedtls

Please unblock package mbedtls

[ Reason ]
Upstream released a new LTS bugfix version, and I'd like to have it in
bookworm. Since mbedtls is a crypto library and backporting single commits can
be dangerous, importing new versions is the safest and most appropriate thing
to do, especially since the upstream developers do a pretty good job in
maintaining LTS versions for a long time.

[ Impact ]
If not granted, Debian will release with a somewhat vulnerable/buggy version of
a widely used crypto library.

[ Tests ]
I've manually reviewed the changelog and diffs of the new release, tested it
locally with the upstream test suite and autopkgtest, and it has passed all the
CI checks on Salsa (repo available at
).

[ Risks ]
Risks should be low, as upstream usually does a good job with backporting. The
"only" issue is that between 2.28.2 and 2.28.3 they have adopted a new code
style, and reformatted the whole codebase accordingly; this means that the
debdiff is huge, even though the changes are only a few. To make reviewing
easier for me and you too, I've prepared three git diffs that exclude the
upstream commits that reformatted the code, and another one that adds the
string "\emptydescription" to many documentation strings in the source files.
As upstream also always backports test code along with fixes, these diffs only
include changes from the include/ and library/ directories, since that's where
the code that gets into the binary packages resides.
.
The diffs were generated with these commands:
.
$ git clone https://github.com/Mbed-TLS/mbedtls.git
$ cd mbedtls
$ git diff v2.28.2..160df1d13621ca3ee70e1fa19d0da88398da9683~1 include/
library/
$ git diff
b37f6c1b95815d39fea26b2a17e318602eefe709..b361e04207831f753a29d6036361d44473bc~1
include/ library/
$ git diff 7a5168e90db359e17e72591cb5ddb06ef5f0388f..v2.28.3 include/
library/

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
I mistakenly uploaded the new mbedtls version to unstable because I didn't
realize it was a key package, and thought that a regular 20 days of waiting
would suffice. This is also my first unblock request, so please be clement with
me, thanks! :D

Also, the debdiff is not directly attached to this email to avoid hitting the
size limit of the mailing list. You can find it here:


unblock mbedtls/2.28.2-1
diff --git a/include/mbedtls/bn_mul.h b/include/mbedtls/bn_mul.h
index a3fc36381..bce9ce38c 100644
--- a/include/mbedtls/bn_mul.h
+++ b/include/mbedtls/bn_mul.h
@@ -84,6 +84,7 @@
 
 #endif /* bits in mbedtls_mpi_uint */
 
+/* *INDENT-OFF* */
 #if defined(MBEDTLS_HAVE_ASM)
 
 #ifndef asm
@@ -1001,4 +1002,5 @@
 #endif /* C (generic)  */
 #endif /* C (longlong) */
 
+/* *INDENT-ON* */
 #endif /* bn_mul.h */
diff --git a/include/mbedtls/check_config.h b/include/mbedtls/check_config.h
index 7ae1ff94d..2ab99823e 100644
--- a/include/mbedtls/check_config.h
+++ b/include/mbedtls/check_config.h
@@ -28,6 +28,7 @@
 #ifndef MBEDTLS_CHECK_CONFIG_H
 #define MBEDTLS_CHECK_CONFIG_H
 
+/* *INDENT-OFF* */
 /*
  * We assume CHAR_BIT is 8 in many places. In practice, this is true on our
  * target platforms, so not an issue, but let's just be extra sure.
@@ -143,6 +144,11 @@
 #error "MBEDTLS_ECDH_VARIANT_EVEREST_ENABLED defined, but 
MBEDTLS_ECDH_LEGACY_CONTEXT not disabled"
 #endif
 
+#if defined(MBEDTLS_ECP_RESTARTABLE)   && \
+!defined(MBEDTLS_ECP_C)
+#error "MBEDTLS_ECP_RESTARTABLE defined, but not all prerequisites"
+#endif
+
 #if defined(MBEDTLS_ECDSA_DETERMINISTIC) && !defined(MBEDTLS_HMAC_DRBG_C)
 #error "MBEDTLS_ECDSA_DETERMINISTIC defined, but not all prerequisites"
 #endif
@@ -955,4 +961,5 @@
  */
 typedef int mbedtls_iso_c_forbids_empty_translation_units;
 
+/* *INDENT-ON* */
 #endif /* MBEDTLS_CHECK_CONFIG_H */
diff --git a/include/mbedtls/cipher.h b/include/mbedtls/cipher.h
index 6d83da882..ce100d3ed 100644
--- a/include/mbedtls/cipher.h
+++ b/include/mbedtls/cipher.h
@@ -917,13 +917,13 @@ int mbedtls_cipher_crypt( mbedtls_cipher_context_t *ctx,
  *  parameter-verification failure.
  * \return  A cipher-specific error code on failure.
  */
-int mbedtls_cipher_auth_encrypt( mbedtls_cipher_context_t *ctx,
- const unsigned char *iv, size_t iv_len,
- const unsigned char *ad, size_t ad_len,
- const unsigned char *input, size_t ilen,
- unsigned char *output, size_t *olen,
- unsigned char *tag, size_t tag_len )
-   

Bug#1011777: Same problem with 5.18.0-2-alpha-smp kernel

[Alex Ernst]

 Same problem with 5.18.0-2-alpha-smp kernel (5.18.0-2-alpha-generic boots
fine).
Also tested with 6.0.0 kernel - same problem.
OpenBSD 6.6 and Tru64 boot fine on this machine and both use 2 processors.

Boot logs from 5.18.0-2-alpha-smp and 5.18.0-2-alpha-generic are below for
comparison:


aboot: loading uncompressed vmlinuz...
aboot: loading compressed vmlinuz...
aboot: zero-filling 376684 bytes at 0xfc0002550e4c
aboot: loading initrd (29170220 bytes/7121 blocks) at 0xfc00fe064000
aboot: starting kernel vmlinuz with arguments ro
 root=UUID=15b2a3ef-adbc-49a5-b99e-7d2c9cf9d073 console=ttyS0
[0.00] Linux version 5.18.0-2-alpha-generic (
debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-3) 11.3.0, GNU ld
(GNU Binutils for Debian) 2.38.50.20220622) #1 Debian 5.18.5-1 (2022-06-16)
[0.00] Booting GENERIC on Titan variation Granite using machine
vector PRIVATEER from SRM
[0.00] Major Options: MAGIC_SYSRQ
[0.00] Command line: ro
 root=UUID=15b2a3ef-adbc-49a5-b99e-7d2c9cf9d073 console=ttyS0
[0.00] memcluster 0, usage 1, start0, end  395
[0.00] memcluster 1, usage 0, start  395, end   524279
[0.00] memcluster 2, usage 1, start   524279, end   524288
[0.00] Initial ramdisk at: 0x(ptrval) (29170220 bytes)
[0.00] 8192K Bcache detected; load hit latency 24 cycles, load miss
latency 137 cycles
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x0fffdfff]
[0.00]   Normal   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x]
[0.00] Initmem setup node 0 [mem
0x-0x]
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 520192
[0.00] Kernel command line: ro
 root=UUID=15b2a3ef-adbc-49a5-b99e-7d2c9cf9d073 console=ttyS0
[0.00] Dentry cache hash table entries: 524288 (order: 9, 4194304
bytes, linear)
[0.00] Inode-cache hash table entries: 262144 (order: 8, 2097152
bytes, linear)
[0.00] Sorting __ex_table...
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] Memory: 4097288K/4194304K available (9074K kernel code,
9491K rwdata, 2768K rodata, 424K init, 367K bss, 97016K reserved, 0K
cma-reserved)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS: 32784
[0.00] Turning on RTC interrupts.
[0.000976] Console: colour dummy device 80x25
[0.027343] printk: console [ttyS0] enabled
[0.028320] Calibrating delay loop... 1987.32 BogoMIPS (lpj=969728)
[0.036132] pid_max: default: 32768 minimum: 301
[0.037109] LSM: Security Framework initializing
[0.038085] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.039062] AppArmor: AppArmor initialized
[0.040039] TOMOYO Linux initialized
[0.041992] Mount-cache hash table entries: 8192 (order: 3, 65536 bytes,
linear)
[0.042968] Mountpoint-cache hash table entries: 8192 (order: 3, 65536
bytes, linear)
[0.046874] cblist_init_generic: Setting adjustable number of callback
queues.
[0.047851] cblist_init_generic: Setting shift to 0 and lim to 1.
[0.048828] Performance events: Supported CPU type!
[0.050781] devtmpfs: initialized
[0.054687] clocksource: jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 1866466235866741 ns
[0.055664] futex hash table entries: 256 (order: -1, 6144 bytes, linear)
[0.057617] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[0.058593] audit: initializing netlink subsys (disabled)
[0.060546] thermal_sys: Registered thermal governor 'fair_share'
[0.060546] thermal_sys: Registered thermal governor 'bang_bang'
[0.061523] thermal_sys: Registered thermal governor 'step_wise'
[0.062499] thermal_sys: Registered thermal governor 'user_space'
[0.063476] EISA bus registered
[0.065429] PCI host bridge to bus :00
[0.066406] pci_bus :00: root bus resource [io  0x-0x1ff]
[0.067382] pci_bus :00: root bus resource [mem
0x-0x7fff]
[0.068359] pci_bus :00: No busn resource found for root bus, will
use [bus 00-ff]
[0.069335] pci :00:07.0: [10b9:1533] type 00 class 0x060100
[0.070312] pci :00:08.0: [8086:1209] type 00 class 0x02
[0.071289] pci :00:08.0: reg 0x10: [mem 0x0102-0x01020fff]
[0.072265] pci :00:08.0: reg 0x14: [io  0x1-0x1003f]
[0.073242] pci :00:08.0: reg 0x18: [mem 0x0100-0x0101]
[0.074218] pci :00:08.0: supports D1 D2
[0.075195] pci :00:08.0: PME# supported from D0 D1 D2 D3hot
[0.076171] pci :00:0c.0: [0e11:a0f7] type 00 class 0x080400
[0.077148] pci :00:0c.0: reg 0x10: [mem 0x01021000-0x010210ff]
[0.079101] pci :00:10.0: [10b9:5229] type 00 class 0x0101fa
[0.080078] pci 

Bug#1034123: mirror submission for debian.holownych.com

[Mike Holownych]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: debian.holownych.com
Type: leaf
Archive-architecture: amd64 arm64 armhf i386
Archive-http: /debian/
Maintainer: Mike Holownych 
Country: CA Canada
Location: Toronto
Sponsor: Holownych https://holownych.com




Trace Url: http://debian.holownych.com/debian/project/trace/
Trace Url: 
http://debian.holownych.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://debian.holownych.com/debian/project/trace/debian.holownych.com

Bug#1034124: udev security update breaks all ext4 removable storage handling

[Floris Bos]

Package: udisks2

Version: 2.8.1-4+deb10u1

Severity: serious


Hi,


The security team recently released udisks2 2.8.1-4+deb10u1 that forces 
the mount option 'errors=remount-ro' to be used for all mounting 
operations on ext4 file systems.
However it seems the code was not modified correctly to allow that 
option to be used.



On a system with a LXDE based desktop environment, hot-plugging an ext4 
formatted USB drive, result in the user being presented with an "Mount 
option `errors=remount-ro' is not allowed" error dialog box, and the 
mount not occurring.


Same when mounting manually as regular user through udisksctl:

==
max@pibuster:~ $ udisksctl mount -b /dev/sda2
Error mounting /dev/sda2: 
GDBus.Error:org.freedesktop.UDisks2.Error.OptionNotPermitted: Mount 
option `errors=remount-ro' is not allowed

==


Looking at debian/patches/mount-ext-readonly-on-errors.patch
It did seem the author of the patch knew options need to be allowed, as 
he does add "errors=remount-ro" to ext4_allow:


+static const gchar *ext4_allow[] = { "errors=remount-ro", NULL };

However looking at is_mount_option_allowed() in 
src/udiskslinuxfilesystem.c the allow list handling code only expect a 
lists of allowed option keys in ext4_allow, not entries in the form 
key=value...


So that is not going to fly without further changes to 
is_mount_option_allowed()...




Yours sincerely,

Floris Bos

Bug#1034122: feh: excessively noisy and unclear if inotify_init() fails

[Michael Gold]

Package: feh
Version: 3.9.1-2
Severity: wishlist

Dear Maintainer,

feh prints some warnings to stderr if inotify_init() fails:
feh WARNING: inotify_init failed: Too many open files
feh WARNING: Disabling inotify-based auto-reload

I reported a related crash here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034121
But I consider the warnings to be problematic too.

A program shouldn't print a warning relating to an optional feature that
I did not specifically enable, based on a function that must be expected
to "randomly" fail (due to its reliance on an extremely limited resource
shared with unrelated programs: by default, each user has a limit of 128
inotify instances).

It is also unclear from the text whether auto-reloading was disabled, or
remains operational via some non-inotify fallback.  The program's manual
page is similarly ambiguous.  I don't see any fallback in the code.

- Michael


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

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

Versions of packages feh depends on:
ii  libc6 2.36-8
ii  libcurl4  7.88.1-8
ii  libexif12 0.6.24-1+b1
ii  libimlib2 1.10.0-4+b1
ii  libpng16-16   1.6.39-2
ii  libx11-6  2:1.8.4-2
ii  libxinerama1  2:1.1.4-3
ii  yudit-common  3.1.0-1

Versions of packages feh recommends:
ii  libjpeg-progs  1:9e-1

feh suggests no packages.

-- no debconf information



signature.asc
Description: PGP signature

Bug#1034121: feh: makes a bad FD_SET() call and aborts if inotify_init() fails

[Michael Gold]

Package: feh
Version: 3.9.1-2
Severity: important

Dear Maintainer,

Today I'm getting the following error whenever I try to run feh:
feh WARNING: inotify_init failed: Too many open files
feh WARNING: Disabling inotify-based auto-reload
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
Aborted

It turns out that inotify_init() has the very low limit of 128 instances
per user by default, and lsof shows they are mostly used by instances of
dbus-daemon, dconf-service, and xdg-desktop-portal.

feh_main_iteration() calls FD_SET(opt.inotify_fd, ) if auto_reload
is enabled, regardless of whether inotify_fd is valid.  It also needs to
check 'opt.inotify_fd >= 0' in the 'if' statement.

A workaround is to use the --reload=0 command line option.

- Michael


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

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

Versions of packages feh depends on:
ii  libc6 2.36-8
ii  libcurl4  7.88.1-8
ii  libexif12 0.6.24-1+b1
ii  libimlib2 1.10.0-4+b1
ii  libpng16-16   1.6.39-2
ii  libx11-6  2:1.8.4-2
ii  libxinerama1  2:1.1.4-3
ii  yudit-common  3.1.0-1

Versions of packages feh recommends:
ii  libjpeg-progs  1:9e-1

feh suggests no packages.

-- no debconf information



signature.asc
Description: PGP signature

Bug#1034120: sensible-utils: Broken shell invocation handling

[Guillem Jover]

Package: sensible-utils
Version: 0.0.18
Severity: serious

Hi!

I installed this some time ago, and started seeing issues, but was
still wondering why no one had reported this already and whether this
was a local issue of mine, until I realized now this is an experimental
only upload. In any case, when calling «dch» I'm getting stuff like:

  ,---
  $ dch
  debian/changelog.dch": 1: Syntax error: Unterminated quoted string
  dch: fatal error at line 1742:
  Error editing debian/changelog
  `---

Regards,
Guillem

Bug#891685: castle-game-engine: FTBFS on m68k: color and vector tests fail

[Abou Al Montacir]

Hi,

On Thu, 2022-05-26 at 20:23 +0200, Abou Al Montacir wrote:
> CGE build correctly on m68k architecture now.
This was broken again in new upstream 7.0~alpha.2 release.

There was a rework of TVector3Byte where the base data was changed from an array
to a record fields and a default property was added to allow array like access.
However, this array like property is read only, while a load from stream
function tries, in big endian mode, to switch bytes.
While I don't think this swap endianess code is needed at all, I would preferred
a faster implementation with basic records:
  TVector3Byte = packed record
  case Boolean of:
    false: (x, y, z: Byte);
    true: (AsBytes: array[0..2] of Byte);
  end;

Anyway, I'll let upstream fix this as they wants, but probably this will never
be in Bookworms.
-- 
Cheers,
Abou Al Montacir


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

Bug#782007: criu: Split up binary packages

[Faidon Liambotis]

On Sun, Apr 09, 2023 at 09:08:09AM +0200, Salvatore Bonaccorso wrote:
> > I submitted an MR implementing this:
> > https://salsa.debian.org/debian/criu/-/merge_requests/3
> > 
> > Looking forward to your review!
> 
> Thanks for doing the work, I will have a look but any such change will
> happen only after the bookworm release.

Of course! If you have some spare cycles to review this during the
freeze, it'd be neat if we could stage it in experimental (and cross
through NEW now that things are relatively quiet :). That way I could
also move up the stack and test crun against libcriu in experimental as
well.

Thanks for the quick response regardless!

Best,
Faidon

Bug#1034119: [INTL:ro] Translation of "ufw" to Romanian

[Remus-Gabriel Chelu]

Package: ufw
Version: 0.36.1
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «ufw» file.

Thanks,
Remus-Gabriel

ufw-ro.po
Description: Binary data

Bug#1031655: Lutris: wine build does not support Esync/Fsync

[Michael Gilbert]

control: severity -1 normal
control: reassign -1 src:lutris

Bernhard Übelacker wrote:
> It looks like Lutris extracts the version
> from the path the wine executable was found.

Lutris parses version information from "wine --version" to conclude
whether features are supported [0].  The wine in debian outputs
package version detail, which lutris does not currently ignore and
concludes that the version is not in its known good set (i.e. does not
support particular features).

Lutris needs to be updated to ignore the extra package details
returned by the debian wine package.

Best wishes,
Mike

[0] https://github.com/lutris/lutris/blob/v0.5.12/lutris/util/wine/wine.py#L274

Bug#1034118: unblock: lowdown/1.0.0-2

[Faidon Liambotis]

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

Please unblock package lowdown, a key package, through:
  bind9 -> libmaxminddb -> lowdown

[ Reason ]
lowdown is a Markdown to HTML/roff/LaTeX/etc. translator. A regression
was introduced at some point where the -Tman (manpage) output used a
roff macro that is not present in the "man" package but in the "ms"
package. I reported this upstream[1], and it was subsequently fixed[2].

This is a bookworm-targeted backport of that specific upstream commit,
that applies cleanly as-is.

1: https://github.com/kristapsdz/lowdown/issues/111
2: 
https://github.com/kristapsdz/lowdown/commit/02491bf4ae2a39df2dfed10382512449a5b3262f

[ Impact ]
The output difference is minor from a visual standpoint, e.g.
   OPTIONS
  -batch_size __
  -  Maximum  number  of  entries to request per call to 
get-entries.
  -  You should not generally need to change this. Defaults to 1000.
  +Maximum number of entries to request per call to get-entries.  
You
  +should not generally need to change this. Defaults to 1000.

However, the roff output is technically invalid.

In Debian, this manifests in reverse build-dependencies that are using
lowdown to generate their manpage to emit lintian warnings, e.g.:
W: certspotter: groff-message 29: warning: macro 'PI' not defined 
[usr/share/man/man8/certspotter-script.8.gz:1]
W: certspotter: groff-message 56: warning: macro 'PI' not defined 
[usr/share/man/man8/certspotter.8.gz:1]

There are three reverse build-dependencies in testing:
  1) src:libmaxminddb
  2) src:certspotter
  3) src:nix

Only the first two are using -Tman. I am the maintainer for both.
src:libmaxminddb was built with an pre-regression version of lowdown and
is not affected. It can be binNMUed, although not strictly necessary.

src:certspotter is affected and should probably be binNMUed, although as
explained, the visual impact is relatively minor.

[ Tests ]
Upstream has a comprehensive test suite that runs as part of the build.
The package also has autopkgtests that pass.

[ Risks ]
The code for the fix is trivial. The package is technically a key
package, but only as a reverse build-dep of another package, and is only
a B-D for three packages in total.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
debdiff attached; you can also find the git diff at:
https://salsa.debian.org/debian/lowdown/-/commit/0e2160bb23e194edc5c15c7772042857fd18f2f7

unblock lowdown/1.0.0-2

Also probably:

nmu certspotter_0.16.0-1 . ANY . unstable . -m "Rebuild with lowdown 1.0.0-2"

(but no idea how to ensure the ordering of those two, not fluent in
wanna-build)
diff -Nru lowdown-1.0.0/debian/changelog lowdown-1.0.0/debian/changelog
--- lowdown-1.0.0/debian/changelog  2023-01-07 06:52:41.0 +0200
+++ lowdown-1.0.0/debian/changelog  2023-04-09 03:39:15.0 +0300
@@ -1,3 +1,13 @@
+lowdown (1.0.0-2) unstable; urgency=medium
+
+  * Backport upstream patch to avoid the use of an -ms macro, PI, in the -Tman
+output. This addresses a man warning ("macro 'PI' not defined") which in
+turn is a lintian warning for packages using lowdown to generate their
+manpage(s).
+  * Bump Standards-Version to 4.6.2, no changes needed.
+
+ -- Faidon Liambotis   Sun, 09 Apr 2023 03:39:15 +0300
+
 lowdown (1.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru lowdown-1.0.0/debian/control lowdown-1.0.0/debian/control
--- lowdown-1.0.0/debian/control2023-01-07 04:49:43.0 +0200
+++ lowdown-1.0.0/debian/control2023-04-09 03:39:15.0 +0300
@@ -6,7 +6,7 @@
  libbsd-dev,
  libmd-dev,
  pkgconf | pkg-config,
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Section: text
 Homepage: https://kristaps.bsd.lv/lowdown/
 Vcs-Browser: https://salsa.debian.org/debian/lowdown
diff -Nru lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch 
lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch
--- lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch 1970-01-01 
02:00:00.0 +0200
+++ lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch 2023-04-09 
03:38:19.0 +0300
@@ -0,0 +1,83 @@
+From: Kristaps Dz 
+Subject: [PATCH] Don't use \(PI for -tman: it doesn't exist.
+
+The \(PI register only exists for -ms macros.  Use the default value
+of 5n for this (for definition lists) when emitting for -tman.
+
+References #111
+
+Origin: upstream, 
https://github.com/kristapsdz/lowdown/commit/02491bf4ae2a39df2dfed10382512449a5b3262f
+Bug: https://github.com/kristapsdz/lowdown/issues/111
+Last-Update: 2023-04-09
+
+--- a/nroff.c
 b/nroff.c
+@@ -745,7 +745,8 @@ rndr_definition_title(struct bnodeq *obq
+ }
+ 
+ static int
+-rndr_definition_data(struct bnodeq *obq, struct bnodeq *bq)

Bug#1034117: installation-reports: Debian testing installer doesn't prepare apt sources

[Julian Groß]

Package: installation-reports
Severity: normal

Dear Maintainer,

installing the image linked below, doesn't set up the apt sources. 
/etc/apt/sources.list only contains the installation media and nothing else 
(not even comments).


Boot method: USB (ISO via Ventoy)
Image version: 
http://saimei.ftp.acc.umu.se/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
  3th april 2023 was shown as the date
Date: 09th April 2023

Machine: 
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]


Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230403-00:01:36"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Curser 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 
(2023-03-19) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0100] (rev 09)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:d798]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev a4)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation B75 Express Chipset 
LPC Controller [8086:1e49] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 
Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7798]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel 

Bug#1034076: unblock: spf-engine/3.0.4-1

[Scott Kitterman]

On Sunday, April 9, 2023 4:11:30 AM EDT Sebastian Ramacher wrote:
> Please go ahead and remove the moreinfo tag once the package is in
> unstable.

Thanks.  Uploaded and tag removed.

Scott K

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

Bug#1033919: svn2cl: svn2cl --html fails due to usrmerge

[Arthur de Jong]

On Mon, 2023-04-03 at 23:39 +0200, H.-Dirk Schmitt wrote:
> The `--html` option fails on bookworm,
> 
> Due to the usrmerge the script is now invoked as `/bin/svn2cl`.
> This leads to an error in the determination of the  snv2cl.xss file.

Thanks for pointing this out (on my system I still had /usr/bin in my
PATH before /bin). I've applied another fix than the one you provided
(one that is also included "upstream").

I've uploaded a version 0.14-3 with a fix to unstable.

Thanks!

-- 
-- arthur - art...@arthurdejong.org - https://arthurdejong.org/ --



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

Bug#1033919: svn2cl: svn2cl --html fails due to usrmerge

[Arthur de Jong]

On Mon, 2023-04-03 at 23:39 +0200, H.-Dirk Schmitt wrote:
> The `--html` option fails on bookworm,
> 
> Due to the usrmerge the script is now invoked as `/bin/svn2cl`.
> This leads to an error in the determination of the  snv2cl.xss file.

Thanks for pointing this out (on my system I still had /usr/bin in my
PATH before /bin). I've applied another fix than the one you provided
(one that is also included "upstream").

I've uploaded a version 0.14-3 with a fix to unstable.

Thanks!

-- 
-- arthur - art...@arthurdejong.org - https://arthurdejong.org/ --



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

Bug#1034115: debian/tests/upstream-tests executes all files in tests/, not only actual tests

[Evgeni Golov]

On April 9, 2023 12:51:33 PM UTC, Santiago Vila  wrote:
>Hello. This is an interesting bug indeed, because it forces us to re-read
>the specification and maybe suggest changes if we see that it's incomplete
>or just suboptimal.
>
>https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst
>
>This is the current wording:
>
>> The cwd of each test is guaranteed to be the root of the source package,
>> which will have been unpacked but not built.
>
>My interpretation of that is that the cwd of each test is guaranteed
>to be the root of the source package in unpacked form.
>
>Under this interpretation, running autopkgtest on a built tree does not follow
>the specification and is not required to work.
>
>Somebody could also interpret it that "you should not rely on the package 
>being built",
>as it "may or may not have been built".

This was always my interpretation, especially given there is an explicit 
restriction to have a *built* tree:

build-needed
The tests need to be run from a built source tree. The test runner
will build the source tree (honouring the source package's build
dependencies), before running the tests. However, the tests are
*not* entitled to assume that the source package's build
dependencies will be installed when the test is run.

>But I would argue that if that was the intended meaning, the wording would be
>quite different.
>
>So, I would reassign this to whatever package is running autopkgtest in a 
>built tree
>(even if it's autopkgtest itself), as I believe the specification is not being 
>followed.


My above test was done using

  autopkgtest hello_2.10-3.dsc --setup-commands='apt-get update' -- docker 
--remote debian:sid

But I guess that virt implementation doesn't matter too much here.

>On the other hand, if we are going to allow both built and not built trees, 
>maybe
>it would be a good idea to change the wording first so that it's clear for 
>everybody.
>
>Thanks.

Bug#1034015: exim4: exim paniclog on lenovo has non-zero size

[Marc Haber]

On Sun, Apr 09, 2023 at 08:43:23PM +0800, Wensheng Xie wrote:
> > Actually that does seem to be relevant at all, the message is from
> > March
> > 17.
> 
> Each time I start the machine, my mailbox will have at least one such
> email.

This is expected and intended behavior, you need to manually move the
paniclog away for the message to go away. See README.Debian 2.5.1

Andreas, we should probably include this reference into the mail
message.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1034115: debian/tests/upstream-tests executes all files in tests/, not only actual tests

[Santiago Vila]

Hi. I keep reading the specs and found this:


build-needed
   The tests need to be run from a built source tree.


I think this reinforces the idea that by default the tests
are supposed to be run in a non-built source tree.

Please reassign.

Thanks.

Bug#1034115: debian/tests/upstream-tests executes all files in tests/, not only actual tests

[Santiago Vila]

Hello. This is an interesting bug indeed, because it forces us to re-read
the specification and maybe suggest changes if we see that it's incomplete
or just suboptimal.

https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst

This is the current wording:


The cwd of each test is guaranteed to be the root of the source package,
which will have been unpacked but not built.


My interpretation of that is that the cwd of each test is guaranteed
to be the root of the source package in unpacked form.

Under this interpretation, running autopkgtest on a built tree does not follow
the specification and is not required to work.

Somebody could also interpret it that "you should not rely on the package being 
built",
as it "may or may not have been built".

But I would argue that if that was the intended meaning, the wording would be
quite different.

So, I would reassign this to whatever package is running autopkgtest in a built 
tree
(even if it's autopkgtest itself), as I believe the specification is not being 
followed.

On the other hand, if we are going to allow both built and not built trees, 
maybe
it would be a good idea to change the wording first so that it's clear for 
everybody.

Thanks.

Bug#1034015: exim4: exim paniclog on lenovo has non-zero size

[Wensheng Xie]

> 
> Actually that does seem to be relevant at all, the message is from
> March
> 17.

Each time I start the machine, my mailbox will have at least one such
email.

> 
> What do the configuration files look like (especially
> /etc/exim4/update-exim4.conf.conf)? What doi the log files show for
> which mail?
> 

I attach the conf file and the email.
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='internet'
dc_other_hostnames='lenovo.debian.lenovo ; mail.debian.lenovo'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.debian.lenovo'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='maildir_home'


exim_paniclog_on_lenovo_has_non-zero_size.mbox
Description: application/mbox


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

Bug#1034116: jenkins.d.n: deploy_kgb.py needs to be updated for bookworm

[Holger Levsen]

package: jenkins.debian.org
severity: important

hi,

when deploying on osuosl3, running bookworm:

Traceback (most recent call last):
  File "/srv/jenkins/bin/deploy_kgb.py", line 19, in 
passwords = yaml.load(fd)
^
TypeError: load() missing 1 required positional argument: 'Loader'



This is blocker for migrating nodes running kgb-client to bookworm.



-- 
cheers,
Holger

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

Friendly reminder, that we are all closer to being climate refugees than
billionaires.


signature.asc
Description: PGP signature

Bug#1034115: debian/tests/upstream-tests executes all files in tests/, not only actual tests

[Evgeni Golov]

Package: hello
Version: 2.10-3

Ohai,

while looking for a simple package to test something with autopkgtest, I
noticed that hello's debian/tests/upstream-tests will try to execute
*all* files from the tests/ directory (skipping greeting-2).

This works correctly when the tests are executed from a clean source
tree, but not if the same source was previously used to build hello
(like it happens if you pass the .dsc to autopkgtest).

In this case, the tests/ directory contains more files:

hello-2.10# ls tests/
greeting-1  greeting-1.log  greeting-1.trs  greeting-2  greeting-2.log  
greeting-2.trs  hello-1  hello-1.log  hello-1.trs  last-1  last-1.log  
last-1.trs  traditional-1  traditional-1.log  traditional-1.trs

And execution of the test-suite fails:

…
autopkgtest [10:47:35]: test upstream-tests: [---
Testing greeting-1 ...
Testing greeting-1.log ...
/tmp/autopkgtest.qGAtSW/build.n6t/src/debian/tests/upstream-tests: 8: 
tests/greeting-1.log: Permission denied
autopkgtest [10:47:35]: test upstream-tests: ---]
autopkgtest [10:47:36]: test upstream-tests:  - - - - - - - - - - results - 
- - - - - - - - -
upstream-tests   FAIL non-zero exit status 126
autopkgtest [10:47:36]: test upstream-tests:  - - - - - - - - - - stderr - 
- - - - - - - - -
/tmp/autopkgtest.qGAtSW/build.n6t/src/debian/tests/upstream-tests: 8: 
tests/greeting-1.log: Permission denied
autopkgtest [10:47:36]:  summary
command1 PASS
upstream-tests   FAIL non-zero exit status 126

While passing an unbuilt source to autopkgtest is not optimal, I think
this is something that should still work.

Thanks for maintaining hello!

Evgeni

Bug#1034100: Acknowledgement (unblock: texlive-base/2022.20230122-3)

[Hilmar Preuße]

Control: tags -1 - moreinfo

Many thanks for help.

Hilmar

09.04.2023 10:12:36 Sebastian Ramacher :

> Control: tags -1 moreinfo confirmed
> 
> On 2023-04-09 00:29:55 +0200, Hilmar Preuße wrote:
>> On 4/9/23 00:24, Debian Bug Tracking System wrote:
>> 
>> Hi,
>> 
>>> You can follow progress on this Bug here: 1034100:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034100.
>>> 
>> Attached is the promised debdiff.
> 
> Please go ahead and remove the moreinfo tag once the package is
> available in unstable.
> 
> Cheers
> 
>> 
>> Hilmar
>> --
>> Testmail
> 
>> diff -Nru texlive-base-2022.20230122/debian/changelog 
>> texlive-base-2022.20230122/debian/changelog
>> --- texlive-base-2022.20230122/debian/changelog 2023-02-15 
>> 14:35:08.0 +0100
>> +++ texlive-base-2022.20230122/debian/changelog 2023-04-01 
>> 12:57:29.0 +0200
>> @@ -1,3 +1,12 @@
>> +texlive-base (2022.20230122-3) UNRELEASED; urgency=medium
>> +
>> +  * Add Romanian debconf translation by Remus-Gabriel Chelu
>> +     (Closes: #1033738).
>> +  * Add patch to fix hyphenation penalties in german language
>> +    (Closes: #1034038).
>> +
>> + -- Hilmar Preusse   Sat, 01 Apr 2023 12:57:29 +0200
>> +
>> texlive-base (2022.20230122-2) unstable; urgency=medium
>> 
>>    [ Jelmer Vernooij ]
>> diff -Nru texlive-base-2022.20230122/debian/patches/1034038 
>> texlive-base-2022.20230122/debian/patches/1034038
>> --- texlive-base-2022.20230122/debian/patches/1034038   1970-01-01 
>> 01:00:00.0 +0100
>> +++ texlive-base-2022.20230122/debian/patches/1034038   2023-04-01 
>> 12:57:29.0 +0200
>> @@ -0,0 +1,11 @@
>> +--- 
>> texlive-base-2022.20230122.orig/texmf-dist/tex/generic/babel/babel-transforms.lua
>>  
>> texlive-base-2022.20230122/texmf-dist/tex/generic/babel/babel-transforms.lua
>> +@@ -364,7 +364,7 @@
>> + goto next
>> +
>> +   elseif mode == 1 and crep and (crep.pre or crep.no or crep.post) 
>> then
>> +-    d = node.new(7, 0)   -- (disc, discretionary)
>> ++    d = node.new(7, 3)   -- (disc, regular)
>> + d.pre = Babel.str_to_nodes(crep.pre, matches, item_base)
>> + d.post    = Babel.str_to_nodes(crep.post, matches, item_base)
>> + d.replace = Babel.str_to_nodes(crep.no, matches, item_base)
>> diff -Nru texlive-base-2022.20230122/debian/patches/series 
>> texlive-base-2022.20230122/debian/patches/series
>> --- texlive-base-2022.20230122/debian/patches/series    2023-02-15 
>> 14:16:01.0 +0100
>> +++ texlive-base-2022.20230122/debian/patches/series    2023-04-01 
>> 12:57:29.0 +0200
>> @@ -25,3 +25,4 @@
>> python3-shebang
>> debian-fix-quote-in-quote
>> update_epspdf_luascript
>> +1034038
>> diff -Nru texlive-base-2022.20230122/debian/po/ro.po 
>> texlive-base-2022.20230122/debian/po/ro.po
>> --- texlive-base-2022.20230122/debian/po/ro.po  1970-01-01 
>> 01:00:00.0 +0100
>> +++ texlive-base-2022.20230122/debian/po/ro.po  2023-04-01 
>> 12:55:00.0 +0200
>> @@ -0,0 +1,77 @@
>> +# Mesajele în limba română pentru pachetul texlive-base.
>> +# Romanian translation of texlive-base.
>> +# Copyright © 2023 THE PACKAGE'S COPYRIGHT HOLDER
>> +# This file is distributed under the same license as the texlive-base 
>> package.
>> +#
>> +# Remus-Gabriel Chelu , 2023.
>> +#
>> +# Cronologia traducerii fișierului „texlive-base”:
>> +# Traducerea inițială, făcută de R-GC, pentru versiunea texlive-base 
>> 2022.20230122-2(2012-04-24).
>> +# Actualizare a traducerii pentru versiunea Y, făcută de X, Y(anul).
>> +#
>> +msgid ""
>> +msgstr ""
>> +"Project-Id-Version: texlive-base 2022.20230122-2\n"
>> +"Report-Msgid-Bugs-To: texlive-b...@packages.debian.org\n"
>> +"POT-Creation-Date: 2012-04-24 14:30+0900\n"
>> +"PO-Revision-Date: 2023-03-26 17:57+0200\n"
>> +"Last-Translator: Remus-Gabriel Chelu \n"
>> +"Language-Team: Romanian \n"
>> +"Language: ro\n"
>> +"MIME-Version: 1.0\n"
>> +"Content-Type: text/plain; charset=UTF-8\n"
>> +"Content-Transfer-Encoding: 8bit\n"
>> +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n==0 || (n!=1 && n%100>=1 && "
>> +"n%100<=19) ? 1 : 2);\n"
>> +"X-Bugs: Report translation errors to the Language-Team address.\n"
>> +"X-Generator: Poedit 3.2.2\n"
>> +
>> +#. Type: error
>> +#. Description
>> +#: ../texlive-base.templates:2001
>> +msgid "Unmanageable system paper size (${libpaperPaper})"
>> +msgstr "Dimensiune de hârtie de sistem imposibil de gestionat 
>> (${libpaperPaper})"
>> +
>> +#. Type: error
>> +#. Description
>> +#: ../texlive-base.templates:2001
>> +msgid ""
>> +"The currently defined system-wide paper size is ${libpaperPaper}. However, 
>> the "
>> +"TeX configuration system cannot handle this paper size for ${binary}."
>> +msgstr ""
>> +"Dimensiunea de hârtie definită în prezent pentru întregul sistem este "
>> +"${libpaperPaper}. Cu toate acestea, sistemul de configurare TeX nu poate "
>> +"gestiona această dimensiune de hârtie pentru ${binary}."
>> +
>> +#. Type: error
>> +#. 

Bug#1033503: dgit autopkgtests broken by git 2.40 [and 2 more messages]

[Ian Jackson]

Recap:

  git's new check in "git hash-object" breaks some tests in src:dgit,
  which deliberately create broken objects eg to detect a regression
  like #849041.  Updating the tests looks nontrivial.

  git 1.2.40-1 doesn't seem like it's going to migrate anyway, given
  that it's a key package which was uploaded during the freeze, and
  the git maintainer hasn't filed an unblock.

My previous message didn't receive any response and we're well into
the hard freeze.  I therefore don't have any plans to update dgit's
test suite for bookworm.

I have taken this work item off my personal todo lists and tracking
machinery, including suppressing the nag emails that I usually get
when my autopkgtests are blocking some other package.

After the bookworm release, the severity of this bug should probably
be raised.  That will put this issue back on my radar.

Thanks,
Ian.

Bug#856649: suricata: IPv4 defrag evasion issue

[Sascha Steinbiss]

Hi,

(re: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856649)

Can we just close this bug? This has been addressed for years, and I am 
not sure we need to keep these open forever.


Thanks and best regards
Sascha


OpenPGP_signature
Description: OpenPGP digital signature

Bug#856648: suricata: dns: out of bound memory read

[Sascha Steinbiss]

Can we just close this bug? This has been fixed for years, and AFAICS no 
CVE has ever been assigned.


Thanks and best regards
Sascha


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034114: RFP: tinytaskmanager -- Tiny task manager for Linux, MacOS and Unix-like systems

[Yuri Escalianti]

Package: wnpp
Severity: wishlist

Version : 0.14.0
Upstream Author : Yuri E. 
URL : https://github.com/yuriescl/ttm
License : MIT

Tiny task manager for Linux, MacOS and Unix-like systems. Written as a
single Python script.

Bug#1034085: spyder: Cursor jumps somewhere else after right-clicking → selecting Format with Black or Autopep8

[Julian Gilbey]

tags 1034085 + unreproducible
thanks

On Sat, Apr 08, 2023 at 01:00:04PM +0200, Amr Ibrahim wrote:
> Package: spyder
> Version: 5.4.2+ds-5
> Severity: normal
> 
> Hello,
> 
> Steps to reproduce the bug:
> 0. Enable a formatter: Black or Autopep8
> 1. Make sure that there is something to be formatted in the code
> 2. Right-click somewhere in the editor and select Format with Black or 
> Autopep8
> 
> What happens:
> After formatting the file, the cursor jumps somewhere else in the editor,
> usually up, changing the editor view.
> 
> What should happen:
> The cursor stays where it is after formatting is done.

Dear Amr,

I have followed your instructions, but I cannot reproduce the
behaviour you describe.  What I *do* observe is that the editor view
changes, but even so, the cursor remains in the same place in the
file.  The bug you describe was fixed upstream a few months ago, see
https://github.com/spyder-ide/spyder/issues/19958

If you can take a screencast showing the behaviour you describe,
please do send it to this bug report and I will be able to investigate
further.

Best wishes,

   Julia
n

Bug#1033593: spyder: does not allow running profiler and says "Please install the Python profiler modules"

[Julian Gilbey]

On Mon, Mar 27, 2023 at 06:34:27PM -0300, Patrick Zanon wrote:
> Package: spyder
> Version: 5.4.2+ds-5
> Severity: important
> X-Debbugs-Cc: ne...@libero.it
> 
> 
> Dear Maintainer,
> 
> I'm trying to use spyder's profiling tools, but when I try to run code with 
> the
> profiler, the menu item is greyed out. Also if I enable profiler pane 
> display, 
> Spyder says "Please install python profiler modules".
> 
> In my installation I have:
>* python3 which provides the python-profiler virtual package
>* python3-line-profiler
>* python3-p profile
> 
> If I try to run the "import cProfile" line it's fine with no errors; same 
> goes 
> if I run "import profile".
> 
> I would expect to be able to run the code from both the "Run - Run profiler" 
> menu item, and to be able to add files in the profiler pane, but neither of 
> those things happen.
> 
> Thanks
> P.Z.

Dear Patrick,

Unfortunately, python3-line-profiler was not in testing at the time of
the freeze, so I was unable to update python3-spyder-profiler for
bookworm and test that it all works.  I intend to do it for trixie
once bookworm has released.

In the meantime, if you cannot get it to work with the current version
of spyder in testing, you may have more success if you run spyder
within a virtual environment pulling in packages directly from PyPI.

I'm sorry to be unable to help further at this point in time.

Best wishes,

   Julian

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Julian Gilbey]

tags 1032995 + unreproducible
thanks

On Wed, Mar 15, 2023 at 10:25:01AM -0300, Patrick Zanon wrote:
> Package: spyder
> Version: 5.4.2+ds-5
> Severity: minor
> X-Debbugs-Cc: ne...@libero.it
> 
> Dear Maintainer,
> 
> Spyder on startup says there is a missin dependency problem with pylsp_black 
> that
> should be >= 1.2.0;however on my installation I have python3-pylsp-black 
> 1.2.1-2.
> 
> The popup warning does not affect the spyder configuration nor functionality.
> 
> P.Z

Dear Patrick,

I'm bemused by this one; I seem to have the same setup as you but I
don't receive this warning.  Is it possible that you are running
spyder in some sort of virtual environment which does not have the
correct dependencies?

One thing you could try: select Help > About Spyder..., click "Copy
version info" and paste it into a reply to this bug report; then do
Help > Dependencies, click "Copy to clipboard" and paste that in as
well.  That may well give us more of an idea of what is happening
here.

Best wishes,

   Julian

Bug#1034004: afl++: afl-clang(-fast) does not support -m32 due to missing afl-compiler-rt-32.o

[Kurt Roeckx]

This seems to be caused by a missing build-depends. If I build it
locally, I do get support for 32 bit builds.

Bug#1034078: [pkg-lua-devel] Bug#1034078: lua-readline: regression in how EOF is reported

[Sergei Golovan]

tags 1034078 + pending
thanks

Hi Kim,

On Sat, Apr 8, 2023 at 10:15 AM Kim Alvefur  wrote:
>
> Dear Maintainer,
>
> The lua-readline package changed how end-of-file is reported back,
> which may cause Ctrl-D to no longer behave as expected in programs that
> use lua-readline.

I confirm the regression.

>
> I have reported this to the upstream author via email as I did not find
> any public bug tracker.

I see that upstream has already released version 3.3 with the fix. I cannot
bump the Debian package to 3.3 because of the freeze, but I'll try to persuade
release team to allow the backported fix to enter testing.

Thank you for the bugreport!
-- 
Sergei Golovan

Bug#1034113: fail2ban does not start/stop/restart in postinst

[Chris Hofstaedtler]

Package: fail2ban
Version: 1.0.2-1
Severity: important

fail2ban currently installs its fail2ban.service file into
/usr/lib/systemd/system/, but dh_installsystemd does not
handle files in this location (#1031695).

It seems like fail2ban moved the file in this commit:
https://salsa.debian.org/python-team/packages/fail2ban/-/commit/bdb82eb3b26485f9ec585896503d3afeed812dc1

If fail2ban wants the automatic install/start/restart
behaviour, and I think it does, because that works in bullseye, probably
that commit needs a revert for bookworm.

Chris

Bug#1032418: zcfan service is not stopped on package removal

[Chris Hofstaedtler]

* Michel Alexandre Salim  [230409 09:09]:
> On Fri, 17 Mar 2023 16:01:16 +0100 Lee Garrett  wrote:
> > Debugging this issue I found that it's caused by #1031695 (a bug in 
> > dh_installsystemd). I've reduced this bug severity accordingly.

> Per our discussion in #debian-mentors we'll need to wait for the 
> dh_installsystemd issue to be fixed.

Heads-up: #1031695 in dh_installsystemd will not get fixed for bookworm.
If your package expects the functionality to work, you have to fix
this bug in your package.

Chris

Bug#853154: configuration broken out of the box

[Sascha Steinbiss]

Hi Hamish,

thanks for the reminder.


The default configuration still seems to be broken.

The provided suricata.yaml refers to /etc/suricata/rules/suricata.rules 
as the rules file, but none is provided.


suricata-update writes rules to /var/lib/suricata, so even after running 
suricata-update, the config is invalid.


You are right. This seems to be because we're not installing
suricata-update with Suricata on Debian [0], which causes the
"ruledirprefix" variable in the configure script to be left at the
default of "sysconfdir", which is /etc. This leads to the
"e_defaultruledir" being /etc/suricata/rules, which ends up in the
default configuration.

I think the best option we have to address this issue is to force the
default rule path in the suricata.yaml that is installed in Debian to be
/var/lib/suricata/rules. Then provide an empty file by default. This
would address your immediate concern, and also keeps compatibility with
suricata-update, should the user decide to use it. That writes into the
same location, so the new rules are picked up automatically
(/var/lib/suricata/rules/suricata.rules).

Any comments? If not I'll implement this in an upcoming package update.

Note that the 'default installation' (i.e. completely unconfigured by
the user) is likely to be 'broken' still because one still needs to at
least define an actual inspection interface to use so Suricata can
start. The default is "eth0" which is unlikely to exist on modern 
systems (also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342).


Best
Sascha

[0] By passing --disable-suricata-update and patching the Makefile.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034112: piuparts: Incorrect link to manpage

[Helge Kreutzmann]

Package: piuparts
Severity: minor

On https://piuparts.debian.org/bug_howto.html there is a link (on the
left side) to a man page. The link points to
https://piuparts.debian.org/doc/piuparts.1.html However, it does not
work (i.e. it is 404).


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages piuparts depends on:
ii  debootstrap  1.0.128+nmu2
pn  debsums  
ii  libjs-sphinxdoc  5.3.0-4
ii  lsb-release  12.0-1
ii  lsof 4.95.0-1
ii  mount2.38.1-5+b1
pn  piuparts-common  
ii  python3  3.11.2-1
ii  python3-debian   0.1.49

Versions of packages piuparts recommends:
pn  adequate  

Versions of packages piuparts suggests:
pn  docker.io  
pn  schroot

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1034111: linux-image-6.1.0-0.deb11.5-amd64: Using bluetooth makes wifi stop working after a while ("a while" may be hours or it may be days)

[Steinar Bang]

Package: src:linux
Version: 6.1.12-1~bpo11+1
Severity: normal
X-Debbugs-Cc: s...@dod.no

Dear Maintainer,

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

   * What led up to the situation?

I bought a Logitech MX Master 3S wireless mouse.
The mouse came with both an USB dongle and the possibility of using bluetooth.
I installed blueman with "apt install blueman".
A bluetooth icon appeared on the top menu bar on my MATE desktop, and I was
able to discover and use the MX Master mouse.

Everything worked find until the network suddenly disappeared.
The NIC still showed up on lspci, but the WLAN NIC was gone from "ifconfig"
output.

I was able to plug the laptop into a wired network and that worked perfectly,
but the WLAN NIC didn't work.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

What I did that was ineffective:
1. restart the networking with "systemctl restart networking"
2. reboot the computer

For these nothing changed. I.e. the network was still gone.

What I did that was effective:
1. Shut the computer down and start it again

This worked: after reboot the wireless network came back.

Since the first time this happened I first tried stopping to use the mouse, but
leave the bluetooth support in place, and after a couple of days, the same
thing happened again: the wireless NIC died.

I then removed blueman "apt remove blueman" and that seemed to take much of the
bluetooth support away. And then the laptop ran for over a week without the
wireless NIC going away.

I reinstalled blueman and started using the mouse again and since then the
computer has run for a while before the wireless NIC dies. What I do then is
power the laptop down and power it back up, and then it runs for a new while
(hours to days) before the NIC goes away.

The reason I suspect a connection between bluetooth and wireless NIC is that
this didn't happen for the 7 months I've had the laptop until I started using
bluetooth, and because both bluetooth and WLAN is handled by the same MEDIATEK
Corp. MT7921 chip.


-- Package-specific info:
** Version:
Linux version 6.1.0-0.deb11.5-amd64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP PREEMPT_DYNAMIC Debian 6.1.12-1~bpo11+1 (2023-03-05)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-0.deb11.5-amd64 
root=UUID=9748403e-c93c-4785-b6bb-70be61aa3749 ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Acer
product_name: Aspire A515-45
product_version: V1.10
chassis_vendor: Chassis Manufacturer
chassis_version: Chassis Version
bios_vendor: INSYDE Corp.
bios_version: V1.10
board_vendor: LN
board_name: Calla_LC
board_version: V1.10

** Loaded modules:
usbhid
ctr
ccm
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
binfmt_misc
bnep
squashfs
nls_ascii
nls_cp437
loop
vfat
fat
mt7921e
intel_rapl_msr
mt7921_common
intel_rapl_common
btusb
edac_mce_amd
btrtl
mt76_connac_lib
btbcm
btintel
kvm_amd
btmtk
mt76
bluetooth
joydev
kvm
mac80211
irqbypass
snd_hda_codec_realtek
libarc4
jitterentropy_rng
snd_hda_codec_generic
ghash_clmulni_intel
ledtrig_audio
uvcvideo
sha512_ssse3
cfg80211
sha512_generic
videobuf2_vmalloc
snd_hda_codec_hdmi
videobuf2_memops
videobuf2_v4l2
drbg
videobuf2_common
snd_hda_intel
ansi_cprng
snd_intel_dspcfg
acer_wmi
snd_intel_sdw_acpi
videodev
ecdh_generic
snd_hda_codec
sparse_keymap
aesni_intel
snd_hda_core
snd_pci_acp6x
ecc
mc
snd_hwdep
crypto_simd
snd_pci_acp5x
cryptd
snd_pcm
rapl
wmi_bmof
snd_rn_pci_acp3x
snd_timer
snd_acp_config
ccp
snd_soc_acpi
snd
wdat_wdt
rfkill
sp5100_tco
k10temp
pcspkr
soundcore
snd_pci_acp3x
rng_core
watchdog
acer_wireless
acpi_cpufreq
ac
hid_multitouch
evdev
serio_raw
msr
parport_pc
ppdev
lp
parport
fuse
efi_pstore
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
amdgpu
gpu_sched
drm_buddy
i2c_algo_bit
drm_display_helper
nvme
cec
xhci_pci
rc_core
ahci
xhci_hcd
nvme_core
drm_ttm_helper
libahci
ttm
t10_pi
libata
drm_kms_helper
usbcore
r8169
crc64_rocksoft
crc64
crc_t10dif
realtek
crct10dif_generic
hid_generic
mdio_devres
crct10dif_pclmul
drm
scsi_mod
crc32_pclmul
crc32c_intel
libphy
i2c_piix4
scsi_common
usb_common
crct10dif_common
battery
i2c_hid_acpi
video
i2c_hid
hid
wmi
button

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel state 
DOWN group default qlen 1000
link/ether c0:18:50:91:da:3e brd ff:ff:ff:ff:ff:ff
3: wlp4s0:  mtu 1500 

Bug#1034110: Newer version upstream

[Dan Jacobson]

Package: testdisk

testdisk-7.2-WIP.linux26-x86_64.tar.bz2 is available upstream.

Bug#1034100: Acknowledgement (unblock: texlive-base/2022.20230122-3)

[Sebastian Ramacher]

Control: tags -1 moreinfo confirmed

On 2023-04-09 00:29:55 +0200, Hilmar Preuße wrote:
> On 4/9/23 00:24, Debian Bug Tracking System wrote:
> 
> Hi,
> 
> > You can follow progress on this Bug here: 1034100:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034100.
> > 
> Attached is the promised debdiff.

Please go ahead and remove the moreinfo tag once the package is
available in unstable.

Cheers

> 
> Hilmar
> --
> Testmail

> diff -Nru texlive-base-2022.20230122/debian/changelog 
> texlive-base-2022.20230122/debian/changelog
> --- texlive-base-2022.20230122/debian/changelog   2023-02-15 
> 14:35:08.0 +0100
> +++ texlive-base-2022.20230122/debian/changelog   2023-04-01 
> 12:57:29.0 +0200
> @@ -1,3 +1,12 @@
> +texlive-base (2022.20230122-3) UNRELEASED; urgency=medium
> +
> +  * Add Romanian debconf translation by Remus-Gabriel Chelu
> + (Closes: #1033738).
> +  * Add patch to fix hyphenation penalties in german language
> +(Closes: #1034038).
> +
> + -- Hilmar Preusse   Sat, 01 Apr 2023 12:57:29 +0200
> +
>  texlive-base (2022.20230122-2) unstable; urgency=medium
>  
>[ Jelmer Vernooij ]
> diff -Nru texlive-base-2022.20230122/debian/patches/1034038 
> texlive-base-2022.20230122/debian/patches/1034038
> --- texlive-base-2022.20230122/debian/patches/1034038 1970-01-01 
> 01:00:00.0 +0100
> +++ texlive-base-2022.20230122/debian/patches/1034038 2023-04-01 
> 12:57:29.0 +0200
> @@ -0,0 +1,11 @@
> +--- 
> texlive-base-2022.20230122.orig/texmf-dist/tex/generic/babel/babel-transforms.lua
>  
> texlive-base-2022.20230122/texmf-dist/tex/generic/babel/babel-transforms.lua
> +@@ -364,7 +364,7 @@
> + goto next
> + 
> +   elseif mode == 1 and crep and (crep.pre or crep.no or crep.post) 
> then
> +-d = node.new(7, 0)   -- (disc, discretionary)
> ++d = node.new(7, 3)   -- (disc, regular)
> + d.pre = Babel.str_to_nodes(crep.pre, matches, item_base)
> + d.post= Babel.str_to_nodes(crep.post, matches, item_base)
> + d.replace = Babel.str_to_nodes(crep.no, matches, item_base)
> diff -Nru texlive-base-2022.20230122/debian/patches/series 
> texlive-base-2022.20230122/debian/patches/series
> --- texlive-base-2022.20230122/debian/patches/series  2023-02-15 
> 14:16:01.0 +0100
> +++ texlive-base-2022.20230122/debian/patches/series  2023-04-01 
> 12:57:29.0 +0200
> @@ -25,3 +25,4 @@
>  python3-shebang
>  debian-fix-quote-in-quote
>  update_epspdf_luascript
> +1034038
> diff -Nru texlive-base-2022.20230122/debian/po/ro.po 
> texlive-base-2022.20230122/debian/po/ro.po
> --- texlive-base-2022.20230122/debian/po/ro.po1970-01-01 
> 01:00:00.0 +0100
> +++ texlive-base-2022.20230122/debian/po/ro.po2023-04-01 
> 12:55:00.0 +0200
> @@ -0,0 +1,77 @@
> +# Mesajele în limba română pentru pachetul texlive-base.
> +# Romanian translation of texlive-base.
> +# Copyright © 2023 THE PACKAGE'S COPYRIGHT HOLDER
> +# This file is distributed under the same license as the texlive-base 
> package.
> +#
> +# Remus-Gabriel Chelu , 2023.
> +#
> +# Cronologia traducerii fișierului „texlive-base”:
> +# Traducerea inițială, făcută de R-GC, pentru versiunea texlive-base 
> 2022.20230122-2(2012-04-24).
> +# Actualizare a traducerii pentru versiunea Y, făcută de X, Y(anul).
> +#
> +msgid ""
> +msgstr ""
> +"Project-Id-Version: texlive-base 2022.20230122-2\n"
> +"Report-Msgid-Bugs-To: texlive-b...@packages.debian.org\n"
> +"POT-Creation-Date: 2012-04-24 14:30+0900\n"
> +"PO-Revision-Date: 2023-03-26 17:57+0200\n"
> +"Last-Translator: Remus-Gabriel Chelu \n"
> +"Language-Team: Romanian \n"
> +"Language: ro\n"
> +"MIME-Version: 1.0\n"
> +"Content-Type: text/plain; charset=UTF-8\n"
> +"Content-Transfer-Encoding: 8bit\n"
> +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n==0 || (n!=1 && n%100>=1 && "
> +"n%100<=19) ? 1 : 2);\n"
> +"X-Bugs: Report translation errors to the Language-Team address.\n"
> +"X-Generator: Poedit 3.2.2\n"
> +
> +#. Type: error
> +#. Description
> +#: ../texlive-base.templates:2001
> +msgid "Unmanageable system paper size (${libpaperPaper})"
> +msgstr "Dimensiune de hârtie de sistem imposibil de gestionat 
> (${libpaperPaper})"
> +
> +#. Type: error
> +#. Description
> +#: ../texlive-base.templates:2001
> +msgid ""
> +"The currently defined system-wide paper size is ${libpaperPaper}. However, 
> the "
> +"TeX configuration system cannot handle this paper size for ${binary}."
> +msgstr ""
> +"Dimensiunea de hârtie definită în prezent pentru întregul sistem este "
> +"${libpaperPaper}. Cu toate acestea, sistemul de configurare TeX nu poate "
> +"gestiona această dimensiune de hârtie pentru ${binary}."
> +
> +#. Type: error
> +#. Description
> +#: ../texlive-base.templates:2001
> +msgid "The setting will remain unchanged."
> +msgstr "Configurarea va rămâne neschimbată."
> +
> +#. Type: error
> +#. Description
> +#: ../texlive-base.templates:2001
> 

Bug#1034076: unblock: spf-engine/3.0.4-1

[Sebastian Ramacher]

Control: tags -1 confirmed moreinfo

On 2023-04-08 00:17:24 -0400, Scott Kitterman wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package spf-engine
> 
> (Please provide enough (but not too much) information to help
> the release team to judge the request efficiently. E.g. by
> filling in the sections below.)
> 
> [ Reason ]
> Fixes a bug that will cause mail processing to stop for systems which
> send mail to/from local users that doesn't have a fully qualified domain
> name.  This a regression from Bullseye.
> 
> [ Impact ]
> For most users, none, but for users sending to local addresses, mail
> will stop flowing after upgrade from Bullseye to Bookworm.
> 
> [ Tests ]
> The affected code was tested by the original bug reporter and they
> verified that the fix worked without unwanted side effects.
> 
> [Risks ]
> Risk is negligible.  Very small code change that's been tested.  There
> is not autopkgtest as the upstream test suite (such as it is, I'm not
> proud of it) isn't suitable.  This is a leaf package, so there's no risk
> of negative effects on other packages.
> 
> [ Checklist ]
>   [*] all changes are documented in the d/changelog
>   [*] I reviewed all changes and I approve them
>   [*] attach debdiff against the package in testing
> 
> [ Other info ]
> I haven't uploaded this yet, but it's prepared in git locally for upload
> if approved.  The only thing I have to do relative to what's in the
> debdiff is dch -r to mark it released.

Please go ahead and remove the moreinfo tag once the package is in
unstable.

Cheers

> 
> This is something I would ask for a post-release update to fix if I
> didn't find out about until after Bookworm's release.
> 
> unblock spf-engine/3.0.4-1

> diff -Nru spf-engine-3.0.3/CHANGES spf-engine-3.0.4/CHANGES
> --- spf-engine-3.0.3/CHANGES  2023-02-19 19:30:05.819651600 -0500
> +++ spf-engine-3.0.4/CHANGES  2023-04-07 20:46:47.963843000 -0400
> @@ -4,6 +4,10 @@
>  #   ! = Changed something significant, or removed a feature
>  #   * = Fixed a bug, or made a minor improvement
>  
> +--- 3.0.4 (2023-04-07)
> +  * Fix recipient logging to not cause an error for local (not fully
> +qualified) email addresses (LP: #2015609)
> +
>  --- 3.0.3 (2023-02-19)
>* Fix reference to QueueID in policydspfsupp.py (LP: #2007123), thanks to
>  Wolfgang Karall-Ahlborn for the bug and the fix
> diff -Nru spf-engine-3.0.3/debian/changelog spf-engine-3.0.4/debian/changelog
> --- spf-engine-3.0.3/debian/changelog 2023-02-19 20:13:27.0 -0500
> +++ spf-engine-3.0.4/debian/changelog 2023-04-08 00:06:57.0 -0400
> @@ -1,3 +1,9 @@
> +spf-engine (3.0.4-1) UNRELEASED; urgency=medium
> +
> +  * New upstream release
> +
> + -- Scott Kitterman   Sat, 08 Apr 2023 00:06:57 -0400
> +
>  spf-engine (3.0.3-1) unstable; urgency=medium
>  
>* New upstream release
> diff -Nru spf-engine-3.0.3/PKG-INFO spf-engine-3.0.4/PKG-INFO
> --- spf-engine-3.0.3/PKG-INFO 1969-12-31 19:00:00.0 -0500
> +++ spf-engine-3.0.4/PKG-INFO 1969-12-31 19:00:00.0 -0500
> @@ -1,6 +1,6 @@
>  Metadata-Version: 2.1
>  Name: spf-engine
> -Version: 3.0.3
> +Version: 3.0.4
>  Summary: SPF (Sender Policy Framework) processing engine for Postfix policy 
> server and Milter implemented in Python.
>  Keywords: Postfix,Sendmail,milter,spf,email
>  Author-email: Scott Kitterman 
> diff -Nru spf-engine-3.0.3/spf_engine/__init__.py 
> spf-engine-3.0.4/spf_engine/__init__.py
> --- spf-engine-3.0.3/spf_engine/__init__.py   2023-02-19 19:30:53.016298500 
> -0500
> +++ spf-engine-3.0.4/spf_engine/__init__.py   2023-04-07 22:36:19.567618000 
> -0400
> @@ -40,7 +40,7 @@
> 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
>  '''
>  
> -__version__ = "3.0.3"
> +__version__ = "3.0.4"
>  
>  import syslog
>  import os
> diff -Nru spf-engine-3.0.3/spf_engine/policyd_spf.py 
> spf-engine-3.0.4/spf_engine/policyd_spf.py
> --- spf-engine-3.0.3/spf_engine/policyd_spf.py2022-12-01 
> 21:07:37.670749200 -0500
> +++ spf-engine-3.0.4/spf_engine/policyd_spf.py2023-04-07 
> 20:44:54.125643300 -0400
> @@ -94,7 +94,10 @@
>  elif configData.get('Hide_Receiver') != 'No':
>  data['recipient'] = ''
>  elif data.get('recipient') != 'none':
> -data['recipient'] = data.get('recipient').split('@')[1]
> +try:
> +data['recipient'] = data.get('recipient').split('@')[1]
> +except IndexError:
> +pass # local recipients may not be fully qualified, so 
> no "@".
>  if debugLevel >= 3: syslog.syslog('Config: %s' % str(configData))
>  #  run the checkers  {{{3
>  checkerValue = None


-- 
Sebastian Ramacher

Bug#782007: criu: Split up binary packages

[Salvatore Bonaccorso]

Hi!

On Sun, Apr 09, 2023 at 03:32:19AM +0300, Faidon Liambotis wrote:
> Control: tags -1 patch
> 
> On Mon, Apr 06, 2015 at 02:00:46PM +0200, Salvatore Bonaccorso wrote:
> > I think it would make sense in meanwhile to split up the criu binary
> > package (although still small) into multiple binary packages: E.g.
> > criu, criu-dbg, libcriuX, libcriu-dev, python-criu.
> 
> I submitted an MR implementing this:
> https://salsa.debian.org/debian/criu/-/merge_requests/3
> 
> Looking forward to your review!

Thanks for doing the work, I will have a look but any such change will
happen only after the bookworm release.

Regards,
Salvatore

Bug#1034086: tcpdump: CVE-2023-1801

[Salvatore Bonaccorso]

Hi Romain,

On Sat, Apr 08, 2023 at 09:49:05PM +0200, Romain Francoise wrote:
> Hi Salvatore,
> 
> On Sat, Apr 8, 2023 at 1:51 PM Salvatore Bonaccorso  wrote:
> > The following vulnerability was published for tcpdump.
> >
> > CVE-2023-1801[0]:
> > | The SMB protocol decoder in tcpdump version 4.99.3 can perform an out-
> > | of-bounds write when decoding a crafted network packet.
> 
> Thanks. Just in case, I will mention that the SMB printer code is
> *not* enabled in Debian anymore. None of the supported distributions
> (oldstable, stable, testing/sid) are affected.

Ah right, I see the binary packages are not affected by the respective
code path, so have marked this in the security-tracker accordingly as
unimportant.

Thanks,

Regards,
Salvatore

Bug#1034109: rust-fancy-regex: Please upload newer upstream version (at least 0.10.0)

[Petter Reinholdtsen]

Package: librust-fancy-regex-dev
Version: 0.7.1-1
Severity: wishlist

The tiktoken package used by Whisper, WNPP request #1034091, depend on
fancy-regex version 0.10.0.  To make it possible to pack tiktoken in
Debian, please update librust-fancy-regex-dev to a newer version.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1034108: System trying to remove main files after adding the i386 architecture and installing certain packages.

[Md Adil]

Package: Debian
Version: Debian 11 bullseye arm64

After adding the i386 architecture then try to install packages it
autoremoving the main required packages.

which apt-get
/usr/bin/apt-get

type apt-get
apt-get is /usr/bin/apt-get

dpkg --search /usr/bin/apt-get
apt: /usr/bin/apt-get

dpkg --list apt
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii apt 2.2.4 arm64 commandline package manager

dpkg --status apt
Package: apt
Status: install ok installed
Priority: required
Section: admin
Installed-Size: 4181
Maintainer: APT Development Team 
Architecture: arm64
Version: 2.2.4
Replaces: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~)
Provides: apt-transport-https (= 2.2.4)
Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.2.4),
debian-archive-keyring, libc6 (>= 2.17), libgcc-s1 (>= 3.0), libgnutls30
(>= 3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 9), libsystemd0
Recommends: ca-certificates
Suggests: apt-doc, aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), gnupg
| gnupg2 | gnupg1, powermgmt-base
Breaks: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~),
aptitude (<< 0.8.10)
Conffiles:
 /etc/apt/apt.conf.d/01autoremove ab6540f7278a05a4b7f9e58afcaa5f46
 /etc/cron.daily/apt-compat 49e9b2cfa17849700d4db735d04244f3
 /etc/kernel/postinst.d/apt-auto-removal 6486b24d4c496e7d6a443178869a019b
 /etc/logrotate.d/apt 179f2ed4f85cbaca12fa3d69c2a4a1c3
Description: commandline package manager
 This package provides commandline tools for searching and
 managing as well as querying information about packages
 as a low-level access to all features of the libapt-pkg library.
 .
 These include:
  * apt-get for retrieval of packages and information about them
from authenticated sources and for installation, upgrade and
removal of packages together with their dependencies
  * apt-cache for querying available information about installed
as well as installable packages
  * apt-cdrom to use removable media as a source for packages
  * apt-config as an interface to the configuration settings
  * apt-key as an interface to manage authentication keys

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

hostnamectl
Static hostname: raspberrypi
 Icon name: computer
Machine ID: 6bed9a922dc84fcfb9b02f5403468ce1
   Boot ID: ebfe7cff77d341fa9cca50e0aa20bf74
  Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
  Architecture: arm64

The architecture I added and update success:
sudo dpkg --add-architecture i386

Packages that I tried to install and the output:

sudo apt install libc6:i386 libncurses5:i386 libstdc++6:i386 libbz2-1.0:i386

Output file:


output.log
Description: Binary data