Bug#1013549: xfsdump: FTBFS: gcc: fatal error: no input files

[Michael Prokop]

Hi,

* Lucas Nussbaum [Fri Jun 24, 2022 at 12:04:39PM +0200]:
> Source: xfsdump
> Version: 3.1.9+0+nmu2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220624 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
[...]

AFAICS the new upstream release v3.1.10 of xfsdump (see
https://git.kernel.org/pub/scm/fs/xfs/xfsdump-dev.git/) doesn't seem
to fix this issue. Also updating xfsprogs to latest upstream git
(see https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/), to
provide more recent xfslibs-dev + xfsprogs, doesn't seem to help
either.

So it might be worth reaching out to upstream, though
https://marc.info/?l=linux-xfs is unavailable right now and I'm not
sure what other ways exist to check/report this towards upstream?

FTR, xfsdump got removed from Debian testing/bookworm due to this RC
bug a few days ago.

regards
-mika-


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> submitter 1017007 i...@hannover.ccc.de
Bug #1017007 [manpages-de] manpages-de: trying to overwrite .../ethers.5.gz, 
which is also in package net-tools
Changed Bug submitter to 'i...@hannover.ccc.de' from 'Ingo Saitz 
'.
> thanks
Stopping processing here.

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

Bug#1016404: marked as done (switch build depends on libnetpbm10-dev to libnetpbm-dev)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 11:35:31 +
with message-id 
and subject line Bug#1016404: fixed in xplanet 1.3.1-1
has caused the Debian Bug report #1016404,
regarding switch build depends on libnetpbm10-dev to libnetpbm-dev
to be marked as done.

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

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


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

Source: astrometry.net
Severity: serious
Control: clone -1 -2 -3 -4 -5
Control: reassign -2 src:ncview
Control: reassign -3 src:pfstools
Control: reassign -4 src:xjig
Control: reassign -5 src:xplanet

Dear maintainers,

Your package build depends on libnetpbm10-dev, but that binary isn't 
built anymore. Please build depend on the developement package without 
version in the name: libnetpbm-dev (currently provided by 
libnetpbm11-dev but hopefully in some future as a stand alone binary, 
bug #1007984).


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xplanet
Source-Version: 1.3.1-1
Done: Alexander Reichle-Schmehl 

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

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl  (supplier of updated xplanet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Aug 2022 18:34:59 +0200
Source: xplanet
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Alexander Reichle-Schmehl 
Changed-By: Alexander Reichle-Schmehl 
Closes: 939035 1003911 1016404
Changes:
 xplanet (1.3.1-1) unstable; urgency=low
 .
   [ Andreas Metzler ]
   * New upstream version 1.3.1
 + Unfuzz patches.
 + Replace giflib5.diff with a minimal patch from Gentoo (also used by
   Fedora), which also fixes the build error against giflib 5.2.
   Closes: #939035
   * [lintian] Delete trailing whitespace.
   * Use DH 12 compat level.
   * Set Rules-Requires-Root: no.
   * Set DEB_BUILD_MAINT_OPTIONS := hardening=+all.
   * Update copyright Format URL and update syntax, using unique license
 identifiers. Also drop trailing whitespace.
 .
   [ Alexander Reichle-Schmehl ]
   * Adopt package (Closes: #1003911)
   * Change build depends from libnetpbm10-dev to libnetpbm-dev (Closes: 
#1016404)
   * Add VCS headers to debian/control
   * Bump standards to 4.6.1 (no changes needed)
   * Fix missing copyright: for smile.png in debian/copyright
Checksums-Sha1:
 65cc9396ed40a1d6d6586ffe0610b8709b3c3c8c 2093 xplanet_1.3.1-1.dsc
 08a145036de033a4f1a3472a18dace5243599b83 1230358 xplanet_1.3.1.orig.tar.gz
 74fbfbde1a03975f551e79dfba566abe7d4e44f3 17864 xplanet_1.3.1-1.debian.tar.xz
 b4788a5168893f53315db2a2fee87a6b5efe729e 10154 xplanet_1.3.1-1_source.buildinfo
Checksums-Sha256:
 f5218b685e22ff799a6bdf36a8eb6128d98149722e61bd604501b86dd4cb8fc9 2093 
xplanet_1.3.1-1.dsc
 9805b08d43191d8667a2bcc5bd7fc8e3f5d5e3af3b409b0160267060448fa1a6 1230358 
xplanet_1.3.1.orig.tar.gz
 a1b570961b9b5ed766ff80e1e19e9ae650538b4a0c1a230ab511ff804b6ac1f0 17864 
xplanet_1.3.1-1.debian.tar.xz
 b950dc3bcdaa73348668af6ace2a958ae918dee90c3055de8745b7387dce3de8 10154 
xplanet_1.3.1-1_source.buildinfo
Files:
 7550cd22ae31715bd66a38a865a1544e 2093 graphics optional xplanet_1.3.1-1.dsc
 349b57ed6e4a8fc38a2699a223edf427 1230358 graphics optional 
xplanet_1.3.1.orig.tar.gz
 89f41bdab7ce7c9e402a9c79fbb77067 17864 graphics optional 
xplanet_1.3.1-1.debian.tar.xz
 0366ca284b799dde8a875651178ec5db 10154 graphics optional 
xplanet_1.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmL05RsRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE4KoQ//fNDDPP2Ofk0MFieUSYEbNWcFvweYbtHi
LYGQAkHbKc4AI5DoDYobYrJLkMiYtn9ZXd0lielsKx56zQZ8fSOiyEaUCIMcm8W4
fe5kdRNja6pXCln5WWt9YiLoZkITgsu22y/8W/l7figxQYADRCR9d3jltamn1aoN
0TxHmCKYSEm7SMQ4OTEqbb5VzMpq4nc3wqjdDCfjefTVxzTczrd8l6yVq/tZMf0t
LmUXeKV1JW9bOw4bGccfRQaQeCxx8ZpQNSJ8TnjPZ73mL3GMReNpVYgdIjT83st4
GnrPM1aHDhCeGIMOd2c1dhhGy5U9DwniRT7614Ra5DA4PtyCkeD0i/e9iZCw2BU

Bug#1017011: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-binary-tagged
Version: 0.2-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Newer versions depend on libraries not available in Debian

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1017012: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bindings-nettle
Version: 0.4-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1016927 src:gtk4
Bug #1016927 [gnome-console] gnome-console: Shortcuts being executed without 
shift being hold
Bug reassigned from package 'gnome-console' to 'src:gtk4'.
No longer marked as found in versions gnome-console/43~beta-1.
Ignoring request to alter fixed versions of bug #1016927 to the same values 
previously set
> retitle 1016927 gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11)
Bug #1016927 [src:gtk4] gnome-console: Shortcuts being executed without shift 
being hold
Changed Bug title to 'gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11)' 
from 'gnome-console: Shortcuts being executed without shift being hold'.
> affects 1016927 gnome-console
Bug #1016927 [src:gtk4] gtk4: Ctrl+Shift shortcuts executed with Ctrl only (X11)
Added indication that 1016927 affects gnome-console
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 1002113 gr-gsm: FTBFS: Unknown CMake command "GR_SWIG_MAKE"
Bug #1002113 [src:gr-gsm] gr-gsm: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
`pthread_create'
Changed Bug title to 'gr-gsm: FTBFS: Unknown CMake command "GR_SWIG_MAKE"' from 
'gr-gsm: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined 
reference to `pthread_create''.
> thanks
Stopping processing here.

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

Bug#1013909: marked as done (pngtools: Package fails to build without network access)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 13:06:37 +
with message-id 
and subject line Bug#1013909: fixed in pngtools 0.5~git20220314.1ccca3a-2
has caused the Debian Bug report #1013909,
regarding pngtools: Package fails to build without network access
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.)


-- 
1013909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pngtools
Version: 0.5~git20220314.1ccca3a-1
Severity: serious
Tags: ftbfs
Justification: 4
X-Debbugs-Cc: mi...@google.com

Dear Maintainer,

The pngtools source package currently fails to auto-build:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pngtools_0.5~git20220314.1ccca3a-1.rbuild.log.gz

Relevant snippet from the build log:
...
Working on: /build/1st/pngtools-0.5~git20220314.1ccca3a/man/pngchunkdesc.sgml
onsgmls:/build/1st/pngtools-0.5~git20220314.1ccca3a/man/pnginfo.sgml:16:59:E: 
could not resolve host "www.oasis-open.org" (try again later)
...

The reason for the build failure is that `onsgmls` (balled by `docbook2man`) 
does a SGML validation against the DTD specified in the SGML file.
The remote DTD file in question is 
http://www.oasis-open.org/docbook/sgml/4.4/docbook.dtd.
On autobuild systems however there is no network connection during the build 
and so the build fails with `could not resolve host "www.oasis-open.org"`.

You can easily reproduce this build issue (with a slightly different error 
message) by adding `127.0.0.1 www.oasis-open.org` to your `/etc/hosts`.

To fix this issue you need to make the DTD available locally. For example see 
the `openjade` package, particularly `/etc/sgml/openjade.cat` and 
`/usr/share/sgml/OpenJade/`. 

Best,

Michael Schaller
--- End Message ---
--- Begin Message ---
Source: pngtools
Source-Version: 0.5~git20220314.1ccca3a-2
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated pngtools 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, 11 Aug 2022 14:51:55 +0200
Source: pngtools
Architecture: source
Version: 0.5~git20220314.1ccca3a-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1013909
Changes:
 pngtools (0.5~git20220314.1ccca3a-2) unstable; urgency=medium
 .
   [ Michael Schaller ]
   * d/patches: Package fails to build without network access. Closes: 1013909
 .
   [ Mathieu Malaterre ]
   * d/control: Bump Std-Vers to 4.6.1 no changes needed
Checksums-Sha1:
 16f3408fdb4efb36ef14e61bf7582c6c98a7d118 2139 
pngtools_0.5~git20220314.1ccca3a-2.dsc
 f6b80b4b774027f0c306d1ebb957ca3a834fc43c 3256 
pngtools_0.5~git20220314.1ccca3a-2.debian.tar.xz
 0ff286d219d539834cac177a1893d97b16a5cdb5 8914 
pngtools_0.5~git20220314.1ccca3a-2_source.buildinfo
Checksums-Sha256:
 05d53440a119e10820f2fec282e06d09548c99a8f43bf5457e4d4e8a7ce4c81c 2139 
pngtools_0.5~git20220314.1ccca3a-2.dsc
 2413a3e8cf47b204c98220f403101b2ec550192d8fadcd149a5fc1434d1ccb0a 3256 
pngtools_0.5~git20220314.1ccca3a-2.debian.tar.xz
 2d678d958277fb773a897de4ff7320dd3eedca1877fd5e2514f185c65b67568c 8914 
pngtools_0.5~git20220314.1ccca3a-2_source.buildinfo
Files:
 c72972f3f045ab93f13b34ad80e5a53f 2139 graphics optional 
pngtools_0.5~git20220314.1ccca3a-2.dsc
 4eec025a4c3d6cf401b42b579dbf2c2d 3256 graphics optional 
pngtools_0.5~git20220314.1ccca3a-2.debian.tar.xz
 6e4e5e59508cd2bf1281c01357b9f068 8914 graphics optional 
pngtools_0.5~git20220314.1ccca3a-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmL0+68RHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0XNGQ/8CYXczcXBKnKxWYz1d4lw6lCDoH6d9nC6
GWDb7SvH53AZbmU/wPlLHoU7AAS8DOc2zhRRpUSK0e4qDxlNpgpolK/aVj+rF2Bl
3dMXex6fuwSUH1AsMcLcN16/SOKqmHle7lbv1cwmUiotxFQ/X4oR6tPlUPHKs0n/
YJocmE2YCghcx2hkHShRd7iK/jhQzbjlBd48t5YxPY25nHFwHBP9GQssMBc1RsJN
Zsx/lWPYLHgyywmZcnys/t1q+1eViRkWjF7D4exvlDPSXzOm4xTWFR5zPsgNUnN

Bug#1017013: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bindings-sane
Version: 0.0.1-13
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1017014: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bindings-uname
Version: 0.1-4
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Last upload more than 5 years ago

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1017015: gnome-console: bugs after switch to GTK4

[Jeremy Bicha]

Source: gnome-console
Severity: serious
Version: 43~beta-1

I think it would be better to prevent gnome-console from migrating to
Testing for a bit since there are some new bugs introduced in
gnome-console 43 Beta probably because of the switch to GTK4.

- Ctrl+Shift shortcuts execute with just Ctrl. Affects X but not Wayland
https://bugs.debian.org/1016927

- Copying won't work if the end of the line is selected
https://gitlab.gnome.org/GNOME/vte/-/issues/2557#note_1514177

- Open Link doesn't show in context menu
https://gitlab.gnome.org/GNOME/console/-/issues/175

Thank you,
Jeremy Bicha

Bug#1017016: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bitarray
Version: 0.0.1.1-6
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * Seems unmaintained; Last upload more than 5 years ago

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1017017: regression: lxc virt backend cannot attach to container

[Antonio Terceiro]

Package: autopkgtest
Version: 5.23
Severity: grave
Justification: renders package unusable


This was first noticed by a salsa-ci user:
https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/270#note_328972

I then tested locally, and reproduced the same issue with the snapshot I
was running from git:

8<8<8<-
autopkgtest [08:53:39]: starting date: 2022-08-11
autopkgtest [08:53:39]: version 5.23~terceiro0
autopkgtest [08:53:39]: host lemur; command line: /usr/bin/autopkgtest 
--output-dir=/tmp/autopkgtest-HicmTIAeQ --no-built-binaries --apt-upgrade 
/home/terceiro/src/debian/ruby-team/build-area/chake_0.82-1_all.deb . -- lxc 
--sudo autopkgtest-unstable-amd64
: failure: timed out waiting for testbed to start: lxc-attach: 
autopkgtest-lxc-jdtdzt: ../src/lxc/attach.c: get_attach_context: 405 Connection 
refused - Failed to get init pid
lxc-attach: autopkgtest-lxc-jdtdzt: ../src/lxc/attach.c: lxc_attach: 1469 
Connection refused - Failed to get attach context

autopkgtest [08:55:45]: ERROR: testbed failure: unexpected eof from the testbed
8<8<8<-

I get the same with 5.23 from unstable. Reverting back to 5.22 fixed
things.

I bisected locally and found out that
6ca1a0a5350026fe32b67c0ef4a64481ede83ea0 is the first bad commit
commit 6ca1a0a5350026fe32b67c0ef4a64481ede83ea0
Author: Simon McVittie 
Date:   Mon Aug 8 10:19:20 2022 +0100

virt-lxc, virt-lxd: Factor out code to wait for container to boot

This is duplicated between the two, and soon we'll want it for podman
as well.

Signed-off-by: Simon McVittie 

 Makefile  |  2 +
 lib/VirtSubproc.py| 99 ++-
 lib/await-sysv-boot   | 30 ++
 lib/detect-init-system| 15 +++
 tests/shellcheck  |  2 +
 virt/autopkgtest-virt-lxc | 27 +
 virt/autopkgtest-virt-lxd | 26 +
 7 files changed, 149 insertions(+), 52 deletions(-)
 create mode 100755 lib/await-sysv-boot
 create mode 100755 lib/detect-init-system

which makes sense.

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

Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils   2.5.2
ii  libdpkg-perl1.21.9
ii  procps  2:3.3.17-7+b1
ii  python3 3.10.5-3
ii  python3-debian  0.1.46

Versions of packages autopkgtest recommends:
ii  autodep8  0.26
ii  fakeroot  1.29-1

Versions of packages autopkgtest suggests:
ii  docker.io20.10.14+dfsg1-1+b1
ii  fakemachine  0.0~git20210901.fc48786-1+b1
ii  lxc  1:5.0.1-1
pn  lxd  
ii  ovmf 2022.05-2
pn  ovmf-ia32
ii  podman   4.0.3+ds1-1
pn  python3-distro-info  
ii  qemu-efi-aarch64 2022.05-2
ii  qemu-efi-arm 2022.05-2
ii  qemu-system  1:7.0+dfsg-7
ii  qemu-utils   1:7.0+dfsg-7
ii  schroot  1.6.12-1
ii  util-linux   2.38.1-1
ii  vmdb20.26-1

-- no debconf information


signature.asc
Description: PGP signature

Bug#1017018: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bytestring-handle
Version: 0.1.0.6-5
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1017019: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-bytestring-mmap
Version: 0.2.2-13
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Home page doesn't work
  * Seems unmaintained; Last upload more than 5 years ago

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Processed: Re: Bug#1016560: glibc 2.34 breaks scalpel autopkgtest on amd64: bash: line 1: 1961 Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +pending
Bug #1016560 [src:scalpel] glibc 2.34 breaks scalpel autopkgtest on amd64: 
bash: line 1:  1961 Segmentation fault
Added tag(s) pending.

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

Bug#1016560: glibc 2.34 breaks scalpel autopkgtest on amd64: bash: line 1: 1961 Segmentation fault

[Aurelien Jarno]

control: tag -1 +pending

On 2022-08-09 09:31, Aurelien Jarno wrote:
> control: severity 1016560 serious
> 
> On 2022-08-03 00:01, Aurelien Jarno wrote:
> > Source: scalpel
> > Version: 1.60-9
> > Severity: important
> > Tags: upstream patch
> > User: debian-gl...@lists.debian.org
> > Usertags: glibc2.34
> > 
> > Dear maintainer,
> > 
> > The autopkgtest of scalpel fails in sid on amd64 when that autopkgtest is
> > run with the binary packages of glibc from experimental. It passes when
> > run with only packages from sid. In tabular form:
> > 
> >  passfail
> > glibcfrom sid2.34-0experimental5
> > scalpel  from sid1.60-9
> > all others   from sidfrom sid
> > 
> > Here is the relevant part of the test log:
> > 
> > autopkgtest [10:36:40]: test command1: scalpel -c debian/tests/scalpel.conf 
> > debian/tests/lua.img
> > autopkgtest [10:36:40]: test command1: [---
> > 
> > Opening target 
> > "/tmp/autopkgtest-lxc.93yq46zi/downtmp/build.fXk/src/debian/tests/lua.img"
> > 
> > bash: line 1:  1961 Segmentation fault  bash -ec 'scalpel -c 
> > debian/tests/scalpel.conf debian/tests/lua.img' 2> >(tee -a 
> > /tmp/autopkgtest-lxc.93yq46zi/downtmp/command1-stderr >&2) > >(tee -a 
> > /tmp/autopkgtest-lxc.93yq46zi/downtmp/command1-stdout)
> > 
> > The full test log is available there:
> > https://ci.debian.net/data/autopkgtest/unstable/amd64/s/scalpel/24235565/log.gz
> > 
> > After some debugging, I have found the issue to be a duplicate use of a
> > va_list without using va_copy. Please find attached a patch to fix that.
> > 
> > Regards
> > Aurelien
> 
> > --- scalpel-1.60.orig/helpers.c
> > +++ scalpel-1.60/helpers.c
> > @@ -70,12 +70,14 @@ void setProgramName(char *s) {
> >  // write entry to both the screen and the audit file 
> >  void scalpelLog(struct scalpelState *state, char *format, ...) {
> >  
> > -  va_list argp;
> > +  va_list argp, argp2;
> >  
> >va_start(argp,format);
> > +  va_copy(argp2, argp);
> >vfprintf (stderr,format,argp);
> > -  vfprintf (state->auditFile,format,argp);
> >va_end(argp);
> > +  vfprintf (state->auditFile,format,argp2);
> > +  va_end(argp2);
> >  }
> >  
> >  // determine if two characters match, with optional case 
> 
> glibc 2.34 is now in unstable, upgrading the severity.

I have uploaded a NMU fixing this issue to DELAYED/2. Please find the
corresponding debdiff attached. Also please feel free to ask me to delay
or cancel this NMU.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru scalpel-1.60/debian/changelog scalpel-1.60/debian/changelog
--- scalpel-1.60/debian/changelog   2020-04-21 02:01:23.0 +
+++ scalpel-1.60/debian/changelog   2022-08-11 13:45:53.0 +
@@ -1,3 +1,11 @@
+scalpel (1.60-9+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/60_va_copy.patch: fix the va_list usage in
+setProgramName(). (Closes: #1016560).
+
+ -- Aurelien Jarno   Thu, 11 Aug 2022 15:45:53 +0200
+
 scalpel (1.60-9) unstable; urgency=medium
 
   * Team upload.
diff -Nru scalpel-1.60/debian/patches/60_va_copy.patch 
scalpel-1.60/debian/patches/60_va_copy.patch
--- scalpel-1.60/debian/patches/60_va_copy.patch1970-01-01 
00:00:00.0 +
+++ scalpel-1.60/debian/patches/60_va_copy.patch2022-08-11 
13:44:57.0 +
@@ -0,0 +1,23 @@
+Description: Fix the va_list usage in setProgramName(). (Closes: #1016560).
+Author: Aurelien Jarno 
+Last-Update: 2022-08-11
+
+--- scalpel-1.60.orig/helpers.c
 scalpel-1.60/helpers.c
+@@ -70,12 +70,14 @@ void setProgramName(char *s) {
+ // write entry to both the screen and the audit file 
+ void scalpelLog(struct scalpelState *state, char *format, ...) {
+ 
+-  va_list argp;
++  va_list argp, argp2;
+ 
+   va_start(argp,format);
++  va_copy(argp2, argp);
+   vfprintf (stderr,format,argp);
+-  vfprintf (state->auditFile,format,argp);
+   va_end(argp);
++  vfprintf (state->auditFile,format,argp2);
++  va_end(argp2);
+ }
+ 
+ // determine if two characters match, with optional case 
diff -Nru scalpel-1.60/debian/patches/series scalpel-1.60/debian/patches/series
--- scalpel-1.60/debian/patches/series  2020-04-21 01:59:40.0 +
+++ scalpel-1.60/debian/patches/series  2022-08-11 13:45:53.0 +
@@ -3,3 +3,4 @@
 30_improve-error-message.patch
 40_fix-spelling.patch
 50_fix-jpg-remove-spaces.patch
+60_va_copy.patch

Processed: Re: Bug#1016898: dolfin needs a rebuild against glibc 2.34

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #1016898 [src:dolfin] dolfin needs a rebuild against glibc 2.34
Added tag(s) pending.

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

Bug#1016898: dolfin needs a rebuild against glibc 2.34

[Aurelien Jarno]

control: tag -1 + pending

On 2022-08-09 13:21, Aurelien Jarno wrote:
> Source: dolfin
> Version: 2019.2.0~git20220407.d29e24d-5
> Severity: serious
> 
> Dear maintainer,
> 
> glibc 2.34 has merged a few libraries (libpthread, libdl, libutil,
> libanl) into libc. While this is handled transparently at runtime, there
> are a few corner cases at build time. In the case of dolfin, the file
> usr/share/dolfin/cmake/DOLFINTargets.cmake files embed the path to
> libdl.so which doesn't exist anymore.
> 
> dolfin has been binNMUed as part of the transition [1], however we later
> realised that the above file is actually in the libdolfin-dev-common
> package which is binary all. Therefore a source upload is necessary.
> 
> Could you please schedule one? There should be no change needed besides
> adding a build-depends on libc-dev (>= 2.34) to ensure it is built
> against glibc 2.34 (not all chroots have been upgraded yet).

I have uploaded a NMU fixing this issue to DELAYED/2. Please find the
corresponding debdiff attached. Also please feel free to ask me to delay
or cancel this NMU.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru dolfin-2019.2.0~git20220407.d29e24d/debian/changelog 
dolfin-2019.2.0~git20220407.d29e24d/debian/changelog
--- dolfin-2019.2.0~git20220407.d29e24d/debian/changelog2022-06-11 
18:18:26.0 +
+++ dolfin-2019.2.0~git20220407.d29e24d/debian/changelog2022-08-11 
13:59:30.0 +
@@ -1,3 +1,11 @@
+dolfin (2019.2.0~git20220407.d29e24d-5+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * No source change upload for glibc 2.34 changes, beside the extra libc-dev
+(>= 2.34) dependency.  Closes: #1016898.
+
+ -- Aurelien Jarno   Thu, 11 Aug 2022 15:59:30 +0200
+
 dolfin (2019.2.0~git20220407.d29e24d-5) unstable; urgency=medium
 
   * skip demo_mixed-poisson_mpi in build-time tests
diff -Nru dolfin-2019.2.0~git20220407.d29e24d/debian/control 
dolfin-2019.2.0~git20220407.d29e24d/debian/control
--- dolfin-2019.2.0~git20220407.d29e24d/debian/control  2022-06-11 
18:18:26.0 +
+++ dolfin-2019.2.0~git20220407.d29e24d/debian/control  2022-08-11 
13:59:30.0 +
@@ -46,7 +46,8 @@
  python3-dijitso (>= 2019.2), python3-dijitso (<< 2019.3),
  python3-numpy,
  python3-ply,
- python3-sphinx
+ python3-sphinx,
+ libc-dev (>= 2.34)
 Build-Depends-Indep:
  python3-sphinx-rtd-theme,
  doxygen,


signature.asc
Description: PGP signature

Bug#1013649: marked as done (libjpeg: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 14:50:38 +
with message-id 
and subject line Bug#1013649: fixed in libjpeg 0.0~git20220615.842c7ba-2
has caused the Debian Bug report #1013649,
regarding libjpeg: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

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

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


-- 
1013649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjpeg
Version: 0.0~git20220615.842c7ba-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> make[2]: 'autoconfig.h.in' is up to date.
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libjpeg using existing 
> ./libjpeg_0.0~git20220615.842c7ba.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file configure, use 
> --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  libjpeg-0.0~git20220615.842c7ba/autoconfig.h.in
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/libjpeg_0.0~git20220615.842c7ba-1.diff.OhEfo7
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2022-06-24T05:30:20Z


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/libjpeg_0.0~git20220615.842c7ba-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libjpeg
Source-Version: 0.0~git20220615.842c7ba-2
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated libjpeg 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, 11 Aug 2022 16:28:56 +0200
Source: libjpeg
Architecture: source
Version: 0.0~git20220615.842c7ba-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1013649
Changes:
 libjpeg (0.0~git20220615.842c7ba-2) unstable; urgency=medium
 .
   * d/patches: fix ftbfs. Closes: #1013649
Checksums-Sha1:
 7ea228717bd8ccf0d8d2f91d8e6219a12dd9d618 2144 
libjpeg_0.0~git20220615.842c7ba-2.dsc
 4ae6e476579f39e1942f09d2ea9fb24f4c3611c7 18152 
libjpeg_0.0~git20220615.842c7ba-2.debian.tar.xz
 6197a4755ea3b566fbc312c216b519a81e28f786 6534 
libjpeg_0.0~git20220615.842c7ba-2_source.buildinfo
Checksums-Sha256:
 da3ecc691dbd3c59ffdf83d7aa7cb890e7ab7cc87059ee3a221e195edc4cfb2a 2144 
libjpeg_0.0~git20220615.842c7ba-2.dsc
 3f6d1eae3168b2dfe09161478dffedb43dd803a2105e35a1264dc11b5b780520 18152 

Bug#1016340: openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.

[Colin Watson]

Control: clone -1 -2
Control: reassign -2 dh-exec
Control: retitle -2 dh-exec-install-rename sometimes moves rather than copies

On Fri, Jul 29, 2022 at 08:40:48PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > # Remove version control tags to avoid unnecessary conffile
> > # resolution steps for administrators.
> > sed -i '/\$OpenBSD:/d' \
> > debian/tmp/etc/ssh/moduli \
> > debian/tmp/etc/ssh/ssh_config \
> > debian/tmp/etc/ssh/sshd_config
> > dh_install -Nopenssh-client-udeb -Nopenssh-server-udeb
> > dh_install -popenssh-client-udeb -popenssh-server-udeb \
> > --sourcedir=debian/build-udeb
> > Failed to copy 'etc/ssh/sshd_config': No such file or directory at 
> > /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
> > dh_install: error: debian/openssh-server.install (executable config) 
> > returned exit code 127
> > make[1]: *** [debian/rules:163: override_dh_install-arch] Error 25

This seems to be a dh-exec regression, and when I fixed that I ran into
additional regressions behind it.  I'm a bit confused at this point.
You should be able to reproduce all these problems by building openssh
1:9.0p1-1.  All this used to work with dh-exec 0.23.4 - see e.g.:

  
https://buildd.debian.org/status/fetch.php?pkg=openssh&arch=amd64&ver=1%3A9.0p1-1%2Bb1&stamp=1652555012&raw=0
  
https://launchpadlibrarian.net/598976391/buildlog_ubuntu-kinetic-amd64.openssh_1%3A9.0p1-1_BUILDING.txt.gz

The first problem here is that dh_install is run multiple times, and the
first one moves a file out of debian/tmp/ when it's only supposed to
copy.  This looks like a simple typo in dh-exec-install-rename; it tries
to copy from a couple of different paths, but for the second one it
calls "move" rather than "cp", which is surely just a mistake.  Patch
for that follows:

diff --git a/lib/dh-exec-install-rename b/lib/dh-exec-install-rename
index 06fe885..2c269e8 100755
--- a/lib/dh-exec-install-rename
+++ b/lib/dh-exec-install-rename
@@ -66,9 +66,9 @@ if (/([^\s]*)\s+=>\s+([^\s]*)/ || /^=>\s+([^\s]*)/) {
 die "Failed to move '$src': $!";
 } else {
 cp ($src, File::Spec->catfile ($debpath, $dstfile)) or
-move (File::Spec->catfile ("debian/tmp", $src),
-  File::Spec->catfile ($debpath, $dstfile)) or
-  die "Failed to copy '$src': $!";
+cp (File::Spec->catfile ("debian/tmp", $src),
+File::Spec->catfile ($debpath, $dstfile)) or
+die "Failed to copy '$src': $!";
 }
 }
 

The second dh_install command does the same copies even though it isn't
supposed to be processing those packages, which is when we hit the
failure.  Horrible, but maybe that's just how debhelper handles
executable config files and dh-exec doesn't get much choice?  Not sure.
(Relatedly, though it doesn't affect openssh, how can
dh-exec-install-move possibly work properly if every dh_install run will
end up moving files regardless of whether it's operating on the package
in question?)

After applying the above fix, the build gets further, and I get to:

   dh_missing
dh_missing: warning: dh-exec.aqR1q_B1/etc/ufw/applications.d/openssh-server 
exists in debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec._KAY3sIj/etc/ufw/applications.d/openssh-server")
dh_missing: warning: 
dh-exec.aqR1q_B1/usr/share/apport/package-hooks/openssh-server.py exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec._KAY3sIj/usr/share/apport/package-hooks/openssh-server.py")
dh_missing: warning: dh-exec.aqR1q_B1/usr/share/openssh/sshd_config exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec._KAY3sIj/usr/share/openssh/sshd_config")
dh_missing: warning: dh-exec.aqR1q_B1/usr/share/openssh/sshd_config.md5sum 
exists in debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec._KAY3sIj/usr/share/openssh/sshd_config.md5sum")
dh_missing: warning: 
dh-exec.eZqm_1C4/usr/share/apport/package-hooks/openssh-client.py exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec.eqEKo0TP/usr/share/apport/package-hooks/openssh-client.py")
dh_missing: warning: dh-exec.slLLJC8v/usr/lib/openssh/gnome-ssh-askpass exists 
in debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/dh-exec.kGOu1t93/usr/lib/openssh/gnome-ssh-askpass")
dh_missing: warning: etc/ssh/sshd_config exists in debian/tmp but is not 
installed to anywhere (related file: 
"debian/tmp/dh-exec._KAY3sIj/usr/share/openssh/sshd_config")
dh_missing: error: missing files, aborting

While detecting missing files, dh_missing noted some files with a 
similar name to those
that were missing.  This error /might/ be resolved by replacing 
references to

Processed: Re: Bug#1016340: openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1016340 [src:openssh] openssh: FTBFS: Failed to copy 
'etc/ssh/sshd_config': No such file or directory at 
/usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
Bug 1016340 cloned as bug 1017023
> reassign -2 dh-exec
Bug #1017023 [src:openssh] openssh: FTBFS: Failed to copy 
'etc/ssh/sshd_config': No such file or directory at 
/usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
Bug reassigned from package 'src:openssh' to 'dh-exec'.
No longer marked as found in versions openssh/1:9.0p1-1.
Ignoring request to alter fixed versions of bug #1017023 to the same values 
previously set
> retitle -2 dh-exec-install-rename sometimes moves rather than copies
Bug #1017023 [dh-exec] openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No 
such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> 
line 7.
Changed Bug title to 'dh-exec-install-rename sometimes moves rather than 
copies' from 'openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such 
file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 
7.'.

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

Bug#1016564: marked as done (haskell-cracknum FTBFS: Package contains no library to register: crackNum-3.2)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 15:19:04 +
with message-id 
and subject line Bug#1016564: fixed in haskell-cracknum 3.2-2
has caused the Debian Bug report #1016564,
regarding haskell-cracknum FTBFS: Package contains no library to register: 
crackNum-3.2
to be marked as done.

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

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


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

https://buildd.debian.org/status/logs.php?pkg=haskell-cracknum&ver=3.2-1

...
Running debian/hlibrary.setup copy --builddir=dist-ghc 
--destdir=debian/tmp-inst-ghc
Installing executable crackNum in debian/tmp-inst-ghc/usr/bin
ln --symbolic --force "debian/tmp-inst-ghc" debian/tmp
dh_haskell_install_ghc_registration --package=libghc-cracknum-dev
Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config 
--verbose=verbose+nowrap
Package contains no library to register: crackNum-3.2...
Cannot generate package registration. at 
/usr/bin/dh_haskell_install_ghc_registration line 70.
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:194: 
install/libghc-cracknum-dev] Error 25
--- End Message ---
--- Begin Message ---
Source: haskell-cracknum
Source-Version: 3.2-2
Done: Ilias Tsitsimpis 

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-cracknum 
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, 11 Aug 2022 17:52:10 +0300
Source: haskell-cracknum
Architecture: source
Version: 3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1016564
Changes:
 haskell-cracknum (3.2-2) unstable; urgency=medium
 .
   * Remove libghc-* binary packages (Closes: #1016564)
   * Add dependency on the z3 solver
Checksums-Sha1:
 b27aa88fa59ac1fb4039a71caf2988723836f876 2199 haskell-cracknum_3.2-2.dsc
 84801ae0929a03c7fdeeaefff6fa1f44dc9ea072 2884 
haskell-cracknum_3.2-2.debian.tar.xz
 140e0fe97d15c6f3377092838d7985ff52ce3c92 8719 
haskell-cracknum_3.2-2_amd64.buildinfo
Checksums-Sha256:
 b94671f679996243540ef97d743f78d6740c7edf8d0440426659b6558338fa88 2199 
haskell-cracknum_3.2-2.dsc
 f2e3d19083d781a61c811e5a4654422e639d160db68dc4b2230f19ce265e721e 2884 
haskell-cracknum_3.2-2.debian.tar.xz
 881edcf01f05398b97d2c28bb6c4a24fb98a6f59e50c00903e9e781568cde615 8719 
haskell-cracknum_3.2-2_amd64.buildinfo
Files:
 5ed0707050c072e906ded8f1622e52f3 2199 haskell optional 
haskell-cracknum_3.2-2.dsc
 e475fce3e3fa42ce9e8a6958a9ca8ffb 2884 haskell optional 
haskell-cracknum_3.2-2.debian.tar.xz
 fa8cd404b4cca1b329093b5a92c021bc 8719 haskell optional 
haskell-cracknum_3.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmL1GlcUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwFERAAmrhehyJCZoro6E3zCcJap9EDdHc0
J5/T8hoAU0wjUoZIWCmPk/l+0/GNe3kQTCUTGZ6IKEDVfFPKIFJyJ98VnggCPFgv
ZS3g3dRI7ZLaQGX6Aq1HupAqcNlY89ZoANgoS0gHUF5bxhmGi/ITDhb/oi7ovT40
dhcJUQr/pMuyD31hkt5v2kG1Wf8NHu+CQbojC4g2BgJTTg8YDeeru+5GKt1yJEb6
WQFmi5e5V/HLqzoyXkS8r4zdRxOckaM9/Y/xDVW4qlx2pZL/fFQYGPLojwhnFgIV
A5gwLQr+WnSAm1/FvXIVWYUqzZF1mnWbdDg+R7qdOFTRQX2mtvilgN2LhSkybd8K
vp/3uA4LKUxO6S/O8EVtYD/i/xTTr7mAkqdF2woE3v5Oc9blUeERLxrrnnr5kyqd
lK1r/+hV3pDSe/NoT/k2ESfizUhkP0bOnDfl5yv6lE5rygDhYuNhzyWHOmuQsqnH
rZZQTQEMTSzd3uuPTjv2Jyi2qdY4rftwBdQKOnxdrfV3FenPdcM5MN817Tju2+VM
3FUD4SHX9IH7VmzmrFt1fdo+cHgZ0QUdS6IIi4bYn3eoO6Xttew2lyz0LxU+wHLa
fI4pKg+atsSkdjegnYEfFDuasIlJcpGDHh9G0Oc23Qo7z+EgqdqvCRmPycCHeriX
/MqWYsV7dD+Z0MA=
=NyVG
-END PGP SIGNATURE End Message ---

Processed: Bug#1016340 marked as pending in openssh

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016340 [src:openssh] openssh: FTBFS: Failed to copy 
'etc/ssh/sshd_config': No such file or directory at 
/usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
Added tag(s) pending.

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

Bug#1016340: marked as pending in openssh

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1016340 in openssh 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/ssh-team/openssh/-/commit/dd1e52af266a53671b162ddd95e4f6b01513e8e5


Work around apparent dh-exec regressions

Closes: #1016340


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016340

Bug#1017027: gdcm: ftbfs, sed command in debian/rules fails

[Jeremy Bicha]

Source: gdcm
Version: 3.0.13-3
Severity: serious
Tags: ftbfs sid

gdcm fails to build from source in my unstable sbuild.

make[1]: Leaving directory '/<>'
   jh_build -O--buildsystem=cmake\+ninja
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/<>'
echo "Do not run build time tests for this package"
Do not run build time tests for this package
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test-indep
make[1]: Entering directory '/<>'
echo "No tests needed for docs"
No tests needed for docs
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary --with cli --with python3 --with javahelper  --buildsystem=cmake+ninja
   dh_testroot -O--buildsystem=cmake\+ninja
   dh_prep -O--buildsystem=cmake\+ninja
   dh_installdirs -O--buildsystem=cmake\+ninja
   debian/rules override_dh_auto_install-arch
make[1]: Entering directory '/<>'
# See #664188
sed -i -e "s/FATAL_ERROR/STATUS/g"
obj-*/CMake/ExportConfiguration/CMakeFiles/Export/lib/x86_64-linux-gnu/gdcm-*/GDCMTargets-*.cmake
sed: can't read
obj-*/CMake/ExportConfiguration/CMakeFiles/Export/lib/x86_64-linux-gnu/gdcm-*/GDCMTargets-*.cmake:
No such file or directory
make[1]: *** [debian/rules:115: override_dh_auto_install-arch] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:54: binary] Error 2

Thank you,
Jeremy Bicha

Bug#1017007: marked as done (manpages-de: trying to overwrite .../ethers.5.gz, which is also in package net-tools)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 18:38:46 +
with message-id 
and subject line Bug#1017007: fixed in manpages-l10n 4.15.0-4
has caused the Debian Bug report #1017007,
regarding manpages-de: trying to overwrite .../ethers.5.gz, which is also in 
package net-tools
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.)


-- 
1017007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-de
Version: 4.14.0-4
Severity: serious
Tags: l10n
Justification: Policy 7.6.1

Unpacking manpages-de (4.15.0-3) over (4.14.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/manpages-de_4.15.0-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/de/man5/ethers.5.gz', which is also in 
package net-tools 1.60+git20181103.0eebece-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/manpages-de_4.15.0-3_all.deb


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

Kernel: Linux 5.19.0-pinguin20220731 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

manpages-de depends on no packages.

manpages-de recommends no packages.

Versions of packages manpages-de suggests:
it  man-db [man-browser]  2.10.2-1
ii  manpages  5.13-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: manpages-l10n
Source-Version: 4.15.0-4
Done: Dr. Helge Kreutzmann 

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

Debian distribution maintenance software
pp.
Dr. Helge Kreutzmann  (supplier of updated manpages-l10n 
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, 11 Aug 2022 18:45:03 +0200
Source: manpages-l10n
Architecture: source
Version: 4.15.0-4
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Helge Kreutzmann 
Closes: 1016989 1017006 1017007
Changes:
 manpages-l10n (4.15.0-4) unstable; urgency=medium
 .
   * Remove conflicting man pages. Closes: #1016989, #1017006, #1017007.
Checksums-Sha1:
 1401a1698464a515047e5e89733b21dd4c204c42 3481 manpages-l10n_4.15.0-4.dsc
 2537935c404467fa6419859f27d215221402d3a9 59316 
manpages-l10n_4.15.0-4.debian.tar.xz
 693b0862a0406d1abb7449b88473e99263b38d19 12876 
manpages-l10n_4.15.0-4_amd64.buildinfo
Checksums-Sha256:
 85a5c5c0963b25bba6507b9369d641b544a66bb20e8de81d97e06f9ff9dbb3fa 3481 
manpages-l10n_4.15.0-4.dsc
 6c1186f8d83f8041d5f416638ec29ccf0229a09b0c15c00a6a09b4d1b1a1f161 59316 
manpages-l10n_4.15.0-4.debian.tar.xz
 a44fe68cf68b932eed91d8258d87373391ebd96b55a6319812ac189c80280e6f 12876 
manpages-l10n_4.15.0-4_amd64.buildinfo
Files:
 6bb63cc6ad39191079cedc4e2b16079d 3481 doc optional manpages-l10n_4.15.0-4.dsc
 ff47b768f1a10e9adfc7cba0c33c1774 59316 doc optional 
manpages-l10n_4.15.0-4.debian.tar.xz
 a9b55e3ab6879aaf22458303c0a52776 12876 doc optional 
manpages-l10n_4.15.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmL1SQgACgkQQbqlJmgq
5nB9sg//elDltOsYbgGxPj9w4BTIWvOnMWVZyyVC82CFc+fMsuwwJVX46ODGfKV8
lZrz3H6bVtZzyX34hs9ms63uCPjtXgTK9Ck+jk7gosTaQQZlSCURRI7JCWMnfduE
xIjCeij9gsL4CZmaIE7gchxd4jJFq5+YmPAncfqhqZqKz5KZ9bJy2aHGtfoRC8VV
/tION8nxyOPqRNfIuY/ZuCO+z4uXvcQdrk9Tqkt33hm7Rh9DrSAfx4bZLs7sB716
3sSPFGrK3jZTb+neDQtgNtV4Fxbi5Atw6gZXqxlMdJBu8WO0RDaEo0fl3fH3ey57
dXpDuUXAEAQ2X+hoId/fPelBbWO3tr4D33tUXmGuwKRcASGk+1LxGVlVFF3zQE7w
I6663jM/o0mSkNDiYgFFT+/Um5//Exrv+E3u0EJjGxNrj+mF3gkO7fi/lTEE7fBZ
YF98+G2cgmv/1MX/rIpXd9tgmFoN1ReUHnKi8QNriVoKammoCgoaxIqgOlwMu6n1
x03SXbgFayFylCVX3lFX3/7/L+vsYBYSInbVovJldIgT2xsTgJbWw110jXTNLSRf
UFdktCxwZ1C8iyMyCRI9gVHMpNiuD3VovSS43tnkvSlHt6N9XW4X8AhrMVc31Ufl
Hlf8YFnn3fB8vNo1DGHFjLfCFiTeLHyL96RmP/pF+LRuOCtyhqE=
=d2Bo

Bug#1016989: marked as done (manpages-fr: trying to overwrite tree.1.gz, which is also in package tree 2.0.2-1)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 18:38:46 +
with message-id 
and subject line Bug#1016989: fixed in manpages-l10n 4.15.0-4
has caused the Debian Bug report #1016989,
regarding manpages-fr: trying to overwrite tree.1.gz, which is also in package 
tree 2.0.2-1
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.)


-- 
1016989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-fr
Version: 4.15.0-3
Severity: grave
Justification: renders package unusable

manpages-fr 4.15.0-3 cannot be installed:

Unpacking manpages-fr (4.15.0-3) over (4.14.0-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-n3cIma/18-manpages-fr_4.15.0-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man1/tree.1.gz', which is also in 
package tree 2.0.2-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

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

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

manpages-fr depends on no packages.

manpages-fr recommends no packages.

Versions of packages manpages-fr suggests:
ii  man-db [man-browser]  2.10.2-1
ii  manpages  5.13-1

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: manpages-l10n
Source-Version: 4.15.0-4
Done: Dr. Helge Kreutzmann 

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

Debian distribution maintenance software
pp.
Dr. Helge Kreutzmann  (supplier of updated manpages-l10n 
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, 11 Aug 2022 18:45:03 +0200
Source: manpages-l10n
Architecture: source
Version: 4.15.0-4
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Helge Kreutzmann 
Closes: 1016989 1017006 1017007
Changes:
 manpages-l10n (4.15.0-4) unstable; urgency=medium
 .
   * Remove conflicting man pages. Closes: #1016989, #1017006, #1017007.
Checksums-Sha1:
 1401a1698464a515047e5e89733b21dd4c204c42 3481 manpages-l10n_4.15.0-4.dsc
 2537935c404467fa6419859f27d215221402d3a9 59316 
manpages-l10n_4.15.0-4.debian.tar.xz
 693b0862a0406d1abb7449b88473e99263b38d19 12876 
manpages-l10n_4.15.0-4_amd64.buildinfo
Checksums-Sha256:
 85a5c5c0963b25bba6507b9369d641b544a66bb20e8de81d97e06f9ff9dbb3fa 3481 
manpages-l10n_4.15.0-4.dsc
 6c1186f8d83f8041d5f416638ec29ccf0229a09b0c15c00a6a09b4d1b1a1f161 59316 
manpages-l10n_4.15.0-4.debian.tar.xz
 a44fe68cf68b932eed91d8258d87373391ebd96b55a6319812ac189c80280e6f 12876 
manpages-l10n_4.15.0-4_amd64.buildinfo
Files:
 6bb63cc6ad39191079cedc4e2b16079d 3481 doc optional manpages-l10n_4.15.0-4.dsc
 ff47b768f1a10e9adfc7cba0c33c1774 59316 doc optional 
manpages-l10n_4.15.0-4.debian.tar.xz
 a9b55e3ab6879aaf22458303c0a52776 12876 doc optional 
manpages-l10n_4.15.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmL1SQgACgkQQbqlJmgq
5nB9sg//elDltOsYbgGxPj9w4BTIWvOnMWVZyyVC82CFc+fMsuwwJVX46ODGfKV8
lZrz3H6bVtZzyX34hs9ms63uCPjtXgTK9Ck+jk7gosTaQQZlSCURRI7JCWMnfduE
xIjCeij9gsL4CZmaIE7gchxd4jJFq5+YmPAncfqhqZqKz5KZ9bJy2aHGtfoRC8VV
/tION8nxyOPqRNfIuY/ZuCO+z4uXvcQdrk9Tqkt33hm7Rh9DrSAfx4bZLs7sB716
3sSPFGrK3jZTb+neDQtgNtV4Fxbi5Atw6gZXqxlMdJBu8WO0RDaEo0fl3fH3ey57
dXpDuUXAEAQ2X+hoId/fPelBbWO3tr4D33tUXmGuwKRcASGk+1LxGVlVFF3zQE7w
I6

Bug#1016444: marked as done (snd: build depends on libnotcurses-dev not available in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 19:04:50 +
with message-id 
and subject line Bug#1016444: fixed in snd 22.6-1
has caused the Debian Bug report #1016444,
regarding snd: build depends on libnotcurses-dev not available in bookworm
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.)


-- 
1016444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snd
Version: 22.3-1
Severity: serious
Control: block -1 by 1001661

Dear maintainer,

libnotcurses-dev hasn't been in bookworm/testing for nearly three
months. Your package build depends on it, so your package can't be
rebuild in bookworm. It's also blocking the migration of the version
in unstable. As you noted in the notcurses bug, your package seems
buildable without the dependency so I think for now that's the best
way forward.

I didn't want to downgrade 1001661 because the latest version had
three timeouts in March, so the issue doesn't seem solved yet. To
confirm I triggered 10 new runs and 1 of them timed out. The ratio
just isn't good enough.

Paul
--- End Message ---
--- Begin Message ---
Source: snd
Source-Version: 22.6-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated snd 
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, 11 Aug 2022 20:42:56 +0200
Source: snd
Architecture: source
Version: 22.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1016444
Changes:
 snd (22.6-1) unstable; urgency=medium
 .
   * New upstream version 22.6
 + Update d/upstream-changelog
   * Drop B-D on notcurses (Closes: #1016444)
   * Provide s7.h (in a private location) for dynamically creating libc_s7.so
   * Add autopkgtests
Checksums-Sha1:
 52281dfb93005441e327c292080baf3bb2fce918 2815 snd_22.6-1.dsc
 548b0fd5e6e717492857ff5364aed7e5030a4862 14681128 snd_22.6.orig.tar.gz
 c3851e2d98ec41ef70bbb585b83bcc9cf70baf79 79672 snd_22.6-1.debian.tar.xz
Checksums-Sha256:
 be355fb693c4de57ff6a1047db80eb8d3d74e16ec96e639f413c8aac307e3ce5 2815 
snd_22.6-1.dsc
 942043efbcd4ec27857348e227b2ee3d6c65f330b404157f6d2c7badee2a1255 14681128 
snd_22.6.orig.tar.gz
 0920b5e4910cffdacd791f5173edcf2534e1731a059295cc60b467f4502f90f9 79672 
snd_22.6-1.debian.tar.xz
Files:
 75c7f8bf37110308e7b3de24ce10a3b4 2815 sound optional snd_22.6-1.dsc
 e8691c3d8ec7e5b036ef96558c6d73e6 14681128 sound optional snd_22.6.orig.tar.gz
 6b22ad17b0ede5b8bff69857bbf440a7 79672 sound optional snd_22.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmL1TnQWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EUTD/9k7qVGxuFrFzkdhwIk6ZBlAYnu
im5s/uERSOAO1OP+lWI/TWc5+7SIwHmiFHOqqgV8b/m61j3mikyvdFsxlS8OiL1W
jC+WhCJ/0d6zJ0QmyRxOo5NTI0+vbcvETaWbLCGJYkoMVH4XiOvahGebMjhPB2dr
xQAOd1+X1Dd4mQ3cNHGeUL0lh5/pFL0lPX7ISXjaLbSeA/qBcTaRjPc8cI+sNrRM
4CiPcYDJfEEGuuIFScLazq21GULHATq68Hwow2AiMHhicsv3R0n2vDbWLmf1zYRs
tu6UHcseZDtfeIaf+wh+6q0shSZkR1DHGh7xWHWtR6orNRlOCl/boZuKCZOLTtWr
WjjMLkZORfB3KaejYBCamfsJ5ajpB0E156j1Jpf4ddMYRtqrZ1dQbUbA8ZoXwvWK
Lxom3hNtwKtrw8jAUcprhWAMu88UDIQe1psuVz6HWsw8V9F1XHk/SM4ua7+JEXJ9
7Up+Ix8QmLlPmFq9ipMKR/yVZUagfcvdzct4VkEyYKfjo1PN6ED1HR5Vx9jxj7Ns
6dkELOIHFLFtRA0cr/+YpuIORvXOUK1WOu8uMaGDeyPujsDn8pn4Qq3a9SS6MGMt
MN6Bx7X0ujbSwFzodbr2c1GKBFicGnjbEsVLGJ0ivJxxlxpJa2CkvYvpQxo+re5e
ZJODXitaId2DSFVJyg==
=+ORd
-END PGP SIGNATURE End Message ---

Bug#1017017: regression: lxc virt backend cannot attach to container

[Simon McVittie]

On Thu, 11 Aug 2022 at 10:32:35 -0300, Antonio Terceiro wrote:
> : failure: timed out waiting for testbed to start: lxc-attach: 
> autopkgtest-lxc-jdtdzt: ../src/lxc/attach.c: get_attach_context: 405 
> Connection refused - Failed to get init pid

Please could you try with
?
I'd prefer not to revert the commit completely, because if I do that,
I'll have to duplicate the same logic in autopkgtest-virt-podman.

I haven't seen this happen on autopkgtest's own Gitlab-CI, or in several
runs of its complete autopkgtest suite under qemu on my laptop.

I'm sorry 5.23 has been such a low-quality release. I had hoped that the
amount of test coverage it has had would be sufficient to avoid that,
but it seems I've reached the fail state where it takes 2 hours to get
a release out *and* the release is broken.

smcv

Bug#1017030: dictd: yields "client_read_status: Connection reset by peer" in the client

[Vincent Lefevre]

Package: dictd
Version: 1.13.0+dfsg-1
Severity: grave
Justification: renders package unusable

I get the following error:

$ dict foo
dict (client_read_status): Error reading from socket
 client_read_status: Connection reset by peer

A strace shows

[...]
connect(3, {sa_family=AF_INET, sin_port=htons(2628), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
write(3, "client \"dict 1.13.0/rf on Linux "..., 65) = 65
read(3, 0x7fffc776e2f7, 1)  = -1 ECONNRESET (Connection reset by 
peer)
write(2, "dict (client_read_status): ", 27) = 27
write(2, "Error reading from socket\n", 26) = 26
write(2, " client_read_status: Connection "..., 46) = 46
exit_group(1)   = ?

With telnet:

$ telnet localhost 2628
Trying ::1...
Connection failed: Connection refused
Trying 127.0.0.1...
flushoutput character is 'off'.
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

i.e. the connection to 127.0.0.1 succeeds, but is immediately closed.

$ ps -fC dictd
UID  PIDPPID  C STIME TTY  TIME CMD
dictd   5039   1  0 Aug08 ?00:00:00 dictd 1.13.0: 1/12

The dictd version hasn't changed for 2 years. So I suspect that dictd
got broken by some library upgrade.

With telnet, a strace on the server gives

# strace -f -p 5039
strace: Process 5039 attached
accept(3, {sa_family=AF_INET, sin_port=htons(52874), 
sin_addr=inet_addr("127.0.0.1")}, [16]) = 6
clone(child_stack=NULL, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLDstrace: Process 202087 
attached
, child_tidptr=0x7fa42f269e50) = 202087
[pid 202087] set_robust_list(0x7fa42f269e60, 24 
[pid  5039] close(6 
[pid 202087] <... set_robust_list resumed>) = 0
[pid  5039] <... close resumed>)= 0
[pid  5039] accept(3,  
[pid 202087] alarm(0)   = 0
[pid 202087] rt_sigaction(SIGALRM, {sa_handler=0x5631a9394d50, sa_mask=[], 
sa_flags=SA_RESTORER, sa_restorer=0x7fa42f2a3940}, NULL, 8) = 0
[pid 202087] alarm(600) = 0
[pid 202087] newfstatat(AT_FDCWD, "/etc/resolv.conf", {st_mode=S_IFREG|0644, 
st_size=137, ...}, 0) = 0
[pid 202087] openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 7
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=9, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] read(7, "multi on\n", 4096) = 9
[pid 202087] read(7, "", 4096)  = 0
[pid 202087] close(7)   = 0
[pid 202087] futex(0x7fa42f43da8c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
[pid 202087] openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 7
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=137, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] read(7, "# Generated by NetworkManager\nse"..., 4096) = 137
[pid 202087] read(7, "", 4096)  = 0
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=137, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] close(7)   = 0
[pid 202087] socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 7
[pid 202087] connect(7, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 
110) = -1 ENOENT (No such file or directory)
[pid 202087] close(7)   = 0
[pid 202087] socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 7
[pid 202087] connect(7, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 
110) = -1 ENOENT (No such file or directory)
[pid 202087] close(7)   = 0
[pid 202087] newfstatat(AT_FDCWD, "/etc/nsswitch.conf", {st_mode=S_IFREG|0644, 
st_size=545, ...}, 0) = 0
[pid 202087] openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 7
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=120622, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] mmap(NULL, 120622, PROT_READ, MAP_PRIVATE, 7, 0) = 0x7fa42f483000
[pid 202087] close(7)   = 0
[pid 202087] openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", 
O_RDONLY|O_CLOEXEC) = 7
[pid 202087] read(7, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=14328, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] mmap(NULL, 16400, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 7, 0) = 
0x7fa42c59
[pid 202087] mmap(0x7fa42c591000, 4096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x1000) = 0x7fa42c591000
[pid 202087] mmap(0x7fa42c592000, 4096, PROT_READ, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x2000) = 0x7fa42c592000
[pid 202087] mmap(0x7fa42c593000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x2000) = 0x7fa42c593000
[pid 202087] close(7)   = 0
[pid 202087] mprotect(0x7fa42c593000, 4096, PROT_READ) = 0
[pid 202087] munmap(0x7fa42f483000, 120622) = 0
[pid 202087] openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 7
[pid 202087] newfstatat(7, "", {st_mode=S_IFREG|0644, st_size=120622, ...}, 
AT_EMPTY_PATH) = 0
[pid 202087] mmap(NULL, 120622, PROT_READ, MAP_PRIVATE, 7, 0) = 0x7fa42f483000
[pid 202087] close(7)   = 0
[pid 202087] open

Bug#1013939: closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#1013939: fixed in python-xarray 2022.06.0-2)

[Paul Gevers]

Control: reopen -1

Hi,

On 10-08-2022 20:51, Debian Bug Tracking System wrote:

  python-xarray (2022.06.0-2) unstable; urgency=medium
  .
* Update  no-installer.patch to avoid accidentally claiming we're
 still at 0.16.1; this was breaking cfgrib
* Temporarily drop zarr support as it segfaults tests
* Temporarily drop rasterio support as python3-rasterio can't find
  proj.db in tests
* Drop bottleneck patch; 1.3.2 now in Debian
* Bug fixed in recent upload: Closes: #1013939


But the log [1] that was generated by the migration trial run has


=== FAILURES 
===
___ test_weighted_operations_nonequal_coords 
___


def test_weighted_operations_nonequal_coords():
# There are no weights for a == 4, so that data point is ignored.
weights = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[0, 1, 2, 3]))
data = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[1, 2, 3, 4]))

check_weighted_operations(data, weights, dim="a", skipna=None)

q = 0.5
result = data.weighted(weights).quantile(q, dim="a")
# Expected value computed using code from 
https://aakinshin.net/posts/weighted-quantiles/ with values at a=1,2,3
expected = DataArray([0.9308707], coords={"quantile": 
[q]}).squeeze()

>   assert_allclose(result, expected)
E   AssertionError: Left and right DataArray objects are not close
E
E   Differing values:
E   L
E   array(0.058928)
E   R
E   array(0.930871)

Paul

[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/24586369/log.gz


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1013939 closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#1013939: fixed in python-xarray 2022.06.0-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1013939 {Done: Alastair McKinstry } 
[src:python-xarray] python-xarray: autopkgtest regression: Left and right 
DataArray objects are not close
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-xarray/2022.06.0-2.

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

Bug#1016937: atop: autopkgtest regression on arm64 and armhf and times out on s390x

[Paul Gevers]

Hi Marc,

On 10-08-2022 12:03, Marc Haber wrote:

Unfortunately, this bug report suffers from multiple cut&paste or
template error. The ci link points to the mercurial page for amd64, the
text alternates between s390s, armhf, arm64 and amd64.


There was only one that I'm aware of, the link to mercurial. But I 
understand it if the text was a bit confusing.



I tried the (dead simple) autopkgtest on the s390s and arm64 porterboxes
and it succeeded in a second's time. I have sharpened the expression
that counts the CPUs in lscpu's output and hope this will fix the issue.


ooo, CPU count. Yes, some of those archs run on hosts with lots of 
CPU's. armhf has 160, s390x has 10.



I also fixed a syntax error in the test, but that should cause the test
to error out and not hang.


Wonderful.


Can you find out in which line the autopkgtest stalls?


Unfortunately; you have access to the same log as I have.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: dictd: yields "client_read_status: Connection reset by peer" in the client

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dictd closes the connection immediately, yielding 
> "client_read_status: Connection reset by peer" in the client
Bug #1017030 [dictd] dictd: yields "client_read_status: Connection reset by 
peer" in the client
Changed Bug title to 'dictd closes the connection immediately, yielding 
"client_read_status: Connection reset by peer" in the client' from 'dictd: 
yields "client_read_status: Connection reset by peer" in the client'.

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

Bug#1017030: dictd: yields "client_read_status: Connection reset by peer" in the client

[Vincent Lefevre]

Control: retitle -1 dictd closes the connection immediately, yielding 
"client_read_status: Connection reset by peer" in the client

as shown by telnet.

I do not have any issue if I start a new instance on a different port
(being careful with bug 1017031 when running dict).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Evangelos Ribeiro Tzaras]

Hi Moritz,

On Wed, 2022-08-10 at 22:08 +0200, Moritz Mühlenhoff wrote:
> Source: sofia-sip
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following vulnerabilities were published for sofia-sip.

I will try to apply the patches and prepare a release!

> CVE-2022-31001[0]:
...
> CVE-2022-31002[1]:
...
> CVE-2022-31003[2]:
...
> 

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

ACK.
Is there a specific format needed when referencing the CVE?

> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2022-31001
>     https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31001
> [1] https://security-tracker.debian.org/tracker/CVE-2022-31002
>     https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31002
> [2] https://security-tracker.debian.org/tracker/CVE-2022-31003
>     https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31003


> Please adjust the affected versions in the BTS as needed.

Will do once I've checked in some detail.

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


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

Bug#1017032: awesome: flaky autopkgtest: sometimes reports on stderr: Could not resolve keysym XF86EmojiPicker

[Paul Gevers]

Source: awesome
Version: 4.3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc [0]. It seems that it 
regularly fails on all architectures due to *warnings* printed on 
stderr. autopkgtest by default fails on output to stderr, which can be 
changed by adding a "allow-stderr" restriction to the test. Obviously 
it's better to prevent the output.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] 
https://ci.debian.net/data/autopkgtest/testing/ppc64el/a/awesome/24520223/log.gz


autopkgtest [23:18:38]: test integration.sh:  - - - - - - - - - - 
results - - - - - - - - - -
integration.sh   FAIL stderr: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
autopkgtest [23:18:38]: test integration.sh:  - - - - - - - - - - stderr 
- - - - - - - - - -

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:  Could not resolve keysym XF86EmojiPicker
Errors from xkbcomp are not fatal to the X server


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017033: scotch: autopkgtest regression on armel, armhf and ppc64el with glibc 2.34: output on stderr

[Paul Gevers]

Source: scotch
Version: 7.0.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc [0] on armel, armhf 
and ppc64el. It seems that it fails due to *warnings* printed on stderr. 
autopkgtest by default fails on output to stderr, which can be changed 
by adding a "allow-stderr" restriction to the test. Obviously it's 
better to prevent the output. Ubuntu already added the restriction 
because they were seeing this before Debian.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] 
https://ci.debian.net/data/autopkgtest/testing/armel/s/scotch/24593514/log.gz


autopkgtest [17:58:43]: test test-scotch:  - - - - - - - - - - stderr - 
- - - - - - - - -

test_scotch_graph_induce.c: In function ‘main’:
test_scotch_graph_induce.c:134:3: warning: ‘memset’ specified size 
between 2147483649 and 4294967295 exceeds maximum object size 2147483647 
[-Wstringop-overflow=]

  134 |   memset (orgparttab, 0, orgvertnbr * sizeof (SCOTCH_GraphPart2));
  |   ^~~


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1016821: libspf2: FTBFS with glibc 2.34

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #1016821 [src:libspf2] libspf2: FTBFS with glibc 2.34
Added tag(s) pending.

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

Bug#1016821: libspf2: FTBFS with glibc 2.34

[Aurelien Jarno]

control: tag -1 + pending

On 2022-08-09 15:12, Aurelien Jarno wrote:
> control: tag -1 + patch
> 
> Hi,
> 
> On 2022-08-08 01:34, Sebastian Ramacher wrote:
> > Source: libspf2
> > Version: 1.2.10-7.1
> > Severity: serious
> > Tags: ftbfs sid bookworm
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > X-Debbugs-Cc: sramac...@debian.org
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=libspf2&arch=arm64&ver=1.2.10-7.1%2Bb2&stamp=1659915050&raw=0
> > 
> > /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wall  -Wl,-z,relro 
> > -Wl,--version-script=/<>/debian/libspf2.ver -o spfquery 
> > spfquery.o ../../src/libspf2/libspf2.la -lpthread -lnsl -lresolv 
> > libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
> > -Wl,relro -Wl,--version-script=/<>/debian/libspf2.ver -o 
> > .libs/spfquery spfquery.o  ../../src/libspf2/.libs/libspf2.so -lpthread 
> > -lnsl -lresolv
> > /usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
> > `__dn_expand'
> > /usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
> > `__dn_skipname'
> 
> It appears that these two symbols have been renamed in glibc 2.34 when
> moved from libresolv to libc. Quoting the glibc NEWS file:
> 
> | * Various symbols previously defined in libresolv have been moved to libc
> |   in order to prepare for libresolv moving entirely into libc (see earlier
> |   entry for merging libraries into libc).  The symbols __dn_comp,
> |   __dn_expand, __dn_skipname, __res_dnok, __res_hnok, __res_mailok,
> |   __res_mkquery, __res_nmkquery, __res_nquery, __res_nquerydomain,
> |   __res_nsearch, __res_nsend, __res_ownok, __res_query, __res_querydomain,
> |   __res_search, __res_send formerly in libresolv have been renamed and no
> |   longer have a __ prefix.  They are now available in libc.
> 
> libspf2 is using libreplace internally to provide "replacements in case
> the OS does not have native libraries that contain (working) copies.".
> In that case it takes care to rename dn_expand into __dn_expand and
> dn_skipname into __dn_skipname. It appears that with the changes done in
> glibc 2.34, libspf2 does not need to use libreplace anymore. Therefore
> the following patch from Ubuntu fixes the issue:
> 
> https://patches.ubuntu.com/libs/libspf2/libspf2_1.2.10-7.1ubuntu1.patch

I have uploaded a NMU fixing this issue to DELAYED/2. Please find the
corresponding debdiff attached. Also please feel free to ask me to delay
or cancel this NMU.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru libspf2-1.2.10/debian/changelog libspf2-1.2.10/debian/changelog
--- libspf2-1.2.10/debian/changelog 2021-08-08 13:46:49.0 +0200
+++ libspf2-1.2.10/debian/changelog 2022-08-11 23:05:37.0 +0200
@@ -1,3 +1,11 @@
+libspf2 (1.2.10-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * no-libreplace.patch: disable libreplace which is not needed anymore and
+causes build failures with glibc 2.34 (Closes: #1016821).
+
+ -- Aurelien Jarno   Thu, 11 Aug 2022 23:05:37 +0200
+
 libspf2 (1.2.10-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libspf2-1.2.10/debian/patches/no-libreplace.patch 
libspf2-1.2.10/debian/patches/no-libreplace.patch
--- libspf2-1.2.10/debian/patches/no-libreplace.patch   1970-01-01 
01:00:00.0 +0100
+++ libspf2-1.2.10/debian/patches/no-libreplace.patch   2022-08-11 
23:05:37.0 +0200
@@ -0,0 +1,19 @@
+Description: Don't use unnecessary libreplace
+ libreplace isn't providing anything of utility here, it's unconditional and
+ causing build failures on some architectures.
+Author: Steve Langasek 
+Last-Updated: 2022-02-24
+Forwarded: no
+
+Index: libspf2-1.2.10/src/libspf2/Makefile.am
+===
+--- libspf2-1.2.10.orig/src/libspf2/Makefile.am
 libspf2-1.2.10/src/libspf2/Makefile.am
+@@ -34,7 +34,6 @@
+   spf_utils.c \
+   spf_win32.c
+ 
+-libspf2_la_LIBADD = $(top_builddir)/src/libreplace/libreplace.la
+ 
+ 
+ 
diff -Nru libspf2-1.2.10/debian/patches/series 
libspf2-1.2.10/debian/patches/series
--- libspf2-1.2.10/debian/patches/series2021-08-08 13:46:49.0 
+0200
+++ libspf2-1.2.10/debian/patches/series2022-08-11 23:05:37.0 
+0200
@@ -5,3 +5,4 @@
 spf_compile.c-Correct-size-of-ds_avail.patch
 Sanity-check-for-sprintf.patch
 Fixed-reverse-macro-modifier.patch
+no-libreplace.patch


signature.asc
Description: PGP signature

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Moritz Muehlenhoff]

On Thu, Aug 11, 2022 at 11:08:49PM +0200, Evangelos Ribeiro Tzaras wrote:
> Hi Moritz,
> 
> On Wed, 2022-08-10 at 22:08 +0200, Moritz Mühlenhoff wrote:
> > Source: sofia-sip
> > X-Debbugs-CC: t...@security.debian.org
> > Severity: grave
> > Tags: security
> > 
> > Hi,
> > 
> > The following vulnerabilities were published for sofia-sip.
> 
> I will try to apply the patches and prepare a release!
> 
> > CVE-2022-31001[0]:
> ...
> > CVE-2022-31002[1]:
> ...
> > CVE-2022-31003[2]:
> ...
> > 
> 
> > If you fix the vulnerabilities please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
> 
> ACK.
> Is there a specific format needed when referencing the CVE?

Not really, just mention them in debian/changelog :-)

In addition we'll keep security-tracker.debian.org updated when the upload 
reaches unstable.

Once the fix is in unstable (and if there are issues reported after a few
days) we can sort out an update for bullseye-security.

Cheers,
Moritz

Bug#1012898: marked as done (assimp: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 22:49:06 +
with message-id 
and subject line Bug#1012898: fixed in assimp 5.2.4~ds0-3
has caused the Debian Bug report #1012898,
regarding assimp: ftbfs with GCC-12
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.)


-- 
1012898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:assimp
Version: 5.2.4~ds0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/assimp_5.2.4~ds0-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
cd "/<>/obj-x86_64-linux-gnu/code" && /usr/bin/c++ 
-DASSIMP_BUILD_DLL_EXPORT -DASSIMP_BUILD_NO_C4D_IMPORTER 
-DASSIMP_BUILD_NO_M3D_EXPORTER -DASSIMP_BUILD_NO_M3D_IMPORTER 
-DASSIMP_BUILD_NO_OWN_ZLIB -DASSIMP_IMPORTER_GLTF_USE_OPEN3DGC=1 
-DMINIZ_USE_UNALIGNED_LOADS_AND_STORES=0 -DOPENDDLPARSER_BUILD 
-DRAPIDJSON_HAS_STDSTRING=1 -DRAPIDJSON_NOMEMBERITERATORCLASS -Dassimp_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/include" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/include" 
-I"/<>/code" -I"/<>/." 
-I"/<>/code/../contrib/pugixml/src" 
-I"/<>/code/../contrib/rapidjson/include" 
-I"/<>/code/../contrib" 
-I"/<>/code/../contrib/openddlparser/include" 
-I"/<>/code/../include" 
-I"/<>/obj-x86_64-linux-gnu/code/../include" 
-I/usr/include/minizip -fvisibility=hidden -fno-strict-aliasing -Wall -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wfo
 rmat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DASSIMP_ENABLE_DRACO=1 -fPIC   -D'ASSIMP_BUILD_ARCHITECTURE="amd64"' -Wall 
-Werror -std=gnu++11 -MD -MT 
code/CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o -MF 
CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o.d -o 
CMakeFiles/assimp.dir/AssetLib/SIB/SIBImporter.cpp.o -c 
"/<>/code/AssetLib/SIB/SIBImporter.cpp"
[ 68%] Building CXX object 
code/CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o
cd "/<>/obj-x86_64-linux-gnu/code" && /usr/bin/c++ 
-DASSIMP_BUILD_DLL_EXPORT -DASSIMP_BUILD_NO_C4D_IMPORTER 
-DASSIMP_BUILD_NO_M3D_EXPORTER -DASSIMP_BUILD_NO_M3D_IMPORTER 
-DASSIMP_BUILD_NO_OWN_ZLIB -DASSIMP_IMPORTER_GLTF_USE_OPEN3DGC=1 
-DMINIZ_USE_UNALIGNED_LOADS_AND_STORES=0 -DOPENDDLPARSER_BUILD 
-DRAPIDJSON_HAS_STDSTRING=1 -DRAPIDJSON_NOMEMBERITERATORCLASS -Dassimp_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/include" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/include" 
-I"/<>/code" -I"/<>/." 
-I"/<>/code/../contrib/pugixml/src" 
-I"/<>/code/../contrib/rapidjson/include" 
-I"/<>/code/../contrib" 
-I"/<>/code/../contrib/openddlparser/include" 
-I"/<>/code/../include" 
-I"/<>/obj-x86_64-linux-gnu/code/../include" 
-I/usr/include/minizip -fvisibility=hidden -fno-strict-aliasing -Wall -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wfo
 rmat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DASSIMP_ENABLE_DRACO=1 -fPIC   -D'ASSIMP_BUILD_ARCHITECTURE="amd64"' -Wall 
-Werror -std=gnu++11 -MD -MT 
code/CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o -MF 
CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o.d -o 
CMakeFiles/assimp.dir/AssetLib/SMD/SMDLoader.cpp.o -c 
"/<>/code/AssetLib/SMD/SMDLoader.cpp"
[ 69%] Building CXX object 
code/CMakeFiles/assimp.dir/AssetLib/STL/STLLoader.cpp.o
cd "/<>/obj-x86_64-linux-gnu/cod

Bug#1016996: libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base

[Cyril Brulebois]

Hi Matthieu,

Matthieu Baerts  (2022-08-11):
> Thank you for having CCed me, provided a fix so quickly and for the
> detailed explanations! Sorry, I didn't notice the regression when
> testing on my side.

Absolutely no problems; it's easy to spot things when some daily build
breaks, much easier than spotting all the changes in a set of 18 binary
packages which tend to hardcode a strict dependency toward sibling
packages…

> Do we need to revert your workaround when #1015263 will be fixed? If
> yes, are you tracking this issue and planning to do the revert or do
> you prefer if someone else looks at that?

At the moment, I didn't think that far ahead… First things first: I hope
this issue doesn't become more widespread, so I'm hoping debhelper gets
a fix sooner than later. If more hotfixes like this are needed, I'll
probably plan on tracking individual changes to coordinate reverts. In
the meanwhile, if you could take care of cancelling that change in that
particular package when the time comes, that'd be awesome! Otherwise, I
do have sticky notes and a large desk, I can deal with it. :)


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


signature.asc
Description: PGP signature

Bug#1016996: libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base

[Cyril Brulebois]

Adam Borowski  (2022-08-11):
> Yeah but I shouldn't have let the bad dependency through.
> 
> My sponsoring workflow automates this kind of checks for regular packages
> but fails to check udebs, and I thus don't have in mind to look by hand.
> Apologies.

Really, don't worry, that's fine.

> But then, we do have _someone_ to spot and fix such problems :þ

It's been a while since the last one, but when we eventually get back to
producing d-i releases: I'll freeze udeb-producing packages for a few
hours or a few days, so that such regressions can't sneak into testing
behind my back, and in the general case, such problems will be spotted
(as you mentioned), and they shouldn't be time-critical anyway.


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


signature.asc
Description: PGP signature

Bug#1017038: icinga2-bin: Uninstallable, missing denepdency package libboost-iostreams1.67.0

[Takatsugu Nokubi]

Package: icinga2-bin
Version: 2.31-13+deb11u3
Severity: grave

Depends: icinga2-common (= 2.13.5-1.buster), libboost-atomic1.67.0,
libboost-chrono1.67.0, libboost-context1.67.0, libboost-coroutine1.67.0,
libboost-date-time1.67.0, libboost-filesystem1.67.0,
libboost-iostreams1.67.0, libboost-program-options1.67.0,
libboost-regex1.67.0 (>= 1.67.0-10), libboost-system1.67.0,
libboost-thread1.67.0, libc6 (>= 2.27), libedit2 (>= 2.11-20080614-0),
libgcc1 (>= 1:3.3.1), libssl1.1 (>= 1.1.0), libstdc++6 (>= 7), libsystemd0,
libtinfo6 (>= 6)

I can't install icinga2-bin because libboost-iostreams1.67.0 is not exist
in bullseye.
Workaround is using oldstable backports deb:
https://packages.debian.org/buster/libboost-iostreams1.67.0

Bug#1017038: marked as done (icinga2-bin: Uninstallable, missing denepdency package libboost-iostreams1.67.0)

[Debian Bug Tracking System]

Your message dated Fri, 12 Aug 2022 06:25:08 +0200
with message-id <7b36302d-fb97-ae17-5648-931936572...@xs4all.nl>
and subject line Re: [Pkg-nagios-devel] Bug#1017038: icinga2-bin: 
Uninstallable, missing denepdency package libboost-iostreams1.67.0
has caused the Debian Bug report #1017038,
regarding icinga2-bin: Uninstallable, missing denepdency package 
libboost-iostreams1.67.0
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.)


-- 
1017038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icinga2-bin
Version: 2.31-13+deb11u3
Severity: grave

Depends: icinga2-common (= 2.13.5-1.buster), libboost-atomic1.67.0,
libboost-chrono1.67.0, libboost-context1.67.0, libboost-coroutine1.67.0,
libboost-date-time1.67.0, libboost-filesystem1.67.0,
libboost-iostreams1.67.0, libboost-program-options1.67.0,
libboost-regex1.67.0 (>= 1.67.0-10), libboost-system1.67.0,
libboost-thread1.67.0, libc6 (>= 2.27), libedit2 (>= 2.11-20080614-0),
libgcc1 (>= 1:3.3.1), libssl1.1 (>= 1.1.0), libstdc++6 (>= 7), libsystemd0,
libtinfo6 (>= 6)

I can't install icinga2-bin because libboost-iostreams1.67.0 is not exist
in bullseye.
Workaround is using oldstable backports deb:
https://packages.debian.org/buster/libboost-iostreams1.67.0
--- End Message ---
--- Begin Message ---

Control: severity -1 normal

On 8/12/22 03:51, Takatsugu Nokubi wrote:

Package: icinga2-bin
Version: 2.31-13+deb11u3
Severity: grave

Depends: icinga2-common (= 2.13.5-1.buster), libboost-atomic1.67.0,
libboost-chrono1.67.0, libboost-context1.67.0, libboost-coroutine1.67.0,
libboost-date-time1.67.0, libboost-filesystem1.67.0,
libboost-iostreams1.67.0, libboost-program-options1.67.0,
libboost-regex1.67.0 (>= 1.67.0-10), libboost-system1.67.0,
libboost-thread1.67.0, libc6 (>= 2.27), libedit2 (>= 2.11-20080614-0),
libgcc1 (>= 1:3.3.1), libssl1.1 (>= 1.1.0), libstdc++6 (>= 7), libsystemd0,
libtinfo6 (>= 6)

I can't install icinga2-bin because libboost-iostreams1.67.0 is not exist
in bullseye.
Workaround is using oldstable backports deb:
https://packages.debian.org/buster/libboost-iostreams1.67.0


This is the upstream icinga2 package, we don't have that version in Debian.

You should report the issue upstream:

 https://github.com/Icinga/icinga2/issues

Kind Regards,

Bas

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

Processed: severity of 1017038 is normal, tagging 1017038

[Debian Bug Tracking System]

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

> severity 1017038 normal
Bug #1017038 {Done: Sebastiaan Couwenberg } [icinga2-bin] 
icinga2-bin: Uninstallable, missing denepdency package libboost-iostreams1.67.0
Severity set to 'normal' from 'grave'
> tags 1017038 + upstream wontfix
Bug #1017038 {Done: Sebastiaan Couwenberg } [icinga2-bin] 
icinga2-bin: Uninstallable, missing denepdency package libboost-iostreams1.67.0
Added tag(s) wontfix and upstream.
> thanks
Stopping processing here.

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

Bug#1016089: marked as done (mistune: CVE-2022-34749)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 09:28:33 +0200
with message-id <8d2afcbcee65df4f7a51687fbd8b7065c8ad6ab0.ca...@gmail.com>
and subject line Fixed mistune migrated to testing
has caused the Debian Bug report #1016089,
regarding mistune: CVE-2022-34749
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.)


