Bug#1032543: marked as done (tryton-sao: FTBFS in testing: build-dependency not installable: node-uglify)

[Debian Bug Tracking System]

Your message dated Thu, 9 Mar 2023 08:17:03 +0100
with message-id <20230309081703.0b1da...@monsterix.mbehrle.de>
and subject line Re: Bug#1032543: tryton-sao: FTBFS in testing: 
build-dependency not installable: node-uglify
has caused the Debian Bug report #1032543,
regarding tryton-sao: FTBFS in testing: build-dependency not installable: 
node-uglify
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.)


-- 
1032543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tryton-sao
Version: 6.0.27.1+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cleancss, nodejs, node-less, 
> node-po2json, node-uglify, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cleancss, nodejs, node-less, 
> node-po2json, node-uglify, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [400 B]
> Get:5 copy:/<>/apt_archive ./ Packages [480 B]
> Fetched 1837 B in 0s (141 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-main-dummy : Depends: node-uglify but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/tryton-sao_6.0.27.1+ds1-2_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230307;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230307=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 mark 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: tryton-sao
Version: 6.0.28+ds1-2
Control: tags -1 + fixed


* Lucas Nussbaum: " Bug#1032543: tryton-sao: FTBFS in
testing: build-dependency not installable: node-uglify" (Wed, 8 Mar 2023
21:32:25 +0100):

> Source: tryton-sao
> Version: 6.0.27.1+ds1-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230307 ftbfs-bookworm

Hi Lucas,

could those bugs be avoided by looking for already fixed versions in sid just
waiting for migration?

https://qa.debian.org/excuses.php?package=tryton-sao

Migration status for tryton-sao (6.0.27.1+ds1-2 to 6.0.28+ds1-2): Waiting for
test results or another package, or too young (no action required now - check
later) Issues preventing migration:

Too young, only 4 of 10 days old

Additional info:

Updating tryton-sao will fix bugs in testing: #1032353

Cheers,
Mathias--- End Message ---

Processed: Re: Bug#1032538: emacs: Shell command and Emacs Lisp code injection in emacsclient-mail.desktop

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 emacs: CVE-2023-27985 CVE-2023-27986
Bug #1032538 [src:emacs] emacs: Shell command and Emacs Lisp code injection in 
emacsclient-mail.desktop
Changed Bug title to 'emacs: CVE-2023-27985 CVE-2023-27986' from 'emacs: Shell 
command and Emacs Lisp code injection in emacsclient-mail.desktop'.

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

Bug#1032538: emacs: Shell command and Emacs Lisp code injection in emacsclient-mail.desktop

[Salvatore Bonaccorso]

Control: retitle -1 emacs: CVE-2023-27985 CVE-2023-27986

On Wed, Mar 08, 2023 at 08:57:52PM +0100, Salvatore Bonaccorso wrote:
> Source: emacs
> Version: 1:28.2+1-11
> Severity: grave
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> 
> Hi
> 
> No CVEs are yet assigned for the the following two issues:
> 
> | emacsclient-mail.desktop is vulnerable to shell command
> | injections and Emacs Lisp injections through a crafted
> | mailto: URI.
> 
> See: https://www.openwall.com/lists/oss-security/2023/03/08/2

CVEs were assigned for those two.

> 
> Fixes:
> 
> http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=d32091199ae5de590a83f1542a01d75fba000467

CVE-2023-27985

> http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=3c1693d08b0a71d40a77e7b40c0ebc42dca2d2cc

CVE-2023-27986

Regards,
Salvatore

Bug#1032567: ddnet: autopkgtests not testing the installed package

[Gianfranco Costamagna]

Source: ddnet
Version: 16.4-1.1
Severity: serious

Hello, the ddnet autopkgtests are not currently testing the installed package, 
but rather doing some sort of testsuite on source directory. This makes the 
test fail on s390x, rather than test not being run due to it being not built 
from source.

G.


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bug 1032539 is forwarded to https://github.com/tstack/lnav/issues/1128

[Debian Bug Tracking System]

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

> forwarded 1032539 https://github.com/tstack/lnav/issues/1128
Bug #1032539 [src:lnav] lnav: FTBFS in testing: dh_auto_test: error: make -j8 
check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 'https://github.com/tstack/lnav/issues/1128'.
> thanks
Stopping processing here.

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

Bug#983719: esptool: Version 3.0 fixes critical bugs

[Faidon Liambotis]

On Thu, Feb 23, 2023 at 12:16:41PM +0200, Faidon Liambotis wrote:
> I also have changes underway for 4.5, but currently looking into what it
> would take dependency-wise to accomplish this, as there are 1-2 new
> Python module dependencies that are not present in Debian yet. I'll
> follow up once I have something; I expect this to be in the next week or
> so.

I packaged the two new dependencies mentioned above:
 * python-reedsolo, which entered unstable this week; and 
 * python-pkcs11 (used only conditionally, for espsecure's HSM bits),
   which is waiting in NEW for about a week now.

I moved the repository to the DEP-14 layout, rebased the
feature/2.8-update branch, and then built on top of it in the new
debian/experimental branch. This now has 4.5.1, with lots of other fixes
and flasher stubs! I'd consider this a release candidate for an
experimental upload once pkcs11 passes through NEW.

Faidon

Bug#979090: marked as done (avrdude: inaccurate copyright file)

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 03:19:02 +
with message-id 
and subject line Bug#979090: fixed in avrdude 7.1+dfsg-1
has caused the Debian Bug report #979090,
regarding avrdude: inaccurate copyright 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.)


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

Package: avrdude
Severity: important

This package depends on libreadline8 which is GPL-3+ licensed. According 
to debian/copyright parts of your package are GPL-2-only licensed. If 
that is also (transitively) the case for the binaries that link with 
libreadline.so.8 it might be legally problematic (see 
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility).


There is an easy solution to the problem: Replacing the build dependency 
libreadline-dev with libeditreadline-dev links with the BSD-licensed 
libedit library which is a readline replacement.
--- End Message ---
--- Begin Message ---
Source: avrdude
Source-Version: 7.1+dfsg-1
Done: Milan Kupcevic 

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

Debian distribution maintenance software
pp.
Milan Kupcevic  (supplier of updated avrdude 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: Wed, 08 Mar 2023 20:53:51 -0500
Source: avrdude
Architecture: source
Version: 7.1+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Milan Kupcevic 
Changed-By: Milan Kupcevic 
Closes: 629360 909573 979090 1030364
Changes:
 avrdude (7.1+dfsg-1) sid; urgency=medium
 .
   * new upstream release
 - support teensy bootloader (closes: #629360)
 - support ATtiny2313A (closes: #909573)
   * remove upstream accepted patches
   * remove upstream tarball signature verification
   * quilt refresh
   * update standards version to 4.6.2
   * bump debhelper compat level to 12
   * debian/copyright: update, exclude non-dfsg files (closes: #979090)
 - lintian override undefined license
 - fix short beer-ware license id
   * update metainfo release license
   * use texi2html instead of makeinfo for pretty html docs (closes: #1030364)
 (lp: #1783814)
   * use dh_installman
   * use dh_installinfo
   * proper AppStrem metainfo id
   * add new devices to metainfo, udev rules
   * enable linuxspi
Checksums-Sha1:
 44a450261c6838bfb740aa1945589cdfd3a1ef70 1849 avrdude_7.1+dfsg-1.dsc
 856bc10eb2bc2723ec32cc9600f4f15b78cecfea 436116 avrdude_7.1+dfsg.orig.tar.xz
 e9d4a952bd45938245d67cbdb94f4addd04174b2 11740 avrdude_7.1+dfsg-1.debian.tar.xz
 74e508fa18a777bb8bd9f5ca2f561ef280c17cc8 9083 
avrdude_7.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 3c15039eae3f7032a217970e9d0e07a4c43ca554ea12c5b91a11a09ab09c5bd6 1849 
avrdude_7.1+dfsg-1.dsc
 91d454994f098f24a1c627036b4c9cec36ad639cda31875e652c104c0bd42906 436116 
avrdude_7.1+dfsg.orig.tar.xz
 6daea79846f0bf11c63d6a0b27b1a2206d60e187be4ad2fd556861e02cce08a5 11740 
avrdude_7.1+dfsg-1.debian.tar.xz
 21fd716b9010c2bc05986b891f6ac2228368119ccbb4ea386e58e2a53197571f 9083 
avrdude_7.1+dfsg-1_amd64.buildinfo
Files:
 f8b9e38a9d83b3715f4e4171da852abe 1849 electronics optional 
avrdude_7.1+dfsg-1.dsc
 580fbcca9717bf684802607adf201d7d 436116 electronics optional 
avrdude_7.1+dfsg.orig.tar.xz
 fe0fc0d62315692c6fa4a71d0899480e 11740 electronics optional 
avrdude_7.1+dfsg-1.debian.tar.xz
 baa47a1489e72efb8606a0affa389cfe 9083 electronics optional 
avrdude_7.1+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHFBAEBCgAvFiEEVkf/m69krCYf+z+G6e1ngbRVCQ4FAmQJSlARHG1pbGFuQGRl
Ymlhbi5vcmcACgkQ6e1ngbRVCQ4cbQwA1mUmVav+Lp38UK3wCs/Ni6YvFY9dC6pV
JWD/2ucKzIZ55GASJxOakdEUPypJP4W5oKMMTz5boayEZzYbS2NOm0gKgYNsikQ4
TqS63oO7SWiK4rWLCNlWvgnX4oKTbHlYFL+2do2mZV+lcaL48OmDKRqkmW4U3qaZ
xn6GsRsYcj6Ok95oJE5zapYGwYC5wFxRm2ok/kvar4/dXyxE2uljBhABEbSCNdz6
jMN1ROiHixrisGXPNsXa2snWjNDMA91w5SlUrzl7hl9EzV85Lb/Sx2zA332/7Ye4
7hQeOtfLxSVd6fpjtXEJmoZPJq4KFTkSt2jTOEs3b5g8c0wPclbdumT1xCq4
kstf9mfJuU3p3LZBTH4dWCRQT/HcKrKXw2MDdS9sLC27gwpcAaES8FL/zWMVivxI

Bug#1032488: marked as done (opendrop: arkode (sundials) error prevents interfacial tension analysis)

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 02:34:33 +
with message-id 
and subject line Bug#1032488: fixed in opendrop 3.3.1-5
has caused the Debian Bug report #1032488,
regarding opendrop: arkode (sundials) error prevents interfacial tension 
analysis
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.)


-- 
1032488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendrop
Version: 3.3.1-4
Severity: grave
Tags: patch upstream
Justification: renders package unusable

debian patch sundials_nvector_API6.patch enabled opendrop to build
against sundials 6. 

Nevertheless it still fails when attempting to analysis interfacial
tension measurements:

[ARKODE::ERKStep ERROR]  erkStep_FullRHS
  At t = inf, the right-hand side routine failed in an unrecoverable manner.


[ARKODE ERROR]  ARKODE
  At t = 0, the right-hand side routine failed in an unrecoverable manner.

Exception in callback PendantAnalysisJob._ylfit_done()
handle: )>
concurrent.futures.process._RemoteTraceback: 
"""
Traceback (most recent call last):
  File "/usr/lib/python3.11/concurrent/futures/process.py", line 256, in 
_process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
^
  File "/usr/lib/python3/dist-packages/opendrop/fit/younglaplace/__init__.py", 
line 51, in young_laplace_fit
model.set_params(initial_params)
  File "/usr/lib/python3/dist-packages/opendrop/fit/younglaplace/model.py", 
line 86, in set_params
dr_dBo, dz_dBo = radius * shape.DBo(s)
  
  File "opendrop/fit/younglaplace/shape.pyx", line 71, in 
opendrop.fit.younglaplace.shape.YoungLaplaceShape.DBo
  File "opendrop/fit/younglaplace/shape.pyx", line 89, in 
opendrop.fit.younglaplace.shape.YoungLaplaceShape.DBo_array
RuntimeError: ERKStepEvolve() failed.
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/opendrop/vendor/aioglib/_loop.py", line 
463, in __call__
self._context.run(self._callback, *self._args)
  File "/usr/lib/python3/dist-packages/opendrop/app/ift/services/analysis.py", 
line 219, in _ylfit_done
raise e
  File "/usr/lib/python3/dist-packages/opendrop/app/ift/services/analysis.py", 
line 217, in _ylfit_done
result = fut.result()
 
RuntimeError: ERKStepEvolve() failed.



Upstream has prepared a patch to update properly for sundials 6 in
commit cf9d5aa (development branch),
https://github.com/jdber1/opendrop/commit/cf9d5aa2f06d625f306114d001a99934cb913ff0


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages opendrop depends on:
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  gir1.2-gtk-3.03.24.36-4
ii  libc6 2.36-8
ii  libgcc-s1 12.2.0-14
ii  libpython3.11 3.11.2-5
ii  libstdc++612.2.0-14
ii  libsundials-arkode5   6.4.1+dfsg1-3
ii  python3   3.11.2-1
ii  python3-cairo 1.20.1-5+b1
ii  python3-gi3.42.2-3+b1
ii  python3-injector  0.20.1-1
ii  python3-matplotlib3.6.3-1+b1
ii  python3-numpy 1:1.24.2-1
ii  python3-opencv4.6.0+dfsg-11
ii  python3-scipy 1.10.1-2

opendrop recommends no packages.

Versions of packages opendrop suggests:
ii  opendrop-doc  3.3.1-4.1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opendrop
Source-Version: 3.3.1-5
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated opendrop package)

(This message was generated automatically at their request; if you
believe 

Bug#1032476: apache2: CVE-2023-25690 CVE-2023-27522

[Yadd]

On 3/8/23 22:39, Moritz Muehlenhoff wrote:

On Wed, Mar 08, 2023 at 07:09:20AM +0400, Yadd wrote:

On 3/7/23 23:46, Salvatore Bonaccorso wrote:

Source: apache2
Version: 2.4.55-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for apache2.

CVE-2023-25690[0]:

CVE-2023-27522[1]:


Hi,

here is the debdiff for Bullseye


I'm fine with a DSA, but we've seen a fair amount of regressions in 2.4.x 
releases,
so let's wait a few days for regressions reported in sid (and Ondreys PHP repo).

You can already upload the new version, though (we can reject/reupload if 
needed).

Cheers,
 Moritz


Hi,

thanks, I just uploaded it.

Regards,

Bug#991478: marked as done (shim-signed in buster fails to boot on Oracle Cloud arm64 with fatal crash in TianoCore)

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 01:19:17 +
with message-id 
and subject line Bug#991478: fixed in shim-signed 1.39
has caused the Debian Bug report #991478,
regarding shim-signed in buster fails to boot on Oracle Cloud arm64 with fatal 
crash in TianoCore
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.)


-- 
991478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shim-signed
Severity: grave

Starting from 1.34~1+deb10u1 and its corresponding "***WARNING***", now the
arm64 shim "is no longer signed".

As a result, after a mundane package upgrade and a reboot, all of my remote
arm64 machines do not boot anymore. I was not aware that the cloud provider
actually uses this "secure boot", else I'd pay more attention to that
"WARNING".

In any case, relying on the user reading upgrade notes, and then to scramble
rolling back the upgrade and holding the affected package ASAP, else the
system is bricked, is not a responsible package policy.

I would humbly suggest that you kept the latest signed version frozen at least
in "buster" with no further updates, until the signing issue is resolved. Or
as of now, release another update with the signed version in place.

P.S. just noticed 1.36~1+deb10u2 tried to do something about the boot breakage
- evidently that did not help.

-- 
With respect,
Roman
--- End Message ---
--- Begin Message ---
Source: shim-signed
Source-Version: 1.39
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated shim-signed package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 09 Mar 2023 00:58:53 +
Source: shim-signed
Architecture: source
Version: 1.39
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI Team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 991478 992073 995940 1008942 1016280 1026415
Changes:
 shim-signed (1.39) unstable; urgency=medium
 .
   * Build against new signed binaries corresponding to 15.7-1
 + This syncs up build-deps again. Closes: #1016280
 + We now have arm64 signed shims again \o/
   Undo the hacky unsigned arm64 build
   Closes: #1008942, #992073, #991478
 Pulls multiple other bugfixes in for the signed version:
 + Make sbat_var.S parse right with buggy gcc/binutils
 + Enable NX support at build time, as required by policy for signing
   new shim binaries.
 + Fixes argument handling bug with some firmware implementations.
   Closes: #995940
   * Update build-dep on shim-unsigned to use 15.7-1
   * Block Debian grub binaries with sbat < 4 (see #1024617)
 + Update Depends on grub2-common to match.
   * postinst/postrm: make config_item() more robust
   * Add pt_BR translation, thanks to Paulo Henrique de Lima
 Santana. Closes: #1026415
   * Tweak dependencies
Checksums-Sha1:
 085f9aac0b4793b4427c28f400ad754d2428dbb2 1808 shim-signed_1.39.dsc
 55f4e78d1a3445dd8a8cbd6f469a099834cdd263 812660 shim-signed_1.39.tar.xz
 f2debc4b26a859222cfc4d901026e00b77a1bfb4 6087 shim-signed_1.39_source.buildinfo
Checksums-Sha256:
 737689a5b0f6479927c7e3edc06b065d06bb3a8526a8b9e03c094958af481b65 1808 
shim-signed_1.39.dsc
 76a2b37953f7b91c69431ab8e9725643fd28b857573b1fff8264fb87e20b08bd 812660 
shim-signed_1.39.tar.xz
 c312757d6c85f2d63007b9941550077eac38eab94a444b5989fd415dfe022936 6087 
shim-signed_1.39_source.buildinfo
Files:
 41d437266aac919570597c981376deee 1808 utils optional shim-signed_1.39.dsc
 b0e69c929eb30472f402acb816c641f3 812660 utils optional shim-signed_1.39.tar.xz
 7bbb60b12068ac624c3470d689456f27 6087 utils optional 
shim-signed_1.39_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmQJMGcRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE5vJw/+JFK90D0vSEdXoTsq+ZzIav1FEb389neP
vuAYljPkorAraBppccN0dU1f6S4WuaCPW2wGHC5WFiwKudKXIT+Pb03vXxRAvRlQ

Bug#1016280: marked as done (shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15.4-7))

[Debian Bug Tracking System]

Your message dated Thu, 09 Mar 2023 01:19:17 +
with message-id 
and subject line Bug#1016280: fixed in shim-signed 1.39
has caused the Debian Bug report #1016280,
regarding shim-signed: FTBFS: build-dependency not installable: shim-unsigned 
(= 15.4-7)
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 13), shim-unsigned (= 15.4-7), sbsigntool 
> (>= 0.9.2-2), po-debconf, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 13), shim-unsigned (= 15.4-7), 
> sbsigntool (>= 0.9.2-2), po-debconf, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [405 B]
> Get:5 copy:/<>/apt_archive ./ Packages [486 B]
> Fetched 1848 B in 0s (115 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: shim-unsigned (= 15.4-7) but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/shim-signed_1.38_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=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: shim-signed
Source-Version: 1.39
Done: Steve McIntyre <93...@debian.org>

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

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

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated shim-signed package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 09 Mar 2023 00:58:53 +
Source: shim-signed
Architecture: source
Version: 1.39
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI Team 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 991478 992073 995940 1008942 1016280 1026415
Changes:
 shim-signed (1.39) unstable; urgency=medium
 .
   * Build against new signed binaries corresponding 

Processed: esptool: Version 3.0 fixes critical bugs

[Debian Bug Tracking System]

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

> block 983719 by 985095
Bug #983719 [esptool] Package is severely outdated
983719 was not blocked by any bugs.
983719 was not blocking any bugs.
Added blocking bug(s) of 983719: 985095
> thanks
Stopping processing here.

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

Bug#1029214: debian-archive-keyring: bookworm archive signing keys

[Ansgar]

Adam D. Barratt wrote:
> We need new archive signing keys for bookworm, so that we can include
> them in the release.

The keys are published now, see
https://lists.debian.org/debian-devel-announce/2023/03/msg1.html

Ansgar

Bug#1032247: marked as done (breezy-debian FTBFS: ERROR: breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version)

[Debian Bug Tracking System]

Your message dated Wed, 08 Mar 2023 22:34:02 +
with message-id 
and subject line Bug#1032247: fixed in breezy-debian 2.8.78
has caused the Debian Bug report #1032247,
regarding breezy-debian FTBFS: ERROR: 
breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=breezy-debian=all=2.8.77=1677498906=0

...
==
ERROR: 
breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version
--
testtools.testresult.real._StringException: log: {{{
19.771  creating repository in 
file:///tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/.bzr/.
19.773  creating branch  in 
file:///tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/
19.778  trying to create missing lock 
'/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/.bzr/checkout/dirstate'
19.778  opening working tree 
'/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work'
19.784  preparing to commit
INFO  Committing to: 
/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/
19.785  Selecting files for commit with filter None
INFO  Committed revision 1.
19.792  Committed revid b'jran...@example.com-20230227115456-yxlugfpwfxn7x7m6' 
as revno 1.
INFO  Current version is release, merging new release.
INFO  No upstream upstream-revision format specified, trying tag:1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:1.0
INFO  No upstream upstream-revision format specified, trying tag:foo-1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:foo-1.0
INFO  No upstream upstream-revision format specified, trying tag:v1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:v1.0
INFO  No upstream upstream-revision format specified, trying tag:v.1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:v.1.0
INFO  No upstream upstream-revision format specified, trying tag:release-1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:release-1.0
INFO  No upstream upstream-revision format specified, trying tag:1_0_release
19.798  Returning RevisionSpec RevisionSpec_tag for tag:1_0_release
INFO  No upstream upstream-revision format specified, trying tag:1_0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:1_0
INFO  No upstream upstream-revision format specified, trying tag:version-1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:version-1.0
INFO  No upstream upstream-revision format specified, trying 
tag:foo-1_0-release
19.798  Returning RevisionSpec RevisionSpec_tag for tag:foo-1_0-release
INFO  No upstream upstream-revision format specified, trying tag:foo-v1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:foo-v1.0
}}}

Traceback (most recent call last):
  File "/<>/upstream/branch.py", line 560, in get_recent_versions
since_revision, _subpath = self.version_as_revision(
   ^
  File "/<>/upstream/branch.py", line 477, in version_as_revision
raise PackageVersionNotPresent(package, version, self)
breezy.plugins.debian.upstream.PackageVersionNotPresent: foo 1.0 was not found 
in .

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/<>/tests/test_upstream.py", line 602, in 
test_get_latest_version
("2.1", "2.1"), source.get_latest_version("foo", "1.0"))
^^^
  File "/<>/upstream/branch.py", line 537, in get_latest_version
version = self.get_latest_release_version(
  
  File "/<>/upstream/branch.py", line 509, in 
get_latest_release_version
versions = list(self.get_recent_versions(package, current_version))
^^
  

Bug#1032168: meson: autopkgtest fills disk completely

[Jussi Pakkanen]

On Wed, 8 Mar 2023 at 20:47, Paul Gevers  wrote:

> Having said that, let me open the discussion on what I expect from this
> bug. I *don't* expect all tests on our infrastructure to be totally
> resilient to all restrictions we have. Although several tens of GB is a
> lot, I also realize that it isn't *that* much, so if you understand why
> meson suddenly needs considerably more disk space and that's to be
> expected, then I'm fine with closing this bug and have meson on the

In my opinion this is definitely a bug. I don't know where, though.
Whenever I do a new release I run a full package build + test suite
run and all that in an isolated VM (with pbuilder). That image has
only a single 40 GB file system. I have never had a problem with disk
space usage even though this image has all the dependency packages
installed twice: once on the main install and once in pbuilder.

I just checked and the image has 8 GB of free disk space so doing a
full package rebuild should take less than that.

Bug#1032163: marked as done (sudo: CVE-2023-27320)

[Debian Bug Tracking System]

Your message dated Wed, 08 Mar 2023 21:05:48 +
with message-id 
and subject line Bug#1032163: fixed in sudo 1.9.13p3-1
has caused the Debian Bug report #1032163,
regarding sudo: CVE-2023-27320
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.)


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

Hi,

The following vulnerability was published for sudo, filling as RC
aiming to have it fixed before bookworm release.

CVE-2023-27320[0]:
| Sudo before 1.9.13p2 has a double free in the per-command chroot
| feature.


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-2023-27320
https://www.cve.org/CVERecord?id=CVE-2023-27320
[1] https://www.openwall.com/lists/oss-security/2023/02/28/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sudo
Source-Version: 1.9.13p3-1
Done: Marc Haber 

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

Debian distribution maintenance software
pp.
Marc Haber  (supplier of updated sudo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Mar 2023 21:17:05 +0100
Source: sudo
Architecture: source
Version: 1.9.13p3-1
Distribution: unstable
Urgency: medium
Maintainer: Sudo Maintainers 
Changed-By: Marc Haber 
Closes: 1032163
Changes:
 sudo (1.9.13p3-1) unstable; urgency=medium
 .
   * new upstream version:
 * Fix potential double free for CHROOT= rules
   CVE-2023-27320. (Closes: #1032163)
 * Fix --enable-static-sudoers regression
 * check for overflow as result of fuzzing efforts
 * Fix parser regression disallowing rules for user "list"
 * Fix eventloop hang if there is /dev/tty data
 * Fix sudo -l command args regression
 * Fix sudo -l -U someuser regression
 * Fix list privs regression
Checksums-Sha1:
 3751b75e24aa6276312386230cdd9651f8a4780f 2573 sudo_1.9.13p3-1.dsc
 dd5bffed0397cd0543e487d1c8847554dcd5fe30 5100355 sudo_1.9.13p3.orig.tar.gz
 2ede198a3e0c3b08490d47978dd32fd609590ec0 833 sudo_1.9.13p3.orig.tar.gz.asc
 fa040675c6a280da99cac30b1a2757aebed7d182 41700 sudo_1.9.13p3-1.debian.tar.xz
 513176de46acdb8a9de2c4ba5e7ae47b35ebdf05 6452 sudo_1.9.13p3-1_source.buildinfo
Checksums-Sha256:
 9c86c42c15df25c1b05b5fb4048933779833f5ff1aa689ea3edfe8c3dcd0ad5a 2573 
sudo_1.9.13p3-1.dsc
 92334a12bb93e0c056b09f53e255ccb7d6f67c6350e2813cd9593ceeca78560b 5100355 
sudo_1.9.13p3.orig.tar.gz
 f0220d3d78c06b50213d3363c14f0eee65ebdbce49f7870a22b651374f23bd92 833 
sudo_1.9.13p3.orig.tar.gz.asc
 d16c26f7e1420a75f5a66db335db8be1278a6bb3b8f65fc28b830265ce82ec73 41700 
sudo_1.9.13p3-1.debian.tar.xz
 5bc6ba8b67b9d42f103ef0ffd456e1bd4209fba0d8ff152e67c5f35dffc9cd7c 6452 
sudo_1.9.13p3-1_source.buildinfo
Files:
 ba4dc90c41b440ed44a3ffad90358ac1 2573 admin optional sudo_1.9.13p3-1.dsc
 be560d914b60376dab3449c99b9f19ef 5100355 admin optional 
sudo_1.9.13p3.orig.tar.gz
 58aef40ebcf0f054ff3c029ff4a3ee1c 833 admin optional 
sudo_1.9.13p3.orig.tar.gz.asc
 3f6b83d15caeab6c5298a1b3f401356a 41700 admin optional 
sudo_1.9.13p3-1.debian.tar.xz
 3c51a2269bfaf1b025432ee731586b2a 6452 admin optional 
sudo_1.9.13p3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmQI8QUACgkQj3cgEwEy
BELlxQ/+Iy55A9nky7jTlcBMD08+pQE71pCJQVnHJf1bSW9dvebI1KikwFWCeZyu
Y3YlbHNrzmx7wGdYx5vXwYDiDMy0zZEooIaiAOP6nFD0nrNqwFr3zVDJvQibV+og
XhjYrQZph4nY9kbRqwpM8eodvc+Cymd0Saa38X79tsPhi6+ZrRk5+fCyYNb5gZRv
K7DqOldUUgJcKo6OgFpzCPxQCCcBSmNbr2RAEhfB2ZwotWddaB1DeTQePkCcCv5N
rbvYyKh3ZqYgIX3mU3pQG2lmF15C0B/AkmxBq1UEc/VzfFyDD5AezdJcVPhsYdaG
IofYME5Lp/V+/i2eWuTVA0ATQ626ha3ZoAyJWGXojqbOi+4JEo5MhMk5RXQW3Oku
2dnIVozFQvdW4s0RZUMzndgt22ACLwfUwcTL0gvDzvKAj4HsvpMtVtpKONsaieTG

Bug#1032506: plantuml: crashes on startup

[Victor Westerhuis]

Control: severity -1 important

Hi Andrej,

Thanks for the quick response.

Andrej Shadura schreef op 08.03.2023 10:44:

Hi,

On Wed, 8 Mar 2023, at 10:36, Victor Westerhuis wrote:

Package: plantuml
Version: 1:1.2020.2+ds-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vic...@westerhu.is

Hi maintainer,

Plantuml immediately crashes on startup with the following stacktrace:


The requested library, 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so,
is found in openjdk-17-jre, which is not a dependency of 
default-jre-headless.
It is, however, a dependency of default-jre. Manually installing 
default-jre

does indeed solve the error.


Thanks for the bug report. Does this happen always, or with some
specific command-line options? I was told before that plantuml is
known to work headless as well, although I hadn’t tested it myself.


The issue is in 
https://salsa.debian.org/debian/plantuml/-/blob/master/debian/plantuml.sh#L29-32: 
if the DISPLAY environment variable is unset the headless AWT backend is 
requested, which is correct. However, the opposite is not necessarily 
true: if DISPLAY is set, default-jre is not necessarily installed.


I have downgraded the severity, because explicitly unsetting DISPLAY 
before calling /usr/bin/plantuml fixes the crash.


--
Groet, Regards,

Victor Westerhuis

Processed: Re: Bug#1032506: plantuml: crashes on startup

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1032506 {Done: Andrej Shadura } [plantuml] plantuml: 
crashes on startup
Severity set to 'important' from 'grave'

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

Bug#1032558: tomopy: autopkgtest failure on s390x: numerical differences

[Paul Gevers]

Source: tomopy
Version: 1.10.4+ds1-9
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package tomopy, great. 
However, it fails. 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=tomopy

https://ci.debian.net/data/autopkgtest/testing/s390x/t/tomopy/31694525/log.gz

==
FAIL: test_bart 
(test_tomopy.test_recon.test_algorithm.ReconstructionAlgorithmTestCase.test_bart)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.usbhl2tu/downtmp/build.j1Q/src/test/test_tomopy/test_recon/test_algorithm.py", 
line 92, in test_bart

assert_allclose(
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
1592, in assert_allclose

assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/lib/python3.11/contextlib.py", line 81, in inner
return func(*args, **kwds)
   ^^^
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
862, in assert_array_compare

raise AssertionError(msg)
AssertionError: Not equal to tolerance rtol=0.01, atol=0

Mismatched elements: 16 / 18432 (0.0868%)
Max absolute difference: 6.0796738e-06
Max relative difference: 0.26425964
 x: array([[[-0.344939, -0.277677, -0.166536, ...,  0.051406, -0.012136,
 -0.053158],
[-0.259402, -0.219799, -0.031947, ...,  0.150905, -0.017446,...
 y: array([[[-0.344939, -0.277679, -0.166535, ...,  0.051409, -0.012139,
 -0.053158],
[-0.259402, -0.219799, -0.031947, ...,  0.150904, -0.017445,...
 >> begin captured logging << 
tomopy.recon.algorithm: INFO: Reconstructing 8 slice groups with 8 
master threads...

- >> end captured logging << -

==
FAIL: test_ospml_hybrid 
(test_tomopy.test_recon.test_algorithm.ReconstructionAlgorithmTestCase.test_ospml_hybrid)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.usbhl2tu/downtmp/build.j1Q/src/test/test_tomopy/test_recon/test_algorithm.py", 
line 220, in test_ospml_hybrid

assert_allclose(
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
1592, in assert_allclose

assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/lib/python3.11/contextlib.py", line 81, in inner
return func(*args, **kwds)
   ^^^
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
862, in assert_array_compare

raise AssertionError(msg)
AssertionError: Not equal to tolerance rtol=0.01, atol=0

Mismatched elements: 40 / 18432 (0.217%)
Max absolute difference: 2.3543835e-06
Max relative difference: 1.0744988
 x: array([[[5.263694e-05, 1.943827e-03, 6.817912e-03, ..., 2.017710e-02,
 1.339560e-02, 8.127209e-03],
[9.065618e-05, 3.251776e-03, 1.258464e-02, ..., 3.958699e-02,...
 y: array([[[5.263694e-05, 1.943812e-03, 6.817927e-03, ..., 2.017727e-02,
 1.339539e-02, 8.127220e-03],
[9.065603e-05, 3.251777e-03, 1.258466e-02, ..., 3.958680e-02,...
 >> begin captured logging << 
tomopy.recon.algorithm: INFO: Reconstructing 8 slice groups with 8 
master threads...

- >> end captured logging << -

==
FAIL: test_ospml_quad 
(test_tomopy.test_recon.test_algorithm.ReconstructionAlgorithmTestCase.test_ospml_quad)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.usbhl2tu/downtmp/build.j1Q/src/test/test_tomopy/test_recon/test_algorithm.py", 
line 237, in test_ospml_quad

assert_allclose(
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
1592, in assert_allclose

assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/lib/python3.11/contextlib.py", line 81, in inner
return func(*args, **kwds)
   ^^^
  File 
"/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
862, in assert_array_compare

raise AssertionError(msg)
AssertionError: Not equal to tolerance rtol=0.01, atol=0

Mismatched elements: 40 / 18432 (0.217%)
Max absolute difference: 

Processed: libvcflib breaks freebayes autopkgtest: Error: signal 11

[Debian Bug Tracking System]

Processing control commands:

> found -1 libvcflib/1.0.9+dfsg-1
Bug #1032557 [src:libvcflib, src:freebayes] libvcflib breaks freebayes 
autopkgtest: Error: signal 11
Marked as found in versions libvcflib/1.0.9+dfsg-1.
> found -1 freebayes/1.3.6-2
Bug #1032557 [src:libvcflib, src:freebayes] libvcflib breaks freebayes 
autopkgtest: Error: signal 11
Marked as found in versions freebayes/1.3.6-2.

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

Bug#1032557: libvcflib breaks freebayes autopkgtest: Error: signal 11

[Paul Gevers]

Source: libvcflib, freebayes
Control: found -1 libvcflib/1.0.9+dfsg-1
Control: found -1 freebayes/1.3.6-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
libvcflib  from testing1.0.9+dfsg-1
freebayes  from testing1.3.6-2
all others from testingfrom testing

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/f/freebayes/32031881/log.gz

.:
README.test_data
bash-tap
freebayes-env.yaml
performance
pipeline.sh
regression
runner.sh
snakemake-freebayes-parallel.smk
splice
t
targets.bed
test-simple-bash
test.alt
test.bam
test.bam.bai
test.bed
test.ref
test.ref.fai
test.vcf
tiny

./bash-tap:

./performance:
benchmark.md

./regression:
NA12878.chr22.tiny.vcf
README.md

./splice:
1:883884-887618.bam
1:883884-887618.bam.bai
1:883884-887618.fa
1:883884-887618.fa.fai

./t:
00_region_and_target_handling.t
01_call_variants.t
01b_call_variants.t
02_multi_bam.t
03_reference_bases.t

./test-simple-bash:

./tiny:
1read.bam
1read.bam.bai
NA12878.chr22.tiny.bam
NA12878.chr22.tiny.bam.bai
NA12878.chr22.tiny.cram
NA12878.chr22.tiny.giab.vcf
NA12878.chr22.tiny.hla.bam
NA12878.chr22.tiny.hla.bam.bai
hla.fa
hla.fa.fai
hla.vcf.gz
hla.vcf.gz.tbi
q with spaces.fa
q with spaces.fa.fai
q with spaces.regions
q.fa
q.fa.fai
q.regions
q.vcf.gz
q.vcf.gz.tbi
q_spiked.vcf.gz
q_spiked.vcf.gz.tbi
Test 1
Passed

Test 2
Passed

Test 3
Passed

Test 4
Passed

Test 5
Passed

Test 6
Passed

Test 7
Passed

Test 8
Error: signal 11:
freebayes(+0xa355a)[0x55743c9a055a]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bf90)[0x7fc692924f90]
/lib/x86_64-linux-gnu/libvcflib.so.1(_ZN6vcfliblsERSoRNS_7VariantE+0xfa0)[0x7fc692e883e0]
freebayes(+0x1247b)[0x55743c90f47b]
/lib/x86_64-linux-gnu/libc.so.6(+0x2718a)[0x7fc69291018a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fc692910245]
freebayes(+0x150d1)[0x55743c9120d1]
autopkgtest [13:13:47]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

[Paul Gevers]

Hi,

On Wed, 01 Mar 2023 09:58:14 +0100 Markus Koschany  wrote:

> I'm not able to reproduce the autopkgtest failure locally running in
> clean sid chroots.


On ci.debian.net, the tests also fail in unstable.

https://ci.debian.net/packages/d/dojo/

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1030440: nuitka: FTBFS: make[1]: *** [debian/rules:47: override_dh_auto_test] Error 1

[Adrian Bunk]

On Sat, Feb 04, 2023 at 08:22:34AM +0100, Lucas Nussbaum wrote:
> Source: nuitka
> Version: 1.3.5+ds-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230203 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 '/<>'
> > # The RUN_TEST_PYTHON is not the one to execute tests, just the for the
> > # test runner.
> > python3 ./tests/run-tests --skip-reflection-test --no-python2.7 
> > --no-python2.6
> > Traceback (most recent call last):
> >   File "/<>/./tests/run-tests", line 43, in 
> > main()
> >   File 
> > "/<>/nuitka/tools/testing/run_nuitka_tests/__main__.py", line 
> > 912, in main
> > assert (
> > AssertionError
> > make[1]: *** [debian/rules:47: override_dh_auto_test] Error 1
>...

Nuitka 1.4 seems to have some preliminary support for Python 3.11, but 
better support will only come in 1.5.

cu
Adrian

Bug#1032553: magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: magic-wormhole
Version: 0.12.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_nameplate.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_interfaces.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_lister.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/tor_manager.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/eventual.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/transit.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_key.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_allocator.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/util.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_code.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_wordlist.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_terminator.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_boss.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_rlcompleter.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/journal.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/xfer_util.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/ipaddrs.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/errors.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_order.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_send.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_input.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_mailbox.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/wormhole.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/timing.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_hints.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_version.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/observer.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_receive.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> copying src/wormhole/_rendezvous.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole
> creating 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/public_relay.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/cmd_ssh.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/cmd_receive.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/welcome.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/cli.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> copying src/wormhole/cli/cmd_send.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/cli
> creating 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/_dilation
> copying src/wormhole/_dilation/outbound.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/_dilation
> copying src/wormhole/_dilation/inbound.py -> 
> /<>/.pybuild/cpython3_3.11_magic-wormhole/build/wormhole/_dilation
> copying src/wormhole/_dilation/__init__.py -> 
> 

Bug#1032551: ruby-kubeclient: FTBFS in testing: ERROR: Test "ruby3.1" failed.

[Lucas Nussbaum]

Source: ruby-kubeclient
Version: 4.9.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-kubeclient/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"kubeclient\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-kubeclient/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/test_common.rb" "test/test_common_url_handling.rb" 
> "test/test_component_status.rb" "test/test_config.rb" "test/test_endpoint.rb" 
> "test/test_exec_credentials.rb" "test/test_gcp_command_credentials.rb" 
> "test/test_google_application_default_credentials.rb" "test/test_helper.rb" 
> "test/test_kubeclient.rb" "test/test_limit_range.rb" 
> "test/test_missing_methods.rb" "test/test_namespace.rb" "test/test_node.rb" 
> "test/test_oidc_auth_provider.rb" "test/test_persistent_volume.rb" 
> "test/test_persistent_volume_claim.rb" "test/test_pod.rb" 
> "test/test_pod_log.rb" "test/test_process_template.rb" 
> "test/test_real_cluster.rb" "test/test_replication_controller.rb" 
> "test/test_resource_list_without_kind.rb" "test/test_resource_quota.rb" 
> "test/test_secret.rb" "test/test_security_context_constraint.rb" 
> "test/test_service.rb" "test/test_service_account.rb" "test/test_watch.rb"  -v
> /usr/lib/ruby/vendor_ruby/http-parser/parser.rb:14: warning: `&' interpreted 
> as argument prefix
> /usr/lib/ruby/vendor_ruby/os.rb:154: warning: mismatched indentations at 
> 'end' with 'for' at 151
> /usr/lib/ruby/vendor_ruby/os.rb:158: warning: assigned but unused variable - 
> kb
> /usr/lib/ruby/vendor_ruby/os.rb:198: warning: mismatched indentations at 
> 'end' with 'def' at 190
> /usr/lib/ruby/vendor_ruby/os.rb:240: warning: mismatched indentations at 
> 'end' with 'case' at 218
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/core_ext/class/subclasses.rb:30:
>  warning: method redefined; discarding old subclasses
> /usr/lib/ruby/vendor_ruby/attr_required.rb:14: warning: `*' interpreted as 
> argument prefix
> /usr/lib/ruby/vendor_ruby/attr_required.rb:20: warning: `*' interpreted as 
> argument prefix
> /usr/lib/ruby/vendor_ruby/attr_required.rb:23: warning: `*' interpreted as 
> argument prefix
> /usr/lib/ruby/vendor_ruby/attr_optional.rb:12: warning: `*' interpreted as 
> argument prefix
> /usr/lib/ruby/vendor_ruby/attr_optional.rb:18: warning: `*' interpreted as 
> argument prefix
> /usr/lib/ruby/vendor_ruby/attr_optional.rb:21: warning: `*' interpreted as 
> argument prefix
> Run options: -v --seed 18236
> 
> # Running:
> 
> TestSecurityContextConstraints#test_create_security_context_constraint = 0.02 
> s = .
> TestSecurityContextConstraints#test_get_security_context_constraints = 0.00 s 
> = .
> TestServiceAccount#test_get_from_json_v1 = 0.00 s = .
> TestNode#test_get_from_json_v1_raw = 0.00 s = .
> TestNode#test_get_from_json_v1_raw_error = 0.00 s = .
> TestNode#test_get_from_json_v1 = 0.00 s = .
> TestNamespace#test_create_namespace = 0.00 s = .
> TestNamespace#test_get_namespace_v1 = 0.00 s = .
> TestNamespace#test_delete_namespace_v1 = 0.00 s = .
> TestProcessTemplate#test_templates_methods = 0.01 s = .
> TestProcessTemplate#test_no_processedtemplates_methods = 0.00 s = .
> TestProcessTemplate#test_process_template = 0.00 s = .
> TestPodLog#test_get_pod_limit_bytes = 0.00 s = .
> TestPodLog#test_get_pod_log_tail_lines = 0.00 s = .
> TestPodLog#test_get_pod_log = 0.00 s = .
> TestPodLog#test_watch_pod_log_with_block = 0.00 s = .
> 

Bug#1032552: libjs-img.srcset: FTBFS in testing: build-dependency not installable: node-uglify

[Lucas Nussbaum]

Source: libjs-img.srcset
Version: 2.0.0~20131003~dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10~), dh-buildinfo, node-uglify | 
> yui-compressor, tofrodos, build-essential, fakeroot
> Filtered Build-Depends: cdbs, debhelper (>= 10~), dh-buildinfo, node-uglify, 
> tofrodos, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [407 B]
> Get:5 copy:/<>/apt_archive ./ Packages [477 B]
> Fetched 1841 B in 0s (103 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-main-dummy : Depends: node-uglify but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/libjs-img.srcset_2.0.0~20131003~dfsg-3_testing.log

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

Bug#1032550: igdiscover: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: igdiscover
Version: 0.11-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
>   pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/species.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/clonoquery.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/dendrogram.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/rename.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/merge.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/germlinefilter.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/union.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/errorplot.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/plotalleles.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/init.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/group.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/discoverj.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/igblast.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/table.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/config.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/haplotype.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/clonotypes.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/dereplicate.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/upstream.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/commonv.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/discover.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/filter.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/multidiscover.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/run.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/trie.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/clusterplot.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/dbdiff.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/utils.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/_version.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/count.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/cluster.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/parse.py -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/igdiscover.yaml -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/Snakefile -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> copying igdiscover/empty.aux -> 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover
> UPDATING 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover/_version.py
> set 
> /<>/.pybuild/cpython3_3.11_igdiscover/build/igdiscover/_version.py
>  to '0.11'
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml doc/ build/html 
> # HTML generator
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> reading sources... [ 11%] advanced
> reading sources... [ 22%] changes
> reading sources... [ 33%] develop
> reading sources... [ 44%] faq
> reading sources... [ 55%] guide
> reading sources... [ 66%] index
> reading sources... [ 77%] installation
> reading sources... [ 88%] manual-installation
> reading sources... [100%] testing
> 
> looking for now-outdated files... none found
> pickling 

Bug#1032548: python-zstandard: FTBFS in testing: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 har

[Lucas Nussbaum]

Source: python-zstandard
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs; LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 sphinx-build -bhtml . _build/html
> Running Sphinx v5.3.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 14 source files that are out of date
> updating environment: [new config] 14 added, 0 changed, 0 removed
> reading sources... [  7%] api_usage
> reading sources... [ 14%] buffer
> reading sources... [ 21%] compression_parameters
> reading sources... [ 28%] compressor
> reading sources... [ 35%] concepts
> reading sources... [ 42%] contributing
> reading sources... [ 50%] decompressor
> reading sources... [ 57%] dictionaries
> reading sources... [ 64%] index
> reading sources... [ 71%] installing
> reading sources... [ 78%] misc_apis
> reading sources... [ 85%] multithreaded
> reading sources... [ 92%] news
> reading sources... [100%] projectinfo
> 
> WARNING: autodoc: failed to import class 'BufferSegment' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegmentsCollection' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionParameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionWriter' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionReader' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionChunker' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionWriter' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionReader' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionDict' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'train_dictionary' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'get_frame_parameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_header_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_content_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'FrameParameters' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 
> 'estimate_decompression_context_size' from module 'zstandard'; the following 
> exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'open' from module 'zstandard'; 
> the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'compress' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'decompress' from module 
> 'zstandard'; the following 

Bug#1032547: facet-analyser: FTBFS in testing: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

[Lucas Nussbaum]

Source: facet-analyser
Version: 0.0~git20221121142040.6be10b8+ds1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start 1: basicPluginTest01
> 
> 1: Test command: /usr/bin/pvpython "/<>/scripts/pvsm2webgl.py" 
> "-i" "8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.pvsm" "-o" 
> "/<>/docs/demos/WebGL/8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.webgl"
>  "-p" 
> "/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyser.so"
> 1: Working Directory: /<>/demos/
> 1: Test timeout computed to be: 1500
> test 2
> Start 2: basicPluginTest02
> 
> 2: Test command: /usr/bin/pvpython "/<>/scripts/pvsm2x3d.py" 
> "-i" "8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.pvsm" "-o" 
> "../docs/demos/X3D/8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.x3d" 
> "-p" 
> "/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyser.so"
> 2: Working Directory: /<>/demos/
> 2: Test timeout computed to be: 1500
> test 3
> Start 3: basicTest01
> 
> 3: Test command: 
> /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyserTest
>  "8faced-rhombic-dodecahedron_twinned_simplified.vtk"
> 3: Working Directory: /<>/testing/
> 3: Test timeout computed to be: 1500
> test 4
> Start 4: basicExampleTest01
> 
> 4: Test command: 
> /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyserCLI
>  "8faced-rhombic-dodecahedron_twinned_010_deformed_wss.vtp" "51" "15" "0.2" 
> "0.001" "2" "0" "8faced-rhombic-dodecahedron_twinned_010_deformed_wss_FA.vtp"
> 4: Working Directory: /<>/demos/
> 4: Test timeout computed to be: 1500
> 3: 
> vtkGaussianSplatterExtended progress:   0.0%
> vtkGaussianSplatterExtended progress:   0.0%
> vtkGaussianSplatterExtended progress:   4.2%
> vtkGaussianSplatterExtended progress:   8.3%
> vtkGaussianSplatterExtended progress:  12.5%
> vtkGaussianSplatterExtended progress:  16.7%
> vtkGaussianSplatterExtended progress:  20.8%
> vtkGaussianSplatterExtended progress:  25.0%
> vtkGaussianSplatterExtended progress:  29.2%
> vtkGaussianSplatterExtended progress:  33.3%
> vtkGaussianSplatterExtended progress:  37.5%
> vtkGaussianSplatterExtended progress:  41.7%
> vtkGaussianSplatterExtended progress:  45.8%
> vtkGaussianSplatterExtended progress:  50.0%
> vtkGaussianSplatterExtended progress:  54.2%
> vtkGaussianSplatterExtended progress:  58.3%
> vtkGaussianSplatterExtended progress:  62.5%
> vtkGaussianSplatterExtended progress:  66.7%
> vtkGaussianSplatterExtended progress:  70.8%
> vtkGaussianSplatterExtended progress:  75.0%
> vtkGaussianSplatterExtended progress:  79.2%
> vtkGaussianSplatterExtended progress:  83.3%
> vtkGaussianSplatterExtended progress:  87.5%
> vtkGaussianSplatterExtended progress:  91.7%
> vtkGaussianSplatterExtended progress:  95.8%
> vtkGaussianSplatterExtended progress: 100.0%
> 3: 
> MorphologicalWatershedFromMarkersImageFilter progress:   0.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   1.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   2.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   3.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   4.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   5.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   6.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   7.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   8.0%
> MorphologicalWatershedFromMarkersImageFilter progress:   9.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  10.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  11.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  12.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  13.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  14.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  15.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  16.0%
> MorphologicalWatershedFromMarkersImageFilter progress:  

Bug#1032549: python-pbcore: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: python-pbcore
Version: 2.1.2+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> debian/rules:55: warning: overriding recipe for target 
> 'override_dh_auto_clean'
> debian/rules:28: warning: ignoring old recipe for target 
> 'override_dh_auto_clean'
> # we need to exclude tests requiring pbtestdata which is not packaged
> mkdir -p /tmp/tests_avoid
> mv `grep -l pbtestdata tests/*.py` /tmp/tests_avoid
> # for whatever reason this test is failing as well - just skip it for the 
> moment
> mv tests/test_pbdataset_filters.py /tmp/tests_avoid
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} setup.py test" \
>   dh_auto_test
> I: pybuild base:240: python3.11 setup.py test
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> running pytest
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /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.11: No module named pip
> error: Command '['/usr/bin/python3.11', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpqico3vl0', '--quiet', 'astroid<=2.14.0-dev0,>=2.12.13']' returned 
> non-zero exit status 1.
> E: pybuild pybuild:388: test: plugin custom failed with: exit code=1: 
> python3.11 setup.py test
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/python-pbcore_2.1.2+dfsg-5_testing.log

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

Bug#1032546: cups-filters: FTBFS in testing: QPDF.hh:1569:36: error: ‘std::string_view’ has not been declared

[Lucas Nussbaum]

Source: cups-filters
Version: 1.28.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x  
> -D_PPD_DEPRECATED=""-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall  
> -D_GNU_SOURCE -c -o filter/pdftopdf/pdftopdf-intervalset.o `test -f 
> 'filter/pdftopdf/intervalset.cc' || echo './'`filter/pdftopdf/intervalset.cc
> /usr/include/qpdf/QPDF.hh:1569:36: error: ‘std::string_view’ has not been 
> declared
>  1569 | void linearizationWarning(std::string_view);
>   |^~~
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x  
> -D_PPD_DEPRECATED=""-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall  
> -D_GNU_SOURCE -c -o filter/pdftopdf/pdftopdf-qpdf_tools.o `test -f 
> 'filter/pdftopdf/qpdf_tools.cc' || echo './'`filter/pdftopdf/qpdf_tools.cc
> In file included from /usr/include/qpdf/Buffer.hh:26,
>  from /usr/include/qpdf/QPDFObjectHandle.hh:36,
>  from filter/pdftopdf/qpdf_tools.h:4,
>  from filter/pdftopdf/qpdf_tools.cc:1:
> /usr/include/qpdf/PointerHolder.hh:31:3: warning: #warning 
> "POINTERHOLDER_TRANSITION is not defined -- see qpdf/PointerHolder.hh" [-Wcpp]
>31 | # warning "POINTERHOLDER_TRANSITION is not defined -- see 
> qpdf/PointerHolder.hh"
>   |   ^~~
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x  
> -D_PPD_DEPRECATED=""-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall  
> -D_GNU_SOURCE -c -o filter/pdftopdf/pdftopdf-qpdf_xobject.o `test -f 
> 'filter/pdftopdf/qpdf_xobject.cc' || echo './'`filter/pdftopdf/qpdf_xobject.cc
> /usr/include/qpdf/QPDF.hh:1569:36: error: ‘std::string_view’ has not been 
> declared
>  1569 | void linearizationWarning(std::string_view);
>   |^~~
> In file included from /usr/include/qpdf/Buffer.hh:26,
>  from /usr/include/qpdf/QPDFObjectHandle.hh:36,
>  from filter/pdftopdf/qpdf_xobject.h:4,
>  from filter/pdftopdf/qpdf_xobject.cc:1:
> /usr/include/qpdf/PointerHolder.hh:31:3: warning: #warning 
> "POINTERHOLDER_TRANSITION is not defined -- see qpdf/PointerHolder.hh" [-Wcpp]
>31 | # warning "POINTERHOLDER_TRANSITION is not defined -- see 
> qpdf/PointerHolder.hh"
>   |   ^~~
> make[3]: *** [Makefile:4224: filter/pdftopdf/pdftopdf-pdftopdf_processor.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/cups-filters_1.28.17-1_testing.log

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

Bug#1032545: r-cran-qpdf: FTBFS in testing: QPDF.hh:1569:36: error: ‘std::string_view’ has not been declared

[Lucas Nussbaum]

Source: r-cran-qpdf
Version: 1.3.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> g++ -std=gnu++11 -I"/usr/share/R/include" -DNDEBUG -I/usr/include/qpdf/ 
> -I'/usr/lib/R/site-library/Rcpp/include'   -fvisibility=hidden -fpic  -g -O2 
> -ffile-prefix-map=/build/r-base-wZDgjM/r-base-4.2.2.20221110=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c bindings.cpp -o bindings.o
> In file included from /usr/include/qpdf/Buffer.hh:26,
>  from /usr/include/qpdf/QPDF.hh:38,
>  from bindings.cpp:1:
> /usr/include/qpdf/PointerHolder.hh:31:3: warning: #warning 
> "POINTERHOLDER_TRANSITION is not defined -- see qpdf/PointerHolder.hh" [-Wcpp]
>31 | # warning "POINTERHOLDER_TRANSITION is not defined -- see 
> qpdf/PointerHolder.hh"
>   |   ^~~
> /usr/include/qpdf/QPDF.hh:1569:36: error: ‘std::string_view’ has not been 
> declared
>  1569 | void linearizationWarning(std::string_view);
>   |^~~
> In file included from bindings.cpp:3:
> /usr/include/qpdf/QPDFWriter.hh:557:27: error: ‘std::string_view’ has not 
> been declared
>   557 | void writeString(std::string_view str);
>   |   ^~~
> /usr/include/qpdf/QPDFWriter.hh:559:30: error: ‘std::string_view’ has not 
> been declared
>   559 | void writeStringQDF(std::string_view str);
>   |  ^~~
> /usr/include/qpdf/QPDFWriter.hh:560:32: error: ‘std::string_view’ has not 
> been declared
>   560 | void writeStringNoQDF(std::string_view str);
>   |^~~
> make[1]: *** [/usr/lib/R/etc/Makeconf:178: bindings.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/r-cran-qpdf_1.3.0+dfsg-1_testing.log

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

Bug#1032543: tryton-sao: FTBFS in testing: build-dependency not installable: node-uglify

[Lucas Nussbaum]

Source: tryton-sao
Version: 6.0.27.1+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cleancss, nodejs, node-less, 
> node-po2json, node-uglify, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cleancss, nodejs, node-less, 
> node-po2json, node-uglify, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [400 B]
> Get:5 copy:/<>/apt_archive ./ Packages [480 B]
> Fetched 1837 B in 0s (141 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-main-dummy : Depends: node-uglify but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/tryton-sao_6.0.27.1+ds1-2_testing.log

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

Bug#1032541: ruby-jekyll-remote-theme: FTBFS in testing: ERROR: Test "ruby3.1" failed: No such file or directory @ rb_sysopen - /<>/tmp/dest/index.html

[Lucas Nussbaum]

Source: ruby-jekyll-remote-theme
Version: 0.4.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>No such file or directory @ rb_sysopen - 
> /<>/tmp/dest/index.html
>  # ./spec/jekyll-remote-theme/integration_spec.rb:31:in `read'
>  # ./spec/jekyll-remote-theme/integration_spec.rb:31:in `block (2 levels) 
> in '
>  # ./spec/jekyll-remote-theme/integration_spec.rb:62:in `block (3 levels) 
> in '
>  # 
> /usr/share/rubygems-integration/all/gems/webmock-3.18.1/lib/webmock/rspec.rb:37:in
>  `block (2 levels) in '
> 
> Finished in 4.44 seconds (files took 0.60867 seconds to load)
> 79 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/jekyll-remote-theme/integration_spec.rb:47 # Jekyll::RemoteTheme 
> Integration the pages-themes/primer theme build the index
> rspec ./spec/jekyll-remote-theme/integration_spec.rb:51 # Jekyll::RemoteTheme 
> Integration the pages-themes/primer theme uses the theme
> rspec ./spec/jekyll-remote-theme/integration_spec.rb:56 # Jekyll::RemoteTheme 
> Integration the pages-themes/primer theme builds stylesheets
> rspec ./spec/jekyll-remote-theme/integration_spec.rb:39 # Jekyll::RemoteTheme 
> Integration the pages-themes/primer theme returns a zero exit code
> rspec ./spec/jekyll-remote-theme/integration_spec.rb:60 # Jekyll::RemoteTheme 
> Integration the pages-themes/primer theme requires dependencies
> 
> Randomized with seed 21554
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> ./spec/jekyll-remote-theme/downloader_spec.rb 
> ./spec/jekyll-remote-theme/integration_spec.rb 
> ./spec/jekyll-remote-theme/mock_gemspec_spec.rb 
> ./spec/jekyll-remote-theme/munger_spec.rb 
> ./spec/jekyll-remote-theme/theme_spec.rb ./spec/jekyll_remote_theme_spec.rb 
> --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/ruby-jekyll-remote-theme_0.4.3-2_testing.log

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

Bug#1032542: conda-package-handling: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-handling
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/interface.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/tarball.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/streaming.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/conda_fmt.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/api.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/validate.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> plugins: mock-3.8.2
> collected 39 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_interface.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_interface.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_interface.py:12: in 
> from conda_package_handling.conda_fmt import CondaFormat_v2
> conda_package_handling/conda_fmt.py:15: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294
>   /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294: 
> PytestConfigWarning: Unknown config option: env
>   
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
> 
> ../../../../../../usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19
>   
> /usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> conda_package_handling/api.py:29
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling/api.py:29:
>  UserWarning: Install zstandard Python bindings for .conda support
> _warnings.warn("Install zstandard Python bindings for .conda support")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> - generated xml file: /<>/.pybuild/cpython3_3.11/build/junit.xml 
> -
> === short test summary info 
> 
> ERROR tests/test_interface.py
>  Interrupted: 1 error during collection 
> 
> = 3 warnings, 1 error in 0.22s 
> =
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i 

Bug#1032539: lnav: FTBFS in testing: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: lnav
Version: 0.11.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> PASS: test_abbrev
> PASS: test_ansi_scrubber
> PASS: test_bookmarks
> PASS: test_auto_fd
> PASS: test_auto_mem
> PASS: test_date_time_scanner
> PASS: test_format_installer.sh
> PASS: lnav_doctests
> PASS: test_grep_proc2
> PASS: test_grep_proc.sh
> PASS: test_log_accel
> PASS: test_reltime
> PASS: test_format_loader.sh
> PASS: test_scripts.sh
> PASS: test_config.sh
> PASS: test_events.sh
> PASS: test_shlexer.sh
> PASS: test_cli.sh
> PASS: test_sql_coll_func.sh
> PASS: test_sql_anno.sh
> PASS: test_meta.sh
> PASS: test_sql_fs_func.sh
> PASS: test_sessions.sh
> PASS: test_sql_search_table.sh
> PASS: test_sql_regexp.sh
> PASS: test_sql_indexes.sh
> PASS: test_sql_yaml_func.sh
> PASS: test_json_format.sh
> PASS: test_text_anonymizer
> PASS: test_sql_xml_func.sh
> PASS: test_sql_time_func.sh
> PASS: test_sql_json_func.sh
> PASS: test_view_colors.sh
> PASS: test_curl.sh
> PASS: test_tui.sh
> PASS: test_text_file.sh
> PASS: test_pretty_print.sh
> PASS: test_data_parser.sh
> FAIL: test_sql_str_func.sh
> PASS: test_sql_views_vtab.sh
> PASS: test_cmds.sh
> ==
>lnav 0.11.1: test/test-suite.log
> ==
> 
> # TOTAL: 41
> # PASS:  40
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test_sql_str_func.sh
> ==
> 
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select length(gzip(1))
> BEGIN 
> test_sql_str_func.sh_7f751009d0db15fc97f9113c5c84db05ff1de9c3.out
> Row 0:
>   Column length(gzip(1)): 21
> END   
> test_sql_str_func.sh_7f751009d0db15fc97f9113c5c84db05ff1de9c3.out
> BEGIN 
> test_sql_str_func.sh_7f751009d0db15fc97f9113c5c84db05ff1de9c3.err
> END   
> test_sql_str_func.sh_7f751009d0db15fc97f9113c5c84db05ff1de9c3.err
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select gunzip(gzip(1))
> BEGIN 
> test_sql_str_func.sh_129e58679e72f3cc5864812026e49a7917baf3d0.out
> Row 0:
>   Column gunzip(gzip(1)): 1
> END   
> test_sql_str_func.sh_129e58679e72f3cc5864812026e49a7917baf3d0.out
> BEGIN 
> test_sql_str_func.sh_129e58679e72f3cc5864812026e49a7917baf3d0.err
> END   
> test_sql_str_func.sh_129e58679e72f3cc5864812026e49a7917baf3d0.err
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select humanize_file_size()
> BEGIN 
> test_sql_str_func.sh_bfe8b09e23389af0ef14359b66d68228d0285185.out
> END   
> test_sql_str_func.sh_bfe8b09e23389af0ef14359b66d68228d0285185.out
> BEGIN 
> test_sql_str_func.sh_bfe8b09e23389af0ef14359b66d68228d0285185.err
> error: sqlite3_exec failed -- wrong number of arguments to function 
> humanize_file_size()
> END   
> test_sql_str_func.sh_bfe8b09e23389af0ef14359b66d68228d0285185.err
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select humanize_file_size('abc')
> BEGIN 
> test_sql_str_func.sh_790da4aab5af901feeff5426790876eb91b967cb.out
> END   
> test_sql_str_func.sh_790da4aab5af901feeff5426790876eb91b967cb.out
> BEGIN 
> test_sql_str_func.sh_790da4aab5af901feeff5426790876eb91b967cb.err
> error: sqlite3_exec failed -- Expecting an integer for argument number 0
> END   
> test_sql_str_func.sh_790da4aab5af901feeff5426790876eb91b967cb.err
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select humanize_file_size(1, 2)
> BEGIN 
> test_sql_str_func.sh_1e7362ac3d9690b1b2cfbd320b6129c46ecfbb8a.out
> END   
> test_sql_str_func.sh_1e7362ac3d9690b1b2cfbd320b6129c46ecfbb8a.out
> BEGIN 
> test_sql_str_func.sh_1e7362ac3d9690b1b2cfbd320b6129c46ecfbb8a.err
> error: sqlite3_exec failed -- wrong number of arguments to function 
> humanize_file_size()
> END   
> test_sql_str_func.sh_1e7362ac3d9690b1b2cfbd320b6129c46ecfbb8a.err
> 
> 2023-03-08T09:31:43+00:00 
> =
> Command: test: ./drive_sql select humanize_file_size(10 * 1000 * 
> 1000)
> BEGIN 
> test_sql_str_func.sh_8c9ef83431ea75050fd16824075bf72056cf5f53.out
> Row 0:
>   Column 

Bug#1032540: conda-package-streaming: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-streaming
Version: 0.7.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 
> * Building wheel...
> Successfully built conda_package_streaming-0.7.0-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> plugins: mock-3.8.2, cov-4.0.0
> collected 15 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_transmute.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_transmute.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_transmute.py:14: in 
> from conda_package_streaming.transmute import transmute, transmute_tar_bz2
> conda_package_streaming/transmute.py:23: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/bottle.py:38
>   /usr/lib/python3/dist-packages/bottle.py:38: DeprecationWarning: 'cgi' is 
> deprecated and slated for removal in Python 3.13
> import base64, cgi, email.utils, functools, hmac, itertools, mimetypes,\
> 
> conda_package_streaming/package_streaming.py:19
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> 
> -- coverage: platform linux, python 3.11.2-final-0 ---
> Name   Stmts   Miss  Cover
> --
> conda_package_streaming/__init__.py1  0   100%
> conda_package_streaming/exceptions.py  9  456%
> conda_package_streaming/extract.py42 3224%
> conda_package_streaming/lazy_wheel.py131 9131%
> conda_package_streaming/package_streaming.py  47 2547%
> conda_package_streaming/s3.py 39 1854%
> conda_package_streaming/transmute.py  52 4415%
> conda_package_streaming/url.py39 2536%
> --
> TOTAL36023934%
> 
> === short test summary info 
> 
> ERROR tests/test_transmute.py
>  Interrupted: 1 error during collection 
> 
> = 2 warnings, 1 error in 0.37s 
> =
> E: pybuild pybuild:388: test: plugin pyproject failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/03/07/conda-package-streaming_0.7.0-4_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230307;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230307=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions 

Processed: tagging 1032163

[Debian Bug Tracking System]

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

> tags 1032163 + confirmed
Bug #1032163 [src:sudo] sudo: CVE-2023-27320
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#1032538: emacs: Shell command and Emacs Lisp code injection in emacsclient-mail.desktop

[Salvatore Bonaccorso]

Source: emacs
Version: 1:28.2+1-11
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

No CVEs are yet assigned for the the following two issues:

| emacsclient-mail.desktop is vulnerable to shell command
| injections and Emacs Lisp injections through a crafted
| mailto: URI.

See: https://www.openwall.com/lists/oss-security/2023/03/08/2

Fixes:

http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=d32091199ae5de590a83f1542a01d75fba000467
http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=3c1693d08b0a71d40a77e7b40c0ebc42dca2d2cc

Those do not affect older versions in bullseye. Making it RC for
bookworm and have a fix included before bookworm release.

Regards,
Salvatore

Processed: Re: Bug#1027439: elementpath breaks python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'

[Debian Bug Tracking System]

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

> # fixed upstream in xmlschema, let's reassign there
> reassign 1027439 src:python-xmlschema 1.10.0-3
Bug #1027439 [src:elementpath, src:python-xmlschema] elementpath breaks 
python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'
Bug reassigned from package 'src:elementpath, src:python-xmlschema' to 
'src:python-xmlschema'.
No longer marked as found in versions elementpath/3.0.2-1 and 
python-xmlschema/1.10.0-3.
Ignoring request to alter fixed versions of bug #1027439 to the same values 
previously set
Bug #1027439 [src:python-xmlschema] elementpath breaks python-xmlschema 
autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'
Marked as found in versions python-xmlschema/1.10.0-3.
> affects 1027439 src:elementpath
Bug #1027439 [src:python-xmlschema] elementpath breaks python-xmlschema 
autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'
Added indication that 1027439 affects src:elementpath
> thanks
Stopping processing here.

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

Bug#1032316: marked as done (llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?)

[Debian Bug Tracking System]

Your message dated Wed, 8 Mar 2023 18:49:12 +
with message-id 
and subject line Re: Bug#1032316: llvm-toolchain-15: is this version intended 
for Debian 12 'bookworm'?
has caused the Debian Bug report #1032316,
regarding llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?
to be marked as done.

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

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


-- 
1032316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-15
Version: 1:15.0.7-1
Severity: serious
Justification: blocking RC bug fixes in Mesa from migrating
X-Debbugs-Cc: debian-rele...@lists.debian.org

llvm-toolchain-15/1:15.0.7-1 was uploaded several weeks ago, shortly
after the transition freeze, but has not migrated to testing due to an
autopkgtest regression (#1029010).

Mesa uses LLVM 15, so the new upstream release is preventing Mesa bug fixes
from migrating, some of them important or even release-critical.

Is this version intended to enter testing in time for Debian 12 'bookworm'?
It seems quite late in the release process for the restructuring that
happened in 1:15.0.6-5~exp1 to be uploaded to unstable, for example.

If this version is meant to enter testing, then please fix the autopkgtest
(I'll follow up to #1029010 with more about that) and coordinate with
the release team to get it into unstable.

Or, if this version is not meant to enter testing, please upload a
version to unstable that is intended for testing (which might involve
reverting some of the changes and/or using a "+really" version), and
then re-upload the newer version to experimental.

For more details of the freeze timeline, please refer to
,
 and
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
On Fri, 03 Mar 2023 at 16:31:09 +, Simon McVittie wrote:
> Is this version intended to enter testing in time for Debian 12 'bookworm'?

On Bug#1032317, Sylvestre Ledru writes:
> yeah, it is intended for bookworm

which is the answer I was looking for, so I'm closing this bug.

After #1032317 is fixed (which I believe should also result in the autopkgtest
regression #1029010 being fixed), please coordinate with the release team
to get an unblock for the updated package so that mesa and rocm-hipamd can
also migrate.

Thanks,
smcv--- End Message ---

Bug#1032168: meson: autopkgtest fills disk completely

[Paul Gevers]

Hi Jussi,

On 08-03-2023 16:13, Jussi Pakkanen wrote:

On Wed, 1 Mar 2023 at 21:09, Paul Gevers  wrote:


No, but e.g. on s390x it never ever came close to filling the disk, so
the peaks of before today here are really new:
https://ci.debian.net/munin/ci-worker-s390x-01/ci-worker-s390x-01/df.html
(but apparently another package is also suddenly misbehaving, so maybe
it's indeed something *below* meson. I'll try to figure out tonight or
tomorrow morning.


Did you manage to discover whether that is the same issue or something
different?


Yes, sorry for not following up. meson was still getting scheduled on 
s390x because the worker prefetched tests from the queue before I 
disallowed meson. So it was meson all the time.


Having said that, let me open the discussion on what I expect from this 
bug. I *don't* expect all tests on our infrastructure to be totally 
resilient to all restrictions we have. Although several tens of GB is a 
lot, I also realize that it isn't *that* much, so if you understand why 
meson suddenly needs considerably more disk space and that's to be 
expected, then I'm fine with closing this bug and have meson on the 
rejectlist for architecture where we don't have enough (or you implement 
restrictions in your test of course). What this bug tries to prevent is 
*accidental* increased requirements that point out a flaw somewhere.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032476: apache2: CVE-2023-25690 CVE-2023-27522

[Moritz Muehlenhoff]

On Wed, Mar 08, 2023 at 07:09:20AM +0400, Yadd wrote:
> On 3/7/23 23:46, Salvatore Bonaccorso wrote:
> > Source: apache2
> > Version: 2.4.55-1
> > Severity: grave
> > Tags: security upstream
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> > 
> > Hi,
> > 
> > The following vulnerabilities were published for apache2.
> > 
> > CVE-2023-25690[0]:
> > 
> > CVE-2023-27522[1]:
> 
> Hi,
> 
> here is the debdiff for Bullseye

I'm fine with a DSA, but we've seen a fair amount of regressions in 2.4.x 
releases,
so let's wait a few days for regressions reported in sid (and Ondreys PHP repo).

You can already upload the new version, though (we can reject/reupload if 
needed).

Cheers,
Moritz

Bug#1030669: Only include in Bookworm with commitment to stable updates

[Moritz Muehlenhoff]

On Wed, Mar 08, 2023 at 02:20:25PM +0100, Marco d'Itri wrote:
0;115;0c> On Feb 14, Moritz Muehlenhoff  wrote:
> 
> > > > Varnish should only be included in Bookworm with a reliable commitment
> > > > by the maintainers to backport/test security fixes across the typical
> > > > three year life cycle (two years of stable-security and one year of
> > > > oldstable-security).
> > > I do not think that this will be helpful for Varnish users.
> > Then someone needs to step up, it's as easy as that.
> Fine: "I hereby commit to backport/test security fixes for varnish 
> across the lifetime of bookworm".

Noted, thanks.

Cheers,
Moritz

Bug#1031964: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

[Graham Inggs]

Hi

Sorry for missing this.  I noticed the empty packages (or at least,
Lintian did!) while sponsoring the upload of 13.4.1-1 to experimental
and fixed it there, but didn't think it important enough to fix for
bookworm.

If someone is willing to do a (team) upload, I'll be happy to unblock it.

Please consider this a release team unblock pre-approval.

Regards
Graham

Bug#1031489: temporary fix

[Alexander Procenko]

qt software uses
libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0×7f0e27e0)
pastebin.com/raw/qNyjpFsv
but load
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
and gives Segmentation Fault
if add this
export QT_XCB_GL_INTEGRATION=none
export QT_OPENGL=software
and starting trough
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libGL.so qbittorrent
software starting without error

Bug#1032517:

[Jan Mojzis]

Hello,
can You please send me the steps how i can reproduce it
- packages list/versions before the upgrade
- exact apt/apt-get command
- packages list/versions after the upgrade

Jan

Bug#1032525: packer: crashes on a very simple template

[Santiago Vila]

Package: packer
Version: 1.6.6+ds1-7
Severity: grave

Hello.

I'm using packer and ansible to create images for GCP.

After upgrading to Debian bookworm, packer crashes on
the most simple template:

$ packer build sample.pkr.hcl
panic: ConfigSpec failed: gob: type cty.Type has no exported fields [recovered]
panic: ConfigSpec failed: gob: type cty.Type has no exported fields

goroutine 1 [running]:
log.Panic({0xc00083e8e8?, 0x0?, 0x0?})
log/log.go:388 +0x65
github.com/hashicorp/packer/packer/plugin.(*cmdBuilder).checkExit(0xc0005e0490?,
 {0x314b860, 0xc0005e04c0}, 0x0)
github.com/hashicorp/packer/packer/plugin/builder.go:47 +0x7f
github.com/hashicorp/packer/packer/plugin.(*cmdBuilder).ConfigSpec.func1()
github.com/hashicorp/packer/packer/plugin/builder.go:19 +0x39
panic({0x314b860, 0xc0005e04c0})
runtime/panic.go:884 +0x212
github.com/hashicorp/packer/packer-plugin-sdk/rpc.(*commonClient).ConfigSpec(0xc00068e9e0)
github.com/hashicorp/packer/packer-plugin-sdk/rpc/common.go:44 +0x297
github.com/hashicorp/packer/packer/plugin.(*cmdBuilder).ConfigSpec(0xc00047f0d0?)
github.com/hashicorp/packer/packer/plugin/builder.go:22 +0x65
github.com/hashicorp/packer/hcl2template.decodeHCL2Spec({0x4447708, 
0xc000483650}, 0xd?, {0x7fc2746a1680?, 0xc0004728a0?})
github.com/hashicorp/packer/hcl2template/decode.go:17 +0x39
github.com/hashicorp/packer/hcl2template.(*PackerConfig).startBuilder(0x3379060?,
 {{0xc000792540, 0xd}, {0xc000792570, 0xa}, 0xc0004cd1e0, {0x0, 0x0}, {0x0, 
0x0}}, ...)
github.com/hashicorp/packer/hcl2template/types.source.go:110 +0x16a
github.com/hashicorp/packer/hcl2template.(*PackerConfig).GetBuilds(0xc00077f320,
 {{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, {0x0, ...}})
github.com/hashicorp/packer/hcl2template/types.packer_config.go:396 
+0xb48
github.com/hashicorp/packer/command.(*BuildCommand).RunContext(0xc53920, 
{0x4447120?, 0xcaa540}, 0xc000782120)
github.com/hashicorp/packer/command/build.go:156 +0x1b5
github.com/hashicorp/packer/command.(*BuildCommand).Run(0xc53920, 
{0xc000112170, 0x1, 0x1})
github.com/hashicorp/packer/command/build.go:40 +0xc5
github.com/mitchellh/cli.(*CLI).Run(0xc000748640)
github.com/mitchellh/cli/cli.go:261 +0x5f8
main.wrappedMain()
github.com/hashicorp/packer/main.go:249 +0xb11
main.realMain()
github.com/hashicorp/packer/main.go:50 +0xf5
main.main()
github.com/hashicorp/packer/main.go:36 +0x19



!!! PACKER CRASH 

Packer crashed! This is always indicative of a bug within Packer.
A crash log has been placed at "crash.log" relative to your current
working directory. It would be immensely helpful if you could please
report the crash with Packer[1] so that we can fix this.

[1]: https://github.com/hashicorp/packer/issues

!!! PACKER CRASH 

This is the template I'm using:

-
locals { timestamp = regex_replace(timestamp(), "[- TZ:]", "") }

source "googlecompute" "buildd-gce" {
  account_file= "my-account-file.json"
  image_family= "debian-12-buildd"
  image_name  = "debian-12-buildd-amd64-${local.timestamp}"
  machine_type= "n1-standard-1"
  disk_size   = 10
  project_id  = "my-project-id"
  source_image_family = "debian-11"
  ssh_username= "packer"
  tags= ["ssh"]
  zone= "us-central1-f"
}

build {
  sources = ["source.googlecompute.buildd-gce"]

  provisioner "ansible" {
extra_arguments = ["--become"]
groups  = ["buildd"]
playbook_file   = "playbooks/buildd-gce.yml"
  }

}
-

I'm also attaching the crash.log file.


For completeness: Version 1.8.6 from github does not crash, but it has
two subtle incompatibilities with openssh-client in bookworm:

https://github.com/hashicorp/packer-plugin-ansible/issues/140
https://github.com/hashicorp/packer/issues/11783

I was going to report those issues here for documentation purposes,
as both of them have workarounds. but then I found the Debian
version seems not to work at all.

Thanks.2023/03/08 18:30:02 [INFO] Packer version: 1.6.6 [go1.19.6 linux amd64]
2023/03/08 18:30:02 Checking 'PACKER_CONFIG' for a config file path
2023/03/08 18:30:02 'PACKER_CONFIG' not set; checking the default config file path
2023/03/08 18:30:02 Attempting to open config file: /home/bluser/.packerconfig
2023/03/08 18:30:02 [WARN] Config file doesn't exist: /home/bluser/.packerconfig
2023/03/08 18:30:02 Setting cache directory: /home/bluser/packer_cache
2023/03/08 18:30:02 [TRACE] validateValue: not active for timestamp, so skipping
2023/03/08 18:30:02 [TRACE] validateValue: not active for timestamp, so skipping
2023/03/08 18:30:02 [TRACE] validateValue: not active for timestamp, 

Processed: affects 1032316

[Debian Bug Tracking System]

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

> affects 1032316 + src:mesa
Bug #1032316 [src:llvm-toolchain-15] llvm-toolchain-15: is this version 
intended for Debian 12 'bookworm'?
Added indication that 1032316 affects src:mesa
> thanks
Stopping processing here.

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

Bug#1032316: llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?

[Simon McVittie]

On Mon, 06 Mar 2023 at 21:35:41 +0100, Étienne Mollier wrote:
> Simon McVittie, on 2023-03-03:
> > llvm-toolchain-15/1:15.0.7-1 was uploaded several weeks ago, shortly
> > after the transition freeze, but has not migrated to testing due to an
> > autopkgtest regression (#1029010).
> 
> I subscribe the debian-ai mailing list.  The ROCm compiler is
> currently built on top of llvm-toolchain-15, and moving back to
> the llvm-toolchain-14 may require some non-trivial effort if the
> latter were to not target Debian 12 bookworm.

There is *a* version of llvm-toolchain-15 in bookworm, version 1:15.0.6-4,
which is used by the rocm-hipamd_5.2.3-1 and mesa_22.3.3-1 in bookworm.
I'm not suggesting that 1:15.0.6-4 should be *removed*. What I'm asking
here is whether it's intended to be upgraded to 1:15.0.7-1 (or presumably
a later version where #1029010 has been fixed), or kept at 1:15.0.6-4.

It looks as though rocm-hipamd and mesa are in a very similar situation,
actually: each one has a newer version in unstable which fixes a RC bug
currently present in bookworm (#1021643 in rocm-hipamd, #1029731 in mesa)
but cannot migrate because it's blocked by llvm-toolchain-15_1:15.0.7-1
not migrating.

smcv

Processed: Forwarded upstream (Was: salmon call causing pigx-rnaseq to infinitely loop)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1028713 [salmon] salmon call causing pigx-rnaseq to infinitely loop
Added tag(s) upstream.
> forwarded -1 https://github.com/COMBINE-lab/salmon/issues/835
Bug #1028713 [salmon] salmon call causing pigx-rnaseq to infinitely loop
Set Bug forwarded-to-address to 
'https://github.com/COMBINE-lab/salmon/issues/835'.

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

Bug#1028713: Forwarded upstream (Was: salmon call causing pigx-rnaseq to infinitely loop)

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/COMBINE-lab/salmon/issues/835

Bug#1029010: llvm-toolchain-15: autopkgtest regression

[Faidon Liambotis]

On Wed, Mar 08, 2023 at 09:41:21AM +, Simon McVittie wrote:
> > there is a metapackage, libc++-dev-wasm32, which Depends on the
> > default implementation, which is libc++-14-dev-wasm32 right now. That
> > metapackage has at least one notable reverse B-D, firefox, using it to
> > build certain security/sandboxing features (RLBox[1], AIUI). That is to
> > say, this feature works (w/ 14) and does very useful things today. it
> > (seemingly) broke when it was ported to llvm-toolchain-15, which
> > src:firefox does not depend on directly.
> 
> If I understand correctly, that doesn't *necessarily* have to be RC for
> bookworm, because llvm-toolchain-15 is not (yet!) the default version
> of LLVM provided by the metapackage, and is only used by Mesa? But it
> would be a blocker for either moving the default forward from 14 to 15
> (as has already been done in experimental), or making Firefox use the
> non-default 15 toolchain like Mesa does, presumably to get some new
> feature or optimization that isn't in 14?

At least as I also understand it, that's right. 

I think it'd be a pity to revert this for 15 and we should aim for
feature parity between the two branches, but disabling it is, and can
remain an option as a plan B given where we are in the bookworm release
cycle. That's IMHO, with a biased view, as the wasm patches author, but
ultimately up to the maintainer (which is definitely not me ;).

I'm hopeful we can address the underlying issue quickly though, and I
propose to put a hold to this conversation for the time being and see
where we get with a proper resolution first. I just posted a patch in
the other bug report. Fingers crossed.

Faidon

Bug#1032517: nginx settings deleted on upgrade

[Piotr Jurkiewicz]

I can confirm this bug. Happened to me twice yesterday. The problem 
occurs also when pruning is being done after system upgrade, in a 
separate step.

Bug#1032168: meson: autopkgtest fills disk completely

[Jussi Pakkanen]

On Wed, 1 Mar 2023 at 21:09, Paul Gevers  wrote:

> No, but e.g. on s390x it never ever came close to filling the disk, so
> the peaks of before today here are really new:
> https://ci.debian.net/munin/ci-worker-s390x-01/ci-worker-s390x-01/df.html
> (but apparently another package is also suddenly misbehaving, so maybe
> it's indeed something *below* meson. I'll try to figure out tonight or
> tomorrow morning.

Did you manage to discover whether that is the same issue or something
different?

Processed: Re: Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #982794 [firefox-esr] firefox-esr/armhf: fails on non-NEON systems
Added tag(s) patch.

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

Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

[Emanuele Rocca]

Control: tags -1 + patch

On Fri, Mar 03, 2023 at 03:13:15PM +0100, Emanuele Rocca wrote:
> Firefox seems to erroneously enable NEON in places where it shouldn't. Trying
> to figure out exactly where and what's the best way to address this.

Patch attached.

According to the large disclaimer in moz.build one should not touch that file
but instead modify generate_mozbuild.py. It seems to me however that changes to
the python script are not automatically applied to moz.build?

In any case with the attached patch firefox-esr builds properly for armhf and
works fine here emulating a cortex-r5f CPU.

Thanks,
  ema
Index: firefox-esr-102.8.0esr/gfx/skia/moz.build
===
--- firefox-esr-102.8.0esr.orig/gfx/skia/moz.build
+++ firefox-esr-102.8.0esr/gfx/skia/moz.build
@@ -455,8 +455,6 @@ if CONFIG['INTEL_ARCHITECTURE']:
 SOURCES['skia/src/opts/SkOpts_sse42.cpp'].flags += ['-msse4.2']
 SOURCES['skia/src/opts/SkOpts_avx.cpp'].flags += ['-mavx']
 SOURCES['skia/src/opts/SkOpts_hsw.cpp'].flags += ['-mavx2', '-mf16c', '-mfma']
-elif CONFIG['CPU_ARCH'] == 'arm' and CONFIG['CC_TYPE'] in ('clang', 'gcc'):
-CXXFLAGS += CONFIG['NEON_FLAGS']
 elif CONFIG['CPU_ARCH'] == 'aarch64' and CONFIG['CC_TYPE'] in ('clang', 'gcc'):
 SOURCES['skia/src/opts/SkOpts_crc32.cpp'].flags += ['-march=armv8-a+crc']
 

Processed: tagging 1008320

[Debian Bug Tracking System]

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

> tags 1008320 + pending
Bug #1008320 [src:ocrfeeder] ocrfeeder: CVE-2022-27811
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Guilhem Moulin]

On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
>> No please don't, #-1 is RC so that would block transitioning into
>> Bookworm which only supports merged-usr…  Will fix that later during
>> the
>> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
>> further delay the transition.
>
> Well but at least right now people without merged /usr will still end
> up in a broken system?

Yes.  Been the case for a week (since the argon2=0~20190702-0.1 upload).
However the TC has ruled that these systems are no longer supported, so
the issue isn't RC.  Not saying we should shove it under the carpet,
only that it shouldn't delay transition.

> And there is no guarantee that /usr has already been merged at that
> point... I mean it should, when the upgrade to bookwork completes...
> but can it happen that it's interrupted? Or that people do it in
> several steps? Then they could upgrade argon2, reboot and have the
> missing libgcc.

Correct, but AFAICT that's would be a FrankenDebian so not something
supported either.  Either way that's not something src:cryptsetup can
fix.  One could upload src:argon2 again adding “Break: cryptsetup-initramfs
(<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing
given the freeze and the fact that covered that supported systems are
covered.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1030669: marked as done (Only include in Bookworm with commitment to stable updates)

[Debian Bug Tracking System]

Your message dated Wed, 8 Mar 2023 14:20:25 +0100
with message-id 
and subject line Re: Bug#1030669: Only include in Bookworm with commitment to 
stable updates
has caused the Debian Bug report #1030669,
regarding Only include in Bookworm with commitment to stable updates
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.)


-- 
1030669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish
Version: 7.1.1-1.1
Severity: serious

Varnish should only be included in Bookworm with a reliable commitment
by the maintainers to backport/test security fixes across the typical
three year life cycle (two years of stable-security and one year of
oldstable-security).

Especially since testing currently has 7.1, which reaches it's end of
life on March 15 2023 and does not contain the LTS release.

(It's not unlikely that most people who operate a CDN based on Varnish
only use custom/patched/recent packages backported from stable
anyway, which is perfectly fine, but then let's make that explicit
by keeping it out of testing).

Cheers,
 Moritz
--- End Message ---
--- Begin Message ---
On Feb 14, Moritz Muehlenhoff  wrote:

> > > Varnish should only be included in Bookworm with a reliable commitment
> > > by the maintainers to backport/test security fixes across the typical
> > > three year life cycle (two years of stable-security and one year of
> > > oldstable-security).
> > I do not think that this will be helpful for Varnish users.
> Then someone needs to step up, it's as easy as that.
Fine: "I hereby commit to backport/test security fixes for varnish 
across the lifetime of bookworm".

I manage about 150 instances of Varnish, so let's just assume that 
I have the experience needed and some motivation.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Processed: closing 1032221 ...

[Debian Bug Tracking System]

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

> close 1032221 2:2.6.1-2
Bug #1032221 [cryptsetup-initramfs] cryptsetup: libgcc_s.so.1 must be installed 
for pthread_exit to work
Marked as fixed in versions cryptsetup/2:2.6.1-2.
Bug #1032221 [cryptsetup-initramfs] cryptsetup: libgcc_s.so.1 must be installed 
for pthread_exit to work
Marked Bug as done
> retitle 1032518 cryptsetup-initramfs: libgcc_s.so.1 missing on non-merged-usr 
> systems
Bug #1032518 [cryptsetup-initramfs] cryptsetup: libgcc_s.so.1 must be installed 
for pthread_exit to work
Changed Bug title to 'cryptsetup-initramfs: libgcc_s.so.1 missing on 
non-merged-usr systems' from 'cryptsetup: libgcc_s.so.1 must be installed for 
pthread_exit to work'.
> thanks
Stopping processing here.

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

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Christoph Anton Mitterer]

On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr…  Will fix that later during
> the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the transition.

Well but at least right now people without merged /usr will still end
up in a broken system?

And there is no guarantee that /usr has already been merged at that
point... I mean it should, when the upgrade to bookwork completes...
but can it happen that it's interrupted? Or that people do it in
several steps? Then they could upgrade argon2, reboot and have the
missing libgcc.

Anyway... thanks for taking care :-)


Cheers,
Chris.

Processed (with 1 error): Re: Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1032221 [cryptsetup-initramfs] cryptsetup: libgcc_s.so.1 must be installed 
for pthread_exit to work
Bug 1032221 cloned as bug 1032518
> severity -2 important
Bug #1032518 [cryptsetup-initramfs] cryptsetup: libgcc_s.so.1 must be installed 
for pthread_exit to work
Severity set to 'important' from 'grave'
> done -1 2:2.6.1-2
Unknown command or malformed arguments to command.


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

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Guilhem Moulin]

Control: clone -1 -2
Control: severity -2 important
Control: done -1 2:2.6.1-2

On Wed, 08 Mar 2023 at 13:42:53 +0100, Christoph Anton Mitterer wrote:
> @Guilhem, I'm reopening this for now.

No please don't, #-1 is RC so that would block transitioning into
Bookworm which only supports merged-usr…  Will fix that later during the
freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
further delay the transition.

-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: Re: [pkg-cryptsetup-devel] Bug#1032221: Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1032221 {Done: Guilhem Moulin } [cryptsetup-initramfs] 
cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work
'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 cryptsetup/2:2.6.1-2.

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

Bug#1032517: nginx settings deleted on upgrade

[Ralf Jung]

Package: nginx
Version: 1.22.1-7
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

last weekend I did an "apt upgrade" of my system as usual, asking apt to prune 
configuration files for packages that are being uninstalled.
Now I realize that my nginx stopped working, and it turns out its configuration 
files are just completely gone.
Look like the recent package reorganization went wrong and actually deletes 
configuration under certain conditions -- that's pretty bad.
Package updates shouldn't cause a loss of configuration files, even when 
pruning packages that are not present any more.

Kind regards,
Ralf

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

Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
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 nginx depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  iproute2   6.1.0-1
ii  libc6  2.36-8
ii  libcrypt1  1:4.4.33-2
ii  libpcre2-8-0   10.42-1
ii  libssl33.0.8-1
ii  zlib1g 1:1.2.13.dfsg-1

nginx recommends no packages.

Versions of packages nginx suggests:
ii  fcgiwrap   1.1.0-14
pn  nginx-doc  
ii  ssl-cert   1.1.2

-- Configuration Files:
/etc/nginx/fastcgi.conf [Errno 2] No such file or directory: 
'/etc/nginx/fastcgi.conf'
/etc/nginx/fastcgi_params [Errno 2] No such file or directory: 
'/etc/nginx/fastcgi_params'
/etc/nginx/koi-utf [Errno 2] No such file or directory: '/etc/nginx/koi-utf'
/etc/nginx/koi-win [Errno 2] No such file or directory: '/etc/nginx/koi-win'
/etc/nginx/mime.types [Errno 2] No such file or directory: 
'/etc/nginx/mime.types'
/etc/nginx/nginx.conf [Errno 2] No such file or directory: 
'/etc/nginx/nginx.conf'
/etc/nginx/proxy_params [Errno 2] No such file or directory: 
'/etc/nginx/proxy_params'
/etc/nginx/scgi_params [Errno 2] No such file or directory: 
'/etc/nginx/scgi_params'
/etc/nginx/sites-available/default [Errno 2] No such file or directory: 
'/etc/nginx/sites-available/default'
/etc/nginx/snippets/fastcgi-php.conf [Errno 2] No such file or directory: 
'/etc/nginx/snippets/fastcgi-php.conf'
/etc/nginx/snippets/snakeoil.conf [Errno 2] No such file or directory: 
'/etc/nginx/snippets/snakeoil.conf'
/etc/nginx/uwsgi_params [Errno 2] No such file or directory: 
'/etc/nginx/uwsgi_params'
/etc/nginx/win-utf [Errno 2] No such file or directory: '/etc/nginx/win-utf'

-- debconf information:
  nginx/log-symlinks:

Bug#1032221: [pkg-cryptsetup-devel] Bug#1032221: Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Christoph Anton Mitterer]

Control: reopen -1

On Wed, 2023-03-08 at 08:16 +0100, Milan Broz wrote:
> Just upstream is no longer responding here...

Seems upstream is dead... I also have some minor PRs open against
argon2, but no response. Tried to get directly in contact with some of
them, but the same.

@Guilhem, I'm reopening this for now.


Cheers,
Chris.

Bug#1031765: pgrep: signal handler matching breaks argument parsing

[Heinrich Schuchardt]

Upstream has merged https://github.com/ganeti/ganeti/pull/1692, commit 
9cd67e6a81c6 ("uidpool_unittest: avoid using negative UIDs") to solve 
the issue.


Additionally the following patch is needed to fix a separate problem 
with testing:

a40748ab26fc ("py-tests: make tests compatible with roman 3.2+")

Best regards

Heinrich

Bug#1032506: marked as done (plantuml: crashes on startup)

[Debian Bug Tracking System]

Your message dated Wed, 08 Mar 2023 11:49:45 +
with message-id 
and subject line Bug#1032506: fixed in plantuml 1:1.2020.2+ds-3
has caused the Debian Bug report #1032506,
regarding plantuml: crashes on startup
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.)


-- 
1032506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plantuml
Version: 1:1.2020.2+ds-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vic...@westerhu.is

Hi maintainer,

Plantuml immediately crashes on startup with the following stacktrace:

Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2393)
at java.base/java.lang.Runtime.load0(Runtime.java:755)
at java.base/java.lang.System.load(System.java:1953)
at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
at 
java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
at 
java.base/jdk.internal.loader.NativeLibraries.findFromPaths(NativeLibraries.java:315)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:285)
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2398)
at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:818)
at java.base/java.lang.System.loadLibrary(System.java:1989)
at java.desktop/java.awt.image.ColorModel$1.run(ColorModel.java:210)
at java.desktop/java.awt.image.ColorModel$1.run(ColorModel.java:208)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at 
java.desktop/java.awt.image.ColorModel.loadLibraries(ColorModel.java:207)
at java.desktop/java.awt.image.ColorModel.(ColorModel.java:220)
at 
java.desktop/java.awt.image.BufferedImage.(BufferedImage.java:286)
at net.sourceforge.plantuml.FileFormat.(FileFormat.java:90)
at net.sourceforge.plantuml.Option.(Option.java:94)
at net.sourceforge.plantuml.Run.main(Run.java:88)

The requested library, /usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so,
is found in openjdk-17-jre, which is not a dependency of default-jre-headless.
It is, however, a dependency of default-jre. Manually installing default-jre
does indeed solve the error.

--
Groet, Regards,

Victor Westerhuis

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

Kernel: Linux 6.1.14+ (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plantuml depends on:
ii  default-jre-headless  2:1.17-74
ii  libavalon-framework-java  4.2.0-10
ii  libbatik-java 1.16+dfsg-1
ii  libcommons-io-java2.11.0-2
ii  libcommons-logging-java   1.2-3
ii  libfop-java   1:2.8-2
ii  libjlatexmath-java1.0.7-3
ii  libxml-commons-external-java  1.4.01-5
ii  libxmlgraphics-commons-java   2.8-2

Versions of packages plantuml recommends:
ii  graphviz  2.42.2-7+b3

plantuml suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: plantuml
Source-Version: 1:1.2020.2+ds-3
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated plantuml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Mar 

Processed: Update version information

[Debian Bug Tracking System]

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

> found 1032506 plantuml/1:1.2020.2+ds-1
Bug #1032506 [plantuml] plantuml: crashes on startup
Marked as found in versions plantuml/1:1.2020.2+ds-1.
> thanks
Stopping processing here.

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

Processed: severity of 1010347 is grave

[Debian Bug Tracking System]

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

> severity 1010347 grave
Bug #1010347 [src:cloudcompare] cloudcompare: CVE-2021-21897 - heap-based 
buffer overflow loading a DXF file via embedded dxflib
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1032506: plantuml: crashes on startup

[Victor Westerhuis]

Hi (again) Andrej,

Victor Westerhuis schreef op 08.03.2023 10:56:

Control: severity -1 important

Hi Andrej,

Thanks for the quick response.

Andrej Shadura schreef op 08.03.2023 10:44:

Hi,

On Wed, 8 Mar 2023, at 10:36, Victor Westerhuis wrote:

Package: plantuml
Version: 1:1.2020.2+ds-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vic...@westerhu.is

Hi maintainer,

Plantuml immediately crashes on startup with the following 
stacktrace:


The requested library, 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so,
is found in openjdk-17-jre, which is not a dependency of 
default-jre-headless.
It is, however, a dependency of default-jre. Manually installing 
default-jre

does indeed solve the error.


Thanks for the bug report. Does this happen always, or with some
specific command-line options? I was told before that plantuml is
known to work headless as well, although I hadn’t tested it myself.


The issue is in
https://salsa.debian.org/debian/plantuml/-/blob/master/debian/plantuml.sh#L29-32:
if the DISPLAY environment variable is unset the headless AWT backend
is requested, which is correct. However, the opposite is not
necessarily true: if DISPLAY is set, default-jre is not necessarily
installed.
I have opened a MR on Salsa with a fix at 
https://salsa.debian.org/debian/plantuml/-/merge_requests/3.


I have downgraded the severity, because explicitly unsetting DISPLAY
before calling /usr/bin/plantuml fixes the crash.

--
Groet, Regards,

Victor Westerhuis

--
Groet, Regards,

Victor Westerhuis

Bug#1032510: packagekit: pkcon what-provides application/x-keepass2 makes PK crash

[Laurent Bigonville]

Package: packagekit
Version: 1.2.6-3
Severity: serious

Hello,

pkcon what-provides application/x-keepass2 makes PK crash:

$ pkcon what-provides application/x-keepass2
Getting provides[=]
Loading cache   [=]
Querying[=] e 
daemon crashed mid-transaction!
Finished[ ] (0%)

   Stack trace of thread 10447:
#0  0x7faf3ef75ccc __pthread_kill_implementation (libc.so.6 
+ 0x8accc)
#1  0x7faf3ef26ef2 __GI_raise (libc.so.6 + 0x3bef2)
#2  0x7faf3ef11472 __GI_abort (libc.so.6 + 0x26472)
#3  0x7faf3c89d919 
_ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x9d919)
#4  0x7faf3c8a8e1a _ZN10__cxxabiv111__terminateEPFvvE 
(libstdc++.so.6 + 0xa8e1a)
#5  0x7faf3c8a8e85 _ZSt9terminatev (libstdc++.so.6 + 
0xa8e85)
#6  0x7faf3c8a90d8 __cxa_throw (libstdc++.so.6 + 0xa90d8)
#7  0x7faf3c8a00e4 _ZSt19__throw_logic_errorPKc 
(libstdc++.so.6 + 0xa00e4)
#8  0x7faf3e96cb3a 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC4IS3_EEPKcRKS3_ 
(libpk_backend_apt.so + 0x2cb3a)
#9  0x7faf3e95d122 backend_what_provides_thread 
(libpk_backend_apt.so + 0x1d122)
#10 0x5644cb0c7aca pk_backend_job_thread_setup (packagekitd 
+ 0x23aca)
#11 0x7faf3f5dbcfd g_thread_proxy (libglib-2.0.so.0 + 
0x7ecfd)
#12 0x7faf3ef73fd4 start_thread (libc.so.6 + 0x88fd4)
#13 0x7faf3eff466c __clone3 (libc.so.6 + 0x10966c)


This breaks GNOME ability to suggest which application to install when
opening files.

Feel free to downgrade the severity if you want.

Kind regards,
Laurent Bigonville


-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages packagekit depends on:
ii  init-system-helpers 1.65.2
ii  libappstream4   0.16.1-1
ii  libapt-pkg6.0   2.6.0
ii  libc6   2.36-8
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-1
ii  libglib2.0-bin  2.74.6-1
ii  libgstreamer1.0-0   1.22.0-2
ii  libpackagekit-glib2-18  1.2.6-3
ii  libpolkit-gobject-1-0   122-3
ii  libsqlite3-03.40.1-1
ii  libstdc++6  12.2.0-14
ii  libsystemd0 252.6-1
ii  polkitd 122-3

Versions of packages packagekit recommends:
ii  packagekit-tools  1.2.6-3
ii  systemd   252.6-1

Versions of packages packagekit suggests:
ii  appstream  0.16.1-1

-- no debconf information

Bug#1032506: plantuml: crashes on startup

[Andrej Shadura]

Hi,

On Wed, 8 Mar 2023, at 10:36, Victor Westerhuis wrote:
> Package: plantuml
> Version: 1:1.2020.2+ds-2
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: vic...@westerhu.is
>
> Hi maintainer,
>
> Plantuml immediately crashes on startup with the following stacktrace:

> The requested library, /usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so,
> is found in openjdk-17-jre, which is not a dependency of default-jre-headless.
> It is, however, a dependency of default-jre. Manually installing default-jre
> does indeed solve the error.

Thanks for the bug report. Does this happen always, or with some specific 
command-line options? I was told before that plantuml is known to work headless 
as well, although I hadn’t tested it myself.

-- 
Cheers,
  Andrej

Bug#1029010: llvm-toolchain-15: autopkgtest regression

[Simon McVittie]

On Wed, 08 Mar 2023 at 03:11:57 +0200, Faidon Liambotis wrote:
> On Fri, Mar 03, 2023 at 05:46:15PM +, Simon McVittie wrote:
> > I don't think this is *really* a regression, because in the version in
> > bookworm, the autopkgtest didn't exercise compilation of C++ into
> > WebAssembly at all.
> 
> This statement strictly speaking is true, but applies only if you look
> at LLVM 15 in isolation. It *is* a regression, in the sense that this
> works with llvm-toolchain-14, where the WebAssembly work was first
> pushed, today, in both bookworm and sid. For example, retracing your
> steps in #1032317 with s/15/14/ does not result into a failure.

Sorry, I was confused by the binary package reorganization in the
llvm-toolchain-15 toolchain since it forked from -14, and I hadn't
realised that -14 had undergone equivalent restructuring to enable
WASM support. Yes, this is a regression since -14, even if it isn't
a regression since the -15 in bookworm.

> there is a metapackage, libc++-dev-wasm32, which Depends on the
> default implementation, which is libc++-14-dev-wasm32 right now. That
> metapackage has at least one notable reverse B-D, firefox, using it to
> build certain security/sandboxing features (RLBox[1], AIUI). That is to
> say, this feature works (w/ 14) and does very useful things today. it
> (seemingly) broke when it was ported to llvm-toolchain-15, which
> src:firefox does not depend on directly.

If I understand correctly, that doesn't *necessarily* have to be RC for
bookworm, because llvm-toolchain-15 is not (yet!) the default version
of LLVM provided by the metapackage, and is only used by Mesa? But it
would be a blocker for either moving the default forward from 14 to 15
(as has already been done in experimental), or making Firefox use the
non-default 15 toolchain like Mesa does, presumably to get some new
feature or optimization that isn't in 14?

smcv

Bug#1032506: plantuml: crashes on startup

[Victor Westerhuis]

Package: plantuml
Version: 1:1.2020.2+ds-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vic...@westerhu.is

Hi maintainer,

Plantuml immediately crashes on startup with the following stacktrace:

Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2393)
at java.base/java.lang.Runtime.load0(Runtime.java:755)
at java.base/java.lang.System.load(System.java:1953)
at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
at 
java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
at 
java.base/jdk.internal.loader.NativeLibraries.findFromPaths(NativeLibraries.java:315)
at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:285)
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2398)
at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:818)
at java.base/java.lang.System.loadLibrary(System.java:1989)
at java.desktop/java.awt.image.ColorModel$1.run(ColorModel.java:210)
at java.desktop/java.awt.image.ColorModel$1.run(ColorModel.java:208)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at 
java.desktop/java.awt.image.ColorModel.loadLibraries(ColorModel.java:207)
at java.desktop/java.awt.image.ColorModel.(ColorModel.java:220)
at 
java.desktop/java.awt.image.BufferedImage.(BufferedImage.java:286)
at net.sourceforge.plantuml.FileFormat.(FileFormat.java:90)
at net.sourceforge.plantuml.Option.(Option.java:94)
at net.sourceforge.plantuml.Run.main(Run.java:88)

The requested library, /usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so,
is found in openjdk-17-jre, which is not a dependency of default-jre-headless.
It is, however, a dependency of default-jre. Manually installing default-jre
does indeed solve the error.

--
Groet, Regards,

Victor Westerhuis

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

Kernel: Linux 6.1.14+ (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plantuml depends on:
ii  default-jre-headless  2:1.17-74
ii  libavalon-framework-java  4.2.0-10
ii  libbatik-java 1.16+dfsg-1
ii  libcommons-io-java2.11.0-2
ii  libcommons-logging-java   1.2-3
ii  libfop-java   1:2.8-2
ii  libjlatexmath-java1.0.7-3
ii  libxml-commons-external-java  1.4.01-5
ii  libxmlgraphics-commons-java   2.8-2

Versions of packages plantuml recommends:
ii  graphviz  2.42.2-7+b3

plantuml suggests no packages.

-- no debconf information

Bug#1031794: socklog: fails to extract source package: dpkg-source: error: pathname 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points outside source root (to '/run/runit/supervis

[Mathieu Mirmont]

Hi,

Sorry for the noise on this ticket, it looks like every git push
triggered an email here. I have fixed this silly bug and prepared a
new package to upload, it is on mentors [1]. I would really appreciate
if someone could upload it before socklog is removed from testing.

[1] https://mentors.debian.net/package/socklog/

Cheers,

Mathieu.


On Wed, Feb 22, 2023 at 09:45:29PM +0100, Lucas Nussbaum wrote:
> Source: socklog
> Version: 2.1.0+repack-4
> Severity: serious
> 
> Hi,
> 
> # dget 
> https://deb.debian.org/debian/pool/main/s/socklog/socklog_2.1.0+repack-4.dsc
> dget: retrieving 
> https://deb.debian.org/debian/pool/main/s/socklog/socklog_2.1.0+repack-4.dsc
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  1980  100  19800 0   8615  0 --:--:-- --:--:-- --:--:--  8646
> dget: retrieving 
> https://deb.debian.org/debian/pool/main/s/socklog/socklog_2.1.0+repack.orig.tar.gz
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100 59796  100 597960 0   162k  0 --:--:-- --:--:-- --:--:--  163k
> dget: retrieving 
> https://deb.debian.org/debian/pool/main/s/socklog/socklog_2.1.0+repack-4.debian.tar.xz
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100 11080  100 110800 0  46909  0 --:--:-- --:--:-- --:--:-- 46751
> socklog_2.1.0+repack-4.dsc:
>   Good signature found
>validating socklog_2.1.0+repack.orig.tar.gz
>validating socklog_2.1.0+repack-4.debian.tar.xz
> All files validated successfully.
> dpkg-source: info: extracting socklog in socklog-2.1.0+repack
> dpkg-source: info: unpacking socklog_2.1.0+repack.orig.tar.gz
> dpkg-source: info: unpacking socklog_2.1.0+repack-4.debian.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: applying 0001-socklog-conf-update-service.patch
> dpkg-source: info: applying 0002-tryto-c.patch
> dpkg-source: info: applying 0003-patches-fix-build-warnings.patch
> dpkg-source: error: pathname 
> 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points 
> outside source root (to '/run/runit/supervise/socklog-unix.log')
> 
> That's on a system with a mix of testing and unstable. I'm not sure of
> which package introduced that additional check. Let me know if you
> cannot reproduce.
> 
> Lucas
> 

-- 
Mathieu Mirmont 


signature.asc
Description: Digital signature