Bug#982483: marked as done (r-cran-rcppparallel: generates broken load path for libtbb and fails on several architectures)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 08:35:11 +0100
with message-id <20210221073511.gi8...@an3as.eu>
and subject line Close bug on behalf of Shayan Doust
has caused the Debian Bug report #982483,
regarding r-cran-rcppparallel: generates broken load path for libtbb and fails 
on several architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debia...@lists.debian.org

Hi ftpmaster,

Shayan Doust worked really hard to fix an issue in r-cran-rstan to
enable smooth building of r-cran-rstanarm.  For the moment it is not
clear yet why this fix does not work for armhf, i386 and mips64el but
other architectures are building nicely.  We will keep on investigating
this issue but it would be important to let r-cran-rstanarm migrate
to testing to let a whole bunch of other R package migrate as well.

So please remove r-cran-rstanarm for the said architectures from
unstable.

Thanks a lot for your ftpmaster work

   Andreas.
--- End Message ---
--- Begin Message ---
This bug is done with version 5.0.2+dfsg-4--- End Message ---

Bug#983213: ukui-control-center: Missing dependency on libglib2.0-bin

[Adrian Bunk]

Package: ukui-control-center
Version: 3.0.2-1
Severity: serious

https://piuparts.debian.org/sid/fail/ukui-control-center_3.0.2-1.log

...
  Setting up ukui-control-center (3.0.2-1) ...
  /var/lib/dpkg/info/ukui-control-center.postinst: 5: glib-compile-schemas: not 
found
  dpkg: error processing package ukui-control-center (--configure):
   installed ukui-control-center package post-installation script subprocess 
returned error exit status 127
...

Processed: Re: Bug#959138 closed by Debian FTP Masters (reply to Yaroslav Halchenko ) (Bug#959138: fixed in nipy 0.4.3~rc1-1)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # prevent BTS getting confused
> reassign 959138 src:nipy 0.4.2-3
Bug #959138 {Done: Yaroslav Halchenko } [src:nipy] numpy 
breaks nipy autopkgtest: No module named 'numpy.testing.decorators'
Ignoring request to reassign bug #959138 to the same package
Bug #959138 {Done: Yaroslav Halchenko } [src:nipy] numpy 
breaks nipy autopkgtest: No module named 'numpy.testing.decorators'
Marked as found in versions nipy/0.4.2-3.
> affects 959138 src:numpy
Bug #959138 {Done: Yaroslav Halchenko } [src:nipy] numpy 
breaks nipy autopkgtest: No module named 'numpy.testing.decorators'
Added indication that 959138 affects src:numpy
> fixed 959138 0.4.3~rc1-1
Bug #959138 {Done: Yaroslav Halchenko } [src:nipy] numpy 
breaks nipy autopkgtest: No module named 'numpy.testing.decorators'
Ignoring request to alter fixed versions of bug #959138 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
959138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983211: php-http-psr7-integration-tests: autopkgtest failure

[Adrian Bunk]

Source: php-http-psr7-integration-tests
Version: 1.1.1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-http-psr7-integration-tests/10589995/log.gz

...
autopkgtest [21:38:30]: test command1: mkdir -p vendor && phpab -o 
vendor/autoload.php -t debian/autoload.tests.php.tpl tests && phpunit 
--testsuite Guzzle
autopkgtest [21:38:30]: test command1: [---
phpab %development% - Copyright (C) 2009 - 2021 by Arne Blankerts and 
Contributors

Scanning directory tests

Autoload file vendor/autoload.php generated.

PHPUnit 9.5.2 by Sebastian Bergmann and contributors.

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using "--migrate-configuration"!

..S  63 / 137 ( 45%)
....E.E.E..E... 126 / 137 ( 91%)
... 137 / 137 (100%)

Time: 00:00.137, Memory: 8.00 MB

There were 4 errors:

1) Http\Psr7Test\Tests\Guzzle\StreamTest::testIsNotSeekable
fopen(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
failed

/usr/share/php/Http/Psr7Test/StreamIntegrationTest.php:152

2) Http\Psr7Test\Tests\Guzzle\StreamTest::testIsNotWritable
fopen(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
failed

/usr/share/php/Http/Psr7Test/StreamIntegrationTest.php:179

3) Http\Psr7Test\Tests\Guzzle\StreamTest::testIsNotReadable
fopen(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
failed

/usr/share/php/Http/Psr7Test/StreamIntegrationTest.php:206

4) Http\Psr7Test\Tests\Guzzle\StreamTest::testRewindNotSeekable
fopen(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
failed

/usr/share/php/Http/Psr7Test/StreamIntegrationTest.php:251

ERRORS!
Tests: 137, Assertions: 247, Errors: 4, Skipped: 5.
autopkgtest [21:38:30]: test command1: ---]
autopkgtest [21:38:30]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 2

Bug#983028: marked as done (splint-data build failure: missing files)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 06:35:17 +
with message-id 
and subject line Bug#983028: fixed in splint 1:3.1.2+dfsg-5
has caused the Debian Bug report #983028,
regarding splint-data build failure: missing files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: splint
Version: 1:3.1.2+dfsg-4
Severity: serious
Tags: ftbfs
Justification: ftbfs

splint-data 1:3.1.2+dfsg-4 is missing, so that splint cannot be
installed.

https://buildd.debian.org/status/package.php?p=splint signals a
build failure for "all" (thus affecting splint-data):

make[1]: Entering directory '/<>'
dh_install -psplint-data -X.lcd -XMakefile
dh_install: warning: Cannot find (any matches for) "usr/share/splint/imports/" 
(tried in ., debian/tmp)

dh_install: warning: splint-data missing files: usr/share/splint/imports/
dh_install: warning: Cannot find (any matches for) "usr/share/splint/lib/" 
(tried in ., debian/tmp)