-- 
1016089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mistune
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for mistune.

CVE-2022-34749[0]:
| In mistune through 2.0.2, support of inline markup is implemented by
| using regular expressions that can involve a high amount of
| backtracking on certain edge cases. This behavior is commonly named
| catastrophic backtracking.

https://github.com/lepture/mistune/commit/a6d43215132fe4f3d93f8d7e90ba83b16a0838b2

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-34749
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34749

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Hi,

the fixed package migrated to testing, so this report can be closed.

Cheers,

J.Puydt--- End Message ---

Bug#1011762: marked as done (allure: FTBFS: make: *** No rule to make target 'check-ghc-stamp', needed by 'common-binary-arch'. Stop.)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 07:48:51 +
with message-id 
and subject line Bug#1011762: fixed in allure 0.11.0.0-1
has caused the Debian Bug report #1011762,
regarding allure: FTBFS: make: *** No rule to make target 'check-ghc-stamp', 
needed by 'common-binary-arch'.  Stop.
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/QVyPJOsHCi -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> allure
> Running dh_listpackages
> allure
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/allure-0.9.5.0/ --datasubdir=allure 
> --htmldir=/usr/share/doc/libghc-allure-doc/html/ --enable-tests
> Using Parsec parser
> Configuring Allure-0.9.5.0...
> Flags chosen: supportnodejs=True
> Dependency LambdaHack >=0.9.5.0 && <0.9.6.0: using LambdaHack-0.9.5.0
> Dependency async -any: using async-2.2.2
> Dependency base >=4.10 && <99: using base-4.13.0.0
> Dependency enummapset -any: using enummapset-0.6.0.3
> Dependency filepath -any: using filepath-1.4.2.1
> Dependency ghc-compact -any: using ghc-compact-0.1.0.0
> Dependency optparse-applicative -any: using optparse-applicative-0.15.1.0
> Dependency primitive -any: using primitive-0.7.0.1
> Dependency random -any: using random-1.1
> Dependency template-haskell >=2.6: using template-haskell-2.15.0.0
> Dependency text -any: using text-1.2.4.0
> Dependency transformers -any: using transformers-0.5.6.2
> Dependency Allure -any: using Allure-0.9.5.0
> Dependency LambdaHack -any: using LambdaHack-0.9.5.0
> Dependency async -any: using async-2.2.2
> Dependency base -any: using base-4.13.0.0
> Dependency filepath -any: using filepath-1.4.2.1
> Dependency optparse-applicative -any: using optparse-applicative-0.15.1.0
> Dependency Allure -any: using Allure-0.9.5.0
> Dependency LambdaHack -any: using LambdaHack-0.9.5.0
> Dependency async -any: using async-2.2.2
> Dependency base -any: using base-4.13.0.0
> Dependency filepath -any: using filepath-1.4.2.1
> Dependency optparse-applicative -any: using optparse-applicative-0.15.1.0
> Source component graph:
> component lib
> component exe:Allure dependency lib
> component test:test dependency lib
> Configured component graph:
> component Allure-0.9.5.0-8XPSLIgOGqUJbvZ8by11yB
> include LambdaHack-0.9.5.0-F8tMx5oJu4gJDAqurnBqB7
> include async-2.2.2-1jIe70QEPH1GVJJWPbuUZ4
> include base-4.13.0.0
> include enummapset-0.6.0.3-8Mv1eW4ryALYpWG34NeVt
> include filepath-1.4.2.1
> include ghc-compact-0.1.0.0
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> include primitive-0.7.0.1-CN4ea3Jrhra6yENuqrDg51
> include random-1.1-CUqV1zxrwrE4K5XCdTZSYy
> include template-haskell-2.15.0.0
> include text-1.2.4.0
> include transformers-0.5.6.2
> component Allure-0.9.5.0-BAWm3kR2P8dFSJD3DkCkns-Allure
> include Allure-0.9.5.0-8XPSLIgOGqUJbvZ8by11yB
> include LambdaHack-0.9.5.0-F8tMx5oJu4gJDAqurnBqB7
> include async-2.2.2-1jIe70QEPH1GVJJWPbuUZ4
> include base-4.13.0.0
> include filepath-1.4.2.1
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> component Allure-0.9.5.0-FoF6Mc959ATBN5ETgTX9Mp-test
> in

