Bug#1008779: 1.37-1 has been uploaded to DELAYED/7

[Jordi Mallach]

Hi,

This is to state that after 21 days, I've uploaded postgrey to
DELAYED/7, as documented in the salvaging procedure.

Jordi

-- 
Jordi Mallach 
Debian Project

Bug#1009918: virtualbox memset symbol fix

[Gianfranco Costamagna]

control: fixed -1 6.1.34-dfsg-2
control: close -1
On Thu, 21 Apr 2022 03:37:12 +0200 Jan Nordholz  wrote:

Hi,

the attached one-liner diff fixes the symbol issue and enables me to run
my Virtualbox VMs again. (However, I didn't check how the addition of
this flag to CXXFLAGS affects the rest of R0 compilation - on the other
hand, it's already there in CFLAGS.)

The missing 'memset' symbol is caused by a compiler-generated call to
memset(), not by an actual call in the source code - my guess is that
g++ emits it to optimize this loop that was added for 6.1.34:

=
--- ./virtualbox-6.1.32-dfsg/src/VBox/Devices/Network/DevE1000.cpp  
2022-01-13 19:55:54.0 +0100
+++ ./virtualbox-6.1.34-dfsg/src/VBox/Devices/Network/DevE1000.cpp  
2022-03-23 00:43:01.0 +0100
@@ -5462,6 +5543,17 @@
 AssertMsgFailed(("Impossible descriptor type!"));
 continue;
 }
+if (fInvalidPacket)
+{
+for (int index = pThis->iTxDCurrent; index < i; ++index)
+pThis->afTxDValid[index] = false; /* Make sure all descriptors 
for this packet are skipped by processing */
+LogFlow(("%s e1kLocateTxPacket: marked %d descriptors as invalid\n", 
pThis->szPrf, i - pThis->iTxDCurrent));
+LogFlow(("%s e1kLocateTxPacket: RET true cbTxAlloc=%d 
cbPacket=%d%s%s\n",
+ pThis->szPrf, pThis->cbTxAlloc, cbPacket,
+ pThis->fGSO ? " GSO" : "", fTSE ? " TSE" : ""));
+pTxdc->nextPacket = i;
+return true;
+}
 if (pDesc->legacy.cmd.fEOP)
 {
 /*
=

Feel free to forward upstream.

Best regards



thanks for the patch, however a similar patch was already committed upstream.

G.

Bug#1010002: libgeos++-dev: Missing files or misconfigured build

[Sebastiaan Couwenberg]

On 4/22/22 09:19, Pierre Gergondet wrote:

I kindly disagree. This is not related to the API, the package is broken:
the build is either misconfigured or the package is missing critical files
for the compilation of programs dependent upon the C++ API.


The files are explicitly removed because the C++ API should not be used 
by others.


Having to rebuild rdeps for every upstream release is unacceptable.

Kind Regards,

Bas

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

Bug#716555: [Mayhem] Bug report on omniorb: omniMapper crashes with exit status 139

[Neil Williams]

On Wed, 10 Jul 2013 15:37:18 -0400 Alexandre Rebert 
wrote:
> Package: omniorb
> Version: 4.1.6-2
> Severity: normal
> User: may...@forallsecure.com
> Usertags: mayhem
> 
> omniMapper crashes with exit status 139. We confirmed the crash by
> re-running it in a fresh debian unstable installation.

Apologies for taking so long to reply to this bug. Omniorb 4.2.5 is now
available in Debian unstable, testing and a backport has been made to
stable (bullseye).

The URL in the bug is now a 404 but the omniMapper-report.tar.bz2
attachment remains, so thanks for providing that.

I have reproduced the crash on Stretch (omniorb 4.1.6-2.1+b1).
crash.sh: line 12: warning: command substitution: ignored null byte in
input
crash.sh: line 19:  7401 Segmentation fault  env -i MALLOC_CHECK_=0
$GDB /usr/bin/omniMapper "`cat $DIR/argv_1.symb`" <
"$DIR/file___dev__stdin.symb"


The crash no longer happens with 4.2.5:
crash.sh: line 12: warning: command substitution: ignored null byte in
input

usage: omniMapper [-port ]
  [-config ]
  [-v]

With no -port argument, the standard default of 2809 is used.

Use -config to specify the location of omniMapper's config file.

Alternatively, set the environment variable OMNIMAPPER_CONFIG
or use the default /etc/omniMapper.cfg.

Use -v to verbosely record what's going on.

I'll close this bug report with the next upload of omniorb.

-- 
Neil Williams
=
https://linux.codehelp.co.uk/


pgp743XM79ry_.pgp
Description: OpenPGP digital signature

Bug#1010003: ITP: dynamic-motd -- gives some informations when you log into a server through SSH

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: dynamic-motd
  Version : 0.04
  Upstream Author : Luc Didry 
* URL : https://github.com/ldidry/dynamic-motd
* License : GPL-2
  Programming Lang: Python
  Description : gives some informations when you log into a server through S

 dynamic-motd replaces the standard /etc/motd prompt by a more dynamic thingy,
 which is also modular, so you can customize the SSH motd with information from
 your system.

Bug#978748: libboost-dev: Boost 1.75

[Giovanni Mascellani]

Hi,

Il 14/04/22 04:24, strager ha scritto:

Is there anything I can do to help get a newer version of Boost into
the Debian repository?


Unfortunately I am not having a lot of time to care about Boost right 
now, even if I'll get to it as soon as possible. I don't know what is 
your experience with Debian packaging, but Boost if you're a beginner I 
don't feel it's the right package to start with.


As you say, vendoring code is usually not considered a good idea in 
Debian, but in can be a reasonable interim solution, I'd say, as long as 
you're happy to switch back to the packaged dependency once it is 
available. I would suggest you to investigate this road for 
quick-lint-js. I won't be able to provide much help, though.


Thanks, Giovanni.
--
Giovanni Mascellani 

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Jeff]

Going through what changed between the previous successful build

https://buildd.debian.org/status/fetch.php?pkg=libpdf-builder-perl&arch=all&ver=3.023-1&stamp=1631870648&raw=0

and the failure:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdf-builder-perl.html

I see the following changes in the dependency versions:

libbrotli1_1.0.9-2+b2 -> b3
libfreetype6_2.10.4+dfsg-1 -> 2.11.1+dfsg-1
fontconfig-config_2.13.1-4.2 -> .4
libfontconfig1_2.13.1-4.2 -> .4
libaom0_1.0.0.errata1-3 -> libaom3_3.3.0-1
libdav1d5_0.9.2-1 -> +b1
libnuma1_2.0.12-1+b1 -> 2.0.14-3
libx265-192_3.4-2 -> -199_3.5-2
libheif1_1.12.0-2+b1 -> b3
libjpeg62-turbo_1%3a2.0.6-4 -> 1%3a2.1.2-1
libglib2.0-0_2.68.4-1 -> 2.72.1-1
libltdl7_2.4.6-15 -> 2.4.7-3
libopenjp2-7_2.4.0-3 -> -6
libdeflate0_1.7-2 -> 1.10-2
libwebp6_0.6.1-2.1 -> libwebp7_1.2.2-2+b1
libtiff5_4.3.0-2 -> -6
libwebpdemux2_0.6.1-2.1 -> 1.2.2-2+b1
libwebpmux3_0.6.1-2.1 -> 1.2.2-2+b1
libmd0_1.0.3-3 -> 1.0.4-1
libbsd0_0.11.3-1 -> 0.11.6-1
libx11-data_2%3a1.7.2-2 -> 2%3a1.7.5-1
libx11-6_2%3a1.7.2-2+b1 -> 2%3a1.7.5-1
libxml2_2.9.12+dfsg-4 -> 2.9.13+dfsg-1
libmagickcore-6.q16-6_8%3a6.9.11.60+dfsg-1.3 -> +b2
libmagickwand-6.q16-6_8%3a6.9.11.60+dfsg-1.3 -> +b2
imagemagick-6.q16_8%3a6.9.11.60+dfsg-1.3 -> +b2
libmagic-mgc_1%3a5.39-3 -> 1%3a5.41-3
libmagic1_1%3a5.39-3 -> 1%3a5.41-3
file_1%3a5.39-3 -> 1%3a5.41-3
autotools-dev_20180224.1+nmu1 -> 20220109.1
automake_1%3a1.16.4-2 -> 1%3a1.16.5-1.3
autopoint_0.21-4 -> -6
libdebhelper-perl_13.5.1 -> 13.7.1
libtool_2.4.6-15 -> 2.4.7-3
libfile-stripnondeterminism-perl_1.12.0-1 -> 1.13.0-1
dh-strip-nondeterminism_1.12.0-1 -> 1.13.0-1
libelf1_0.185-2 -> 0.186-1
gettext_0.21-4 -> -6
debhelper_13.5.1 -> 13.7.1
libgs9-common_9.54.0~dfsg-5 -> 9.56.0~dfsg-1
libgs9_9.54.0~dfsg-5 -> 9.56.0~dfsg-1
ghostscript_9.54.0~dfsg-5 -> 9.56.0~dfsg-1
libdbus-1-3_1.12.20-2 -> 1.14.0-1
libcups2_2.3.3op2-7 -> 2.4.1op1-2
libgd3_2.3.0-2 -> +b1
libgd-perl_2.73-1+b1 -> 2.76-2+b1
libgraphics-tiff-perl_16-1 -> 18-1+b1
libimage-png-libpng-perl_0.57-1 -> -2+b1
libpadwalker-perl_2.5-1+b1 -> b2

The libcms2 version is identical, so I don't think that is the problem.

If I have interpreted the versioning correctly, the imagemagick change 
should be negligible.


However, the ghostscript change is not, and indeed the error messages 
look like they come from ghostscript:


Error: /typecheck in --runpdf--
Operand stack:
   --dict:6/14(L)--   --dict:6/14(L)--   --dict:6/14(L)--   MediaBox 
--nostringval--   20.0   20.0   20.0   20.0   false   20.0   2

Execution stack:
   %interp_exit   .runexec2   --nostringval--   runpdf 
--nostringval--   2   %stopped_push   --nostringval--   runpdf   runpdf 
 false   1   %stopped_push   1990   1   3   %oparray_pop   1989   1   3 
  %oparray_pop   1977   1   3   %oparray_pop   1978   1   3 
%oparray_pop   runpdf   runpdf   2   1   1   runpdf 
%for_pos_int_continue   runpdf   runpdf   runpdf

Dictionary stack:
   --dict:765/1123(ro)(G)--   --dict:0/20(G)--   --dict:76/200(L)-- 
--dict:18/20(L)--

Current allocation mode is local
Last OS error: No such file or directory


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Mark Hindley]

Helge,

On Wed, Apr 20, 2022 at 08:39:44PM +0200, Helge Kreutzmann wrote:
> > The other possibility might be dpkg-diverts. Perhaps that depends on how 
> > many
> > conflicts there actually are/will be. I will try to quantify that more
> > accurately.
> 
> That is an interesting idea. Than I wait for your analysis, thanks.

I have just compared the manpage lists in sysvinit, manpages-l10n and
systemd. AFAICS the duplicates are the 7 in systemd-sysv:

  init.1
  halt.8
  poweroff.8
  reboot.8
  runlevel.8
  shutdown.8
  telinit.8

src:sysvinit has manpage translations for 7 languages: de es fi fr hu id pl.

That seems a manageable number to handle through dpkg-divert.

Mark

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Mark Hindley]

Thorsten,

Thanks for your input, as always.

On Wed, Apr 20, 2022 at 08:38:57PM +0200, Thorsten Glaser wrote:
> > The other possibility might be dpkg-diverts. Perhaps that depends on how 
> > many
> > conflicts there actually are/will be. I will try to quantify that more
> > accurately.
> 
> Or Replaces: but that has downsides on deinstallation.

Yes. And I am unclear how dpkg would behave if sysvinit-core was installed
Replacing the manpages-l10n versions but then manpages-l10n was upgraded.

dpkg-divert seems preferable to me.

Thanks

Mark

Bug#1010004: RFS: odr-dabmod/2.6.0-1 [ITP] -- DAB modulator compliant to ETSI EN 300 401

[Robin ALEXANDER]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "odr-dabmod":

 * Package name    : odr-dabmod
   Version : 2.6.0-1
   Upstream Author : Matthias P. Braendli 
 * URL : https://www.opendigitalradio.org/mmbtools
 * License : FSFAP, GPL-2+ with Autoconf-data exception, GPL-
3.0+ with autoconf exception, GPL-3.0+, Apache-2.0, BSD-3-Clause,
EXPAT, LGPL-3, GPL-2.0+, Expat
 * Vcs : https://salsa.debian.org/ralex/odr-dabmod
   Section : hamradio

The source builds the following binary packages:

  odr-dabmod - DAB modulator compliant to ETSI EN 300 401

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

  https://mentors.debian.net/package/odr-dabmod/

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

  dget -x
https://mentors.debian.net/debian/pool/main/o/odr-dabmod/odr-dabmod_2.6.0-1.dsc

Changes for the initial release:

 odr-dabmod (2.6.0-1) unstable; urgency=low
 .
   * Initial release. Closes: #1007104

Regards,

-- 
Robin ALEXANDER



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

Bug#1010005: cloud.debian.org: AMIs lists of Bullseye and Buster have not been updated

[gco...@one-tm.com]

Package: cloud.debian.org
Severity: normal

Dear Maintainer,

It appears that the "AMI names" and "region-specific AMI IDs" listed in the URL 
below are not up to date.
https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye
https://wiki.debian.org/Cloud/AmazonEC2Image/Buster


-- System Information:
Debian Release: 10.12
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-20-cloud-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1010006: RM: node-temporary -- ROM; Incompatible with Node.js >= 14

[Yadd]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 1009...@bugs.debian.org

Hi all,

node-temporary is incompatible with Node.js >= 14 (#1009528). It has no
reverse dependencies and then should be removed from Debian.

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Jeff]

My machine running testing currently has ghostscript 9.55.0, and there 
it still builds fine. So I'm guessing the problem is between 9.55.0 and 
9.56.0.


Indeed since the failure with 9.56.0, 9.56.1 has been uploaded.

I've just tried building it with 9.56.1 but it still has the same two 
failures.


I'll do some debugging.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009685: Please close as resolved without package upload

[Markus Blatt]

As the transition to python3.10 is finished and the missing library 
/usr/lib/x86_64-linux-gnu/libpython3.10.so will now be there when running

the autopkgtest, I believe the only thing preventing migration of opm-grid
Version 2021.10-3, is this bug being open. The autpkgtests are green on [1].

I hope that we can simply close this bug without uploading a new package version
with any changes. I abstained from closing it myself, as I am not sure whether
that would be rude. I am happy to close it myself if that is ok.

[1] https://qa.debian.org/excuses.php?package=opm-grid


signature.asc
Description: PGP signature

Bug#1010007: ITP: mathcomp-zify -- Micromega arithmetic solvers for Mathematical Components

[Julien Puydt]

Package: wnpp
Severity: wishlist
Owner: Julien Puydt 
X-Debbugs-Cc: Debian OCaml Maintainers , 
jpu...@debian.org

* Package name: mathcomp-zify
  Version : 1.2.0+1.12+8.13
  Upstream Author : Kazuhiko Sakaguchi
* URL : https://github.com/math-comp/mczify
* License : CeCILL-B
  Programming Lang: Coq
  Description : Micromega arithmetic solvers for Mathematical Components
 This package enables the use of the micromega arithmetic solvers
 of Coq for goals stated with the Mathematical Components library,
 by extending the zify tactic.
 .
 The Mathematical Components library is a coherent repository of
 general-purpose formalized mathematical theories for the
 Coq proof assistant.

I plan to maintain it within the Debian Ocaml Maintainers team, along with the
rest of the Coq+MathComp packages.

Cheers,

J.Puydt

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Jeff]

To confirm - I've just put the 3 packages for gs 9.56.1 (and nothing 
else) from sid on my testing machine, and now I see the same failures.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#955551: Is this still broken?

[Dr. Bas Wijnen]

Hi,

On Debian's buildd this does not appear to be a problem (anymore?); all of
ppc64, ppc64el and s390x are successfully built.

So it appears this bug has been fixed by now. Can it be closed?

Thanks,
Bas Wijnen


signature.asc
Description: PGP signature

Bug#1010009: RM: node-connect-timeout -- ROM; useless and RC-buggy

[Yadd]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 1009...@bugs.debian.org

Hi,

node-connect-timeout has no reverse dependencies and seems incompatible
with Node.js >= 14. It should be removed from Debian

Bug#1009865: transition: octave

[Sébastien Villemot]

Le jeudi 21 avril 2022 à 09:57 +0200, Sébastien Villemot a écrit :
> Le mercredi 20 avril 2022 à 12:06 +0200, Sebastian Ramacher a écrit :
> > On 2022-04-19 15:57:14 +0200, Sébastien Villemot wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: transition
> > > X-Debbugs-Cc: debian-oct...@lists.debian.org
> > > 
> > > Please schedule a transition for octave. The new major upstream release
> > > (7.1.0), currently in experimental, changes the ABI. 
> > 
> > Please go ahead
> 
> Thanks. The new version of octave was uploaded to unstable and built on
> all release architectures.

The transition is mostly over. I suggest to remove octave-mpi and
octave-level-set from testing, and call it a day!

Thanks for your help,

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




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

Bug#1010008: node-fd-slicer: stream errors are no more reported

[Yadd]

On 13/04/2022 13:19, Yadd wrote:

Control: tags -1 + help

On 12/04/2022 21:22, Lucas Nussbaum wrote:

Source: node-fd-slicer
Version: 1.1.0+repack1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm

Hi,

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


Package is broken with node 14. Maybe someone can help here ?


I fixed RC-bug (#1009585): disable test that should report a stream 
error. It seems that Node.js streams behavior change and fd-slicer 
errors are no more reported.

Bug#1010010: ITP: python-fhs -- Python module for using the FHS and XDG basedir paths.

[Bas Wijnen]

Package: wnpp
Severity: wishlist
Owner: Bas Wijnen 
X-Debbugs-Cc: debian-de...@lists.debian.org, wij...@debian.org

* Package name: python-fhs
  Version : 1.0
  Upstream Author : Bas Wijnen 
* URL : https://github.com/wijnen/python-fhs
* License : AGPL3+
  Programming Lang: Python
  Description : Python module for using the FHS and XDG basedir paths.

The FHS and XDG basedir specification defines locations for several files.
This module provides functions for accessing those files without requiring the
program to search the filesystem itself.
It provides a convenient way to use configuration from files, with commandline
override functionality.

I use this for most of my Python programs. It is also depended on by
python-network and python-websocketd, which I will file an ITP for after this.

Bug#1010011: Periodically vacuum database to prevent it growing endlessly

[Thijs Kinkhorst]

Package: fail2ban
Version: 0.11.2-6
Severity: normal
Tags: patch

Hi,

fail2ban (since 0.11) automatically cleans up stale entries in its
database, by default daily. However, the sqlite database is not
vacuum'ed so the file size on disk is not reduced after this. On one of
my systems, the database file was > 1 GB in size while after vacuum only
a 1 M remained, so it really was growing way to large.

The attached patch installs a weekly cronjob to perform the vacuum.
I've also submitted it as a merge request on salsa.


Kind regards,
Thijs Kinkhorst
diff -Nru fail2ban-0.11.2/debian/control fail2ban-0.11.2/debian/control
--- fail2ban-0.11.2/debian/control  2022-03-10 21:52:59.0 +
+++ fail2ban-0.11.2/debian/control  2022-04-22 09:14:01.0 +
@@ -21,8 +21,8 @@
 Package: fail2ban
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}, lsb-base
-Recommends: nftables | iptables, whois, python3-pyinotify, python3-systemd
-Suggests: mailx, system-log-daemon, monit, sqlite3
+Recommends: nftables | iptables, whois, sqlite3, python3-pyinotify, 
python3-systemd
+Suggests: mailx, system-log-daemon, monit
 Description: ban hosts that cause multiple authentication errors
  Fail2ban monitors log files (e.g. /var/log/auth.log,
  /var/log/apache/access.log) and temporarily or persistently bans
diff -Nru fail2ban-0.11.2/debian/cron.weekly fail2ban-0.11.2/debian/cron.weekly
--- fail2ban-0.11.2/debian/cron.weekly  1970-01-01 00:00:00.0 +
+++ fail2ban-0.11.2/debian/cron.weekly  2022-04-22 09:13:51.0 +
@@ -0,0 +1,8 @@
+#!/bin/sh
+
+sqlite="/usr/bin/sqlite3"
+database="/var/lib/fail2ban/fail2ban.sqlite3"
+
+[ -x $sqlite ] && [ -f $database ] || exit 0
+
+$sqlite $database "VACUUM;"

Bug#1004924: xkb: Alt key ceased working after last update

[Julien Cristau]

Control: tag -1 moreinfo

On Thu, Feb 03, 2022 at 11:26:16AM -0600, Carlos wrote:
> 
>* What led up to the situation?
>   updating packages with apt
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   press key combinations that involve Alt keys. For example: Alt + . used 
> to produce a middle dot, and I have a shortcut defined with Super+Alt+T, 
> which opens thunderbird. The most simple possible test I could imagine was 
> opening xev, and pressing different keys. The only one I could find not 
> working are Alt keys (no events are produced).
>* What was the outcome of this action?
>   No keypress events are produced with the alt keys
>* What outcome did you expect instead?
>   Keypress events should be produced when pressing Alt keys.
> 
Hi,

Please share more information about your system, desktop environment, setup,
config, relevant logs.  Also, after which specific update did the problem
start, and can you pin down which exact package caused it (e.g. by downgrading
individual packages that were part of that update)?

Cheers,
Julien

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Jeff]

forwarded 1009448 
https://github.com/PhilterPaper/Perl-PDF-Builder/issues/184

thanks


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009963: deb-systemd-helper: Misleading error message in "sub enable" if systemctl fails

[sh-bugs]

On Thu, 21 Apr 2022 19:08:26 +0200 Michael Biebl  wrote:


> ...
> 
> Currently it always give "$!" as the reason, even when not correct.

> This would also be incorrect if the real systemctl is used if the
> command fails because of syntax errors or so.

Thanks for the additional information, Ansgar.

I guess we have two issues then:
- systemctl (from docker-systemctl-replacement) most likely not being 
compatible with the real systemctl

- handling of the return code from system()


Yes, i think this is correct. I will fill an additional bug report for 
the systemctl package, which is the root cause of the problem. The bug 
reported here just gave some additional headaches while searching the 
real problem.


Thanks,
Sascha

Bug#1010012: ITP: python-network -- Python module for easy networking

[Bas Wijnen]

Package: wnpp
Severity: wishlist
Owner: Bas Wijnen 
X-Debbugs-Cc: debian-de...@lists.debian.org, wij...@debian.org

* Package name: python-network
  Version : 0.2
  Upstream Author : Bas Wijnen 
* URL : https://github.com/wijnen/python-network
* License : AGPL3+
  Programming Lang: Python
  Description : Python module for easy networking

Implementing networking in C is a pain. Unfortunately, much of that pain is
copied to Python. This module instead tries to follow the "batteries included"
approach, like the rest of Python. With this module, networking is a piece of
cake. It can use tcp sockets and unix domain sockets and supports avahi and ssl
connections without hassle.
.
This module provides a Socket class and a Server class.  The Server creates
Sockets when accepting connections; Sockets can be created by the user to
initiate a connection.  All of this is symmetrical: once the connection is
established, the client and server use the same interface.
.
For providing RPC functionality in a language independent way, see
python3-websocketd.

I use this module for many of my programs, usually in combination with
python-websocketd, for which I'll file an ITP after this. It requires
python-fhs, for which I just filed #1010010.

Bug#1010013: ITP: python-websocketd -- Python module for creating a http server which uses WebSockets

[Bas Wijnen]

Package: wnpp
Severity: wishlist
Owner: Bas Wijnen 
X-Debbugs-Cc: debian-de...@lists.debian.org, wij...@debian.org

* Package name: python-websocketd
  Version : 0.2
  Upstream Author : Bas Wijnen 
* URL : https://github.com/wijnen/python-websocketd
* License : AGPL3+
  Programming Lang: Python
  Description : Python module for creating a http server or client which 
uses WebSockets

This module uses the network module to create a server, and implements http(s)
and WebSockets over those connections.  With only 6 lines of code you have a
working system.  You only have to add what you want your server to do.
.
It also provides a client socket, which can be used to communicate with such a
server.

I use this module for many of my networked programs. It requires python-network
(#1010012) and python-fhs (#1010010).

Bug#1009996: IBus broken on GNOME on x11

[Osamu Aoki]

Hi Gunnar,

I don't use GNOME on x11 so you should know better than me.  Please read the
following first and please give me your thought.

This part of logic in 21_ibus.rc all started around:
38989f8 ("Show IBus icon on Budgie desktop", 2020-08-04) -- you
8b13771 ("Refactor with new find_match and document", 2020-08-07) -- me

Logic around here is a part which can be easily tangled as I recall. I now know 
GTK
apps need `GTK_IM_MODULE=ibus` under GNOME on x11.  That was different from 
what you
told me when we discussed to create this part of code.

> I submitted this im-config merge request:
> 
> https://salsa.debian.org/input-method-team/im-config/-/merge_requests/15
> 
> It works around the issue. Maybe we should use that on both Debian and 
> Ubuntu for now. In any case, unless some more proper solution comes up 
> very soon, I'm inclined to use it for a stable release update on Ubuntu.

I certainly agree that this patch seems to address stated issues for user of 
GNOME on
x11.  But is this the best fix?

Let me first ask ask 2 key questions.  Please help me:

Q1: Does desktop starts `ibus-daemon --daemonize --xim` for GNOME on x11 ?
Q2: Do we need to set `QT_IM_MODULE=ibus` under GNOME on x11?

Let me call your attention to the later part of 21_ibus.rc which sets following 
for
non-GNOME in PHASE 1

  GTK_IM_MODULE=ibus
  QT_IM_MODULE=ibus
  CLUTTER_IM_MODULE=ibus

So adding only GTK_IM_MODULE in place you proposed and still not running 
ibus-daemon
and not setting other environment variables looked tangled way to address the 
issue.

If we are to exclude "hands off list" for GNOME on x11, why not just do so and 
leave
the rest of code shared.  I mean if the answer to Q1 and Q2 are yes and yes, I 
think
it is cleaner to do the following patch:

```
$ git diff
diff --git a/data/21_ibus.rc b/data/21_ibus.rc
index 85cd3a2..45751b8 100644
--- a/data/21_ibus.rc
+++ b/data/21_ibus.rc
@@ -1,9 +1,10 @@
 # start IBus
 # vim: set sts=4 expandtab:
 
-# hands off to set up IM if listed in $DESKTOP_SETUP_IBUS
-if find_match "$IM_CONFIG_CURRENT_DESKTOP" "$DESKTOP_SETUP_IBUS" ; then
-# ibus set up is owned by desktop --> do the same as "none"
+# hands off to set up IM if listed in $DESKTOP_SETUP_IBUS and wayland
+if find_match "$IM_CONFIG_CURRENT_DESKTOP" "$DESKTOP_SETUP_IBUS" && \
+ ["$XDG_SESSION_TYPE" = 'wayland'] ; then
+# ibus set up is owned by desktop on wayland --> do the same as "none"
 return
 fi
 
```

Extra discussion: Was the Budgie:GNOME issue related to this?  (Were 
Budgie:GNOME
running under x11?)

FYI: I read Ubuntu bug: https://launchpad.net/bugs/1969637 but not so 
carefully.  So
I may be missing something.

Regards,

Osamu

Bug#1009664: gddrescue: Please upgrade gddrescue to 1.26

[Michael Prokop]

Control: tag -1 pending

Hi Anthony,

* Anthony Fok [Wed Apr 13, 2022 at 04:31:20PM -0600]:

> Thank you so much for maintaining gddrescue which has helped me rescue
> failing disks quite a few times.
> 
> GNU ddrescue 1.26 has been released, and it would be really nice if you
> could upgrade the Debian packaging from 1.23 to 1.26 at your
> convenience.  Here are the links to the release announcements:
[...]

Thanks for the ping! :)

I just uploaded gddrescue v1.26-1 towards unstable,
so it should show up soonish. :)

regards
-mika-


signature.asc
Description: PGP signature

Bug#1010014: ITP: mathcomp-algebra-tactics -- Ring and field tactics for Mathematical Components

[Julien Puydt]

Package: wnpp
Severity: wishlist
Owner: Julien Puydt 
X-Debbugs-Cc: Debian OCaml Maintainers , 
jpu...@debian.org

* Package name: mathcomp-algebra-tactics
  Version : 0.3.0
  Upstream Author : Kazuhiko Sakaguchi
* URL : https://github.com/math-comp/algebra-tactics
* License : CeCILL-B
  Programming Lang: Coq
  Description : Ring and field tactics for Mathematical Components
 This package provides the 'ring' and 'field' tactics for
 the Mathematical Components library, that work for any instance
 of 'comRingType' and 'fieldType' through canonical structure inference.
 .
 The Mathematical Components library is a coherent repository of
 general-purpose formalized mathematical theories for the

I plan to maintain it within the Debian OCaml Maintainers team, along with the
other Coq/MathComp packages.

Cheers,

J.Puydt

Bug#1009996: IBus broken on GNOME on x11

[Gunnar Hjalmarsson]

Thanks for your reply, Osamu!

On 2022-04-22 11:49, Osamu Aoki wrote:

This part of logic in 21_ibus.rc all started around:
38989f8 ("Show IBus icon on Budgie desktop", 2020-08-04) -- you
8b13771 ("Refactor with new find_match and document", 2020-08-07) -- me


Yep, I remember.


Logic around here is a part which can be easily tangled as I recall.
I now know GTK apps need `GTK_IM_MODULE=ibus` under GNOME on x11.
That was different from what you told me when we discussed to create
this part of code.


GTK_IM_MODULE=ibus was not needed at the time, but the mechanism which 
made it work was broken in GNOME 42. So it's a regression.



I submitted this im-config merge request:

https://salsa.debian.org/input-method-team/im-config/-/merge_requests/15

It works around the issue. Maybe we should use that on both Debian and
Ubuntu for now. In any case, unless some more proper solution comes
up very soon, I'm inclined to use it for a stable release update on
Ubuntu.


I certainly agree that this patch seems to address stated issues for
user of GNOME on x11.  But is this the best fix?


It's a workaround, hopefully only temporary until we can do it properly 
in the right package (maybe gnome-settings-daemon).


It's the urgency which motivates the workaround. Especially as regards 
Ubuntu 22.04, which was released yesterday with the issue, but I suppose 
we don't want a broken IBus on testing's GNOME on Xorg either.



Let me first ask ask 2 key questions.  Please help me:

Q1: Does desktop starts `ibus-daemon --daemonize --xim` for GNOME on
x11 ?


No. GNOME currently starts it like this:

/usr/bin/ibus-daemon --panel disable --xim


Q2: Do we need to set `QT_IM_MODULE=ibus` under GNOME on x11?


No. That's already set by GNOME.


Let me call your attention to the later part of 21_ibus.rc which sets
following for non-GNOME in PHASE 1

   GTK_IM_MODULE=ibus
   QT_IM_MODULE=ibus
   CLUTTER_IM_MODULE=ibus

So adding only GTK_IM_MODULE in place you proposed and still not
running ibus-daemon and not setting other environment variables
looked tangled way to address the issue.


Our original idea was to defer everything to GNOME. And GNOME still 
starts ibus-daemon and sets XMODIFIERS and QT_IM_MODULE. So the only 
thing we need to add through im-config is GTK_IM_MODULE.



If we are to exclude "hands off list" for GNOME on x11, why not just
do so and leave the rest of code shared.  I mean if the answer to Q1
and Q2 are yes and yes, I think it is cleaner to do the following
patch:


But the answer to Q1 and Q2 are no and no. ;) And especially because of 
the different way to start ibus-daemon (--panel disable) I think we 
shouldn't go back to let im-config do things which are already done by 
GNOME.


So for those reasons I think my merge request is better (even if it's a 
workaround).



Extra discussion: Was the Budgie:GNOME issue related to this?  (Were
Budgie:GNOME running under x11?)


Budgie is run under x11, and Budgie starts ibus-daemon and sets the same 
variables as GNOME does. I don't know to which extent this new issue 
affects Budgie. But OTOH, "GTK_IM_MODULE=ibus" won't hurt on x11.



FYI: I read Ubuntu bug: https://launchpad.net/bugs/1969637 but not so
carefully.  So I may be missing something.


Ack. The issue is different in Ubuntu, but the proposed workaround 
applies to Ubuntu too. The Ubuntu bug includes a couple of links to 
interesting upstream gnome-settings-daemon commits.


--
Cheers,
Gunnar

Bug#1010017: katex: TypeError: Cannot read property 'search' of undefined

[Jakub Wilk]

Package: katex
Version: 0.13.11+~cs6.0.0-3

The CLI doesn't work at all:

  $ katex < /dev/null
  /usr/share/nodejs/katex/cli.js:95
  const i = m.search(":");
  ^

  TypeError: Cannot read property 'search' of undefined
  at splitMacros (/usr/share/nodejs/katex/cli.js:95:21)
  at readMacros (/usr/share/nodejs/katex/cli.js:83:9)
  at Object. (/usr/share/nodejs/katex/cli.js:139:1)
  at Module._compile (internal/modules/cjs/loader.js:1085:14)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
  at Module.load (internal/modules/cjs/loader.js:950:32)
  at Function.Module._load (internal/modules/cjs/loader.js:790:12)
  at Function.executeUserEntryPoint [as runMain] 
(internal/modules/run_main.js:75:12)
  at internal/main/run_main_module.js:17:47


-- System Information:
Architecture: i386

Versions of packages katex depends on:
ii  libjs-katex 0.13.11+~cs6.0.0-3
ii  node-commander  9.1.0-1
ii  nodejs  16.13.2+really14.19.1~dfsg-6

--
Jakub Wilk

Bug#1010018: katex man page: bad synopsis

[Jakub Wilk]

Package: katex
Version: 0.13.11+~cs6.0.0-3
Severity: minor

I saw this in the man page:

  $ man katex | grep -w SYNOPSIS -A1
  SYNOPSIS
 cli [options]

It should say "katex", not "cli".


-- System Information:
Architecture: i386

Versions of packages katex depends on:
ii  libjs-katex 0.13.11+~cs6.0.0-3
ii  node-commander  9.1.0-1
ii  nodejs  16.13.2+really14.19.1~dfsg-6

--
Jakub Wilk

Bug#1009965: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder not working anymore

[Holger Schröder]

Hi

I found the following in the journal, a tuner timeout. As I said, with
kernel linux-image-5.16.0-6-amd64 everything works. With
linux-image-5.17.0-1-amd64 it doesn't work anymore, not a single program.



[...]
Apr 22 14:07:01 vdrbox vdr[2034]: [2419] frontend 0/0 timed out while
tuning to channel 2 (Das Erste HD), tp 266
Apr 22 14:07:03 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
1151608 bytes/s (8996 kbit/s)
Apr 22 14:07:11 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
9588272 bytes/s (74908 kbit/s)
Apr 22 14:07:12 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
5246688 bytes/s (40989 kbit/s)
Apr 22 14:07:13 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
10374720 bytes/s (81052 kbit/s)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] switching to channel 16
C-61442-7-10355 (hr-Fernsehen HD)
Apr 22 14:07:15 vdrbox vdr[2034]: [3858] osdteletext-receiver thread
ended (pid=2034, tid=3858)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] osdteletext: cTxtReceiver
stopped after 23 sec: cTelePage received on DVB 0 for channel 2 'Das
Erste HD' ID=C-41985-1051-11100: 0 (0,000/sec)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] buffer stats: 0 (0%) used
Apr 22 14:07:15 vdrbox vdr[2034]: [3859] device 1 TS buffer thread ended
(pid=2034, tid=3859)
Apr 22 14:07:15 vdrbox vdr[2034]: [3857] buffer stats: 0 (0%) used
Apr 22 14:07:15 vdrbox vdr[2034]: [3857] device 1 receiver thread ended
(pid=2034, tid=3857)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] osdteletext: cTxtReceiver
started on DVB 0 for channel 16 'hr-Fernsehen HD' ID=C-61442-7-10355
storeTopText=true LiveView=true
Apr 22 14:07:15 vdrbox vdr[2034]: [3939] device 1 receiver thread
started (pid=2034, tid=3939, prio=high)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] creating directory
/var/cache/vdr/vtx/C-61442-7-10355
Apr 22 14:07:15 vdrbox vdr[2034]: [3940] device 1 TS buffer thread
started (pid=2034, tid=3940, prio=high)
Apr 22 14:07:15 vdrbox vdr[2034]: [3941] osdteletext-receiver thread
started (pid=2034, tid=3941, prio=low)
Apr 22 14:07:15 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
2623344 bytes/s (20494 kbit/s)
Apr 22 14:07:18 vdrbox vdr[2034]: [2034] [xine..put] OSD bandwidth:
767792 bytes/s (5998 kbit/s)
Apr 22 14:07:24 vdrbox vdr[2034]: [2419] frontend 0/0 timed out while
tuning to channel 16 (hr-Fernsehen HD), tp 354
[...]


...

Bug#1010020: systemctl-replacement doesn't work with deb-systemd-helper

[Sascha Herrmann]

Package: systemctl
Version: 1.4.4181-1.1
Severity: important

Dear Maintainer,

systemctl-replacement fails to support the preset parameter, which is used by
the deb-systemd-helper script when installing packages with systemd service
files. If the systemctl package is installed before a package, which wants to
install a systemd service file, enabling this service fails. If the systemctl
package is not installed, deb-systemd-helper itself takes care of enabling the
service file, if no systemd is installed on the system.

With installed systemctl package:


# DEBIAN_FRONTEND=noninteractive apt-get install -y ntp

...

Setting up ntp (1:4.2.8p15+dfsg-1) ...
/usr/bin/deb-systemd-helper: error: systemctl preset failed on ntp.service: No 
such file or directory
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up libgdbm-compat4:amd64 (1.19-2) ...
Setting up libperl5.32:amd64 (5.32.1-4+deb11u2) ...
Setting up perl (5.32.1-4+deb11u2) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...

# ls -l /etc/systemd/system/
default.target.wants/ timers.target.wants/

# ls -l /etc/systemd/system/*.wants

/etc/systemd/system/default.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Jan  1  1970 e2scrub_reap.service -> 
/lib/systemd/system/e2scrub_reap.service

/etc/systemd/system/timers.target.wants:
total 0
lrwxrwxrwx 1 root root 43 Jan  1  1970 apt-daily-upgrade.timer -> 
/lib/systemd/system/apt-daily-upgrade.timer
lrwxrwxrwx 1 root root 35 Jan  1  1970 apt-daily.timer -> 
/lib/systemd/system/apt-daily.timer
lrwxrwxrwx 1 root root 37 Jan  1  1970 e2scrub_all.timer -> 
/lib/systemd/system/e2scrub_all.timer
lrwxrwxrwx 1 root root 32 Jan  1  1970 fstrim.timer -> 
/lib/systemd/system/fstrim.timer

# ls -l /lib/systemd/system/ntp.service
-rw-r--r-- 1 root root 354 Sep 23  2020 /lib/systemd/system/ntp.service


Notice, that the error message "No such file or directory" is misleading and
wrong, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009963.

Calling systemctl manually with the parameter set by deb-systemd-helper fails
too, 1 is returned as result and no links to the service files are setup.


# systemctl --system --preset-mode=enable-only preset ntp.service
# echo $?
1


Thanks,
Sascha

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

Kernel: Linux 5.4.0-107-generic (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages systemctl depends on:
ii  python3  3.9.2-3

Versions of packages systemctl recommends:
ii  procps  2:3.3.17-5

Versions of packages systemctl suggests:
pn  tini | dumb-init  

-- no debconf information

Bug#1010022: RFS: microdc2/0.15.6-4.1 [NMU] -- command-line based Direct Connect client

[Hugh McMaster]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the package "microdc2":

 * Package name: microdc2
   Version : 0.15.6-4.1
   Upstream Author : Vladimir Chugunov
 * URL : http://corsair626.no-ip.org/microdc/
 * License : GPL-2+
 * Vcs : N/A]
   Section : net

The source builds the following binary packages:

  microdc2 - command-line based Direct Connect client

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

  https://mentors.debian.net/package/microdc2/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/m/microdc2/microdc2_0.15.6-4.1.dsc

Changes since the last upload:

 microdc2 (0.15.6-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Build-Depend on pkg-config.
   * debian/patches:
 - Drop "disable-libxml2-version-check" in favour of pkg-config.
 - Refresh some patches due to removal of "disable-libxml2-version-check".
 - Use pkg-config to find libxml2 (Closes: #949413).

Regards,
-- 
  Hugh McMaster

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

[Mattia Rizzolo]

Control: notfound -1 2.114.163
Control: found -1 2.111.0
Control: close -1 2.113.0

On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote:
> Package: lintian
> Version: 2.114.163

What version is this?! ...

> The Lintian on mentors.debian.net incorrectly reports:
> 
> W: improbable-bug-number-in-closes 1008784
> 
> The relevant changelog entry:
> 
> Replaces part of the cron job that we used to provide (Closes: #1008784).
> 
> That bug report very much exists.


This bug has long long been fixed, but lintian is not migrating and as
such no backport to bullseye can be done.
(plus I notice lintian hasn't been uploaded _at all_ for many months…)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1010023: microdc2: NMU 0.15.6-4.1

[Bastian Germann]

Source: microdc2
Version: 0.15.6-4.1

The debdiff for the just uploaded NMU is attached.diff -Nru microdc2-0.15.6/debian/changelog microdc2-0.15.6/debian/changelog
--- microdc2-0.15.6/debian/changelog2016-07-08 00:31:05.0 +0200
+++ microdc2-0.15.6/debian/changelog2022-04-22 14:29:15.0 +0200
@@ -1,3 +1,14 @@
+microdc2 (0.15.6-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Build-Depend on pkg-config.
+  * debian/patches:
+- Drop "disable-libxml2-version-check" in favour of pkg-config.
+- Refresh some patches due to removal of "disable-libxml2-version-check".
+- Use pkg-config to find libxml2 (Closes: #949413).
+
+ -- Hugh McMaster   Fri, 22 Apr 2022 22:29:15 +1000
+
 microdc2 (0.15.6-4) unstable; urgency=medium
 
   * Hardening insecure fprintf() logging in screen.c -- repeat 
diff -Nru microdc2-0.15.6/debian/control microdc2-0.15.6/debian/control
--- microdc2-0.15.6/debian/control  2016-07-08 00:17:31.0 +0200
+++ microdc2-0.15.6/debian/control  2022-04-22 13:51:03.0 +0200
@@ -2,7 +2,13 @@
 Section: net
 Priority: extra
 Maintainer: Al Nikolov 
-Build-Depends: debhelper (>= 9), dh-autoreconf, libreadline-dev, libxml2-dev 
(>= 2.6.16), libbz2-dev
+Build-Depends:
+ debhelper (>= 9),
+ dh-autoreconf,
+ libreadline-dev,
+ libxml2-dev (>= 2.6.16),
+ libbz2-dev,
+ pkg-config
 Standards-Version: 3.9.8
 Homepage: http://corsair626.no-ip.org/microdc/
 
diff -Nru microdc2-0.15.6/debian/patches/debian-link-system-bz2 
microdc2-0.15.6/debian/patches/debian-link-system-bz2
--- microdc2-0.15.6/debian/patches/debian-link-system-bz2   2010-01-21 
00:57:38.0 +0100
+++ microdc2-0.15.6/debian/patches/debian-link-system-bz2   2022-04-22 
13:56:16.0 +0200
@@ -2,14 +2,12 @@
 Author: Al Nikolov 
 Forwarded: non-needed
 Last-Update: 2010-01-21
-Index: microdc2-0.15.6/configure.ac
-===
 microdc2-0.15.6.orig/configure.ac  2010-01-20 23:55:08.0 +
-+++ microdc2-0.15.6/configure.ac   2010-01-20 23:57:34.0 +
+--- a/configure.ac
 b/configure.ac
 @@ -64,6 +64,7 @@
- #AC_MSG_WARN([XML libxml2 library version 2.6.16 or later is required to 
support XML filelists])
- #  fi
- #fi
+ AC_MSG_WARN([XML libxml2 library version 2.6.16 or later is required to 
support XML filelists])
+   fi
+ fi
 +AC_CHECK_LIB(bz2, BZ2_bzRead,, AC_MSG_ERROR([Missing bz2 library]))
  
  # Checks for header files
@@ -22,10 +20,8 @@
 src/tth/Makefile
 rpm/microdc.spec])
  AC_CONFIG_FILES([slackware/microdc.SlackBuild],
-Index: microdc2-0.15.6/src/Makefile.am
-===
 microdc2-0.15.6.orig/src/Makefile.am   2010-01-20 23:55:08.0 
+
-+++ microdc2-0.15.6/src/Makefile.am2010-01-20 23:57:20.0 +
+--- a/src/Makefile.am
 b/src/Makefile.am
 @@ -1,4 +1,4 @@
 -SUBDIRS = common bzip2 tth
 +SUBDIRS = common tth
diff -Nru microdc2-0.15.6/debian/patches/disable-libxml2-version-check 
microdc2-0.15.6/debian/patches/disable-libxml2-version-check
--- microdc2-0.15.6/debian/patches/disable-libxml2-version-check
2010-01-17 22:46:14.0 +0100
+++ microdc2-0.15.6/debian/patches/disable-libxml2-version-check
1970-01-01 01:00:00.0 +0100
@@ -1,46 +0,0 @@
-Description: Disable the libxml2 version check
- The check is broken (dotted version to integer conversion is wrong).
- .
- Since the Debian package has versionned dependency on a fresh version
- of libxml2-dev, the version check isn't needed. And probably libxml2
- older than version 2.6.16 aren't in the wild anymore.
-Author: Al Nikolov 
-Last-Update: 2010-01-17
-Index: microdc2-0.15.6/configure.ac
-===
 microdc2-0.15.6.orig/configure.ac  2010-01-17 04:45:33.0 +
-+++ microdc2-0.15.6/configure.ac   2010-01-17 04:44:54.0 +
-@@ -47,12 +47,12 @@
- #AH_TEMPLATE([XML_SAVE_FORMAT], [1], [Define if libxml2 has no such option 
for xmlSave- functions])
- AC_PATH_PROG(XML_CONFIG, xml2-config)
- AC_PATH_PROG(TR, tr)
--if test -n "$XML_CONFIG" && test -n "$TR"; then
--  LIBXML2_VERSION=`$XML_CONFIG --version | $TR -d "."`
--  if test $LIBXML2_VERSION -eq 2616; then
--AC_DEFINE([XML_SAVE_FORMAT], [1], [The libxml2 version 2.6.16 has no such 
option defined in the library headers])
--  fi
--  if test $LIBXML2_VERSION -ge 2616; then
-+#if test -n "$XML_CONFIG" && test -n "$TR"; then
-+#  LIBXML2_VERSION=`$XML_CONFIG --version | $TR -d "."`
-+#  if test $LIBXML2_VERSION -eq 2616; then
-+#AC_DEFINE([XML_SAVE_FORMAT], [1], [The libxml2 version 2.6.16 has no 
such option defined in the library headers])
-+#  fi
-+#  if test $LIBXML2_VERSION -ge 2616; then
- AC_DEFINE([HAVE_LIBXML2])
- LIBXML2_LIBS="`$XML_CONFIG --libs`"
- LIBXML2_CFLAGS="`$XML_CONFIG --cflags`"
-@@ 

Bug#1009877: hexchat-python3 ver. 1.14.3-4 present in bullseye (stable) lacks of dependency python3-cffi

[Mattia Rizzolo]

Control: fixed -1 2.16.0-1

On Tue, Apr 19, 2022 at 09:08:39PM +0200, Robin-antiX wrote:
> when installing hexchat-python3 in bullseye (version 1.14.3-4) hexchat will 
> fail to load this plugin.
> console error output:
> 
> 
> Installing the additional package python3-cffi fixes the problem, after this 
> python interface is loaded perfectly on hexchat startup.
> 
> So there is obviously the dependency missing in this package version.


Thank you for your report.
Indeed somebody reported this issue on IRC a few days ago too :)

> hexchat-python3 packages version above 1.16.0 have this dependency corectly 
> set.

I added a dependency on python3-cffi-backend in 2.16.0-1 indeed.  From
what I remember from when I added the dependency, the -backend package
was enough, there was no need for the whole python3-cffi package.

Guess I'll double check if that's enough also in bullseye, and do a
stable update.

> Automatically added system information inappropriate for this bug report, 
> since I'm reporting from another machine, not a debian bullsey.

That's fine :)
However you could have just dropped this info, in that case :P

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1010024: git-buildpackage: fails to import pristine-tar: File name too long

[Drew Parsons]

Package: git-buildpackage
Version: 0.9.25
Severity: normal
Control: affects -1 src:rclone
Control: block 1001261 by -1

I'm trying to update the rclone package, using gbp import-orig in the
"usual" way, with uscan, pristine-tar and importing into the
experimental branch.

The import is failing, apparently due to using a git commit in a
filename during the pristine-tar step.

$ git clone g...@salsa.debian.org:go-team/packages/rclone.git
$ cd rclone
$ git checkout upstream; git checkout pristine-tar; git checkout experimental
$ git branch
* experimental
  master
  pristine-tar
  upstream
$ uscan --report
uscan: Newest version of rclone on remote site is 1.58.0, local version is 
1.53.3
uscan:  => Newer package available from:
=> https://github.com/rclone/rclone/archive/refs/tags/v1.58.0.tar.gz

$ gbp import-orig --verbose --uscan --pristine-tar  --debian-branch=experimental
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'for-each-ref', '--format=%(refname:short)', 'refs/heads/']
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream']
gbp:debug: ['git', 'status', '--porcelain']
gbp:info: Launching uscan...
gbp:info: Using uscan downloaded tarball ../rclone_1.58.0.orig.tar.gz
What is the upstream version? [1.58.0] 
gbp:debug: ['git', 'tag', '-l', 'upstream/1.58.0']
gbp:debug: tar ['-C', '../tmpkiz0ywn3', '-a', '-xf', 
'../rclone_1.58.0.orig.tar.gz'] []
gbp:debug: Unpacked '../rclone_1.58.0.orig.tar.gz' to 
'../tmpkiz0ywn3/rclone-1.58.0'
gbp:info: 
gbp:info: Importing '../rclone_1.58.0.orig.tar.gz' to branch 'upstream'...
gbp:info: Source package is rclone
gbp:info: Upstream version is 1.58.0
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'upstream']
gbp:debug: ['git', 'add', '-f', '.']
gbp:debug: ['git', 'write-tree']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'upstream']
gbp:debug: ['git', 'commit-tree', '260bd813325c0b30022ab31e09fc3d9ab570e072', 
'-p', '4d715ab7de2dd24d802fe89bd79048ba674a25ea']
gbp:debug: ['git', 'update-ref', '-m', 'gbp: New upstream version 1.58.0', 
'refs/heads/upstream', '70bb7aad80b8c50a88d59be119fbdc5c0f72ad3c', 
'4d715ab7de2dd24d802fe89bd79048ba674a25ea']
gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/pristine-tar']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'pristine-tar']
gbp:debug: ['git', 'ls-tree', '-z', 'upstream', '--']
gbp:debug: ['git', 'mktree', '-z']
gbp:debug: pristine-tar [] ['commit', '../rclone_1.58.0.orig.tar.gz', 
'260bd813325c0b30022ab31e09fc3d9ab570e072']
gbp:error: Import of ../rclone_1.58.0.orig.tar.gz failed: Couldn't commit to 
'pristine-tar' with upstream '260bd813325c0b30022ab31e09fc3d9ab570e072': mkdir 
/tmp/pristine-tar.iXqSpNTndf/workdir/rclone-1.58.0/cmd/bisync/testdata/test_extended_char_paths/golden/normal-sync._testdir_path1_\346\270\254\350\251\246_\320\240\321\203\321\201\321\201\320\272\320\270\320\271_\304\233_\303\241\303\261.._testdir_path2_\346\270\254\350\251\246_\320\240\321\203\321\201\321\201\320\272\320\270\320\271_\304\233_\303\241\303\261.copy1to2.que:
 File name too long at /usr/bin/pristine-tar line 451.
gbp:error: Error detected, Will roll back changes.
gbp:info: Rolling back branch upstream by resetting it to 
4d715ab7de2dd24d802fe89bd79048ba674a25ea
gbp:debug: ['git', 'update-ref', '-m', 'gbp import-orig: failure rollback of 
upstream', 'refs/heads/upstream', '4d715ab7de2dd24d802fe89bd79048ba674a25ea']
gbp:info: Rolling back branch pristine-tar by resetting it to 
f92427a73c1a897f36b08dbf40a402c144d75b73
gbp:debug: ['git', 'update-ref', '-m', 'gbp import-orig: failure rollback of 
pristine-tar', 'refs/heads/pristine-tar', 
'f92427a73c1a897f36b08dbf40a402c144d75b73']
gbp:error: Rolled back changes after import error.
gbp:debug: rm ['-rf', '../tmpkiz0ywn3'] []






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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.22.1
ii  git1:2.35.2-1
ii  man-db 2.10.2-1
ii  python33.10.4-1
ii  python3-dateutil   2.8.1-6
ii  python3-pkg-resources  59.6.0-1.2
ii  sensible-utils 0.0.17

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.89
ii  pbuilder  0.231
ii  pristine-tar  1.49
ii  python3-requests  2.27.1+dfsg-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.10-3
ii  unzip6.0-26

-- no debconf

Bug#1009998: Thunar and Nautilus don't show login and password box before conect

[Dramon Conte]

Dear Maintainer,

I tested on Thunar and Nautilus and the file systems do not show login and
password box before connect. The system is passing wrong credentials to
Windows file server.

Bug#1010025: ghc: Haddock fails with internal error when calculating transitive dependencies

[Scott Talbert]

Package: ghc
Version: 8.8.4-3
Severity: normal

Dear Maintainer,

While attempting to package doctest-parallel for Debian, the following 
error was encountered during build:

Preprocessing library 'spectests-modules' for doctest-parallel-0.2..
Running Haddock on library 'spectests-modules' for doctest-parallel-0.2..
Warning: The documentation for the following packages are not installed. No
links will be generated to these packages: dlist-0.8.0.8, hashable-1.3.0.0,
transformers-compat-0.6.5
Warning: --source-* options are ignored when --hyperlinked-source is enabled.
CallStack (from HasCallStack):
  withTempDirectoryEx, called at 
libraries/Cabal/Cabal/Distribution/Simple/Haddock.hs:273:11 in 
Cabal-3.0.1.0:Distribution.Simple.Haddock
  haddock, called at libraries/Cabal/Cabal/Distribution/Simple.hs:636:35 in 
Cabal-3.0.1.0:Distribution.Simple
  haddockHook, called at 
libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:139:5 in 
Cabal-3.0.1.0:Distribution.Simple.UserHooks
  cmd_hook, called at libraries/Cabal/Cabal/Distribution/Simple.hs:497:9 in 
Cabal-3.0.1.0:Distribution.Simple
  cmd_hook, called at libraries/Cabal/Cabal/Distribution/Simple.hs:516:4 in 
Cabal-3.0.1.0:Distribution.Simple
  hookedActionWithArgs, called at 
libraries/Cabal/Cabal/Distribution/Simple.hs:495:5 in 
Cabal-3.0.1.0:Distribution.Simple
  hookedAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:360:3 in 
Cabal-3.0.1.0:Distribution.Simple
  haddockAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:187:50 
in Cabal-3.0.1.0:Distribution.Simple
  defaultMainHelper, called at 
libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in 
Cabal-3.0.1.0:Distribution.Simple
  defaultMain, called at Setup.lhs:3:10 in main:Main
hlibrary.setup: internal error when calculating transitive package
dependencies.
Debug info: []

 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 106.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 130

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 723
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:152: build-ghc-stamp] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2

This is likely related to the fact that doctest-parallel contains 
internal dependencies.

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

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

Versions of packages ghc depends on:
ii  dpkg  1.21.7
ii  gcc   4:11.2.0-2
ii  libbsd-dev0.11.6-1
ii  libc6 2.33-7
ii  libc6-dev 2.33-7
ii  libffi-dev3.4.2-4
ii  libffi8   3.4.2-4
ii  libgmp-dev2:6.2.1+dfsg-3
ii  libgmp10  2:6.2.1+dfsg-3
ii  libncurses-dev [libncurses5-dev]  6.3-2
ii  libncurses5-dev   6.3-2
ii  libtinfo6 6.3-2

ghc recommends no packages.

Versions of packages ghc suggests:
ii  ghc-doc  8.8.4-3
ii  ghc-prof 8.8.4-3
pn  haskell-doc  
pn  llvm-11  
ii  perl 5.34.0-4

-- no debconf information

Bug#737359:

[Lee james jason Stephen hayes]

Bug#949098: dvdauthor: FTBFS with libxml2 2.9.10 (uses xml2-config)

[Bastian Germann]

A release does not seem to be coming soon. Would you please backport the patch to a new revision or release a git-based 
version?

Bug#949521: kamailio: loses link (and a bunch of other files) against libxml2 not shipping xml2-config

[Bastian Germann]

Am 22.04.22 um 16:04 schrieb Bastian Germann:

Can this be closed? It is marked as fixed and the upstream fixes are in buster 
and following.


* bullseye

Bug#949521: kamailio: loses link (and a bunch of other files) against libxml2 not shipping xml2-config

[Bastian Germann]

Can this be closed? It is marked as fixed and the upstream fixes are in buster 
and following.

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Adrian Davey]

Package: qemu-system-x86
Version: 1:7.0+dfsg-1
Severity: normal

Dear Maintainer,

VMs controlled by libvirt failed to start when using "host" cpu type with kvm
acceleration

libvirt log gives:

2022-04-21T17:07:40.354354Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.npt [bit 0]
2022-04-21T17:07:40.354467Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.nrip-save [bit
3]
2022-04-21T17:07:40.354476Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.vmcb-clean [bit
5]
2022-04-21T17:07:40.354482Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.svme-addr-chk
[bit 28]
2022-04-21T17:07:40.355818Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.npt [bit 0]
2022-04-21T17:07:40.355850Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.nrip-save [bit
3]
2022-04-21T17:07:40.355857Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.vmcb-clean [bit
5]
2022-04-21T17:07:40.355864Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.svme-addr-chk
[bit 28]
2022-04-21T17:07:40.419616Z qemu-system-x86_64: error: failed to set MSR
0xc104 to 0x1
qemu-system-x86_64: ../../target/i386/kvm/kvm.c:2996: kvm_buf_set_msrs:
Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

Reverting to qemu-system-x86 6.2+dfsg-3 and the VMs start-up perfectly fine
using the same libvirt xml.

host cpu flags from /proc/cpuinfo :

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy
abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate
vmmcall npt lbrv svm_lock nrip_save

Cheers,

Adrian


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

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

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu 1.0.0+git-20190125.36a4c85-5.1
ii  libaio1   0.3.113-2
ii  libbpf0   1:0.7.0-2
ii  libc6 2.33-7
ii  libcapstone4  4.0.2-5
ii  libfdt1   1.6.1-1
ii  libfuse3-33.10.5-1
ii  libgcc-s1 12-20220319-1
ii  libglib2.0-0  2.72.1-1
ii  libgnutls30   3.7.4-2
ii  libibverbs1   39.0-1+b1
ii  libjpeg62-turbo   1:2.1.2-1
ii  libnettle83.7.3-1
ii  libnuma1  2.0.14-3
ii  libpixman-1-0 0.40.0-1
ii  libpmem1  1.11.1-3
ii  libpng16-16   1.6.37-3
ii  librdmacm139.0-1+b1
ii  libsasl2-22.1.28+dfsg-4
ii  libseccomp2   2.5.3-2
ii  libslirp0 4.6.1-1
ii  libudev1  250.4-1
ii  liburing2 2.1-2
ii  libvdeplug2   4.0.1-3
ii  libxendevicemodel14.16.0+51-g0941d6cb-1+b1
ii  libxenevtchn1 4.16.0+51-g0941d6cb-1+b1
ii  libxenforeignmemory1  4.16.0+51-g0941d6cb-1+b1
ii  libxengnttab1 4.16.0+51-g0941d6cb-1+b1
ii  libxenmisc4.164.16.0+51-g0941d6cb-1+b1
ii  libxenstore4  4.16.0+51-g0941d6cb-1+b1
ii  libxentoolcore1   4.16.0+51-g0941d6cb-1+b1
ii  libzstd1  1.5.2+dfsg-1
ii  qemu-system-common1:7.0+dfsg-1
ii  qemu-system-data  1:7.0+dfsg-1
ii  seabios   1.15.0-1
ii  zlib1g1:1.2.11.dfsg-4

Versions of packages qemu-system-x86 recommends:
ii  ovmf  2022.02-3
pn  qemu-block-extra  
pn  qemu-system-gui   
ii  qemu-utils1:7.0+dfsg-1

Versions of packages qemu-system-x86 suggests:
ii  samba  2:4.16.0+dfsg-6
pn  vde2   

-- no debconf information

Bug#1009969: openvswitch: patch for riscv64 ftbfs

[Bo YU]

Source: openvswitch
Version: 2.15.0+ds1-10
Followup-For: Bug #1009969
Control: tags -1 patch

Dear Maintainer,

The speical fail cases are below that i grap from the build log on riscv64 
hardware:

...
## - ##
## Test results. ##
## - ##

ERROR: 2267 tests were run,
3 failed unexpectedly.
22 tests were skipped.
## -- ##
## testsuite.log was created. ##
## -- ##

Please send `tests/testsuite.log' and all information you think might help:

   To: 
  Subject: [openvswitch 2.15.0] testsuite: 1036 1072 1139 failed

You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point.  Its output may
be found below `tests/testsuite.dir'.
...
make[5]: Entering directory '/<>/_debian'
set /bin/bash '../tests/testsuite' -C tests 
AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests::; \
"$@" --recheck || (test X'' = Xyes && "$@" --recheck)
not a dynamic executable
## -- ##
## openvswitch 2.15.0 test suite. ##
## -- ##

ofproto-dpif

1036: ofproto-dpif - select group with weightsFAILED 
(ofproto-dpif.at:787)
1072: ofproto-dpif - controller action without megaflows FAILED 
(ofproto-dpif.at:2145)
1139: ofproto-dpif - sFlow packet sampling - LACP structures ok

## - ##
## Test results. ##
## - ##

ERROR: All 3 tests were run,
2 failed unexpectedly.
## -- ##
## testsuite.log was created. ##
## -- ##

Please send `tests/testsuite.log' and all information you think might help:
...

And I noticed the commit:

https://salsa.debian.org/openstack-team/third-party/openvswitch/-/commit/c4c329b15cafee9ccc7ce724c0fc8aa5b7d33881

It seems there is a blacklist for riscv64, but it had been pushed
debian/yoga branch. And the patch for the reportbug is ok that I
can build openvswitch package successfully on my riscv64 hardware
(Unmatched board). It is different with the commit that I mentioned.

If you need me to test more case, please feel free to let me know.
Index: openvswitch-2.15.0+ds1/debian/rules
===
--- openvswitch-2.15.0+ds1.orig/debian/rules
+++ openvswitch-2.15.0+ds1/debian/rules
@@ -165,6 +165,15 @@ TEST_LIST = 1-19 22-531 533-1020 1022-10
 TEST_LIST_DPDK = $(TEST_LIST)
 endif #ia64
 
+# riscv64
+#  1036: ofproto-dpif - select group with weightsFAILED 
(ofproto-dpif.at:787)
+#  1072: ofproto-dpif - controller action without megaflows FAILED 
(ofproto-dpif.at:2145)
+#  1139: ofproto-dpif - sFlow packet sampling - LACP structures ok
+ifneq (,$(filter riscv64, $(DEB_HOST_ARCH)))
+TEST_LIST = 1-1035 1037-1071 1073-1138 1140-
+TEST_LIST_DPDK = $(TEST_LIST)
+endif #riscv64
+
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
if $(MAKE) -C _debian check TESTSUITEFLAGS='$(PARALLEL) $(TEST_LIST)' 
|| \

Bug#1009118: python3-biopython: incompatible with muscle >= 5

[Andrius Merkys]

Control: tags -1 + wontfix

Hello,

The upstream has confirmed that command line wrappers are deprecated and
will most likely be removed before bookworm freeze. Thus there is no
need to patch this. I suggest keeping this issue open until bookworm
release as a reminder to check this before the release.

Andrius

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Michael Tokarev]

Control: tag -1 + moreinfo

22.04.2022 17:10, Adrian Davey wrote:

Package: qemu-system-x86
Version: 1:7.0+dfsg-1
Severity: normal

Dear Maintainer,

VMs controlled by libvirt failed to start when using "host" cpu type with kvm
acceleration

libvirt log gives:

2022-04-21T17:07:40.354354Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.npt [bit 0]


..

2022-04-21T17:07:40.419616Z qemu-system-x86_64: error: failed to set MSR
0xc104 to 0x1
qemu-system-x86_64: ../../target/i386/kvm/kvm.c:2996: kvm_buf_set_msrs:
Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.


Please show the complete qemu command line (it should be available in the log 
too).

This assertion does not look like something cpu-feature-specific, it smells
like a bug by its own, not depending on -cpu host.

Thanks,

/mjt

Bug#1006920: please split out a libtbbmalloc2 package, both in tbb and onetbb

[Andrius Merkys]

Hello,

For me tbb 2020.3-1 fails to build in sid chroot with tbb.diff applied.
First of all, build runs into missing symbols. I managed to get past
this by removing them:

--- a/debian/libtbbmalloc2.symbols.amd64
+++ b/debian/libtbbmalloc2.symbols.amd64
@@ -2,8 +2,6 @@ libtbbmalloc.so.2 libtbbmalloc2 #MINVER#
  MallocInitializeITT@Base 2017~U7
  _Z9parseFileILi100ELi1EEvPKcRAT0__K13parseFileItem@Base 2018~U6
  _Z9parseFileILi100ELi2EEvPKcRAT0__K13parseFileItem@Base 2018~U6
- (optional)_ZN11MallocMutex11scoped_lockD1Ev@Base 2020.3
- (optional)_ZN11MallocMutex11scoped_lockD2Ev@Base 2020.3
  _ZN3rml10pool_msizeEPNS_10MemoryPoolEPv@Base 2019~U4
  _ZN3rml10pool_resetEPNS_10MemoryPoolE@Base 2017~U7
  _ZN3rml11pool_createElPKNS_13MemPoolPolicyE@Base 2017~U7

After that, build fails at dh_shlibdeps step:

   dh_shlibdeps
dpkg-shlibdeps: error: cannot find library libtbbmalloc.so.2 needed by
debian/libtbbmalloc2/usr/lib/${DEB_HOST_MULTIARCH}/libtbbmalloc_proxy.so.2
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot continue due to the error above
Note: libraries are not searched in other binary packages that do not
have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to use -l.
dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libtbbmalloc2.substvars
debian/libtbbmalloc2/usr/lib/\${DEB_HOST_MULTIARCH}/libtbbmalloc.so.2
debian/libtbbmalloc2/usr/lib/\${DEB_HOST_MULTIARCH}/libtbbmalloc_proxy.so.2
returned exit code 2
dh_shlibdeps: error: Aborting due to earlier error
make: *** [debian/rules:49: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2

onetbb 2021.5.0-7 builds fine with onetbb.diff in sid chroot.

Best,
Andrius

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Michael Tokarev]

22.04.2022 17:10, Adrian Davey wrote:

Package: qemu-system-x86
Version: 1:7.0+dfsg-1
Severity: normal

2022-04-21T17:07:40.354354Z qemu-system-x86_64: warning: This feature depends
on other features that were not requested: CPUID.800AH:EDX.npt [bit 0]


As I said, this is unrelated.


2022-04-21T17:07:40.419616Z qemu-system-x86_64: error: failed to set MSR
0xc104 to 0x1
qemu-system-x86_64: ../../target/i386/kvm/kvm.c:2996: kvm_buf_set_msrs:
Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.


And this is the actual issue in the.. KERNEL.

The commit in the kernel which introduce it is this one:

commit 880993138396f8f0be620c425d08f84490c35251
Author: Maxim Levitsky 
Date:   Tue Mar 22 19:24:48 2022 +0200

KVM: x86: SVM: fix tsc scaling when the host doesn't support it

which is part of 5.16.0 kernel.  And the commit which fixed this is

commit e910a53fb4f20aa012e46371ffb4c32c8da259b4
Author: Maxim Levitsky 
Date:   Wed Feb 23 13:56:49 2022 +0200

KVM: x86: nSVM: disallow userspace setting of MSR_AMD64_TSC_RATIO to non 
default value when tsc scaling disabled

which is a part of 5.16.12 kernel.

I don't know which is 5.16.0-5-amd64, - but it looks like 5.16.18 is
in Debian now. Is it your current kernel? What does `uname -a' say?

It looks like the only thing you need is to upgrade the kernel.


Reverting to qemu-system-x86 6.2+dfsg-3 and the VMs start-up perfectly fine
using the same libvirt xml.


It is because new qemu started using the MSRs it didn't use previously,
and hit this very issue. It is all in the kernel, -- it is the kernel
who reports the list of MSRs it supports, and qemu sets only those MSRs
which the kernel reports are supported. And out of the sudden one of
the reported-as-supported MSRs turned out to be unsupported by the kernel -
that's the meaining of this assert().

Please verify your kernel is at least 5.16.18.

Thanks,

/mjt


Kernel: Linux 5.16.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)

Bug#1010027: python3-paraview: pvpython does not run scripts

[Matsievskiy S.V.]

Package: python3-paraview
Version: 5.10.1-1
Severity: important
X-Debbugs-Cc: seregaxvm.m...@gmail.com

Dear Maintainer,

when trying to run script using pvpython or pvbatch python shell opens instead
of actually executing commands from the script. Prebuilt executable from
paraview site runs scripts as expected.

Steps to reproduce:
1. Create file test.py with contents `print("hello world")`
2. Run command pvpython test.py
3. Observe python shell being opened (expected behavior -- "hello world" in the
output)


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (580, 'stable-security'), (550, 
'stable-updates'), (500, 'stable'), (200, 'unstable'), (60, 'testing-debug'), 
(50, 'stable-debug'), (40, 'unstable-debug'), (20, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages python3-paraview depends on:
ii  libc6  2.33-7
ii  libgcc-s1  12-20220319-1
ii  libpython3.10  3.10.4-1
ii  libstdc++6 12-20220319-1
ii  paraview   5.10.1-1
ii  python33.9.8-1

python3-paraview recommends no packages.

python3-paraview suggests no packages.

-- no debconf information

Bug#1010013: ITP: python-websocketd -- Python module for creating a http server which uses WebSockets

[Paul Gevers]

Hmm,

On 22-04-2022 11:44, Bas Wijnen wrote:

* Package name: python-websocketd


I assume it's quite different from the nearly identical named 
python-websockets, which we already have.


paul@mulciber ~ $ rmadison python-websockets -s testing
python-websockets | 10.2-1| testing| source

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Helge Kreutzmann]

Hello Mark,
On Fri, Apr 22, 2022 at 09:11:46AM +0100, Mark Hindley wrote:
> On Wed, Apr 20, 2022 at 08:39:44PM +0200, Helge Kreutzmann wrote:
> > > The other possibility might be dpkg-diverts. Perhaps that depends on how 
> > > many
> > > conflicts there actually are/will be. I will try to quantify that more
> > > accurately.
> > 
> > That is an interesting idea. Than I wait for your analysis, thanks.
> 
> I have just compared the manpage lists in sysvinit, manpages-l10n and
> systemd. AFAICS the duplicates are the 7 in systemd-sysv:
> 
>   init.1
>   halt.8
>   poweroff.8
>   reboot.8
>   runlevel.8
>   shutdown.8
>   telinit.8
> 
> src:sysvinit has manpage translations for 7 languages: de es fi fr hu id pl.
> 
> That seems a manageable number to handle through dpkg-divert.

Thanks for the analysis, this is roughly what I've expected. 

Looking at the example section of dpkg-divert(1) I assume that
you will issue the appropriate calls to dpkg-divert in sysvinit
maintainer scripts and that I (on the manpage-l10n side) do not have
to use any special handling, correct?

Greetings

   Helge


-- 
  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#1009965: linux-image-5.17.0-1-amd64

[Holger Schröder]

Hi

I tried the 5.17 kernel from siduction.
It works fine with it, no problems.


...

Bug#978748: libboost-dev: Boost 1.75

[Anton Gladky]

Hi,

I did some work a couple of months ago, packaging 1.78.
It worked, but I did not have time to finish it. I would probably
continue this work soon to prepare 1.79 or even 1.80 for the
next stable Debian version.

Cheers

Anton


Am Fr., 22. Apr. 2022 um 10:03 Uhr schrieb Giovanni Mascellani <
g...@debian.org>:

> Hi,
>
> Il 14/04/22 04:24, strager ha scritto:
> > Is there anything I can do to help get a newer version of Boost into
> > the Debian repository?
>
> Unfortunately I am not having a lot of time to care about Boost right
> now, even if I'll get to it as soon as possible. I don't know what is
> your experience with Debian packaging, but Boost if you're a beginner I
> don't feel it's the right package to start with.
>
> As you say, vendoring code is usually not considered a good idea in
> Debian, but in can be a reasonable interim solution, I'd say, as long as
> you're happy to switch back to the packaged dependency once it is
> available. I would suggest you to investigate this road for
> quick-lint-js. I won't be able to provide much help, though.
>
> Thanks, Giovanni.
> --
> Giovanni Mascellani 
>
>

Bug#1010013: ITP: python-websocketd -- Python module for creating a http server which uses WebSockets

[Bas Wijnen]

On Fri, Apr 22, 2022 at 05:10:24PM +0200, Paul Gevers wrote:
> I assume it's quite different from the nearly identical named
> python-websockets, which we already have.

Yes, it is. They serve a similar purpuse, of course: using WebSockets in Python
programs. But the interface is very different. I'm not familiar with
python-websockets, so I can talk about what python-websocketd does that it
doesn't seem to do.

Python-websocketd attempts to provide RPC functionality, making it work like
the remote object is local. So you need to provide an object to the constructor
(if you want calls to be made by the remote end). Then the remote end can call
member functions of that object and receive the returned value. It can do so
while blocking, or asynchronously. For security (by avoiding accidentally
exposing functionality), data properties and member functions starting with an
underscore cannot be accessed remotely.

Thanks,
Bas


signature.asc
Description: PGP signature

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Adrian Davey]

HI Michael,

Apologies the reportbug package is installed on a laptop, the issue is on a
headless system, unfortunately debian doesn't allow SMTP from my mail
server so I am trying to get this posted via reportbug -> text editor ->
gmail -> bugs.debian , sometimes I miss replacing parts that are taken from
the laptop system information with the real system information.

This headless server has both Kernel: Linux 5.16.0-6-amd64 as well as Linux
5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux
same result as above.

libvirt full log (modified for anonymity) :
2022-04-21 17:07:40.149+: starting up libvirt version: 8.2.0, package:
1 (Andrea Bolognani  Wed, 20 Apr 2022 22:51:26 +0200), qemu
version: 7.0.0Debian 1:7.0+dfsg-1, kernel: 5.17.0-1-amd64, hostname:
REPLACED_VHOSTNAME
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME \
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.local/share \
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.cache \
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.config \
/usr/bin/qemu-system-x86_64 \
-name guest=REPLACED_VM_NAME,debug-threads=on \
-S \
-object
'{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/master-key.aes"}'
\
-blockdev
'{"driver":"file","filename":"/usr/share/OVMF/OVMF_CODE_4M.ms.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}'
\
-blockdev
'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/REPLACED_VM_NAME_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}'
\
-machine
pc-q35-5.2,usb=off,vmport=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram
\
-accel kvm \
-cpu
Opteron_G3,vme=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,mmxext=on,fxsr-opt=on,pdpe1gb=on,3dnowext=on,3dnow=on,cmp-legacy=on,cr8legacy=on,3dnowprefetch=on,osvw=on,amd-no-ssb=on,npt=on,nrip-save=on,vmcb-clean=on,svme-addr-chk=on,monitor=off
\
-m 512 \
-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":536870912}' \
-overcommit mem-lock=off \
-smp 2,sockets=2,cores=1,threads=1 \
-uuid f7722398-98ca-020a-13e7-93de4f798123 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-global ICH9-LPC.disable_s3=1 \
-global ICH9-LPC.disable_s4=1 \
-boot menu=off,strict=on \
-device
'{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}'
\
-device
'{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}'
\
-device
'{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}'
\
-device
'{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}'
\
-device
'{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}'
\
-device
'{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}'
\
-device
'{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}'
\
-device
'{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.2","addr":"0x0"}'
\
-device
'{"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.1","addr":"0x0"}' \
-device
'{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}'
\
-blockdev
'{"driver":"file","filename":"/opt/vm/images/REPLACED_VHOSTNAME/default/REPLACED_VM_NAME.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}'
\
-device
'{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk0","bootindex":1}'
\
-netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=34 \
-device
'{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:a7:24:12","bus":"pcie.0","addr":"0x3"}'
\
-netdev tap,fd=35,id=hostnet1,vhost=on,vhostfd=36 \
-device
'{"driver":"virtio-net-pci","netdev":"hostnet1","id":"net1","mac":"52:54:00:97:27:bf","bus":"pcie.0","addr":"0x6"}'
\
-chardev socket,id=charchannel0,fd=30,server=on,wait=off \
-device
'{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}'
\
-audiodev '{"id":"audio1","driver":"none"}' \
-vnc 127.0.0.1:0,audiodev=au

Bug#934258: Current status?

[julien . puydt]

Hi,

I wanted to push things a little further, and hence tried to get the
salsa repository ; I couldn't get very far, because d/control lists
quite a few non-existing packages:
- node-blueprintjs-core ;
- node-blueprintjs-select ;
- node-fortawesome-fontawesome-free.

By non-existing, I mean neither in unstable nor in NEW... there are
repositories though, and I'll try to have a look.

Could you give a feedback on where things stand?

What are you working on?

Is there a direction where I can push?

Cheers,

J.Puydt

Bug#1010028: cyrus-imapd: debian/rules license clarification

[Bastian Germann]

Source: cyrus-imapd
Severity: minor
Version: 3.6.0~beta2-2

debian/copyright claims debian/* to be CMU licensed while debian/rules has a 
GPL header.
Please clarify the license of that one file.

Bug#872398: closed by Julien Cristau (Re: Bug#872398: x11-xkb-utils: setxkbmap, when run at startup, has no effect)

[Christopher Cramer]

On Fri, Apr 22, 2022 at 02:48:03PM +, Debian Bug Tracking System wrote:
> Closing this old report.  It's not a bug in x11-xkb-utils, but probably
> in the X server, where changes made before the first keypress get (or
> used to get?) overwritten.  IIRC we had a number of reports about that
> over the years.

The bug seems to have been fixed anyway. The problem went away, and I
totally forgot about it.

Bug#1006935: Same problem

[Andrés Maldonado]

Hello,

I got the same problem as 1. after an 'apt upgrade', which upgraded 
Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to 
2:4.13.13+dfsg-1~deb11u3.


I'm on Debian Bullseye, I also use a i386 package and I have 'bind 
interfaces only = yes' in my config


After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using 
snapshot.debian.org), the problem was fixed.


Here is the backtrace:

[2022/04/22 17:16:17.267120,  0] ../../source3/smbd/server.c:1784(main)
  smbd version 4.13.13-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2020
[2022/04/22 17:16:17.313995,  0] 
../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve 
connections
[2022/04/22 17:16:17.315414,  0] 
../../source3/smbd/server.c:1244(open_sockets_smbd)

  open_sockets_smbd: No sockets available to bind to.
[2022/04/22 17:16:17.315751,  0] ../../lib/util/fault.c:159(smb_panic_log)
  ===
[2022/04/22 17:16:17.315779,  0] ../../lib/util/fault.c:160(smb_panic_log)
  INTERNAL ERROR: open_sockets_smbd() failed in pid 60894 (4.13.13-Debian)
[2022/04/22 17:16:17.315800,  0] ../../lib/util/fault.c:164(smb_panic_log)
  If you are running a recent Samba version, and if you think this 
problem is not yet fixed in the latest versions, please consider 
reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting

[2022/04/22 17:16:17.315819,  0] ../../lib/util/fault.c:169(smb_panic_log)
  ===
[2022/04/22 17:16:17.315836,  0] ../../lib/util/fault.c:170(smb_panic_log)
  PANIC (pid 60894): open_sockets_smbd() failed in 4.13.13-Debian
[2022/04/22 17:16:17.316116,  0] ../../lib/util/fault.c:274(log_stack_trace)
  BACKTRACE: 9 stack frames:
   #0 /lib/i386-linux-gnu/libsamba-util.so.0(log_stack_trace+0x30) 
[0xf7b3d140]
   #1 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic_log+0x76) 
[0xf7b3d296]

   #2 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic+0x31) [0xf7b3d431]
   #3 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff580) 
[0xf7dad580]
   #4 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff9d3) 
[0xf7dad9d3]
   #5 /usr/lib/i386-linux-gnu/samba/libsmbd-shim.so.0(exit_server+0x22) 
[0xf782d362]

   #6 /usr/sbin/smbd(main+0x176e) [0x565d56be]
   #7 /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0x106) [0xf75bde46]
   #8 /usr/sbin/smbd(_start+0x31) [0x565d63b1]
[2022/04/22 17:16:17.316220,  0] ../../source3/lib/util.c:838(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 60894]
[2022/04/22 17:16:17.376982,  0] ../../source3/lib/util.c:845(smb_panic_s3)
  smb_panic(): action returned status 0
[2022/04/22 17:16:17.377067,  0] ../../source3/lib/dumpcore.c:315(dump_core)
  dumping core in /var/log/samba/cores/smbd

Regards,

--
Andrés Maldonado
Code Lutin

Bug#1009996: IBus broken on GNOME on x11

[Osamu Aoki]

Hi,

Since no-no, I agree to go with what you proposed.

In order to avoid future confusion, can you add some of the key facts you 
stated.

> GTK_IM_MODULE=ibus was not needed at the time, but the mechanism which 
> made it work was broken in GNOME 42. So it's a regression.

Please add specific commit reference as a comment by explaining the above 
statement..


> It's a workaround, hopefully only temporary until we can do it properly 
> in the right package (maybe gnome-settings-daemon).

Let's add a comment to review situation by September/2022.

> It's the urgency which motivates the workaround. Especially as regards 
> Ubuntu 22.04, which was released yesterday with the issue, but I suppose 
> we don't want a broken IBus on testing's GNOME on Xorg either.

As I read the discussion, if this bug affects Debian/testing, and 
GTK_IM_MODULE=ibus
solves major concern which may come with on-screen keyboard, that's OK.

...

> Our original idea was to defer everything to GNOME. And GNOME still 
> starts ibus-daemon and sets XMODIFIERS and QT_IM_MODULE. So the only 
> thing we need to add through im-config is GTK_IM_MODULE.

I see.  Let's add this stance as comment since this is a temporary work around.

> But the answer to Q1 and Q2 are no and no. ;)

I see.


> So for those reasons I think my merge request is better (even if it's a 
> workaround).

As a code to fix issue, I agree with your merge request.

As for the issue tracking, I appreciate you add more context into comment. 

> > Extra discussion: Was the Budgie:GNOME issue related to this?  (Were
> > Budgie:GNOME running under x11?)
> 
> Budgie is run under x11, and Budgie starts ibus-daemon and sets the same 
> variables as GNOME does. I don't know to which extent this new issue 
> affects Budgie. But OTOH, "GTK_IM_MODULE=ibus" won't hurt on x11.

I see.

> > FYI: I read Ubuntu bug: https://launchpad.net/bugs/1969637 but not so
> > carefully.  So I may be missing something.
> 
> Ack. The issue is different in Ubuntu, but the proposed workaround 
> applies to Ubuntu too. The Ubuntu bug includes a couple of links to 
> interesting upstream gnome-settings-daemon commits.

You are talking about Ikuya's message, I think.  I didn't have time to check it 
yet.

Anyway, please upload updated im-config including your logic in the proposed 
patch.

Regards,

Osamu

Bug#1009883: closed by Debian FTP Masters (reply to Felix Lechner ) (Bug#1009883: fixed in haskell-devscripts 0.16.12)

[Scott Talbert]

Control: reopen -1

This does not appear to work correctly.  When a directory is created for 
package registration, the output changes to:


Creating package registration directory: 

Note the last part "directory" vs "file" in the single file case.  This 
causes the regex that's looking for "Creating package registration file" 
to not match.


Scott

Bug#1009772: armci-mpi: autopkgtest regression on s390x

[Dipak Zope1]

Thanks for reporting the bug Grahm!
I am looking into it.

Regards,
-Dipak

From: Graham Inggs 
Date: Sunday, 17 April 2022 at 1:33 PM
To: Debian Bug Tracking System 
Subject: [EXTERNAL] Bug#1009772: armci-mpi: autopkgtest regression on s390x
Source: armci-mpi
Version: 0.3.1~beta-6
X-Debbugs-CC: debian-s...@lists.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

armci-mpi's autopkgtests started failing on the big-endian s390x
architecture [1] where they passed previously.  I've copied what I
hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/a/armci-mpi/testing/s390x/


PASS: benchmarks/ping-pong
PASS: benchmarks/ring-flood
PASS: benchmarks/contiguous-bench
FAIL: benchmarks/strided-bench
PASS: benchmarks/rmw_perf
PASS: tests/test_onesided
PASS: tests/test_onesided_shared
PASS: tests/test_onesided_shared_dla
PASS: tests/test_mutex
PASS: tests/test_mutex_rmw
PASS: tests/test_mutex_trylock
PASS: tests/test_malloc_irreg
FAIL: tests/ARMCI_PutS_latency
FAIL: tests/ARMCI_AccS_latency
PASS: tests/test_groups
PASS: tests/test_group_split
PASS: tests/test_malloc_group
FAIL: tests/test_accs
FAIL: tests/test_accs_dla
FAIL: tests/test_puts
FAIL: tests/test_puts_gets
FAIL: tests/test_puts_gets_dla
FAIL: tests/test_putv
PASS: tests/test_igop
PASS: tests/test_rmw_fadd
PASS: tests/test_parmci
PASS: tests/mpi/test_mpi_accs
FAIL: tests/mpi/test_mpi_dim
FAIL: tests/mpi/test_mpi_indexed_accs
FAIL: tests/mpi/test_mpi_indexed_gets
FAIL: tests/mpi/test_mpi_indexed_puts_gets
FAIL: tests/mpi/test_mpi_subarray_accs
PASS: tests/mpi/test_win_create
PASS: tests/mpi/test_win_model
PASS: tests/ctree/ctree_test
PASS: tests/ctree/ctree_test_rand
PASS: tests/ctree/ctree_test_rand_interval
FAIL: tests/contrib/armci-perf
FAIL: tests/contrib/armci-test
PASS: tests/contrib/lu/lu-block
PASS: tests/contrib/lu/lu-b-bc
PASS: tests/contrib/transp1D/transp1D-c
PASS: tests/contrib/non-blocking/simple

Testsuite summary for armci 0.1

# TOTAL: 43
# PASS:  27
# SKIP:  0
# XFAIL: 0
# FAIL:  16
# XPASS: 0
# ERROR: 0
...

test-armci-mpich FAIL non-zero exit status 2

Bug#1005850: chromium: APNGs flicker

[Gianfranco Costamagna]

Hello,


I just looked into it; debian's libpng carries that same patch. 
Specifically, libpng-1.6.37-apng.patch from 
https://sourceforge.net/projects/libpng-apng/files/.


The request for upstream libpng to include the patch is at 
https://sourceforge.net/p/libpng/feature-requests/16/, but upstream 
libpng never merged it. Chromium bundles libpng without that patch, and 
seems to have made APNGs work without needing to patch libpng. To fix 
this bug, chromium should either use the bundled version of libpng, or 
debian's libpng should drop libpng-1.6.37-apng.patch.


I'm curious what the libpng maintainers think?



its ok for me to drop the patch, but somebody says that firefox needs it, so 
before dropping we should make sure
firefox for Debian and derivatives (also snap?) are using the bundled version 
and it works correctly.


I'll try to drop it and see what happens.

G.

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Michael Tokarev]

22.04.2022 19:01, Adrian Davey wrote:

HI Michael,

Apologies the reportbug package is installed on a laptop, the issue is on a 
headless system [..]


That's okay, that happens.


This headless server has both Kernel: Linux 5.16.0-6-amd64 as well as Linux 
5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux
same result as above.


The fix went into 5.17.0-rc3 kernel so it is included in your 5.17 kernel.

Now, 5.16.0-6-amd64 - this one is based on 5.16.18 which includes the fix.
While 5.16.0-5-amd64 is based on 5.16.14, which does not have it.

Are you sure the assertion failure problem occur with any of these *fixed*
kernels - either with  5.16.0-6-amd64 or with 5.17.3-1?

Please post the qemu error message(s) from any ofthe "fixed" kernels.

Also you can try the _older_ kernel, such as 5.15, - that one should work too.



libvirt full log (modified for anonymity) :


um. Where's the errors in there? I see full qemu command line (for which
I asked initially, before discovering the bad and the good commits).  Now
it seems the command line isn't really necessary (but we do have it anyway
which is good).

Thanks!

/mjt

Bug#1009080: transition: libgit2

[Sebastian Ramacher]

Control: tags -1 moreinfo
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-libgit2.html

On 2022-04-07 06:28:07 +0530, Mohammed Bilal wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: prav...@debian.org, mdbi...@disroot.org
> 
> Hello Release Team,
> 
> We would like to request a transition for libgit2 1.3.0
> (experimental -> unstable). 
> 
> The status of the most recent rebuilds is as follows.I've raised failure bugs 
> against these packages.
> 
> rebuild cargo ... FAIL (#1009015)
> rebuild criterion ... FAIL (#1009017)
> rebuild fritzing ... PASS
> rebuild geany-plugins ... PASS
> rebuild gitg ... PASS
> rebuild gnuastro ... PASS
> rebuild guile-git ... FAIL (#1009041)
> rebuild horizon-eda ... PASS
> rebuild julia ... FAIL (#1009029)
> rebuild ktexteditor ... PASS 
> rebuild kup-backup ... PASS 
> rebuild libgit-raw-perl ... FAIL (#1009031)
> rebuild libgit2-glib ... FAIL (#1009019)
> rebuild python-pygit2 ... FAIL (#1009033)
> rebuild r-cran-gert ... PASS
> rebuild ruby-rugged ... PASS
> rebuild rust-libgit2-sys ... FAIL (#1009034)

the tracker at
https://release.debian.org/transitions/html/auto-libgit2.html also lists
packages such as git-evtag and gnome-builder. Are they able to build
with the new libgit2 version?

Cheers

> 
> Ben file:
> 
> title = "libgit2";
> is_affected = .depends ~ "libgit2-1.1" | .depends ~ "libgit2-1.3";
> is_good = .depends ~ "libgit2-1.3";
> is_bad = .depends ~ "libgit2-1.1";
> 
> 
> Regards,
> rmb
> 
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1009984: transition: qt6-base

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-04-21 20:16:09 +0200, Patrick Franz wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: delta...@debian.org
> 
> Dear Release Team,
> 
> Qt 6.2.4 is packaged in experimental and needs a transition
> as we have an ABI change for the private headers as usual.
> 
> As Qt 6 is still quite new in Debian, only 2 non-Qt packages
> are affected by this:
> 
> * fcitx-qt5
> * fcitx5-qt
> 
> I successfully built both against Qt 6.2.4 and thus they should
> only need a NMU.

Please go ahead

Cheers

> 
> 
> Ben file:
> 
> title = "Qt 6.2.4";
> is_affected = .depends ~ /qt6-base-abi \(= 6\.2\.2\)/ | .depends ~ 
> /qt6-base-abi \(= 6\.2\.4\)/;
> is_good = .depends ~ /qt6-base-abi \(= 6\.2\.4\)/;
> is_bad = .depends ~ /qt6-base-abi \(= 6\.2\.2\)/;
> 
> 
> --
> Med vänliga hälsningar
> 
> Patrick Franz

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1007905: transition: icu

[Sebastian Ramacher]

Control: tags -1 = confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/auto-icu.html

Hi

On 2022-04-13 17:24:20 +0200, László Böszörményi wrote:
> On Wed, Apr 13, 2022 at 2:36 PM Jeremy Bicha  
> wrote:
> > mozjs78 and mozjs91 now no longer have an ICU dependency in Unstable.
> >
> > 0ad was fixed also.
>  Thanks. Did the rebuild locally on i386 and amd64; started with the
> ICU 71.1 RC release and finished with the final release if that
> matters. Only used Sid versions, didn't try the ones in experimental.
> The following is the result.
> icu-le-hb is outdated, need to be removed; pyicu needs an update that
> I've locally. gnucash self-testing fails with its C and Golang tests.
> The former can be fixed by adding tzdata build dependency and not yet
> checked the latter.
> LibreOffice self-testing, especially its break iterator test fails for
> the Lao language. Otherwise everything was fine. But I think I might
> redo the rebuilds (only on amd64 now) to test everything with the
> final release of ICU. If that's not mandatory, I think ICU is quite OK
> for a transition soon.

Please go ahead

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Adrian Davey]

Hi Michael,

Please ignore the 5.16.0-5-amd64 that is the laptop kernel, it only
features on the bug report due to my error, not the server's kernel @
5.16.0-6-amd64 and 5.17.0-1-amd64.

log using 5.17.0-1-amd64 kernel :

2022-04-21 17:07:40.149+: starting up libvirt version: 8.2.0, package:
1 (Andrea Bolognani  Wed, 20 Apr 2022 22:51:26 +0200), qemu
version: 7.0.0Debian 1:7.0+dfsg-1, kernel: 5.17.0-1-amd64, hostname:
REPLACED_VHOSTNAME
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME \
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.local/share \
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.cache \
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/.config \
/usr/bin/qemu-system-x86_64 \
-name guest=REPLACED_VM_NAME,debug-threads=on \
-S \
-object
'{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-REPLACED_VM_NAME/master-key.aes"}'
\
-blockdev
'{"driver":"file","filename":"/usr/share/OVMF/OVMF_CODE_4M.ms.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}'
\
-blockdev
'{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/REPLACED_VM_NAME_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}'
\
-machine
pc-q35-5.2,usb=off,vmport=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram
\
-accel kvm \
-cpu
Opteron_G3,vme=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,mmxext=on,fxsr-opt=on,pdpe1gb=on,3dnowext=on,3dnow=on,cmp-legacy=on,cr8legacy=on,3dnowprefetch=on,osvw=on,amd-no-ssb=on,npt=on,nrip-save=on,vmcb-clean=on,svme-addr-chk=on,monitor=off
\
-m 512 \
-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":536870912}' \
-overcommit mem-lock=off \
-smp 2,sockets=2,cores=1,threads=1 \
-uuid f7722398-98ca-020a-13e7-93de4f798282 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-global ICH9-LPC.disable_s3=1 \
-global ICH9-LPC.disable_s4=1 \
-boot menu=off,strict=on \
-device
'{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}'
\
-device
'{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}'
\
-device
'{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}'
\
-device
'{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}'
\
-device
'{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}'
\
-device
'{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}'
\
-device
'{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}'
\
-device
'{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.2","addr":"0x0"}'
\
-device
'{"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.1","addr":"0x0"}' \
-device
'{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}'
\
-blockdev
'{"driver":"file","filename":"/opt/vm/images/REPLACED_VHOSTNAME/default/REPLACED_VM_NAME.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}'
\
-device
'{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk0","bootindex":1}'
\
-netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=34 \
-device
'{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:a7:24:12","bus":"pcie.0","addr":"0x3"}'
\
-netdev tap,fd=35,id=hostnet1,vhost=on,vhostfd=36 \
-device
'{"driver":"virtio-net-pci","netdev":"hostnet1","id":"net1","mac":"52:54:00:97:27:bf","bus":"pcie.0","addr":"0x6"}'
\
-chardev socket,id=charchannel0,fd=30,server=on,wait=off \
-device
'{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}'
\
-audiodev '{"id":"audio1","driver":"none"}' \
-vnc 127.0.0.1:0,audiodev=audio1 \
-device
'{"driver":"virtio-vga","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}'
\
-device
'{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.5","addr":"0x0"}'
\
-object
'{"qom-type":"rng-random","id":"objrng0","filename":"/dev/urandom"}' \
-device
'{"driver":"virtio-rng-pci","rng":"objrng0","id":"rng0","bus":"pci.6","addr":"0x0"}'
\
-sandbox

Bug#1009954: gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency

[Eric Valette]

On 21/04/2022 14:12, Pirate Praveen wrote:



2022, ഏപ്രിൽ 21 5:27:25 PM IST, "Éric Valette" ൽ എഴുതി


The breakage is there for more than 8 months. I tried to install regularly.


Even if I want to, I'm not able to support gitlab in unstable or experimental. 
That is the reason why I had to create fasttrack.debian.net

Gitlab changes too fast for unstable or experimental.


I would say the contrary : experimental version are always above what 
gitlab expects. experiùmental is way faster than gitlab.


Putting gitlab related packages in experimental or unstable that you 
know cannot install is just frustrating. People have someting cretaed 
private packages version.




In this specific case multiple upstream gems needs to updated to work with 
omniauth 2.0. There are upstream bugs filed already. I can't step in as 
upstream maintainers of all those gems. More help is always welcome.
  

I does not work either if you bstarted from a testing ISO.


Yes, only stable is currently supported. More volunteers to support testing, 
unstable or experimental welcome.


Ben then why do yopu publsih pacakages that have no chnace to install 
for unstable and experimental.


Even outside gitlab, only stable is officially supported, unstable remains 
broken for many days during transitions.






   See wiki.debian.org/gitlab
  
  
 



Been ther done that. No way to make it work. FIX your package dependency. Its broken for as long as 1.9.1-1 has been in unstable meaning April 2020 see https://tracker.debian.org/pkg/ruby-omniauth


I meant follow the recommended option, that is bullseye-fasttrack.


Evne with buleyes fastrack, once you installed a testing iso and updated 
 you are scewed.



Could you please follow the rules and publish in experimental things that works 
with a debian unstable system.


I'm not able to do this alone, even if I want to, this is too much work for a 
single maintainer. At this point only bullseye-fasttrack I can reasonably 
support.


Then avoid publishing package for other debian version.


-- eric

Bug#1009883: closed by Debian FTP Masters (reply to Felix Lechner ) (Bug#1009883: fixed in haskell-devscripts 0.16.12)

[Scott Talbert]

On Fri, 22 Apr 2022, Scott Talbert wrote:


Control: reopen -1

This does not appear to work correctly.  When a directory is created for 
package registration, the output changes to:


Creating package registration directory: 

Note the last part "directory" vs "file" in the single file case.  This 
causes the regex that's looking for "Creating package registration file" to 
not match.


But actually...looking closer at this...I'm not entirely sure that 
handling multiple registration files per package is actually useful here. 
I think the case where I'm seeing multiple files is where packages have 
internal modules, which probably should not be being registered.  Let me 
investigate further.


Scott

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Thorsten Glaser]

On Fri, 22 Apr 2022, Mark Hindley wrote:

> > Or Replaces: but that has downsides on deinstallation.
> 
> Yes. And I am unclear how dpkg would behave if sysvinit-core was installed
> Replacing the manpages-l10n versions but then manpages-l10n was upgraded.

Hm. Given that manpages-l10n would *not* Replaces sysvinit-core,
I’d… say/hope ☺ that those of sysvinit-core take precedence. But
I have to admit… I actually am not sure. Asking the experts ☻

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against  Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!

Bug#1010029: apt: [INTL:nl] Dutch translation for the apt package

[Frans Spiesschaert]

 
 
Package: apt 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the apt package. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1006935: [Pkg-samba-maint] Bug#1006935: Same problem

[Michael Tokarev]

Control: tag -1 + confirmed

22.04.2022 19:15, Andrés Maldonado wrote:

Hello,

I got the same problem as 1. after an 'apt upgrade', which upgraded Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to 
2:4.13.13+dfsg-1~deb11u3.


I'm on Debian Bullseye, I also use a i386 package and I have 'bind interfaces 
only = yes' in my config

After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using 
snapshot.debian.org), the problem was fixed.


Just confirmed this in a local 32bit chroot. smbd immediately crashes at
startup with bind interfaces only = yes.

However I see no changes between 4.13.13+dfsg-1~deb11u2 and 
4.13.13+dfsg-1~deb11u3
which might be problematic in this context. Everything in there is completely
unrelated.

Lemme see if to-be 4.13.13+dfsg-1+deb11u4 works...

/mjt

Bug#1010032: dpkg: [INTL:nl] Dutch translation for the dpkg package

[Frans Spiesschaert]

 
 
Package: dpkg 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the dpkg package. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1010031: dselect: [INTL:nl] Dutch translation for the dselect package

[Frans Spiesschaert]

 
 
Package: dselect 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the dselect package. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as "dselect/po/nl.po" in your dpkg package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

[Michael Tokarev]

Control: retitle -1 qemu-system-x86_64: ../../target/i386/kvm/kvm.c:2996: 
kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

22.04.2022 20:34, Adrian Davey wrote:

Hi Michael,

Please ignore the 5.16.0-5-amd64 that is the laptop kernel, it only features on the bug report due to my error, not the server's kernel @ 
5.16.0-6-amd64 and 5.17.0-1-amd64.


log using 5.17.0-1-amd64 kernel :


Ok, that works. So it looks like the already mentioned commit didn't
actually fix the issue.  Let's retitle the bugreport (it fails to start
due to the assertion failure, the requested feature warnings are just
that - warnings, they're harmless).

And let's ask upstream about this..

Thank you!

/mjt

Bug#1010035: cryptsetup-nuke-password: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 
 
Package: cryptsetup-nuke-password 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the Dutch translation of cryptsetup-nuke-password
debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1010034: openldap: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 
 
Package: openldap 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of openldap debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1006935: Same problem

[Michael Tokarev]

22.04.2022 21:20, Michael Tokarev wrote:
..

Lemme see if to-be 4.13.13+dfsg-1+deb11u4 works...


And this one works indeed.  There's no changes between deb11u3
and deb11u4 which can fix this issue, but the prob (with locally
built deb11u4) is gone.  The build is performed on a stable
bullseye schroot.

Hmm..

Lemme re-build deb11u3 locally to see if this is maybe a build
issue?..

/mjt

Bug#913386: marked as done (Cacti Package Dependancy Issues)

[Paul Gevers]

Control: reopen -1
Control: block -1 by 1009943 1009944 1009945 1009946 1009947
Control: block -1 by 1009948 1009949 1009950 1009951 1009952
Control: block -1 by 1009953

On 14-04-2022 11:06, Debian Bug Tracking System wrote:

  cacti (1.2.20+ds1-1) unstable; urgency=medium



* Replace dependency on libjs-d3 by node-d3 (Closes: #913385)


I have to reopen this bug for now as node-d3 isn't ready yet to replace 
libjs-d3 as it can't be installed on armel.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

[Martin-Éric Racine]

On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo  wrote:
>
> Control: notfound -1 2.114.163
> Control: found -1 2.111.0
> Control: close -1 2.113.0
>
> On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote:
> > Package: lintian
> > Version: 2.114.163
>
> What version is this?! ...

The one reported when someone clicks on the line below.

> > The Lintian on mentors.debian.net incorrectly reports:
> >
> > W: improbable-bug-number-in-closes 1008784
> >
> > The relevant changelog entry:
> >
> > Replaces part of the cron job that we used to provide (Closes: #1008784).
> >
> > That bug report very much exists.
>
>
> This bug has long long been fixed, but lintian is not migrating and as
> such no backport to bullseye can be done.
> (plus I notice lintian hasn't been uploaded _at all_ for many months…)

Something tells me that the Lintian version found on Mentors is
unrelated to Testing migrations.

Martin-Éric

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

[Mattia Rizzolo]

On Fri, Apr 22, 2022 at 09:59:50PM +0300, Martin-Éric Racine wrote:
> On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo  wrote:
> >
> > Control: notfound -1 2.114.163
> > Control: found -1 2.111.0
> > Control: close -1 2.113.0
> >
> > On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote:
> > > Package: lintian
> > > Version: 2.114.163
> >
> > What version is this?! ...
> 
> The one reported when someone clicks on the line below.

Ah, now I found the number.. That's the version that is used on
lintian.debian.org, which is unrelated to what mentors.d.n reports.

> > This bug has long long been fixed, but lintian is not migrating and as
> > such no backport to bullseye can be done.
> > (plus I notice lintian hasn't been uploaded _at all_ for many months…)
> 
> Something tells me that the Lintian version found on Mentors is
> unrelated to Testing migrations.

It is very relevant instead, as on mentors we run whatever is on
bullseye-backports.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

[Martin-Éric Racine]

On Fri, Apr 22, 2022 at 10:05 PM Mattia Rizzolo  wrote:
>
> On Fri, Apr 22, 2022 at 09:59:50PM +0300, Martin-Éric Racine wrote:
> > On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo  wrote:
> > >
> > > Control: notfound -1 2.114.163
> > > Control: found -1 2.111.0
> > > Control: close -1 2.113.0
> > >
> > > On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote:
> > > > Package: lintian
> > > > Version: 2.114.163
> > >
> > > What version is this?! ...
> >
> > The one reported when someone clicks on the line below.
>
> Ah, now I found the number.. That's the version that is used on
> lintian.debian.org, which is unrelated to what mentors.d.n reports.

Noted.

> > > This bug has long long been fixed, but lintian is not migrating and as
> > > such no backport to bullseye can be done.
> > > (plus I notice lintian hasn't been uploaded _at all_ for many months…)
> >
> > Something tells me that the Lintian version found on Mentors is
> > unrelated to Testing migrations.
>
> It is very relevant instead, as on mentors we run whatever is on
> bullseye-backports.

Noted.

Martin-Éric

Bug#1010036: RM: lightyears -- RoQA; outdated; no interest in Debian to commit to its maintenance; still using python2

[Sandro Tosi]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mo...@debian.org

As the subject says, it's time to remove this old python2-only package

Bug#747196: cstream: new upstream release (3.1.1 18-Feb-2013)

[Florian Ernst]

Control: retitle -1 cstream: new upstream release (3.2.1, 2022-03-13)

On Tue, May 06, 2014 at 11:25:23AM +0200, Florian Ernst wrote:
> there is a new upstream release of cstream, the changelog reads as
> follows:

Well, 3.1.1 had entered the archives over three years ago, cf.
.

However, by now there are new upstream releases available, cf.
. The newest CHANGES read

| 3.2.1:
| --
| 
| print throughput after fsync, if requested.
| 
| 3.2.0:
| --
| 
| -O F option (do an fsync at the end of the output file).
| 
| When closing files fails, exit with an error code.

Please update the package when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1006935: Same problem

[Michael Tokarev]

22.04.2022 21:37, Michael Tokarev wrote:

Lemme re-build deb11u3 locally to see if this is maybe a build
issue?..


So I just rebuilt ~deb11u3 in a clean bullseye i386 schroot environment,
the standard way.

With the resulting samba-libs package samba does not crash at startup anymore,
and it all other sympthoms mentioned in this bugreport are gone too.

And the binaries are just too different to understand what's going on there.

Unfortunately there's no easily available build logs of this deb11u3 build,
to see maybe there are some interesting things in there.

*sigh*.

/mjt

Bug#993527: [debian-mysql] Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.

[Tobias Frost]

Control: found -1 1:10.5.15-0+deb11u1

On Sat, 9 Oct 2021 19:13:33 -0700 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
 wrote:
> Version: 1:10.5.12-0+deb11u1
> 
> Your testing verified that the issue is fixed in Debian testing that
> had 1:10.5.12-1. Debian Bullseye now got 1:10.5.12-0+deb11u1 so I
> assume it is now fixed for Bullseye, as the code in those versions are
> identical. Hence, closing issue.
> 
> 

Unfortunatly it's not fixed...

Today I came around to upgrade one of my servers from buster to bullseye, and
after upgrade I've found mariadb-server was uninstalled and I had to manually
install it afterwards.

Attached var/log/apt/history.log of the apt dist-upgrade step, including the
manual fixing.

-- 
Cheers,
tobi

Start-Date: 2022-04-22  20:18:31
Commandline: apt dist-upgrade
Requested-By: tobi (1000)
Install: linux-kbuild-5.10:amd64 (5.10.106-1, automatic), debhelper:amd64 (13.3.4, automatic), php7.4-mbstring:amd64 (7.4.28-1+deb11u1, automatic), php-symfony-service-contracts:amd64 (1.1.10-2, automatic), equivs:amd64 (2.3.1, automatic), libnginx-mod-stream-geoip2:amd64 (1.18.0-6.1, automatic), libonig5:amd64 (6.9.6-1.1, automatic), libgdk-pixbuf-xlib-2.0-0:amd64 (2.40.2-2, automatic), gcc-10:amd64 (10.2.1-6, automatic), libnl-3-200:amd64 (3.4.0-1+b1, automatic), libctf-nobfd0:amd64 (2.35.2-2, automatic), libnl-genl-3-200:amd64 (3.4.0-1+b1, automatic), libtypes-serialiser-perl:amd64 (1.01-1, automatic), libnftables1:amd64 (0.9.8-3.1, automatic), dwz:amd64 (0.13+20210201-1, automatic), php7.4-readline:amd64 (7.4.28-1+deb11u1, automatic), php7.4-gd:amd64 (7.4.28-1+deb11u1, automatic), php7.4-curl:amd64 (7.4.28-1+deb11u1, automatic), gsasl-common:amd64 (1.10.0-4, automatic), libnginx-mod-http-geoip2:amd64 (1.18.0-6.1, automatic), containerd:amd64 (1.4.13~ds1-1~deb11u1, automatic), php7.4-imap:amd64 (7.4.28-1+deb11u1, automatic), libskarnet2.10:amd64 (2.10.0.2-1, automatic), php7.4-bcmath:amd64 (7.4.28-1+deb11u1, automatic), libaom0:amd64 (1.0.0.errata1-3, automatic), libperl4-corelibs-perl:amd64 (0.004-2, automatic), libx265-192:amd64 (3.4-2, automatic), linux-compiler-gcc-10-x86:amd64 (5.10.106-1, automatic), automake:amd64 (1:1.16.3-2, automatic), php7.4-opcache:amd64 (7.4.28-1+deb11u1, automatic), php-psr-container:amd64 (1.0.0-2, automatic), libdeflate0:amd64 (1.7-1, automatic), libnginx-mod-stream-geoip:amd64 (1.18.0-6.1, automatic), libarchive-zip-perl:amd64 (1.68-1, automatic), alsa-ucm-conf:amd64 (1.2.4-2, automatic), libdav1d4:amd64 (0.7.1-3, automatic), python3-distro:amd64 (1.5.0-1, automatic), libs6-2.10:amd64 (2.10.0.2-1, automatic), libisc1105:amd64 (1:9.11.19+dfsg-2.1, automatic), libsub-override-perl:amd64 (0.09-2, automatic), linux-headers-5.10.0-13-common:amd64 (5.10.106-1, automatic), php7.4-cli:amd64 (7.4.28-1+deb11u1, automatic), po-debconf:amd64 (1.0.21+nmu1, automatic), libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1, automatic), php7.4-mysql:amd64 (7.4.28-1+deb11u1, automatic), libjson-perl:amd64 (4.03000-1, automatic), php7.4-fpm:amd64 (7.4.28-1+deb11u1, automatic), libdebhelper-perl:amd64 (13.3.4, automatic), libmail-authenticationresults-perl:amd64 (2.20210112-1, automatic), php7.4-gmp:amd64 (7.4.28-1+deb11u1, automatic), libcairo-gobject2:amd64 (1.16.0-5, automatic), php-symfony-polyfill-php80:amd64 (1.22.1-1, automatic), libbpf0:amd64 (1:0.3-2, automatic), nginx-core:amd64 (1.18.0-6.1, automatic), php7.4-json:amd64 (7.4.28-1+deb11u1, automatic), gcc-9-base:amd64 (9.3.0-22, automatic), libruby2.7:amd64 (2.7.4-1+deb11u1, automatic), libisc-export1105:amd64 (1:9.11.19+dfsg-2.1, automatic), libmaxminddb0:amd64 (1.5.2-1, automatic), php7.4-xml:amd64 (7.4.28-1+deb11u1, automatic), libltdl-dev:amd64 (2.4.6-15, automatic), php-symfony-event-dispatcher-contracts:amd64 (1.1.10-2, automatic), php7.4-zip:amd64 (7.4.28-1+deb11u1, automatic), libdns1110:amd64 (1:9.11.19+dfsg-2.1, automatic), autoconf:amd64 (2.69-14, automatic), libasan6:amd64 (10.2.1-6, automatic), fonts-urw-base35:amd64 (20200910-1, automatic), libopus0:amd64 (1.3.1-0.1, automatic), libnsl-dev:amd64 (1.3.0-2, automatic), autopoint:amd64 (0.21-4, automatic), linux-headers-5.10.0-13-amd64:amd64 (5.10.106-1, automatic), libcommon-sense-perl:amd64 (3.75-1+b4, automatic), mailcap:amd64 (3.69, automatic), media-types:amd64 (4.0.0, automatic), liburi-escape-xs-perl:amd64 (0.14-1+b5, automatic), php7.4-phpdbg:amd64 (7.4.28-1+deb11u1, automatic), libctf0:amd64 (2.35.2-2, automatic), bind9-dnsutils:amd64 (1:9.16.27-1~deb11u1, automatic), libperlio-utf8-strict-perl:amd64 (0.008-1+b1, automatic), libevent-2.1-7:amd64 (2.1.12-stable-1, automatic), autotools-dev:amd64 (20180224.1+nmu1, automatic), python3-icu:amd64 (2.5-1+b2, automatic), libprocps8:amd64 (2:3.3.17-5, automatic), gettext:amd64 (0.21-4, automatic), libcrypt-dev:amd64 (1:4.4.18-4, automatic), libtool:amd64 (2.4.6-15, automatic), php7.4-sqlite3:amd64 (7.4.28-1+deb11u1, automatic), libip6tc2:amd64 (1.8.7-1, automatic), cpp-10:amd64 (10.2.1-6, automatic), php7.4-common:amd64 (7.4.28

Bug#1010037: bullseye-pu: package hexchat/2.14.3-6

[Mattia Rizzolo]

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


[ Reason ]
Missing dependency on the python3 extension package.

I added this dependency some time ago, but only in bookworm, didn't
really thing of bullseye.

[ Impact ]
In a simple installation where this dependency is not available, trying
to load the python extensions leads to this traceback on the console,
and the ui just doesn't consider the python3 extension available.

|% hexchat
|Failed to initialize the Python-CFFI embedding logic:
|
|Traceback (most recent call last):
|  File "", line 1007, in _find_and_load
|  File "", line 984, in _find_and_load_unlocked
|ModuleNotFoundError: No module named '_cffi_backend'
|
|From: _hexchat_embedded
|compiled with cffi version: 1.14.5
|_cffi_backend module: not loaded
|sys.path: ['/usr/lib/python39.zip', '/usr/lib/python3.9', 
'/usr/lib/python3.9/lib-dynload']
|
|function _hexchat_embedded._on_plugin_init() called, but initialization code 
failed.  Returning 0.

This has also been reported via IRC on the upstream channel.

[ Tests ]
No automatic tests, trivial to manual check.

[ Risks ]
Nothing interesting, just an extra dep, no risks at all.

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



I already uploaded the package.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for hexchat-2.14.3 hexchat-2.14.3

 changelog |7 +++
 control   |1 +
 2 files changed, 8 insertions(+)

diff -Nru hexchat-2.14.3/debian/changelog hexchat-2.14.3/debian/changelog
--- hexchat-2.14.3/debian/changelog 2021-05-26 14:55:10.0 +0200
+++ hexchat-2.14.3/debian/changelog 2022-04-22 21:40:55.0 +0200
@@ -1,3 +1,10 @@
+hexchat (2.14.3-6+deb11u1) bullseye; urgency=medium
+
+  * hexchat-python3: Add missing dependency on python3-cffi-backend.
+Closes: #1009877
+
+ -- Mattia Rizzolo   Fri, 22 Apr 2022 21:40:55 +0200
+
 hexchat (2.14.3-6) unstable; urgency=medium
 
   * Add Recommends:ca-certificates.
diff -Nru hexchat-2.14.3/debian/control hexchat-2.14.3/debian/control
--- hexchat-2.14.3/debian/control   2021-05-26 14:54:00.0 +0200
+++ hexchat-2.14.3/debian/control   2022-04-22 21:39:07.0 +0200
@@ -81,6 +81,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
+ python3-cffi-backend,
  ${misc:Depends},
  ${shlibs:Depends},
 Recommends:


signature.asc
Description: PGP signature

Bug#1010038: monitoring-plugins-basic: check_ide_smart introduces risk of data loss

[Antonio Trueba]

Package: monitoring-plugins-basic
Severity: normal
Tags: upstream
X-Debbugs-Cc: atga...@gmail.com

Dear maintainer,

I've been relying on check_ide_smart for some time to monitor my HDDs and up to
now there has never been a malfunction reported, with all disks being reported
as passing all tests and in the OK status. While setting up a new server I've
found two issues with this plugin that I think should be enough to mark it as
deprecated, both in Debian and in upstream:

- It just doesn't recognize drives connected through an HBA, even though
smartctl does. This is a known limitation of the plugin.

- When using a more up to date alternative, I've found that some of the HDDs
that check_ide_smart was reporting as OK have in fact reached some pre-failure
conditions and are worth replacing. This isn't related to the hardware
interface as those drives are in production and have been monitored with
check_ide_smart for quite some time, I've just changed the monitoring plugin.


So, as check_ide_smart isn't properly reporting HDD status (or, at least,
failing to report early warnings) I believe keeping it available as is
introduces the risk for a potential data loss. There are alternatives
available, so I suggest to consider substituting the plugin instead of updating
it. The best I've found is Kurt Yoder and Claudio Kuenzler's check_smart[1][2],
but I'm not sure of the licensing status (the code shows that "This script was
initially created under contract for the US Government and is therefore Public
Domain", but there's no specific license mentioned).


Regards.


[1]https://www.claudiokuenzler.com/monitoring-plugins/check_smart.php
[2]https://exchange.nagios.org/directory/Plugins/System-Metrics/Storage-
Subsystem/check_smart-2Epl--2D-physical-drive-monitoring/details


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages monitoring-plugins-basic depends on:
ii  iputils-ping   3:20211215-1
ii  libc6  2.33-7
ii  libssl1.1  1.1.1n-1
pn  monitoring-plugins-common  
ii  procps 2:3.3.17-7+b1
ii  ucf3.0043

Versions of packages monitoring-plugins-basic recommends:
ii  libcap2-bin  1:2.44-1

Versions of packages monitoring-plugins-basic suggests:
pn  icinga2  

Bug#1009965: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder not working anymore

[Diederik de Haas]

Control: tag -1 moreinfo

On Friday, 22 April 2022 17:22:42 CEST Holger Schröder wrote:
> I tried the 5.17 kernel from siduction.
> It works fine with it, no problems.

Comparing/sharing the dmesg output of both could be helpful.

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

Bug#1010039: autorandr: python deprecation warnings

[gregor herrmann]

Package: autorandr
Version: 1.11-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Looks like autorandr needs an update for compatibility with future
python versions:

% autorandr 
/usr/bin/autorandr:42: DeprecationWarning: The distutils package is deprecated 
and slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
  from distutils.version import LooseVersion as Version


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmJjK/5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYVZA//S+jLJTwbI+zhjGnQwIHwk5BsST0ejRzgZpyzehH4F7y2NLIeSmf+p7O+
BKq/I539SWy1q3UhMYJtwBGeEe49Yn9u3nRSjMsUqn4Q4hxveKV5lTxq7l22tZgU
QYK+awYhUlAHqvXxlAdRPe5VVqTZeL4zJzBKYnhn62vHPMeFiLIL/8yntHXg9W91
xnm4xskrnsH69MujNkg0xn+6omrcb3m41S2kXgeC+w7AX+jDMAunLajFvpkY0puw
ayCirAM6DPSe3dF/miw1uGJm/rqQxUySfY8YVv9NVunKZb6LINNTT1B8+hcM746c
VxvRLijwGzq8uics/OlYnGKMzLT1Wv8W/qzgZfxPB6uNdzalIpAjN1F1PuvuXykH
KqrBMeO4Po+J75C3wlvhnHPbswKjA628JQ9b34PZfFQcyd90BOYAlTXgTobJtoUw
oWZoZPbzyaAsUYfkHYXGCJlC0dTSIKDyzlUYHT0PwVZUEpX1L9mzju43tFlhuGnS
NqtrieRVrjqdMpWjZhrKUQ1dGC6X+1hsXfn9ZAVhoX9aXBREayRVwm9yFzd4Tpse
r3lDH/NhKkd9EhViBDJ9fGwJiT/lFZPEAxGtLGDIk0RPhX2lQjXtO+/mpiGg+dPA
Er/TnkHTi+1uD8oUrsY3P8A3HFi64fKnEkaPZvU2OVkv1carlDI=
=pR2U
-END PGP SIGNATURE-

Bug#965922: zpspell: diff for NMU version 0.4.3-4.2

[Joao Eriberto Mota Filho]

Control: tags 965922 + patch
Control: tags 965922 + pending

Dear maintainer,

I've prepared an NMU for zpspell (versioned as 0.4.3-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u zpspell-0.4.3/debian/compat zpspell-0.4.3/debian/compat
--- zpspell-0.4.3/debian/compat
+++ zpspell-0.4.3/debian/compat
@@ -1 +1 @@
-5
+7
diff -u zpspell-0.4.3/debian/changelog zpspell-0.4.3/debian/changelog
--- zpspell-0.4.3/debian/changelog
+++ zpspell-0.4.3/debian/changelog
@@ -1,3 +1,10 @@
+zpspell (0.4.3-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/compat: bumped level to 7. (Closes: #965922)
+
+ -- Joao Eriberto Mota Filho   Fri, 22 Apr 2022 19:23:46 
-0300
+
 zpspell (0.4.3-4.1) unstable; urgency=low
 
   * Non-maintainer upload.

Bug#965911: yasat: diff for NMU version 848-1.2

[Joao Eriberto Mota Filho]

Control: tags 965911 + patch
Control: tags 965911 + pending

Dear maintainer,

I've prepared an NMU for yasat (versioned as 848-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -Nru yasat-848/debian/changelog yasat-848/debian/changelog
--- yasat-848/debian/changelog  2021-01-03 15:56:33.0 -0300
+++ yasat-848/debian/changelog  2022-04-22 19:36:32.0 -0300
@@ -1,3 +1,16 @@
+yasat (848-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965911
+  * debian/clean: created to remove some files created from the build process
+and forgotten after this. This action will allow package to build twice.
+
+ -- Joao Eriberto Mota Filho   Fri, 22 Apr 2022 19:36:32 
-0300
+
 yasat (848-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru yasat-848/debian/clean yasat-848/debian/clean
--- yasat-848/debian/clean  1969-12-31 21:00:00.0 -0300
+++ yasat-848/debian/clean  2022-04-22 19:36:32.0 -0300
@@ -0,0 +1,4 @@
+tests/test_rsa.pem
+tests/test_rsa_password.pem
+tests/yasat_global.advice
+yasat.advices
diff -Nru yasat-848/debian/compat yasat-848/debian/compat
--- yasat-848/debian/compat 2014-01-24 11:29:46.0 -0200
+++ yasat-848/debian/compat 1969-12-31 21:00:00.0 -0300
@@ -1 +0,0 @@
-5
diff -Nru yasat-848/debian/control yasat-848/debian/control
--- yasat-848/debian/control2016-08-30 06:04:43.0 -0300
+++ yasat-848/debian/control2022-04-22 19:36:32.0 -0300
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Corentin LABBE 
-Build-Depends: debhelper (>= 7.0.50)
+Build-Depends: debhelper-compat (= 13)
 Standards-Version: 3.9.8
 Homepage: http://yasat.sourceforge.net/
 

Bug#965910: xtron: diff for NMU version 1.1a-14.2

[Joao Eriberto Mota Filho]

Control: tags 965910 + patch
Control: tags 965910 + pending

Dear maintainer,

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

Regards,

Eriberto

diff -u xtron-1.1a/debian/changelog xtron-1.1a/debian/changelog
--- xtron-1.1a/debian/changelog
+++ xtron-1.1a/debian/changelog
@@ -1,3 +1,10 @@
+xtron (1.1a-14.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/compat: bumped compat level to 7. (Closes: #965910)
+
+ -- Joao Eriberto Mota Filho   Fri, 22 Apr 2022 20:18:27 
-0300
+
 xtron (1.1a-14.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u xtron-1.1a/debian/compat xtron-1.1a/debian/compat
--- xtron-1.1a/debian/compat
+++ xtron-1.1a/debian/compat
@@ -1 +1 @@
-5
+7

Bug#1010040: RFS: quick-lint-js/2.4.1-2 -- JavaScript linter

[strager]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "quick-lint-js":

 * Package name: quick-lint-js
   Version : 2.4.1-2
   Upstream Author : Matthew "strager" Glazar 
 * URL : https://quick-lint-js.com/
 * License : BSL-1.0, GPL-3.0-or-later and MIT, CC-BY-SA-4.0,
GPL-3.0-or-later
 * Vcs : https://github.com/quick-lint/quick-lint-js
   Section : devel

ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009937b

The source builds the following binary packages:

  quick-lint-js - JavaScript linter
  quick-lint-js-vim - Vim and Neovim plugin for quick-lint-js

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

  https://mentors.debian.net/package/quick-lint-js/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/q/quick-lint-js/quick-lint-js_2.4.1-2.dsc

Thanks,
Matthew "strager" Glazar

Bug#1008424: audiofile: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2

[Alberto Garcia]

On Mon, Apr 04, 2022 at 03:25:44PM +0200, Alberto Garcia wrote:

> > During a rebuild of all packages in sid, your package failed to
> > build on amd64.
> > 
> > > FAIL: FLAC
> 
> This started to happen after flac was updated from 1.3.3-2 to 1.3.4-1.

I bisected the changes in flac and the problems started here:

   commit 159cd6c41a6ec17b36d74043c45a3aa64de90d5e
   Author: Robert Kausch 
   Date:   Thu Oct 29 20:37:40 2020 +0100

   libFLAC/stream_decoder.c: Use current position as bound when seeking

I submitted a bug report upstream: https://github.com/xiph/flac/issues/327

Berto