Bug#999334: android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std'

[Roger Shimizu]

control: tags -1 +help

I pushed a few patches to salsa that can resolve previously reported
ftbfs issues, however there're still other ftbfs issues.
For amd64, pbuilder reports:

:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
:1:1: note: while in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL art_quick_initialize_static_storage,
artInitializeStaticStorageFromCode, 0x20
^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1154:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL_FOR_CLINIT
art_quick_initialize_static_storage,
artInitializeStaticStorageFromCode
^
:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
:1:1: note: while in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL art_quick_resolve_type,
artResolveTypeFromCode, 0x20
^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1155:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL_FOR_CLINIT art_quick_resolve_type,
artResolveTypeFromCode
^
:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1156:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL
art_quick_resolve_type_and_verify_access,
artResolveTypeAndVerifyAccessFromCode
^
:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1157:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL art_quick_resolve_method_handle,
artResolveMethodHandleFromCode
^
:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1158:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL art_quick_resolve_method_type,
artResolveMethodTypeFromCode
^
:12:24: error: expected newline
.cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8)
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1159:1: note: while
in macro instantiation
ONE_ARG_SAVE_EVERYTHING_DOWNCALL art_quick_resolve_string,
artResolveStringFromCode
^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1282:24: error:
expected newline
.cfi_restore_state .cfi_def_cfa rsp,64
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1544:24: error:
expected newline
.cfi_restore_state .cfi_def_cfa rsp,16
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:1559:24: error:
expected newline
.cfi_restore_state .cfi_def_cfa rsp,16
   ^
art/runtime/arch/x86_64/quick_entrypoints_x86_64.S:2263:24: error:
expected newline
.cfi_restore_state .cfi_def_cfa rsp,80
   ^


for other ARCH, there might be other errors as well.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Re: Bug#999334: android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +help
Bug #999334 [src:android-platform-tools] android-platform-tools: FTBFS: error: 
no member named 'unique_lock' in namespace 'std'
Added tag(s) help.

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

Bug#1004230: libgpuarray: please drop upstreamtestsclblas until bug 949767 is fixed

[Paul Gevers]

Source: libgpuarray
Version: 0.7.6-8
Severity: serious
Justification: blocks other packages from migrating

Dear maintainer,

The autopkgtest of libgpuarray fails with libclblas-dev and libclblas2
installed due to bug #949767. Because those binaries are not available
in testing, the upstreamtests and upstreamtestsclblas are doing the
same in testing and pass. However, for migration testing, we add
unstable to the available suites and the binaries are pulled in and
fail (this was e.g. blocking glibc from migrating). Obviously this
switching behavior should be fixed in autopkgtest (I will file a bug
about that), but then the test will just fail in testing, which is
also RC.

Until clblas is available in testing (and bug #949767 fixed), please
drop the test.

Paul

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

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

Bug#1003907: fails to successfully associate

[Masashi Honma]

I will drop this patch, this does not solve the issue.


2022年1月23日(日) 10:30 Masashi Honma :
>
> 2022年1月19日(水) 19:13 Michael Biebl :
> > I tried the various versions from snapshots.d.o
> >
> > 2:2.9.0-23 - works
> > 2:2.9.0+git20200221+f65da0c-1 - works
> > 2:2.9.0+git20200517+dd2daf0-1 - doesn't work
> > 2:2.9.0+git20210909+a75fdcd-1 - doesn't work
> > 2:2.9.0+git20211018+2e122945fa53-1 - doesn't work
> > 2:2.9.0+git2026+0b853303ae31-1 - doesn't work
> > 2:2.10-1 - doesn't work
> >
> >
> > I then went on and disabled WPA2+WPA3 mode on the Wi-Fi router and set
> > it to WPA2 (CCMP).
> >
> > After that, the connection was established successfully with 2.10.
> >
> > If I remember correctly, my hardware doesn't support WPA3, but since I
> > enabled support for both WPA2+WPA3, it should fall back to WPA2.
> >
> > Obviously I'd like to keep WPA3 enabled for newer clients.
> >
> > Regards,
> > Michael
>
> Could you try this patch to latest wpa_supplicant ?
>
> diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
> index d37a994f9..626e26e4f 100644
> --- a/wpa_supplicant/wpa_supplicant.c
> +++ b/wpa_supplicant/wpa_supplicant.c
> @@ -7976,17 +7976,10 @@ int wpas_network_disabled(struct
> wpa_supplicant *wpa_s, struct wpa_ssid *ssid)
>
>  int wpas_get_ssid_pmf(struct wpa_supplicant *wpa_s, struct wpa_ssid *ssid)
>  {
> -   if (ssid == NULL || ssid->ieee80211w == 
> MGMT_FRAME_PROTECTION_DEFAULT) {
> -   if (wpa_s->conf->pmf == MGMT_FRAME_PROTECTION_OPTIONAL &&
> -   !(wpa_s->drv_enc & WPA_DRIVER_CAPA_ENC_BIP)) {
> -   /*
> -* Driver does not support BIP -- ignore pmf=1 default
> -* since the connection with PMF would fail and the
> -* configuration does not require PMF to be enabled.
> -*/
> -   return NO_MGMT_FRAME_PROTECTION;
> -   }
> +   if (!(wpa_s->drv_enc & WPA_DRIVER_CAPA_ENC_BIP))
> +   return NO_MGMT_FRAME_PROTECTION;
>
> +   if (ssid == NULL || ssid->ieee80211w == 
> MGMT_FRAME_PROTECTION_DEFAULT) {
> if (ssid &&
> (ssid->key_mgmt &
>  ~(WPA_KEY_MGMT_NONE | WPA_KEY_MGMT_WPS |
>
> Regards,
> Masashi Honma.

Bug#1000717: marked as done (supysonic: FTBFS on Python 3.10)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 23:50:44 -0500
with message-id <69af2bb2-3f79-6a8b-67af-02c031efb...@debian.org>
and subject line close supysonic FTBFS
has caused the Debian Bug report #1000717,
regarding supysonic: FTBFS on Python 3.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.)


-- 
1000717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supysonic
Version: 0.6.2+ds-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.10

supysonic FTBFS when using Python 3.10. This is caused by python3-pony
not supporting Python 3.10 yet.

=== python3.10 ===
tests (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 154, in
loadTestsFromName
module = __import__(module_name)
  File
"/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/__init__.py",
line 11, in 
from . import base
  File
"/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/base/__init__.py",
line 10, in 
from .test_cli import CLITestCase
  File
"/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/base/test_cli.py",
line 14, in 
from pony.orm import db_session
  File "/usr/lib/python3/dist-packages/pony/orm/__init__.py", line 3, in

from pony.orm.core import *
  File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 18, in

from pony.thirdparty.compiler import ast, parse
  File
"/usr/lib/python3/dist-packages/pony/thirdparty/compiler/__init__.py",
line 24, in 
from .transformer import parse, parseFile
  File
"/usr/lib/python3/dist-packages/pony/thirdparty/compiler/transformer.py", line
32, in 
import parser
ModuleNotFoundError: No module named 'parser'

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Just uploaded 0.7.1+ds-1 to unstable and forgot to close this bug in the
changelog.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1003003: marked as done (libqalculate FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jan 2022 04:48:41 +
with message-id 
and subject line Bug#1003003: fixed in libqalculate 3.22.0-3
has caused the Debian Bug report #1003003,
regarding libqalculate FTBFS on architectures where char is unsigned
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.)


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

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

...
FAIL: unittest
==


./tests/variables.batch - 11 tests passed


./tests/units.batch - 13 tests passed


Mismatch detected at line 42
char(0xD8)
expected ''Ø''
received '"Ø"'

Running all unit tests

Running unit tests from 'variables.batch'
Running unit tests from 'units.batch'
Running unit tests from 'strings.batch'
FAIL unittest (exit status: 1)


Testsuite summary for libqalculate 3.22.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/test-suite.log

make[4]: *** [Makefile:835: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: libqalculate
Source-Version: 3.22.0-3
Done: James Lu 

We believe that the bug you reported is fixed in the latest version of
libqalculate, 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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Lu  (supplier of updated libqalculate 
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: SHA384

Format: 1.8
Date: Sat, 22 Jan 2022 15:37:39 -0800
Source: libqalculate
Architecture: source
Version: 3.22.0-3
Distribution: unstable
Urgency: medium
Maintainer: Qalculate Team 
Changed-By: James Lu 
Closes: 1003003
Changes:
 libqalculate (3.22.0-3) unstable; urgency=medium
 .
   * Apply -fsigned-char to CXXFLAGS too (Closes: #1003003)
   * d/control:
 - Set libqalculate20-data section to oldlibs, add D: ${misc:Depends},
   remove duplicate Priority field
 - Set Rules-Requires-Root to no
   * d/copyright: update authors and years
Checksums-Sha1:
 2ba1d0063c90e5acd30635fed6ebd5b8b9b83f43 2501 libqalculate_3.22.0-3.dsc
 fb37e92eb82f4b99078f6589873506c74d4bb4ce 1661965 
libqalculate_3.22.0.orig.tar.gz
 e04a2127fae5ace02c1731df8c220819cfaa9c4f 8744 
libqalculate_3.22.0-3.debian.tar.xz
 6e63e631ada07554a7f977e91e8aa83be9fa013f 11754 
libqalculate_3.22.0-3_amd64.buildinfo
Checksums-Sha256:
 debd6142ea6b5cfad34e871d23df30d8ab536ca84ec4e8b840ba468d1a3a4434 2501 
libqalculate_3.22.0-3.dsc
 2128645c52a65bc77567669e0c01c0c409318bb2efc3a5e287450df5125aa263 1661965 
libqalculate_3.22.0.orig.tar.gz
 5ee741bf0e18e69c48510d8c72f8a811a03c61a836a25c3aefcf7b7624695007 8744 
libqalculate_3.22.0-3.debian.tar.xz
 ac1417a3dfdd10e5153059e48281a0e75e055d0115e07292d4e05f31208855ab 11754 
libqalculate_3.22.0-3_amd64.buildinfo
Files:
 a267ff8a42d2d0a1ed4e5065fcd95353 2501 math optional libqalculate_3.22.0-3.dsc
 752c1c2db53c0e9c9fdda7b2108d00b3 1661965 math optional 
libqalculate_3.22.0.orig.tar.gz
 98077168f1c8baaae56e01d0e6374a64 8744 math optional 
libqalculate_3.22.0-3.debian.tar.xz
 e326848dac28b1c4478a4abfa98732a7 11754 math optional 
libqalculate_3.22.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmHs2VwACgkQUAHhsJqj
dEs1iQ//XhbqLxVgsD3Ojgxoo+tuoPQ5kcooXyDOsRqfq/YdqGklqNbOAeyNfhKR
W3eljhxeWPwHIzd9KV8Dt40x9mk8RPe4nbjBvmOQIA75w9yBGSiauxTmZyvr/GCg
YRoG0vwfuu/PbvA3ziSUaNh0g/J47NbnKWIc6t+dtVRTpIp6UIFyJ4ZAemz/ZQKS
qMvXDZjvcs14ubExwPCoF0Bsub/EB5419OlkrJkGjQhBRz71g0+7AuiTAoxrt25v
/Fj8OG37qw3ugUwOrk7RW7brjvh/6MJLr0D2Q/8YXyY9I+ORwQi1OOw6xX0N61OG
0Fwo8RwZHoAwFHlx73/keTdHaP0hznNXYXPiRiZXnd8wd4ewuCUilwH4SXN/+QOd
kTw2BMYR400Us1UfOqE9kc/QeX20eML4fQnlTlrgQByrO61rXMWeWTRFFv2OHB6W
XgBaI0uk0LpftGPVCPFilGz3g

Bug#1004223: minetest-server: ItemStack meta injection vulnerability in Minetest 5.3

[Nils Dagsson Moskopp]

Package: minetest-server
Version: 5.3.0+repack-2.1
Severity: grave
Tags: patch security
Justification: user security hole
X-Debbugs-Cc: nils+debian-report...@dieweltistgarnichtso.net, Debian Security 
Team 

Dear Maintainer,


Minetest 5.3 contains a serious security issue by default.
The ItemStack meta is not sanitized properly by the server.

Is is therefore possible for clients to inject ItemStack meta.
It might be possible to backdoor the server by injecting Lua.

Computers running Minetest 5.3 are vulnerable to this exploit.
The following patch, part of Minetest 5.4, fixes the problem:

https://github.com/minetest/minetest/commit/b5956bde259faa240a81060ff4e598e25ad52dae


Greetings,
Nils Moskopp

-- System Information:
Debian Release: 11.2
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-6-686 (SMP w/2 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minetest-server depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc62.31-13+deb11u2
ii  libcurl3-gnutls  7.74.0-1.3+deb11u1
ii  libgcc-s110.2.1-6
ii  libgmp10 2:6.2.1+dfsg-1+deb11u1
ii  libjsoncpp24 1.9.4-4
ii  libleveldb1d 1.22-3
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-5.3
ii  libncursesw6 6.2+20201114-2
ii  libpq5   13.5-0+deb11u1
ii  libspatialindex6 1.9.3-2
ii  libsqlite3-0 3.34.1-3
ii  libstdc++6   10.2.1-6
ii  libtinfo66.2+20201114-2
ii  lsb-base 11.1.0
ii  minetest-data5.3.0+repack-2.1
ii  zlib1g   1:1.2.11.dfsg-2

minetest-server recommends no packages.

minetest-server suggests no packages.

-- no debconf information

Bug#1003907: fails to successfully associate

[Masashi Honma]

2022年1月19日(水) 19:13 Michael Biebl :
> I tried the various versions from snapshots.d.o
>
> 2:2.9.0-23 - works
> 2:2.9.0+git20200221+f65da0c-1 - works
> 2:2.9.0+git20200517+dd2daf0-1 - doesn't work
> 2:2.9.0+git20210909+a75fdcd-1 - doesn't work
> 2:2.9.0+git20211018+2e122945fa53-1 - doesn't work
> 2:2.9.0+git2026+0b853303ae31-1 - doesn't work
> 2:2.10-1 - doesn't work
>
>
> I then went on and disabled WPA2+WPA3 mode on the Wi-Fi router and set
> it to WPA2 (CCMP).
>
> After that, the connection was established successfully with 2.10.
>
> If I remember correctly, my hardware doesn't support WPA3, but since I
> enabled support for both WPA2+WPA3, it should fall back to WPA2.
>
> Obviously I'd like to keep WPA3 enabled for newer clients.
>
> Regards,
> Michael

Could you try this patch to latest wpa_supplicant ?

diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
index d37a994f9..626e26e4f 100644
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -7976,17 +7976,10 @@ int wpas_network_disabled(struct
wpa_supplicant *wpa_s, struct wpa_ssid *ssid)

 int wpas_get_ssid_pmf(struct wpa_supplicant *wpa_s, struct wpa_ssid *ssid)
 {
-   if (ssid == NULL || ssid->ieee80211w == MGMT_FRAME_PROTECTION_DEFAULT) {
-   if (wpa_s->conf->pmf == MGMT_FRAME_PROTECTION_OPTIONAL &&
-   !(wpa_s->drv_enc & WPA_DRIVER_CAPA_ENC_BIP)) {
-   /*
-* Driver does not support BIP -- ignore pmf=1 default
-* since the connection with PMF would fail and the
-* configuration does not require PMF to be enabled.
-*/
-   return NO_MGMT_FRAME_PROTECTION;
-   }
+   if (!(wpa_s->drv_enc & WPA_DRIVER_CAPA_ENC_BIP))
+   return NO_MGMT_FRAME_PROTECTION;

+   if (ssid == NULL || ssid->ieee80211w == MGMT_FRAME_PROTECTION_DEFAULT) {
if (ssid &&
(ssid->key_mgmt &
 ~(WPA_KEY_MGMT_NONE | WPA_KEY_MGMT_WPS |

Regards,
Masashi Honma.

Bug#984063: marked as done (insighttoolkit4: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 23:04:05 +
with message-id 
and subject line Bug#984063: fixed in insighttoolkit4 4.13.3withdata-dfsg2-1
has caused the Debian Bug report #984063,
regarding insighttoolkit4: ftbfs with GCC-11
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.)


-- 
984063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:insighttoolkit4
Version: 4.13.3withdata-dfsg1-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/insighttoolkit4_4.13.3withdata-dfsg1-4_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_vector.h:556:1: 
note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
  556 | VCL_TEMPLATE_EXPORT template  VNL_TEMPLATE_EXPORT 
std::istream& operator>>(std::istream &, vnl_vector  &);
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_vector_ref.h:26:1: 
note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
   26 | VCL_TEMPLATE_EXPORT template 
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_matrix.h:56:1: 
note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
   56 | VCL_TEMPLATE_EXPORT template  class vnl_vector;
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_matrix.h:57:1: 
note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
   57 | VCL_TEMPLATE_EXPORT template  class vnl_matrix;
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_vector_fixed.h:43:1:
 note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
   43 | VCL_TEMPLATE_EXPORT template  class 
vnl_vector_fixed;
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define VCL_TEMPLATE_EXPORT export
  |  ^~
/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/vnl_vector_fixed.h:44:1:
 note: in expansion of macro ‘VCL_TEMPLATE_EXPORT’
   44 | VCL_TEMPLATE_EXPORT template  class vnl_matrix_fixed;
  | ^~~
/<>/Modules/ThirdParty/VNL/src/vxl/vcl/vcl_compiler.h:114:30: 
warning: keyword ‘export’ is deprecated, and is ignored
  114 | # define V

Processed: Re: Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

[Debian Bug Tracking System]

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

> retitle 1002527 milter-greylist -u user does not correctly ensure user can 
> update greylist.db
Bug #1002527 [milter-greylist] postinst ignores USER from 
/etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist
Changed Bug title to 'milter-greylist -u user does not correctly ensure user 
can update greylist.db' from 'postinst ignores USER from 
/etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist'.
> quit
Stopping processing here.

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

Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

[Marvin Renich]

retitle 1002527 milter-greylist -u user does not correctly ensure user can 
update greylist.db
quit

* Adrian Bunk  [220120 21:43]:
> On Thu, Dec 23, 2021 at 02:12:04PM -0500, Marvin Renich wrote:
> >...
> > With an existing installation of milter-greylist set up to work with
> > chrooted postfix (i.e. USER="postfix" in /etc/default/milter-greylist),
> > every upgrade sets the owner of the directory /var/lib/milter-greylist
> > to "greylist" regardless of the setting of USER.  This effectively
> > breaks postfix, as it will no longer deliver mail until the problem is
> > resolved.
> > 
> > Note that the particular system hosting my mail server is still running
> > sysvinit, not systemd.  I do not know how milter-greylist configures the
> > user under systemd, but the postinst has "greylist" hardcoded, so I
> > suspect that if the sysadmin has configured a different user, this will
> > break under systemd, as well.
> >...
> 
> With systemd the problem likely doesn't exist since the user is 
> hardcoded also in the service file:
> 
> /lib/systemd/system/milter-greylist.service:
>   ExecStart=/usr/sbin/milter-greylist -u greylist

I'm not sure how that fixes anything.

When I first migrated from exim to postfix (many years ago), the
recommendation to get milter-greylist to work with Debian's chroot'ed
postfix was to run milter-greylist as user postfix (I believe to get the
permissions correct on the socket created by greylist, or perhaps to
allow it to create the socket in the postfix chroot, or both).

milter-greylist had a documented way to run it as a different user by
setting USER="postfix" in the above file.

I don't have milter-greylist running with postfix on a systemd system,
so I can't test this, but I suspect that if I copied
/lib/systemd/system/milter-greylist.service to /etc/systemd/system/ and
edited it to use -u postfix, and corrected the ownership and permissions
on /var/lib/milter-greylist, the next upgrade would still clobber the
ownership, thus breaking postfix.

Doing some research (just now), I think I can get this working reliably
across milter-greylist upgrades by adding user postfix to the group
greylist, and running milter-greylist with its default user (greylist).
I will try this when I have a chance.  But this is only a workaround for
the bug.  As long as the package supports running as a different user,
an upgrade should not change ownership of /var/lib/milter-greylist.

More research has narrowed down the problem.  This is not an
installation problem, but a failure of the "-u" option to perform its
documented behavior:

  Make sure this user (and group) has write access to greylist.db.

Because every write to greylist.db is (at least seems to be) done by
writing a temporary file in the same directory and then atomically
renaming it, the above promise is equivalent to ensuring that the user
and group has write access to the containing directory.  This is not
done at all.  I am retitling this bug appropriately.

...Marvin

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

[Paul Gevers]

Hi,

On Thu, 30 Sep 2021 11:07:17 +0200 Paul Gevers  wrote:

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


Ping.

If nobody is going to fix this issue, I am going to upload the package 
removing the autopkgtest soon. This issue is blocking migration to 
testing for too long. The package can't be easily removed because it's a 
key package.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004216: missing directory: /usr/share/fonts/truetype/

[Paul Gevers]

Source: fonts-ipaexfont
Version: 00401-3
Followup-For: Bug #1004216

Dear maintainer,

I fixed the issue with the attached debdiff, which I uploaded to DELAYED/10. 
Please let me know if I should cancel my upload.

Paul
diff --git a/debian/changelog b/debian/changelog
index e2d00aa..f21e606 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+fonts-ipaexfont (00401-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Ensure that /usr/share/fonts/truetype/ exists when update-alternatives
+runs (Closes: #1004216)
+
+ -- Paul Gevers   Sat, 22 Jan 2022 22:25:47 +0100
+
 fonts-ipaexfont (00401-4) unstable; urgency=medium
 
   * debian/control
diff --git a/debian/fonts-ipaexfont-gothic.dirs 
b/debian/fonts-ipaexfont-gothic.dirs
new file mode 100644
index 000..60e95ec
--- /dev/null
+++ b/debian/fonts-ipaexfont-gothic.dirs
@@ -0,0 +1 @@
+usr/share/fonts/truetype/
diff --git a/debian/fonts-ipaexfont-mincho.dirs 
b/debian/fonts-ipaexfont-mincho.dirs
new file mode 100644
index 000..60e95ec
--- /dev/null
+++ b/debian/fonts-ipaexfont-mincho.dirs
@@ -0,0 +1 @@
+usr/share/fonts/truetype/

Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

[Vasyl Gello]

Control: severity -1 important

Hi Stephen!

Thanks for the bugreport! However, the "grave" severity is too high for it 
given I see the following issues:

* Your logfile attached in the previous message pasted to Kodi hastebin ( 
https://paste.kodi.tv/ovifonuziy.kodi ) shows
the presence of banned addons (marked in red). You should remove them and 
reproduce the issue without them.

* The logfile is not a debug log at all. Also there is no stacktrace in it. You 
need to install gdb and kodi-bin-dbgsym from
Debian debug repository according to https://wiki.debian.org/HowToGetABacktrace 
and run Kodi under gdb, reproduce
the crash and run "bt full" to get a proper stacktrace.

* The kernel you run is 5.16.2-xanmod1, which is not an official Debian kernel. 
Did you also update Mesa from external
repos by chance? If you did, this might be an issue, too.

Please try running Kodi with default Debian kernel and 3D stack and capture the 
proper backtrace so we can fix the segfault.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Processed: Re: Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1004214 [kodi] kodi: Segfaults on menu  selection
Severity set to 'important' from 'grave'

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

Bug#995351: src:fonts-ipaexfont: piuparts detected issue: /usr/share/fonts/truetype/ doesn't exist

[Paul Gevers]

Control: clone -1 -2
Control: reopen -2
Control: retitle -2 missing directory: /usr/share/fonts/truetype/

Hi,

I checked the piuparts log, and it seems to me that the alternatives 
methode is used in a directory that's not guaranteed to exist. I think 
the solution to the problem is trivial.


Paul

https://piuparts.debian.org/sid/fail/fonts-ipaexfont-gothic_00401-4.log

  Setting up fonts-ipaexfont-gothic (00401-4) ...
  update-alternatives: using 
/usr/share/fonts/opentype/ipaexfont-gothic/ipaexg.ttf to provide 
/usr/share/fonts/truetype/fonts-japanese-gothic.ttf 
(fonts-japanese-gothic.ttf) in auto mode
  update-alternatives: error: error creating symbolic link 
'/usr/share/fonts/truetype/fonts-japanese-gothic.ttf.dpkg-tmp': No such 
file or directory

  dpkg: error processing package fonts-ipaexfont-gothic (--configure):
   installed fonts-ipaexfont-gothic package post-installation script 
subprocess returned error exit status 2

  Errors were encountered while processing:
   fonts-ipaexfont-gothic


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: src:fonts-ipaexfont: piuparts detected issue: /usr/share/fonts/truetype/ doesn't exist

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #995351 {Done: Paul Gevers } [src:fonts-ipaexfont] 
src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts 
regression
Bug 995351 cloned as bug 1004216
> reopen -2
Bug #1004216 {Done: Paul Gevers } [src:fonts-ipaexfont] 
src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts 
regression
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fonts-ipaexfont/00401-4.
> retitle -2 missing directory: /usr/share/fonts/truetype/
Bug #1004216 [src:fonts-ipaexfont] src:fonts-ipaexfont: fails to migrate to 
testing for too long: piuparts regression
Changed Bug title to 'missing directory: /usr/share/fonts/truetype/' from 
'src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts 
regression'.

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

Bug#997845: marked as done (growlight: autopkgtest regression: log repeats until it times out)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 21:52:05 +0100
with message-id 
and subject line Re: Bug#997845: bug 997845
has caused the Debian Bug report #997845,
regarding growlight: autopkgtest regression: log repeats until it times out
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.)


-- 
997845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: growlight
Version: 1.2.37-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression timesout

Dear maintainer(s),

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

   passfail
growlight  from testing1.2.37-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. The message is
repeated over and over again until autopkgtest timesout.

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=growlight

https://ci.debian.net/data/autopkgtest/testing/amd64/g/growlight/16172667/log.gz

growlight 1.2.37
libblkid 2.37.2, libpci 0x30700, libdm 1.02.175 (2021-01-08)
No ZFS support in this build.
Watching /sys/class/block/ on fd 1
scanning /sys/class/block/ on 8...
nvme0n1 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1
Numa node 0 (/sys/devices/pci:00/:00:04.0//numa_node)
/sys/class/block/ blocks on 4 devices for up to 1s
Controller: Amazon.com, Inc. NVMe EBS Controller
nvme0n1p15 ->
../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p15
nvme0n1p1 ->
../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1
Controller: Amazon.com, Inc. NVMe EBS Controller
Not recursing on partition nvme0n1p15
Couldn't get a revision for nvme0n1 (No such file or directory)
Model: Amazon Elastic Block Store revision n/a S/N n/a type 0
Controller: Amazon.com, Inc. NVMe EBS Controller
nvme0n1p14 ->
../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p14
Not recursing on partition nvme0n1p1
Controller: Amazon.com, Inc. NVMe EBS Controller
Not recursing on partition nvme0n1p14
Partition 1 at nvme0n1p1
Partition 14 at nvme0n1p14
Partition 15 at nvme0n1p15
Couldn't open /dev/nvme0n1 (No such file or directory)
Couldn't inotify on /dev/md/ (No such file or directory)
Couldn't inotify on /dev/disk/by-path/ (No such file or directory)
Couldn't inotify on /dev/disk/by-id/ (No such file or directory)
virtual filesystem support: sysfs
virtual filesystem support: tmpfs
virtual filesystem support: bdev
virtual filesystem support: proc
virtual filesystem support: cgroup
virtual filesystem support: cgroup2
virtual filesystem support: cpuset
virtual filesystem support: devtmpfs
virtual filesystem support: debugfs
virtual filesystem support: tracefs
virtual filesystem support: securityfs
virtual filesystem support: sockfs
virtual filesystem support: bpf
virtual filesystem support: pipefs
virtual filesystem support: ramfs
virtual filesystem support: hugetlbfs
virtual filesystem support: devpts
filesystem support: ext3
filesystem support: ext2
filesystem support: ext4
virtual filesystem support: mqueue
virtual filesystem support: pstore
virtual filesystem support: autofs
virtual filesystem support: configfs
filesystem support: fuseblk
virtual filesystem support: fuse
virtual filesystem support: fusectl
filesystem support: vfat
virtual filesystem support: binfmt_misc
virtual filesystem support: overlay
virtual filesystem support: rpc_pipefs
virtual filesystem support: nfsd
nvme0n1p1 ->
../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1
Controller: Amazon.com, Inc. NVMe EBS Controller
Not recursing on partition nvme0n1p1
nvme0n1p1 ->
../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1
Controller: Amazon.com, Inc. NVMe EBS Controller
Not recursing on partition nvme0n1p1
Couldn't read link at /sys/class/block/cgroup (No such file or directory)
virtfs cgroup2 at /sys/fs/cgroup
Couldn't read link at /sys/class/block/lxcfs (No such file or directory)
virtfs fuse.lxcfs at /proc/cpuinfo
C

Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

[SDA]

Output from starting in terminal:

failed to open zone.tab
libva info: VA-API version 1.13.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_13
libva info: va_openDriver() returns 0
Segmentation fault

Attaching Kodi's own bugreport
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Sat Jan 22 15:28:41 EST 2022
 Kodi Options: 
 Arch: x86_64
 Kernel: Linux 5.16.2-xanmod1 #0~git20220120.a17cd44 SMP Thu Jan 20 21:24:46 
UTC 2022
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
gdb not installed, can't get stack trace.
# END STACK TRACE ###

# LOG FILE ##

2022-01-22 15:27:49.124 T:5953 INFO : 
---
2022-01-22 15:27:49.124 T:5953 INFO : Starting Kodi from Debian 
(19.3 Debian package version: 2:19.3+dfsg1-1+b1). Platform: Linux x86 64-bit
2022-01-22 15:27:49.124 T:5953 INFO : Using Release Kodi from 
Debian x64
2022-01-22 15:27:49.124 T:5953 INFO : Kodi from Debian compiled 
2021-12-21 by GCC 11.2.0 for Linux x86 64-bit version 5.15.5 (331525)
2022-01-22 15:27:49.124 T:5953 INFO : Running on Debian GNU/Linux 
bookworm/sid unstable, kernel: Linux x86 64-bit version 5.16.2-xanmod1
2022-01-22 15:27:49.124 T:5953 INFO : FFmpeg version/source: 
4.4.1-3
2022-01-22 15:27:49.124 T:5953 INFO : Host CPU: AMD Ryzen 7 3700X 
8-Core Processor , 16 cores available
2022-01-22 15:27:49.124 T:5953 INFO : special://xbmc/ is mapped 
to: /usr/share/kodi
2022-01-22 15:27:49.124 T:5953 INFO : special://xbmcbin/ is mapped 
to: /usr/lib/x86_64-linux-gnu/kodi
2022-01-22 15:27:49.124 T:5953 INFO : special://xbmcbinaddons/ is 
mapped to: /usr/lib/x86_64-linux-gnu/kodi/addons
2022-01-22 15:27:49.124 T:5953 INFO : special://masterprofile/ is 
mapped to: /home/stephen/.kodi/userdata
2022-01-22 15:27:49.124 T:5953 INFO : special://envhome/ is mapped 
to: /home/stephen
2022-01-22 15:27:49.124 T:5953 INFO : special://home/ is mapped 
to: /home/stephen/.kodi
2022-01-22 15:27:49.124 T:5953 INFO : special://temp/ is mapped 
to: /home/stephen/.kodi/temp
2022-01-22 15:27:49.124 T:5953 INFO : special://logpath/ is mapped 
to: /home/stephen/.kodi/temp
2022-01-22 15:27:49.124 T:5953 INFO : The executable running is: 
/usr/lib/x86_64-linux-gnu/kodi/kodi.bin
2022-01-22 15:27:49.124 T:5953 INFO : Local hostname: debian01
2022-01-22 15:27:49.124 T:5953 INFO : Log File is located: 
/home/stephen/.kodi/temp/kodi.log
2022-01-22 15:27:49.124 T:5953 INFO : 
---
2022-01-22 15:27:49.124 T:5953 INFO : loading settings
2022-01-22 15:27:49.124 T:5953 INFO : special://profile/ is mapped 
to: special://masterprofile/
2022-01-22 15:27:49.142 T:5953 INFO : No settings file to load 
(special://xbmc/system/advancedsettings.xml)
2022-01-22 15:27:49.142 T:5953 INFO : No settings file to load 
(special://masterprofile/advancedsettings.xml)
2022-01-22 15:27:49.142 T:5953 INFO : Default Video Player: 
VideoPlayer
2022-01-22 15:27:49.142 T:5953 INFO : Default Audio Player: 
paplayer
2022-01-22 15:27:49.142 T:5953 INFO : Disabled debug logging due 
to GUI setting. Level 0.
2022-01-22 15:27:49.142 T:5953 INFO : Log level changed to "INFO"
2022-01-22 15:27:49.142 T:5953 INFO : CMediaSourceSettings: 
loading media sources from special://masterprofile/sources.xml
2022-01-22 15:27:49.142 T:5953 INFO : creating subdirectories
2022-01-22 15:27:49.142 T:5953 INFO : userdata folder: 
special://masterprofile/
2022-01-22 15:27:49.142 T:5953 INFO : recording folder: 
2022-01-22 15:27:49.142 T:5953 INFO : screenshots folder: 
/home/stephen/Pictures/
2022-01-22 15:27:49.143 T:5953 INFO : Running database version 
Addons33
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
audioencoder.kodi.builtin.aac v1.0.2 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
audioencoder.kodi.builtin.wma v1.0.2 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
context.elementum v0.0.10 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
context.trakt.addtowatchlist v1.1.0+matrix.1 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
context.trakt.contextmenu v1.1.0+matrix.1 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
context.trakt.rate v1.1.0+matrix.1 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
context.trakt.watched v1.1.0+matrix.1 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 
game.controller.default v1.0.19 installed
2022-01-22 15:27:49.161 T:5953 INFO : CAddonMgr::FindAddons: 

Processed: update bts with meta info

[Debian Bug Tracking System]

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

> reassign 1004094 src:python-imageio 2.4.1-3
Bug #1004094 {Done: Graham Inggs } [src:pillow, 
src:python-imageio] pillow breaks python-imageio autopkgtest: assert (150, 200, 
3) == (150, 200, 4)
Bug reassigned from package 'src:pillow, src:python-imageio' to 
'src:python-imageio'.
No longer marked as found in versions pillow/9.0.0-1 and python-imageio/2.4.1-3.
Ignoring request to alter fixed versions of bug #1004094 to the same values 
previously set
Bug #1004094 {Done: Graham Inggs } [src:python-imageio] 
pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4)
Marked as found in versions python-imageio/2.4.1-3.
> affects 1004094 src:pillow
Bug #1004094 {Done: Graham Inggs } [src:python-imageio] 
pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4)
Added indication that 1004094 affects src:pillow
> fixed 1004094 2.4.1-4
Bug #1004094 {Done: Graham Inggs } [src:python-imageio] 
pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4)
Marked as fixed in versions python-imageio/2.4.1-4.
> thanks
Stopping processing here.

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

Bug#1004214: kodi: Segfaults on menu selection

[SDA]

Package: kodi
Version: 2:19.3+dfsg1-1+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: marathon.duran...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
Start up Kodi and select a submenu item seems to trigger the segfault

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?




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

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

Versions of packages kodi depends on:
ii  kodi-bin   2:19.3+dfsg1-1+b1
ii  kodi-data  2:19.3+dfsg1-1

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:19.3+dfsg1-1
ii  kodi-visualization-spectrum 19.0.0+ds1-2

kodi suggests no packages.

-- no debconf information

Processed: Re: Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1004204 [libqt5webenginecore5] libqt5webenginecore5: Fails to upgrade to 
Sid version
Severity set to 'important' from 'critical'

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

Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version

[Diederik de Haas]

Control: severity -1 important

On Saturday, 22 January 2022 19:02:27 CET Elijah wrote:
> pkg-deb (subprocess): decompressing archive
> '/var/cache/apt/archives/libqt5webenginecore5_5.15.8+dfsg-1_amd64.deb'
> (size=39497412) member 'data.tar': lzma error: compressed data is corrupt

What happens if you delete that file and do a new apt update && apt upgrade?

On my Sid system the upgrade to 5.15.8+dfsg-1 was successful, so downgrading 
the severity to important.

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

Bug#1004212: berkeley-abc: autopkgtest regression on arm64, i386 and ppc64el: Segmentation fault

[Paul Gevers]

Source: berkeley-abc
Version: 1.01+20211229git48498af+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
berkeley-abc   from testing1.01+20211229git48498af+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration 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=berkeley-abc

https://ci.debian.net/data/autopkgtest/testing/arm64/b/berkeley-abc/18577291/log.gz

Segmentation fault
autopkgtest [00:13:20]: test can-show-help



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004211: dirty.js: autopkgtest failure on armhf and ppc64el

[Paul Gevers]

Source: dirty.js
Version: 1.1.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package dirty.js, great. 
However, it fails on armhf and ppc64el. Currently this failure is 
blocking the migration to testing [1]. Can you please investigate the 
situation and fix it?


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

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=dirty.js

https://ci.debian.net/data/autopkgtest/testing/armhf/d/dirty.js/18345360/log.gz

# Using ./package.(json|yaml)
# Node module name is dirty
# Build files found: Makefile
# Test files found: test
# Files/dir to be installed from source: test Makefile
# Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest-lxc.y6211edt/downtmp/autopkgtest_tmp/smokea4xGpX/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest-lxc.y6211edt/downtmp/autopkgtest_tmp/smokea4xGpX/debian/tests/pkg-js/test'

# Searching module in /usr/lib/nodejs/dirty
# Searching module in /usr/lib/*/nodejs/dirty
# Searching module in /usr/share/nodejs/dirty
# Found /usr/share/nodejs/dirty
# Searching files to link in /usr/share/nodejs/dirty
'./index.js' -> '/usr/share/nodejs/dirty/index.js'
'./lib' -> '/usr/share/nodejs/dirty/lib'
'./package.json' -> '/usr/share/nodejs/dirty/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ mocha test/test-api.js test/test-nostore.js test/test-system.js 
test/test-types.js



  dirty api (transient mode)
undefined constructor without new
dirty constructor
  undefined is an event emitter
  undefined is a dirty
events
  undefined should fire load
  undefined should fire drain after write
accessors
  undefined .set should trigger callback
  undefined .get should return value
  undefined .path is valid
  undefined .forEach runs for all
  undefined .rm removes key/value pair
  undefined .rm of unknown key is a no-op
N/A in transient mode
  undefined will reload file from disk
db file close
N/A in transient mode
  undefined close

  dirty api (persistent mode)
undefined constructor without new
dirty constructor
  undefined is an event emitter
  undefined is a dirty
events
  undefined should fire load
  undefined should fire drain after write
accessors
  undefined .set should trigger callback
  undefined .get should return value
  undefined .path is valid
  undefined .forEach runs for all
  undefined .rm removes key/value pair
  undefined .rm of unknown key is a no-op
  undefined will reload file from disk
db file close
  undefined close

  test-load-event
undefined should fire load event

  test-set-callback
undefined should trigger callback on set

  test-flush
undefined should fire drain event on write
undefined should write to disk appropriately

  test-for-each
undefined should return each doc key and contents

  test-load
undefined should load after write to disk

  test-size
undefined should be equal to number of keys set

  test-chaining-of-constructor
1) should allow .on load to chain to constructor

  test-update
undefined updater receives old value and sets new value

  test-types
keys
  - should prevent storage of an undefined key
  - should not return an undefined key


  34 passing (39ms)
  2 pending
  1 failing

  1) test-chaining-of-constructor
   should allow .on load to chain to constructor:

  AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

1 !== 2

  + expected - actual

  -1
  +2
at Context. (test/test-system.js:114:12)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)



autopkgtest [15:12:29]: test pkg-js-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:datalad: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.15.3-1
Bug #1004210 [src:datalad] src:datalad: fails to migrate to testing for too 
long: FTBFS
The source 'datalad' and version '0.15.3-1' do not appear to match any binary 
packages
Marked as fixed in versions datalad/0.15.3-1.
Bug #1004210 [src:datalad] src:datalad: fails to migrate to testing for too 
long: FTBFS
Marked Bug as done
> block -1 by 1002359
Bug #1004210 {Done: Paul Gevers } [src:datalad] src:datalad: 
fails to migrate to testing for too long: FTBFS
1004210 was not blocked by any bugs.
1004210 was not blocking any bugs.
Added blocking bug(s) of 1004210: 1002359

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

Bug#1004210: src:datalad: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: datalad
Version: 0.15.0-2
Severity: serious
Control: close -1 0.15.3-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1002359

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:datalad has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=datalad



OpenPGP_signature
Description: OpenPGP digital signature

Bug#996375: marked as done (chromium build-depends on removed package.)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 19:17:18 +
with message-id 
and subject line Bug#996375: fixed in chromium 97.0.4692.71-0.1~deb11u1
has caused the Debian Bug report #996375,
regarding chromium build-depends on removed package.
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.)


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

Package: chromium
Version: 93.0.4577.82-1
Severity: serious

chromium build-depends on python-jinja2 which is no longer built by the 
jinja2 source package.
It is still present in unstable as a cruft package but is completely 
gone from testing.


--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 97.0.4692.71-0.1~deb11u1
Done: Andres Salomon 

We believe that the bug you reported is fixed in the latest version of
chromium, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andres Salomon  (supplier of updated chromium 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: Thu, 13 Jan 2022 18:30:21 -0500
Source: chromium
Architecture: source
Version: 97.0.4692.71-0.1~deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Chromium Team 
Changed-By: Andres Salomon 
Closes: 861796 942962 955540 995212 996375
Changes:
 chromium (97.0.4692.71-0.1~deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload.
   * Stop building chromium's bunded gn and instead build-dep on generate-ninja.
   * Drop numerous patches related to gcc building, since we just build w/ 
clang.
   * Use python3 as default instead of relying on python2
 (closes: #942962, #996375).
   * Enable the ozone backend in the build (closes: #955540).
   * Automatically detect & enable Wayland support when launching chromium
 (closes: #861796).
   * Rename crashpad_handler to chrome_crashpad_handler.
   * No longer hardcode desktop GL implementation as default - it causes
 the chromium compositor's draw buffer to fill up & crash on my system.
   * Enable official builds.
   * New upstream stable release (closes: #995212).
 - CVE-2022-0096: Use after free in Storage. Reported by Yangkang
   (@dnpushme) of 360 ATA
 - CVE-2022-0097: Inappropriate implementation in DevTools. Reported by
   David Erceg
 - CVE-2022-0098: Use after free in Screen Capture. Reported by
   @ginggilBesel
 - CVE-2022-0099: Use after free in Sign-in. Reported by Rox
 - CVE-2022-0100: Heap buffer overflow in Media streams API. Reported by
   Cassidy Kim of Amber Security Lab, OPPO Mobile Telecommunications
   Corp. Ltd.
 - CVE-2022-0101: Heap buffer overflow in Bookmarks. Reported by raven
   (@raid_akame)
 - CVE-2022-0102: Type Confusion in V8. Reported by Brendon Tiszka
 - CVE-2022-0103: Use after free in SwiftShader. Reported by Abraruddin
   Khan and Omair
 - CVE-2022-0104: Heap buffer overflow in ANGLE. Reported by Abraruddin
   Khan and Omair
 - CVE-2022-0105: Use after free in PDF. Reported by Cassidy Kim of Amber
   Security Lab, OPPO Mobile Telecommunications Corp. Ltd.
 - CVE-2022-0106: Use after free in Autofill. Reported by Khalil Zhani
 - CVE-2022-0107: Use after free in File Manager API. Reported by raven
   (@raid_akame)
 - CVE-2022-0108: Inappropriate implementation in Navigation. Reported by
   Luan Herrera (@lbherrera_)
 - CVE-2022-0109: Inappropriate implementation in Autofill. Reported by
   Young Min Kim (@ylemkimon), CompSec Lab at Seoul National University
 - CVE-2022-0110: Incorrect security UI in Autofill. Reported by
   Alesandro Ortiz
 - CVE-2022-0111: Inappropriate implementation in Navigation. Reported by
   garygreen
 - CVE-2022-0112: Incorrect security UI in Browser UI. Reported by Thomas
   Orlita
 - CVE-2022-0113: Inappropriate implementation in Blink. Reported by Luan
   Herrera (@lbherrera_)
 - CVE-2022-0114: Out of bounds memory access in Web Serial. Reported by
   Looben Yang
 - CVE-2022

Bug#995212: marked as done (chromium: Update to version 94.0.4606.61 (security-fixes))

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 19:17:17 +
with message-id 
and subject line Bug#995212: fixed in chromium 97.0.4692.71-0.1~deb11u1
has caused the Debian Bug report #995212,
regarding chromium: Update to version 94.0.4606.61 (security-fixes)
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.)


-- 
995212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 93.0.4577.82-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I updated my google-chrome-stable package to version 94.0.4606.61-1 on my 
Debian/unstable AMD64 system.

Debian's security-tracker for chromium [1] package shows several CVE security 
issues not fixed.

Open issues:

Bug stretch buster  bullseyebookworm
sid Description
CVE-2021-37973  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37972  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37971  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37970  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37969  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37968  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37967  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37966  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37965  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37964  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37963  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37962  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37961  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37960  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37959  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37958  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37957  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37956  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable

For more details also see "Stable Channel Update for Desktop" at [2].

Please upgrade chromium from v93.x to v94.x.

Thanks.

Regards,
- Sedat -

[1] https://security-tracker.debian.org/tracker/source-package/chromium
[2] https://chromereleases.googleblog.com/search/label/Stable%20updates
[3] 
https://www.heise.de/news/Google-schliesst-19-Sicherheitsluecken-in-Chrome-6199412.html
 (German)

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common 93.0.4577.82-1
ii  libasound2  1.2.5.1-1
ii  libatk-bridge2.0-0  2.38.0-2
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  11.2.0-8
ii  libatspi2.0-0   2.42.0-1
ii  libavcodec587:4.4-6+b2
ii  libavformat58   7:4.4-6+b2
ii  libavutil56 7:4.4-6+b2
ii  libc6   2.32-4
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-7
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.107-8
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.4.1-2+b1
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgbm1 21.2.2-1
ii  libgcc-s1   11.2.0-8
ii  libglib2.0-02.70.0-1+b1
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-7
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.32-1
ii  libnss3  

Bug#1003243: marked as done (wordpress: WordPress 5.8.3 Security Release)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 19:18:06 +
with message-id 
and subject line Bug#1003243: fixed in wordpress 5.7.5+dfsg1-0+deb11u1
has caused the Debian Bug report #1003243,
regarding wordpress: WordPress 5.8.3 Security Release
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.)


-- 
1003243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 5.8.2+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

WordPress have released version 5.8.3 which fixes 4 security bugs.
https://wordpress.org/news/2022/01/wordpress-5-8-3-security-release/

 * An issue with stored XSS through post slugs.
   CVE-2022-21662 - Stored XSS through authenticated users
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-699q-3hj9-889w
   https://hackerone.com/reports/425342


 * An issue with Object injection in some multisite installations.
   CVE-2022-21663 - Authenticated Object Injection in Multisites
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jmmq-m8p8-332h
   https://hackerone.com/reports/541469


 * A SQL injection vulnerability in WP_Query.
   CVE-2022-21661 - WordPress: SQL Injection through WP_Query
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-6676-cqfm-gw84
   https://hackerone.com/reports/1378209

 * A SQL injection vulnerability in WP_Meta_Query
   CVE-2022-21664 - SQL injection due to improper sanitization in WP_Meta_Query
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jp3p-gw8h-6x86
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 5.7.5+dfsg1-0+deb11u1
Done: Craig Small 

We believe that the bug you reported is fixed in the latest version of
wordpress, 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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress 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: Fri, 07 Jan 2022 17:51:21 +1100
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen 
wordpress-theme-twentytwenty wordpress-theme-twentytwentyone
Architecture: source all
Version: 5.7.5+dfsg1-0+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentynineteen - weblog manager - twentynineteen theme files
 wordpress-theme-twentytwenty - weblog manager - twentytwenty theme files
 wordpress-theme-twentytwentyone - weblog manager - twentytwentyone theme files
Closes: 1003243
Changes:
 wordpress (5.7.5+dfsg1-0+deb11u1) bullseye-security; urgency=high
 .
   * Upstream security release Closes: #1003243
  - CVE-2022-21662 - Stored XSS through authenticated users
  - CVE-2022-21663 - Authenticated Object Injection in Multisites
  - CVE-2022-21661 - WordPress: SQL Injection through WP_Query
  - CVE-2022-21664 - SQL injection due to improper sanitization
in WP_Meta_Query
   * WordPress 5.7.4 just had a removal of an old CA certificate
 which isn't used in Debian installations
Checksums-Sha1:
 5fc7a817e1d19a1cd206568483082e3f0d40ec2d 2424 
wordpress_5.7.5+dfsg1-0+deb11u1.dsc
 daebd4d240df13721e9395c8a126f9410ff72141 11472936 
wordpress_5.7.5+dfsg1.orig.tar.xz
 93a123e4d40ba68c6361a3714a701dddf62e60fa 6825032 
wordpress_5.7.5+dfsg1-0+deb11u1.debian.tar.xz
 ca3eb8a80f927766d96af427915f28c8fbeb9a45 4385616 
wordpress-l10n_5.7.5+dfsg1-0+deb11u1_all.deb
 414551ed3c22ef0882cf6238f1cb5bf98e7edf9c 500644 
wordpress-theme-twentynineteen_5.7.5+dfsg1-0+deb11u1_all.deb
 19c5eb6537ac6af7709c1f50786f1ad8dbfc1244 772532 
wordpress-theme-twentytwenty_5.7.5+dfsg1-0+deb11u1_all.deb
 431c4e3e0577c6439314de81ee8827707a18da6c 2586056 
wordpress-theme-twentytwentyone_5.7.5+dfsg1-0+deb11u1_all.deb
 a71bbc5755672e7c40fc71a50874082230668ca9 7779360 
wordpress_5.7.5+dfsg1-0+deb11u1_all.deb
 004a20048f2

Bug#984063: [Debian-med-packaging] Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

[Andreas Tille]

Thanks a lot!

Am Sat, Jan 22, 2022 at 07:15:25PM +0100 schrieb Étienne Mollier:
> Hi Andreas,
> 
> Andreas Tille, on 2022-01-16:
> > I think the roadmap that ITK4 will be deleted as soon as possible
> > is clear.  However, if it might serve as an intermediate means
> > to support some remaining dependencies temporarily I think it
> > is OK to do some tricks that would not be acceptable as long
> > term means.
> 
> I have been working on a rewrap of insighttoolkit4 to include
> the embedded tiff library, and with all the previous patching to
> address the initial issue described in this bug, the build went
> through.  The package should be in shape for upload tomorrow.
> 
> Have a nice day,  :)
> -- 
> Étienne Mollier 
> Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
> Sent from /dev/pts/6, please excuse my verbosity.
> On air: Lemur Voice - Solilocide



-- 
http://fam-tille.de

Bug#997829: marked as done (libipc-shareable-perl: autopkgtest regression on armhf and i386)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 18:19:07 +
with message-id 
and subject line Bug#997829: fixed in libipc-shareable-perl 1.06-2
has caused the Debian Bug report #997829,
regarding libipc-shareable-perl: autopkgtest regression on armhf and i386
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.)


-- 
997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libipc-shareable-perl
Version: 1.06-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
libipc-shareable-perl  from testing1.06-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The issue
seems to be related to 32 bit archs.

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=libipc-shareable-perl

https://ci.debian.net/data/autopkgtest/testing/armhf/libi/libipc-shareable-perl/16170185/log.gz

t/65-seg_size.t .. ok 1 - size larger than MAX croaks ok
ok 2 - ...and error is sane
IPC_MEM env var not set, skipping the exhaust memory test
not ok 3 - We croak if size is greater than max RAM

#   Failed test 'We croak if size is greater than max RAM'
#   at t/65-seg_size.t line 52.
#  got: '1'
# expected: undef
not ok 4 - ...and error is sane

#   Failed test '...and error is sane'
#   at t/65-seg_size.t line 54.
#   ''
# doesn't match '(?^:Cannot allocate memory|Out of memory|Invalid
argument)'
ok 5 - size param is the same as the segment size
ok 6 - actual size in bytes ok if sending in custom size
1..6
# Looks like you failed 2 tests of 6.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/6 subtests

[...]

t/85-spawn_object_contains_data.t  skipped: IPC_SPAWN_TEST env var
not set
t/86-unspawn_object_contains_data.t .. skipped: IPC_SPAWN_TEST env var
not set
t/91-pod_linkcheck.t . skipped: Author test:
RELEASE_TESTING not set
t/93-manifest.t .. skipped: Author test:
RELEASE_TESTING not set

Test Summary Report
---
t/65-seg_size.t(Wstat: 512 Tests: 6 Failed: 2)
  Failed tests:  3-4
  Non-zero exit status: 2
Files=36, Tests=412, 16 wallclock secs ( 0.20 usr  0.36 sys +  4.66 cusr
 4.92 csys = 10.14 CPU)
Result: FAIL
autopkgtest [10:47:54]: test autodep8-perl-build-deps




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libipc-shareable-perl
Source-Version: 1.06-2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libipc-shareable-perl, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libipc-shareable-perl 
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, 22 Jan 2022 19:06:22 +0100
Source: libipc-shareable-perl
Architecture: source
Version: 1.06-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 997829
Changes:
 libipc-shareable-perl (1.06-2) unstable; urgency=medium
 .
   * Add patch to mark tests as TODO which fail on 32bit architectures.
 Thanks to Niko Tyni for the analysis. (Closes: #997829)
   * Update years of packaging copyright.
Checksums-Sha1:
 b7460bec2d9084438526ce51397be1dd4ec4df63 2522 libipc-shareable-perl_1.06-2.dsc
 fdccae83885f86366bbe16ab1b4f2d85150fb972 4392 

Bug#997829: marked as pending in libipc-shareable-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #997829 in libipc-shareable-perl 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/perl-team/modules/packages/libipc-shareable-perl/-/commit/2bb8b7686bbed7057b466085b70e8bfa3b3347ff


Add patch to mark tests as TODO which fail on 32bit architectures.

Thanks: Niko Tyni for the analysis.
Closes: #997829


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997829

Processed: Bug#997829 marked as pending in libipc-shareable-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest 
regression on armhf and i386
Added tag(s) pending.

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

Bug#1000896: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386

[gregor herrmann]

On Sat, 22 Jan 2022 18:57:30 +0200, Niko Tyni wrote:

> Given  % 2^32 == 3567587327 it's pretty clear that the
> requested size does not fit into 32 bits (shmget(2) takes a size_t)
> so just its lower bits get passed in. Not sure if perl should protest
> somehow there.

Thanks for the analysis!
 
> Anyway, seems like the test could just be skipped on 32-bit or something.

As I'm not sure there's a reliable way detect the bitness from the
test, I've marked it as TODO for the time being (and added your
findings to the upstream issue).


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bob Dylan: Mr Tambourine Man


signature.asc
Description: Digital Signature

Bug#997829: Bug#1000896: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386

[Niko Tyni]

On Sat, Jan 15, 2022 at 11:20:51PM +0100, gregor herrmann wrote:
> On Mon, 25 Oct 2021 19:59:39 +0200, gregor herrmann wrote:
 
> No reaction so far at https://github.com/stevieb9/ipc-shareable/issues/14
> 
> Failures are visible at
> https://qa.debian.org/excuses.php?package=libipc-shareable-perl
> 
> And can easily be reproduced by building in an i386 chroot.
> 
> After some looking at the the code I have no idea what's broken
> there.
> Anyone else?

It boils down to

  perl -e 'shmget(0, , 0666) or die'

which dies on amd64 but not in i386.

Looking further:

  # strace -e shmget perl -we 'shmget(0, , 0666) or die'
  shmget(IPC_PRIVATE, 3567587327, 0666)   = 5177377
  +++ exited with 0 +++

Given  % 2^32 == 3567587327 it's pretty clear that the
requested size does not fit into 32 bits (shmget(2) takes a size_t)
so just its lower bits get passed in. Not sure if perl should protest
somehow there.

Anyway, seems like the test could just be skipped on 32-bit or something.
-- 
Niko Tyni   nt...@debian.org

Bug#1002390: marked as done (python3-babeltrace does not work with Python 3.10)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 16:33:42 +
with message-id 
and subject line Bug#1002390: fixed in babeltrace 1.5.8-2
has caused the Debian Bug report #1002390,
regarding python3-babeltrace does not work with Python 3.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.)


-- 
1002390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lttnganalyses
Version: 0.6.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> copying lttnganalyses/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> copying lttnganalyses/_version.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/parse_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/format_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/trace_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/version_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> copying lttnganalyses/common/time_utils.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/common
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/period.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/cputop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/memtop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/irq.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/sched.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/periods.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/io.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/event.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/stats.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/syscalls.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> copying lttnganalyses/core/analysis.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/core
> creating 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/cputop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/syscallstats.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/memtop.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/progressbar.py -> 
> /<>/.pybuild/cpython3_3.10_lttnganalyses/build/lttnganalyses/cli
> copying lttnganalyses/cli/irq.py -> 
> /<>/.pybuild/cpyt

Bug#1004156: src:adapt: fails to migrate to testing for too long: FTBFS

[Wouter Verhelst]

Hi Paul,

On Fri, Jan 21, 2022 at 10:22:43PM +0100, Paul Gevers wrote:
> If you believe your package is unable to migrate to testing due to issues
> beyond your control, don't hesitate to contact the Release Team.

No, that's not it; I've just not been able to look at the problem, due
to being too busy with other things[1].

I'll get around that early next month, hopefully.

Thanks for caring,

[1] e.g., https://fosdem.org/2022/, which I help organizing.

-- 
 w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}

Bug#1004194: loguru: CVE-2022-0329

[Salvatore Bonaccorso]

Source: loguru
Version: 0.5.3-4
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Delgan/loguru/issues/563
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for loguru.

CVE-2022-0329[0]:
| Code Injection in PyPi loguru prior to and including 0.5.3.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-0329
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0329
[1] https://github.com/Delgan/loguru/issues/563
[2] 
https://github.com/delgan/loguru/commit/4b0070a4f30cbf6d5e12e6274b242b62ea11c81b

Regards,
Salvatore

Bug#998937: marked as done (aspell-cs: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 15:18:39 +
with message-id 
and subject line Bug#998937: fixed in aspell-cs 0.51.0-1.3
has caused the Debian Bug report #998937,
regarding aspell-cs: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
998937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspell-cs
Version: 0.51.0-1.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: aspell-cs
Source-Version: 0.51.0-1.3
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
aspell-cs, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated aspell-cs 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: Wed, 12 Jan 2022 15:25:42 +0100
Source: aspell-cs
Architecture: source
Version: 0.51.0-1.3
Distribution: unstable
Urgency: medium
Maintainer: Miroslav Kure 
Changed-By: Andreas Beckmann 
Closes: 998937
Changes:
 aspell-cs (0.51.0-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: Add build-arch and build-indep targets.  (Closes: #998937)
Checksums-Sha1:
 4790f9e813c1a15c2033a7c2fc84eeff68bccfa4 1793 aspell-cs_0.51.0-1.3.dsc
 9ebe42ce85344cd4b944716853a1e81dc5b52d99 2928 
aspell-cs_0.51.0-1.3.debian.tar.xz
 20cf7699e0e5400ff6b954196f4e24a507ee2d10 5595 
aspell-cs_0.51.0-1.3_source.buildinfo
Checksums-Sha256:
 db28b8bd4c871c8eb972730fedcd7b0a465bf556c04f45df3c9d423b21a91744 1793 
aspell-cs_0.51.0-1.3.dsc
 a58d95aceec779960dfc8cf033a23c908ffe3057b8f9b1b8124fffa26b8f917b 2928 
aspell-cs_0.51.0-1.3.debian.tar.xz
 881338a17ad054e58e63d7f0fc15c49970b1d7dc6090cece13a6289d76fc1384 5595 
aspell-cs_0.51.0-1.3_source.buildinfo
Files:
 6586c382046add26ca54938fe4fe7134 1793 text optional aspell-cs_0.51.0-1.3.dsc
 3d4e924da9ca83c37364381da6025a72 2928 text optional 
aspell-cs_0.51.0-1.3.debian.tar.xz
 6262aa58a2011ab34f3b293f62366c1f 5595 text optional 
aspell-cs_0.51.0-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmHe5fkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKrtD/4w2lUPzED43v/wIaHB249uoDqBgEczQM5J
Lo2xWHRguxpbZLGdL1g2dlrCgITEtw19kCa0HxXZMm1/dl7MQU1qxtcdeu4rbIz9
4TzQgZohjSFVuT0w46NQq5wixMzBZYBPfjJxF8+u9bW/EYdWeQnNwwKmrNy4x5Xo
WdyRVi5AKYmJvzlbSM3iJnTdQgRBKlaQXbfl6Bztk0CyqBzUjw5HLdBLutlr23ND
WXzgjay7mlniO/4rStobkHiL0nQgMXE3Ds4xCOiyp2cYv+rsl2kQm3t2k+PGJdZD
7qREX2V3V6BT20MxHKrgjMomUkFYIQWLoY0FydFmlhDTo5Q7s5PLHJOk1zdvhioZ
gzL+caE9wIq7GCLwENVJWYuiUajIhY7pwSjQLS/o8Lg3GHunaR0gUaZrbjaHQ5Fs
XCmA6hYaKmENwW3QvqNR8tBQ65BRFnBBapGBthSz2E5i7q6ldwCvNhdlozsxAyr7
2lxbvfDYxd0WC6PAJXOeNY2b9zQrQaI+IE6eFb8r3Jlbar6OCd4h2DifO0NMPOsw
LCf6V3y/LLgdHQzNEbVDhU4QS2Orr0+pa/rfetC1tPYOlWlfnpDaTYL9U9U1jOlo
tQmlRH1K5NOTlnJQEUDt19hHRpOmIOgVpAQ6wmGQU9tpsnFYKH0X+A4VuZDFIep1
8QhzEBs+bQ==
=j+vN
-END PGP SIGNATURE End Message ---

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[Paul Gevers]

Source: scikit-learn
Followup-For: Bug #1003165

Hi,

I have uploaded the attached debdiff as NMU to DELAYED/2. Please let
me know if I should cancel the upload.

Paul
diff --git a/debian/changelog b/debian/changelog
index 7816bd5..2cf4db0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+scikit-learn (1.0.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * To advance the python3.10 transition, disable the tests during build
+for now (see: #1003165)
+
+ -- Paul Gevers   Fri, 21 Jan 2022 22:38:09 +0100
+
 scikit-learn (1.0.1-1) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/rules b/debian/rules
index 3359be5..80fc485 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,6 +3,8 @@
 
 # See also: skimage
 
+export DEB_BUILD_OPTIONS += nocheck
+
 include /usr/share/dpkg/architecture.mk
 
 PY3VER  ?= $(shell py3versions -vd)

Processed: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

[Debian Bug Tracking System]

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

> notfound 1004167 5.5-1
Bug #1004167 [debianutils] debianutils: tries to overwrite 
/usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr
No longer marked as found in versions debianutils/5.5-1.
> found 1004167 5.6-0.1
Bug #1004167 [debianutils] debianutils: tries to overwrite 
/usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr
Marked as found in versions debianutils/5.6-0.1.
> thanks
Stopping processing here.

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

Bug#1003964: marked as done (cmark-gfm: shlibs too relaxed for unstable ABI)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jan 2022 13:00:10 +
with message-id 
and subject line Bug#1003964: fixed in cmark-gfm 0.29.0.gfm.2-2
has caused the Debian Bug report #1003964,
regarding cmark-gfm: shlibs too relaxed for unstable ABI
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.)


-- 
1003964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pandoc
Version: 2.9.2.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While looking at some test issues in libpod-pandoc-perl, I noticed
that pandoc looks quite broken in current amd64/sid:

% pandoc --version
pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0: 
cannot open shared object file: No such file or directory
% echo $?
127
% apt-file search libcmark-gfm.so.0.29.0.gfm.0
libcmark-gfm0: /usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0
% dpkg -l libcmark-gfm0
…
ii  libcmark-gfm0:amd64 0.29.0.gfm.2-1 amd64CommonMark GitHub flavor 
gfm library
% dpkg -L libcmark-gfm0 
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2
/usr/share
/usr/share/doc
/usr/share/doc/libcmark-gfm0
/usr/share/doc/libcmark-gfm0/changelog.Debian.gz
/usr/share/doc/libcmark-gfm0/changelog.gz
/usr/share/doc/libcmark-gfm0/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libcmark-gfm0
% ls -la /usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2 
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0
ls: cannot access '/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0': No 
such file or directory
- -rw-r--r-- 1 root root 317688 Jan 18 01:43 
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2

So it looks like pandoc wants libcmark-gfm.so.0.29.0.gfm.0 but libcmark-gfm0
ships libcmark-gfm.so.0.29.0.gfm.2. Maybe this is an issue in libcmark-gfm0
… Not sure where to fix this.

cmark-gfm (0.29.0.gfm.2-1) unstable; urgency=medium

  * New upstream version.
  * Fix for CVE-2020-5238. (Closes: #965984)
  * Switch man page --safe to --unsafe. (Closes: #1003745)

 -- Keith Packard   Mon, 17 Jan 2022 16:43:27 -0800

cmark-gfm (0.29.0.gfm.0-6) unstable; urgency=medium

  * Use  directly instead of "config.h". (Closes: #969212)

 -- Keith Packard   Wed, 02 Sep 2020 10:25:33 -0700




Cheers,
gregor


- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages pandoc depends on:
ii  libc6 2.33-2
ii  libcmark-gfm-extensions0  0.29.0.gfm.2-1
ii  libcmark-gfm0 0.29.0.gfm.2-1
ii  libffi8   3.4.2-4
ii  libgmp10  2:6.2.1+dfsg-3
ii  libpcre3  2:8.39-13
ii  pandoc-data   2.9.2.1-2
ii  zlib1g1:1.2.11.dfsg-2

pandoc recommends no packages.

Versions of packages pandoc suggests:
pn  citation-style-language-styles  
ii  context 2020.03.10.20200331-1
pn  ghc 
ii  groff   1.22.4-8
pn  libjs-katex 
ii  libjs-mathjax   2.7.9+dfsg-1
ii  librsvg2-bin2.50.7+dfsg-2
pn  nodejs  
pn  pandoc-citeproc 
ii  perl5.32.1-6
pn  php 
pn  python  
pn  r-base-core 
ii  ruby1:2.7.6
ii  texlive-latex-extra 2021.20211217-1
ii  texlive-latex-recommended   2021.20211217-1
ii  texlive-luatex  2021.20211217-1
ii  texlive-xetex   2021.20211217-1
pn  wkhtmltopdf 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmHm8/JfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaeqg//SynSrZ9ifms45FsFTw/25leWnr1rbeGLz

Processed: clone 1001168

[Debian Bug Tracking System]

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

> clone 1001168 -1
Bug #1001168 [src:hkl] hkl: FTBFS on mipsel: FAIL: trajectory.py
Bug 1001168 cloned as bug 1004184
1004184 was blocked by: 1000774 1000435
1004184 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1004184 to the same blocks 
previously set
1004184 was blocked by: 1000774 1000435
1004184 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1004184 to the same blocks 
previously set
> reassign -1 src:gcc-11
Bug #1004184 [src:hkl] hkl: FTBFS on mipsel: FAIL: trajectory.py
Bug reassigned from package 'src:hkl' to 'src:gcc-11'.
No longer marked as found in versions hkl/5.0.0.2816-2.
Ignoring request to alter fixed versions of bug #1004184 to the same values 
previously set
> retitle -1 gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el
Bug #1004184 [src:gcc-11] hkl: FTBFS on mipsel: FAIL: trajectory.py
Changed Bug title to 'gcc-11: generate bad code for matplotlib with -O1/-O2 on 
mips64el' from 'hkl: FTBFS on mipsel: FAIL: trajectory.py'.
> thanks
Stopping processing here.

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

Bug#1000435: Matplotlib crashes on mips64el in lines.py

[YunQiang Su]

On Sat, 22 Jan 2022 17:06:00 +0800 YunQiang Su  wrote:> On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher  wrote:> > Source: matplotlib> > Severity: serious> > Version: 3.5.0-1> > Control: affects -1 yt> > Control: affects -1 astropy> >> > With the new matplotlib version, I now have crashes with a segmentation fault> > in at least two of my packages on mips64el, which cause a FTBFS: yt and> > astropy. On both packages, the crash happens here:> >> > --8<> >    File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in draw> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in draw> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in draw> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositing_images> >    File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 in draw> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositing_images> >    File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in draw> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in draw_wrapper> >    File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 436 in draw> > --8<> >> > Build log on Astropy: https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=mips64el&ver=5.0-1&stamp=1637626067&raw=0> >> > Build log on yt: https://buildd.debian.org/status/fetch.php?pkg=yt&arch=mips64el&ver=4.0.1-3&stamp=1637588650&raw=0> >> > This happens on both Python 3.9 and 3.10. The I will try to create a stacktrace for it.> >> > It is due to gcc-11 of mips64el.> > -O1, -O2 may generate bad code, while -O0 and -O3 works well.> As a workaround: we can:> > The attachment is a workaround patch.> 

matplotlib-mips64el-o3.diff
Description: Binary data
A better formatted patch with DEB__MAINT_APPEND> >

Bug#1004181: wolfssl: CVE-2022-23408

[Salvatore Bonaccorso]

Source: wolfssl
Version: 5.0.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/wolfSSL/wolfssl/pull/4710
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for wolfssl.

CVE-2022-23408[0]:
| wolfSSL 5.x before 5.1.1 uses non-random IV values in certain
| situations. This affects connections (without AEAD) using AES-CBC or
| DES3 with TLS 1.1 or 1.2 or DTLS 1.1 or 1.2. This occurs because of
| misplaced memory initialization in BuildMessage in internal.c.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-23408
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23408
[1] https://github.com/wolfSSL/wolfssl/pull/4710
[2] 
https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-511-jan-3rd-2022

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: Re: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1004167 [debianutils] debianutils: tries to overwrite 
/usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr
Added tag(s) patch.

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

Bug#1004167: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

[Johannes Schauer Marin Rodrigues]

Control: tag -1 + patch

On Sat, 22 Jan 2022 04:08:18 +0100 Vincent Lefevre  wrote:
> I get the following error when I want to upgrade:
> 
> Unpacking debianutils (5.6-0.1) over (5.5-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb (--unpack):
>  trying to overwrite '/usr/share/man/fr/man1/readlink.1.gz', which is also in 
> package manpages-fr 4.12.1-3
> Errors were encountered while processing:
>  /var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

this is due to the following change in the last NMU:

https://salsa.debian.org/debian/debianutils/-/commit/af07f29d318781033e560030fdd3ebc0458abdcf#7197be9dcd1c350e8cd40ad50073d78624da6f10_12_11

The following MR reverts this change:

https://salsa.debian.org/debian/debianutils/-/merge_requests/19

Thanks!

cheers, josch

signature.asc
Description: signature

Processed: nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824

[Debian Bug Tracking System]

Processing control commands:

> found -1 12.22.5~dfsg-2~11u1
Bug #1004177 [src:nodejs] nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 
CVE-2022-21824
Marked as found in versions nodejs/12.22.5~dfsg-2~11u1.

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

Bug#1004177: nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824

[Salvatore Bonaccorso]

Source: nodejs
Version: 12.22.7~dfsg-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 12.22.5~dfsg-2~11u1

Hi,

The following vulnerabilities were published for nodejs.

CVE-2021-44531[0]:
| Improper handling of URI Subject Alternative Names

CVE-2021-44532[1]:
| Certificate Verification Bypass via String Injection

CVE-2021-44533[2]:
| Incorrect handling of certificate subject and issuer fields

CVE-2022-21824[3]:
| Prototype pollution via console.table properties

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-44531
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44531
[1] https://security-tracker.debian.org/tracker/CVE-2021-44532
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44532
[2] https://security-tracker.debian.org/tracker/CVE-2021-44533
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44533
[3] https://security-tracker.debian.org/tracker/CVE-2022-21824
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21824

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1001168: [Debian-pan-maintainers] Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[YunQiang Su]

PICCA Frederic-Emmanuel
 于2022年1月22日周六 17:28写道：
>
> Is it not better to use the
>
> DEB__MAINT_APPEND
>
> variable in order to deal with this issue ?

Thanks, you are right. the patch looks better now.


-- 
YunQiang Su


matplotlib-mips64el-o3.diff
Description: Binary data

Bug#1001168: [Debian-pan-maintainers] Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[PICCA Frederic-Emmanuel]

Is it not better to use the

DEB__MAINT_APPEND

variable in order to deal with this issue ?

Bug#1004103: calcurse FTBFS on big endian

[Dipak Zope1]

Hi Adrian,
Thanks for reporting this. I will check this and revert back. 



From:   "Adrian Bunk" 
To: "Debian Bug Tracking System" 
Date:   21/01/2022 03:00 AM
Subject:[EXTERNAL] Bug#1004103: calcurse FTBFS on big endian



Source: calcurse
Version: 4.7.1-1
Severity: serious
Tags: ftbfs
Control: block 1002519 by -1

https://buildd.debian.org/status/logs.php?pkg=calcurse&ver=4.7.1-1 


...
FAIL: ical-003.sh
=

Running ./ical-003.sh... FAIL
FAIL ical-003.sh (exit status: 1)


Testsuite summary for calcurse 4.7.1

# TOTAL: 77
# PASS:  76
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to b...@calcurse.org

make[6]: *** [Makefile:761: test-suite.log] Error 1



s390x porters Cc'ed to debug this issue.

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[YunQiang Su]

Graham Inggs  于2022年1月22日周六 16:48写道：
>
> On Sat, 22 Jan 2022 at 10:45, YunQiang Su  wrote:
> > Sure. I will.
>
> Thank you!

Patch sent: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435

-- 
YunQiang Su

Bug#1000435: Matplotlib crashes on mips64el in lines.py

[YunQiang Su]

On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher  wrote:
> Source: matplotlib
> Severity: serious
> Version: 3.5.0-1
> Control: affects -1 yt
> Control: affects -1 astropy
>
> With the new matplotlib version, I now have crashes with a segmentation fault
> in at least two of my packages on mips64el, which cause a FTBFS: yt and
> astropy. On both packages, the crash happens here:
>
> --8<
>File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in draw
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in draw
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in draw
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in 
> _draw_list_compositing_images
>File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 
> in draw
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in 
> _draw_list_compositing_images
>File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in 
> draw
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in 
> draw_wrapper
>File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", 
> line 436 in draw
> --8<
>
> Build log on Astropy: 
> https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=mips64el&ver=5.0-1&stamp=1637626067&raw=0
>
> Build log on yt: 
> https://buildd.debian.org/status/fetch.php?pkg=yt&arch=mips64el&ver=4.0.1-3&stamp=1637588650&raw=0
>
> This happens on both Python 3.9 and 3.10. The I will try to create a 
> stacktrace for it.
>

It is due to gcc-11 of mips64el.

-O1, -O2 may generate bad code, while -O0 and -O3 works well.
As a workaround: we can:

The attachment is a workaround patch.

>


matplotlib-mips64el-o3.diff
Description: Binary data

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[Graham Inggs]

On Sat, 22 Jan 2022 at 10:45, YunQiang Su  wrote:
> Sure. I will.

Thank you!

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[YunQiang Su]

Graham Inggs  于2022年1月22日周六 16:42写道：
>
> On Sat, 22 Jan 2022 at 10:12, YunQiang Su  wrote:
> > Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> > If it works, we can workaround it for now.
> > I will continue to dig the real problem of gcc (maybe).
>
> To be clear, will you try building matplotlib with -O3 and if it
> works, send a patch to matplotlib?

Sure. I will.

-- 
YunQiang Su

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[Graham Inggs]

On Sat, 22 Jan 2022 at 10:12, YunQiang Su  wrote:
> Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> If it works, we can workaround it for now.
> I will continue to dig the real problem of gcc (maybe).

To be clear, will you try building matplotlib with -O3 and if it
works, send a patch to matplotlib?

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

[YunQiang Su]

Graham Inggs  于2022年1月22日周六 15:42写道：
>
> Hi YunQiang Su
>
> Have you been able to make any progress with this issue?
>
> If not, then we should consider asking ftp-master for temporary
> removal of the affected mips64el packages from testing.  We'd like to
> move the python3-defaults transition along.
>

Let's have a try to build matplotlib with -O3, and try to build hkl with it.
If it works, we can workaround it for now.
I will continue to dig the real problem of gcc (maybe).

> Regards
> Graham



-- 
YunQiang Su