Bug#1017007: manpages-de: trying to overwrite .../ethers.5.gz, which is also in package net-tools

[Ingo Saitz]

Package: manpages-de
Version: 4.14.0-4
Severity: serious
Tags: l10n
Justification: Policy 7.6.1

Unpacking manpages-de (4.15.0-3) over (4.14.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/manpages-de_4.15.0-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/de/man5/ethers.5.gz', which is also in 
package net-tools 1.60+git20181103.0eebece-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/manpages-de_4.15.0-3_all.deb


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

Kernel: Linux 5.19.0-pinguin20220731 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

manpages-de depends on no packages.

manpages-de recommends no packages.

Versions of packages manpages-de suggests:
it  man-db [man-browser]  2.10.2-1
ii  manpages  5.13-1

-- no debconf information

Bug#1015789: marked as done (mysql-8.0: CVE-2022-21569 CVE-2022-21556 CVE-2022-21553 CVE-2022-21550 CVE-2022-21547 CVE-2022-21539 CVE-2022-21538 CVE-2022-21537 CVE-2022-21535 CVE-2022-21534 CVE-2022-2

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 09:09:13 +
with message-id 
and subject line Bug#1015789: fixed in mysql-8.0 8.0.30-1
has caused the Debian Bug report #1015789,
regarding mysql-8.0: CVE-2022-21569 CVE-2022-21556 CVE-2022-21553 
CVE-2022-21550 CVE-2022-21547 CVE-2022-21539 CVE-2022-21538 CVE-2022-21537 
CVE-2022-21535 CVE-2022-21534 CVE-2022-21531 CVE-2022-21530 CVE-2022-21529 
CVE-2022-21528 CVE-2022-21527 CVE-2022-21526 CVE-2022-21525 CVE-2022-21522 
CVE-2022-21519 CVE-2022-21517 CVE-2022-21515 CVE-2022-21509 CVE-2022-21455
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.)


-- 
1015789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-8.0
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for mysql-8.0.

All fixed in latest CPU:

CVE-2022-21569[0]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.29
| and prior. Easily exploitable vulnerability allows low privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

CVE-2022-21556[1]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.28
| and prior. Easily exploitable vulnerability allows high privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized creation, deletion or modification access to critical
| data or all MySQL Server accessible data and unauthorized ability to
| cause a hang or frequently repeatable crash (complete DOS) of MySQL
| Server. CVSS 3.1 Base Score 6.5 (Integrity and Availability impacts).
| CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H).

CVE-2022-21553[2]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.29
| and prior. Easily exploitable vulnerability allows high privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

CVE-2022-21550[3]:
| Vulnerability in the MySQL Cluster product of Oracle MySQL (component:
| Cluster: General). Supported versions that are affected are 7.4.36 and
| prior, 7.5.26 and prior, 7.6.22 and prior and and 8.0.29 and prior.
| Difficult to exploit vulnerability allows high privileged attacker
| with access to the physical communication segment attached to the
| hardware where the MySQL Cluster executes to compromise MySQL Cluster.
| Successful attacks require human interaction from a person other than
| the attacker. Successful attacks of this vulnerability can result in
| takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality,
| Integrity and Availability impacts). CVSS Vector:
| (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

CVE-2022-21547[4]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Federated). Supported versions that are affected are 8.0.29
| and prior. Easily exploitable vulnerability allows high privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