dh_install: warning: splint-data missing files: usr/share/splint/lib/
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:52: override_dh_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:23: binary-indep] Error 2

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

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

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: splint
Source-Version: 1:3.1.2+dfsg-5
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
splint, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated splint package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2021 07:38:34 +0200
Source: splint
Architecture: source
Version: 1:3.1.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 983028
Changes:
 splint (1:3.1.2+dfsg-5) unstable; urgency=medium
 .
   * QA upload.
   * Workaround binary-all FTBFS by reverting the splint-data.install
 change and going back to debhelper compat 12. (Closes: #983028)
Checksums-Sha1:
 c4416522fac45ef26004dabae8dc233d40931d32 2002 splint_3.1.2+dfsg-5.dsc
 02e1462a807d5897b598bd58c642dee9535ec9a8 107252 
splint_3.1.2+dfsg-5.debian.tar.xz
Checksums-Sha256:
 1ee69fc7ffe6fae0ebea0fe16858fcb2656eea56ebecb32382356759226e5d7a 2002 
splint_3.1.2+dfsg-5.dsc
 797f1bf017ed729476ba045df802d45bb1205843e96df658aef08ad0c6f4ff7f 107252 
splint_3.1.2+dfsg-5.debian.tar.xz
Files:
 7021a7cd1ca7abe2cee52ad610356079 2002 devel optional splint_3.1.2+dfsg-5.dsc
 ff1aa3a97ffeac5da3aa1c3185799668 107252 devel optional 
splint_3.1.2+dfsg-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAx+18ACgkQiNJCh6LY
mLEjNQ//aOEGk3SM99hp4AYhxMFD+UXp1rAeheSsnVWsGS/QozZtaeP6KjX8txIm
qXzTMVQl3j4K2aATQvjMOiba2E82dXVpULQ9zbe1dL9EqinjH1rnWt4FEmTyqk9H
en2Q8ary4Hgbq0QuU4Ekrzy0MKjwTtzOBOiFHwKwwYMIWpTnKIBWaXNXNXRgwe1Q
M19jiwU0haGNqA9nolHRaenuI98sB7NCmogaC7Wc2CrNUaPZgJbIvGnakU0InSgl
uhV2xYrsAWwyedKduAq5MD8RWjxbkgsw968EN8A2BpQ11//0WIuF1YJnNVVUBac+
tDstxVFQunDxBGQZ2bs/tXKLHmCjPlxAT5nD5y8w/GJW8+q2I9hIqdkS4WXCsEq0
RrVT1wfk7T6Noqka7WZcr2RIgxs4e14DmbsJfjKhjh78uqyHigymEwpTEc+zNMFl
eBBiqxz30mEyXx0itCioE1xiVALkOLWzFBELSAnu2ImvMmNkQP2ljERGojjIEg6T

Bug#978371: marked as done (gnokii: FTBFS: configure.in:74: error: possibly undefined macro: AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 05:35:54 +
with message-id 
and subject line Bug#978371: fixed in gnokii 0.6.30+dfsg-1.3
has caused the Debian Bug report #978371,
regarding gnokii: FTBFS: configure.in:74: error: possibly undefined macro: 
AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnokii
Version: 0.6.30+dfsg-1.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh_testdir
> dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:74: warning: macro 'AM_LANGINFO_CODESET' not found in library
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> configure.in:112: the top level
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> configure.in:112: the top level
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> configure.in:112: the top level
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> configure.in:112: the top level
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> configure.in:112: the top level
> configure.in:112: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4170: 

Processed: bug 971289 is forwarded to https://github.com/bbangert/beaker/pull/205

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 971289 https://github.com/bbangert/beaker/pull/205
Bug #971289 [src:beaker] beaker: Switch to python3-pycryptodome
Set Bug forwarded-to-address to 'https://github.com/bbangert/beaker/pull/205'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982870: marked as done (hotspot FTBFS on mips*)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 05:03:34 +
with message-id 
and subject line Bug#982870: fixed in hotspot 1.3.0-2
has caused the Debian Bug report #982870,
regarding hotspot FTBFS on mips*
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hotspot
Version: 1.3.0-1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: 
https://github.com/KDAB/perfparser/commit/834db4506d1aeae02d32fe41065d558300491d84

https://buildd.debian.org/status/package.php?p=hotspot

...
/<>/3rdparty/perfparser/app/perfregisterinfo.cpp:55:12: error: 
expected unqualified-id before numeric constant
   55 | static int mips[] = { 32,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 
12, 13, 14, 15, 16, 17,
  |^~~~
...
--- End Message ---
--- Begin Message ---
Source: hotspot
Source-Version: 1.3.0-2
Done: Yanhao Mo 

We believe that the bug you reported is fixed in the latest version of
hotspot, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yanhao Mo  (supplier of updated hotspot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2021 11:26:09 +0800
Source: hotspot
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Yanhao Mo 
Changed-By: Yanhao Mo 
Closes: 982870
Changes:
 hotspot (1.3.0-2) unstable; urgency=medium
 .
   * Patch to fix build on mips (Closes: #982870)
Checksums-Sha1:
 309888505fa27bd7e38114513c17e1e5d1b01d10 2100 hotspot_1.3.0-2.dsc
 360d3596379ed23d80d530f7f8184e623eb200ac 633952 hotspot_1.3.0-2.debian.tar.xz
 0eda7bde6df01863e3b9541ffa7ca140096a3972 14320 hotspot_1.3.0-2_amd64.buildinfo
Checksums-Sha256:
 b014e848c1ac40b9e2357b90d5b9f555658816e7cd99acac44de5e3a9d77c5af 2100 
hotspot_1.3.0-2.dsc
 810207fc781190a988c1c0aca3318f2dbecbb81351f17f03e532ffe090857f86 633952 
hotspot_1.3.0-2.debian.tar.xz
 27e4a3f2520226d89bdcffe0e3b61230131453a9f70a74c8ceab482c4de671e5 14320 
hotspot_1.3.0-2_amd64.buildinfo
Files:
 b3c282cbacdd6ef1a78d552f9345920f 2100 utils optional hotspot_1.3.0-2.dsc
 79c83a15e1e9b15f9e6680060d554311 633952 utils optional 
hotspot_1.3.0-2.debian.tar.xz
 c64055e1dc952c3fb9c897d68d1bc284 14320 utils optional 
hotspot_1.3.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEb9bJQfCTGv6uM2+ujv2XAviIsq4FAmAx5cITHHlhbmhhb2Nz
QGdtYWlsLmNvbQAKCRCO/ZcC+Iiyrn+xD/wOux8TdNwdbel7TexS6m+zepDHYnr4
SosgRHpghF0KHU8Z2+5YatGKKBYZQLP9QGVQ3yM82Ku9iBkPylExeibVOsYoBoj0
eNH+kNnlQ9P27vjdlSFZk2gJJC4RM1CGXDWf7fQgnmFS410z+AWDBdJ0TAEZgj1Y
EEth9iCbp3TsPqPjzQK+vwqf78CTLNproD7rnNMD6uIhedDZulXQ0V0psLZEN2fy
StInx1pVo8Yc24YBIVdDE48gnte1VpCvMBdOqKTY9z3RE9Iiz5G6k8ehBeoAx8d8
OEyezklfDNGlip6qxsokKM7C00ONyng2Vdo+IMI/HAcXVb8S3iHOJSyQPG5+V+fH
9YyRxTF0CaZdM64WxF9lf8qcuxvsU+36ZDdNH32ETdZyBA8BKDV0DjDPc2aaMd2d
PkSFMgdGXiN5qyQX9nNWoTaEt+AEhwXq7YM1lyxQtQlILZeHQiSGn0ryzW8D68/S
Kkd09/Ajb3lIbguWGiNbQEjrejSJa9Pcuha8KaV/3j8s8uP8OEtCnzVYQmlXdICY
pQf6MyR35NseIVu8tdNylJ/ayl2i9Rz8HumcBvkZe+ThjXBG1YFmeT79RnXNaHgH
FlgAckBvLRqVXZQpMwxecSAvxyoRfoE2RZpQCILMHWeYoQxd4Ua1PCCIy2J8xG27
Iea1VOcL0RUlcw==
=6lHx
-END PGP SIGNATURE End Message ---

Bug#983206: [libupnp13] Please update for CVE-2020-12695 & fixes

[Lyndon Brown]

On Sun, 21 Feb 2021 04:16:21 + Lyndon Brown 
wrote:
> I'm also having trouble getting DLNA working with minidlna on one
> system and vlc on another, with little idea so far why it's not
> working. Getting an updated libupnp13 with all the fixes they've made
> may help eliminate some possible causes.

Weird, having spent hours on this, I switched back to vlc after firing
off the email and the remote system was suddenly right there in vlc's
list... I can't explain that. I don't think I'd made any changes since
the last time I checked. Something I did earlier must have fixed it but
with some sort of delay to updating something. I think that the only
big difference to where I started from is no longer having minissdpd on
the server. Interestingly with it now fixed I refreshed the
x.x.x.x:8200 webpage in the browser and noticed the client type field
changed, from 'Unknown' to 'Generic UPnP 1.0'.

Hmm... Well that did not last. A little fiddling, and now it's gone
again and I'm not having any success at getting it back. The client has
also gone back to 'Unknown'. :/

Anyway, please update at least for the CVE, and fingers crossed it may
help with this also.

Bug#983206: [libupnp13] Please update for CVE-2020-12695 & fixes

[Lyndon Brown]

Package: libupnp13
Version: 1:1.8.4-2
Severity: critical

According to the changelog upstream version 1.14.0 includes a security
fix for CVE-2020-12695 (currently not tracked for pupnp in the debian
security tracker).

Please update to 1.14.x. Thanks.

I'm also having trouble getting DLNA working with minidlna on one
system and vlc on another, with little idea so far why it's not
working. Getting an updated libupnp13 with all the fixes they've made
may help eliminate some possible causes.

Bug#983205: golang-github-go-ping-ping: Some tests require network access

[Logan Rosen]

Package: golang-github-go-ping-ping
Version: 0+git20201106.b6486c6-2
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hi,

python-rfc6555 currently requires network access during build for some of its
tests, which causes the build to fail in Ubuntu [1] (and reproducible
builds [2]) and is a violation of Debian policy.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/skip-tests-requiring-network-access.patch: Skip tests that require
network access since Ubuntu's buildds don't have it.

Thanks for considering the patch.

Logan

[1] 
https://launchpad.net/ubuntu/+source/golang-github-go-ping-ping/0+git20201106.b6486c6-2/+build/20988534
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-go-ping-ping.html
diff -Nru 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/series 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/series
--- golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/series  
1969-12-31 19:00:00.0 -0500
+++ golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/series  
2021-02-20 23:04:52.0 -0500
@@ -0,0 +1 @@
+skip-tests-requiring-network-access.patch
diff -Nru 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/skip-tests-requiring-network-access.patch
 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/skip-tests-requiring-network-access.patch
--- 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/skip-tests-requiring-network-access.patch
   1969-12-31 19:00:00.0 -0500
+++ 
golang-github-go-ping-ping-0+git20201106.b6486c6/debian/patches/skip-tests-requiring-network-access.patch
   2021-02-20 23:05:17.0 -0500
@@ -0,0 +1,18 @@
+--- a/ping_test.go
 b/ping_test.go
+@@ -227,6 +227,7 @@
+ }
+ 
+ func TestNewPingerValid(t *testing.T) {
++  t.Skip("Requires network access")
+   p := New("www.google.com")
+   err := p.Resolve()
+   AssertNoError(t, err)
+@@ -344,6 +345,7 @@
+ }
+ 
+ func TestSetIPAddr(t *testing.T) {
++  t.Skip("Requires network access")
+   googleaddr, err := net.ResolveIPAddr("ip", "www.google.com")
+   if err != nil {
+   t.Fatal("Can't resolve www.google.com, can't run tests")

Bug#982709: marked as done (direnv: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 03:33:31 +
with message-id 
and subject line Bug#982709: fixed in direnv 2.25.2-2
has caused the Debian Bug report #982709,
regarding direnv: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: direnv
Version: 2.25.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> shellcheck stdlib.sh
> ./test/stdlib.bash
> --- find_up
> --- source_up
> direnv: loading /<>/test/.envrc
> --- direnv_apply_dump
> --- PATH_rm
> --- path_rm
> --- expand_path
> --- semver_search
> --- use_julia
> --- source_env_if_exists
> direnv: loading existing_file
> OK (5 tests)
> OK
> go test -v ./...
> === RUN   TestEnvDiff
> --- PASS: TestEnvDiff (0.00s)
> === RUN   TestEnvDiffEmptyValue
> --- PASS: TestEnvDiffEmptyValue (0.00s)
> === RUN   TestIgnoredEnv
> --- PASS: TestIgnoredEnv (0.00s)
> === RUN   TestEnv
> --- PASS: TestEnv (0.00s)
> === RUN   TestUpdate
> --- PASS: TestUpdate (0.00s)
> === RUN   TestFTJsons
> --- PASS: TestFTJsons (0.00s)
> === RUN   TestRoundTrip
> --- PASS: TestRoundTrip (0.00s)
> === RUN   TestCanonicalAdds
> --- PASS: TestCanonicalAdds (0.00s)
> === RUN   TestCheckPasses
> --- PASS: TestCheckPasses (0.00s)
> === RUN   TestCheckStale
> --- PASS: TestCheckStale (0.00s)
> === RUN   TestCheckAppeared
> --- PASS: TestCheckAppeared (0.00s)
> === RUN   TestCheckGone
> --- PASS: TestCheckGone (0.00s)
> === RUN   TestSomething
> --- PASS: TestSomething (0.00s)
> === RUN   TestRootDir
> --- PASS: TestRootDir (0.00s)
> === RUN   TestBashEscape
> --- PASS: TestBashEscape (0.00s)
> === RUN   TestShellDetection
> --- PASS: TestShellDetection (0.00s)
> PASS
> okgithub.com/direnv/direnv0.005s
> ? github.com/direnv/direnv/gzenv  [no test files]
> ? github.com/direnv/direnv/script [no test files]
> ? github.com/direnv/direnv/script/issue-command   [no test files]
> ? github.com/direnv/direnv/script/release-changelog   [no test files]
> === RUN   TestSRIHasher
> --- PASS: TestSRIHasher (0.00s)
> PASS
> okgithub.com/direnv/direnv/sri0.009s
> ? github.com/direnv/direnv/xdg[no test files]
> bash ./test/direnv-test.bash
> direnv: loading /<>/test/.envrc
> ## Testing base ##
> Setting up
> direnv: loading /<>/test/scenarios/base/.envrc
> direnv: export +HELLO
> Reloading (should be no-op)
> Updating envrc and reloading (should reload)
> direnv: loading /<>/test/scenarios/base/.envrc
> direnv: export +HELLO
> Leaving dir (should clear env set by dir's envrc)
> direnv: loading /<>/test/.envrc
> 
> direnv: unloading
> ## Testing inherit ##
> direnv: loading /<>/test/scenarios/inherit/.envrc
> direnv: loading ../inherited/.envrc
> world
> direnv: export +HELLO
> HELLO should be world: world
> direnv: loading /<>/test/scenarios/inherit/.envrc
> direnv: loading ../inherited/.envrc
> goodbye
> direnv: export +HELLO
> direnv: unloading
> ## Testing ruby-layout ##
> direnv: loading /<>/test/scenarios/ruby-layout/.envrc
> direnv: export +BUNDLE_BIN +GEM_HOME ~PATH
> direnv: unloading
> ## Testing space dir ##
> direnv: loading /<>/test/scenarios/space dir/.envrc
> direnv: export +SPACE_DIR ~PATH
> direnv: unloading
> ## Testing child-env ##
> direnv: loading /<>/test/scenarios/child-env/.envrc
> direnv: export +CHILD +PARENT_POST +PARENT_PRE
> direnv: unloading
> ## Testing special-vars ##
> direnv: loading /<>/test/scenarios/special-vars/.envrc
> direnv: unloading
> ## Testing dump ##
> direnv: loading /<>/test/scenarios/dump/.envrc
> to stdout
> to stderr
> direnv: direnv_load would previously hang if DIRENV_DUMP_FILE_PATH was not 
> opened.
> direnv: Expect the following to emit an error (which we suppress).
> direnv: As long as it doesn't hang, we're okay.
> tput: No value for $TERM and no -T specified
> tput: No value for $TERM and no -T specified
> direnv: Environment not dumped; did you invoke 'direnv dump'?
> direnv: export +LESSOPEN +LS_COLORS +THREE_BACKSLASHES
> direnv: unloading
> ## Testing empty-var ##
> direnv: loading /<>/test/scenarios/empty-var/.envrc
> direnv: export +FOO
> direnv: unloading
> ## Testing empty-var-unset ##
> direnv: loading /<>/test/scenarios/empty-var-unset/.envrc
> direnv: export -FOO
> direnv: unloading
> 

Bug#965181: marked as done (goval-dictionary: B-D on removed golang-github-dgrijalva-jwt-go-v3-dev)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2021 00:33:36 +
with message-id 
and subject line Bug#965181: fixed in goval-dictionary 0.2.0-2
has caused the Debian Bug report #965181,
regarding goval-dictionary: B-D on removed golang-github-dgrijalva-jwt-go-v3-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
965181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: goval-dictionary
Version: 0.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

goval-dictionary/experimental cannot be built any more since its
build-dependency golang-github-dgrijalva-jwt-go-v3-dev is gone.

Andreas
--- End Message ---
--- Begin Message ---
Source: goval-dictionary
Source-Version: 0.2.0-2
Done: Debian Janitor 

We believe that the bug you reported is fixed in the latest version of
goval-dictionary, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Debian Janitor  (supplier of updated goval-dictionary 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 01:55:02 +
Source: goval-dictionary
Architecture: source
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Debian Janitor 
Closes: 965181
Changes:
 goval-dictionary (0.2.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Aloïs Micard ]
   * Fix wrong B-D (Closes: #965181).
   * Bump debhelper from old 9 to 13.
   * Bump S-V to 4.5.1.
   * Add Rules-Require-Root.
Checksums-Sha1:
 c4bfdbe632dce5d71a7e49ce0c29668d58e38283 3320 goval-dictionary_0.2.0-2.dsc
 7d5098bc8fff1dadabaf35e3742a3010c73b43bf 4324 
goval-dictionary_0.2.0-2.debian.tar.xz
 951c442d4e111b75bd908cc3df0bafb03c01a560 8108 
goval-dictionary_0.2.0-2_source.buildinfo
Checksums-Sha256:
 7a11696215a5ea5056ed47f0e8f19b3e039d4ac7b4306c9ffd8a52415a85e4a2 3320 
goval-dictionary_0.2.0-2.dsc
 48c3f1737219afe5e7f571a2eea0bd394c447bd7d5286b1181c3fbfb59e92bba 4324 
goval-dictionary_0.2.0-2.debian.tar.xz
 fed5e5cca59b31b1b5e076967f31bf404b5b3e2da1c688b04e872129cf35d2a7 8108 
goval-dictionary_0.2.0-2_source.buildinfo
Files:
 2f8b6571ef60032832f10b691c09923f 3320 devel optional 
goval-dictionary_0.2.0-2.dsc
 17f043f24c664dab3a9668e130c99c2a 4324 devel optional 
goval-dictionary_0.2.0-2.debian.tar.xz
 d32d3cc205ed693d08580c0e142723b3 8108 devel optional 
goval-dictionary_0.2.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAmAxpBMACgkQjysRPGU1
xaes2RAAhYqXdLKLv0D1Qx28Q7hAcv/Jd1GHu+pY6PJV+F/u26kwxSsu52z+e9SO
NAuUFumOwxJGtJ4Z5dJLETUja6kQ1q4ThWjwIoLX8JB5QfnQACZzwswwT2X06tXa
JvL6Ks7DTpaVeonE43luPukHEZy2ICc0QH80T3YcO0fyjbe2dfsaBJ0Z5zT8VO4r
0JnTpgJfImDiBbGwF8/ZKNiKUdeaBIM0SSDdDlhvZRzHi0x0tOnyR+R5YMS8iXc0
azqigNy0qbfNCKNG/HeE6ROXe5I4cK0ZJ4LT4JS1MYC0/Tz8p7wwBUAcc9i0MUiM
fAm47S/NDtLA+7VuV+ipswYO8mD2gQeYa/MMy+dltwoJ80VFJ+ZjMVvivkav5wwx
ArZySjoe9mnBheyqvKt9HuZ+SGTE7mAZ4aVfukoLFwsYt2xbE//Xv2wFwTSI5U9n
b4cNwUxjyGMDnkFhZ7P+8B5NSH03etfXR04RwO3FlGSo9wPBCOnKCX+2jVE4Dg/m
lGYK0c3paha/L5KqSH3kupbZBu0BURyKLFWpHblG5CVaizKvauuGsG0nBQgG1eu4
GeoO8pSsWJ4U378vaXIBwL5ob1mFrFre0AuSSxPX4ey+jPO44uNsrpCK4OAJBgR+
9wFuX4azOtDFb3QGMeX2NtsCz5MuPMzZ6w6bZ3mmNiN0ly9OF4M=
=I1n8
-END PGP SIGNATURE End Message ---

Bug#981612: epoptes-client: socat[1483] E Failed to set SNI host ""

[Vagrant Cascadian]

Control: found 981612 21.01-1
Control: notfound 981612 1.0.1-2

Marking as notfound for the version in buster, as buster does not have
the socat versions (1.7.4+) that triggers the issue.

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Re: Bug#981612: epoptes-client: socat[1483] E Failed to set SNI host ""

[Debian Bug Tracking System]

Processing control commands:

> found 981612 21.01-1
Bug #981612 {Done: Vagrant Cascadian } [epoptes-client] 
epoptes-client: socat[1483] E Failed to set SNI host ""
Marked as found in versions epoptes/21.01-1.
> notfound 981612 1.0.1-2
Bug #981612 {Done: Vagrant Cascadian } [epoptes-client] 
epoptes-client: socat[1483] E Failed to set SNI host ""
Ignoring request to alter found versions of bug #981612 to the same values 
previously set

-- 
981612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 940821 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 940821 important
Bug #940821 [src:linux] linux-image-5.2.0-2-amd64: file cache corruption with 
nfs4
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
940821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#940821: NFS Caching broken in 4.19.37

[Chuck Lever]

> On Feb 20, 2021, at 3:13 PM, Anton Ivanov  
> wrote:
> 
> On 20/02/2021 20:04, Salvatore Bonaccorso wrote:
>> Hi,
>> 
>> On Mon, Jul 08, 2019 at 07:19:54PM +0100, Anton Ivanov wrote:
>>> Hi list,
>>> 
>>> NFS caching appears broken in 4.19.37.
>>> 
>>> The more cores/threads the easier to reproduce. Tested with identical
>>> results on Ryzen 1600 and 1600X.
>>> 
>>> 1. Mount an openwrt build tree over NFS v4
>>> 2. Run make -j `cat /proc/cpuinfo | grep vendor | wc -l` ; make clean in a
>>> loop
>>> 3. Result after 3-4 iterations:
>>> 
>>> State on the client
>>> 
>>> ls -laF 
>>> /var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
>>> 
>>> total 8
>>> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
>>> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
>>> 
>>> State as seen on the server (mounted via nfs from localhost):
>>> 
>>> ls -laF 
>>> /var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
>>> total 12
>>> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
>>> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
>>> -rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h
>>> 
>>> Actual state on the filesystem:
>>> 
>>> ls -laF 
>>> /exports/work/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
>>> total 12
>>> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
>>> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
>>> -rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h
>>> 
>>> So the client has quite clearly lost the plot. Telling it to drop caches and
>>> re-reading the directory shows the file present.
>>> 
>>> It is possible to reproduce this using a linux kernel tree too, just takes
>>> much more iterations - 10+ at least.
>>> 
>>> Both client and server run 4.19.37 from Debian buster. This is filed as
>>> debian bug 931500. I originally thought it to be autofs related, but IMHO it
>>> is actually something fundamentally broken in nfs caching resulting in cache
>>> corruption.
>> According to the reporter downstream in Debian, at
>> https://bugs.debian.org/940821#26 thi seem still reproducible with
>> more recent kernels than the initial reported. Is there anything Anton
>> can provide to try to track down the issue?
>> 
>> Anton, can you reproduce with current stable series?
> 
> 100% reproducible with any kernel from 4.9 to 5.4, stable or backports. It 
> may exist in earlier versions, but I do not have a machine with anything 
> before 4.9 to test at present.

Confirming you are varying client-side kernels. Should the Linux
NFS client maintainers be Cc'd?


> From 1-2 make clean && make  cycles to one afternoon depending on the number 
> of machine cores. More cores/threads the faster it does it.
> 
> I tried playing with protocol minor versions, caching options, etc - it is 
> still reproducible for any nfs4 settings as long as there is client side 
> caching of metadata.
> 
> A.
> 
>> 
>> Regards,
>> Salvatore
>> 
> 
> -- 
> Anton R. Ivanov
> Cambridgegreys Limited. Registered in England. Company Number 10273661
> https://www.cambridgegreys.com/

--
Chuck Lever

Bug#940821: NFS Caching broken in 4.19.37

[Anton Ivanov]

On 20/02/2021 20:04, Salvatore Bonaccorso wrote:

Hi,

On Mon, Jul 08, 2019 at 07:19:54PM +0100, Anton Ivanov wrote:

Hi list,

NFS caching appears broken in 4.19.37.

The more cores/threads the easier to reproduce. Tested with identical
results on Ryzen 1600 and 1600X.

1. Mount an openwrt build tree over NFS v4
2. Run make -j `cat /proc/cpuinfo | grep vendor | wc -l` ; make clean in a
loop
3. Result after 3-4 iterations:

State on the client

ls -laF 
/var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm

total 8
drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../

State as seen on the server (mounted via nfs from localhost):

ls -laF 
/var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
total 12
drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
-rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h

Actual state on the filesystem:

ls -laF 
/exports/work/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
total 12
drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
-rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h

So the client has quite clearly lost the plot. Telling it to drop caches and
re-reading the directory shows the file present.

It is possible to reproduce this using a linux kernel tree too, just takes
much more iterations - 10+ at least.

Both client and server run 4.19.37 from Debian buster. This is filed as
debian bug 931500. I originally thought it to be autofs related, but IMHO it
is actually something fundamentally broken in nfs caching resulting in cache
corruption.

According to the reporter downstream in Debian, at
https://bugs.debian.org/940821#26 thi seem still reproducible with
more recent kernels than the initial reported. Is there anything Anton
can provide to try to track down the issue?

Anton, can you reproduce with current stable series?


100% reproducible with any kernel from 4.9 to 5.4, stable or backports. 
It may exist in earlier versions, but I do not have a machine with 
anything before 4.9 to test at present.


From 1-2 make clean && make  cycles to one afternoon depending on the 
number of machine cores. More cores/threads the faster it does it.


I tried playing with protocol minor versions, caching options, etc - it 
is still reproducible for any nfs4 settings as long as there is client 
side caching of metadata.


A.



Regards,
Salvatore



--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/

Bug#940821: NFS Caching broken in 4.19.37

[Salvatore Bonaccorso]

Hi,

On Mon, Jul 08, 2019 at 07:19:54PM +0100, Anton Ivanov wrote:
> Hi list,
> 
> NFS caching appears broken in 4.19.37.
> 
> The more cores/threads the easier to reproduce. Tested with identical
> results on Ryzen 1600 and 1600X.
> 
> 1. Mount an openwrt build tree over NFS v4
> 2. Run make -j `cat /proc/cpuinfo | grep vendor | wc -l` ; make clean in a
> loop
> 3. Result after 3-4 iterations:
> 
> State on the client
> 
> ls -laF 
> /var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
> 
> total 8
> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
> 
> State as seen on the server (mounted via nfs from localhost):
> 
> ls -laF 
> /var/autofs/local/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
> total 12
> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
> -rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h
> 
> Actual state on the filesystem:
> 
> ls -laF 
> /exports/work/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
> total 12
> drwxr-xr-x 2 anivanov anivanov 4096 Jul  8 11:40 ./
> drwxr-xr-x 3 anivanov anivanov 4096 Jul  8 11:40 ../
> -rw-r--r-- 1 anivanov anivanov   32 Jul  8 11:40 ipcbuf.h
> 
> So the client has quite clearly lost the plot. Telling it to drop caches and
> re-reading the directory shows the file present.
> 
> It is possible to reproduce this using a linux kernel tree too, just takes
> much more iterations - 10+ at least.
> 
> Both client and server run 4.19.37 from Debian buster. This is filed as
> debian bug 931500. I originally thought it to be autofs related, but IMHO it
> is actually something fundamentally broken in nfs caching resulting in cache
> corruption.

According to the reporter downstream in Debian, at
https://bugs.debian.org/940821#26 thi seem still reproducible with
more recent kernels than the initial reported. Is there anything Anton
can provide to try to track down the issue?

Anton, can you reproduce with current stable series?

Regards,
Salvatore

Processed: Re: Bug#940821: closed by Bastian Blank (No response by submitter)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #940821 {Done: Bastian Blank } [src:linux] 
linux-image-5.2.0-2-amd64: file cache corruption with nfs4
Bug reopened
Ignoring request to alter fixed versions of bug #940821 to the same values 
previously set

-- 
940821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#940821: closed by Bastian Blank (No response by submitter)

[Salvatore Bonaccorso]

Control: reopen -1

Hi Anton,

On Sat, Feb 20, 2021 at 12:59:17PM +, Anton Ivanov wrote:
> On 20/02/2021 10:33, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the src:linux package:
> > 
> > #940821: linux-image-5.2.0-2-amd64: file cache corruption with nfs4
> > 
> > It has been closed by Bastian Blank .
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Bastian Blank 
> >  by
> > replying to this email.
> > 
> > 
> I missed the question. Probably hit the spam bucket for some reason.
> 
> I am able to reproduce it with more recent versions as well.
> 
> The most recent one I have around is 5.4.0-0.bpo.2-amd64
> 
> Still reproducible 100% - just tested it.
> 
> It is trivial to reproduce if anyone actually bothers to do so. Just grab a
> big enough tree where make runs truly in parallel - openwrt is best, but
> even the Linux kernel does the job.
> 
> Mount it via nfs4 from another server (it will work even locally, but takes
> longer to reproduce - may take a whole afternoon)
> 
> Run while make -j 12 clean && make -j 12 ; do true ; done
> 
> Leave it to run. On 6 cores/12 threads it takes 2-3 builds of openwrt or ~
> 5-8 linux kernel builds to blow up. More cores - faster. Less cores slower.
> 
> I sent it to the mailing list too, but nobody could be bothered to even ask
> any questions.

Let's reopen then but can you try to followup with upstream? I think
that's the best place to handle the issue. 5.4.0-0.bpo.2-amd64 is in
meanwhile as well quite behind, can you still reproduce it with the
current stable series? Most ucrrent in backports is 5.10.13 based.

Regards,
Salvatore

Bug#983091: xapian-core FTBFS on i386: test failure

[Olly Betts]

On Fri, Feb 19, 2021 at 11:36:46AM +0200, Adrian Bunk wrote:
> With the old debian/rules the test was only run with
> the SSE build.
> 
> If exact results are required and the x87 excess precision is unwanted,
> test with the non-SSE build can be fixed with:
> 
> --- debian/rules.old  2021-02-18 15:12:59.097207579 +
> +++ debian/rules  2021-02-18 15:13:51.537168694 +
> @@ -51,6 +51,10 @@
>  
>  export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
>  
> +ifneq (,$(filter $(DEB_HOST_ARCH), i386 m68k))
> +export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store
> +endif
> +
>  # For i386 and *-i386.
>  ifeq ($(patsubst %-i386,i386,$(DEB_HOST_ARCH)), i386)
>  XAPIAN_BUILD_SSE := 1

Thanks for the report, and for tracking this down to excess precision.

The upstream code is meant to address excess precision in the small
number of places where it matters but I guess there's a newer instance
that hasn't been caught before, or a newer testcase uncovers an existing
problem (or perhaps newer GCC optimises differently and that's uncovered
this.)

The SSE2 build will get used by more i386 systems, so the overhead
from -ffloat-store won't affect many there at least, but it is a bit of
heavy hammer.  I'll take a look and see if I can fix this in a more
targetted way.  If not applying this for bullseye seems reasonable.
Or we could change the tests back to run just for the SSE2 build for
now - in real world use exact results are rarely a requirement, but
performance often is.

Cheers,
Olly

Bug#982725: marked as done (massxpert: FTBFS: [ERROR] LazyFont - Failed to read font file /usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 19:34:45 +
with message-id 
and subject line Bug#982725: fixed in massxpert 6.0.2-1
has caused the Debian Bug report #982725,
regarding massxpert: FTBFS: [ERROR] LazyFont - Failed to read font file 
/usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf 
java.io.FileNotFoundException: 
/usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf (No 
such file or directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: massxpert
Version: 6.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[6]: Entering directory '/<>/doc/user-manual'
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> msXpertSuite
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> msXpertSuite
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> massxpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertMiner
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertMiner
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> Updating makefiles
> Updating goal targets
>  File 'pdf' does not exist.
>File 
> '/<>/doc/user-manual/build/massxpert-user-manual/massxpert-user-manual_color_en.pdf'
>  does not exist.
>  File 
> '/<>/doc/user-manual/build/.tmp/massxpert-user-manual-fop_color_en.fo'
>  does not exist.
>File 
> '/<>/doc/user-manual/build/.profiled/noprofile/MAIN-massxpert-user-manual.xml'
>  does not exist.
>  File '/<>/doc/user-manual/build/.profiled/noprofile' 
> does not exist.
> Must remake target 
> '/<>/doc/user-manual/build/.profiled/noprofile'.
> mkdir -p /<>/doc/user-manual/build/.profiled/noprofile
> Successfully remade target file 
> '/<>/doc/user-manual/build/.profiled/noprofile'.
>   Must remake target 
> '/<>/doc/user-manual/build/.profiled/noprofile/MAIN-massxpert-user-manual.xml'.
> 

Bug#972936: marked as done (libgcc-s1 needs Breaks: libgcc1 (<< 1:10))

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 19:34:30 +
with message-id 
and subject line Bug#972936: fixed in gcc-10 10.2.1-20
has caused the Debian Bug report #972936,
regarding libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc-s1
Version: 10.2.0-15
Severity: grave

On a buster system, with unstable pinned to low priority:

# apt-get install libgcc-s1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  gcc-10-base
The following NEW packages will be installed:
  gcc-10-base libgcc-s1
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/241 kB of archives.
After this operation, 384 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package gcc-10-base:amd64.
(Reading database ... 508501 files and directories currently installed.)
Preparing to unpack .../gcc-10-base_10.2.0-15_amd64.deb ...
Unpacking gcc-10-base:amd64 (10.2.0-15) ...
Selecting previously unselected package libgcc-s1:amd64.
Preparing to unpack .../libgcc-s1_10.2.0-15_amd64.deb ...
Unpacking libgcc-s1:amd64 (10.2.0-15) ...
Replacing files in old package libgcc1:amd64 (1:8.3.0-6) ...
Setting up gcc-10-base:amd64 (10.2.0-15) ...
Setting up libgcc-s1:amd64 (10.2.0-15) ...
Processing triggers for libc-bin (2.28-10) ...
# apt-get remove libgcc-s1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libgcc-s1
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 119 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 508502 files and directories currently installed.)
Removing libgcc-s1:amd64 (10.2.0-15) ...
Processing triggers for libc-bin (2.28-10) ...
# apt-get install libgcc-s1
apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open 
shared object file: No such file or directory
#


libgcc-s1 needs
  Breaks: libgcc1 (<< 1:10)
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10.2.1-20
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 20 Feb 2021 19:58:49 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-20
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 972936
Changes:
 gcc-10 (10.2.1-20) experimental; urgency=medium
 .
   * Update to git 20210220 from the gcc-10 branch.
 - Fix PR rtl-optimization/96015, PR debug/96997, PR c++/94034,
   PR c++/96905, PR c++/98326, PR c++/20408, PR c++/95888,
   PR fortran/99111, PR fortran/99043, PR fortran/98897, PR fortran/99060,
   PR libfortran/95647, PR libstdc++/99021.
   * Still build the lib*gccN compat packages for sid/bullseye. Note, this
 doesn't change anything for the upload to experimental. Closes: #972936.
Checksums-Sha1:
 b94cd144b1eed7fa3fddbe0b7c07b2589f6e2212 22051 gcc-10_10.2.1-20.dsc
 0334e45082776e9e4b448bef8e8d0a1fa6d60719 2409276 gcc-10_10.2.1-20.debian.tar.xz
 1014a284cacd0aa7b9ca88cc0826886246af619c 9811 gcc-10_10.2.1-20_source.buildinfo
Checksums-Sha256:
 aa8bb5d42db5a9b2b1b1d0ba3a899be5b968c0047d91a89b175c295152a40690 22051 
gcc-10_10.2.1-20.dsc
 540c46ebf716ec22446598aaf20dda80470270057612b31f53b6afb1d6916189 2409276 
gcc-10_10.2.1-20.debian.tar.xz
 2a4b68ff9260eacb61dd30797895363222d25a3b675be08194c9adbb57858235 9811 
gcc-10_10.2.1-20_source.buildinfo
Files:
 a67d5593e5cdef9ca51954801700f49c 22051 devel optional gcc-10_10.2.1-20.dsc
 ccb50b85ac41c10e3dbf018fa55b8d7c 2409276 devel optional 
gcc-10_10.2.1-20.d

Processed: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #949519 [sudo-ldap] sudo-ldap: Fails to connect to LDAP : 
"ldap_sasl_bind_s(): Can't contact LDAP server"
Added tag(s) unreproducible and moreinfo.

-- 
949519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

[Dennis Filder]

Control: tag -1 + moreinfo unreproducible

Jean-Christophe, are you still interested in figuring this out?  If so
you need to provide more information.  You also don't say what else
you have tried to investigate this.

I tried reproducing your observed behaviour, but it doesn't manifest
here unless I put "TLS_REQCERT allow" into my normal user's ~/.ldaprc
file (which is not a bug, but a misconfiguration).

"ldap_sasl_bind_s(): Can't contact LDAP server" is really just a
generic TLS error which could have a million different causes.  Some
ideas what could be going on:

* The certificates may have been generated with outdated TLS
  parameters or the server is running outdated configuration options.
  I recall that during the move to buster OpenSSL changed its default
  settings for what versions of TLS it still allows (TLS_CIPHER_SUITE,
  TLS_PROTOCOL_MIN).  Give us the output of:

  openssl s_client -debug -connect server2.mydomain.com:636 -verify 255 
 /tmp/sudo-l-strace.gz

  Also to turn off any initialization mechanisms run your ldapsearch
  commands like this:

  LDAPNOINIT=1 ldapsearch -x -H ...

  Tell us if this changes anything.

Until you can give us something that clearly points to the code of
sudo-ldap doing something it shouldn't we have to assume that this is
due to a misconfiguration.


Regards,
Dennis.

Bug#980607: netcfg: FTBFS patches

[Bart Martens]

Dennis, Cyril,

Downloading the patches from the bts works fine. The patches can be applied
with ignoring whitespaces (option -l). The patches solve the FTBFS.

  |  (sid)bartm@carolus:~/src/sponsoring/netcfg-1.169$ patch -l -p1 < 
../netcfg_1.169-fix-CheckAPI.patch 
  |  patching file test/test_nc_v6_interface_configured.c
  |  patching file test/test_netcfg_gateway_reachable.c
  |  patching file test/test_inet_ptom.c
  |  patching file test/test_netcfg_network_address.c
  |  patching file test/test_inet_mton.c
  |  patching file test/test_netcfg_parse_cidr_address.c
  |  patching file test/srunner.c
  |  (sid)bartm@carolus:~/src/sponsoring/netcfg-1.169$ patch -l -p1 < 
../netcfg_1.169-fix-strncpy.patch 
  |  patching file autoconfig.c
  |  patching file dhcp.c
  |  patching file netcfg-common.c

Cheers,

Bart

Bug#974828: printer-driver-hpcups: bug of printer-driver-hpcups still present on debian sid kernel 5.10.3

[alain]

Package: printer-driver-hpcups
Version: 3.20.11+dfsg0-3
Followup-For: Bug #974828
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr

alain@sid:~/Téléchargements$ apt policy printer-driver-hpcups hplip
printer-driver-hpcups:
  Installé : 3.20.11+dfsg0-3
  Candidat : 3.20.11+dfsg0-3
 Table de version :
 *** 3.20.11+dfsg0-3 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 3.20.11+dfsg0-2 100
100 http://deb.debian.org/debian testing/main amd64 Packages
 3.18.12+dfsg0-2 100
100 http://deb.debian.org/debian stable/main amd64 Packages
hplip:
  Installé : 3.20.11+dfsg0-3
  Candidat : 3.20.11+dfsg0-3
 Table de version :
 *** 3.20.11+dfsg0-3 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 3.20.11+dfsg0-2 100
100 http://deb.debian.org/debian testing/main amd64 Packages
 3.18.12+dfsg0-2 100
100 http://deb.debian.org/debian stable/main amd64 Packages

alain@sid:~/Téléchargements$ hp-check
Saving output in log file: /home/alain/Téléchargements/hp-check.log

HP Linux Imaging and Printing System (ver. 3.20.11)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling
the HPLIP supplied tarball (.tar.gz or
.run) to determine if the proper dependencies are installed to successfully
compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an
already built HPLIP supplied tarball has the proper dependencies installed to
successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both
compile- and run-time dependencies).

Check types:
a. EXTERNALDEP - External Dependencies
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

-Gtk-Message: 19:48:07.916: Failed to load module "canberra-gtk-module"
warning: debian-unstable version is not supported. Using debian-10.6 versions
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux
 Host: sid
 Proc: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux
 Distribution: debian unstable
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.20.11
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for debian
distro  unstable version

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.20.11

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.20.11
restricted-build=no
ui-toolkit=qt5
qt3=no
qt4=no
qt5=yes
policy-kit=yes
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=no
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[commands]
scan = /usr/bin/simple-scan %SANE_URI%

[fax]
email_address =
voice_phone =

[last_used]
device_uri = escl:http://127.0.0.1:6
printer_name =
working_dir = .

[polling]
device_list =
enable = false
interval = 5

[refresh]
enable = false
rate = 30
type = 1

[settings]
systray_messages = 0
systray_visible = 0

[upgrade]
last_upgraded_time = 1613842662
notify_upgrade = true
pending_upgrade_time = 0

[installation]
date_time = 02/20/21 19:48:08
version = 3.20.11





-
| External Dependencies |
-

 error: cups  CUPS - Common Unix Printing System
REQUIRED1.1 -

Bug#982973: marked as done (qtmultimedia-opensource-src: FTBFS in test: tst_QVideoFrame::image(64x64 NV12) Received a fatal error)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 18:05:08 +
with message-id 
and subject line Bug#982973: fixed in qtmultimedia-opensource-src 5.15.2-3
has caused the Debian Bug report #982973,
regarding qtmultimedia-opensource-src: FTBFS in test: 
tst_QVideoFrame::image(64x64 NV12) Received a fatal error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtmultimedia-opensource-src
Version: 5.15.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

During a rebuild of the package on a Bullseye derivative, it was seen
that the package fails to build from source. It fails in one of the
tests, for which the failure snippet is mentioned below. Please also
note that the same failure (and full build log) is also available on the
Reproducible Builds.

```
[ 1877s] Config: Using QtTest library 5.15.2, Qt 5.15.2 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.1 
20210110), debian unknown
[ 1877s] PASS   : tst_QVideoFrame::initTestCase()
[ 1877s] PASS   : tst_QVideoFrame::create(64x64 ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::create(32x256 YUV420P)
[ 1877s] PASS   : tst_QVideoFrame::createInvalid(64x64 ARGB32 0 size)
[ 1877s] PASS   : tst_QVideoFrame::createInvalid(32x256 YUV420P negative size)
[ 1877s] PASS   : tst_QVideoFrame::createFromBuffer(64x64 ARGB32 no handle)
[ 1877s] PASS   : tst_QVideoFrame::createFromBuffer(64x64 ARGB32 gl handle)
[ 1877s] PASS   : tst_QVideoFrame::createFromBuffer(64x64 ARGB32 user handle)
[ 1877s] PASS   : tst_QVideoFrame::createFromImage(64x64 RGB32)
[ 1877s] PASS   : tst_QVideoFrame::createFromImage(12x45 RGB16)
[ 1877s] PASS   : tst_QVideoFrame::createFromImage(19x46 ARGB32_Premultiplied)
[ 1877s] PASS   : tst_QVideoFrame::createFromIncompatibleImage()
[ 1877s] PASS   : tst_QVideoFrame::createNull()
[ 1877s] PASS   : tst_QVideoFrame::destructor()
[ 1877s] PASS   : tst_QVideoFrame::copy(64x64 ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::copy(64x64 ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::copy(32x256 YUV420P)
[ 1877s] PASS   : tst_QVideoFrame::copy(1052x756 ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::copy(32x256 YUV420P)
[ 1877s] PASS   : tst_QVideoFrame::assign(64x64 ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::assign(32x256 YUV420P)
[ 1877s] PASS   : tst_QVideoFrame::map(read-only)
[ 1877s] PASS   : tst_QVideoFrame::map(write-only)
[ 1877s] PASS   : tst_QVideoFrame::map(read-write)
[ 1877s] PASS   : tst_QVideoFrame::mapImage(read-only)
[ 1877s] PASS   : tst_QVideoFrame::mapImage(write-only)
[ 1877s] PASS   : tst_QVideoFrame::mapImage(read-write)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Planar)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_YUV420P)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_YV12)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_NV12)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_NV21)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_IMC2)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_IMC4)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_IMC1)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_IMC3)
[ 1877s] PASS   : tst_QVideoFrame::mapPlanes(Format_ARGB32)
[ 1877s] PASS   : tst_QVideoFrame::imageDetach()
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_RGB32 | 
QVideoFrame::Format_RGB32)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_ARGB32 | 
QVideoFrame::Format_ARGB32)
[ 1877s] PASS   : 
tst_QVideoFrame::formatConversion(QImage::Format_ARGB32_Premultiplied | 
QVideoFrame::Format_ARGB32_Premultiplied)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_RGB16 | 
QVideoFrame::Format_RGB565)
[ 1877s] PASS   : 
tst_QVideoFrame::formatConversion(QImage::Format_ARGB8565_Premultiplied | 
QVideoFrame::Format_ARGB8565_Premultiplied)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_RGB555 | 
QVideoFrame::Format_RGB555)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_RGB888 | 
QVideoFrame::Format_RGB24)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_MonoLSB)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_Indexed8)
[ 1877s] PASS   : 
tst_QVideoFrame::formatConversion(QImage::Format_ARGB_Premultiplied)
[ 1877s] PASS   : 
tst_QVideoFrame::formatConversion(QImage::Format_ARGB8555_Premultiplied)
[ 1877s] PASS   : tst_QVideoFrame::formatConversion(QImage::Format_RGB666)
[ 1877s] 

Bug#983183: libpam-script: Wrong path for pam_script.so

[Christian Meyer]

Package: libpam-script
Version: 1.1.9-4+b1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: c2h...@web.de

Dear Maintainer,

after reinstalling my (FAI-driven) installation with bullseye (using stretch 
before and ignoring buster),
I found that pam-script doesn't work anymore.
/var/log/auth.log claims that:
PAM unable to dlopen(pam_script.so): 
/lib/x86_64-linux-gnu/security/pam_script.so: Couldn't open Shared-Object-file: 
File or directory not found
PAM adding faulty module: pam_script.so

Your package contains the file, but it lives in a wrong directory (and for me 
there is no other file in there):
/lib/security/pam_script.so

all other pam_*.so files live in /lib/x86_64-linux-gnu/security/
and a simple
ln -s /lib/security/pam_script.so /lib/x86_64-linux-gnu/security/pam_script.so
made pam_script work again.

I'm not knowing the details of PAM and pam_script, but I think simply moving 
the directory should be the right solution.
Please fix it in the remaining bullseye-freeze. 

Thank you
Christian Meyer


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

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

Versions of packages libpam-script depends on:
ii  libc6 2.31-9
ii  libpam0g  1.4.0-4

libpam-script recommends no packages.

libpam-script suggests no packages.

-- no debconf information

Processed (with 2 errors): merge some openjdk-11 issues

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 965965 openjdk-11-jre-headless]
Unknown command or malformed arguments to command.
> forcemerge 960153 965965
Bug #960153 {Done: Matthias Klose } [openjdk-11-jre-headless] 
C2 compiler gets SIGILL/ILL_ILLOPC
Unable to merge bugs because:
package of #965965 is 'openjdk-11-jdk-headless' not 'openjdk-11-jre-headless'
Failed to forcibly merge 960153: Did not alter merged bugs.

> reassign 969038 src:openjdk-11
Bug #969038 [openjdk-11-jre-headless] openjdk-11-jre-headless: manpages 
describe JDK8, last updated in 2015
Bug reassigned from package 'openjdk-11-jre-headless' to 'src:openjdk-11'.
No longer marked as found in versions openjdk-11/11.0.9.1+1-1 and 
openjdk-11/11.0.8+10-1~deb10u1.
Ignoring request to alter fixed versions of bug #969038 to the same values 
previously set
> reassign 920903 src:openjdk-11
Bug #920903 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: ships 
documentation for JDK 8, not JDK 11
Bug reassigned from package 'openjdk-11-jdk-headless' to 'src:openjdk-11'.
No longer marked as found in versions openjdk-11/11.0.2+7-1.
Ignoring request to alter fixed versions of bug #920903 to the same values 
previously set
> forcemerge 920903 969038
Bug #920903 [src:openjdk-11] openjdk-11-jdk-headless: ships documentation for 
JDK 8, not JDK 11
Bug #920903 [src:openjdk-11] openjdk-11-jdk-headless: ships documentation for 
JDK 8, not JDK 11
Added tag(s) upstream.
Bug #969038 [src:openjdk-11] openjdk-11-jre-headless: manpages describe JDK8, 
last updated in 2015
Set Bug forwarded-to-address to 
'https://bugs.openjdk.java.net/browse/JDK-8251572'.
Severity set to 'important' from 'normal'
Merged 920903 969038
> merge 973763 966508
Bug #973763 [openjdk-11-jre] fatal error (SIGSEGV) while running 
jitsi-videobridge2
Bug #966508 [openjdk-11-jre] fatal error (SIGSEGV) while running 
jitsi-videobridge2
Marked as found in versions openjdk-11/11.0.9+11-1~deb10u1.
Bug #973763 [openjdk-11-jre] fatal error (SIGSEGV) while running 
jitsi-videobridge2
Marked as found in versions openjdk-11/11.0.7+9-1.
Merged 966508 973763
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
920903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920903
960153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960153
965965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965965
966508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966508
969038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969038
973763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982882: marked as pending in qtbase-opensource-src

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #982882 in qtbase-opensource-src reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/0ac20d7b3b7f5b45841c28bf404f6354a4c4e2e3


Backport patch to fix allocated memory of QByteArray returned by 
QIODevice::readLine.

Closes: #982882.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982882

Processed: Bug#982882 marked as pending in qtbase-opensource-src

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982882 [libqt5core5a] lconvert uses huge amounts of RAM
Added tag(s) pending.

-- 
982882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982718: marked as done (msxpertsuite: FTBFS: [ERROR] LazyFont - Failed to read font file /usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 17:04:24 +
with message-id 
and subject line Bug#982718: fixed in msxpertsuite 5.8.9-1
has caused the Debian Bug report #982718,
regarding msxpertsuite: FTBFS: [ERROR] LazyFont - Failed to read font file 
/usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf 
java.io.FileNotFoundException: 
/usr/share/texlive/texmf-dist/fonts/opentype/public/stix2-otf/STIX2Math.otf (No 
such file or directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msxpertsuite
Version: 5.8.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[6]: Entering directory '/<>/doc/user-manuals/massxpert'
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> msXpertSuite
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> msXpertSuite
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> massxpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertMiner
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> mineXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertMiner
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> namespace warning : Namespace default prefix was not found
> massXpert
> ^
> namespace warning : Namespace default prefix was not found
> XpertDef
> ^
> namespace warning : Namespace default prefix was not found
> XpertCalc
> ^
> namespace warning : Namespace default prefix was not found
> XpertEdit
> ^
> Updating makefiles
> Updating goal targets
>  File 'pdf' does not exist.
>File 
> '/<>/doc/user-manuals/massxpert/build/massxpert-user-manual/massxpert-user-manual_color_en.pdf'
>  does not exist.
>  File 
> '/<>/doc/user-manuals/massxpert/build/.tmp/massxpert-user-manual-fop_color_en.fo'
>  does not exist.
>File 
> '/<>/doc/user-manuals/massxpert/build/.profiled/noprofile/MAIN-massxpert-user-manual.xml'
>  does not exist.
>  File 
> '/<>/doc/user-manuals/massxpert/build/.profiled/noprofile' does 
> not exist.
> Must remake target 
> '/<>/doc/user-manuals/massxpert/build/.profiled/noprofile'.
> Successfully remade target file 
> '/<>/doc/user-manuals/massxpert/build/.profiled/noprofile'.
>   Must remake target 
> 

Bug#983144: marked as done (unknown-horizons: Crash with unexpected keyword argument 'encoding')

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 16:24:03 +
with message-id 
and subject line Bug#983144: fixed in unknown-horizons 2019.1-3
has caused the Debian Bug report #983144,
regarding unknown-horizons: Crash with unexpected keyword argument 'encoding'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unknown-horizons
Version: 2019.1-2
Severity: grave
Tags: a11y
Justification: renders package unusable

Hi,

I encountered a problem starting unknown-horizons. I installed from standard
debian testing repository and get the following error:

---
$ unknown-horizons --debug
Logging to b'/home/sal/.local/share/unknown-horizons/log/unknown-
horizons-2020-12-29_20-40-06.log' and /usr/share/unknown-horizons/fife.log
Python version: sys.version_info(major=3, minor=9, micro=1,
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
SYS.PATH: ['/usr/games', '/usr/lib/python39.zip', '/usr/lib/python3.9',
'/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages',
'/usr/lib/python3/dist-packages']
PATHSEP: ":" SEP: "/"
LD_LIBRARY_PATH: 
PATH:
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/var/lib/flatpak/exports/bin
PYTHONPATH 
Python version: sys.version_info(major=3, minor=9, micro=1,
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
Using fife version 0.4.2, at least 0.4.2 required
Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
main()
  File "/usr/games/unknown-horizons", line 122, in main
ret = horizons.main.start(options)
  File "/usr/lib/python3/dist-packages/horizons/main.py", line 113, in start
horizons.globals.fife = Fife()
  File "/usr/lib/python3/dist-packages/horizons/engine/engine.py", line 46, in
__init__
self._setting = Settings(PATHS.USER_CONFIG_FILE,
PATHS.SETTINGS_TEMPLATE_FILE)
  File "/usr/lib/python3/dist-packages/horizons/engine/settings.py", line 39,
in __init__
self._settings_serializer.load(settings_file)
  File "/usr/lib/python3/dist-
packages/fife/extensions/serializers/simplexml.py", line 132, in load
self._validateTree()
  File "/usr/lib/python3/dist-
packages/fife/extensions/serializers/simplexml.py", line 386, in _validateTree
for c in self._root_element.getchildren():
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute
'getchildren'

 Unknown Horizons has crashed.

We are very sorry for this and want to fix the underlying error.
In order to do this, we need the information from the logfile:
/home/sal/.local/share/unknown-horizons/log/unknown-
horizons-2020-12-29_20-40-06.log
Please give it to us via IRC or our forum, for both see http://unknown-
horizons.org .
---


I also attached the unknown-horizons log file.

If you need more information just get back on me.

Kind regards
Steffen



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

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

Versions of packages unknown-horizons depends on:
ii  python3 3.9.0-4
ii  python3-enet0.0~vcs.2017.05.26.git-2.2+b2
ii  python3-fife0.4.2-2+b3
ii  python3-future  0.18.2-5
ii  python3-yaml5.3.1-3+b1
ii  ttf-unifont 1:13.0.04-1

unknown-horizons recommends no packages.

unknown-horizons suggests no packages.

-- no debconf information

 Unknown Horizons has crashed.

We are very sorry for this and want to fix the underlying error.
In order to do this, we need the information from the logfile:
/home/sal/.local/share/unknown-horizons/log/unknown-horizons-2020-12-29_20-40-06.log
Please give it to us via IRC or our forum, for both see 
http://unknown-horizons.org .
: ":" SEP: "/"
LD_LIBRARY_PATH: 
PATH: 
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/var/lib/flatpak/exports/bin
PYTHONPATH 
Python version: sys.version_info(major=3, minor=9, micro=1, 
releaselevel='final', serial=0)
Platform: Linux-5.9.0-4-amd64-x86_64-with-glibc2.31
Using fife version 0.4.2, at least 0.4.2 required
Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
main()
  File "/usr/games/unknown-horizons", line 122, in main
ret = horizons.main.start(options)
  File 

Bug#982567: openms build-depends on removed package

[Filippo Rusconi]

Greetings, Andreas and Michael,

I hope you are doing fine.

On Fri, Feb 19, 2021 at 10:19:11PM +0100, Andreas Tille wrote:

Hi Filippo,

this is extremely unfortunate.  However, I guess the alternative would
have been to keep some RC buggy seqan-dev which would not have helped
openms as well.  I tried the same as Peter and replaced the
Build-Depends seqan-dev by libseqan2-dev.

I can confirm the observation from Peter about the missing header file.
I simply tried to comment those missing headers (next one is also
missing):


// #include 
// #include 

[...]

Thank you for your trials and explanations. I am no on vacation, which means
I'll finally find some time to try understand the implications of that SeqAn
upgrade.

I'll keep you posted with my findings.

Cheers,

Filippo


--

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

Processed: Re: Bug#982882: stellarium FTBFS on armel and mipsel

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libqt5core5a 5.15.2+dfsg-4
Bug #982882 [src:stellarium] stellarium FTBFS on armel and mipsel
Bug reassigned from package 'src:stellarium' to 'libqt5core5a'.
No longer marked as found in versions stellarium/0.20.4-1.
Ignoring request to alter fixed versions of bug #982882 to the same values 
previously set
Bug #982882 [libqt5core5a] stellarium FTBFS on armel and mipsel
Marked as found in versions qtbase-opensource-src/5.15.2+dfsg-4.
> retitle -1 lconvert uses huge amounts of RAM
Bug #982882 [libqt5core5a] stellarium FTBFS on armel and mipsel
Changed Bug title to 'lconvert uses huge amounts of RAM' from 'stellarium FTBFS 
on armel and mipsel'.
> affects -1 src:stellarium
Bug #982882 [libqt5core5a] lconvert uses huge amounts of RAM
Added indication that 982882 affects src:stellarium
> forwarded -1 https://bugreports.qt.io/browse/QTBUG-87010
Bug #982882 [libqt5core5a] lconvert uses huge amounts of RAM
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-87010'.

-- 
982882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982882: stellarium FTBFS on armel and mipsel

[Adrian Bunk]

Control: reassign -1 libqt5core5a 5.15.2+dfsg-4
Control: retitle -1 lconvert uses huge amounts of RAM
Control: affects -1 src:stellarium
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-87010

On Thu, Feb 18, 2021 at 07:33:21PM +0100, Tomasz Buchert wrote:
> On 15/02/21 20:54, Paul Gevers wrote:
> > Source: stellarium
> > Version: 0.20.4-1
> > Severity: serious
> > Tags: ftbfs
> >
> > [...]
> 
> Seems like it is
> https://github.com/Stellarium/stellarium/issues/1131. This has been
> solved with https://bugreports.qt.io/browse/QTBUG-87010.
> 
> Surprisingly, the fix is not in qtbase-opensource-src-5.15.2+dfsg. I'm
> not sure why, it seems like the fix was intended to land there.
>...

I'm re-assigning the bug there.

cu
Adrian

Bug#983172: closed by Andreas Beckmann (Re: Bug#983172: nvidia-cuda-toolkit: Version of libcusolver11 lower than in the archive)

[Adrian Bunk]

On Sat, Feb 20, 2021 at 03:30:03PM +, Debian Bug Tracking System wrote:
>...
> On 2/20/21 2:36 PM, Adrian Bunk wrote:
> > Your upload included the binary package libcusolver11, version 
> > 11.1.0.135~11.2.1-1, for amd64,
> > however testing already has version 11.1.1+~11.0.2.68~11.2.0-2.
> > Uploads to unstable must have a higher version than present in testing.
> 
> Hmm, why didn't I get the reject per email?
>...

https://buildd.debian.org/status/fetch.php?pkg=nvidia-cuda-toolkit=amd64=11.2.1-1=1613465686=0

...
Source: nvidia-cuda-toolkit
...
Architecture: amd64
Version: 11.2.1-1
Distribution: sid
Urgency: medium
Maintainer: amd64 Build Daemon (x86-grnet-01) 

Changed-By: Andreas Beckmann 
...

> Andreas

cu
Adrian

Bug#983172: marked as done (nvidia-cuda-toolkit: Version of libcusolver11 lower than in the archive)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 16:27:46 +0100
with message-id 
and subject line Re: Bug#983172: nvidia-cuda-toolkit: Version of libcusolver11 
lower than in the archive
has caused the Debian Bug report #983172,
regarding nvidia-cuda-toolkit: Version of libcusolver11 lower than in the 
archive
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-cuda-toolkit
Version: 11.2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=nvidia-cuda-toolkit+=sid


bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/nvidia-cuda-toolkit_11.2.1-1_amd64.changes.reason

Version check failed:
Your upload included the binary package libcusolver11, version 
11.1.0.135~11.2.1-1, for amd64,
however testing already has version 11.1.1+~11.0.2.68~11.2.0-2.
Uploads to unstable must have a higher version than present in testing.
--- End Message ---
--- Begin Message ---
Version: 11.2.1-2

On 2/20/21 2:36 PM, Adrian Bunk wrote:
> Your upload included the binary package libcusolver11, version 
> 11.1.0.135~11.2.1-1, for amd64,
> however testing already has version 11.1.1+~11.0.2.68~11.2.0-2.
> Uploads to unstable must have a higher version than present in testing.

Hmm, why didn't I get the reject per email?

Upstream introduced a new version prefix < 11.1.1 that was not jet
handled to be properly prefixed.

Andreas--- End Message ---

Bug#959138: marked as done (numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators')

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 15:19:15 +
with message-id 
and subject line Bug#959138: fixed in nipy 0.4.3~rc1-1
has caused the Debian Bug report #959138,
regarding numpy breaks nipy autopkgtest: No module named 
'numpy.testing.decorators'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
959138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numpy, nipy
Control: found -1 numpy/1:1.18.3-1
Control: found -1 nipy/0.4.2-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
numpy  from testing1:1.18.3-1
nipy   from testing0.4.2-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of numpy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nipy/5197095/log.gz

autopkgtest [22:13:27]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/nipy/__init__.py", line 12, in

from nipy.testing import Tester
  File "/usr/lib/python3/dist-packages/nipy/testing/__init__.py", line
44, in 
from . import decorators as dec
  File "/usr/lib/python3/dist-packages/nipy/testing/decorators.py", line
11, in 
from numpy.testing.decorators import *
ModuleNotFoundError: No module named 'numpy.testing.decorators'
autopkgtest [22:13:27]: test autodep8-python3: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nipy
Source-Version: 0.4.3~rc1-1
Done: Yaroslav Halchenko 

We believe that the bug you reported is fixed in the latest version of
nipy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated nipy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 20 Feb 2021 02:57:19 -0500
Source: nipy
Architecture: source
Version: 0.4.3~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Yaroslav Halchenko 
Closes: 959138 961846
Changes:
 nipy (0.4.3~rc1-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Resolve nipy autopkgtest failure due to numpy testing decorators
 Closes: #959138
   * Fix homepage (thanks to Drew Parsons)
 Closes: #961846
   * Standards-Version: 4.5.1 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Add salsa-ci file (routine-update)
   * watch file standard 4 (routine-update)
   * Do not force maintainers to install Build-Depends on local machine
 .
   [ Yaroslav Halchenko ]
   * debian/patches
 + 0001-BF-avoid-relying-on-Pythonic-casting-of-bool-into-nu.patch
   for compatibility with sympy >= 1.6
   * debian/rules
 - exclude  test_interpolator test for now, failing, reported upstream
   https://github.com/nipy/nipy/issues/468
   due to scipy jump from 1.5.4-1+b1 to 1.6.0-2
 - exclude  resample_outvalue for now, reported upstream
   https://github.com/nipy/nipy/issues/471
Checksums-Sha1:
 7f388863a2e82671731d51df62ebaa892849d00f 2488 nipy_0.4.3~rc1-1.dsc
 0390f8e265a284dafe1d0a7a2d1654f50a7bd5fa 2404037 

Bug#983172: nvidia-cuda-toolkit: Version of libcusolver11 lower than in the archive

[Adrian Bunk]

Source: nvidia-cuda-toolkit
Version: 11.2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=nvidia-cuda-toolkit+=sid


bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/nvidia-cuda-toolkit_11.2.1-1_amd64.changes.reason

Version check failed:
Your upload included the binary package libcusolver11, version 
11.1.0.135~11.2.1-1, for amd64,
however testing already has version 11.1.1+~11.0.2.68~11.2.0-2.
Uploads to unstable must have a higher version than present in testing.

Bug#940821: closed by Bastian Blank (No response by submitter)

[Anton Ivanov]

On 20/02/2021 10:33, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the src:linux package:

#940821: linux-image-5.2.0-2-amd64: file cache corruption with nfs4

It has been closed by Bastian Blank .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Bastian Blank 
 by
replying to this email.



I missed the question. Probably hit the spam bucket for some reason.

I am able to reproduce it with more recent versions as well.

The most recent one I have around is 5.4.0-0.bpo.2-amd64

Still reproducible 100% - just tested it.

It is trivial to reproduce if anyone actually bothers to do so. Just 
grab a big enough tree where make runs truly in parallel - openwrt is 
best, but even the Linux kernel does the job.


Mount it via nfs4 from another server (it will work even locally, but 
takes longer to reproduce - may take a whole afternoon)


Run while make -j 12 clean && make -j 12 ; do true ; done

Leave it to run. On 6 cores/12 threads it takes 2-3 builds of openwrt or 
~ 5-8 linux kernel builds to blow up. More cores - faster. Less cores 
slower.


I sent it to the mailing list too, but nobody could be bothered to even 
ask any questions.


--
Anton R. Ivanov
https://www.kot-begemot.co.uk/

Bug#983041: marked as done (php-imagick: autopkgtest regression: cd: too many arguments)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 13:05:39 +
with message-id 
and subject line Bug#983041: fixed in php-imagick 3.4.4+php8.0+3.4.4-2+deb11u1
has caused the Debian Bug report #983041,
regarding php-imagick: autopkgtest regression: cd: too many arguments
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-imagick
Version: 3.4.4+php8.0+3.4.4-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
php-imagickfrom testing3.4.4+php8.0+3.4.4-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-imagick/10526591/log.gz

autopkgtest [13:11:38]: test command1: cd imagick-*/tests && phpunit
--verbose .
autopkgtest [13:11:38]: test command1: [---
bash: line 1: cd: too many arguments
autopkgtest [13:11:38]: test command1: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-imagick
Source-Version: 3.4.4+php8.0+3.4.4-2+deb11u1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
php-imagick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-imagick package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Feb 2021 13:33:52 +0100
Source: php-imagick
Architecture: source
Version: 3.4.4+php8.0+3.4.4-2+deb11u1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Closes: 983041
Changes:
 php-imagick (3.4.4+php8.0+3.4.4-2+deb11u1) unstable; urgency=medium
 .
   * Use only the main version to run the autopkgtest (Closes: #983041)
Checksums-Sha1:
 e983900a460bb831aa5f63ae378a27f9527caf07 2388 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.dsc
 a43dfc0641c8aeadc9a9f7e055127d88873d9f3e 21364 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.debian.tar.xz
 997400ffce5704b8796ae841ec0750cfa0d3fb08 12422 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1_amd64.buildinfo
Checksums-Sha256:
 0de76f69ebb395e57b773522e87d513a02a8e7668415766e6ed99f1a8c5aebae 2388 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.dsc
 e68697e087b284ab82d04f3980f6759c6ddef65bb49ab2985976afe464a70d88 21364 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.debian.tar.xz
 3f629a205fa396408bf94341e6b3ab1a255bb3268f97c58d8f8a75681a815451 12422 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1_amd64.buildinfo
Files:
 28e513ac5ba9ace2986a77cec42a8036 2388 php optional 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.dsc
 129bc13501c1ae96f1b76e26d0ea422b 21364 php optional 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1.debian.tar.xz
 f8bbdcf0e59791c3b059c57742fc2ceb 12422 php optional 
php-imagick_3.4.4+php8.0+3.4.4-2+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmAxA/pfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcIy5g//aLSJw8H15Y+e9Jtr3dKzotKf3KEunlcFt9tH4uzCYL3U9Lvw0tLZxFN2
qKsaSWNVAjsvS+gBtCNRJGQeptU1NTODN2bRfQx5CsXxYCHow700mIautnwlO52J
QUP0bzJeVwy8URV2aH8iI7ZLdzEAWD8SR6tR3ZnuK0jRWMCPw8GdJwJZsBgCW2MD

Processed: bug 979075 is forwarded to https://github.com/jonls/redshift/issues/794

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 979075 https://github.com/jonls/redshift/issues/794
Bug #979075 [redshift-gtk] redshift-gtk silently adds to systemd causing double 
instance to run in user session
Set Bug forwarded-to-address to 'https://github.com/jonls/redshift/issues/794'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983169: ensmallen FTBFS on several architectures: test failure

[Adrian Bunk]

Source: ensmallen
Version: 2.16.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=ensmallen

...
Running tests...
/usr/bin/ctest --force-new-ctest-process -j8
Test project /<>/obj-aarch64-linux-gnu
Start 1: ensmallen_tests
1/1 Test #1: ensmallen_tests ..***Failed  486.69 sec
ensmallen version: 2.16.0 (Severely Dented Can Of Polyurethane)
armadillo version: 10.1.2 (Orchid Ambush)

~~~
ensmallen_tests is a Catch v2.4.1 host application.
Run with -? for options

---
AdamSchafferFunctionN2Test
---
./tests/adam_test.cpp:331
...

./tests/test_function_tools.hpp:114: FAILED:
  REQUIRE( objective == Approx(expectedObjective).margin(objectiveMargin) )
with expansion:
  0.4988660447 == Approx( 0.0 )

===
test cases:   274 |   273 passed | 1 failed
assertions: 13331 | 13330 passed | 1 failed



0% tests passed, 1 tests failed out of 1

Total Test time (real) = 486.69 sec

The following tests FAILED:
  1 - ensmallen_tests (Failed)
Errors while running CTest
make[2]: *** [Makefile:119: test] Error 8

Processed: Bug#982973 marked as pending in qtmultimedia-opensurce-src

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982973 [src:qtmultimedia-opensource-src] qtmultimedia-opensource-src: 
FTBFS in test: tst_QVideoFrame::image(64x64 NV12) Received a fatal error
Added tag(s) pending.

-- 
982973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982973: marked as pending in qtmultimedia-opensurce-src

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #982973 in qtmultimedia-opensurce-src reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/qt/qtmultimedia/-/commit/f869d887c41ee9b9276291fc5c62f95908da7b3b


Add a patch to increase buffer sizes in tst_QVideoFrame::image() test.

To fix segmentation fault that sometimes happens.

Closes: #982973.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982973

Processed: tagging 977057

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 977057 + patch
Bug #977057 [src:behave] behave FTBFS with pytest 6
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 979075 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 979075 serious
Bug #979075 [redshift-gtk] redshift-gtk silently adds to systemd causing double 
instance to run in user session
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983167: vtk7: binary-all FTBFS

[Adrian Bunk]

Source: vtk7
Version: 7.1.1+dfsg2-9
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=vtk7=all=7.1.1%2Bdfsg2-9=1613772102=0

...
CMake Error at Utilities/KWSys/vtksys/cmake_install.cmake:153 (file):
  file INSTALL cannot find
  "/<>/debian/build/lib/libvtksys-7.1.so.7.1p.1":
  No such file or directory.
Call Stack (most recent call first):
  Utilities/KWSys/cmake_install.cmake:51 (include)
  cmake_install.cmake:110 (include)


make[2]: *** [Makefile:108: install] Error 1

Processed: Re: Bug#983034: plasma-workspace-wayland: hanging in ksplashqml

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #983034 [plasma-workspace-wayland] plasma-workspace-wayland: hanging in 
ksplashqml
Severity set to 'normal' from 'grave'

-- 
983034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983034: plasma-workspace-wayland: hanging in ksplashqml

[Norbert Preining]

> dmesg shows a crash in the nouveau driver:

Well ... that is not something we can care for, so I suggest closing
this bug.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#983034: plasma-workspace-wayland: hanging in ksplashqml

[Norbert Preining]

Control: severity -1 normal

Change severity - nothing we can really deal with

> dmesg shows a crash in the nouveau driver:

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#940821: marked as done (linux-image-5.2.0-2-amd64: file cache corruption with nfs4)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 11:29:54 +0100
with message-id 
and subject line No response by submitter
has caused the Debian Bug report #940821,
regarding linux-image-5.2.0-2-amd64: file cache corruption with nfs4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
940821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.9-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

NFSv4 caching is completely broken on SMP.

How to reproduce:

Option 1. clone openwrt, run while make clean && make -j `nproc` ; do true ; 
done

It will break depending on number of CPUs within several runs. 

Symptoms of breakage. A directory on the client looks empty. Example (mnt is an 
NFSv4 mount):

ls -laF 
/mnt/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
total 8
drwxr-xr-x 2 anivanov anivanov 4096 Sep 20 10:51 ./
drwxr-xr-x 3 anivanov anivanov 4096 Sep 20 10:51 ../

While it actually has a file in it (same on server):

ls -laF 
/exports/work/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
total 12
drwxr-xr-x 2 anivanov anivanov 4096 Sep 20 10:51 ./
drwxr-xr-x 3 anivanov anivanov 4096 Sep 20 10:51 ../
-rw-r--r-- 1 anivanov anivanov   32 Sep 20 10:51 ipcbuf.h

This cache entry on the client does not expire as it should per the NFSv4 
caching documentation - the only way of dealing with it is reboot, unmount or 
caches drop.

Option 2. Have your $HOME on nfsv4 and use thunderbird. Move mails between 
folders. Sooner or later (usually sooner) you will lose an email.

So this is both "breaks unrelated software" and "data loss" depending on what 
you are doing.

Tested on:

AMD Ryzen 5 2400G, AMD Ryzen 5 1600X, AMD Ryzen 5 1600, AMD A8-6500

Shows up on all. Fastest on the 6 core 12 thread ryzens, slowest on the AMD A8 
(takes up to 3 iterations of make there).

Brgds,

A.

-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.2.0-2-amd64 
root=UUID=8eb17efb-6574-42d0-885e-487b98364059 ro mitigations=off noht quiet

** Not tainted

** Kernel log:
[3.684402] input: HD-Audio Generic Front Mic as 
/devices/pci:00/:00:08.1/:09:00.3/sound/card0/input8
[3.684490] input: HD-Audio Generic Rear Mic as 
/devices/pci:00/:00:08.1/:09:00.3/sound/card0/input9
[3.684555] input: HD-Audio Generic Line as 
/devices/pci:00/:00:08.1/:09:00.3/sound/card0/input10
[3.685553] input: HD-Audio Generic Line Out as 
/devices/pci:00/:00:08.1/:09:00.3/sound/card0/input11
[3.685627] input: HD-Audio Generic Front Headphone as 
/devices/pci:00/:00:08.1/:09:00.3/sound/card0/input12
[3.806626] kvm: Nested Virtualization enabled
[3.806636] kvm: Nested Paging enabled
[3.806637] SVM: Virtual VMLOAD VMSAVE supported
[3.806637] SVM: Virtual GIF supported
[3.820371] MCE: In-kernel MCE decoding enabled.
[3.824533] EDAC amd64: Node 0: DRAM ECC disabled.
[3.824536] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[3.872569] pktcdvd: pktcdvd0: writer mapped to sr0
[3.900858] EDAC amd64: Node 0: DRAM ECC disabled.
[3.900860] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[3.948661] EDAC amd64: Node 0: DRAM ECC disabled.
[3.948662] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[3.996651] EDAC amd64: Node 0: DRAM ECC disabled.
[3.996652] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause 

Processed: reassign 983139 to xfwm4, reassign 982171 to src:psi4, fixed 982171 in 1:1.3.2+dfsg-1, affects 982171 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 983139 xfwm4
Bug #983139 [xfwm] Artifacts in x2go rendering connecting to testing from a 
buster client
Warning: Unknown package 'xfwm'
Bug reassigned from package 'xfwm' to 'xfwm4'.
Ignoring request to alter found versions of bug #983139 to the same values 
previously set
Ignoring request to alter fixed versions of bug #983139 to the same values 
previously set
> reassign 982171 src:psi4 1:1.3.2-3
Bug #982171 {Done: Andreas Tille } [src:libint, src:psi4] 
libint breaks psi4 autopkgtest: 'str' object is not callable; perhaps you 
missed a comma?
Bug reassigned from package 'src:libint, src:psi4' to 'src:psi4'.
No longer marked as found in versions psi4/1:1.3.2-3 and libint/1.2.1-4.
No longer marked as fixed in versions psi4/1:1.3.2+dfsg-1.
Bug #982171 {Done: Andreas Tille } [src:psi4] libint breaks 
psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma?
Marked as found in versions psi4/1:1.3.2-3.
> fixed 982171 1:1.3.2+dfsg-1
Bug #982171 {Done: Andreas Tille } [src:psi4] libint breaks 
psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma?
Marked as fixed in versions psi4/1:1.3.2+dfsg-1.
> affects 982171 + src:libint
Bug #982171 {Done: Andreas Tille } [src:psi4] libint breaks 
psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma?
Added indication that 982171 affects src:libint
> reassign 982992 src:node-regexpu-core 4.7.1-1
Bug #982992 [src:node-regjsparser, src:node-regexpu-core] node-regjsparser 
breaks node-regexpu-core autopkgtest: Missing expected exception (Error).
Bug reassigned from package 'src:node-regjsparser, src:node-regexpu-core' to 
'src:node-regexpu-core'.
No longer marked as found in versions node-regexpu-core/4.7.1-1 and 
node-regjsparser/0.6.6+ds-1.
No longer marked as fixed in versions node-regexpu-core/4.7.1-2.
Bug #982992 [src:node-regexpu-core] node-regjsparser breaks node-regexpu-core 
autopkgtest: Missing expected exception (Error).
Marked as found in versions node-regexpu-core/4.7.1-1.
> fixed 982992 4.7.1-2
Bug #982992 [src:node-regexpu-core] node-regjsparser breaks node-regexpu-core 
autopkgtest: Missing expected exception (Error).
Marked as fixed in versions node-regexpu-core/4.7.1-2.
> affects 982992 + src:node-regjsparser
Bug #982992 [src:node-regexpu-core] node-regjsparser breaks node-regexpu-core 
autopkgtest: Missing expected exception (Error).
Added indication that 982992 affects src:node-regjsparser
> reassign 982994 src:silver-platter 0.4.0-1
Bug #982994 {Done: Jelmer Vernooij } [src:lintian-brush, 
src:silver-platter] lintian-brush breaks silver-platter autopkgtest: cannot 
import name 'guess_upstream_metadata' from 'lintian_brush.upstream_metadata'
Bug reassigned from package 'src:lintian-brush, src:silver-platter' to 
'src:silver-platter'.
No longer marked as found in versions lintian-brush/0.96 and 
silver-platter/0.4.0-1.
No longer marked as fixed in versions silver-platter/0.4.1-1.
Bug #982994 {Done: Jelmer Vernooij } [src:silver-platter] 
lintian-brush breaks silver-platter autopkgtest: cannot import name 
'guess_upstream_metadata' from 'lintian_brush.upstream_metadata'
Marked as found in versions silver-platter/0.4.0-1.
> fixed 982994 0.4.1-1
Bug #982994 {Done: Jelmer Vernooij } [src:silver-platter] 
lintian-brush breaks silver-platter autopkgtest: cannot import name 
'guess_upstream_metadata' from 'lintian_brush.upstream_metadata'
Marked as fixed in versions silver-platter/0.4.1-1.
> affects 982994 + src:lintian-brush
Bug #982994 {Done: Jelmer Vernooij } [src:silver-platter] 
lintian-brush breaks silver-platter autopkgtest: cannot import name 
'guess_upstream_metadata' from 'lintian_brush.upstream_metadata'
Added indication that 982994 affects src:lintian-brush
> notfixed 951834 7.4.11-3
Bug #951834 [src:php7.4] php7.4 FTBFS on hurd-i386
The source 'php7.4' and version '7.4.11-3' do not appear to match any binary 
packages
No longer marked as fixed in versions 7.4.11-3.
> fixed 915762 1:10.0.0+r36-7
Bug #915762 {Done: Roger Shimizu } 
[src:android-platform-system-core] Port to Hurd
Marked as fixed in versions android-platform-system-core/1:10.0.0+r36-7.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
915762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915762
951834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951834
982171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982171
982992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982992
982994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982994
983139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907637: marked as done (bonding with virtio NICs does not work any more)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 11:27:46 +0100
with message-id 
and subject line No response by submitter
has caused the Debian Bug report #907637,
regarding bonding with virtio NICs does not work any more
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.110-3+deb9u4
Severity: critical

Hi,

For network testing reasons I run several KVM VMs with up to now four virtio 
NICs,
where only one NIC is connected and the others are marked as "link_down" in the
KVM configuration.

In the guest the NICs are configured as bonding device with lacp. Up to 
linux-image-4.9.0-6-amd64
this worked without issues. Starting with linux-image-4.9.0-7-amd64 the kernel 
now reports
after booting:

Aug 27 12:01:39 test-gate-1 kernel: [   22.881163] bond0: link status up for 
interface ens18, enabling it in 0 ms
Aug 27 12:01:39 test-gate-1 kernel: [   22.882881] bond0: failed to get link 
speed/duplex for ens18
Aug 27 12:01:39 test-gate-1 kernel: [   22.985209] bond0: link status up for 
interface ens18, enabling it in 0 ms
Aug 27 12:01:39 test-gate-1 kernel: [   22.986998] bond0: failed to get link 
speed/duplex for ens18
Aug 27 12:01:39 test-gate-1 kernel: [   23.089250] bond0: link status up for 
interface ens18, enabling it in 0 ms
Aug 27 12:01:39 test-gate-1 kernel: [   23.091765] bond0: failed to get link 
speed/duplex for ens18
Aug 27 12:01:40 test-gate-1 kernel: [   23.193170] bond0: link status up for 
interface ens18, enabling it in 0 ms
Aug 27 12:01:40 test-gate-1 kernel: [   23.195772] bond0: failed to get link 
speed/duplex for ens18

ethtool also shows unknown speed and duplex for the virtio interfaces.

This seems to not have been an issue before linux-4.9.0-7.

Switching the virtual NICs from virtio to vmxnet3 solves the issue,
ethtool also reports speed and duplex mode.

I do not know if this is a KVM issue or a kernel issue, but as
the older kernel image works it looks more like a kernel issue to me.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: QEMU
product_name: Standard PC (i440FX + PIIX, 1996)
product_version: pc-i440fx-2.11
chassis_vendor: QEMU
chassis_version: pc-i440fx-2.11
bios_vendor: SeaBIOS
bios_version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
BAR=0 offset= size=
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
BAR=4 offset=3000 size=1000 multiplier=0004
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
BAR=4 offset=2000 size=1000
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
BAR=4 offset=1000 size=1000
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
BAR=4 offset= size=1000
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:05.0 SCSI storage controller [0100]: Red Hat, Inc Virtio SCSI [1af4:1004]
Subsystem: Red Hat, Inc Virtio SCSI [1af4:0008]
Physical Slot: 5
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
BAR=0 offset= size=
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
BAR=4 offset=3000 size=1000 multiplier=0004
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
BAR=4 offset=2000 size=1000
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
BAR=4 offset=1000 size=1000
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
BAR=4 offset= size=1000
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:08.0 Communication controller [0780]: Red Hat, Inc Virtio console 

Processed: severity of 979994 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 979994 important
Bug #979994 [src:linux] linux-image-4.19.0-13-amd64: The Debian 10 freezes.
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 962485 is important, tagging 962485

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 962485 important
Bug #962485 [src:linux] Please revert CONFIG_MIPS_O32_FP64_SUPPORT change
Severity set to 'important' from 'serious'
> tags 962485 + wontfix
Bug #962485 [src:linux] Please revert CONFIG_MIPS_O32_FP64_SUPPORT change
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
962485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 926539 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 926539 important
Bug #926539 [src:linux,rootskel] rootskel: steal-ctty no longer works on at 
least sparc64
Bug #961056 [src:linux,rootskel] debian-installer: qemu-system-s390x 
installation fails due to incorrect serial device
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539
961056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983092: marked as done (xapps-common:all is not properly arch-independent)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 10:18:34 +
with message-id 
and subject line Bug#983092: fixed in xapp 2.0.6-2
has caused the Debian Bug report #983092,
regarding xapps-common:all is not properly arch-independent
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xapp
Version: 2.0.6-1
Severity: serious

xapps-common is tagged as architecture:all, but the generated
xapp-sn-watcher.desktop included in it depends on the architecture it was
built on.

By accident, we rebuilt the arch:all packages from xapp on i386, while our
main architecture is amd64.
The result is an xapp-sn-watcher.desktop file that isn't functional, as it
leads to:

systemd-xdg-autostart-generator[29117]: Exec binary
'/usr/lib/i386-linux-gnu/xapps/sn-watcher/xapp-sn-watcher' does not exist:
No such file or directory

Similarly, if someone would install Debian bullseye with a main
architecture i386 (not many would do, but there are certainly some) or an
ARM architecture, this would also fail (because there, it refers to the
x86_64 library directory). Thus I'm setting the severity to Serious here -
It is broken for any architecture other than amd64 in Debian.

There are probably two possible fixes (maybe more):
1) Move the autostart file into the respective libxapp1 packages (with the
binary)
2) Use the alternatives mechanism to let one binary package provide the
executable at a common location.

Cheers,
Sven
--- End Message ---
--- Begin Message ---
Source: xapp
Source-Version: 2.0.6-2
Done: Norbert Preining 

We believe that the bug you reported is fixed in the latest version of
xapp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated xapp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Feb 2021 18:42:03 +0900
Source: xapp
Architecture: source
Version: 2.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cinnamon Team 
Changed-By: Norbert Preining 
Closes: 983092
Changes:
 xapp (2.0.6-2) unstable; urgency=medium
 .
   [ Fabio Fantoni ]
   * Move xapp-sn-watcher.desktop from xapps-common to libxapp1
 because contain arch dep. path (Closes: #983092)
Checksums-Sha1:
 ba486933dd03e4fb7e32e1624f12381e72960a87 2196 xapp_2.0.6-2.dsc
 753f107619d34cfec762f47f6e0f1cdef6e77de6 6516 xapp_2.0.6-2.debian.tar.xz
 7e3f1b926fd76a7a2caa504761e75cb4e1ec5e24 16835 xapp_2.0.6-2_source.buildinfo
Checksums-Sha256:
 f2d840dee99706af416baeb5baebf56555ad488048bc34fcb19f174485632f9d 2196 
xapp_2.0.6-2.dsc
 60948b1bd31f4b2a8005d47926c3c9c18b02ee7ff92d742cac755ea1468541cc 6516 
xapp_2.0.6-2.debian.tar.xz
 933f0a8e2c8d51f3ad7e4308aa087c19a9fb1e5318e79c0496796a8d7c684df0 16835 
xapp_2.0.6-2_source.buildinfo
Files:
 d35c21e9a49e61fd6370ff8ed6e82936 2196 x11 optional xapp_2.0.6-2.dsc
 c0770b14434e7f3d1ece9d2ab1092231 6516 x11 optional xapp_2.0.6-2.debian.tar.xz
 99627cf406654f9fea13ec7b84811ade 16835 x11 optional 
xapp_2.0.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAmAw2iQACgkQ2A4JsIcU
AGbUfgf/U91JtwH0/77bcPEJit/YrpCXt6Zj+6AFZC/dxJwwRhNwhDKcqOiHdFrx
Ng0r+hTASycK9/RdKAfaBEDOtnlRwz9li9LL2La4rFa+yF3Hmw39F1zU+CNjxyMg
k5Xhss68dCmvU8BAqDMOdyIORRsUNWZYio1LnoAoeEF+y5soND70ZZnD3Knw+JCW
OqYFWGjKtyGZl/hYCyKJh0mf/0tu9K4lVnilhe5WmafK7P+5yh3JbfhdtF3eXYsz
SOjqQQINJETVFjzp3yXpfvQ+MBEkxPdoGVOfS3T0/R24aQUeiHXnr9QqkenpEkPh
P3TUxp+2Rz7hr7gvetF3K55jvP9D2Q==
=INGQ
-END PGP SIGNATURE End Message ---

Bug#928526: marked as done (linux-image-4.19.0-4-amd64: data corruption with swap file on filesystem with encrypted SSD, LVM and TRIM enabled)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 11:19:26 +0100
with message-id 
and subject line No response from submitter
has caused the Debian Bug report #928526,
regarding linux-image-4.19.0-4-amd64: data corruption with swap file on 
filesystem with encrypted SSD, LVM and TRIM enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.28-2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Hi,

I have an older laptop with an SSD and an encrypted LVM setup with TRIM
passthrough through the crypto layers. Normally I run without swap space,
but occasionally I will set up a swap file if I anticipate a need for it.

I create the swap file on an encrypted partition using

dd if=/dev/zero of=/home/swap bs=1G count=8
mkswap /home/swap
swapon /home/swap

The file system in question is ext4 in a LVM logical volume in a PV that is
a LUKS volume inside a DOS partition on an SSD. The "discard" option is set
in /etc/crypttab.

Since upgrading from stretch to buster, processes using a lot of memory die
with signal 11 (often) or 6 (seldom), typically after being swapped in. I
can reproduce this rather consistently by compiling KiCad, which at one
point invokes four ld processes in parallel that each take roughly 3 GB of
RAM, causing some swapping: most of the time, one or two of the ld
processes terminates with a segmentation fault. Switching to Firefox during
that time almost certainly kills Firefox or the X server, so this seems
related to swapping.

I have also experienced some file system corruption on the /home partition
(that needed manual repair with fsck), it is not entirely clear to me if
that is coincidental or related. That partition has run without fsck for
some time before, but the affected files were all created shortly before
the system went into memory pressure. Other partitions were fine, but that
might also be because they are not usually written to during operation.

Memtest86+ reports no problems.

The same setup works fine with 4.9.0-8-amd64 from stretch, so this is a
regression.

I can probably test intermediate versions and/or changes in setup, but this
is difficult to automate because "bad" runs require manual file system
repairs and every run requires LUKS setup to be repeated.

   Simon

-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
initrd=\7fa8c2303086c2fad03bc1be50eaac8c\4.19.0-4-amd64\initrd 
root=/dev/mapper/coffee-root ro quiet

** Not tainted

** Kernel log:
[   20.645047] systemd-udevd[726]: Using default interface naming scheme 'v240'.
[   20.645574] videodev: Linux video capture interface: v2.00
[   20.646574] systemd-udevd[726]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[   20.647277] usbcore: registered new interface driver qcserial
[   20.647289] usbserial: USB Serial support registered for Qualcomm USB modem
[   20.647997] qcserial 1-1.5:1.0: Qualcomm USB modem converter detected
[   20.648074] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB0
[   20.648279] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   20.648800] usbcore: registered new interface driver cdc_wdm
[   20.651751] qcserial 1-1.5:1.2: Qualcomm USB modem converter detected
[   20.652053] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB1
[   20.653496] qcserial 1-1.5:1.3: Qualcomm USB modem converter detected
[   20.653565] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB2
[   20.654411] qmi_wwan 1-1.5:1.8: cdc-wdm0: USB WDM device
[   20.654574] qmi_wwan 1-1.5:1.8 wwan0: register 'qmi_wwan' at 
usb-:00:1a.0-1.5, WWAN/QMI device, 0a:b7:4f:bc:8b:4c
[   20.654622] usbcore: registered new interface driver qmi_wwan
[   20.655678] systemd-udevd[604]: Using default interface naming scheme 'v240'.
[   20.657076] systemd-udevd[604]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[   20.657187] qmi_wwan 1-1.5:1.8 wwp0s26u1u5i8: renamed from wwan0
[   20.667147] uvcvideo: Found UVC 1.00 device FJ Camera  (04f2:b2fc)
[   20.686810] Bluetooth: Core ver 2.22
[   20.686822] NET: Registered protocol family 31
[   20.686823] Bluetooth: HCI device and connection manager initialized
[   20.686826] Bluetooth: HCI socket layer initialized
[   20.686827] Bluetooth: 

Bug#801975: marked as done (linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but mdadm doesn't set this drive failing)

[Debian Bug Tracking System]

Your message dated Sat, 20 Feb 2021 11:17:15 +0100
with message-id 
and subject line No response from submitter
has caused the Debian Bug report #801975,
regarding linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but 
mdadm doesn't set this drive failing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-0.bpo.4-amd64
Version: 3.16.7-ckt11-1~bpo70+1
Justification: causes serious data loss
Severity: critical
Subject: linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but 
mdadm doesn't set this drive failing

hello,

We enconter a serious bug related with a 6805H adapect controler on wich
8 drives were plugged.
Those drives were configured as raid6 with LVM.

The october the 4th pm80xx modules repport a failling disk but the disk
was not repported by mdadm as faulty, and the data became corrupted.

We are trying to reproduce the bug on non cruitical date but with no
succes for the moment. However, in my mind the data loss was big enough
for repporting the bug whatever.


Note : 
(1) we have remounted the machine for data retrieval, adding an ASUS
controller card (so no relation to the signaled bug).
(2) may be related to bug 774583 as problems appear after a checkarray.

thanks

best regards
Xavier Quost



-- Package-specific info:
** Version:
Linux version 3.16.0-0.bpo.4-amd64 (debian-ker...@lists.debian.org) (gcc
version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt11-1~bpo70+1
(2015-06-08)

Package: mdadm
Version: 3.2.5-5

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-0.bpo.4-amd64
root=UUID=23b97aa0-53d0-42c4-afd0-48f302de1b08 ro quiet
processor.max_cstate=1 idle=poll nox2apic intermap=off

** Tainted: WO (4608)
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
Oct  4 00:57:01 nassli kernel: [3944417.125573] md: data-check of RAID
array md0
Oct  4 00:57:01 nassli kernel: [3944417.125576] md: minimum _guaranteed_
speed: 5 KB/sec/disk.
Oct  4 00:57:01 nassli kernel: [3944417.125577] md: using maximum
available idle IO bandwidth (but not more than 500 KB/sec) for
data-check.
Oct  4 00:57:01 nassli kernel: [3944417.125582] md: using 128k window,
over a total of 3907016192k.
Oct  4 08:41:31 nassli kernel: [3972277.588119] pm80xx mpi_sata_event
2689:SATA EVENT 0x23
Oct  4 08:41:31 nassli kernel: [3972277.588125] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.588315] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.588634] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.588945] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.589256] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.589563] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.589875] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:31 nassli kernel: [3972277.590186] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:57 nassli kernel: [3972277.590494] pm80xx
mpi_sata_completion 2373:SAS Address of IO Failure
Drive:5d1106ee7590pm80xx mpi_sata_completion 2373:SAS Address of IO
Failure Drive:5d1106ee7590
Oct  4 08:41:57 nassli kernel: [3972304.318093] sas: Enter
sas_scsi_recover_host busy: 30 failed: 30
Oct  4 08:41:57 nassli kernel: [3972304.318099] sas: trying to find task
0x8802b80d6440
Oct  4 08:41:57 nassli kernel: [3972304.318100] sas: sas_scsi_find_task:
aborting task 0x8802b80d6440
Oct  4 08:41:57 nassli kernel: [3972304.318254] pm80xx

Processed: severity of 979765 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 979765 important
Bug #979765 [src:linux] linux-image-5.10.0-1-amd64: Kernel panic on boot on my 
Via VX900
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983034: plasma-workspace-wayland: hanging in ksplashqml

[Heinrich Schuchardt]

On 19.02.21 19:40, Dennis Filder wrote:
> Control: tag -1 + moreinfo bullseye sid
>
> If you cannot switch to console with Ctrl-Alt-F2 then this is a strong
> indicator that the bug is in the kernel, probably nouveau.
>
> If you can reproduce this reliably it would help a lot if you could
> provide the output of these commands after the bug has happened:
>
>   dmesg
>   strace -f -p $(pidof ksplashqml) 2>&1 | dd bs=1k count=20
>   journalctl -ab
>
> You may have to run some of them as root.
>

dmesg shows a crash in the nouveau driver:

[  441.529012] [ cut here ]
[  441.529076] WARNING: CPU: 1 PID: 1964 at
drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x84/0x9c [nouveau]
[  441.529078] Modules linked in: xt_conntrack nft_chain_nat
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat
nf_tables nfnetlink br_netfilter bridge stp llc rfkill overlay nls_ascii
nls_cp437 vfat fat snd_hda_codec_hdmi aes_ce_blk crypto_simd
snd_hda_intel cryptd snd_intel_dspcfg aes_ce_cipher snd_hda_codec
ghash_ce gf128mul libaes sha2_ce snd_hda_core snd_hwdep snd_pcm
sha256_arm64 sha1_ce snd_timer evdev snd soundcore sg efi_pstore
omap_rng rng_core sbsa_gwdt armada_thermal fuse configfs efivarfs
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor xor_neon raid6_pq libcrc32c crc32c_generic raid1 raid0
multipath linear md_mod hid_generic usbhid hid sd_mod t10_pi crc_t10dif
crct10dif_generic nouveau i2c_mux_pca954x i2c_mux ahci_platform
libahci_platform libahci marvell10g libata crct10dif_ce
[  441.529194]  crct10dif_common scsi_mod i2c_algo_bit ttm xhci_plat_hcd
drm_kms_helper marvell xhci_hcd drm mvpp2 usbcore i2c_mv64xxx mvmdio
mdio_devres sfp mdio_i2c phylink of_mdio phy_generic fixed_phy libphy
sdhci_xenon_driver sdhci_pltfm usb_common phy_mvebu_cp110_comphy fixed sdhci
[  441.529236] CPU: 1 PID: 1964 Comm: kworker/1:0 Not tainted
5.10.0-3-arm64 #1 Debian 5.10.13-1
[  441.529238] Hardware name: SolidRun Armada 8040 MacchiatoBin/Armada
8040 MacchiatoBin, BIOS EDK II Mar 26 2020
[  441.529284] Workqueue: events nouveau_cli_work [nouveau]
[  441.529289] pstate: 6005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
[  441.529332] pc : nvif_vmm_put+0x84/0x9c [nouveau]
[  441.529375] lr : nvif_vmm_put+0x78/0x9c [nouveau]
[  441.529376] sp : 8000119cbc80
[  441.529378] x29: 8000119cbc80 x28: ·
[  441.529383] x27: 386ac5329f28 x26: 0001·
[  441.529387] x25: dead0100 x24: dead0122·
[  441.529391] x23: 386ac5329f18 x22: 386ac5077300·
[  441.529395] x21: 386ac5329f08 x20: 386ac2b00080·
[  441.529398] x19: 8000119cbce8 x18: ·
[  441.529402] x17:  x16: bbff1d518580·
[  441.529406] x15:  x14: ·
[  441.529410] x13:  x12: 0040·
[  441.529414] x11: bbff1dcf5ec0 x10: 0ad0·
[  441.529417] x9 : bbfea5a3d3f0 x8 : fefefefefefefeff·
[  441.529421] x7 : 8888 x6 : 8000119cbcb8·
[  441.529425] x5 :  x4 : 0008·
[  441.529429] x3 : 048a x2 : ·
[  441.529433] x1 :  x0 : fffe·
[  441.529437] Call trace:
[  441.529480]  nvif_vmm_put+0x84/0x9c [nouveau]
[  441.529523]  nouveau_vma_del+0x9c/0xe0 [nouveau]
[  441.529565]  nouveau_gem_object_delete_work+0x48/0x80 [nouveau]
[  441.529607]  nouveau_cli_work+0xe8/0x180 [nouveau]
[  441.529616]  process_one_work+0x1d4/0x490
[  441.529619]  worker_thread+0x188/0x504
[  441.529622]  kthread+0x130/0x134
[  441.529625]  ret_from_fork+0x10/0x38
[  441.529628] ---[ end trace 28675099a596659e ]---
:set nonumber

Best regards

Heinrich

Bug#983092: xapps-common:all is not properly arch-independent

[Norbert Preining]

Hi all,

thanks Sven for the report - good catch - and thanks to Fabio for the quick
fix. I have uploaded the package with Fabio's fix to unstable just now.

Here my comments:

On Fri, 19 Feb 2021, Sven Mueller wrote:
> 1) Move the autostart file into the respective libxapp1 packages (with the
> binary)

On Fri, 19 Feb 2021, Andreas Henriksson wrote:
> Seems like Fabio Fantoni went with this solution and while I agree
> that desktop files should be shipped in the same package as the binary
> they launch in general,

Let us separate the issues first:
* first of all, the fix by Fabio does indeed fix the bug, so that
  is a correct fix.
* While I agree that it is nice to have .desktop files and their
  programs in the same package, it is not an obligation (last time I
  checked the policy), and I have several other cases where it is not
  the like this.
  So while it would be nice - we can target it after bullseye release.

On Fri, 19 Feb 2021, Andreas Henriksson wrote:
> I also think it's very wrong to ship
> non-SO-verioned files in a libfooN package!

On Sat, 20 Feb 2021, Sven Mueller wrote:
> I agree, Andreas. I would actually consider the binary being in the ABI
> versions library package questionable, now that I think about it. You
> wouldn't be able to run two versions of this at the same time anyhow.

Again, I agree, but consider it irrelevant for bullseye.
Please open a bug with severity important, and we will work on this
after the release of bullseye. There is no libxapp2, and much more there
will not be one in bullseye, so this is theoretical hair splitting that
is only for the "beauty" but has not influence on user experience.


On Sat, 20 Feb 2021, Sven Mueller wrote:
> Given we're in freeze it might be too late to introduce a new binary
> package (if that's needed), but fixing one bug by doing something
> wrong doesn't feel like debian style either. Wouldn't it be better
> to just ask the release team which solution they prefer and possibly
> get an exception for introducing a new binary package if needed?

No. First of all, as I mentioned, having desktop and the invoked program
in different package is not a requirement. At least **I** will not
introduce a new binary package and try to fix all corner cases so late,
just for some beauty.



To sum it up:
- please submit a bug of severity important concerning the SO version
  file
- please submit a bug concerning the fact that desktop file and invoked
  program are in different packages - severity normal
- after release of bullseye we will clear this up

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: openms build-depends on removed package

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #982567 [openms] openms build-depends on removed package.
Added tag(s) upstream.
> forwarded -1 https://github.com/OpenMS/OpenMS/issues/5151
Bug #982567 [openms] openms build-depends on removed package.
Set Bug forwarded-to-address to 'https://github.com/OpenMS/OpenMS/issues/5151'.

-- 
982567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#982567: openms build-depends on removed package

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/OpenMS/OpenMS/issues/5151

Processed: Bug#981404 affects stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # stretch also affected
> found 981404 libzstd/1.1.2-1
Bug #981404 {Done: Étienne Mollier } [zstd] 
compressed file is world readable, while zstd is running
Marked as found in versions libzstd/1.1.2-1.
> thank you
Stopping processing here.

Please contact me if you need assistance.
-- 
981404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#983092: xapps-common:all is not properly arch-independent

[Sven Mueller]

I agree, Andreas. I would actually consider the binary being in the ABI
versions library package questionable, now that I think about it. You
wouldn't be able to run two versions of this at the same time anyhow.

I was too tired when I filled the bug to actually notice that it was a
versioned library package I spoke about. Doh.

Cheers,
Sven

Andreas Henriksson  schrieb am Fr., 19. Feb. 2021, 21:22:

> Hello,
>
> On Fri, Feb 19, 2021 at 10:45:41AM +0100, Sven Mueller wrote:
> > Package: xapp
> > Version: 2.0.6-1
> > Severity: serious
> >
> > xapps-common is tagged as architecture:all, but the generated
> > xapp-sn-watcher.desktop included in it depends on the architecture it was
> > built on.
> [...]
> > 1) Move the autostart file into the respective libxapp1 packages (with
> the
> > binary)
> [...]
>
> Seems like Fabio Fantoni went with this solution and while I agree
> that desktop files should be shipped in the same package as the binary
> they launch in general, I also think it's very wrong to ship
> non-SO-verioned files in a libfooN package!
> (You'll most likely cause a file conflict bug when you later move
> to libxapp2 in the future the entire reason we put the SO version
> in the package name is to make the different versions co-installable,
> but if you put non-versioned files in the package then you're breaking
> that)
>
> The executable and desktop file should really be in a different
> (possibly newly added) package!
>
> Given we're in freeze it might be too late to introduce a new binary
> package (if that's needed), but fixing one bug by doing something
> wrong doesn't feel like debian style either. Wouldn't it be better
> to just ask the release team which solution they prefer and possibly
> get an exception for introducing a new binary package if needed?
>
> Regards,
> Andreas Henriksson
>
>

Processed: severity of 983106 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 983106 important
Bug #983106 [src:linux] linux-image-5.10.0-3-amd64: kernel 5.10.0-3-amd64 fails 
to boot system on Ryzen APU
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
983106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems