Bug#1007992: libigdgmm12: new version causes segfaults

[Christoph Anton Mitterer]

Package: libigdgmm12
Version: 22.1.1+ds1-1
Severity: critical
Justification: breaks unrelated software


Hey.


This version breaks e.g. video playback with mpv (also vlc):
$ mpv test.mp4
 (+) Video --vid=1 (h264 720x300 23.976fps)
 (+) Audio --aid=1 (aac 2ch 44100Hz)
Segmentation fault


With:
Mar 20 04:30:17 heisenberg kernel: mpv/vo[292810]: segfault at 30200 ip 
7f93a01e49ae sp 7f93ab2514b0 error 4 in 
libigdgmm.so.12.1.0[7f93a017b000+78000]
Mar 20 04:30:17 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:22 heisenberg kernel: mpv/vo[292830]: segfault at 30200 ip 
7fb5381d49ae sp 7fb53b4564b0 error 4 in 
libigdgmm.so.12.1.0[7fb53816b000+78000]
Mar 20 04:30:22 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:23 heisenberg kernel: mpv/vo[292850]: segfault at 30200 ip 
7f57901de9ae sp 7f579ea9f4b0 error 4 in 
libigdgmm.so.12.1.0[7f5790175000+78000]
Mar 20 04:30:23 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:30 heisenberg kernel: vlc[292895]: segfault at 30200 ip 
7f94f12fb9ae sp 7f94f105bb00 error 4 in 
libigdgmm.so.12.1.0[7f94f1292000+78000]
Mar 20 04:30:30 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:31:20 heisenberg kernel: mpv/vo[293088]: segfault at 30200 ip 
7f923547a9ae sp 7f925251a4b0 error 4 in 
libigdgmm.so.12.1.0[7f9235411000+78000]
Mar 20 04:31:20 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f


Downgrading to 22.0.2+ds1-1 fixes the issue.


Cheers,
Chris.


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

Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libigdgmm12 depends on:
ii  libc6   2.33-7
ii  libgcc-s1   12-20220319-1
ii  libstdc++6  12-20220319-1

libigdgmm12 recommends no packages.

libigdgmm12 suggests no packages.

-- no debconf information

Bug#996098: marked as done (libxsmm: CVE-2021-39535 CVE-2021-39536)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2022 00:34:01 +
with message-id 
and subject line Bug#996098: fixed in libxsmm 1.17-1
has caused the Debian Bug report #996098,
regarding libxsmm: CVE-2021-39535 CVE-2021-39536
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.)


-- 
996098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxsmm
Version: 1.9-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for libxsmm.

CVE-2021-39535[0]:
| An issue was discovered in libxsmm through v1.16.1-93. A NULL pointer
| dereference exists in JIT code. It allows an attacker to cause Denial
| of Service.


CVE-2021-39536[1]:
| An issue was discovered in libxsmm through v1.16.1-93. The JIT code
| has a heap-based buffer overflow.

Severity is slight overrated here, but making it RC to make sure fixed
version can land in bookworm.


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-39535
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39535
[1] https://security-tracker.debian.org/tracker/CVE-2021-39536
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39536

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxsmm
Source-Version: 1.17-1
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
libxsmm, 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.
Boyuan Yang  (supplier of updated libxsmm 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, 19 Mar 2022 20:01:55 -0400
Source: libxsmm
Architecture: source
Version: 1.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Boyuan Yang 
Closes: 917526 962949 996098
Changes:
 libxsmm (1.17-1) unstable; urgency=medium
 .
   * New upstream version 1.17.
 + Fix old CVEs:
   - CVE-2018-20541
   - CVE-2018-20542 (Closes: #917526)
   - CVE-2021-39535
   - CVE-2021-39536 (Closes: #996098)
   * Add myself as package uploader. (Closes: #962949)
   * debian/control: Use up-to-date homepage information.
   * Bump Standards-Version to 4.6.0.
   * debian/rules: Use vanilla build for now.
   * debian/docs: Also install upstream documentation.
   * debian/patches: Refresh patches:
 + Makefile_rebuild_fix.patch: Refreshed.
 - 0004-Force-python3.patch: Dropped, useless.
 - destdir.patch: Dropped for now.
 - remove_stdc++_link.patch: Dropped for now.
   * debian/patches: Add new patches:
 + 0002-Makefile-fix-pkgconfigdir.patch: Fix pkgconfigdir.
Checksums-Sha1:
 219ad1d609fff1a754154721f8a04f86e9c77d00 2016 libxsmm_1.17-1.dsc
 aa92d10675cbff54aacd72a369e540ce85b1badd 2528419 libxsmm_1.17.orig.tar.gz
 9bc4c5b9a2da59e9252a67c64a5d816a3617ad1a 3348 libxsmm_1.17-1.debian.tar.xz
 b2fbd44e71ad227fa2c213d0a4a5588d3f96483e 6854 libxsmm_1.17-1_amd64.buildinfo
Checksums-Sha256:
 bc5fa24e832d8bd7aa8eb984d1b34c684c4f2ef9ed03a62f05659f8842cde706 2016 
libxsmm_1.17-1.dsc
 8b642127880e92e8a75400125307724635ecdf4020ca4481e5efe7640451bb92 2528419 
libxsmm_1.17.orig.tar.gz
 861fb6abf84907f11450065f532d46a11d799cdacda4b50dc58ac7f5226f8c1b 3348 
libxsmm_1.17-1.debian.tar.xz
 6c5230aa252c840a40cbd447bd8706ea2ead6da150e41c6bd78822e5712300b6 6854 
libxsmm_1.17-1_amd64.buildinfo
Files:
 57e2a7db824f3616487364f9a2e96cc4 2016 libs optional libxsmm_1.17-1.dsc
 bef3b02f8837b0eed1ea334045da0524 2528419 libs optional libxsmm_1.17.orig.tar.gz
 e92fd20f407ea5ef0e22fbbba057acb2 3348 libs optional 
libxsmm_1.17-1.debian.tar.xz
 030ad87fb7407d6b48ba5f4aab25abb4 6854 libs optional 
libxsmm_1.17-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmI2b8wACgkQwpPntGGC
Ws6gFw//fqkr5+4moaRPa0l4/ZVHgM5WuIihaPTwrrqLuvNTeWN1kzcWe2b+1gtW

Bug#917526: marked as done (libxsmm: CVE-2018-20541 CVE-2018-20542)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2022 00:34:01 +
with message-id 
and subject line Bug#917526: fixed in libxsmm 1.17-1
has caused the Debian Bug report #917526,
regarding libxsmm: CVE-2018-20541 CVE-2018-20542
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.)


-- 
917526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxsmm
Version: 1.9-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/hfp/libxsmm/issues/287

Hi,

The following vulnerabilities were published for libxsmm.

CVE-2018-20541[0]:
| There is a heap-based buffer overflow in libxsmm_sparse_csc_reader at
| generator_spgemm_csc_reader.c in LIBXSMM 1.10, a different
| vulnerability than CVE-2018-20542 (which is in a different part of the
| source code and is seen at different addresses).

CVE-2018-20542[1]:
| There is a heap-based buffer-overflow at generator_spgemm_csc_reader.c
| (function libxsmm_sparse_csc_reader) in LIBXSMM 1.10, a different
| vulnerability than CVE-2018-20541 (which is in a different part of the
| source code and is seen at a different address).

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-2018-20541
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20541
[1] https://security-tracker.debian.org/tracker/CVE-2018-20542
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20542
[2] https://github.com/hfp/libxsmm/issues/287

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxsmm
Source-Version: 1.17-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated libxsmm 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, 19 Mar 2022 20:01:55 -0400
Source: libxsmm
Architecture: source
Version: 1.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Boyuan Yang 
Closes: 917526 962949 996098
Changes:
 libxsmm (1.17-1) unstable; urgency=medium
 .
   * New upstream version 1.17.
 + Fix old CVEs:
   - CVE-2018-20541
   - CVE-2018-20542 (Closes: #917526)
   - CVE-2021-39535
   - CVE-2021-39536 (Closes: #996098)
   * Add myself as package uploader. (Closes: #962949)
   * debian/control: Use up-to-date homepage information.
   * Bump Standards-Version to 4.6.0.
   * debian/rules: Use vanilla build for now.
   * debian/docs: Also install upstream documentation.
   * debian/patches: Refresh patches:
 + Makefile_rebuild_fix.patch: Refreshed.
 - 0004-Force-python3.patch: Dropped, useless.
 - destdir.patch: Dropped for now.
 - remove_stdc++_link.patch: Dropped for now.
   * debian/patches: Add new patches:
 + 0002-Makefile-fix-pkgconfigdir.patch: Fix pkgconfigdir.
Checksums-Sha1:
 219ad1d609fff1a754154721f8a04f86e9c77d00 2016 libxsmm_1.17-1.dsc
 aa92d10675cbff54aacd72a369e540ce85b1badd 2528419 libxsmm_1.17.orig.tar.gz
 9bc4c5b9a2da59e9252a67c64a5d816a3617ad1a 3348 libxsmm_1.17-1.debian.tar.xz
 b2fbd44e71ad227fa2c213d0a4a5588d3f96483e 6854 libxsmm_1.17-1_amd64.buildinfo
Checksums-Sha256:
 bc5fa24e832d8bd7aa8eb984d1b34c684c4f2ef9ed03a62f05659f8842cde706 2016 
libxsmm_1.17-1.dsc
 8b642127880e92e8a75400125307724635ecdf4020ca4481e5efe7640451bb92 2528419 
libxsmm_1.17.orig.tar.gz
 861fb6abf84907f11450065f532d46a11d799cdacda4b50dc58ac7f5226f8c1b 3348 
libxsmm_1.17-1.debian.tar.xz
 6c5230aa252c840a40cbd447bd8706ea2ead6da150e41c6bd78822e5712300b6 6854 
libxsmm_1.17-1_amd64.buildinfo
Files:
 57e2a7db824f3616487364f9a2e96cc4 2016 libs optional libxsmm_1.17-1.dsc
 bef3b02f8837b0eed1ea334045da0524 2528419 libs optional libxsmm_1.17.orig.tar.gz
 e92fd20f407ea5ef0e22fbbba057acb2 3348 libs optional 
libxsmm_1.17-1.debian.tar.xz
 030ad87fb7407d6b48ba5f4aab25abb4 6854 libs optional 

Bug#953530: samba-common-bin: post-install fails with "lock directory /run/samba does not exist"

[Diederik de Haas]

On vrijdag 18 maart 2022 23:28:33 CET Diederik de Haas wrote:
> And indeed I do not have a /run/samba/ directory on my Bookworm
> system/server.

After I manually created /run/samba/, the installation succeeded.

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

Bug#1007929: marked as pending in netcfg

[Samuel Thibault]

Control: tag -1 pending

Hello,

Bug #1007929 in netcfg 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/installer-team/netcfg/-/commit/6444d2aaa53ef49744dd3915d51fe0c69ea57d33


netcfg-common.c: Fix endianness support in netcfg_gateway_reachable

(Closes: #1007929)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007929

Processed: Bug#1007929 marked as pending in netcfg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007929 [src:netcfg] netcfg: FTBFS on s390x
Ignoring request to alter tags of bug #1007929 to the same tags previously set

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

Bug#1007929: netcfg: FTBFS on s390x

[Samuel Thibault]

Control: tags -1 + pending

Hello,

Cyril Brulebois, le sam. 19 mars 2022 16:32:06 +0100, a ecrit:
> > Running suite(s): inet_mton
> > 95%: Checks: 24, Failures: 1, Errors: 0
> > test/test_netcfg_gateway_reachable.c:94:F:netcfg_gateway_reachable:test_netcfg_gateway_reachable_v6_fe80:0:
> >  Gateway erroneously unreachable
> > make[1]: *** [test/tests.mk:19: test] Error 1
> > make[1]: Leaving directory '/<>'
> > dh_auto_test: error: make -j1 test returned exit code 2
> > make: *** [debian/rules:6: build-arch] Error 25
> 
> Paging Samuel & Igor, hunch says this might be related:
> 
> commit 3549f77c39c06e7dfcfd59fce01ff2d4a0622058
> Merge: 90e52aed 6bff2dee
> Author: Samuel Thibault 
> Date:   Sun Sep 5 14:59:46 2021 +
> 
> Merge branch 'ipv6-link-local-gateway' into 'master'
> 
> Add support for fe80::/10 addresses as IPv6 gateway, closes #901255
> 
> See merge request installer-team/netcfg!3

I committed

-if ((ntohs(gw_addr.in6.s6_addr32[0]) & 0xffc0) == (0xfe80 & 0xffc0)) {
+if ((ntohl(gw_addr.in6.s6_addr32[0]) & 0xffc0) == (0xfe80 & 0xffc0)) {

which is required for the test to work at all indeed.  I guess that'll
just fix the issue.

Samuel

Processed: Re: Bug#1007929: netcfg: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1007929 [src:netcfg] netcfg: FTBFS on s390x
Added tag(s) pending.

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

Bug#1007985: apertium-lex-tools: fatal error: lttoolbox/ltstr.h: No such file or directory

[Tino Didriksen]

We are in the process of updating all the packages that use lttoolbox, so
this is fully expected.

-- Tino Didriksen


On Sat, 19 Mar 2022 at 23:03, Sebastian Ramacher 
wrote:

> Source: apertium-lex-tools
> Version: 0.2.7-1
> Severity: serious
> Tags: ftbfs sid bookworm
> X-Debbugs-Cc: sramac...@debian.org
>
> g++ -DPACKAGE_NAME=\"apertium-lex-tools\"
> -DPACKAGE_TARNAME=\"apertium-lex-tools\" -DPACKAGE_VERSION=\"0.2.7\"
> -DPACKAGE_STRING=\"apertium-lex-tools\ 0.2.7\" -DPACKAGE_BUGREPORT=\"
> apertium-st...@lists.sourceforge.net\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"apertium-lex-tools\" -DVERSION=\"0.2.7\" -DHAVE_IRSTLM=0
> -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1
> -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_YASMET=0
> -DHAVE_LIBXML2=1 -DHAVE_SETLOCALE=1 -DHAVE_STRDUP=1
> -DHAVE_DECL_FREAD_UNLOCKED=1 -DHAVE_DECL_FWRITE_UNLOCKED=1
> -DHAVE_DECL_FGETC_UNLOCKED=1 -DHAVE_DECL_FPUTC_UNLOCKED=1
> -DHAVE_DECL_FPUTS_UNLOCKED=1 -DHAVE_DECL_FGETWC_UNLOCKED=0
> -DHAVE_DECL_FPUTWC_UNLOCKED=0 -DHAVE_DECL_FGETWS_UNLOCKED=0
> -DHAVE_DECL_FPUTWS_UNLOCKED=0 -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Wextra -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -I/usr/include/lttoolbox-3.6 -I/usr/include/apertium-3.8
> -I/usr/lib/x86_64-linux-gnu/apertium-3.8/include -I/usr/include/libxml2
> -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++20 -c -o
> lrx_proc.o lrx_proc.cc
> In file included from lrx_proc.cc:17:
> ./lrx_processor.h:37:10: fatal error: lttoolbox/ltstr.h: No such file or
> directory
>37 | #include 
>   |  ^~~
> compilation terminated.
> make[2]: *** [Makefile:426: lrx_proc.o] Error 1
>
>
> See
>
> https://buildd.debian.org/status/fetch.php?pkg=apertium-lex-tools=amd64=0.2.7-1%2Bb1=1647711879=0
>
> Cheers
> --
> Sebastian Ramacher
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
>

Bug#1003907: fails to successfully associate

[Masashi Honma]

In my opinion, this issue could be closed.

These are reasons.
1) It is not wpa_supplicant issue but AP issue.
2) Users affected by this issue have some workarounds.


Details of the 1)
The investigation has revealed that the AP is in violation of "2.3
WPA3-Personal transition mode" of the "WPA3 Specification v3.0", which
is causing the issue. Specifically, the target AP is setting MFPR to 1
even though it implicitly requires IEEE 802.11w. By "implicitly" we
mean that the Assocation Request fails with WLAN_STATUS_INVALID_IE
when using a Wi-Fi NIC with IEEE 802.11w disabled.


Details of the 2)
We know that users who meet the following conditions are affected by this issue.
- Using FRITZ!Box 7580/7590 with WPA2+WPA3 mode
- Using wpa_supplicant with wpa_key_mgmt=SAE WPA-PSK
- Local Wi-Fi NIC does not support IEEE802.11w

Users affected by this issue can work around the issue in one of the
following ways.
- Use wpa_supplicant with WPA2 only mode (specify wpa_key_mgmt=WPA-PSK)
- Use FRITZ!Box 7580/7590 with WPA2 only mode
- Use IEEE 802.11w supporting Wi-Fi NIC

Regards,
Masashi Honma.

2022年3月20日(日) 6:30 Andrej Shadura :
>
> Hi,
>
> Michael, Masashi, what’s your opinion, what should I do as the maintainer of 
> wpa in Debian?
>
> --
> Cheers,
>   Andrej

Bug#1003907: fails to successfully associate

[Michael Biebl]

Am 19.03.22 um 22:30 schrieb Andrej Shadura:

Hi,

Michael, Masashi, what’s your opinion, what should I do as the maintainer of 
wpa in Debian?


I can still reproduce the problem.
If more debugging is needed, please let me know. I'll try to help as 
much as I can.


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007890: FTBFS: No module named 'ipython_genutils'

[Jérémy Lal]

On Sat, Mar 19, 2022 at 10:37 PM Rebecca N. Palmer 
wrote:
>
> Control: reassign -1 python3-nbclient, src:theano
> Control: tags -1 patch
>
> This looks like a missing dependency on python3-ipython-genutils, though
> I haven't actually tested adding that.  (That package was installed when
> current theano was built on the arch:all buildd, suggesting that this
> bug was triggered by something dropping a dependency.)
>
> I'm not sure whether it's src:theano or python3-nbclient that should
> have that dependency.  (python3-nbclient's autopkgtests do pull that
> package in, though I don't know via what chain.)


This is probably #1007883

Bug#1007985: apertium-lex-tools: fatal error: lttoolbox/ltstr.h: No such file or directory

[Sebastian Ramacher]

Source: apertium-lex-tools
Version: 0.2.7-1
Severity: serious
Tags: ftbfs sid bookworm
X-Debbugs-Cc: sramac...@debian.org

g++ -DPACKAGE_NAME=\"apertium-lex-tools\" 
-DPACKAGE_TARNAME=\"apertium-lex-tools\" -DPACKAGE_VERSION=\"0.2.7\" 
-DPACKAGE_STRING=\"apertium-lex-tools\ 0.2.7\" 
-DPACKAGE_BUGREPORT=\"apertium-st...@lists.sourceforge.net\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"apertium-lex-tools\" -DVERSION=\"0.2.7\" -DHAVE_IRSTLM=0 
-DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_YASMET=0 -DHAVE_LIBXML2=1 
-DHAVE_SETLOCALE=1 -DHAVE_STRDUP=1 -DHAVE_DECL_FREAD_UNLOCKED=1 
-DHAVE_DECL_FWRITE_UNLOCKED=1 -DHAVE_DECL_FGETC_UNLOCKED=1 
-DHAVE_DECL_FPUTC_UNLOCKED=1 -DHAVE_DECL_FPUTS_UNLOCKED=1 
-DHAVE_DECL_FGETWC_UNLOCKED=0 -DHAVE_DECL_FPUTWC_UNLOCKED=0 
-DHAVE_DECL_FGETWS_UNLOCKED=0 -DHAVE_DECL_FPUTWS_UNLOCKED=0 -I.   -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/lttoolbox-3.6 -I/usr/include/apertium-3.8 
-I/usr/lib/x86_64-linux-gnu/apertium-3.8/include -I/usr/include/libxml2  -Wall 
-Wextra -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -std=c++20 -c -o lrx_proc.o lrx_proc.cc
In file included from lrx_proc.cc:17:
./lrx_processor.h:37:10: fatal error: lttoolbox/ltstr.h: No such file or 
directory
   37 | #include 
  |  ^~~
compilation terminated.
make[2]: *** [Makefile:426: lrx_proc.o] Error 1


See
https://buildd.debian.org/status/fetch.php?pkg=apertium-lex-tools=amd64=0.2.7-1%2Bb1=1647711879=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#1007890: FTBFS: No module named 'ipython_genutils'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-nbclient, src:theano
Bug #1007890 [src:theano] FTBFS: No module named 'ipython_genutils'
Bug reassigned from package 'src:theano' to 'python3-nbclient,src:theano'.
No longer marked as found in versions theano/1.0.5+dfsg-4.
Ignoring request to alter fixed versions of bug #1007890 to the same values 
previously set
> tags -1 patch
Bug #1007890 [python3-nbclient,src:theano] FTBFS: No module named 
'ipython_genutils'
Added tag(s) patch.

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

Processed: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

[Debian Bug Tracking System]

Processing control commands:

> found -1 node-puppeteer/13.1.0+dfsg-6
Bug #1007983 [src:node-puppeteer] node-puppeteer: broken autopkgtest keeping 
chromium from migrating to testing
Marked as found in versions node-puppeteer/13.1.0+dfsg-6.
> affects -1 chromium
Bug #1007983 [src:node-puppeteer] node-puppeteer: broken autopkgtest keeping 
chromium from migrating to testing
Added indication that 1007983 affects chromium

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

Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

[Andres Salomon]

Source: node-puppeteer
Control: found -1 node-puppeteer/13.1.0+dfsg-6
Control: affects -1 chromium
Severity: serious
Tags: sid bookworm

node-puppeteer is keeping chromium from migrating; as
https://tracker.debian.org/pkg/chromium describes,

"Issues preventing migration:
∙ ∙ autopkgtest for node-puppeteer/13.1.0+dfsg-6: amd64: Regression ♻
  (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻
  (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Not a
  regression"

One of the failure logs is here:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20095690/log.gz

  1 failing

  1) AriaQueryHandler
   queryOne (Chromium web test)
 should find by role "button":
 Error: expect(received).toEqual(expected) // deep equality

- Expected  - 0
+ Received  + 1

  Array [
"node5",
"node6",
+   "node7",
"node8",
"node10",
"node21",
  ]



I'm not entirely sure why it's failing, as the test in
node-puppeteer-13.1.0+dfsg/test/ariaqueryhandler.spec.ts seems to be
searching for button nodes and finds an extra (hidden) button:



it('should find by role "button"', async () => {
  const { page } = getTestState();
  const found = await
page.$$('aria/[role="button"]'); const ids =
await getIds(found); expect(ids).toEqual(['node5', 'node6',
'node8', 'node10', 'node21']); });



Please fix the test; or if this is an actual bug in chromium, please
reassign and let me know.

Thanks,
Andres

Bug#1003907: fails to successfully associate

[Andrej Shadura]

Hi,

Michael, Masashi, what’s your opinion, what should I do as the maintainer of 
wpa in Debian?

-- 
Cheers,
  Andrej

Processed: src:flint-arb: fails to migrate to testing for too long: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:2.22.1-1
Bug #1007980 [src:flint-arb] src:flint-arb: fails to migrate to testing for too 
long: FTBFS on mips64el
Marked as fixed in versions flint-arb/1:2.22.1-1.
Bug #1007980 [src:flint-arb] src:flint-arb: fails to migrate to testing for too 
long: FTBFS on mips64el
Marked Bug as done
> block -1 by 1006779
Bug #1007980 {Done: Paul Gevers } [src:flint-arb] 
src:flint-arb: fails to migrate to testing for too long: FTBFS on mips64el
1007980 was not blocked by any bugs.
1007980 was not blocking any bugs.
Added blocking bug(s) of 1007980: 1006779

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

Bug#1007980: src:flint-arb: fails to migrate to testing for too long: FTBFS on mips64el

[Paul Gevers]

Source: flint-arb
Version: 1:2.21.1-2
Severity: serious
Control: close -1 1:2.22.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1006779

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:flint-arb has been trying to migrate for 
61 days [2]. Hence, I am filing this bug.


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=flint-arb



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:wpa: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 2:2.10-2
Bug #1007979 [src:wpa] src:wpa: fails to migrate to testing for too long: 
unresolved RC bug
Marked as fixed in versions wpa/2:2.10-2.
Bug #1007979 [src:wpa] src:wpa: fails to migrate to testing for too long: 
unresolved RC bug
Marked Bug as done
> block -1 by 1003907
Bug #1007979 {Done: Paul Gevers } [src:wpa] src:wpa: fails 
to migrate to testing for too long: unresolved RC bug
1007979 was not blocked by any bugs.
1007979 was not blocking any bugs.
Added blocking bug(s) of 1007979: 1003907

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

Bug#1007979: src:wpa: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: wpa
Version: 2:2.9.0-23
Severity: serious
Control: close -1 2:2.10-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1003907

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:wpa has been trying to migrate for 61 days 
[2]. Hence, I am filing this bug. Your package is blocked by an 
unresolved bug, but reading the bug report, it looks like faulty 
hardware and the bug should be closed, no?


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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007977: android-platform-system-core: builds adb which is also built (at a higher version) by android-platform-tools

[Peter Michael Green]

Package: android-platform-system-core
Version: 1:10.0.0+r36-9
Severity: serious

The android-platform-system-core source package builds the adb and fastboot
binary packages which are also built (with a higher version number) by
android-platform-tools, I belive this is what lead to the rejection of 
the amd64
build, it would certainly cause rejections if the package was reuploaded 
now.


Please consider dropping the build of the adb binary package so your package
can be accepted on all architectures and the fix for migrate to testing.

Bug#1007974: polyml: autopkgtest regression on amd64: relocation in read-only section `.text'

[Paul Gevers]

Source: polyml
Version: 5.7.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, somewhere between 05 
July 2021 and 12 July 2021 it regressed in testing on amd64 [1]


I copied some of the output of a recent failure at the bottom of this 
report. The test passes, but ld prints a warning to stderr. By default 
output to sdterr is considered a failure by autopkgtest unless the 
allow-stderr restriction is set in d/t/control. Preferably you fix the 
issue, but the allow-stderr is a valid alternative if the warning is 
harmless.


Paul

[1] https://ci.debian.net/packages/p/polyml/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/p/polyml/20060752/log.gz

autopkgtest [06:15:06]: test upstream-polyc: [---
/usr/bin/ld: /tmp/polyobj.1608.o: warning: relocation in read-only 
section `.text'

/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
Test106.ML => Passed


OpenPGP_signature
Description: OpenPGP digital signature

Processed: update bts with new metadata

[Debian Bug Tracking System]

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

> reassign 1007739 src:curl 7.82.0-1
Bug #1007739 {Done: Samuel Henrique } [src:curl, 
src:stenographer] curl breaks stenographer autopkgtest: curl: (27) Out of memory
Bug reassigned from package 'src:curl, src:stenographer' to 'src:curl'.
No longer marked as found in versions curl/7.82.0-1 and stenographer/1.0.1-2.
No longer marked as fixed in versions curl/7.82.0-2.
Bug #1007739 {Done: Samuel Henrique } [src:curl] curl 
breaks stenographer autopkgtest: curl: (27) Out of memory
Marked as found in versions curl/7.82.0-1.
> affects 1007739 src:stenographer
Bug #1007739 {Done: Samuel Henrique } [src:curl] curl 
breaks stenographer autopkgtest: curl: (27) Out of memory
Added indication that 1007739 affects src:stenographer
> fixed 1007739 7.82.0-2
Bug #1007739 {Done: Samuel Henrique } [src:curl] curl 
breaks stenographer autopkgtest: curl: (27) Out of memory
Marked as fixed in versions curl/7.82.0-2.
> reassign 1007740 src:curl 7.82.0-1
Bug #1007740 {Done: Samuel Henrique } [src:curl, 
src:xmltooling] curl breaks xmltooling autopkgtest
Bug reassigned from package 'src:curl, src:xmltooling' to 'src:curl'.
No longer marked as found in versions xmltooling/3.2.1-1 and curl/7.82.0-1.
No longer marked as fixed in versions curl/7.82.0-2.
Bug #1007740 {Done: Samuel Henrique } [src:curl] curl 
breaks xmltooling autopkgtest
Marked as found in versions curl/7.82.0-1.
> affects 1007740 src:xmltooling
Bug #1007740 {Done: Samuel Henrique } [src:curl] curl 
breaks xmltooling autopkgtest
Added indication that 1007740 affects src:xmltooling
> fixed 1007740 7.82.0-2
Bug #1007740 {Done: Samuel Henrique } [src:curl] curl 
breaks xmltooling autopkgtest
Marked as fixed in versions curl/7.82.0-2.
> thanks
Stopping processing here.

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

Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Paul Gevers]

Hi,

On 19-03-2022 14:48, Nilesh Patra wrote:

For avoidance of doubt, the canonical definition lives in the autopkgtest
package: 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst


I usually refer /usr/share/doc/autopkgtest/README.package-tests.rst.gz in the 
autopkgtest package,
I believe that's the same thingy.


Agree, except it doesn't refer so nicely in on-line discussions *and* 
the on-line document may be more up-to-date than your local copy. But, 
you're right of course.



And I would have recommended negative architectures: "-arm64" and try to
test on all architectures not explicitly mentioned for the case where new
architectures are added.


That is what I always do, I add a negation as "!", which is also what I did in
this case:

https://salsa.debian.org/med-team/toil/-/blob/master/debian/tests/control#L8


Oops. I should use the right syntax if I teach something...

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: tagging 1005981

[Debian Bug Tracking System]

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

> tags 1005981 + pending
Bug #1005981 [src:redet] Please migrate away from dpatch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1006816: Forwarded upstream

[Gianfranco Costamagna]

Hello,

On Thu, 10 Mar 2022 07:55:19 +0100 Julien Puydt  wrote:

Hi,

I forwarded the bug to
upstream: https://github.com/agronholm/anyio/issues/417

Here is the commit upstream would like feedback about:
https://github.com/agronholm/anyio/commit/184744ca291d426dd278f697c3637623eb9de0ed



sadly, it looks like its still having some troubles

=== FAILURES ===
__ test_getaddrinfo[asyncio] ___
tests/test_sockets.py:1144: in test_getaddrinfo
correct = await getaddrinfo('faß.de', 0)
anyio/_core/_sockets.py:419: in getaddrinfo
gai_res = await get_asynclib().getaddrinfo(encoded_host, port, 
family=family, type=type,
anyio/_backends/_asyncio.py:1570: in getaddrinfo
result = await get_running_loop().getaddrinfo(
/usr/lib/python3.10/asyncio/base_events.py:860: in getaddrinfo
return await self.run_in_executor(
/usr/lib/python3.10/concurrent/futures/thread.py:58: in run
result = self.fn(*self.args, **self.kwargs)
/usr/lib/python3.10/asyncio/base_events.py:843: in _getaddrinfo_debug
addrinfo = socket.getaddrinfo(host, port, family, type, proto, flags)
/usr/lib/python3.10/socket.py:955: in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
E   socket.gaierror: [Errno -2] Name or service not known
___ test_getaddrinfo[asyncio+uvloop] ___
tests/test_sockets.py:1144: in test_getaddrinfo
correct = await getaddrinfo('faß.de', 0)
anyio/_core/_sockets.py:419: in getaddrinfo
gai_res = await get_asynclib().getaddrinfo(encoded_host, port, 
family=family, type=type,
anyio/_backends/_asyncio.py:1570: in getaddrinfo
result = await get_running_loop().getaddrinfo(
uvloop/loop.pyx:1514: in getaddrinfo
???
E   socket.gaierror: [Errno -2] Name or service not known
=== short test summary info 
SKIPPED [1] tests/test_taskgroups.py:57: could not import 'trio': No module 
named 'trio'
SKIPPED [1] tests/test_fileio.py:119: Drive only makes sense on Windows
SKIPPED [1] tests/test_fileio.py:159: Only makes sense on Windows
SKIPPED [2] tests/test_fileio.py:318: os.lchmod() is not available
=== 2 failed, 751 passed, 5 skipped, 2 deselected in 17.30s 
E: pybuild pybuild:367: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.10/build; python3.10 -m pytest --verbose -W ignore 
-k "not test_is_block_device"
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --before-test 
"{interpreter} {dir}/setup.py egg_info --egg-base={dir}/.pybuild/egg" --test-pytest --test-args 
"--verbose -W ignore -k \"not test_is_block_device\"" returned exit code 13
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



full build log here

https://launchpadlibrarian.net/591544052/buildlog_ubuntu-jammy-amd64.python-anyio_3.5.0-3_BUILDING.txt.gz

G.


Can you check?

Thanks!

J.Puydt

Bug#1007929: netcfg: FTBFS on s390x

[Cyril Brulebois]

Hi Paul,

Paul Gevers  (2022-03-18):
> Source: netcfg
> Version: 1.177
> Severity: serious
> Tags: ftbfs

Thanks for the report.

> Dear maintainer,
> 
> Your package failed to migrate for 60 days, hence I spotted it. It
> fails to build from source on s390x. I hit the giveback button once
> because looking at the failing test result I suspected it is "just" a
> flaky test. However, that didn't work. The same issue happened on
> powerpc, ppc64 and sparc64 but those are not release architectures.
> 
> Paul
> 
> https://buildd.debian.org/status/fetch.php?pkg=netcfg=s390x=1.177=1642282014=0
> 
> 
> Running suite(s): inet_mton
>  inet_ptom
>  netcfg_parse_cidr_address
>  netcfg_network_address
>  netcfg_gateway_reachable
>  nc_v6_interface_configured
> 95%: Checks: 24, Failures: 1, Errors: 0
> test/test_netcfg_gateway_reachable.c:94:F:netcfg_gateway_reachable:test_netcfg_gateway_reachable_v6_fe80:0:
>  Gateway erroneously unreachable
> make[1]: *** [test/tests.mk:19: test] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j1 test returned exit code 2
> make: *** [debian/rules:6: build-arch] Error 25

Paging Samuel & Igor, hunch says this might be related:

commit 3549f77c39c06e7dfcfd59fce01ff2d4a0622058
Merge: 90e52aed 6bff2dee
Author: Samuel Thibault 
Date:   Sun Sep 5 14:59:46 2021 +

Merge branch 'ipv6-link-local-gateway' into 'master'

Add support for fe80::/10 addresses as IPv6 gateway, closes #901255

See merge request installer-team/netcfg!3


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


signature.asc
Description: PGP signature

Processed: found 1005473 in 7

[Debian Bug Tracking System]

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

> found 1005473 7
Bug #1005473 [src:gcc-11-cross-ports] gcc-11-cross-ports: FTBFS: 
s-tsmona.adb:160: undefined reference to `dladdr'
Marked as found in versions gcc-11-cross-ports/7.
> thanks
Stopping processing here.

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

Bug#1007954: [debian-mysql] Bug#1007954: galera-4 FTBFS on IPV6-only buildds

[Otto Kekäläinen]

Hi!

Thanks for looking into this. Can you elaborate why you filed this on
26.4.8 and not latest 26.4.10?

Builds are passing. Thus tests indicate that there is no issue. What is the
broken thing exactly and since tests are passing, how will we verify that
the broken thing is fixed or still broken?

Bug#1007962: sslsplit FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: sslsplit
Version: 0.5.0+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sslsplit=amd64=0.5.5-2=1640486198=0

...
Running suite(s):
 main
 opts
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1' port '10025': Name or service not known
Cannot resolve address '127.0.0.1' port '10025': Name or service not known
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
 dynbuf
 logbuf
 cert
 cachemgr
 cachefkcrt
 cachetgcrt
 cachedsess
 cachessess
 ssl
 sys
 base64
 url
 util
 pxythrmgr
 defaults
92%: Checks: 142, Failures: 0, Errors: 11
opts.t.c:99:E:proxyspec_parse:proxyspec_parse_01:0: (after this point) Early 
exit with return value 1
opts.t.c:179:E:proxyspec_parse:proxyspec_parse_05:0: (after this point) Early 
exit with return value 1
opts.t.c:203:E:proxyspec_parse:proxyspec_parse_06:0: (after this point) Early 
exit with return value 1
opts.t.c:227:E:proxyspec_parse:proxyspec_parse_07:0: (after this point) Early 
exit with return value 1
opts.t.c:251:E:proxyspec_parse:proxyspec_parse_08:0: (after this point) Early 
exit with return value 1
opts.t.c:302:E:proxyspec_parse:proxyspec_parse_11:0: (after this point) Early 
exit with return value 1
opts.t.c:342:E:proxyspec_parse:proxyspec_parse_13:0: (after this point) Early 
exit with return value 1
opts.t.c:377:E:proxyspec_parse:proxyspec_parse_14:0: (after this point) Early 
exit with return value 1
opts.t.c:414:E:proxyspec_parse:proxyspec_parse_15:0: (after this point) Early 
exit with return value 1
opts.t.c:437:E:proxyspec_parse:proxyspec_parse_16:0: (after this point) Early 
exit with return value 1
opts.t.c:487:E:proxyspec_parse:proxyspec_parse_18:0: (after this point) Early 
exit with return value 1
make[1]: *** [GNUmakefile:500: test] Error 1

Bug#1007739: marked as done (curl breaks stenographer autopkgtest: curl: (27) Out of memory)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 14:49:48 +
with message-id 
and subject line Bug#1007739: fixed in curl 7.82.0-2
has caused the Debian Bug report #1007739,
regarding curl breaks stenographer autopkgtest: curl: (27) Out of memory
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.)


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

Source: curl, stenographer
Control: found -1 curl/7.82.0-1
Control: found -1 stenographer/1.0.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
curl   from testing7.82.0-1
stenographer   from testing1.0.1-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/stenographer/19997617/log.gz

Using interface eth0
● stenographer.service - packet capture to disk
 Loaded: loaded (/lib/systemd/system/stenographer.service; 
disabled; vendor preset: enabled)

 Active: active (running) since Tue 2022-03-15 08:12:20 UTC; 15ms ago
   Docs: https://github.com/google/stenographer
 https://github.com/google/stenographer/blob/master/DESIGN.md
 https://github.com/google/stenographer/blob/master/INSTALL.md
   Main PID: 1917 (stenographer)
  Tasks: 6 (limit: 462652)
 Memory: 9.1M
CPU: 7ms
 CGroup: /system.slice/stenographer.service
 └─1917 /usr/sbin/stenographer

Mar 15 08:12:20 ci-074-d629a5ed systemd[1]: Started packet capture to disk.
active
  % Total% Received % Xferd  Average Speed   TimeTime Time 
 Current
 Dload  Upload   Total   SpentLeft 
 Speed


  0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0
100   271  100   2710 0   1532  0 --:--:-- --:--:-- --:--:-- 
 1539

● stenographer.service - packet capture to disk
 Loaded: loaded (/lib/systemd/system/stenographer.service; 
disabled; vendor preset: enabled)
 Active: active (running) since Tue 2022-03-15 08:12:20 UTC; 3min 
0s ago

   Docs: https://github.com/google/stenographer
 https://github.com/google/stenographer/blob/master/DESIGN.md
 https://github.com/google/stenographer/blob/master/INSTALL.md
   Main PID: 1917 (stenographer)
  Tasks: 13 (limit: 462652)
 Memory: 22.6M
CPU: 157ms
 CGroup: /system.slice/stenographer.service
 ├─1917 /usr/sbin/stenographer
 └─1925 /usr/sbin/stenotype --blocks=256 --seccomp=none 
--threads=1 --dir=/tmp/stenographer2493450690 --iface=eth0


Mar 15 08:12:20 ci-074-d629a5ed systemd[1]: Started packet capture to disk.
tcp0  0 127.0.0.1:1234  0.0.0.0:* 
LISTEN  1917/stenographer   Running stenographer query 'after 5m 
ago', piping to 'tcpdump '

curl: (27) Out of memory
tcpdump: truncated dump file; tried to read 4 file header bytes, only got 0
autopkgtest [08:15:21]: test run-example



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.82.0-2
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated curl package)

(This message was generated automatically at their request; if you
believe that there is a 

Bug#1007740: marked as done (curl breaks xmltooling autopkgtest)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 14:49:48 +
with message-id 
and subject line Bug#1007740: fixed in curl 7.82.0-2
has caused the Debian Bug report #1007740,
regarding curl breaks xmltooling autopkgtest
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.)


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

Source: curl, xmltooling
Control: found -1 curl/7.82.0-1
Control: found -1 xmltooling/3.2.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
curl   from testing7.82.0-1
xmltooling from testing3.2.1-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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


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

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
curl/7.82.0-1. I.e. due to versioned dependencies or breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/x/xmltooling/19997618/log.gz

FAIL: xmltoolingtest
=
   xmltooling 3.2.1: xmltoolingtest/test-suite.log
=

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

.. contents:: :depth: 2

FAIL: xmltoolingtest


Running cxxtest tests (125 tests)..1647332074 WARN XMLTooling.XMLHelper 
: DEPRECATED: attribute "ignoreCase" encountered in configuration. Use 
"caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : DEPRECATED: attribute 
"ignoreCase" encountered in configuration. Use "caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : DEPRECATED: attribute 
"ignoreCase" encountered in configuration. Use "caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : Attribute "ignoreCase" and 
"caseSensitive" should not be used in the same element.
.1647332074 WARN DirectoryWalkerTest : Unable to open directory 
(invalid)
...1647332074 ERROR XMLTooling.ParserPool : fatal error on line 
2, column 10, message: invalid document structure
.1647332074 ERROR XMLTooling.XMLObject : no default builder 
installed, found unknown child element (test:UnknownElement)
..1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping 
invalid ds:KeyValue (Modulus must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Exponent must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Modulus must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (RSAKeyValue must have Modulus.)
1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (DSKeyValue cannot have P without Q.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (P must have TextContent.)
...1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (DSKeyValue cannot have P without Q.)
..1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Q must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (P must have TextContent.)
1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (G must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping 
invalid ds:KeyValue (DSAKeyValue must have Y.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Y must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : 

Bug#1007739:

[Samuel Henrique]

Hello,

I've uploaded 7.82.0-2 with upstream's patch, hopefully fixing these issues.

Thank you to everyone who helped!

-- 
Samuel Henrique 

Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Nilesh Patra]

On Sat, Mar 19, 2022 at 02:32:12PM +0100, Paul Gevers wrote:
> > [1] https://people.debian.org/~eriberto/README.package-tests.html
> 
> For avoidance of doubt, the canonical definition lives in the autopkgtest
> package: 
> https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst

I usually refer /usr/share/doc/autopkgtest/README.package-tests.rst.gz in the 
autopkgtest package,
I believe that's the same thingy.

> And I would have recommended negative architectures: "-arm64" and try to
> test on all architectures not explicitly mentioned for the case where new
> architectures are added.

That is what I always do, I add a negation as "!", which is also what I did in
this case:

https://salsa.debian.org/med-team/toil/-/blob/master/debian/tests/control#L8

Regards,
Nilesh


signature.asc
Description: PGP signature

Processed: update bts metadata

[Debian Bug Tracking System]

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

> reassign 1007823 src:dune-common 2.8.0-3
Bug #1007823 {Done: Drew Parsons } [src:scotch, 
src:opm-grid] scotch breaks opm-grid autopkgtest: Failed to build 
dune-autopkgtest
Bug reassigned from package 'src:scotch, src:opm-grid' to 'src:dune-common'.
No longer marked as found in versions opm-grid/2021.10-2 and scotch/7.0.1-2.
No longer marked as fixed in versions dune-common/2.8.0-4.
Bug #1007823 {Done: Drew Parsons } [src:dune-common] 
scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest
Marked as found in versions dune-common/2.8.0-3.
> affects 1007823 src:opm-grid,src:scotch
Bug #1007823 {Done: Drew Parsons } [src:dune-common] 
scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest
Added indication that 1007823 affects src:opm-grid and src:scotch
> fixed 1007823 2.8.0-4
Bug #1007823 {Done: Drew Parsons } [src:dune-common] 
scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest
The source 'dune-common' and version '2.8.0-4' do not appear to match any 
binary packages
Marked as fixed in versions dune-common/2.8.0-4.
> thanks
Stopping processing here.

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

Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Paul Gevers]

Hi,

On 19-03-2022 09:26, Sascha Steinbiss wrote:

Would it be possible to add a hint to ignore arm64 autopkgtest suite?


BTW I think this is possible already in the autopkgtest definition [1] by 
adding an Architecture: section and leaving out arm64 in the list of archs you 
list in there — if that is what you mean.

Cheers
Sascha

[1] https://people.debian.org/~eriberto/README.package-tests.html


For avoidance of doubt, the canonical definition lives in the 
autopkgtest package: 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst


And I would have recommended negative architectures: "-arm64" and try to 
test on all architectures not explicitly mentioned for the case where 
new architectures are added.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007823: marked as done (scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 13:03:56 +
with message-id 
and subject line Bug#1007823: fixed in dune-common 2.8.0-4
has caused the Debian Bug report #1007823,
regarding scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest
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.)


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

Source: scotch, opm-grid
Control: found -1 scotch/7.0.1-2
Control: found -1 opm-grid/2021.10-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
scotch from testing7.0.1-2
opm-grid   from testing2021.10-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/opm-grid/20035246/log.gz


== Dune project/module generator ==

duneproject will assist you in the creation of a new Dune application.
During this process a new directory with the name of your project will be
created. This directory will hold all configuration and Makefiles and a
simple example application.

2) Which modules should this module depend on?
   The following modules have been found:
   dune-common dune-geometry dune-uggrid dune-grid dune-istl opm-common 
opm-grid
creating Project "dune-autopkgtest", version 0.0.1 which depends on 
"opm-grid"

with maintainer "DUNE autopkgtest "

A sample code dune-autopkgtest.cc is generated in the "dune-autopkgtest" 
directory.

Look at the README and dune.module files there.
Now you can run the dunecontrol script which will setup the new module.
Sometimes you may have to tweak CMakeLists.txt a bit.
--
writing initial files:
- dune-autopkgtest/README
- dune-autopkgtest/CMakeLists.txt
- dune-autopkgtest/dune-autopkgtest.pc.in
Please remember to update your dune-autopkgtest/dune-autopkgtest.pc.in,
Description and URL are missing right now.
- dune-autopkgtest/config.h.cmake
- dune-autopkgtest/src/CMakeLists.txt
- dune-autopkgtest/src/dune-autopkgtest.cc
- dune-autopkgtest/dune/autopkgtest
- dune-autopkgtest/dune/CMakeLists.txt
- dune-autopkgtest/dune/autopkgtest/CMakeLists.txt
- dune-autopkgtest/dune/autopkgtest/autopkgtest.hh
- dune-autopkgtest/doc/CMakeLists.txt
- dune-autopkgtest/doc/doxygen/Doxylocal
Doxygen is not installed! Your documentation will not work without it.
- dune-autopkgtest/doc/doxygen/CMakeLists.txt
- dune-autopkgtest/cmake/modules/CMakeLists.txt
- dune-autopkgtest/cmake/modules/DuneAutopkgtestMacros.cmake

done.
--
For further details read the Dune build system documentation at
https://www.dune-project.org/buildsystem/
- using default flags $CONFIGURE_FLAGS from environment -
--- going to build dune-autopkgtest  ---
--- calling all for dune-autopkgtest ---
--- calling vcsetup for dune-autopkgtest ---
--- calling cmake for dune-autopkgtest ---
cmake"-Ddune-common_DIR=/usr" "-Ddune-geometry_DIR=/usr" 
"-Ddune-uggrid_DIR=/usr" "-Ddune-grid_DIR=/usr" "-Dopm-common_DIR=/usr" 
"-Ddune-istl_DIR=/usr/lib//cmake/dune-istl" "-Dopm-grid_DIR=/usr" 
"/tmp/autopkgtest-lxc._4o3y13e/downtmp/autopkgtest_tmp/dune-autopkgtest"

-- The CXX compiler identification is GNU 11.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The C compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Dependencies for 

Bug#993578: marked as done (90gpg-agent generator: `gpgconf --check-programs` can hang)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 11:47:18 +
with message-id 
and subject line Bug#993578: fixed in gnupg2 2.2.27-2+deb11u1
has caused the Debian Bug report #993578,
regarding 90gpg-agent generator: `gpgconf --check-programs` can hang
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.)


-- 
993578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpg-agent
Version: 2.2.27-2
Severity: normal
File: /usr/lib/systemd/user-environment-generators/90gpg-agent

The 90gpg-agent generator calls `gpgconf --check-programs` which calls
`dirmngr` which tries to connect to localhost:9050 (Tor) for some
reason.  This can hang, causing the generator to timeout (and thus the
systemd --user instance as well) and causing 90s delay for logins.

This issue was reported once a few days ago in #-devel (user
configured firewall to drop packets, even on the lo interface) and
today on #-systemd (not sure why connection to localhost:9050 did not
succeed, Tor should even be available).

The generator should avoid relying on network operations that
potentially hang/time out.

Ansgar
--- End Message ---
--- Begin Message ---
Source: gnupg2
Source-Version: 2.2.27-2+deb11u1
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gnupg2 
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, 27 Jan 2022 14:46:11 -0500
Source: gnupg2
Architecture: source
Version: 2.2.27-2+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Closes: 982546 993578
Changes:
 gnupg2 (2.2.27-2+deb11u1) bullseye; urgency=medium
 .
   [ Raphaël Hertzog ]
   * Avoid network interaction in generator. Closes: #993578
 .
   [ Christoph Biedl ]
   * Backport "Scd: Fix CCID driver for SCM SPR332/SPR532". Closes: #982546
 .
   [ Daniel Kahn Gillmor ]
   * update git to point to debian/bullseye branch
Checksums-Sha1:
 1e2920259ba5c5504c00f446f59a5609101389d9 3322 gnupg2_2.2.27-2+deb11u1.dsc
 c55c2dae9a8f7157b975c94bfa398edd083c7d8b 63404 
gnupg2_2.2.27-2+deb11u1.debian.tar.xz
 335ee5aba52ec68d77591076599b7da3a04ca656 10498 
gnupg2_2.2.27-2+deb11u1_source.buildinfo
 7fc979ac1633b07f7ccb2fa06150402935726b05 119 gnupg2_2.2.27.orig.tar.bz2.asc
Checksums-Sha256:
 851827956ba7268a14f2043c5af8f00d833f77f238fa4f02410215d36aa6327b 3322 
gnupg2_2.2.27-2+deb11u1.dsc
 8b7117b6ea0efebd36e96b9501e03715d0954032234378c4051dfd99ca86e69d 63404 
gnupg2_2.2.27-2+deb11u1.debian.tar.xz
 e95f49328174260ba31e5d60e25581b66efbd2ba74a9dee5135b17a8f1641479 10498 
gnupg2_2.2.27-2+deb11u1_source.buildinfo
 2b44fd82da223cb629062b9c8840d92698c003be8531fc393c38f97b28cae2a4 119 
gnupg2_2.2.27.orig.tar.bz2.asc
Files:
 0990f685ff84b112f775da163ad1fcf3 3322 utils optional 
gnupg2_2.2.27-2+deb11u1.dsc
 9ac2c0363ef6e627ac2ffc4132773c1b 63404 utils optional 
gnupg2_2.2.27-2+deb11u1.debian.tar.xz
 5e8efccd4d24034bf88d06a428ecec3c 10498 utils optional 
gnupg2_2.2.27-2+deb11u1_source.buildinfo
 3a7ebb524a333b41032765eb651ea032 119 utils optional 
gnupg2_2.2.27.orig.tar.bz2.asc

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCYjT1ZAAKCRA+nXFzcd5W
XGkvAPsHwmyPMektR0yIw4gVLHs4s0IzgctafazMMeo4+dkO5QD/WF1BUq4FaYQ3
7jvPNmL66IeWO6odAfcA92wXm2vmBQk=
=aQMe
-END PGP SIGNATURE End Message ---

Bug#992065: marked as done (mpich: libhdf5-mpich-dev upgrade problems if libmpich1.0-dev is still installed)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 11:47:19 +
with message-id 
and subject line Bug#992065: fixed in mpich 3.4.1-5~deb11u1
has caused the Debian Bug report #992065,
regarding mpich: libhdf5-mpich-dev upgrade problems if libmpich1.0-dev is still 
installed
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.)


-- 
992065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpich
Version: 3.4.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libhdf5-mpich-dev

During an piuparts upgrade test of libhdf5-mpich-dev on the upgrade path
  squeeze -> wheezy -> jessie -> stretch -> buster -> bullseye
I observed this failure:

  Setting up libhdf5-mpich-dev (1.10.6+repack-4) ...
  update-alternatives: priority must be an integer

  Use 'update-alternatives --help' for program usage information.
  dpkg: error processing package libhdf5-mpich-dev (--configure):
   installed libhdf5-mpich-dev package post-installation script subprocess 
returned error exit status 2


mpi alternative setting after the failure
(after upgrade squeeze...bullseye):

# update-alternatives --query mpi
Name: mpi
Link: /usr/include/mpi
Slaves:
 libmpi++.a /usr/lib/libmpi++.a
 libmpi++.so /usr/lib/libmpi++.so
 libmpi.a /usr/lib/libmpi.a
 libmpi.so /usr/lib/libmpi.so
 mpiCC /usr/bin/mpiCC
 mpiCC.1.gz /usr/share/man/man1/mpiCC.1.gz
 mpicc /usr/bin/mpicc
 mpicc.1.gz /usr/share/man/man1/mpicc.1.gz
 mpicxx /usr/bin/mpicxx
 mpicxx.1.gz /usr/share/man/man1/mpicxx.1.gz
 mpif77 /usr/bin/mpif77
 mpif77.1.gz /usr/share/man/man1/mpif77.1.gz
 mpif90 /usr/bin/mpif90
 mpif90.1.gz /usr/share/man/man1/mpif90.1.gz
 mpireconfig /usr/bin/mpireconfig
 mpireconfig.1.gz /usr/share/man/man1/mpireconfig.1.gz
Status: auto
Best: /usr/lib/mpich/include
Value: /usr/lib/mpich/include

Alternative: /usr/lib/mpich/include
Priority: 10
Slaves:
 libmpi++.a /usr/lib/mpich/lib/libpmpich++.a
 libmpi++.so /usr/lib/mpich/lib/shared/libpmpich++.so
 libmpi.a /usr/lib/mpich/lib/libmpich.a
 libmpi.so /usr/lib/mpich/lib/shared/libmpich.so
 mpiCC /usr/bin/mpiCC.mpich
 mpiCC.1.gz /usr/share/man/man1/mpiCC.mpich.1.gz
 mpicc /usr/bin/mpicc.mpich
 mpicc.1.gz /usr/share/man/man1/mpicc.mpich.1.gz
 mpicxx /usr/bin/mpicxx.mpich
 mpicxx.1.gz /usr/share/man/man1/mpicxx.mpich.1.gz
 mpif77 /usr/bin/mpif77.mpich
 mpif77.1.gz /usr/share/man/man1/mpif77.mpich.1.gz
 mpif90 /usr/bin/mpif90.mpich
 mpif90.1.gz /usr/share/man/man1/mpif90.mpich.1.gz
 mpireconfig /usr/bin/mpireconfig.mpich
 mpireconfig.1.gz /usr/share/man/man1/mpireconfig.mpich.1.gz


and after fresh installation in bullseye:

# update-alternatives --query mpi
Name: mpi
Link: /usr/bin/mpicc
Slaves:
 hdf5-mpi.pc /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5-mpi.pc
 mpiCC /usr/bin/mpiCC
 mpic++ /usr/bin/mpic++
 mpicxx /usr/bin/mpicxx
 mpif77 /usr/bin/mpif77
 mpif90 /usr/bin/mpif90
 mpifort /usr/bin/mpifort
Status: auto
Best: /usr/bin/mpicc.mpich
Value: /usr/bin/mpicc.mpich

Alternative: /usr/bin/mpicc.mpich
Priority: 40
Slaves:
 hdf5-mpi.pc /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5-mpich.pc
 mpiCC /usr/bin/mpicxx.mpich
 mpic++ /usr/bin/mpicxx.mpich
 mpicxx /usr/bin/mpicxx.mpich
 mpif77 /usr/bin/mpifort.mpich
 mpif90 /usr/bin/mpifort.mpich
 mpifort /usr/bin/mpifort.mpich


OK, that is still an ancient mpi alternative at the time
libhdf5-mpich-dev.postinst runs ...

Probably caused by libmpich1.0-dev providing libmpich-dev and therefore
no newer libmpich-dev getting installed.

Trying to add some Breaks/Replaces ... tests running ...

BTW, installing libmpich-dev in the failure state causes

Selecting previously unselected package mpich.
Preparing to unpack .../31-mpich_3.4.1-4_amd64.deb ...
Unpacking mpich (3.4.1-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-S2t7dN/31-mpich_3.4.1-4_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/mpicc.mpich', which is also in package 
libmpich1.0-dev 1.2.7-9.1


Andreas


libhdf5-mpich-dev_1.10.6+repack-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 3.4.1-5~deb11u1
Done: Andreas Beckmann 

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

Debian distribution 

Bug#1003801: marked as done (why3 FTBFS: Error: File graph.cmo not found)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 11:34:01 +
with message-id 
and subject line Bug#1003801: fixed in why3 1.4.1-1
has caused the Debian Bug report #1003801,
regarding why3 FTBFS: Error: File graph.cmo not found
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.)


-- 
1003801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: why3
Version: 1.4.0-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/why3.html

...
Linking  lib/plugins/hypothesis_selection.cmo
File "_none_", line 1:
Error: File graph.cmo not found
make[2]: *** [Makefile:591: lib/plugins/hypothesis_selection.cmo] Error 2
--- End Message ---
--- Begin Message ---
Source: why3
Source-Version: 1.4.1-1
Done: Ralf Treinen 

We believe that the bug you reported is fixed in the latest version of
why3, 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.
Ralf Treinen  (supplier of updated why3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Mar 2022 12:16:02 +0100
Source: why3
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 1003801
Changes:
 why3 (1.4.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * New patch ocamlgraph-cma to cope with the fact that ocamlgraph does no
 longer produce graph.cmo (closes: #1003801)
   * Drop building of the why3-coq package.
Checksums-Sha1:
 17c2b967450a3447eca128d88969e9f347c4f9f8 2662 why3_1.4.1-1.dsc
 6222ebede22bbdd4d15ecdbea824c0814fa4e671 6305011 why3_1.4.1.orig.tar.gz
 1a9763d0af0b97d0691f2f18690a3f0a7763e641 20384 why3_1.4.1-1.debian.tar.xz
 a5c2eff27917f5cb1e124d515536f1f3f97f411f 14988 why3_1.4.1-1_source.buildinfo
Checksums-Sha256:
 a1ab0e558b40e0e9a7c248d86445e76b3d8321e83c4f109911523fa84fd87da8 2662 
why3_1.4.1-1.dsc
 580eec4d9af0bd4f37ebc34e1fa82b3edbed3b2f0cd0e907b1f9a94dfff51ee7 6305011 
why3_1.4.1.orig.tar.gz
 e5a3a77ab7c2fbe049893250cb68a923f4724f177d2eed188ea8f555de584c7a 20384 
why3_1.4.1-1.debian.tar.xz
 7a608a21756c24c86709d28ea35d63d4faf9d42b0be6256e736b50cd781922c1 14988 
why3_1.4.1-1_source.buildinfo
Files:
 917252715f0639192cd6bc45bb13acd2 2662 math optional why3_1.4.1-1.dsc
 4710c10b5cfeb63950f3cd12b5d91a49 6305011 math optional why3_1.4.1.orig.tar.gz
 71206d89e11a4af627444be992145edb 20384 math optional why3_1.4.1-1.debian.tar.xz
 fcad88ae6230691d321c3136826ffa7c 14988 math optional 
why3_1.4.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAmI1u8IACgkQdFxHZtTK
zf+zNQ//QeEArcHtsWVUdhSLayP+mLV6Lrc2cObbMAXHO676XkWIt14snATmmm9M
IBf4AL7gq/BMojYaTdgqpBEP16Bp9HZA6bkdamm8oKAYytZx7OpDrhZpM/HzPEm6
PcUsFstNZbO1rZJU8h31fo2G7ZGFbe84cW9kkG8sJCHsD63gWtBSoK6PuEBoi2CO
9MiCZFBcpb3yBPAEcvc366IJ2si6XZJ2W4VklJGnUi7MVnTHJxPpIiqc/Dpog0ES
c5OPy9yQVxURU3V2iPZIbPum9/qcbdlYA9EAmPz3A5+blpCD5mvEHHQymkSeffz1
yQ4dYzowbkUi0LGNnM7KEXyV24dayXTYZjOUOMoZNYie8maApiaBbaqYJTHGkTd/
7tU+7WYYYixpHKityJBWwLKMBjC8ELpGq7JdJw+mz07eX9hPK3t01hgCQ8ORBJ88
T9JQ/maU1vrgantpyq7MaUYSyRMVfTKzgtFlfZhd93VxUm68T7kJaX7rULbjTHot
jSVcyRIPX11XP97SULGozKvAfWgrzaZT4mFvNtakVETrhErZlAfmCcodZ4HIBgHw
ar5apKA9YyFZe+3ofxiEEUquqd0k7nlvHicLPPOgZ1jLHX3ZmzJCkWnx34+rSWYM
hCnVAbRb8WdsDOWqP0OVShH3eN82BqblZyPsHCIxlp95gnIZgJ4=
=ZW5F
-END PGP SIGNATURE End Message ---

Bug#1007954: galera-4 FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: galera-4
Version: 26.4.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=galera-4=amd64
https://buildd.debian.org/status/logs.php?pkg=galera-4=armel
https://buildd.debian.org/status/logs.php?pkg=galera-4=i386

...
Running suite(s): gu::asio
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram socketudp://239.255.0.1:0: 1 (Operation not 
permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram 
socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram socketudp://127.0.0.1:0: 1 (Operation not 
permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram 
socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
terminate called after throwing an instance of 'gu::Exception'
  what():  error opening datagram 
socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted)
 at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107
90%: Checks: 80, Failures: 0, Errors: 8
./galerautils/tests/gu_asio_test.cpp:1788:E:test_datagram_open:test_datagram_open:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1797:E:test_datagram_connect:test_datagram_connect:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1806:E:test_datagram_open_connect:test_datagram_open_connect:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1816:E:test_datagram_connect_multicast:test_datagram_connect_multicast:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1830:E:test_datagram_connect_multicast_local_if:test_datagram_connect_multicast_local_if:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1871:E:test_datagram_send_to_and_async_read:test_datagram_send_to_and_async_read:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1884:E:test_datagram_send_to_and_async_read_multicast:test_datagram_send_to_and_async_read_multicast:0:
 (after this point) Received signal 6 (Aborted)
./galerautils/tests/gu_asio_test.cpp:1897:E:test_datagram_write_multicast:test_datagram_write_multicast:0:
 (after this point) Received signal 6 (Aborted)
Running suite(s): gu::DeqMap
100%: Checks: 11, Failures: 0, Errors: 0
Total tests failed: 8

Start 3: check_gcomm
3/7 Test #3: check_gcomm ..   Passed0.99 sec
Start 4: gcache_tests
4/7 Test #4: gcache_tests .   Passed0.02 sec
Start 5: gcs_tests
5/7 Test #5: gcs_tests    Passed8.99 sec
Start 6: galera_check
6/7 Test #6: galera_check .   Passed1.98 sec
Start 7: wsrep_test
7/7 Test #7: wsrep_test ...   Passed0.01 sec

86% tests passed, 1 tests failed out of 7

Total Test time (real) =  17.00 sec

The following tests FAILED:
  2 - gu_tests++ (Failed)
Errors while running CTest
make[2]: *** [Makefile:129: test] Error 8

Bug#998008: marked as done (libc-bin: postinst makes a working NIS system not to work anymore at every point release)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 10:02:09 +
with message-id 
and subject line Bug#998008: fixed in glibc 2.31-13+deb11u3
has caused the Debian Bug report #998008,
regarding libc-bin: postinst makes a working NIS system not to work anymore at 
every point 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.)


-- 
998008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.31-13+deb11u2
Severity: serious
Tags: patch

Dear libc-bin maintainers:

In Debian 11, the default /etc/nsswitch.conf file has now "files"
instead of the traditional "compat".

So far, so good. This is documented in Release Notes, and those who
need NIS may change /etc/nsswitch.conf if they need it.

But there is a problem: The postinst updates the file every time
it is detected that it matches *any* old default (via md5sum).

This is a functionality which was part of base-files in the past and
it was useful when there was a default /etc/nsswitch.conf which
would work for almost everybody. But this is not the case anymore,
because the default file is not good for those using NIS.

As a result, not only upgrading a Debian 10 system to Debian 11 makes
NIS to require an adjustment (i.e. putting compat again after postinst
modifies the file), but also each and every upgrade from Debian 11
point x to Debian 11 point x+1.

Patch attached. I hope this may be fixed for Debian 11.2.

Thanks.--- a/debian/debhelper.in/libc-bin.postinst
+++ b/debian/debhelper.in/libc-bin.postinst
@@ -43,9 +43,10 @@ if [ "$1" = "configure" ] && [ "$2" = "" ] ; then
   install_from_default /usr/share/libc-bin/nsswitch.conf /etc/nsswitch.conf
 fi
 
-if [ "$1" = "configure" ] && [ "$2" != "" ]; then
-  update_to_current_default /usr/share/libc-bin/nsswitch.conf 
/etc/nsswitch.conf
-fi
+# Not ok to do this on a Debian 11 system anymore.
+# if [ "$1" = "configure" ] && [ "$2" != "" ]; then
+#   update_to_current_default /usr/share/libc-bin/nsswitch.conf 
/etc/nsswitch.conf
+# fi
 
 if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then
   ldconfig || ldconfig --verbose
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-13+deb11u3
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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: Thu, 17 Mar 2022 22:37:00 +0100
Source: glibc
Architecture: source
Version: 2.31-13+deb11u3
Distribution: bullseye
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 987266 989147 998008 998622 1004861
Changes:
 glibc (2.31-13+deb11u3) bullseye; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix bad conversion from ISO-2022-JP-3 with iconv (CVE-2021-43396).
   Closes: #998622.
 - Remove PIE check on amd64 to fix FTBFS with binutils 2.37.
 - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
 - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).
   * debian/debhelper.in/libc-bin.postinst: stop replacing older versions from
 /etc/nsswitch.conf.  Closes: #998008.
   * debian/debhelper.in/libc.preinst: simplify the version comparison by only
 comparing the two first parts, now that kernel 2.X are not supported
 anymore.  Closes: #1004861.
   * debian/debhelper.in/libc.preinst: drop the check for kernel release > 255
 now that glibc and preinstall script are fixed.  Closes: #987266.
   * debian/patches/local-CVE-2021-33574-mq_notify-use-after-free.diff:
 fix a possible use-after-free in mq_notify (CVE-2021-33574).  Closes:
 #989147.
Checksums-Sha1:
 fdc75bac6fd6f430366dae36fd7807aefb2fc46d 8347 glibc_2.31-13+deb11u3.dsc
 b95746511969a1071f03c7a79855dfd4181f4238 916044 
glibc_2.31-13+deb11u3.debian.tar.xz
 8311b1881f16eb90968469c7b26d445ace889426 8907 

Bug#996807: marked as done (tinydns stops replying to queries after a few hours)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 10:02:08 +
with message-id 
and subject line Bug#996807: fixed in djbdns 1:1.05-13+deb11u1
has caused the Debian Bug report #996807,
regarding tinydns stops replying to queries after a few hours
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.)


-- 
996807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tinydns
Version: 1:1.05-13
Severity: grave
Justification: renders package unusable


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=ro_RO (charmap=ISO-8859-2), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages tinydns depends on:
ii  init-system-helpers  1.60
ii  libc62.31-17
ii  runit-helper 2.10.3
ii  sysuser-helper   1.3.5.1

Versions of packages tinydns recommends:
pn  daemon  
pn  runit   

tinydns suggests no packages.

-- no debconf information

None of the tinydns files have been changed when this bug started manifesting
(nor the ELF or its data files).
In fact it was an update of libc which caused this. 

Any version of libc6 2.32-* will cause tinydns to ignore queries after a
while. dnscache runing on the same machine is not affected.

tinydns doesn't crash and there is nothing unusual in its logfiles.
If I kill the tinydns daemon then supervise will spawn another version
and it starts working again for a while then stops replying to queries.

Rolling back libc6 to version 2.31-17 makes tinydns working again.
--- End Message ---
--- Begin Message ---
Source: djbdns
Source-Version: 1:1.05-13+deb11u1
Done: Peter Pentchev 

We believe that the bug you reported is fixed in the latest version of
djbdns, 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.
Peter Pentchev  (supplier of updated djbdns 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, 26 Feb 2022 19:29:35 +0200
Source: djbdns
Architecture: source
Version: 1:1.05-13+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 996807
Changes:
 djbdns (1:1.05-13+deb11u1) bullseye; urgency=medium
 .
   * Add the 0011-datalimit patch to catch up with recent versions of
 glibc generating larger executable files. Closes: #996807
   * Several improvements to the Python tinytest autopkgtest tool:
 - use "with subprocess.Popen()"
 - simplify the command-line parsing a bit
 - minor import statement fixes
 - add a tox.ini file to make it easier to run static code checkers
 - turn a class into a dataclass
 - send a lot of queries to tinydns to make sure that the fix for
   #996807 actually works
Checksums-Sha1:
 9a337d741a932096331ececedd11ebaa5cae4ec7 2468 djbdns_1.05-13+deb11u1.dsc
 695f85dd5911e454b7a59a6f7dd2ee222d6d2455 60784 
djbdns_1.05-13+deb11u1.debian.tar.xz
Checksums-Sha256:
 5fc2c5a34ddc8c558e3479ee7b2af5e386924b548be1f59b33f98391a070d2fd 2468 
djbdns_1.05-13+deb11u1.dsc
 84c14f92d692ebfa644c1b0e38d2d097d743a8076a8e8d5358fa5cde63daaf03 60784 
djbdns_1.05-13+deb11u1.debian.tar.xz
Files:
 cccfba1ea8a5fff9c0250fbca99a9516 2468 net optional djbdns_1.05-13+deb11u1.dsc
 2c6cd719d11b084a85ed0b166e8683ca 60784 net optional 
djbdns_1.05-13+deb11u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmIy2UYQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffEyzZD/sHxesiFL9UgG/nrtgsC9sTO6Stajy7MYo+
BYS2LMXAgvP3R4fdRXjR45lQHjgyHWW2mF5mz7MGWSfo7IEpTYpTY6RtDhP3qZzf
F9mUwPN/iw8UCYpl9gQBUu3jBejvRj8/HLYRqmxsxn284lXUStppidT881NCm9Qb
q7mE6OjHCUk7VLajigzu1HYukXhiJjVCpG7fqDVkPmZZMuOqiSFAshbDLg7dfzIj
JKX8MdiQH2AyHOAYr1VsyXMtLz7rpplrMP1X1R9UU6O3nbERznvGkNbndZ/oBW/n
Qan85mBuuonJwbRW59gwKZiuHzwe/0c8a0eZ3MQDo7WqUC6UPsLc3v3XuhGn0MHX

Bug#1001610: marked as done (GBonds Unable to Update Redemption Tables)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 10:02:09 +
with message-id 
and subject line Bug#1001610: fixed in gbonds 2.0.3-16+deb11u1
has caused the Debian Bug report #1001610,
regarding GBonds Unable to Update Redemption Tables
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.)


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

Package: gbonds
Version: 2.0.3-8
Severity: grave

The U.S. Treasury has discontinued publishing the sbMM.asc files on 
its FTP site. Unfortunately, this means that GBonds is unable to update 
its redemption tables. Given that a, if not the, major reason to use 
GBonds is to track the current redemption value of one's U.S. Savings 
Bonds, this renders the application mostly broken as of December 1, 2021.


The good news is that Savings Bond value data is available at the 
FiscalData site as a JSON-based RESTful API. I have ported GBonds to use 
this API and will be making an upload shortly.


--
Richard
--- End Message ---
--- Begin Message ---
Source: gbonds
Source-Version: 2.0.3-16+deb11u1
Done: Richard Laager 

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

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated gbonds 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: Thu, 23 Dec 2021 21:24:14 -0600
Source: gbonds
Architecture: source
Version: 2.0.3-16+deb11u1
Distribution: bullseye
Urgency: high
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Closes: 1001610
Changes:
 gbonds (2.0.3-16+deb11u1) bullseye; urgency=high
 .
   * Add redemption data through 11/2021 (sb202106.asc)
   * Use Treasury API for redemption data (Closes: 1001610)
Checksums-Sha1:
 94ff478353035db5c1f357056456d100581621da 2014 gbonds_2.0.3-16+deb11u1.dsc
 4cc4d3e797b8862838f41871bf0e193cd84db9ec 1165574 gbonds_2.0.3.orig.tar.gz
 77d002ba55cbe49f82d2dca6d8b6a061a3c0b6b8 106820 
gbonds_2.0.3-16+deb11u1.debian.tar.xz
 1b3b8081c967133553a0e6e5e114edff29ae58c2 14324 
gbonds_2.0.3-16+deb11u1_source.buildinfo
Checksums-Sha256:
 9a08887e45c0b2f0d9af82cd28464f8026739c942cc1c9f07e2c419f131bccc0 2014 
gbonds_2.0.3-16+deb11u1.dsc
 0b07a82ed198553dcfdf5ac011087ee3cf1070f59a7eb48d7afd0b97c606dc0c 1165574 
gbonds_2.0.3.orig.tar.gz
 8b2d935a62b9bd2c773c323a2530f8d164716203d683f80659a4e51159785510 106820 
gbonds_2.0.3-16+deb11u1.debian.tar.xz
 b1d42b5319b59827a4960524374b004c69255c5a28b8ed28bc4104a55d51163b 14324 
gbonds_2.0.3-16+deb11u1_source.buildinfo
Files:
 a3ca7b09bede71ae58c8d7a447562981 2014 gnome optional 
gbonds_2.0.3-16+deb11u1.dsc
 4d9b9d7065fa3d013f21edefc10cb27a 1165574 gnome optional 
gbonds_2.0.3.orig.tar.gz
 9fc4bb27f2fdc2913dd3a735b741bc56 106820 gnome optional 
gbonds_2.0.3-16+deb11u1.debian.tar.xz
 d963983ef1931191f9fa076f6496e712 14324 gnome optional 
gbonds_2.0.3-16+deb11u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE1Ot9lOeOTujs4H+U+HlhmcBFhs4FAmHFSa0ACgkQ+HlhmcBF
hs5x3hAAmr8VvhPI1y4K73cRTPx0mTIVFG9jjtGyTHkMBxdpGfFY2UivNUBnauVH
ywcjFKxBTuJbA20FfGzIJSBW4PNnWRAj+cng7wmN6PvKNKKfiYPBKRPWC4fZ6QpQ
GxuDp7RvmQ2uEBlPkcKVbV7qrwLz87iUI3xwgnS+DuokBsY10M6bzz/bS/ESLEoS
K/+A5Drdk1033qMGITUp+wYUDFANx0lUkz3SekCvspO+xI/Xu9zkC7Gxk1kSrXlY
fml2gHqUPvInLpxWZYPxo2WiqI5HKj3iALQlUKgcLCdyWAPMwDxHlPZkeqMWqQpO
yRgnZes+X5GArkm9z+y77uWNZx7hDBC3KGRscJeGCcbwXvTptBNDOKHc0ZXfrwFY
YA9s5SNkNW0iU0/zW7FiEHMFsZUqZGkB+o4QY6cFbcGGcbj3BKLSDwSWSkhCcpkf
Y47fHyereS2eLSWMIACHBPfoYfg4dn5J32Lg4vXlDpFQjJXG+R+WBldCoUfaCUGM
XYsWk6SOZFPCSnPuWoGXmQ5a5CjxottCYQVpQ659J3300UM9d0UOfzO4fG7qIOu8
nuRIsWQTn87WdfNhX9e3o9eq7IzJOCI4xJLpg+S4pix3vtNdrZRiBTn0ulvM2Hzi
0gzub+SZ9qSnPTs+9kXZMkURn+7PJ0GTe3O9X3SP2Rn5WwFOmiw=
=Excp
-END PGP SIGNATURE End Message ---

Bug#978882: pike8.0: diff for NMU version 8.0.1116-1.1

[Adrian Bunk]

Control: tags 978882 + patch
Control: tags 978882 + pending

Dear maintainer,

I've prepared an NMU for pike8.0 (versioned as 8.0.1116-1.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru pike8.0-8.0.1116/debian/changelog pike8.0-8.0.1116/debian/changelog
--- pike8.0-8.0.1116/debian/changelog	2021-01-31 22:55:53.0 +0200
+++ pike8.0-8.0.1116/debian/changelog	2022-03-19 11:27:09.0 +0200
@@ -1,3 +1,11 @@
+pike8.0 (8.0.1116-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with autoconf2.69 to workaround FTBFS with autocof 2.71.
+(Closes: #978882)
+
+ -- Adrian Bunk   Sat, 19 Mar 2022 11:27:09 +0200
+
 pike8.0 (8.0.1116-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru pike8.0-8.0.1116/debian/control pike8.0-8.0.1116/debian/control
--- pike8.0-8.0.1116/debian/control	2018-06-24 02:07:35.0 +0300
+++ pike8.0-8.0.1116/debian/control	2022-03-19 11:27:07.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Magnus Holmgren 
 Standards-Version: 4.1.4
 Build-Depends: dpkg-dev (>= 1.15.7), debhelper (>= 9), bison,
- sharutils, bc, pkg-config, dh-autoreconf,
+ sharutils, bc, pkg-config, dh-autoreconf, autoconf2.69,
  libgmp10-dev, nettle-dev (>= 2.1~), zlib1g-dev | libz-dev,
  libbz2-dev, libgdbm-dev, unixodbc-dev, default-libmysqlclient-dev,
  libpq-dev, libsqlite3-dev, libpcre3-dev, libsdl-mixer1.2-dev,
diff -Nru pike8.0-8.0.1116/debian/patches/0001-Build-Configure-Prefer-autoconf-2.69.patch pike8.0-8.0.1116/debian/patches/0001-Build-Configure-Prefer-autoconf-2.69.patch
--- pike8.0-8.0.1116/debian/patches/0001-Build-Configure-Prefer-autoconf-2.69.patch	1970-01-01 02:00:00.0 +0200
+++ pike8.0-8.0.1116/debian/patches/0001-Build-Configure-Prefer-autoconf-2.69.patch	2022-03-19 11:18:57.0 +0200
@@ -0,0 +1,30 @@
+From 38d68a1f723ca04677f2c005f7ccfc07f004df36 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Henrik=20Grubbstr=C3=B6m=20=28Grubba=29?=
+ 
+Date: Tue, 16 Mar 2021 12:30:43 +0100
+Subject: Build [Configure]: Prefer autoconf 2.69.
+
+Avoid using autoconf 2.71.
+---
+ src/run_autoconfig | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/src/run_autoconfig b/src/run_autoconfig
+index d60b51ea00..2ab4d8e7f1 100755
+--- a/src/run_autoconfig
 b/src/run_autoconfig
+@@ -52,7 +52,10 @@ findprog() {
+ # for. There are also configure.in scripts (e.g. in Pike) that tries
+ # to detect which autoconf they're running in. These tend to fool each
+ # other, so try to avoid the script wrappers.
+-if findprog autoconf2.50 && findprog autoheader2.50; then
++if findprog autoconf2.69 && findprog autoheader2.69; then
++  autoconf=autoconf2.69
++  autoheader=autoheader2.69
++elif findprog autoconf2.50 && findprog autoheader2.50; then
+   autoconf=autoconf2.50
+   autoheader=autoheader2.50
+ else
+-- 
+2.20.1
+
diff -Nru pike8.0-8.0.1116/debian/patches/series pike8.0-8.0.1116/debian/patches/series
--- pike8.0-8.0.1116/debian/patches/series	2021-01-31 22:55:53.0 +0200
+++ pike8.0-8.0.1116/debian/patches/series	2022-03-19 11:26:46.0 +0200
@@ -13,3 +13,4 @@
 undefined_htons.patch
 bad_size_t_redef.patch
 dont_disable_debug_symbols.patch
+0001-Build-Configure-Prefer-autoconf-2.69.patch

Processed: pike8.0: diff for NMU version 8.0.1116-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 978882 + patch
Bug #978882 [src:pike8.0] pike8.0: ftbfs with autoconf 2.70
Added tag(s) patch.
> tags 978882 + pending
Bug #978882 [src:pike8.0] pike8.0: ftbfs with autoconf 2.70
Added tag(s) pending.

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

Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Nilesh Patra]

On 19 March 2022 1:56:17 pm IST, Sascha Steinbiss  wrote:
>Hi Nilesh,
>
>[…]
>> Would it be possible to add a hint to ignore arm64 autopkgtest suite?
>
>BTW I think this is possible already in the autopkgtest definition [1] by 
>adding an Architecture: section and leaving out arm64 in the list of archs you 
>list in there — if that is what you mean.

That is what I eventually did. The package even migrated to testing now[2], 
along with cwltool. So all good, I guess.

Regards,
Nilesh


>[1] https://people.debian.org/~eriberto/README.package-tests.html
[2]: https://tracker.debian.org/news/1311322/toil-560-5-migrated-to-testing/

Bug#1004562: marked as done (libguestfs: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Sat, 19 Mar 2022 11:15:12 +0200
with message-id <20220319091512.GI4190@localhost>
and subject line Fixed in 1:1.48.0-2
has caused the Debian Bug report #1004562,
regarding libguestfs: autopkgtest regression
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.)


-- 
1004562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libguestfs
Version: 1:1.46.2-11
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libguestfs/18786402/log.gz

...
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405863.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405868.414064
+ i=39
+ [ 39 -ge 40 ]
+ true
+ rv=0
+ ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 
10022 -o ConnectTimeout=5 root@localhost echo success
Connection timed out during banner exchange
Connection to 127.0.0.1 port 10022 timed out
+ rv=1
+ [ 1 -eq 0 ]
+ sleepenh 1643405868.414064 5
+ [ 1 -eq 1 ]
+ TIMESTAMP=1643405873.414064
+ i=40
+ [ 40 -ge 40 ]
+ break
+ [ 40 -eq 40 ]
+ echo timeout reached: unable to connect to qemu via ssh
+ exit 1
+ cat --show-nonprinting qemu.log
+ kill 26114
autopkgtest [21:37:54]:  summary
extlinux FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Version: 1:1.48.0-2

libguestfs (1:1.48.0-2) unstable; urgency=medium

  * Add needs-root to autopkgtetst restrictions

 -- Hilko Bengen   Fri, 18 Mar 2022 15:26:57 +0100

libguestfs (1:1.48.0-1) unstable; urgency=medium
...
  * autopkgtest: use stable image, make VM bootable, limit test to amd64

 -- Hilko Bengen   Fri, 18 Mar 2022 01:25:59 +0100



https://ci.debian.net/packages/libg/libguestfs/--- End Message ---

Bug#1005479: toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Sascha Steinbiss]

Hi Nilesh,

[…]
> Would it be possible to add a hint to ignore arm64 autopkgtest suite?

BTW I think this is possible already in the autopkgtest definition [1] by 
adding an Architecture: section and leaving out arm64 in the list of archs you 
list in there — if that is what you mean.

Cheers
Sascha

[1] https://people.debian.org/~eriberto/README.package-tests.html

Processed: block 1005747 with 1007013

[Debian Bug Tracking System]

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

> block 1005747 with 1007013
Bug #1005747 {Done: Steffen Moeller } [src:freecad] 
freecad: CVE-2021-45844 - Improper sanitization in the invocation of ODA File 
Converter
1005747 was not blocked by any bugs.
1005747 was not blocking any bugs.
Added blocking bug(s) of 1005747: 1007013
> thanks
Stopping processing here.

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