CVE-2022-21539[5]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| InnoDB). Supported versions that are affected are 8.0.29 and prior.
| Difficult to exploit vulnerability allows low privileged attacker with
| network access via multiple protocols to compromise MySQL Server.
| Successful attacks of this vulnerability can result in unauthorized
| update, insert or delete access to some of MySQL Server accessible
| data as well 

Bug#1016996: libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base

[Matthieu Baerts]

Hi Cyril,

On 11/08/2022 02:00, Cyril Brulebois wrote:
> Package: libnl-3-200-udeb
> Version: 3.7.0-0.1
> Severity: grave
> Tags: d-i patch
> Justification: renders package unusable
> X-Debbugs-Cc: Matthieu Baerts , Adam Borowski 
> , debian-b...@lists.debian.org
> 
> Hi Matthieu, hi Adam,
> 
> The set of packages you uploaded contains uninstallable udebs, as they
> depend on sgml-base, which doesn't exist in the installer context
> (there's no udeb for it. Current dependencies are as follows:
> 
> $ dpkg --info libnl-3-200-udeb_3.7.0-0.1_amd64.udeb|grep Depends
>  Depends: sgml-base (>= 1.28), libc6-udeb (>= 2.34)
> 
> $ dpkg --info libnl-genl-3-200-udeb_3.4.0-1+b1_amd64.udeb|grep Depends
>  Depends: libnl-3-200-udeb (= 3.4.0-1+b1), libc6-udeb (>= 2.28)
> 
> This leads to the following build failure for the daily builds of the
> installer:
> 
> The following packages have unmet dependencies:
>  libnl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not installable
>  libnl-genl-3-200-udeb : Depends: sgml-base (>= 1.28) but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> 
> (Note that I'm filing this bug report against only one of those udebs.)
> 
> This is not your fault, that's debhelper's #1015263:
>   https://bugs.debian.org/1015263
> 
> but I thought I'd loop you in so that you know about this issue, and
> about my current plan: the installer team (X-D-Cc'd) doesn't require an
> immediate fix, but since I'm not sure when the debhelper bug is getting
> fixed (and packages binNMU'd), I thought I'd prepare a workaround to
> make sure this source package isn't a blocker when we plan for a Debian
> Installer release.

Thank you for having CCed me, provided a fix so quickly and for the
detailed explanations! Sorry, I didn't notice the regression when
testing on my side.

Do we need to revert your workaround when #1015263 will be fixed? If
yes, are you tracking this issue and planning to do the revert or do you
prefer if someone else looks at that?

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

Processed: flint's FTBFS forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 1016296 https://github.com/wbhart/flint2/issues/1175
Bug #1016296 [src:flint] flint: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 AT= QUIET_CXX= QUIET_CC= QUIET_AR= 
"INCS=-I/<> -I/<>/build" "ABI_FLAG=-Wl,-z,relro 
-Wl,-z,now" returned exit code 2
Set Bug forwarded-to-address to 'https://github.com/wbhart/flint2/issues/1175'.
> thanks
Stopping processing here.

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

Bug#1016996: libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base

[Adam Borowski]

On Thu, Aug 11, 2022 at 02:00:59AM +0200, Cyril Brulebois wrote:
> The set of packages you uploaded contains uninstallable udebs, as they
> depend on sgml-base, which doesn't exist in the installer context
> (there's no udeb for it.

> This is not your fault, that's debhelper's #1015263:

Yeah but I shouldn't have let the bad dependency through.

My sponsoring workflow automates this kind of checks for regular packages
but fails to check udebs, and I thus don't have in mind to look by hand.
Apologies.

But then, we do have _someone_ to spot and fix such problems :þ

> +libnl3 (3.7.0-0.2) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Dodge debhelper's #1015263 by resetting misc:Depends via
> +DEB_DH_GENCONTROL_ARGS_libnl{,-genl}-3-200-udeb to avoid pulling
> +sgml-base.
> +
> + -- Cyril Brulebois   Wed, 10 Aug 2022 23:43:51 +

> +# Dodge debhelper's #1015263, pulling sgml-base for udebs:
> +DEB_DH_GENCONTROL_ARGS_$(udeb_libnl) = -- -Vmisc:Depends=
> +DEB_DH_GENCONTROL_ARGS_$(udeb_libnl_genl) = -- -Vmisc:Depends=

Thanks!


Meow.
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ What kind of a drug are "base" and "red pill"?  I think acid is
⢿⡄⠘⠷⠚⠋⠀ LSD, which would make base... ?  Judging from the behaviour of
⠈⠳⣄ those "based and redpilled", something nasty.

Bug#1016249: marked as done (osk-sdl: FTBFS: ../src/config.cpp:163:17: error: ‘transform’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2022 09:54:14 +
with message-id 
and subject line Bug#1016249: fixed in osk-sdl 0.67-2
has caused the Debian Bug report #1016249,
regarding osk-sdl: FTBFS: ../src/config.cpp:163:17: error: ‘transform’ was not 
declared in this scope
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.)


-- 
1016249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osk-sdl
Version: 0.67-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> c++ -Iosk-sdl.p -I. -I.. -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra 
> -Wpedantic -std=c++2a -O0 '-DVERSION="0.67"' -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ 
> osk-sdl.p/src_config.cpp.o -MF osk-sdl.p/src_config.cpp.o.d -o 
> osk-sdl.p/src_config.cpp.o -c ../src/config.cpp
> ../src/config.cpp: In member function ‘bool Config::Read(const std::string&)’:
> ../src/config.cpp:163:17: error: ‘transform’ was not declared in this scope
>   163 | transform(val.begin(), val.end(), val.begin(), 
> ::tolower);
>   | ^
> [7/11] c++ -Iosk-sdl.p -I. -I.. -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra 
> -Wpedantic -std=c++2a -O0 '-DVERSION="0.67"' -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ 
> osk-sdl.p/src_toggle.cpp.o -MF osk-sdl.p/src_toggle.cpp.o.d -o 
> osk-sdl.p/src_toggle.cpp.o -c ../src/toggle.cpp
> [8/11] c++ -Iosk-sdl.p -I. -I.. -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra 
> -Wpedantic -std=c++2a -O0 '-DVERSION="0.67"' -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ 
> osk-sdl.p/src_main.cpp.o -MF osk-sdl.p/src_main.cpp.o.d -o 
> osk-sdl.p/src_main.cpp.o -c ../src/main.cpp
> [9/11] c++ -Iosk-sdl.p -I. -I.. -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra 
> -Wpedantic -std=c++2a -O0 '-DVERSION="0.67"' -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ 
> osk-sdl.p/src_util.cpp.o -MF osk-sdl.p/src_util.cpp.o.d -o 
> osk-sdl.p/src_util.cpp.o -c ../src/util.cpp
> [10/11] c++ -Iosk-sdl.p -I. -I.. -I/usr/include/SDL2 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra 
> -Wpedantic -std=c++2a -O0 '-DVERSION="0.67"' -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ 
> osk-sdl.p/src_keyboard.cpp.o -MF osk-sdl.p/src_keyboard.cpp.o.d -o 
> osk-sdl.p/src_keyboard.cpp.o -c ../src/keyboard.cpp
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v 
> returned exit code 1
> make: *** [debian/rules:13: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/osk-sdl_0.67-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodv