Bug#1023248: systemd fails to install: Failed to resolve group 'systemd-journal'.

[Jochen Sprickerhof]

Hi Helmut,

* Helmut Grohne  [2022-11-01 06:08]:

Package: systemd
Version: 252-1
Severity: serious

systemd fails to install in unstable:

mmdebstrap --verbose --variant apt --include systemd unstable /dev/null

| Setting up systemd (252-1) ...
| Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → 
/lib/systemd/system/getty@.service.
| Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target 
→ /lib/systemd/system/remote-fs.target.
| Created symlink 
/etc/systemd/system/sysinit.target.wants/systemd-pstore.service → 
/lib/systemd/system/systemd-pstore.service.
| Initializing machine ID from random generator.
| /usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:29: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:30: Failed to resolve group 
'systemd-journal'.
| dpkg: error processing package systemd (--configure):
|  installed systemd package post-installation script subprocess returned error 
exit status 65
| Processing triggers for libc-bin (2.35-4) ...
| Errors were encountered while processing:
|  systemd
| E: Sub-process env returned an error code (1)

Hope you can figure this out quickly. It happens to break rebootstrap
CI. If you happen to know a workaround that'd be appreciated as well.


I've opened a MR to fix this:

https://salsa.debian.org/systemd-team/systemd/-/merge_requests/182

Cheers Jochen


signature.asc
Description: PGP signature

Processed: bug 1022806 is forwarded to https://gitlab.freedesktop.org/drm/amd/-/issues/2237, tagging 1022806

[Debian Bug Tracking System]

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

> forwarded 1022806 https://gitlab.freedesktop.org/drm/amd/-/issues/2237
Bug #1022806 [src:linux] linux-image-5.10.0-19-amd64: amggpu unbootable problem 
persists
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/amd/-/issues/2237'.
> tags 1022806 + upstream
Bug #1022806 [src:linux] linux-image-5.10.0-19-amd64: amggpu unbootable problem 
persists
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1023248: systemd fails to install: Failed to resolve group 'systemd-journal'.

[Helmut Grohne]

Package: systemd
Version: 252-1
Severity: serious

systemd fails to install in unstable:

mmdebstrap --verbose --variant apt --include systemd unstable /dev/null

| Setting up systemd (252-1) ...
| Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → 
/lib/systemd/system/getty@.service.
| Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target 
→ /lib/systemd/system/remote-fs.target.
| Created symlink 
/etc/systemd/system/sysinit.target.wants/systemd-pstore.service → 
/lib/systemd/system/systemd-pstore.service.
| Initializing machine ID from random generator.
| /usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:29: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:30: Failed to resolve group 
'systemd-journal'.
| dpkg: error processing package systemd (--configure):
|  installed systemd package post-installation script subprocess returned error 
exit status 65
| Processing triggers for libc-bin (2.35-4) ...
| Errors were encountered while processing:
|  systemd
| E: Sub-process env returned an error code (1)

Hope you can figure this out quickly. It happens to break rebootstrap
CI. If you happen to know a workaround that'd be appreciated as well.

Helmut

Processed: Re: Bug#1023230: [Debian-med-packaging] Bug#1023230: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 t-coffee 13.45.0.4846264+dfsg-1
Bug #1023230 [src:t-coffee, src:libbio-tools-run-alignment-tcoffee-perl] 
t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times 
out after 2:47 hours
Bug reassigned from package 'src:t-coffee, 
src:libbio-tools-run-alignment-tcoffee-perl' to 't-coffee'.
No longer marked as found in versions 
libbio-tools-run-alignment-tcoffee-perl/1.7.4-3 and 
t-coffee/13.45.0.4846264+dfsg-1.
Ignoring request to alter fixed versions of bug #1023230 to the same values 
previously set
Bug #1023230 [t-coffee] t-coffee breaks libbio-tools-run-alignment-tcoffee-perl 
autopkgtest: test times out after 2:47 hours
Marked as found in versions t-coffee/13.45.0.4846264+dfsg-1.

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

Bug#1023230: [Debian-med-packaging] Bug#1023230: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

[gregor herrmann]

Control: reassign -1 t-coffee 13.45.0.4846264+dfsg-1

On Tue, 01 Nov 2022 09:12:43 +0900, Charles Plessy wrote:

> Le Mon, Oct 31, 2022 at 09:27:47PM +0100, Paul Gevers a écrit :
> > 
> > https://ci.debian.net/data/autopkgtest/testing/arm64/libb/libbio-tools-run-alignment-tcoffee-perl/27686780/log.gz
> > 
> > autopkgtest [11:59:24]: ERROR: timed out on command "su -s /bin/bash debci
> 
> I think that t-coffee never worked on ARM.  It built, but never worked.
> The simplest would be to distribute it only on amd64.
> See https://bugs.debian.org/631249

Also https://bugs.debian.org/1022570 might be relevant.

Reassigning to (only) t-coffee.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1022046: marked as done (git: CVE-2022-39253 CVE-2022-39260)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 02:34:48 +
with message-id 
and subject line Bug#1022046: fixed in git 1:2.38.1-1
has caused the Debian Bug report #1022046,
regarding git: CVE-2022-39253 CVE-2022-39260
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.)


-- 
1022046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.30.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:2.37.2-1

Hi,

The following vulnerabilities were published for git.

CVE-2022-39253[0] and CVE-2022-39260[1].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-39253
https://www.cve.org/CVERecord?id=CVE-2022-39253
[1] https://security-tracker.debian.org/tracker/CVE-2022-39260
https://www.cve.org/CVERecord?id=CVE-2022-39260
[2] https://www.openwall.com/lists/oss-security/2022/10/18/5

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.38.1-1
Done: Jonathan Nieder 

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated git 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: Mon, 31 Oct 2022 18:32:00 -0700
Source: git
Architecture: source
Version: 1:2.38.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Closes: 1022046
Changes:
 git (1:2.38.1-1) unstable; urgency=medium
 .
   * new upstream release (closes: #1022046; see RelNotes/2.38.0.txt,
 RelNotes/2.38.1.txt).
 * Addresses the security issue CVE-2022-39253: cloning an
   attacker-controlled local repository could store arbitrary files
   in the ".git" directory of the destination repository.
 .
   Thanks to Cory Snider of Mirantis for reporting this
   vulnerability and Taylor Blau for the mitigation.
 .
 * Addresses CVE-2022-39260: a long command string passed to a `git
   shell` configured to support custom commands could overflow and
   run arbitrary code.
 .
   Thanks to Kevin Backhouse of GitHub for reporting this
   vulnerability and Kevin Backhouse, Jeff King, and Taylor Blau
   for mitigating it.
Checksums-Sha1:
 449c41de458306bfdb5c3799304325abedf3c1b4 2825 git_2.38.1-1.dsc
 a1886780a89423ddb600e141d44751480eb1413f 7088208 git_2.38.1.orig.tar.xz
 488bf4953a4480e6bcbc0f751caede0e2b938cd0 733140 git_2.38.1-1.debian.tar.xz
 4ff32dc38d82a5ee5c99a9c3e98de859830a1e00 12288 git_2.38.1-1_amd64.buildinfo
Checksums-Sha256:
 500be7ab00360288196aaf434efcc15e733e90dfb02157483e48196a8d56fe89 2825 
git_2.38.1-1.dsc
 97ddf8ea58a2b9e0fbc2508e245028ca75911bd38d1551616b148c1aa5740ad9 7088208 
git_2.38.1.orig.tar.xz
 b2aec5827639f2f939774f457414a6b46f1fce1f014f76a1a48f12a980c3baca 733140 
git_2.38.1-1.debian.tar.xz
 07d50f78c51a4b7ab5aeb01f35a509a0b612f926c2ec73de495a05f8af80137c 12288 
git_2.38.1-1_amd64.buildinfo
Files:
 af8a914ca17fccdf2bb81a9ccd0f0e52 2825 vcs optional git_2.38.1-1.dsc
 abdafbfb85d205421903a2100c734b17 7088208 vcs optional git_2.38.1.orig.tar.xz
 0f6b1dbbd7cf870b4433769c3d72e6a0 733140 vcs optional git_2.38.1-1.debian.tar.xz
 ccb61ddd515c72e896217e91166c5652 12288 vcs optional 
git_2.38.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEUh5Y8X6W1xKqD/EC38Zx7rMz+iUFAmNge4MTHGpybmllZGVy
QGdtYWlsLmNvbQAKCRDfxnHuszP6JZmhEACXloP5VyGShmkzXieZfdL+SE+8eURk
JQ3Xuh6/Nzm0sdpHBcO1AQqlLoOJ9X/vx1BPZAW+B8j2SGYv96LmshkZebCb/j81
/8jhG+9y6Aip8zFCvHQ+wYqkgg3JTkeDEjNjvNx5tkvZpd8+Hf6Ou1J1nBfhnVTH
f7mceBwaJRoXB77fFDH4ypx3KrHkmJRYQh69PmQbOP/PcFEV9x0K7fjnlzTrmTvP
9vMckRQJjBlE8qPge/f5Pcr9l5JzUaOtnh6nz8jqvERb6F27mczjwajHvr+TuUH6
Hx041mhspnmBiDcsYQoqUA6dsoai5fDuTj4NU9ROzz6I/Tze8tuXaCyjnBJzfxyj

Bug#1018225: src:rust-rustls: fails to migrate to testing for too long: blocked by build dependency

[Peter Green]

On 31/10/2022 16:17, Jonas Smedegaard wrote:

Quoting Peter Green (2022-10-31 03:39:28)

src:rust-rustls: fails to migrate to testing for too long: blocked by build 
dependency

Specifically rust-async-std has taken some time to package, because of the 
large number
of dependencies. There has been effort on this front both by the rust team and 
by Jonas
who currently packages rust stuff outside the rust team because he doesn't like 
our
packaging workflow.

Thanks, Peter.  For issues like this one by Release team and explicitly
described in subject as "blocked by build dependency" I believe however
than there is no need for explaining the cause (in _these_ bugreports -
it may make sense and be helpful to elaborate on the cause at a _root_
blocking bugreport).


This bug report is the one that is in testing, and has rc severity and
hence can cause stuff to be removed from testing.

The autoremovals system operates on the basis of when a bug report
was last posted to as an indication of wheter progress is being made
on the bug. Progress is being made on this bug, but the autoremovals
system doesn't know that in case a status update is posted to the
bug, hence why I posted one.

Bug#1023230: [Debian-med-packaging] Bug#1023230: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

[Charles Plessy]

Le Mon, Oct 31, 2022 at 09:27:47PM +0100, Paul Gevers a écrit :
> 
> https://ci.debian.net/data/autopkgtest/testing/arm64/libb/libbio-tools-run-alignment-tcoffee-perl/27686780/log.gz
> 
> autopkgtest [11:59:24]: ERROR: timed out on command "su -s /bin/bash debci

Hi all,

I think that t-coffee never worked on ARM.  It built, but never worked.
The simplest would be to distribute it only on amd64.

See https://bugs.debian.org/631249

Have a nice day,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#1023095: marked as done (dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id 
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.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.)


-- 
1023093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dleyna-core
Version: 0.7.0-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-core to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df8

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.4.1-1+rm

Dear submitter,

as the package dleyna-connector-dbus has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023135

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023094: marked as done (dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id 
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.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.)


-- 
1023093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dleyna-core
Version: 0.7.0-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-core to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df8

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.4.1-1+rm

Dear submitter,

as the package dleyna-connector-dbus has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023135

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023093: marked as done (dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id 
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.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.)


-- 
1023093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dleyna-core
Version: 0.7.0-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-core to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df8

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.4.1-1+rm

Dear submitter,

as the package dleyna-connector-dbus has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023135

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022011: marked as done (dleyna-server: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:06:06 +
with message-id 
and subject line Bug#1023134: Removed package(s) from unstable
has caused the Debian Bug report #1022011,
regarding dleyna-server: transition to gssdp/gupnp 1.6.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.)


-- 
1022011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dleyna-server
Version: 0.7.2-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-server to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-server/commit/e7f64192643f5783e19482a11697d

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.7.2-1+rm

Dear submitter,

as the package dleyna-server has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023134

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022010: marked as done (dleyna-renderer: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:05:35 +
with message-id 
and subject line Bug#1023133: Removed package(s) from unstable
has caused the Debian Bug report #1022010,
regarding dleyna-renderer: transition to gssdp/gupnp 1.6.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.)


-- 
1022010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dleyna-renderer
Version: 0.7.2-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-renderer to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-renderer/commit/b3a06c8bc4b91803d7bde312f49a6

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.7.2-1+rm

Dear submitter,

as the package dleyna-renderer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023133

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#922579: marked as done (FTBFS against opencv 4.0.1 (exp))

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:04:39 +
with message-id 
and subject line Bug#1023128: Removed package(s) from unstable
has caused the Debian Bug report #922579,
regarding FTBFS against opencv 4.0.1 (exp)
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.)


-- 
922579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeture
Version: 1.3.0-1
Severity: important

Opencv4 has moved its headers to /usr/include/opencv4/opencv2/*


freeture_1.3.0-1_ppc64el-2019-02-15T10:47:06Z.build.zst
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.3.0-1+rm

Dear submitter,

as the package freeture has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023128

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023173: marked as done (freeture: not installable, depends on libaravis-0.6-0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:04:39 +
with message-id 
and subject line Bug#1023128: Removed package(s) from unstable
has caused the Debian Bug report #1023173,
regarding freeture: not installable, depends on libaravis-0.6-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.)


-- 
1023173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeture
Version: 1.3.0-1+b1
Severity: serious

Hi, 

freeture is not installable in sid as it depends on  libaravis-0.6-0,
which only exists in oldstable.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 1.3.0-1+rm

Dear submitter,

as the package freeture has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023128

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1018774: marked as done (sockjs-client: Deprecated, replaced by node-sockjs)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:03:39 +
with message-id 
and subject line Bug#1023062: Removed package(s) from unstable
has caused the Debian Bug report #1018774,
regarding sockjs-client: Deprecated, replaced by node-sockjs
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.)


-- 
1018774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sockjs-client
Version: 0.3.4+dfsg-2
Severity: serious
Justification: Duplicate

An updated libjs-sockjs is given by node-sockjs. Please remove this
package
--- End Message ---
--- Begin Message ---
Version: 0.3.4+dfsg-2+rm

Dear submitter,

as the package sockjs-client has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023062

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022009: marked as done (dleyna-core: transition to gssdp/gupnp 1.6.0)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:05:08 +
with message-id 
and subject line Bug#1023131: Removed package(s) from unstable
has caused the Debian Bug report #1022009,
regarding dleyna-core: transition to gssdp/gupnp 1.6.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.)


-- 
1022009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dleyna-core
Version: 0.7.0-1
Severity: normal
Tags: fixed-upstream

Dear (non-existant) Maintainer,

New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI
and thus bumped the SONAME. A transition is needed.
The new versions are currently stuck in binary-NEW but should hopefully
soon be available in experimental (you can `gbp clone vcsgit:gssdp`,
`gbp clone vcsgit:gupnp` and build them yourself for now if you wish).

Please consider uploading a version of dleyna-core to experimental
that is compatible with the new SONAMEs.
The relevant upstream commit is:
https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df8

The relevant bug report for coordinating the transition is #1022003

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Version: 0.7.0-1+rm

Dear submitter,

as the package dleyna-core has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023131

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023030: marked as done (pysha3: Affected by CVE-2022-37454, unmaintained, remove from Debian?)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 00:01:57 +
with message-id 
and subject line Bug#1023033: Removed package(s) from unstable
has caused the Debian Bug report #1023030,
regarding pysha3: Affected by CVE-2022-37454, unmaintained, remove from Debian?
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.)


-- 
1023030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysha3
Version: 1.0.2-4.2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 
Forwarded: https://github.com/tiran/pysha3/issues/29

pysha3 is affected by CVE-2022-37454, a security issue in Keccak
See: https://github.com/python/cpython/issues/98517
https://mouha.be/sha-3-buffer-overflow/

This is a backport module to bring a feature from Python 3.6 back to
older versions.

It seems very dead upstream, should we just remove it from the archive?

There is currently one reverse-dependency, python-opentimestamps, and I
think we can trivially migrate that to use hashlib.

SR
--- End Message ---
--- Begin Message ---
Version: 1.0.2-4.2+rm

Dear submitter,

as the package pysha3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023033

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023229: f3d: autopkgtest regression on s390x: Compare with ref failed

[François Mazen]

Hello Paul,

thanks for reporting the issue, I've investigated and this is an Assimp
problem that I've reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023212

The big endian architecture may be the root of the issue, thanks for
pointing that out.

Best Regards,
François






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

Bug#1009966: Fixed upstream in 1.7.0 release

[Paweł Krawczyk]

https://github.com/kravietz/pam_tacplus/releases/tag/v1.7.0


libpam-tacplus (1.7.0-1) unstable; urgency=medium

  * libtac: Refactored the complex and overengineered TACACS+ session 
id generation,

replacing it with getrandom(2).
  * libtac: gnulib now provides implementation of missing functions.
  * libtac: Removed legacy MD5 code and replaced it with gnulib.
  * libtac: Legacy data structures such as attribute lists were 
replaced with gnulib structures.
  * libtac: CHAP implementation used a fixed challenge in contradiction 
with the RFC 1994
requirement. This was replaced with a pseudo-random challenge 
generated using getrandom(2).
  * libtac: ABI version set to 5:0:0. From now on, this is the only way 
to version the library.

The legacy static variables tac_ver_ were removed as confusing.
  * pam_tacplus: Calling process PID is now used as the task_id 
attribute in TACACS+
accounting session. This replaces an overengineered 
cryptographically random tasks identifiers.

  * libtac: Fix CVE-2016-20014. Closes: #1009966

 -- Pawel Krawczyk   Sat, 31 Oct 2022 22:44:00 
+0100

Processed: Merge and mark as forwarded

[Debian Bug Tracking System]

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

> reassign 1021078 src:celery
Bug #1021078 [src:billiard, src:celery] billiard breaks celery autopkgtest: 48 
failed
Bug reassigned from package 'src:billiard, src:celery' to 'src:celery'.
No longer marked as found in versions billiard/4.0.2-1 and celery/5.2.6-2.
Ignoring request to alter fixed versions of bug #1021078 to the same values 
previously set
> forcemerge 1020137 1021078
Bug #1020137 [src:celery] celery: FTBFS: KeyError: 4
Bug #1021078 [src:celery] billiard breaks celery autopkgtest: 48 failed
Marked as found in versions celery/5.2.6-2.
Added tag(s) ftbfs.
Merged 1020137 1021078
> affects 1020137 src:billiard
Bug #1020137 [src:celery] celery: FTBFS: KeyError: 4
Bug #1021078 [src:celery] billiard breaks celery autopkgtest: 48 failed
Added indication that 1020137 affects src:billiard
Added indication that 1021078 affects src:billiard
> forwarded 1020137 https://github.com/celery/celery/pull/7781
Bug #1020137 [src:celery] celery: FTBFS: KeyError: 4
Bug #1021078 [src:celery] billiard breaks celery autopkgtest: 48 failed
Set Bug forwarded-to-address to 'https://github.com/celery/celery/pull/7781'.
Set Bug forwarded-to-address to 'https://github.com/celery/celery/pull/7781'.
> thanks
Stopping processing here.

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

Processed: retitle 1020100 to projectile FTBFS with emacs 28

[Debian Bug Tracking System]

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

> retitle 1020100 projectile FTBFS with emacs 28
Bug #1020100 [src:projectile] projectile: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Changed Bug title to 'projectile FTBFS with emacs 28' from 'projectile: FTBFS: 
make: *** [debian/rules:4: binary] Error 25'.
> thanks
Stopping processing here.

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

Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

[Andreas Wirooks]

On Fri, 28 Oct 2022 20:26:55 +0200 Gert  wrote:
> 5.19.0-0.deb11.2-amd64 works fine at first glance.

I am also affected and i also tried this kernel and it works as you can
read here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#160

I also filed a new drm bug here:

https://gitlab.freedesktop.org/drm/amd/-/issues/2237

Kind regards,

Andreas

Bug#1022042: Bug#1022025: fixed in linux 5.10.149-2

[Andreas Wirooks]

On Thu, 27 Oct 2022 19:12:43 + inasprecali 
wrote:
> I think bug 1022806 is a recent one referring to 5.10.149-2
> specifically, which is about this same issue. I don't think there
> is a need to report yet another bug about it.

Ok, then i switch to 1022806 too. I already created a new drm bug:

https://gitlab.freedesktop.org/drm/amd/-/issues/2237

Processed: bug 1020180 is forwarded to https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3

[Debian Bug Tracking System]

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

> forwarded 1020180 
> https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3
Bug #1020180 [src:emacs-ivy] emacs-ivy: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Set Bug forwarded-to-address to 
'https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3'.
> thanks
Stopping processing here.

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

Processed: tagging 1020189

[Debian Bug Tracking System]

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

> tags 1020189 + fixed-upstream
Bug #1020189 [src:helpful-el] helpful-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1023225: esup-el: autopkgtest regression: No such file or directory, comp

[Debian Bug Tracking System]

Processing control commands:

> block 1020178 by -1
Bug #1020178 {Done: Lev Lamberov } [src:esup-el] esup-el: 
FTBFS: (file-missing "Cannot open load file" "No such file or directory" 
"comp")
1020178 was not blocked by any bugs.
1020178 was not blocking any bugs.
Added blocking bug(s) of 1020178: 1023225

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

Bug#1023225: esup-el: autopkgtest regression: No such file or directory, comp

[Adrian Bunk]

Control: block 1020178 by -1

On Mon, Oct 31, 2022 at 09:04:04PM +0100, Paul Gevers wrote:
>...
> With a recent upload of esup-el the autopkgtest of esup-el fails in testing
> when that autopkgtest is run with the binary packages of esup-el from
> unstable. It passes when run with only packages from testing. In tabular
> form:
> 
>passfail
> esup-elfrom testing0.7.1-4
> all others from testingfrom testing

But:
 pass
esup-el  from unstable
all others   from unstable

>...
> Paul
>...
> Cannot open load file: No such file or directory, comp
>...

I suspect the test-only fix for #1020178 that fixed the tests with Emacs 28
broke them with Emacs 27, so testing esup-el/unstable with emacs/unstable
should pass.

cu
Adrian

Processed: Re: Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: 
hci0: Reading Intel version command failed (-110)
Severity set to 'important' from 'grave'
> tags -1 + moreinfo
Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: 
hci0: Reading Intel version command failed (-110)
Added tag(s) moreinfo.

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

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Salvatore Bonaccorso]

Control: severity -1 important
Control: tags -1 + moreinfo

Hi Vincent,

On Mon, Oct 31, 2022 at 01:09:31PM +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: grave
> Justification: renders package unusable
> 
> (Setting to grave because Bluetooth is a major component.)
> 
> Bluetooth no longer works at all.
> 
> zira:~> journalctl -b -g bluetooth
> Oct 31 12:55:16 zira kernel: Bluetooth: Core ver 2.22
> Oct 31 12:55:16 zira kernel: NET: Registered PF_BLUETOOTH protocol family
> Oct 31 12:55:16 zira kernel: Bluetooth: HCI device and connection manager 
> initialized
> Oct 31 12:55:16 zira kernel: Bluetooth: HCI socket layer initialized
> Oct 31 12:55:16 zira kernel: Bluetooth: L2CAP socket layer initialized
> Oct 31 12:55:16 zira kernel: Bluetooth: SCO socket layer initialized
> Oct 31 12:55:17 zira systemd[1]: Starting Bluetooth service...
> Oct 31 12:55:17 zira systemd[795]: ConfigurationDirectory 'bluetooth' already 
> exists but the mode is different. (File system: 755 
> ConfigurationDirectoryMode: 555)
> Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth daemon 5.65
> Oct 31 12:55:17 zira systemd[1]: Started Bluetooth service.
> Oct 31 12:55:17 zira systemd[1]: Reached target Bluetooth Support.
> Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth management interface 1.22 
> initialized
> Oct 31 12:55:17 zira dbus-daemon[801]: [system] Activating via systemd: 
> service name='org.freedesktop.hostname1' 
> unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 
> pid=795 comm="/usr/libexec/bluetooth/bluetoothd")
> Oct 31 12:55:17 zira kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> Oct 31 12:55:17 zira kernel: Bluetooth: BNEP filters: protocol multicast
> Oct 31 12:55:17 zira kernel: Bluetooth: BNEP socket layer initialized
> Oct 31 12:55:17 zira NetworkManager[950]:   [1667217317.6273] Loaded 
> device plugin: NMBluezManager 
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.40.2/libnm-device-plugin-bluetooth.so)
> Oct 31 12:55:19 zira kernel: Bluetooth: hci0: Reading Intel version command 
> failed (-110)
> Oct 31 12:55:19 zira kernel: Bluetooth: hci0: command 0xfc05 tx timeout
> 
> With the 6.0.3-1 kernel version, I got:
> 
> Oct 31 11:17:59 zira kernel: Bluetooth: Core ver 2.22
> Oct 31 11:17:59 zira kernel: NET: Registered PF_BLUETOOTH protocol family
> Oct 31 11:17:59 zira kernel: Bluetooth: HCI device and connection manager 
> initialized
> Oct 31 11:17:59 zira kernel: Bluetooth: HCI socket layer initialized
> Oct 31 11:17:59 zira kernel: Bluetooth: L2CAP socket layer initialized
> Oct 31 11:17:59 zira kernel: Bluetooth: SCO socket layer initialized
> Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 
> build 2 week 3 2013
> Oct 31 11:17:59 zira kernel: bluetooth hci0: firmware: direct-loading 
> firmware intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
> Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Intel Bluetooth firmware file: 
> intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
> Oct 31 11:17:59 zira systemd[1]: Starting Bluetooth service...
> [...]
> 
> So it appears that the 6.0.5-1 kernel version can't load the firmware.

There were no Bluetooth related changes in the relatively small 6.0.3
to 6.0.5 update and I cannot reproduce the issue. Can you provide the
full boot and kernel logs? (ideally from both runs).

Regards,
Salvatore

Bug#1023239: dracut: [regression] missing grep

[Bastien Roucariès]

Package: dracut
Version: 056-3
Severity: critical
Tags: patch upstream
Justification: breaks the whole system
Forwarded: 
https://github.com/dracutdevs/dracut/commit/79f9d9e1c29a9c8fc046ab20765e5bde2aaa3428

Dear Maintainer,

grep is missing failling with lvm main partition.

Could you apply patch from upstream ?

Bastien


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

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

Versions of packages dracut depends on:
ii  dracut-core  056-3

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  

-- no debconf information

Bug#1023153: marked as done (fq FTBFS: missing build dependencies?)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 21:19:41 +
with message-id 
and subject line Bug#1023153: fixed in fq 0.0.9-2
has caused the Debian Bug report #1023153,
regarding fq FTBFS: missing build dependencies?
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.)


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

https://buildd.debian.org/status/logs.php?pkg=fq=0.0.9-1

...
 debian/rules binary-arch
dh binary-arch --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--builddirectory=_build 
-O--buildsystem=golang
   dh_autoreconf -a -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_configure -a -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_build -a -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 4 github.com/wader/fq
src/github.com/wader/fq/format/toml/toml.go:7:2: cannot find package 
"github.com/BurntSushi/toml" in any of:
/usr/lib/go-1.19/src/github.com/BurntSushi/toml (from $GOROOT)
/<>/_build/src/github.com/BurntSushi/toml (from $GOPATH)
src/github.com/wader/fq/format/crypto/hash.go:18:2: cannot find package 
"golang.org/x/crypto/md4" in any of:
/usr/lib/go-1.19/src/golang.org/x/crypto/md4 (from $GOROOT)
/<>/_build/src/golang.org/x/crypto/md4 (from $GOPATH)
src/github.com/wader/fq/format/crypto/hash.go:19:2: cannot find package 
"golang.org/x/crypto/sha3" in any of:
/usr/lib/go-1.19/src/golang.org/x/crypto/sha3 (from $GOROOT)
/<>/_build/src/golang.org/x/crypto/sha3 (from $GOPATH)
dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
github.com/wader/fq returned exit code 1
make: *** [debian/rules:60: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: fq
Source-Version: 0.0.9-2
Done: Daniel Milde 

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

Debian distribution maintenance software
pp.
Daniel Milde  (supplier of updated fq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 22:05:12 +0100
Source: fq
Architecture: source
Version: 0.0.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Daniel Milde 
Closes: 1023153
Changes:
 fq (0.0.9-2) unstable; urgency=medium
 .
   * Added dependencies (Closes: 1023153)
Checksums-Sha1:
 866b1694056f8ccee553ded30fb1588ac03b18cf 2425 fq_0.0.9-2.dsc
 efc7af35c2dfaef7debcba2c574659dfa2149cd1 7764844 fq_0.0.9.orig.tar.gz
 3033a6942be73d1f42dfa06714de9d775542dc76 6456 fq_0.0.9-2.debian.tar.xz
 25e7d0504b2eea76bba9fd84b06ff40a6f9462cf 7709 fq_0.0.9-2_source.buildinfo
Checksums-Sha256:
 a613ce8ebbf55baa35460efbda8a9c2ea8696c3960cfca15d938c3d789d056d3 2425 
fq_0.0.9-2.dsc
 abcc1292af007b8405cc924e3db0dc4e1838c6a851661f6388dce1a35fa7e8b6 7764844 
fq_0.0.9.orig.tar.gz
 89da6112f1618d2f5bf38e1483ff95c253d37b379795179b2ebf93e5f2591d30 6456 
fq_0.0.9-2.debian.tar.xz
 55c72279b4ad25783d3061f776aec847f3b4108f53c0ab28f91d37f20b372b6f 7709 
fq_0.0.9-2_source.buildinfo
Files:
 ba0625ff5c83b0e1aa3a1fc8031bf161 2425 utils optional fq_0.0.9-2.dsc
 1c1ab7ebed44acea1f45508478b0d1f7 7764844 utils optional fq_0.0.9.orig.tar.gz
 60b8613f74104c4618c822d4c4456668 6456 utils optional fq_0.0.9-2.debian.tar.xz
 228755ac66811e1fa941ac954b6218b5 7709 utils optional 
fq_0.0.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEENgtlhwehpEylf7Z+7wuhxPOZAQMFAmNgOTkQHGRhbmllbEBt
aWxkZS5jegAKCRDvC6HE85kBA9+LD/0SYUF0Z7x2RvzeEbC8eqR97zvH14jeocDW
SXXGvoFruoMhcGbxnU91W9F6pa6YUpFsqiUbo/sBBpaC7OnGT7zgnCEruELrdlq2
Y56RfRwMWd9ew9VF0k6S/jLpBIYS11By2ZuyGBJ4v5qCLZ7I+d7XkyZZgfPAuJmV
3Y/kq40cwVA0dcTk9+1ZOCvXrp8687uuQHKiHUT7kwGaX1sAPEQYU9W/HvY0hJA1
VpVfs24GEaCiFUAviGgvrnc9hlsxng6DsLN3YzXDbzXoh5LwDdqiHL3aEeSoNRhx
cfeOOAHUHptjIF59KYMq7YKVTUY4D7QerM1z2DZ5FmGrzUiFVKJmE4yxOzG31DM4
6AHWPYYIO9iytshdj3hn2dUbBht1DIZCvz+Q90IdWI2bln0X2ZbsgzHhbxZcu+oZ

Processed: retitle 1022355 to /usr/bin/msgfmt: cannot locate ITS rules for policy/org.freedesktop.color.policy.in

[Debian Bug Tracking System]

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

> retitle 1022355 /usr/bin/msgfmt: cannot locate ITS rules for 
> policy/org.freedesktop.color.policy.in
Bug #1022355 [src:colord] colord: FTBFS: 
../src/sensors/argyll/cd-spawn.c:475:20: warning: Deprecated pre-processor 
symbol: replace with "G_ADD_PRIVATE"
Changed Bug title to '/usr/bin/msgfmt: cannot locate ITS rules for 
policy/org.freedesktop.color.policy.in' from 'colord: FTBFS: 
../src/sensors/argyll/cd-spawn.c:475:20: warning: Deprecated pre-processor 
symbol: replace with "G_ADD_PRIVATE"'.
> thanks
Stopping processing here.

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

Processed: libdecaf please migrate to python3

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.0.2-1
Bug #1023238 [src:libdecaf] libdecaf please migrate to python3
Marked as fixed in versions libdecaf/1.0.2-1.

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

Bug#1023238: libdecaf please migrate to python3

[Paul Gevers]

Source: libdecaf
Version: 1.0.1-2
Severity: serious
Justification: rt
Control: fixed -1 1.0.2-1

Dear maintainers,

If I didn't make a mistake, wand is keeping python2.7 in the key package 
set because it (Build-)Depends on it. We're trying hard to remove 
python2.7 before the bookworm release. libdecaf seems to be one of two 
last packages blocking removal.


I note that a recent upload in experimental already build depends on 
python3. The Release Team would appreciate it if you don't wait to long 
with uploading to unstable if no further concerns block that decision.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023237: openjdk-11: Keep out of testing and stable

[Emmanuel Bourg]

Source: openjdk-11
Version: 11.0.4+11-1
Severity: serious
Justification: should not migrate to testing or stable any more


openjdk-17 is now the default JDK, but openjdk-11 is still required for
bootstrapping JVM-based languages like Kotlin or Scala in unstable.
Therefore the package should no longer migrate to testing or stable anymore.

Bug#1023231: cimg: autopkgtest failure everywhere but on amd64: './libHalf.so': File exists

[Paul Gevers]

Source: cimg
Version: 3.1.6+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

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


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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/c/cimg/27599388/log.gz

make[1]: Entering directory 
'/tmp/autopkgtest-lxc.1l29kob2/downtmp/autopkgtest_tmp'

grep: ../CImg.h: No such file or directory
grep: ../CImg.h: No such file or directory
grep: ../CImg.h: No such file or directory

** Compiling 'CImg_demo (..)' with 'gcc version 12.2.0 (Debian 12.2.0-3) '

Hack to provide -lIlmImf and -lHalf
if [ ! -e ./libHalf.so ] ; then   ln -s `find /usr/lib -type l -name 
"libHalf-2_5.so.*"`   ./libHalf.so ; fi

ln: failed to create symbolic link './libHalf.so': File exists
make[1]: *** [Makefile:322: CImg_demo] Error 1
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.1l29kob2/downtmp/autopkgtest_tmp'

make: *** [Makefile:459: Mlinux] Error 2
autopkgtest [17:13:51]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023230: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

[Paul Gevers]

Source: t-coffee, libbio-tools-run-alignment-tcoffee-perl
Control: found -1 t-coffee/13.45.0.4846264+dfsg-1
Control: found -1 libbio-tools-run-alignment-tcoffee-perl/1.7.4-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of t-coffee the autopkgtest of 
libbio-tools-run-alignment-tcoffee-perl fails in testing on all 
architectures but amd64 and i386 when that autopkgtest is run with the 
binary packages of t-coffee from unstable. It passes when run with only 
packages from testing. In tabular form:


  passfail
t-coffee  from testing13.45.0.4846264+dfsg-1
libbio-tools-run-alignment-tcoffee-perl from testing1.7.4-3
all othersfrom testingfrom testing

I copied some of the output at the bottom of this report. There's 
nothing there, it just waits for the timeout after 2:47h.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/libb/libbio-tools-run-alignment-tcoffee-perl/27686780/log.gz

autopkgtest [11:59:24]: ERROR: timed out on command "su -s /bin/bash 
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.l1eqkc21/downtmp/build.05l/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autodep8-perl-build-deps-artifacts"; 
export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autodep8-perl-build-deps-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=4; unset LANGUAGE 
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;cd "$buildtree"; exec 
/tmp/autopkgtest-lxc.l1eqkc21/downtmp/wrapper.sh 
--script-pid-file=/tmp/autopkgtest_script_pid 
--stderr=/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autodep8-perl-build-deps-stderr 
--stdout=/tmp/autopkgtest-lxc.l1eqkc21/downtmp/autodep8-perl-build-deps-stdout 
-- bash -ec '/usr/share/pkg-perl-autopkgtest/runner build-deps' ;" 
(kind: test)

autopkgtest [11:59:24]: test autodep8-perl-build-deps



OpenPGP_signature
Description: OpenPGP digital signature

Processed: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

[Debian Bug Tracking System]

Processing control commands:

> found -1 t-coffee/13.45.0.4846264+dfsg-1
Bug #1023230 [src:t-coffee, src:libbio-tools-run-alignment-tcoffee-perl] 
t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times 
out after 2:47 hours
Marked as found in versions t-coffee/13.45.0.4846264+dfsg-1.
> found -1 libbio-tools-run-alignment-tcoffee-perl/1.7.4-3
Bug #1023230 [src:t-coffee, src:libbio-tools-run-alignment-tcoffee-perl] 
t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times 
out after 2:47 hours
Marked as found in versions libbio-tools-run-alignment-tcoffee-perl/1.7.4-3.

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

Bug#1023229: f3d: autopkgtest regression on s390x: Compare with ref failed

[Paul Gevers]

Source: f3d
Version: 1.3.1+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
f3dfrom testing1.3.1+dfsg-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. I note that 
s390x is our only big endian release architecture (just in case that 
matters to the problem at hand).


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/s390x/f/f3d/27693775/log.gz

==
Smoke Test
==
No config file found
Loading: /tmp/autopkgtest-lxc.dd0h8lat/downtmp/autopkgtest_tmp/cube.dae

Warning: In 
./library/VTKExtensions/Readers/vtkF3DAssimpImporter.cxx, line 583
vtkF3DAssimpImporter (0x2aa2fdf42f0): Assimp failed to load: 
/tmp/autopkgtest-lxc.dd0h8lat/downtmp/autopkgtest_tmp/cube.dae



No camera available in this file



Camera position: 0,0,1
Camera focal point: 0,0,0
Camera view up: 0,1,0
Camera view angle: 30


===
Generate the new screenshot
===

Compare with ref

Comparing "debian/tests/cube_dae_ref.png" and 
"/tmp/autopkgtest-lxc.dd0h8lat/downtmp/check-cube-dae-artifacts/cube_dae.png"

  Mean error = 0.0898372
  RMS error = 0.250222
  Peak SNR = 12.0335
  Max error  = 0.72549 @ (393, 106, R)  values are 0.92549, 0.92549, 
0.92549 vs 0.2, 0.2, 0.2

  47288 pixels (15.4%) over 1e-06
  47288 pixels (15.4%) over 1e-06
FAILURE
autopkgtest [06:20:10]: test check-cube-dae



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023227: breezy: autopkgtest regression: Non-UTF-8 code starting with '\xf2' in file /usr/bin/brz

[Paul Gevers]

Source: breezy
Version: 3.3.0+bzr7661-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
breezy from testing3.3.0+bzr7661-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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


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

Paul

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/b/breezy/27685392/log.gz

SyntaxError: Non-UTF-8 code starting with '\xf2' in file /usr/bin/brz on 
line 2, but no encoding declared; see 
https://python.org/dev/peps/pep-0263/ for details

autopkgtest [23:12:42]: test testsuite3



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023226: pg-fact-loader: autopkgtest regression

[Paul Gevers]

Source: pg-fact-loader
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pg-fact-loader from testing1.7.0-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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


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

Paul

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pg-fact-loader/27687022/log.gz

### PostgreSQL 15 installcheck ###
Creating new PostgreSQL cluster 15/regress ...
echo "+++ regress install-check in  +++" && 
/usr/lib/postgresql/15/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress 
--inputdir=./ --bindir='/usr/lib/postgresql/15/bin' 
--dbname=contrib_regression 01_create_ext 02_schema 03_audit 04_seeds 
05_pgl_setup 06_basic_workers 07_launch_worker 08_fact_table_deps 
09_purge 10_delete 11_more_data 12_no_proid 13_cutoff_no_dep_on_filter 
14_null_key 15_source_change_date 16_1_2_features 17_1_3_features

+++ regress install-check in  +++
(using postmaster on localhost, port 5433)
== dropping database "contrib_regression" ==
SET
DROP DATABASE
== creating database "contrib_regression" ==
CREATE DATABASE
ALTER DATABASE
ALTER DATABASE
ALTER DATABASE
ALTER DATABASE
ALTER DATABASE
ALTER DATABASE
== running regression test queries==
test 01_create_ext... ok  146 ms
test 02_schema... ok   92 ms
test 03_audit ... ok   41 ms
test 04_seeds ... ok   64 ms
test 05_pgl_setup ... ok   27 ms
test 06_basic_workers ... ok 8854 ms
test 07_launch_worker ... ok 4031 ms
test 08_fact_table_deps   ... ok 2663 ms
test 09_purge ... ok  176 ms
test 10_delete... ok13701 ms
test 11_more_data ... ok 6198 ms
test 12_no_proid  ... ok10785 ms
test 13_cutoff_no_dep_on_filter   ... ok36008 ms
test 14_null_key  ... ok  238 ms
test 15_source_change_date... ok  101 ms
test 16_1_2_features  ... ok 3220 ms
test 17_1_3_features  ... FAILED 8219 ms

===
 1 of 17 tests failed. ===

The differences that caused some tests to fail can be viewed in the
file 
"/tmp/autopkgtest-lxc.68jcp06n/downtmp/build.L0a/src/regression.diffs". 
A copy of the test summary that you see
above is saved in the file 
"/tmp/autopkgtest-lxc.68jcp06n/downtmp/build.L0a/src/regression.out".


make: *** [/usr/lib/postgresql/15/lib/pgxs/src/makefiles/pgxs.mk:433: 
installcheck] Error 1
*** /tmp/pg_virtualenv.Azz268/log/postgresql-15-regress.log (last 100 
lines) ***


, update_key AS (
SELECT qdwr.queue_table_dep_id,
  --Cutoff the id to that newly found, otherwise default to last value
  COALESCE(mu.last_cutoff_id, qdwr.last_cutoff_id) AS last_cutoff_id,
	  --This cutoff time must always be the same for all queue tables for 
given fact table.
	  --Even if there are no new records, we move this forward to wherever 
the stream is at

  qdwr.maximum_cutoff_time AS last_cutoff_source_time
FROM fact_loader.queue_deps_all qdwr
	LEFT JOIN new_metadata mu ON mu.queue_table_dep_id = 
qdwr.queue_table_dep_id

WHERE qdwr.fact_table_id = 2
--Exclude dependent fact tables from updates directly to 
queue_table_deps
  AND qdwr.fact_table_dep_id IS NULL
)

/
	This SQL also nearly matches that for the queue_table_deps but would be 
a little ugly to try to DRY up

/
, update_key_fact_dep AS (
SELECT qdwr.fact_table_dep_queue_table_dep_id,
  qdwr.fact_table_id,
  COALESCE(mu.last_cutoff_id, qdwr.last_cutoff_id) AS last_cutoff_id,
  qdwr.maximum_cutoff_time AS last_cutoff_source_time

Bug#1023225: esup-el: autopkgtest regression: No such file or directory, comp

[Paul Gevers]

Source: esup-el
Version: 0.7.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
esup-elfrom testing0.7.1-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. I'm seeing 
command lines about native complilation. Are you sure you don't need a 
new enough emacs that supports that for your test or package?


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/e/esup-el/27685397/log.gz

	emacs -batch -Q -l package --eval "(setq native-comp-eln-load-path 
'(\"/tmp/3oIzPMCFGJ\"))" --eval "(add-to-list 'package-directory-list 
\"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
package-initialize -L . -L test -l test/esup-test.el --eval 
\(ert-run-tests-batch-and-exit\)

Cannot open load file: No such file or directory, comp
dh_elpa_test: error: emacs -batch -Q -l package --eval "(setq 
native-comp-eln-load-path '(\"/tmp/3oIzPMCFGJ\"))" --eval "(add-to-list 
'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
"(add-to-list 'package-directory-list 
\"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -L 
test -l test/esup-test.el --eval \(ert-run-tests-batch-and-exit\) 
returned exit code 255

autopkgtest [23:12:43]: test dh-elpa-test-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

[Paul Gevers]

Source: strongswan
Version: 5.9.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
strongswan from testing5.9.8-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The 
autopkgtest d/t/control files says the first test depends on 
strongswan-scepclient, but src:strongswan no long build it.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/strongswan/27694623/log.gz

Removing autopkgtest-satdep (0) ...
autopkgtest: WARNING: package strongswan is not installed though it 
should be
autopkgtest: WARNING: package strongswan-pki is not installed though it 
should be
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt 
pinning. Retrying with using all packages from unstable

Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on strongswan-scepclient:amd64 < 
none @un H >
  Considering strongswan-scepclient:amd64 1 as a solution to 
autopkgtest-satdep:amd64 -2
  Removing autopkgtest-satdep:amd64 rather than change 
strongswan-scepclient:amd64

Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  autopkgtest-satdep
0 upgraded, 0 newly installed, 1 to remove and 15 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13114 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest: WARNING: package strongswan is not installed though it 
should be
autopkgtest: WARNING: package strongswan-pki is not installed though it 
should be
autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt 
install on test deps directly for further data about failing 
dependencies in test logs

Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) strongswan-scepclient:amd64 < none -> 5.9.6-1+b1 @un 
puN Ib >
Broken strongswan-scepclient:amd64 Depends on libstrongswan:amd64 < none 
-> 5.9.8-1+b1 @un puN > (= 5.9.6-1+b1)
  Considering libstrongswan:amd64 6 as a solution to 
strongswan-scepclient:amd64 

  Re-Instated libstrongswan:amd64
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 strongswan-scepclient : Depends: libstrongswan (= 5.9.6-1+b1) but 
5.9.8-1+b1 is to be installed

E: Unable to correct problems, you have held broken packages.
admin-strongswan-charon FAIL badpkg
blame: strongswan



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023222: python-xarray: autopkgtest regression on s390x: segmentation fault

[Paul Gevers]

Source: python-xarray
Version: 2022.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python-xarray  from testing2022.10.0-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/s390x/p/python-xarray/27672266/log.gz

[ 90%]
tests/test_sparse.py::test_variable_property[nbytes] PASSED 
[ 90%]
tests/test_sparse.py::test_variable_property[ndim] PASSED 
[ 90%]
tests/test_sparse.py::test_variable_property[values] XFAIL (Coercion...) 
[ 90%]
tests/test_sparse.py::test_variable_method[obj.all(*(), **{})-False] 
Fatal Python error: Segmentation fault


Current thread 0x03ff91575040 (most recent call first):
  File "/usr/lib/python3/dist-packages/sparse/_coo/core.py", line 1562 
in _grouped_reduce
  File "/usr/lib/python3/dist-packages/sparse/_coo/core.py", line 687 
in _reduce_calc
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
360 in reduce
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
278 in _reduce
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
307 in __array_ufunc__
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
490 in all
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
268 in __array_function__

  File "<__array_function__ internals>", line 5 in all
  File "/usr/lib/python3/dist-packages/xarray/core/variable.py", line 
1901 in reduce
  File "/usr/lib/python3/dist-packages/xarray/core/common.py", line 73 
in wrapped_func
  File "/usr/lib/python3/dist-packages/xarray/tests/test_sparse.py", 
line 69 in __call__
  File "/usr/lib/python3/dist-packages/xarray/tests/test_sparse.py", 
line 231 in test_variable_method
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 192 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1761 in 
runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 166 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 259 in 

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 338 in 
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 258 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 219 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 130 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 111 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 347 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__

  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 322 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 268 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 315 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 164 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 187 in console_main
  File 

Processed: bug 1022681 is forwarded to https://github.com/yesodweb/clientsession/issues/37

[Debian Bug Tracking System]

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

> forwarded 1022681 https://github.com/yesodweb/clientsession/issues/37
Bug #1022681 [src:haskell-clientsession] haskell-clientsession build depends on 
haskell-cipher-aes and haskell-cprng-aes
Set Bug forwarded-to-address to 
'https://github.com/yesodweb/clientsession/issues/37'.
> thanks
Stopping processing here.

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

Bug#1023220: src:pd-flext: fails to migrate to testing for too long: autopkgtest failure on armel and armhf

[Paul Gevers]

Source: pd-flext
Version: 0.6.1-3
Severity: serious
Control: close -1 0.6.2-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:pd-flext has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package recently gained an 
autopkgtest (great), however it fails on armel and armhf:

fatal error: gnu/stubs-hard.h: No such file or directory

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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:pd-flext: fails to migrate to testing for too long: autopkgtest failure on armel and armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6.2-1
Bug #1023220 [src:pd-flext] src:pd-flext: fails to migrate to testing for too 
long: autopkgtest failure on armel and armhf
Marked as fixed in versions pd-flext/0.6.2-1.
Bug #1023220 [src:pd-flext] src:pd-flext: fails to migrate to testing for too 
long: autopkgtest failure on armel and armhf
Marked Bug as done

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

Processed: src:psychtoolbox-3: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0.18.12.dfsg1-1
Bug #1023219 [src:psychtoolbox-3] src:psychtoolbox-3: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions psychtoolbox-3/3.0.18.12.dfsg1-1.
Bug #1023219 [src:psychtoolbox-3] src:psychtoolbox-3: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#1023219: src:psychtoolbox-3: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: psychtoolbox-3
Version: 3.0.18.9.dfsg1-1
Severity: serious
Control: close -1 3.0.18.12.dfsg1-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#945139: marked as done (pipenv: update to latest pipenv)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id 
and subject line Bug#945139: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #945139,
regarding pipenv: update to latest pipenv
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.)


-- 
945139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipenv
Version: 11.9.0-1
Severity: normal

Dear Maintainer,

the pipenv 11.9.0-1 does not work many feature ex:
pipenv check and pipenv run
please update latest pipenv
reguards



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pipenv depends on:
ii  python3   3.7.3-1
ii  python3-certifi   2018.8.24-1
ii  python3-pip   18.1-5
ii  python3-pkg-resources 40.8.0-1
ii  python3-virtualenv15.1.0+ds-2
ii  python3-virtualenv-clone  0.3.0-1.2

pipenv recommends no packages.

pipenv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipenv
Source-Version: 2022.10.25+ds2-1
Done: Ileana Dumitrescu 

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

Debian distribution maintenance software
pp.
Ileana Dumitrescu  (supplier of updated pipenv 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 16:36:38 +
Source: pipenv
Architecture: source
Version: 2022.10.25+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ileana Dumitrescu 
Closes: 941447 945139 958292 1012124 1019714
Launchpad-Bugs-Fixed: 1943582 1970106
Changes:
 pipenv (2022.10.25+ds2-1) unstable; urgency=medium
 .
   [ Ileana Dumitrescu ]
   * New upstream release (Closes: #945139) (LP: #1943582)
 Builds with python3.10 (Closes: #1012124) (LP: #1970106)
 Fixes pipenv check issue (Closes: #941447)
   * Remove patches (no longer needed)
   * d/control: Bump standards version to 4.6.1
Add Rules-Requires-Root line
Remove unnecessary comments
Add myself as an uploader
   * d/copyright: Exclude get-pipenv.py from tarball (Closes: #1019714)
  Exclude prebuilt windows binaries from tarball
  Update licensing
  Update debian copyright year to 2022
   * d/pipenv.docs: Fix README.rst location
   * d/rules: Remove unnecessary comments
  Remove vendor license and readme files during dh_auto_install
   * d/source/lintian-overrides: Override for false positive source-is-missing
   * d/watch: Remove unnecessary comments
  Remove  string and debian uupdate
  Add repack opts
 .
   [ Bastian Germann ]
   * d/control: No longer endorse the package as official (Closes: #958292)
 .
   [ Jeroen Ploemen ]
   * Control: bump compat level to 13 (from 10).
   * Rules: set buildsystem to pybuild.
Checksums-Sha1:
 2f27395d95f43ea593633dcf62cecae2e185efc8 2194 pipenv_2022.10.25+ds2-1.dsc
 680810acea719d9e5c46193fa6dd9f6eb9cd8abe 8126268 
pipenv_2022.10.25+ds2.orig.tar.xz
 1698c54a27bc1b76992778bd8b3f7c76efc859b5 6144 
pipenv_2022.10.25+ds2-1.debian.tar.xz
 a076a81392ea87134fca283e493e59b6cf784b22 8071 
pipenv_2022.10.25+ds2-1_source.buildinfo
Checksums-Sha256:
 cab9eb6c2b48b94904f025d2ed4fd6d611f5a8fd0e32206d1ba60f3d0ee35c85 2194 
pipenv_2022.10.25+ds2-1.dsc
 d33d3a7fc583e5c1acc9522cd2714cf352821861da43491f65c541d2f7df6227 8126268 
pipenv_2022.10.25+ds2.orig.tar.xz
 ec931f4e83348c3eeb168780c735e7bec73056c92e374accd66e681a17be5468 6144 
pipenv_2022.10.25+ds2-1.debian.tar.xz
 ffd033188824f448ab51ceb834b6eb97e2602d793012a85e0dc5f84a47bcb458 8071 

Bug#1012124: marked as done (pipenv: Pipenv 11.9.0-2 fails with python3.10, which is the default python3 in sid)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id 
and subject line Bug#1012124: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #1012124,
regarding pipenv: Pipenv 11.9.0-2 fails with python3.10, which is the default 
python3 in sid
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.)


-- 
1012124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipenv
Version: 11.9.0-2
Severity: normal
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

The pipenv script in /usr/bin/pipenv uses the shebang #!/usr/bin/python3, which
in turn points currently in sid to python3.10

When using python3.10 instead of python3.9, pipenv fails with errors such as
those included at the end of this report. However, if the script is invoked
using python 3.9, as follows:

python3.9 /usr/bin/pipenv

then pipenv works fine.

I would assume that either a different, newer version of pipenv needs to be
uploaded, or the current version would need to ensure that python 3.9 is used
instead of python 3.10, by either modifying the shebang in the script, or
verifying that the python version in use is one of the known-compatible ones.

Errors when running pipenv:
--

Traceback (most recent call last):
  File "/usr/bin/pipenv", line 33, in 
sys.exit(load_entry_point('pipenv==11.9.0', 'console_scripts', 'pipenv')())
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 722,
in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 696,
in main
with self.make_context(prog_name, args, **extra) as ctx:
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 621,
in make_context
self.parse_args(ctx, args)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 1018,
in parse_args
rest = Command.parse_args(self, ctx, args)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 875,
in parse_args
parser = self.make_parser(ctx)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 821,
in make_parser
for param in self.get_params(ctx):
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 774,
in get_params
help_option = self.get_help_option(ctx)
  File "/usr/lib/python3/dist-packages/pipenv/cli.py", line 26, in
get_help_option
from .import core
  File "/usr/lib/python3/dist-packages/pipenv/core.py", line 21, in 
import requests
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/__init__.py",
line 65, in 
from . import utils
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/utils.py", line
27, in 
from .cookies import RequestsCookieJar, cookiejar_from_dict
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/cookies.py", line
172, in 
class RequestsCookieJar(cookielib.CookieJar, collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'

--


Thank you very much!


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

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

Versions of packages pipenv depends on:
ii  python3   3.10.4-1+b1
ii  python3-certifi   2020.6.20-1
ii  python3-pip   22.1.1+dfsg-1
ii  python3-pkg-resources 59.6.0-1.2
ii  python3-virtualenv20.14.0+ds-1
ii  python3-virtualenv-clone  0.3.0-2

pipenv recommends no packages.

pipenv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipenv
Source-Version: 2022.10.25+ds2-1
Done: Ileana Dumitrescu 

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

Debian distribution maintenance software
pp.
Ileana Dumitrescu  

Bug#1019714: marked as done (pipenv: Contains non-source file)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id 
and subject line Bug#1019714: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #1019714,
regarding pipenv: Contains non-source file
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.)


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

Source: pipenv
Version: 11.9.0-2
Severity: serious

pipenv contains get-pipenv.py, which has a base85 blob that supposedly "contains an 
entire copy of pip."
pipenv has a runtime dependency on python3-pip, so this is not actually needed 
and removing the file
does not make the build fail.

Please repack the source, excluding that file.
--- End Message ---
--- Begin Message ---
Source: pipenv
Source-Version: 2022.10.25+ds2-1
Done: Ileana Dumitrescu 

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

Debian distribution maintenance software
pp.
Ileana Dumitrescu  (supplier of updated pipenv 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 16:36:38 +
Source: pipenv
Architecture: source
Version: 2022.10.25+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ileana Dumitrescu 
Closes: 941447 945139 958292 1012124 1019714
Launchpad-Bugs-Fixed: 1943582 1970106
Changes:
 pipenv (2022.10.25+ds2-1) unstable; urgency=medium
 .
   [ Ileana Dumitrescu ]
   * New upstream release (Closes: #945139) (LP: #1943582)
 Builds with python3.10 (Closes: #1012124) (LP: #1970106)
 Fixes pipenv check issue (Closes: #941447)
   * Remove patches (no longer needed)
   * d/control: Bump standards version to 4.6.1
Add Rules-Requires-Root line
Remove unnecessary comments
Add myself as an uploader
   * d/copyright: Exclude get-pipenv.py from tarball (Closes: #1019714)
  Exclude prebuilt windows binaries from tarball
  Update licensing
  Update debian copyright year to 2022
   * d/pipenv.docs: Fix README.rst location
   * d/rules: Remove unnecessary comments
  Remove vendor license and readme files during dh_auto_install
   * d/source/lintian-overrides: Override for false positive source-is-missing
   * d/watch: Remove unnecessary comments
  Remove  string and debian uupdate
  Add repack opts
 .
   [ Bastian Germann ]
   * d/control: No longer endorse the package as official (Closes: #958292)
 .
   [ Jeroen Ploemen ]
   * Control: bump compat level to 13 (from 10).
   * Rules: set buildsystem to pybuild.
Checksums-Sha1:
 2f27395d95f43ea593633dcf62cecae2e185efc8 2194 pipenv_2022.10.25+ds2-1.dsc
 680810acea719d9e5c46193fa6dd9f6eb9cd8abe 8126268 
pipenv_2022.10.25+ds2.orig.tar.xz
 1698c54a27bc1b76992778bd8b3f7c76efc859b5 6144 
pipenv_2022.10.25+ds2-1.debian.tar.xz
 a076a81392ea87134fca283e493e59b6cf784b22 8071 
pipenv_2022.10.25+ds2-1_source.buildinfo
Checksums-Sha256:
 cab9eb6c2b48b94904f025d2ed4fd6d611f5a8fd0e32206d1ba60f3d0ee35c85 2194 
pipenv_2022.10.25+ds2-1.dsc
 d33d3a7fc583e5c1acc9522cd2714cf352821861da43491f65c541d2f7df6227 8126268 
pipenv_2022.10.25+ds2.orig.tar.xz
 ec931f4e83348c3eeb168780c735e7bec73056c92e374accd66e681a17be5468 6144 
pipenv_2022.10.25+ds2-1.debian.tar.xz
 ffd033188824f448ab51ceb834b6eb97e2602d793012a85e0dc5f84a47bcb458 8071 
pipenv_2022.10.25+ds2-1_source.buildinfo
Files:
 c55e271bd5366ec6753470cd0ef0069d 2194 python optional 
pipenv_2022.10.25+ds2-1.dsc
 d52be3a9486b1d5186653e108857775d 8126268 python optional 
pipenv_2022.10.25+ds2.orig.tar.xz
 a0d2fce7529ea6f6c6713492db375b4d 6144 python optional 
pipenv_2022.10.25+ds2-1.debian.tar.xz
 be1f10755157e562bf1d22af46662127 8071 python optional 
pipenv_2022.10.25+ds2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmNgD7UACgkQQoMEoXSN
zHqQehAA6Pw4bbhLiMHVpHMR0vp+/TDEbiPOvrCKmRYJ8cvBy3400akIyHcAb326

Bug#1022414: marked as done (bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding bpftrace: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_configure] Error 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DBUILD_TESTING:BOOL=OFF
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix 
> Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTING:BOOL=OFF ..
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Found LibBcc: /usr/lib/x86_64-linux-gnu/libbcc.so  
> -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE
> -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE - Success
> -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE
> -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE - Success
> -- Looking for bcc_usdt_foreach
> -- Looking for bcc_usdt_foreach - found
> -- Found LibBpf: /usr/lib/x86_64-linux-gnu/libbpf.so  
> -- Looking for btf_dump__new
> -- Looking for btf_dump__new - found
> -- Looking for btf_dump__emit_type_decl
> -- Looking for btf_dump__emit_type_decl - found
> -- Looking for bpf_prog_load
> -- Looking for bpf_prog_load - found
> -- Looking for bpf_map_create
> -- Looking for bpf_map_create - found
> -- Looking for bpf_map_lookup_batch
> -- Looking for bpf_map_lookup_batch - found
> -- Looking for bpf_link_create
> -- Looking for bpf_link_create - found
> -- Looking for bpf_prog_test_run_opts
> -- Looking for bpf_prog_test_run_opts - found
> -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT
> -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT - Success
> -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0
> -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 - Success
> -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED
> -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED - Success
> -- Performing Test HAVE_LIBBPF_KPROBE_MULTI
> -- Performing Test HAVE_LIBBPF_KPROBE_MULTI - Success
> -- Found LibElf: /usr/lib/x86_64-linux-gnu/libelf.so  
> -- Found LibCereal: /usr/include  
> -- Found BISON: /usr/bin/bison (found version "3.8.2") 
> -- Found FLEX: /usr/bin/flex (found version "2.6.4") 
> -- Looking for name_to_handle_at
> -- Looking for name_to_handle_at - found
> -- Please install the libbfd development package (missing: LIBBFD_LIBRARIES 
> LIBBFD_INCLUDE_DIRS) 
> -- Please install the libopcodes development package (missing: 
> LIBOPCODES_LIBRARIES LIBOPCODES_INCLUDE_DIRS) 
> -- Found LibDw: /usr/lib/x86_64-linux-gnu/libdw.so  
> -- Please install the libcap development package (missing: LIBPCAP_LIBRARIES 
> LIBPCAP_INCLUDE_DIRS) 
> -- Looking for bcc_elf_foreach_sym
> -- Looking for bcc_elf_foreach_sym - found
> -- Looking for bpf_attach_kfunc
> -- Looking for bpf_attach_kfunc - found
> -- Looking for bcc_usdt_addsem_probe
> -- Looking for bcc_usdt_addsem_probe - found
> -- Looking for bcc_procutils_which_so
> -- Looking for bcc_procutils_which_so - found
> -- Looking for sys/sdt.h
> -- Looking for sys/sdt.h - found
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- 

Bug#1022409: marked as done (ccls: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding ccls: FTBFS: make[1]: *** [debian/rules:18: 
override_dh_auto_configure] Error 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DCCLS_VERSION=0.20220729-1 
> -DCLANG_RESOURCE_DIR=/usr/include/clang/14
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCCLS_VERSION=0.20220729-1 -DCLANG_RESOURCE_DIR=/usr/include/clang/14 ..
> -- The CXX compiler identification is GNU 12.2.0
> -- The C compiler identification is GNU 12.2.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/lib/cmake/llvm/LLVMConfig.cmake:323 (include)
>   /usr/lib/cmake/clang-14/ClangConfig.cmake:10 (find_package)
>   CMakeLists.txt:72 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //No help, variable specified on the command line.
> CCLS_VERSION:UNINITIALIZED=0.20220729-1
> 
> //No help, variable specified on the command line.
> CLANG_RESOURCE_DIR:UNINITIALIZED=/usr/include/clang/14
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> 

Bug#1022381: marked as done (cvise: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding cvise: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_configure] Error 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   -DCMAKE_PREFIX_PATH=/usr/lib/llvm-14 \
>   -DCLANG_FORMAT=clang-format-14 \
>   -DCMAKE_INSTALL_LIBEXECDIR=lib
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix 
> Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_PREFIX_PATH=/usr/lib/llvm-14 -DCLANG_FORMAT=clang-format-14 
> -DCMAKE_INSTALL_LIBEXECDIR=lib ..
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
>   CMakeLists.txt:30 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //No help, variable specified on the command line.
> CLANG_FORMAT:UNINITIALIZED=clang-format-14
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
> 
> //A wrapper around 'ar' adding the appropriate '--plugin' option
> // for the GCC compiler
> 

Bug#1022366: marked as done (irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 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.)


-- 
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: irony-mode
Version: 1.5.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary -Dserver --with elpa
>dh_update_autotools_config -O-Dserver
>dh_autoreconf -O-Dserver
>dh_auto_configure -O-Dserver
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> ../server
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/lib/cmake/llvm/LLVMConfig.cmake:323 (include)
>   /usr/lib/cmake/clang-14/ClangConfig.cmake:10 (find_package)
>   src/CMakeLists.txt:4 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build the testing tree.
> BUILD_TESTING:BOOL=ON
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
> 
> //A wrapper around 'ar' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-12
> 
> //A wrapper around 'ranlib' 

Bug#1022337: marked as done (qt6-tools: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding qt6-tools: FTBFS: The imported target "sancov" references the file 
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu \
>   -DCMAKE_SKIP_INSTALL_RPATH=ON
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu -DCMAKE_SKIP_INSTALL_RPATH=ON ..
> -- The CXX compiler identification is GNU 12.2.0
> -- The C compiler identification is GNU 12.2.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
> -- Found Threads: TRUE  
> -- Performing Test HAVE_STDATOMIC
> -- Performing Test HAVE_STDATOMIC - Success
> -- Found WrapAtomic: TRUE  
> -- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so   
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
>   /usr/lib/llvm-14/lib/cmake/clang/ClangConfig.cmake:10 (find_package)
>   cmake/FindWrapLibClang.cmake:14 (find_package)
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFindPackageHelpers.cmake:130 
> (find_package)
>   configure.cmake:17 (qt_find_package)
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFeature.cmake:573 (include)
>   src/CMakeLists.txt:21 (qt_feature_evaluate_features)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build Qt statically or dynamically
> BUILD_SHARED_LIBS:BOOL=ON
> 
> BUILD_WITH_PCH:STRING=ON
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //CXX compiler
> 

Bug#1022353: marked as done (doxygen: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding doxygen: FTBFS: The imported target "sancov" references the file 
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
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.)


-- 
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doxygen
Version: 1.9.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>/jquery'
> cat jquery-3.6.0.min.js jquery.ui-1.12.1.min.js jquery.scrollTo-2.1.2.min.js 
> jquery.powertip-1.3.1.mod.min.js jquery.ui.touch-punch-0.2.3.min.js 
> jquery.smartmenus-1.1.0.min.js > jquery.js
> cat sm-core-css.css sass/sm-dox.scss | sassc -I sass --style compressed > 
> doxmenu-min.css
> cp jquery.js ../templates/html/jquery.js
> cp doxmenu-min.css ../templates/html/tabs.css
> make[1]: Leaving directory '/<>/jquery'
> rm -rf build
> mkdir -p build
> cd build && cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/usr 
> -Dbuild_wizard=ON -Dbuild_doc=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 
> -Duse_libclang=ON -Dbuild_search=ON -Dbuild_parse=ON /<>
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11") 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
>   CMakeLists.txt:53 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/build/CMakeFiles/CMakeOutput.log".
> make: *** [debian/rules:42: configure-stamp] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/doxygen_1.9.4-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=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 ---

fixed 1021857 1:14.0.6-7
thanks

I think the issue is fixed but if someone knows cmake well. please let 
me know :)


Cheers
S--- End Message ---

Bug#1022349: marked as done (iwyu: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding iwyu: FTBFS: The imported target "sancov" references the file 
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS= 
> -DLLVM_PATH=/usr/lib/llvm-14/ -DCMAKE_PREFIX_PATH=/usr/lib/llvm-14/
>   cd iwyu-build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS= -DLLVM_PATH=/usr/lib/llvm-14/ 
> -DCMAKE_PREFIX_PATH=/usr/lib/llvm-14/ ..
> -- IWYU: out-of-tree configuration
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11") 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 
> (message):
>   The imported target "sancov" references the file
> 
>  "/usr/lib/llvm-14/bin/sancov"
> 
>   but this file does not exist.  Possible reasons include:
> 
>   * The file was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and contained
> 
>  "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"
> 
>   but not all the files it references.
> 
> Call Stack (most recent call first):
>   /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
>   CMakeLists.txt:19 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/iwyu_8.18-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=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 ---

fixed 1021857 1:14.0.6-7
thanks

I think the issue is fixed but if someone knows cmake well. please let 
me know :)


Cheers
S--- End Message ---

Bug#1021857: marked as done (llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id 
and subject line fixed
has caused the Debian Bug report #1021857,
regarding llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target 
"sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does 
not exist.
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.)


-- 
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-14-dev
Version: 1:14.0.6-5
Severity: serious

This is an autopkgtest regression, but also experienced e.g. while
building spirv-llvm-translator-14:

-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test HAVE_FFI_CALL
-- Performing Test HAVE_FFI_CALL - Success
-- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
-- Performing Test Terminfo_LINKABLE
-- Performing Test Terminfo_LINKABLE - Success
-- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") 
CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):
  The imported target "sancov" references the file

 "/usr/lib/llvm-14/bin/sancov"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
  CMakeLists.txt:3 (find_package)


-- Configuring incomplete, errors occurred!


Andreas
--- End Message ---
--- Begin Message ---

fixed 1021857 1:14.0.6-7
thanks

I think the issue is fixed but if someone knows cmake well. please let 
me know :)


Cheers
S--- End Message ---

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 1021857 1:14.0.6-7
Bug #1021857 [llvm-14-dev] llvm-14-dev: CMake Error in LLVMExports.cmake: The 
imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but 
this file does not exist.
Bug #1022334 [llvm-14-dev] qtcreator: FTBFS: make[1]: *** [debian/rules:26: 
override_dh_auto_configure] Error 2
Bug #1022337 [llvm-14-dev] qt6-tools: FTBFS: The imported target "sancov" 
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022349 [llvm-14-dev] iwyu: FTBFS: The imported target "sancov" references 
the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022353 [llvm-14-dev] doxygen: FTBFS: The imported target "sancov" 
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022366 [llvm-14-dev] irony-mode: FTBFS: make: *** [debian/rules:8: 
binary] Error 2
Bug #1022381 [llvm-14-dev] cvise: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_configure] Error 2
Bug #1022409 [llvm-14-dev] ccls: FTBFS: make[1]: *** [debian/rules:18: 
override_dh_auto_configure] Error 2
Bug #1022414 [llvm-14-dev] bpftrace: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_configure] Error 2
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
Marked as fixed in versions llvm-toolchain-14/1:14.0.6-7.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
1022334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022334
1022337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022337
1022349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022349
1022353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022353
1022366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022366
1022381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022381
1022409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022409
1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021857: fixed

[Sylvestre Ledru]

fixed 1021857 1:14.0.6-7
thanks

I think the issue is fixed but if someone knows cmake well. please let 
me know :)


Cheers
S

Processed: OpenJDK 17 is now the default JRE

[Debian Bug Tracking System]

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

> severity  981938 serious
Bug #981938 [src:lombok-ast] lombok-ast: FTBFS with OpenJDK 17: module 
jdk.compiler does not "opens com.sun.tools.javac.processing" to unnamed module
Severity set to 'serious' from 'important'
> severity  982026 serious
Bug #982026 [src:guacamole-client] guacamole-client: FTBFS with OpenJDK 17 due 
to new compiler warning (primitive constructors marked for removal)
Severity set to 'serious' from 'important'
> severity  982526 serious
Bug #982526 [src:stockpile-clojure] stockpile-clojure: FTBFS with OpenJDK 17 
due to JDK detection error
Severity set to 'serious' from 'important'
> severity 1011129 serious
Bug #1011129 [src:gridengine] gridengine: FTBFS with OpenJDK 17 due to JDK 
detection error
Severity set to 'serious' from 'important'
> severity 1011134 serious
Bug #1011134 [src:geotranz] geotranz: FTBFS with OpenJDK 17 due to unsupported 
javac source/target level 6
Severity set to 'serious' from 'important'
> severity 1011156 serious
Bug #1011156 [src:picard-tools] picard-tools: FTBFS with OpenJDK 17 due to 
com.sun.javadoc removal
Severity set to 'serious' from 'important'
> severity 1011172 serious
Bug #1011172 [src:segment] segment: FTBFS with OpenJDK 17: Attempting to assign 
weaker access privileges to CharSequence.isEmpty()
Severity set to 'serious' from 'important'
> severity 1011181 serious
Bug #1011181 [src:libspring-java] libspring-java: FTBFS with OpenJDK 17 due to 
unsupported javac source/target level 6
Severity set to 'serious' from 'important'
> severity 1011532 serious
Bug #1011532 [src:icedtea-web] icedtea-web: FTBFS with OpenJDK 17 due to 
pack200 removal
Severity set to 'serious' from 'important'
> severity 1011534 serious
Bug #1011534 [src:opsin] opsin: FTBFS with OpenJDK 17 due to new javadoc layout
Severity set to 'serious' from 'important'
> severity 1011535 serious
Bug #1011535 [openjfx] openjfx: FTBFS with OpenJDK 17 due to javadoc errors
Severity set to 'serious' from 'important'
> severity 1011567 serious
Bug #1011567 [android-framework-23] android-framework-23: FTBFS with OpenJDK 17 
due to com.sun.javadoc removal
Severity set to 'serious' from 'important'
> severity 1011597 serious
Bug #1011597 [src:tiles] tiles: FTBFS with OpenJDK 17 due to an illegal 
reflective access in maven-autotag-plugin
Severity set to 'serious' from 'important'
> severity 1011598 serious
Bug #1011598 [src:insubstantial] insubstantial: FTBFS with OpenJDK 17 due to 
unsupported javac source/target level 6
Severity set to 'serious' from 'important'
> severity 1011600 serious
Bug #1011600 [src:opencensus-java] opencensus-java: FTBFS with OpenJDK 17 due 
to new compiler warnings
Severity set to 'serious' from 'important'
> severity 1011775 serious
Bug #1011775 [src:jamm] jamm: FTBFS with OpenJDK 17 due to an illegal 
reflective access during the tests
Severity set to 'serious' from 'important'
> severity 1011923 serious
Bug #1011923 [src:ice-builder-gradle] ice-builder-gradle: FTBFS with OpenJDK 17 
due to an illegal reflective access
Severity set to 'serious' from 'important'
> severity 1011924 serious
Bug #1011924 [src:capsule-nextflow] capsule-nextflow: FTBFS with OpenJDK 17 due 
to pack200 removal and ambiguous reference to FileSystems.newFileSystem()
Severity set to 'serious' from 'important'
> severity 1011977 serious
Bug #1011977 [src:htsjdk] FTBFS with OpenJDK 17: 5 failing tests
Severity set to 'serious' from 'important'
> severity 1012063 serious
Bug #1012063 [src:cofoja] cofoja: FTBFS with OpenJDK 17: module jdk.compiler 
does not export com.sun.tools.javac.processing to unnamed module
Severity set to 'serious' from 'important'
> severity 1012067 serious
Bug #1012067 [src:jss] jss: FTBFS with OpenJDK 17: no such provider SunJSSE
Severity set to 'serious' from 'important'
> severity 1012068 serious
Bug #1012068 [src:classmate] classmate: FTBFS with OpenJDK 17 due to test 
failures
Severity set to 'serious' from 'important'
> severity 1012070 serious
Bug #1012070 [src:simple-xml] simple-xml: FTBFS with OpenJDK 17 due to an 
illegal reflective access during the tests
Severity set to 'serious' from 'important'
> severity 1012072 serious
Bug #1012072 [src:libjose4j-java] libjose4j-java: FTBFS with OpenJDK 17 due to 
test failures
Severity set to 'serious' from 'important'
> severity 1012081 serious
Bug #1012081 [src:jboss-classfilewriter] jboss-classfilewriter: FTBFS with 
OpenJDK 17 due to test failures
Severity set to 'serious' from 'important'
> severity 1012093 serious
Bug #1012093 [src:ciftools-java] ciftools-java: FTBFS with OpenJDK 17 due to 
test failures
Severity set to 'serious' from 'important'
> severity 1012098 serious
Bug #1012098 [src:intervalstorej] intervalstorej: FTBFS with OpenJDK 17 due to 
test failures
Severity set to 'serious' from 'important'
> severity 1012099 serious
Bug #1012099 [src:scilab] scilab: FTBFS with OpenJDK 17: no scilocalization in 
java.library.path
Severity set to 'serious' from 

Bug#1019682: marked as done (schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 17:35:44 +
with message-id 
and subject line Bug#1019682: fixed in schleuder 4.0.3-6
has caused the Debian Bug report #1019682,
regarding schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:   
Failure/Error: expect(error).to be_empty
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.)


-- 
1019682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: schleuder
Version: 4.0.3-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild schleuder with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>   Failure/Error: expect(error).to be_empty
> expected 
> `":85:in
>  `require': cannot loa...or_ruby/rubygems/core_ext/kernel_require.rb>:85:in 
> `require'\n\tfrom bin/schleuder:12:in `'\n".empty?` to be truthy, got 
> false
>   # ./spec/schleuder/integration/filters_spec.rb:104:in `block (3 levels) 
> in '
>   # ./spec/spec_helper.rb:64:in `block (3 levels) in '
>   # ./spec/spec_helper.rb:63:in `block (2 levels) in '
> 
> Finished in 3 minutes 8.5 seconds (files took 0.86967 seconds to load)
> 543 examples, 21 failures
> 
> Failed examples:
> 
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:10]' 
> # user sends emails with different charsets works with simple_latin1
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:1]' 
> # user sends emails with different charsets works with japanese
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:5]' 
> # user sends emails with different charsets works with japanese_shift_jis
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:3]' 
> # user sends emails with different charsets works with 
> japanese_attachment_long_name
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:11]' 
> # user sends emails with different charsets works with simple_utf8
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:6]' 
> # user sends emails with different charsets works with ks_c_5601-1987
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:12]' 
> # user sends emails with different charsets works with 
> thunderbird-multi-alt-html
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:9]' 
> # user sends emails with different charsets works with simple_jpiso2022
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:2]' 
> # user sends emails with different charsets works with japanese_attachment
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:4]' 
> # user sends emails with different charsets works with japanese_iso_2022
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:8]' 
> # user sends emails with different charsets works with simple_jis
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:7]' 
> # user sends emails with different charsets works with signed_utf8
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:4]' # user sends 
> an encrypted message from thunderbird being encrypted+signed-mime
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:2]' # user sends 
> an encrypted message from thunderbird being encrypted-mime
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:1]' # user sends 
> an encrypted message from thunderbird being encrypted-inline
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:3]' # user sends 
> an encrypted message from thunderbird being encrypted+signed-inline
> rspec ./spec/schleuder/integration/receive_bounce_spec.rb:4 # a bounce 
> message is received from bounce example
> rspec ./spec/schleuder/integration/filters_spec.rb:55 # running filters 
> .fix_exchange_messages! accepts a valid plain-text message
> rspec ./spec/schleuder/integration/filters_spec.rb:32 # running filters 
> .fix_exchange_messages! accepts an invalid pgp/mime Exchange message
> rspec ./spec/schleuder/integration/filters_spec.rb:118 # running filters 
> .strip_html_from_alternative! does NOT strip HTML-part from 
> multipart/alternative-message that does NOT contain ascii-armored PGP-data
> rspec ./spec/schleuder/integration/filters_spec.rb:81 # running filters 
> .strip_html_from_alternative! strips HTML-part from 
> 

Processed: [bts-link] source package src:cypari2

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cypari2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1020456 (http://bugs.debian.org/1020456)
> # Bug title: cypari2 FTBFS with PARI 2.15.0
> #  * https://github.com/sagemath/cypari2/issues/122
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1020456 + fixed-upstream
Bug #1020456 [src:cypari2] cypari2 FTBFS with PARI 2.15.0
Added tag(s) fixed-upstream.
> usertags 1020456 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1020456 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: tagging 1019682

[Debian Bug Tracking System]

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

> tags 1019682 + pending
Bug #1019682 [src:schleuder] schleuder: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:   Failure/Error: expect(error).to be_empty
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: owfs: fails to build with php8.1

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libow-php7: misnomer
Bug #1003472 [src:owfs] owfs: fails to build with php8.1
Changed Bug title to 'libow-php7: misnomer' from 'owfs: fails to build with 
php8.1'.
> tags -1 - ftbfs
Bug #1003472 [src:owfs] libow-php7: misnomer
Removed tag(s) ftbfs.
> severity -1 minor
Bug #1003472 [src:owfs] libow-php7: misnomer
Severity set to 'minor' from 'serious'

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

Bug#1003472: owfs: fails to build with php8.1

[Bastian Germann]

Control: retitle -1 libow-php7: misnomer
Control: tags -1 - ftbfs
Control: severity -1 minor

The package should build with swig 4.1.0.
But with a build based on PHP 8, the libow-php7 package is a misnomer.

Bug#1018225: src:rust-rustls: fails to migrate to testing for too long: blocked by build dependency

[Jonas Smedegaard]

Quoting Peter Green (2022-10-31 03:39:28)
> > src:rust-rustls: fails to migrate to testing for too long: blocked by build 
> > dependency
> 
> Specifically rust-async-std has taken some time to package, because of the 
> large number
> of dependencies. There has been effort on this front both by the rust team 
> and by Jonas
> who currently packages rust stuff outside the rust team because he doesn't 
> like our
> packaging workflow.

Thanks, Peter.  For issues like this one by Release team and explicitly
described in subject as "blocked by build dependency" I believe however
than there is no need for explaining the cause (in _these_ bugreports -
it may make sense and be helpful to elaborate on the cause at a _root_
blocking bugreport).

> rust-async-std is now in unstable, however the autopkgtests for 
> rust-criterion and
> rust-async-std are failing. Jonas can you deal with these or do you want help?

Thanks, you offer is appreciated but (hopefully - should be confirmed
within few hours) there was no need for help this time.

Also, in future it is better if you post offers for help with the root
issue at the root bugreport rather than one of these leaf ones.


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1017223: marked as done (xrayutilities: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmp0f

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 16:11:37 +
with message-id 
and subject line Bug#1017223: fixed in xrayutilities 1.7.4-1
has caused the Debian Bug report #1017223,
regarding xrayutilities: FTBFS: distutils.errors.DistutilsError: Command 
'['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', 
'--no-deps', '-w', '/tmp/tmp0fa_exd4', '--quiet', 'h5py']' returned non-zero 
exit status 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.)


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

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.10
> I: pybuild base:239: python3.10 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
> SetuptoolsDeprecationWarning: setuptools.installer is deprecated. 
> Requirements should be satisfied by a PEP 517 installer.
>   warnings.warn(
> WARNING: The wheel package is not available.
> /usr/bin/python3.10: No module named pip
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in 
> fetch_build_egg
> subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmp0fa_exd4', '--quiet', 'h5py']' returned non-zero exit status 1.
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 155, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 152, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 147, in 
> _install_setup_requires
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 812, in 
> fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 771, 
> in resolve
> dist = best[req.key] = env.best_match(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1056, 
> in best_match
> return self.obtain(req, installer)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1068, 
> in obtain
> return installer(requirement)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 883, in 
> fetch_build_egg
> return fetch_build_egg(self, req)
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 84, in 
> fetch_build_egg
> raise DistutilsError(str(e)) from e
> distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 
> 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmp0fa_exd4', '--quiet', 'h5py']' returned non-zero exit status 1.
> E: pybuild pybuild:369: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:14: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/xrayutilities_1.7.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=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: xrayutilities
Source-Version: 

Bug#1022225: marked as done (libxml2: CVE-2022-40304: dict corruption caused by entity reference cycles)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 16:04:53 +
with message-id 
and subject line Bug#105: fixed in libxml2 2.9.14+dfsg-1.1
has caused the Debian Bug report #105,
regarding libxml2: CVE-2022-40304: dict corruption caused by entity reference 
cycles
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.)


-- 
105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.14+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libxml2.

CVE-2022-40304[0]:
| dict corruption caused by entity reference cycles

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-40304
https://www.cve.org/CVERecord?id=CVE-2022-40304
[1] 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/1b41ec4e9433b05bb0376be4725804c54ef1d80b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.14+dfsg-1.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Oct 2022 11:18:06 +0100
Source: libxml2
Architecture: source
Version: 2.9.14+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 104 105
Changes:
 libxml2 (2.9.14+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix integer overflows with XML_PARSE_HUGE (CVE-2022-40303)
 (Closes: #104)
   * Fix dict corruption caused by entity reference cycles (CVE-2022-40304)
 (Closes: #105)
Checksums-Sha1: 
 e57c6121b412173f773d960f5f51e0c174c1c633 3078 libxml2_2.9.14+dfsg-1.1.dsc
 7b8dab3e0e6a3176ab83be9cb69db76e2e8f3121 32820 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz
Checksums-Sha256: 
 ed31c56a4ecec3acbed5012fa5f1a2e23059d89eab938d5c66e809d9ae9bbf8d 3078 
libxml2_2.9.14+dfsg-1.1.dsc
 9a6d8cfcd1cab9ef2130c6e28e2d63c9eb789c3f6e8d25e2e702694f3049ef9a 32820 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz
Files: 
 50a41ce15477818c75e16a5b6972a9d4 3078 libs optional libxml2_2.9.14+dfsg-1.1.dsc
 ce64ba9c8243518c40acd49d75736713 32820 libs optional 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNeUBRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E3N4P/iWKWh72yCXaOPvR0N+zNgrK68+F4U9I
G4o1i7IDTOIh4E08pgsxF5iSPCTirf9XfeEvLl39R/+JjCdkn8OmYEhFqzOiqxaV
G15nqFowHuhOsoi97Js0UXyj+PoMOODCG5tc5Kst019UOJA6hq/8qQGcof8G8t/l
1uluQyVNEU8o5GQTKIp46LEJO20jVC6sDCRRnaevVsPYq45kddoUcAfHhZ8YgQ8t
yZXvfCPVJhwIfdoTarFWL5VJZjQ2rBxsAVOP6PdUtiahz/QBZaM9pZyBx6QyoNuu
SWI7qft9kBVkoDAp8Cm4+/jng+DGVh01NHA6WdFyevaOWNFhJZIJOoYMKD3joLjI
8gXQhr5dulHp0ln0HLeOJanqY922Xwh0BVISTRZaW651MewIBC8/zOOHYaXgOgDP
1FeWvF/HOVxtX0oUB2pdU4siLHugBChKHL3ZojDN4o0I7VAXvclw3UOgdIC7bGy6
ZePgHIE0wyyHxr4Jj+omqTmG08zcTCpZZtHGONnCMsvxilTZKtX/1nDQumfzDz9K
ykT83wDNExRFjgIrxuFFKN7C1X2WnM0kTMoriDOa6SzkXs2U402kAluezaZqPy0j
MujIR0vDc6dfbnFGYaEKfj+dZokSBAnLI8eVL/uIcH065fTkQh9fZDP+9PhIcRj3
XZdtC8LYg+EM
=8gEE
-END PGP SIGNATURE End Message ---

Bug#1022224: marked as done (libxml2: CVE-2022-40303: Integer overflows with XML_PARSE_HUGE)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 16:04:53 +
with message-id 
and subject line Bug#104: fixed in libxml2 2.9.14+dfsg-1.1
has caused the Debian Bug report #104,
regarding libxml2: CVE-2022-40303: Integer overflows with XML_PARSE_HUGE
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.)


-- 
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.14+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libxml2.

CVE-2022-40303[0]:
| Integer overflows with XML_PARSE_HUGE

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-40303
https://www.cve.org/CVERecord?id=CVE-2022-40303
[1] 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/c846986356fc149915a74972bf198abc266bc2c0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.14+dfsg-1.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Oct 2022 11:18:06 +0100
Source: libxml2
Architecture: source
Version: 2.9.14+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 104 105
Changes:
 libxml2 (2.9.14+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix integer overflows with XML_PARSE_HUGE (CVE-2022-40303)
 (Closes: #104)
   * Fix dict corruption caused by entity reference cycles (CVE-2022-40304)
 (Closes: #105)
Checksums-Sha1: 
 e57c6121b412173f773d960f5f51e0c174c1c633 3078 libxml2_2.9.14+dfsg-1.1.dsc
 7b8dab3e0e6a3176ab83be9cb69db76e2e8f3121 32820 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz
Checksums-Sha256: 
 ed31c56a4ecec3acbed5012fa5f1a2e23059d89eab938d5c66e809d9ae9bbf8d 3078 
libxml2_2.9.14+dfsg-1.1.dsc
 9a6d8cfcd1cab9ef2130c6e28e2d63c9eb789c3f6e8d25e2e702694f3049ef9a 32820 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz
Files: 
 50a41ce15477818c75e16a5b6972a9d4 3078 libs optional libxml2_2.9.14+dfsg-1.1.dsc
 ce64ba9c8243518c40acd49d75736713 32820 libs optional 
libxml2_2.9.14+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNeUBRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E3N4P/iWKWh72yCXaOPvR0N+zNgrK68+F4U9I
G4o1i7IDTOIh4E08pgsxF5iSPCTirf9XfeEvLl39R/+JjCdkn8OmYEhFqzOiqxaV
G15nqFowHuhOsoi97Js0UXyj+PoMOODCG5tc5Kst019UOJA6hq/8qQGcof8G8t/l
1uluQyVNEU8o5GQTKIp46LEJO20jVC6sDCRRnaevVsPYq45kddoUcAfHhZ8YgQ8t
yZXvfCPVJhwIfdoTarFWL5VJZjQ2rBxsAVOP6PdUtiahz/QBZaM9pZyBx6QyoNuu
SWI7qft9kBVkoDAp8Cm4+/jng+DGVh01NHA6WdFyevaOWNFhJZIJOoYMKD3joLjI
8gXQhr5dulHp0ln0HLeOJanqY922Xwh0BVISTRZaW651MewIBC8/zOOHYaXgOgDP
1FeWvF/HOVxtX0oUB2pdU4siLHugBChKHL3ZojDN4o0I7VAXvclw3UOgdIC7bGy6
ZePgHIE0wyyHxr4Jj+omqTmG08zcTCpZZtHGONnCMsvxilTZKtX/1nDQumfzDz9K
ykT83wDNExRFjgIrxuFFKN7C1X2WnM0kTMoriDOa6SzkXs2U402kAluezaZqPy0j
MujIR0vDc6dfbnFGYaEKfj+dZokSBAnLI8eVL/uIcH065fTkQh9fZDP+9PhIcRj3
XZdtC8LYg+EM
=8gEE
-END PGP SIGNATURE End Message ---

Bug#1022333: marked as done (zookeeper: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_build-indep] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 15:40:59 +
with message-id 
and subject line Bug#1022333: fixed in zookeeper 3.8.0-9
has caused the Debian Bug report #1022333,
regarding zookeeper: FTBFS: make[1]: *** [debian/rules:20: 
override_dh_auto_build-indep] Error 25
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.)


-- 
1022333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Version: 3.8.0-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- package javadoc:jar javadoc:aggregate -Pfull-build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -Pfull-build -DskipTests -Dnotimestamp=true 
> -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache ZooKeeper   
> [pom]
> [INFO] Apache ZooKeeper - Documentation   
> [pom]
> [INFO] Apache ZooKeeper - Jute
> [jar]
> [INFO] Apache ZooKeeper - Server  
> [jar]
> [INFO] Apache ZooKeeper - Metrics Providers   
> [pom]
> [INFO] Apache ZooKeeper - Client  
> [pom]
> [INFO] Apache ZooKeeper - Client - C  
> [pom]
> [INFO] Apache ZooKeeper - Recipes 
> [pom]
> [INFO] Apache ZooKeeper - Recipes - Election  
> [jar]
> [INFO] Apache ZooKeeper - Recipes - Lock  
> [jar]
> [INFO] Apache ZooKeeper - Recipes - Queue 
> [jar]
> [INFO] Apache ZooKeeper - Assembly
> [pom]
> [INFO] Apache ZooKeeper - Compatibility Tests 
> [pom]
> [INFO] Apache ZooKeeper - Contrib 
> [pom]
> [INFO] Apache ZooKeeper - Contrib - Loggraph  
> [jar]
> [INFO] Apache ZooKeeper - Contrib - ZooInspector  
> [jar]
> [INFO] Apache ZooKeeper - Tests   
> [jar]
> [WARNING] The artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 
> has been relocated to org.apache.maven.plugins:maven-antrun-plugin:jar:1.8
> [INFO] 
> [INFO] < org.apache.zookeeper:parent 
> >-
> [INFO] Building Apache ZooKeeper 3.8.0   
> [1/17]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-antrun-plugin:1.8:run (set-hostname-property) @ parent ---
> [INFO] Executing tasks
> 
> main:
> [INFO] Executed tasks
> [INFO] 
> [INFO] --- maven-jar-plugin:3.3.0:test-jar (Jar Tests Package) @ parent ---
> [INFO] Skipping packaging of the test-jar
> [INFO] 
> [INFO] >>> maven-source-plugin:3.2.1:jar (attach-sources) > generate-sources 
> @ parent >>>
> [INFO] 
> [INFO] --- maven-antrun-plugin:1.8:run (set-hostname-property) @ parent ---
> [INFO] Executing tasks
> 
> main:
> [INFO] Executed tasks
> [INFO] 
> [INFO] <<< maven-source-plugin:3.2.1:jar (attach-sources) < generate-sources 
> @ parent <<<
> [INFO] 
> [INFO] 
> [INFO] --- maven-source-plugin:3.2.1:jar (attach-sources) @ parent ---
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ parent ---
> [INFO] Not executing Javadoc as the project is not a Java classpath-capable 
> package
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.0.1:jar (default-cli) @ parent ---
> [INFO] Not executing Javadoc as the project is not a Java classpath-capable 
> package
> [INFO] 
> [INFO] < org.apache.zookeeper:zookeeper-docs 
> >-
> [INFO] Building Apache ZooKeeper - 

Bug#1023031: marked as done (rust-async-std: autopkgtest failure.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 15:39:12 +
with message-id 
and subject line Bug#1023031: fixed in rust-async-std 1.12.0-6
has caused the Debian Bug report #1023031,
regarding rust-async-std: autopkgtest failure.
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.)


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

Package: rust-async-std
Version: 1.12.0-5
Severity: serious

The autopkgtest for rust-async-std is failing and preventing it's migration to 
testing.


error[E0425]: cannot find function `block_on` in module `task`
   --> src/io/read/take.rs:231:15
|
231 | task::block_on(async move {
|    not found in `task`
|
help: consider importing one of these items
|
223 | use async_io::block_on;
|
223 | use futures::executor::block_on;
|

error[E0425]: cannot find function `block_on` in module `crate::task`
   --> src/io/read/mod.rs:394:22
|
394 | crate::task::block_on(async {
|   not found in `crate::task`
|
help: consider importing one of these items
|
389 | use async_io::block_on;
|
389 | use futures::executor::block_on;
|

For more information about this error, try `rustc --explain E0425`.
error: could not compile `async-std` due to 2 previous errors
--- End Message ---
--- Begin Message ---
Source: rust-async-std
Source-Version: 1.12.0-6
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-async-std package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 15:43:34 +0100
Source: rust-async-std
Architecture: source
Version: 1.12.0-6
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1023031
Changes:
 rust-async-std (1.12.0-6) unstable; urgency=medium
 .
   * fix have autopkgtests skip test io_timeout
   * fix set X-Cargo-Crate: async_std;
 closes: bug#1023031, thanks to Peter Green
Checksums-Sha1:
 814b4bb3a865cdc94b60479949f73f5089fe80cd 3295 rust-async-std_1.12.0-6.dsc
 b070f5dd1ef502101b01730e7ee63db405aa40be 12676 
rust-async-std_1.12.0-6.debian.tar.xz
 e175faafaa8a45be75ac27071960541aba769709 12856 
rust-async-std_1.12.0-6_amd64.buildinfo
Checksums-Sha256:
 c5ea3994bf2c199dbff3e7b42c054e6b4b9e93190f5774e9a2cbf1483e6f6712 3295 
rust-async-std_1.12.0-6.dsc
 f61c975d3e565749170250755f3ef476434dca7742a1448e5c0fdac8f4fa6bf4 12676 
rust-async-std_1.12.0-6.debian.tar.xz
 5182ed16796a6dead607c828f41b42b77c898d197ce0ed3fefb4b62e00dc10ad 12856 
rust-async-std_1.12.0-6_amd64.buildinfo
Files:
 341509277960ffd7eea8c5881bedbe06 3295 rust optional rust-async-std_1.12.0-6.dsc
 ca24de695888397221b1593de5718535 12676 rust optional 
rust-async-std_1.12.0-6.debian.tar.xz
 8fb4b84f5c1f0e0cf93269bf7008182c 12856 rust optional 
rust-async-std_1.12.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNf4hQACgkQLHwxRsGg
ASEVag/9F3JOE0Fwkb8AZ34Qe7JHRKlpV5e/EQcYJIaYEqgrWHFW53sJ6XiDxsGn
drU+Ra+n1pHxsuvyOZ71NIofkYnRJC3P/kMPZuqRsrXpB0p1P2HqqKILnc1lJcRp
pYISmhkzeEz107bSAPgU4OJlGGMOOAZtLWHR7Hs+ttGFBx0djvajJnHxogHewQ2P
2WFVyLkGOsf9HTkOnztqMKzU5JXD+l5uPreKaUouLBPyUmMOTxexCvWHMNsnTE7O
BeAOBXc44k8Pwd517vGPwrff2ZIUtTBIdYJHjm0Xpghepw4jBY/18J9Bkw2BrRMG
R1lgy6aO4R8WawRO1BdXiqDVmqYIf+V2MIygGYNwmIy/V5dAmwR8QhK+bD62FyiD
BmSKi8DKqDjpDa/gMjTteSpZLptK3NF5t0H5KyFjdsLzm3EhjJSzLp71ztLqZQ4u
NHM5O6iQF+l2mC4tWKpGCccPFVPvNC9GiZOGPaV2cSL0VLvCPJYDyrhIeTKl7F9+
gfF+IHMBgKfLR46pdTRGPclTuexvTnXCfNU9k2suhX8XfcIea1Vvr3cuRFfQUbXM
z0mZhsMCklGWOd/W/mpDXd/2qB/si4p5p8ADNgQMPAdXCaKc+ipS8OgAVTFp2TJN
DWSxQhUD2Wm0okf2b59fj4RnQdSiDDbdeNRyC7BV8Ucmsybrp34=
=BMBt
-END PGP SIGNATURE End Message ---

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

[Vincent Lefevre]

Hi,

On 2022-10-30 06:31:27 -0700, Sean Whitton wrote:
> I've backported a couple of patches from upstream related to native
> compilation, now, so would you be able to test again with the latest
> upload?  Thanks.

If you mean 1:28.2+1-3, I still got the same issue. But it seems
that after a reboot, the problem no longer occurs (after removing
the .emacs.d directory). Was a reboot needed?

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

Bug#1023204: sssd-ipa: sssd fails to start due to broken dependency

[Michael Stone]

Package: sssd-ipa
Version: 2.7.4-1+b1
Severity: critical
Justification: breaks the whole system

After upgrade of samba-libs syslog has messages like

... sssd[448823]: /usr/libexec/sssd/sssd_pac: error while loading shared 
libraries: libndr.so.2: cannot open shared object file: No such file or 
directory

/usr/lib/x86_64-linux-gnu/sssd/libsss_ipa.so seems to have a dependency on
libndr.so.2 while current samba-libs only provides libndr.so.3.

As a result, there is no uid/gid resolution, etc, for all centrally managed
users, making the system unusable for non-local accounts.

This may be an issue with the way the dependency in the way samba is generating
library dependencies deserving of a separate bug, but for now sssd is broken
until recompiled against latest samba library. The dependency on samba-libs
should probably be a strict version rather than a >= version.

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

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

Versions of packages sssd-ipa depends on:
ii  libc6 2.35-4
ii  libdhash1 0.6.2-1
ii  libipa-hbac0  2.7.4-1+b1
ii  libldap-2.5-0 2.5.13+dfsg-2+b1
ii  libldb2   2:2.6.1+samba4.17.2-3
ii  libpopt0  1.19+dfsg-1
ii  libselinux1   3.4-1+b2
ii  libsemanage2  3.4-1+b2
ii  libsss-idmap0 2.7.4-1+b1
ii  libtalloc22.3.4-2
ii  libtevent00.13.0-2
ii  samba-libs2:4.17.2+dfsg-3
ii  sssd-ad-common2.7.4-1+b1
ii  sssd-common   2.7.4-1+b1
ii  sssd-krb5-common  2.7.4-1+b1

sssd-ipa recommends no packages.

sssd-ipa suggests no packages.

-- no debconf information

Processed: bug 1007026 is forwarded to https://github.com/rustwasm/weedle/issues/51

[Debian Bug Tracking System]

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

> forwarded 1007026 https://github.com/rustwasm/weedle/issues/51
Bug #1007026 [rust-weedle] rust-weedle - needs nom 5
Set Bug forwarded-to-address to 'https://github.com/rustwasm/weedle/issues/51'.
> thanks
Stopping processing here.

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

Processed: Re: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e
Bug #1019995 [src:supercollider] supercollider: FTBFS: sndfile.h:356:33: error: 
conflicting declaration ‘typedef struct sf_private_tag SNDFILE’
Set Bug forwarded-to-address to 
'https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e'.

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

Bug#1019995: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’

[s3v]

Control: forwarded -1 
https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e
thanks

Dear Maintainer,

After applying upstream commit, I was able to build your package in a sid 
chroot environment.

Kind Regards

Bug#1003479: marked as done (swig: Missing support for php8.1)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 13:06:51 +
with message-id 
and subject line Bug#1003479: fixed in swig 4.1.0-0.1
has caused the Debian Bug report #1003479,
regarding swig: Missing support for php8.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.)


-- 
1003479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swig
Version: 4.0.2-1
Severity: important

  php8.1 is entering sid but swig generates incompatible source files
(with the -php7 flag as there are no -php8 flag for now)
The result is that some packages FTBFS due to this (see owfs, #1003472 for
example).

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811#200
swig 4.2.0 should fix the problem (I did not check myself).

  Regards,
   Vincent

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swig depends on:
ii  swig4.0  4.0.2-1

swig recommends no packages.

Versions of packages swig suggests:
pn  swig-doc   
pn  swig-examples  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: swig
Source-Version: 4.1.0-0.1
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated swig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 13:05:40 +0100
Source: swig
Architecture: source
Version: 4.1.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Torsten Landschoff 
Changed-By: Bastian Germann 
Closes: 1003479
Changes:
 swig (4.1.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * d/copyright: Represent actual source URL
   * Mangle pre-release versions for correct ordering
   * New upstream version 4.1.0 (Closes: #1003479)
   * Drop upstream patches
 .
   [ Debian Janitor ]
   * Apply multi-arch hints. + swig4.0-examples: Add Multi-Arch: foreign.
Checksums-Sha1:
 e7e93d7b540142ec97a776bd673e2c66feb1 2019 swig_4.1.0-0.1.dsc
 8ed58569e461493aad4e33750eb7f978aff16ca0 8600226 swig_4.1.0.orig.tar.gz
 b4f08f5e75a980dff7d5bc8dab2b07808a8d0337 20024 swig_4.1.0-0.1.debian.tar.xz
 91eccafe7bfebd112d94d3828c1f4fb1818944c4 6178 swig_4.1.0-0.1_source.buildinfo
Checksums-Sha256:
 13c5df50796dd1289e0d4372ca0f51fb62eff3ecaf518de644150e33b43a1ca3 2019 
swig_4.1.0-0.1.dsc
 d6a9a8094e78f7cfb6f80a73cc271e1fe388c8638ed22668622c2c646df5bb3d 8600226 
swig_4.1.0.orig.tar.gz
 abf58374fd3464d12505db770b78b823493dcb38b85beb2ca2ac13b29d87659d 20024 
swig_4.1.0-0.1.debian.tar.xz
 9db541c08bd6e990c77f40300e3c6ea02aab7f4e7daea8041ee93de79cecf4a2 6178 
swig_4.1.0-0.1_source.buildinfo
Files:
 623c06bb010e73352d1fe994e35c881b 2019 interpreters optional swig_4.1.0-0.1.dsc
 baac03a66f3194e5399d4c71d34df1e2 8600226 interpreters optional 
swig_4.1.0.orig.tar.gz
 a9bab819db226a617d43e95376ac8069 20024 interpreters optional 
swig_4.1.0-0.1.debian.tar.xz
 7b28536189dcb936707c62ea66cce57b 6178 interpreters optional 
swig_4.1.0-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNfw/QQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFP5RC/9aLUHCkXA88gQDYialP3wlOSA34jvnemH3
3gUvQ9eLyCk+bCalNzSUc8x5r1rcqq47krHsldu3sxFwtaHltbkbNEw2vk3pVAwq
mYARgeAxf9Pote2UzUWIKuHu5D5lTcdMkYJXerhyUp4+uW/53YFTpMwFZh6Y96dC
jHDbHWe+Jx1wVtU+zjpBxYrKmBwG5xLFa/JcC6DizRg2O7rM65DcX+znvBaqEfTX
ysJ4DZZYLw33k2w/MAJCpHGutT+WAhgPD3n6KzRr3jOZ7pfnl0WcxV+Z4XVqdrq6

Bug#1003479: swig: LowNMU 4.1.0-0.1

[Bastian Germann]

I have uploaded the new version as NMU 4.1.0-0.1.
The source is also pushed to the git repo.

Bug#1022450: marked as done (logbook: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 12:49:14 +
with message-id 
and subject line Bug#1022450: fixed in logbook 1.5.3-5.1
has caused the Debian Bug report #1022450,
regarding logbook: FTBFS: distutils.errors.DistutilsClassError: command class 
 must subclass Command
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.)


-- 
1022450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logbook
Version: 1.5.3-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> cython3 logbook/_speedups.pyx
> python3 setup.py build_ext --inplace
> /<>/setup.py:60: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of 
> dash-separated 'upload-dir' will not be supported in future versions. Please 
> use the underscore name 'upload_dir' instead
>   warnings.warn(
> Traceback (most recent call last):
>   File "/<>/setup.py", line 229, in 
> run_setup(True)
>   File "/<>/setup.py", line 187, in run_setup
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  '__main__.ve_build_ext'> must subclass Command
> make[2]: *** [Makefile:32: logbook/_speedups.so] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/logbook_1.5.3-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=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: logbook
Source-Version: 1.5.3-5.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated logbook package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

Processed: reopening 996130, reopening 995660, reopening 1023136, reopening 1023138, reopening 1023137

[Debian Bug Tracking System]

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

> reopen 996130
Bug #996130 {Done: Tobias Frost } [src:clickhouse] clickhouse 
FTBFS with gcc 11
'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 clickhouse/18.16.1+ds-7.3~exp1.
> reopen 995660
Bug #995660 {Done: Tobias Frost } [src:clickhouse] clickhouse: 
FTBFS with OpenSSL 3.0
'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 clickhouse/18.16.1+ds-7.3~exp1.
> reopen 1023136
Bug #1023136 {Done: Tobias Frost } [src:clickhouse] 
clickhouse: FTBFS on arch but amd64 arm64 ppc64el.
'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 clickhouse/18.16.1+ds-7.3~exp2.
> reopen 1023138
Bug #1023138 {Done: Tobias Frost } [src:clickhouse] 
clickhouse: server aborts when it cannot set core file size.
'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 clickhouse/18.16.1+ds-7.3~exp3.
> reopen 1023137
Bug #1023137 {Done: Tobias Frost } [src:clickhouse] 
clickhouse: FTBFS when building from packaging (e.g salsa) git repository.
'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 clickhouse/18.16.1+ds-7.3~exp2.
> thanks
Stopping processing here.

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

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

On 2022-10-31 13:09:31 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: grave
> Justification: renders package unusable
> 
> (Setting to grave because Bluetooth is a major component.)
> 
> Bluetooth no longer works at all.

Bluetooth works again after downgrading the kernel to 6.0.3-1.

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

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Package: src:linux
Version: 6.0.5-1
Severity: grave
Justification: renders package unusable

(Setting to grave because Bluetooth is a major component.)

Bluetooth no longer works at all.

zira:~> journalctl -b -g bluetooth
Oct 31 12:55:16 zira kernel: Bluetooth: Core ver 2.22
Oct 31 12:55:16 zira kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 31 12:55:16 zira kernel: Bluetooth: HCI device and connection manager 
initialized
Oct 31 12:55:16 zira kernel: Bluetooth: HCI socket layer initialized
Oct 31 12:55:16 zira kernel: Bluetooth: L2CAP socket layer initialized
Oct 31 12:55:16 zira kernel: Bluetooth: SCO socket layer initialized
Oct 31 12:55:17 zira systemd[1]: Starting Bluetooth service...
Oct 31 12:55:17 zira systemd[795]: ConfigurationDirectory 'bluetooth' already 
exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 
555)
Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth daemon 5.65
Oct 31 12:55:17 zira systemd[1]: Started Bluetooth service.
Oct 31 12:55:17 zira systemd[1]: Reached target Bluetooth Support.
Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth management interface 1.22 
initialized
Oct 31 12:55:17 zira dbus-daemon[801]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' 
requested by ':1.2' (uid=0 pid=795 comm="/usr/libexec/bluetooth/bluetoothd")
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP filters: protocol multicast
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP socket layer initialized
Oct 31 12:55:17 zira NetworkManager[950]:   [1667217317.6273] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.40.2/libnm-device-plugin-bluetooth.so)
Oct 31 12:55:19 zira kernel: Bluetooth: hci0: Reading Intel version command 
failed (-110)
Oct 31 12:55:19 zira kernel: Bluetooth: hci0: command 0xfc05 tx timeout

With the 6.0.3-1 kernel version, I got:

Oct 31 11:17:59 zira kernel: Bluetooth: Core ver 2.22
Oct 31 11:17:59 zira kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 31 11:17:59 zira kernel: Bluetooth: HCI device and connection manager 
initialized
Oct 31 11:17:59 zira kernel: Bluetooth: HCI socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: L2CAP socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: SCO socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 
2 week 3 2013
Oct 31 11:17:59 zira kernel: bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 31 11:17:59 zira systemd[1]: Starting Bluetooth service...
[...]

So it appears that the 6.0.5-1 kernel version can't load the firmware.

-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.5-1 (2022-10-28)

** Command line:
BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/crypt--lvm-root ro quiet 
systemd.swap=no

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
qrtr
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
cpufreq_conservative
cpufreq_userspace
cpufreq_ondemand
cpufreq_powersave
bnep
nf_tables
libcrc32c
nfnetlink
nvidia_drm(POE)
drm_kms_helper
btusb
intel_rapl_msr
intel_rapl_common
iwlmvm
nvidia_modeset(POE)
btrtl
btbcm
btintel
btmtk
snd_ctl_led
mac80211
snd_hda_codec_realtek
bluetooth
snd_hda_codec_generic
snd_hda_codec_hdmi
ledtrig_audio
x86_pkg_temp_thermal
snd_hda_intel
intel_powerclamp
snd_intel_dspcfg
snd_intel_sdw_acpi
coretemp
libarc4
snd_hda_codec
uvcvideo
jitterentropy_rng
rapl
nvidia(POE)
iwlwifi
mei_wdt
snd_hda_core
intel_cstate
videobuf2_vmalloc
videobuf2_memops
binfmt_misc
mei_hdcp
snd_hwdep
videobuf2_v4l2
sha512_ssse3
intel_uncore
sha512_generic
cfg80211
videobuf2_common
snd_pcm
drbg
hp_wmi
videodev
joydev
ansi_cprng
platform_profile
pcspkr
snd_timer
iTCO_wdt
sparse_keymap
intel_pmc_bxt
serio_raw
mxm_wmi
ecdh_generic
iTCO_vendor_support
snd
wmi_bmof
at24
hp_accel
ipmi_devintf
watchdog
mc
rfkill
ecc
apple_mfi_fastcharge
evdev
lis3lv02d
ipmi_msghandler
soundcore
mei_me
tpm_infineon
ac
mei
sg
button
parport_pc
ppdev
drm
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
t10_pi

Bug#1006049: marked as done (botch: FTBFS: ocamlfind: Package `dose3.doseparse' not found)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 12:05:50 +
with message-id 
and subject line Bug#1006049: fixed in botch 0.24-1
has caused the Debian Bug report #1006049,
regarding botch: FTBFS: ocamlfind: Package `dose3.doseparse' not found
to be marked as done.

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

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


-- 
1006049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botch
Version: 0.23-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> atdgen -j -j-std datatypes.atd
> atdgen -t datatypes.atd
> OCAMLPATH=/<>/dose/_build ocamlbuild -lflags 
> -runtime-variant,_pic -classic-display -use-ocamlfind -cflags "-w +a-4-9-24" 
> create-graph.native print-stats.native bin2src.native src2bin.native 
> build-fixpoint.native clean-repository.native buildgraph2srcgraph.native 
> annotate-strong.native partial-order.native find-fvs.native 
> collapse-srcgraph.native optuniv.native calculate-fas.native 
> buildcheck-more-problems.native distcheck-more-problems.native
> ocamlfind ocamldep -package dose3 -package dose3.doseparse -package 
> dose3.algo -package atdgen -package xmlm -package extlib -pp cppo -package 
> parmap -modules create-graph.ml > create-graph.ml.depends
> + ocamlfind ocamldep -package dose3 -package dose3.doseparse -package 
> dose3.algo -package atdgen -package xmlm -package extlib -pp cppo -package 
> parmap -modules create-graph.ml > create-graph.ml.depends
> ocamlfind: Package `dose3.doseparse' not found
> Command exited with code 2.
> make[2]: *** [Makefile:74: native] Error 10


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/botch_0.23-1_unstable.log

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: botch
Source-Version: 0.24-1
Done: Johannes Schauer Marin Rodrigues 

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

Debian distribution maintenance software
pp.
Johannes Schauer Marin Rodrigues  (supplier of updated botch 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 12:51:07 +0100
Source: botch
Architecture: source
Version: 0.24-1
Distribution: unstable
Urgency: medium
Maintainer: Johannes Schauer Marin Rodrigues 
Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 1006049
Changes:
 botch (0.24-1) unstable; urgency=medium
 .
   * New upstream release
  - port to dose3 7.0.0 (closes: #1006049)
   * debian/watch: bump version to 4
   * debian/control: bump dh version to 13
   * debian/control: bump Standards-Version to 4.5.1
   * debian/botch.install: list manpages
   * fix my name
   * drop patches
   * remove parmap and parany
   * add patch fixing Bi_outbuf -> Buffer
   * patch json test formatting
   * debian/tests: remove --jobs
   * debian/source/lintian-overrides: override some lintian false-positives
   * debian/salsa-ci.yml: disable crossbuilding
Checksums-Sha1:
 5cd9efd81ea3c5f906469c741384a8373cba39a7 3014 botch_0.24-1.dsc
 14b126d31178cbecc2903025f9773dc5985729b7 52074108 botch_0.24.orig.tar.xz
 3e1b1d04800cf636f79ee23f767563d3f7ea0c3e 833 botch_0.24.orig.tar.xz.asc
 06f1a6588d1ac3e6cf5d482c1902de888c44ab77 19208 botch_0.24-1.debian.tar.xz
Checksums-Sha256:
 6caa1d6389b1a71d260e93866b5fa248532b8d2911cad5f084c2ce2de989655c 3014 
botch_0.24-1.dsc
 36876889e553af1b9d9a03106f7b1d9a2009fd6db5cc5fa3b748c09060b7453c 52074108 
botch_0.24.orig.tar.xz
 

Processed: Bug#1023040 marked as pending in nbconvert

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023040 [src:nbconvert] nbconvert: downloads artifacts during build
Ignoring request to alter tags of bug #1023040 to the same tags previously set

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

Bug#1023040: marked as pending in nbconvert

[Julien Puydt]

Control: tag -1 pending

Hello,

Bug #1023040 in nbconvert 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/python-team/packages/nbconvert/-/commit/b4c941de7855087e9ee2ec5488428432bbd7f61f


Add 0008-dont-use-intersphinx-during-build.patch

Building documentation with Sphinx uses intersphinx by default, which
downloads data from the internet. This isn't allowed during Debian
binary builds.

Closes: #1023040


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023040

Bug#1004285: [DAViCal-devel] Bug#1004285: fixed in davical 1.1.11-1

[Benno Overeinder]

Dear Florian,

On 18/10/2022 13:01, Florian Schlichting wrote:

On Mon, Oct 10, 2022 at 12:46:57PM +0200, Benno Overeinder wrote:

Unfortunately the problem persists after updating to davical 1.1.11-1. I see
the same messages in the Apache2 error.log as previously reported.


looking at your error log from February, I think the crucial part is

Fri Feb 18 21:14:58.430957 2022] [php:notice] [pid 49689] [client
192.168.1.1:64517] davical: BUG: :DAViCal Fatal Error: [0A000]
SQLSTATE[0A000]: Feature not supported: 7 ERROR:  set-returning
functions are not allowed in CASE...

This sounds like https://gitlab.com/davical-project/davical/-/issues/171

The important bit is to make sure that update-davical-database is run
from the new package, and that it has replaced the expand_memberships
function to not contain a CASE statement any more.


Thanks for your email.  I updated to php8.1 again and ran the 
update-davical-database script, and then restarted apache2.  At first I 
saw the same errors, but after rebooting the server, DAViCal worked 
perfectly as before.  Maybe some sticky state in one of the components 
(postgresql?).


Thanks again for your support and maintaining the davical package.

Cheers,

-- Benno

Bug#1023026: marked as done (gavodachs: Fails it autopkgtest)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 10:50:49 +
with message-id 
and subject line Bug#1023026: fixed in gavodachs 2.6+dfsg-2
has caused the Debian Bug report #1023026,
regarding gavodachs: Fails it autopkgtest
to be marked as done.

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

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


-- 
1023026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gavodachs
Version: 2.6+dfsg-1.1
Severity: serious
X-Debbugs-Cc: oleb...@debian.org

Hi

gavodachs fails it's autopkgtest with permission errors:

| createuser: error: creation of new role failed: ERROR:  role "dachsroot" 
already exists
| *** Error: While executing DB query:
|
|  CREATE OR REPLACE FUNCTION q3c_join_symmetric(
|   leftra double precision, leftdec double 
precision,
|   rightra double precision, rightdec double precision,
|   radius double precision) RETURNS boolean AS '
| SELECT (
|(   
|   ((q3c_ang2ipix($3,$4)>=(q3c_nearby_it($1,$2,$5,0))) AND 
(q3c_ang2ipix($3,$4)<=(q3c_nearby_it($1,$2,$5,1
|OR ((q3c_ang2ipix($3,$4)>=(q3c_nearby_it($1,$2,$5,2))) AND 
(q3c_ang2ipix($3,$4)<=(q3c_nearby_it($1,$2,$5,3
|OR ((q3c_ang2ipix($3,$4)>=(q3c_nearby_it($1,$2,$5,4))) AND 
(q3c_ang2ipix($3,$4)<=(q3c_nearby_it($1,$2,$5,5
|OR ((q3c_ang2ipix($3,$4)>=(q3c_nearby_it($1,$2,$5,6))) AND 
(q3c_ang2ipix($3,$4)<=(q3c_nearby_it($1,$2,$5,7
|) AND   
|(
|   ((q3c_ang2ipix($1,$2)>=(q3c_nearby_it($3,$4,$5,0))) AND 
(q3c_ang2ipix($1,$2)<=(q3c_nearby_it($3,$4,$5,1
|OR ((q3c_ang2ipix($1,$2)>=(q3c_nearby_it($3,$4,$5,2))) AND 
(q3c_ang2ipix($1,$2)<=(q3c_nearby_it($3,$4,$5,3
|OR ((q3c_ang2ipix($1,$2)>=(q3c_nearby_it($3,$4,$5,4))) AND 
(q3c_ang2ipix($1,$2)<=(q3c_nearby_it($3,$4,$5,5
|OR ((q3c_ang2ipix($1,$2)>=(q3c_nearby_it($3,$4,$5,6))) AND 
(q3c_ang2ipix($1,$2)<=(q3c_nearby_it($3,$4,$5,7
|)   
|)
|AND q3c_sindist($1,$2,$3,$4)https://ci.debian.net/packages/g/gavodachs/testing/amd64/


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: gavodachs
Source-Version: 2.6+dfsg-2
Done: Markus Demleitner 

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

Debian distribution maintenance software
pp.
Markus Demleitner  (supplier of updated gavodachs 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 10:47:19 +0100
Source: gavodachs
Architecture: source
Version: 2.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Markus Demleitner 
Closes: 1023026
Changes:
 gavodachs (2.6+dfsg-2) unstable; urgency=medium
 .
   * dachs init now grants gavoadmin create privileges on the public schema.
 (Closes: #1023026)
Checksums-Sha1:
 4ba3c466b6a40e49809d892a57849497eb490695 2397 gavodachs_2.6+dfsg-2.dsc
 ae4a884a5dd5c184e6eaeec49c53a26c929cee92 9840 
gavodachs_2.6+dfsg-2.debian.tar.xz
Checksums-Sha256:
 fd3b731951317738628b4763e9a24cd6e640c9b21edcfd6aeae6fbb4886de637 2397 
gavodachs_2.6+dfsg-2.dsc
 db9f78957930da3f60931a1ff81844645a226f4b8aee8acb2793d6b4b2486ecc 9840 
gavodachs_2.6+dfsg-2.debian.tar.xz
Files:
 f2a0a8dc200e195d0cb20ea1adfe94ef 2397 python optional gavodachs_2.6+dfsg-2.dsc
 f374ef39713a367379e8bd9c8dc7bf65 9840 python optional 
gavodachs_2.6+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmNforQACgkQcRWv0HcQ
3Pe5lg//UONi1tG2jr60pB45k3H9AFaR2ejbl6xVrE43SpbMCHpMbZ7UOPMi2rlr
OuIqY7Q/WdNE3X/gEnN0KYCz0YtvlUfPgDzzIhVlqWmih0VcdQZUs5YbCDhm+61L

Bug#1022487: closing 1022487

[Christoph Berg]

close 1022487 3.5-2
thanks
-- 

Mit freundlichen Grüßen,
Christoph Berg
-- 
Senior Consultant, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
Unser Umgang mit personenbezogenen Daten unterliegt folgenden
Bestimmungen: https://www.credativ.de/datenschutz

Bug#1023185: veusz does not run

[di dit]

Package: veusz
Version: 3.3.1-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: didi...@gmail.com

Dear Maintainer,

veusz does not start when launched from the GUI or from the CLI.
Here is the output of trying to run veusz from a terminal:

$  LANG=C veusz
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Traceback (most recent call last):
  File "/usr/bin/veusz", line 33, in 
sys.exit(load_entry_point('veusz==3.3.1', 'gui_scripts', 'veusz')())
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 369, in
run
app.startup()
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 267, in
startup
self.splash = makeSplash(self)
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 69, in
makeSplash
font.setPointSize(font.pointSize()*1.5)
TypeError: setPointSize(self, int): argument 1 has unexpected type 'float'

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

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

Versions of packages veusz depends on:
ii  libjs-sphinxdoc  4.5.0-4
ii  python3  3.10.6-1
ii  python3-numpy1:1.21.5-1+b1
ii  python3-veusz3.3.1-3

veusz recommends no packages.

veusz suggests no packages.

-- no debconf information

Processed: closing 1022487

[Debian Bug Tracking System]

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

> close 1022487 3.5-2
Bug #1022487 [src:pgq-node] pgq-node: FTBFS: Error: debian/control needs 
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked as fixed in versions pgq-node/3.5-2.
Bug #1022487 [src:pgq-node] pgq-node: FTBFS: Error: debian/control needs 
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1023147: marked as done (python3-asdf: ships /usr/lib/python3/dist-packages/docs/Makefile etc.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2022 10:36:39 +
with message-id 
and subject line Bug#1023147: fixed in python-asdf 2.13.0-2
has caused the Debian Bug report #1023147,
regarding python3-asdf: ships /usr/lib/python3/dist-packages/docs/Makefile etc.
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.)


-- 
1023147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-asdf
Version: 2.13.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed ships documentation build systems
and generically named files under /usr/lib/python3/dist-packages/docs/,
causing file conflicts with other packages doing the same mistake.

Looking at the file list, I find the following badly placed files, not all
of them cause file conflicts:

/usr/lib/python3/dist-packages/compatibility_tests
/usr/lib/python3/dist-packages/compatibility_tests/assert_file_correct.py
/usr/lib/python3/dist-packages/compatibility_tests/common.py
/usr/lib/python3/dist-packages/compatibility_tests/generate_file.py
/usr/lib/python3/dist-packages/compatibility_tests/test_file_compatibility.py

If these modules really need to be shipped, they need to be in some
package specific directory (i.e. something containing asdf).

/usr/lib/python3/dist-packages/docs
/usr/lib/python3/dist-packages/docs/Makefile
/usr/lib/python3/dist-packages/docs/_static
/usr/lib/python3/dist-packages/docs/_static/logo.ico
/usr/lib/python3/dist-packages/docs/_static/logo.pdf
/usr/lib/python3/dist-packages/docs/_static/logo.png
/usr/lib/python3/dist-packages/docs/asdf
/usr/lib/python3/dist-packages/docs/asdf/CODE_OF_CONDUCT.md
/usr/lib/python3/dist-packages/docs/asdf/arrays.rst
/usr/lib/python3/dist-packages/docs/asdf/asdf_tool.rst
/usr/lib/python3/dist-packages/docs/asdf/changes.rst
/usr/lib/python3/dist-packages/docs/asdf/citation.rst
/usr/lib/python3/dist-packages/docs/asdf/config.rst
/usr/lib/python3/dist-packages/docs/asdf/contributing.rst
/usr/lib/python3/dist-packages/docs/asdf/developer_api.rst
/usr/lib/python3/dist-packages/docs/asdf/developer_overview.rst
/usr/lib/python3/dist-packages/docs/asdf/developer_versioning.rst
/usr/lib/python3/dist-packages/docs/asdf/extending
/usr/lib/python3/dist-packages/docs/asdf/extending/compressors.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/converters.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/extensions.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/legacy.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/manifests.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/resources.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/schemas.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/uris.rst
/usr/lib/python3/dist-packages/docs/asdf/extending/use_cases.rst
/usr/lib/python3/dist-packages/docs/asdf/features.rst
/usr/lib/python3/dist-packages/docs/asdf/install.rst
/usr/lib/python3/dist-packages/docs/asdf/overview.rst
/usr/lib/python3/dist-packages/docs/asdf/user_api.rst
/usr/lib/python3/dist-packages/docs/asdf/using_extensions.rst
/usr/lib/python3/dist-packages/docs/conf.py
/usr/lib/python3/dist-packages/docs/index.rst
/usr/lib/python3/dist-packages/docs/make.bat

Documentation belongs into /usr/share/doc/$PACKAGE, and the build system
is probaby not needed at all.


Andreas
--- End Message ---
--- Begin Message ---
Source: python-asdf
Source-Version: 2.13.0-2
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated python-asdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2022 08:57:24 +0100
Source: python-asdf
Architecture: source
Version: 2.13.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 1023147
Changes:
 python-asdf (2.13.0-2) unstable; urgency=medium
 .
   * Remove files that accidently were 

Processed: tagging 979101

[Debian Bug Tracking System]

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

> tags 979101 + pending
Bug #979101 [devtodo] Legally problematic GPL-3+ readline dependency
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo
Bug #1023124 [systemd] libsystemd-shared-251.so: cannot open shared object file
Removed tag(s) moreinfo.
> close -1
Bug #1023124 [systemd] libsystemd-shared-251.so: cannot open shared object file
Marked Bug as done

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

Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

[Luca Boccassi]

Control: tags -1 -moreinfo
Control: close -1

On Sun, 30 Oct 2022 14:56:08 +0100 Salvo Tomaselli
 wrote:
> systemd-machine-id-setup: /usr/bin/systemd-machine-id-setup
> /bin/systemd-machine-id-setup
> /usr/share/man/man1/systemd-machine-id-setup.1.gz
> 
> 
> stat /usr/bin/systemd-machine-id-setup /bin/systemd-machine-id-setup
>  File: /usr/bin/systemd-machine-id-setup
>  Size: 18928   Blocks: 40 IO Block: 4096   regular
file
> Device: 259,5   Inode: 4201937 Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/   
root)
> Access: 2022-10-30 13:34:13.098418093 +0100
> Modify: 2022-08-14 20:06:18.0 +0200
> Change: 2022-08-22 15:25:56.730012624 +0200
> Birth: 2022-08-22 15:25:56.610011671 +0200
>  File: /bin/systemd-machine-id-setup
>  Size: 18928   Blocks: 40 IO Block: 4096   regular
file
> Device: 259,5   Inode: 8650854 Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/   
root)
> Access: 2022-10-30 13:38:20.0 +0100
> Modify: 2022-10-14 16:34:00.0 +0200
> Change: 2022-10-30 13:38:20.944385494 +0100
> Birth: 2022-10-30 13:38:20.816384357 +0100
> 
> 
> 
> It seems my system is in a weird status from some previous issues…
> Maybe originating  when apt told me to split /usr, then I had some
> issues and had to manually install a bunch of packages.

Yes, your system is in a bad state and needs to be fixed, and it has
nothing to do with the systemd packages or this update, so I'll close
this now.

-- 
Kind regards,
Luca Boccassi


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

Bug#1023178: microprofile: Contains non-free source

[Bastian Germann]

Source: microprofile
Version: 3.1+ds-2
Severity: serious

The files src/microprofile*.html contain JavaScript code from 
https://gist.github.com/mjackson/5311256
which never got a license even though people have asked for it. So please 
exclude them.

Bug#1019814: [Pkg-nagios-devel] Bug#1019814: icinga2: Please transition to wxwidgets3.2

[Sebastiaan Couwenberg]

The fixed package is in unstable but testing migration is prevented by 
gcc-12 FTBFS on mips64el (#1022991).


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