Bug#1007736: marked as done (backbone: autopkgtest regression: node: command not found)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2022 05:33:42 +
with message-id 
and subject line Bug#1007736: fixed in backbone 1.4.1~dfsg+~1.4.15-2
has caused the Debian Bug report #1007736,
regarding backbone: autopkgtest regression: node: command not found
to be marked as done.

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

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


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

Source: backbone
Version: 1.4.1~dfsg+~1.4.15-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
backbone   from testing1.4.1~dfsg+~1.4.15-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looks like 
you're missing a test dependency.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/b/backbone/20012303/log.gz

bash: line 1: node: command not found
autopkgtest [16:13:17]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: backbone
Source-Version: 1.4.1~dfsg+~1.4.15-2
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated backbone 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, 16 Mar 2022 06:19:33 +0100
Source: backbone
Architecture: source
Version: 1.4.1~dfsg+~1.4.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1007736
Changes:
 backbone (1.4.1~dfsg+~1.4.15-2) unstable; urgency=medium
 .
   * Team upload
   * Fix old-style autopkgtest (Closes: 1007736)
Checksums-Sha1: 
 54315ca5ca1513391705fdf7fc2a11ddc1bf48df 2608 backbone_1.4.1~dfsg+~1.4.15-2.dsc
 02e317d274f82aed9089a83e1485e96670a350ad 10688 
backbone_1.4.1~dfsg+~1.4.15-2.debian.tar.xz
Checksums-Sha256: 
 0aad45397570c60294fa4b7ec0aa7780e795563715397f11a2e862414939fb59 2608 
backbone_1.4.1~dfsg+~1.4.15-2.dsc
 1bc314dff0f43017e3b7610656cf8e11de1199574e3259b0f42a4519b873c48e 10688 
backbone_1.4.1~dfsg+~1.4.15-2.debian.tar.xz
Files: 
 c3ca5cfecbe72819088b9216b7f58026 2608 javascript optional 
backbone_1.4.1~dfsg+~1.4.15-2.dsc
 6556e92e9576c8dc80e16aa82d906709 10688 javascript optional 
backbone_1.4.1~dfsg+~1.4.15-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIxc6YACgkQ9tdMp8mZ
7umtfw/8Cg8ykDfaIwBjzmtO0hgTejM6j/lycF6zwIH84zjx064hRSE+0vgAFWuH
kPumwLKte/DX1wJ4Kz+wSpQGGbOwl2vVAR0bzxt0NdsvGWm4CFzS2rTlaPR0SmR7
XC2nEHMfiI6ZH92qer/cQIXkieXHQwgx3tdnBDGABv3TWkLB7MKby/dG6eKaxIxK
l9SeAhINw4p+6Q6IlgNBUF01qMdEl2BSRUMe6eaOuC8jss87UFR/Ec1hyAcX8jEI
TyhpkruPQSz52b5DJRuz0uU+QylnIgmoW4sOGgiztTMfHKXlknzTMilPAZSrCyUY
j/iqhmFrRqzIvY649SQSA46fWsoGSDvtLefaHQ0MPK9JVdxQre6o2lcXdradIryI
gQdCpr0vrbwQc1Vd+0WP51lKVLXYidy9/UFG8rIBWTckQjCPFhPcQceJBEzaOFAj
CUlLrthiY0LWPHVhLoJMZxT1Qks9YCWYMe5aulI2qjgqAmlBhbPrEcAePctR88GZ
78GPJ7aAbjuGrczq/uWgomQhWuqjiiBgEVKQJ306IhPYOlS0gNoniezxthu3IoML
5WXNFEiNKtfNspE/58XP4g2nYSbppBYKXAg4Jm0r8ORFa4LtjmafuOfeOaiZUgjx
9c0RoN/P+kAKhKz7GW2jeNNs2Wya6IdiCNC4RAmNBEppdQJWLBc=
=+bn3
-END PGP SIGNATURE End Message ---

Bug#1006088: marked as done (fonts-smc-manjari: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2022 10:28:13 +0530
with message-id 

and subject line Re: Unreproducible
has caused the Debian Bug report #1006088,
regarding fonts-smc-manjari: FTBFS: pkg_resources.DistributionNotFound: The 
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)


-- 
1006088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-smc-manjari
Version: 2.000-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>   BUILDManjari-Regular.otf
>   BUILDManjari-Bold.otf
>   BUILDManjari-Thin.otf
> Traceback (most recent call last):
>   File "/usr/bin/fontmake", line 33, in 
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts', 
> 'fontmake')())
>   File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
>   File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1030, in _gcd_import
>   File "", line 1007, in _find_and_load
>   File "", line 986, in _find_and_load_unlocked
>   File "", line 680, in _load_unlocked
>   File "", line 850, in exec_module
>   File "", line 228, in _call_with_frames_removed
>   File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in 
> 
> from ufo2ft import CFFOptimization
>   File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in 
> 
> from ufo2ft.featureCompiler import (
>   File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14, 
> in 
> from ufo2ft.featureWriters import (
>   File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py", 
> line 11, in 
> from .markFeatureWriter import MarkFeatureWriter
>   File 
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py", 
> line 9, in 
> from ufo2ft.fontInfoData import getAttrWithFallback
>   File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in 
> 
> from fontTools import ufoLib
>   File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8, 
> in 
> import fs
>   File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in 
> __import__("pkg_resources").declare_namespace(__name__)  # type: ignore
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267, 
> in 
> def _initialize_master_working_set():
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241, 
> in _call_aside
> f(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279, 
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573, 
> in _build_master
> ws.require(__requires__)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891, 
> in require
> needed = self.resolve(parse_requirements(requirements))
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777, 
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution 
> was not found and is required by fonttools
> make[1]: *** [Makefile:27: build/Manjari-Regular.otf] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/fonts-smc-manjari_2.000-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: fonts-smc-manjari
Version: 2.000-2

fixed 1006088 2.000-2
thanks

Can't reproduce this in local or Gitlab CI:

Closing.

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
--- End Message ---

Processed (with 2 errors): Re: Unreproducible

[Debian Bug Tracking System]

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

> Source: fonts-smc-manjari
Unknown command or malformed arguments to command.
> Version: 2.000-2
Unknown command or malformed arguments to command.
> fixed 1006088 2.000-2
Bug #1006088 {Done: Kartik Mistry } [src:fonts-smc-manjari] 
fonts-smc-manjari: FTBFS: pkg_resources.DistributionNotFound: The 
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
Marked as fixed in versions fonts-smc-manjari/2.000-2; no longer marked as 
fixed in versions 2.000-2.
> thanks
Stopping processing here.

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

Bug#1007740: curl breaks xmltooling autopkgtest

[Cantor, Scott]

On 3/15/22, 8:08 PM, "Daniel Stenberg"  wrote:

>This is probably the same issue as Bug #1007739. Triggered by a bug in 
> curl 
>for CN-only certificates:

Ah, probably is. This vhost does use a self-signed cert with a CN only, not 
Let's Encrypt, and I can't think why else it would be failing, so that seems 
likely. The macport is on 7.82 so I can't easily check this quickly, but this 
seems a pretty safe bet. Thanks for saving me more time.

-- Scott

Bug#1004330: marked as done (dokuwiki: No more works with PHP 8.1: Array and string offset access syntax with curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line 557)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2022 00:49:18 +
with message-id 
and subject line Bug#1004330: fixed in dokuwiki 0.0.20200729-0.1
has caused the Debian Bug report #1004330,
regarding dokuwiki: No more works with PHP 8.1: Array and string offset access 
syntax with curly braces is no longer supported in 
/usr/share/dokuwiki/inc/init.php on line 557
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.)


-- 
1004330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dokuwiki
Severity: serious
Version: 0.0.20180422.a-2.1
Tags: fixed-upstream

Dokuwiki broke when PHP was upgraded to 8.1 (now in testing):

[Tue Jan 25 03:54:31.666206 2022] [php:error] [pid 1959] [client 
127.0.0.1:39658] PHP Fatal error:  Array and string offset access syntax with 
curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line 
557

This is very likely fixed upstream, either in the not yet packaged
upstream release 2020-07-29 “Hogfather” ("some preparations for the
upcoming PHP8") or in the upcoming upstream release "Igor" ("Fix various
errors in PHP8 support").

-- System Information:
Debian Release: bookworm/sid  APT prefers testing
(Bug report not written on the server where the issue occurs.)
--- End Message ---
--- Begin Message ---
Source: dokuwiki
Source-Version: 0.0.20200729-0.1
Done: Axel Beckert 

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated dokuwiki package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Mar 2022 22:53:27 +0100
Source: dokuwiki
Architecture: source
Version: 0.0.20200729-0.1
Distribution: unstable
Urgency: medium
Maintainer: Tanguy Ortolo 
Changed-By: Axel Beckert 
Closes: 968453 970926 994877 1004330
Changes:
 dokuwiki (0.0.20200729-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. (Closes: #968453, #970926)
 + Support for PHP 8. (Closes: #1004330)
 + Refresh all patches.
 + Drop no more needed stanzas from debian/copyright. Thanks Lintian!
 + Update copyright years in debian/copyright.
   * Add a debian/gbp.conf to document the non-standard upstream branch.
   * Upgrade Homepage header to HTTPS.
   * Cherry-pick upstream commit 6b6d27d9 to avoid 500 server error in
 lessc.inc.php.
   * debian/postinst: Replace all occurrences of tempfile with mktemp.
 (Closes: #994877)
   * Add symlinks for phpseclib and random-compat under
 /usr/share/dokuwiki/vendor/. See comment in #1004330.
   * Add lintian overrides for wiki pages, translations and similar files
 triggering package-contains-documentation-outside-usr-share-doc.
   * Remove no more emitted lintian overrides, partially also because of
 the new upstream release which no more ships some affected files.
   * debian/{watch,postrm}: Convert comments from ISO-8859 to UTF-8.
Checksums-Sha1:
 f265d469741ed267b9b00a85d514d2e609cb80df 1941 dokuwiki_0.0.20200729-0.1.dsc
 119f3875d023d15070068a6aca1e23acd7f9a19a 3821413 
dokuwiki_0.0.20200729.orig.tar.gz
 0eb137cc1ac5a7e17c54887e1fb2a0b887434279 102448 
dokuwiki_0.0.20200729-0.1.debian.tar.xz
 e377d48b571050f8e2ae5c5003e749674fde1455 6844 
dokuwiki_0.0.20200729-0.1_source.buildinfo
Checksums-Sha256:
 8a86b5695d3429952c41371c7c779105135f8f615c2cbc8cda7326877d8c8b7b 1941 
dokuwiki_0.0.20200729-0.1.dsc
 c787d102bc2b647129fce35eb35399dcd7dd5fb10d1c6b3fb113b43a8eb40b60 3821413 
dokuwiki_0.0.20200729.orig.tar.gz
 40e48dd166d5b94ed448679168fdfd2fcc93d6cdc99b14370cca851aa113dd2a 102448 
dokuwiki_0.0.20200729-0.1.debian.tar.xz
 8ad2d61af6bf66bfe3ffc6bb777f88100b324bdf53b9d70079982fa707dd3db3 6844 
dokuwiki_0.0.20200729-0.1_source.buildinfo
Files:
 a5334fa126129aa64741436a43fd815c 1941 web optional 
dokuwiki_0.0.20200729-0.1.dsc
 8867b6a5d71ecb5203402fe5e8fa18c9 3821413 web optional 
dokuwiki_0.0.20200729.orig.tar.gz
 87840fd388adcba5fd0d20576d37c943 102448 web optional 

Bug#994877: marked as done (dokuwiki: During install error /var/lib/dpkg/info/dokuwiki.postinst:123 tempfile: not found)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2022 00:49:18 +
with message-id 
and subject line Bug#994877: fixed in dokuwiki 0.0.20200729-0.1
has caused the Debian Bug report #994877,
regarding dokuwiki: During install error 
/var/lib/dpkg/info/dokuwiki.postinst:123 tempfile: not found
to be marked as done.

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

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


-- 
994877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dokuwiki
Version: 0.0.20180422.a-2.1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

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

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

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
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 dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  javascript-common  11+nmu1
ii  libjs-jquery   3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-cookie12-3
ii  libjs-jquery-ui1.12.1+dfsg-8
ii  libphp-simplepie   1.3.1+dfsg-5
ii  php2:7.4+76
ii  php-geshi  1.0.9.1-1
ii  php-phpseclib  2.0.30-2
ii  php-random-compat  2.0.19-1
ii  php-xml2:7.4+76
ii  php7.4 [php]   7.4.21-1+deb11u1
ii  php7.4-xml [php-xml]   7.4.21-1+deb11u1
ii  ucf3.0043

Versions of packages dokuwiki recommends:
ii  imagemagick  8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3
ii  php-ldap 2:7.4+76
ii  php7.4-cli [php-cli] 7.4.21-1+deb11u1
ii  php7.4-ldap [php-ldap]   7.4.21-1+deb11u1
ii  php8.0-cli [php-cli] 8.0.8-1
ii  wget 1.21-1+b1

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  

-- debconf information:
  dokuwiki/system/writeplugins: false
  dokuwiki/system/localnet: 10.0.0.0/24
  dokuwiki/wiki/email: webmaster@localhost
  dokuwiki/wiki/superuser: admin
  dokuwiki/system/configure-webserver: apache2
  dokuwiki/wiki/acl: true
  dokuwiki/system/writeconf: false
* dokuwiki/system/purgepages: false
  dokuwiki/wiki/fullname: DokuWiki Administrator
  dokuwiki/wiki/policy: public
  dokuwiki/wiki/title: Debian DokuWiki
  dokuwiki/wiki/failpass:
  dokuwiki/system/documentroot: /dokuwiki
  dokuwiki/wiki/license: cc-by-sa
  dokuwiki/system/accessible: localhost only
  dokuwiki/system/restart-webserver: true


Hello 

During the install of dokuwiki dpkg reported the following error:

Creating config file /etc/dokuwiki/htaccess with new version
/var/lib/dpkg/info/dokuwiki.postinst: 123: tempfile: not found
dpkg: error processing package dokuwiki (--configure):
 installed dokuwiki package post-installation script subprocess returned error 
exit status 127
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for php7.4-cli (7.4.21-1+deb11u1) ...
Processing triggers for libapache2-mod-php7.4 (7.4.21-1+deb11u1) ...
Errors were encountered while processing:
 dokuwiki
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up dokuwiki (0.0.20180422.a-2.1) ...
/var/lib/dpkg/info/dokuwiki.postinst: 123: tempfile: not found
dpkg: error processing package dokuwiki (--configure):
 installed dokuwiki package post-installation script subprocess returned error 
exit status 127
Errors were encountered while processing:
 dokuwiki

I noticed the Apache2 configs were not created

Many thanks

Hal
--- End Message ---
--- Begin Message ---
Source: dokuwiki
Source-Version: 0.0.20200729-0.1
Done: Axel Beckert 

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

Debian distribution maintenance software
pp.
Axel Beckert  

Bug#1007740: curl breaks xmltooling autopkgtest

[Daniel Stenberg]

On Tue, 15 Mar 2022, Cantor, Scott wrote:

Looking more closely, I'm going to hope curl is at fault and that this is 
actually "just" a CA list issue.


This is probably the same issue as Bug #1007739. Triggered by a bug in curl 
for CN-only certificates:


 https://github.com/curl/curl/issues/8559

Fixed in curl (after the 7.82.0 release) via this PR:

 https://github.com/curl/curl/pull/8560

--

 / daniel.haxx.se

Bug#1007740: curl breaks xmltooling autopkgtest

[Cantor, Scott]

I would speculate that this isn't caused by curl, but by openssl bumping. I 
reproduced the test failure on a Mac, and the change log for openssl 3.0.2 
includes a very suspicious incompatible change to a critical function. I need 
to dig into it, and I don't know when that will be at this point. It would help 
to determine if this broke in conjunction with openssl revving to 3.0.2 as well.

-- Scott

Bug#1007740: curl breaks xmltooling autopkgtest

[Cantor, Scott]

Looking more closely, I'm going to hope curl is at fault and that this is 
actually "just" a CA list issue.

It's very unusual for any of this code to rely on "default" trust store 
handling but I'm wondering if this code is tripping on that for some reason. If 
so, it's likely due to the Let's Encrypt rollover, which is what 
test.shibboleth.net uses, and that's what those tests are hitting.

-- Scott

Bug#1006615: marked as done (python3-pybind11: Handle Python 3.10's default sysconfig paths)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 22:52:39 +
with message-id 
and subject line Bug#1006615: fixed in pybind11 2.9.1-2
has caused the Debian Bug report #1006615,
regarding python3-pybind11: Handle Python 3.10's default sysconfig paths
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.)


-- 
1006615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pybind11
Version: 2.9.1-1
Severity: normal
Tags: patch
Forwarded: https://github.com/pybind/pybind11/pull/3764

Until recently, the Python sysconfig module didn't know about Debian's
deb_system and posix_local schemes that were patched into
distutils.sysconfig. This changed in 3.10.2-3, to allow the deprecation
of distutils, upstream.

See https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1960608
for some of the back-story here.

The effective change here is that with Python 3.10 as default, packages
using pybind11 are FTBFS because they can't find Python.h. e.g.
https://launchpad.net/ubuntu/+source/avogadrolibs/1.95.1-8

> CMake Error in python/CMakeLists.txt:
>   Imported target "pybind11::module" includes non-existent path
> 
> "/usr/local/include/python3.10"
> 
>   in its INTERFACE_INCLUDE_DIRECTORIES.

I'm pointing to Ubuntu bugs here, because we're hitting these issues in
Ubuntu first, where Python 3.10 is the default Python 3. Debian hasn't
got there, yet.

The solutions here are two-fold:
1. Migrate from distutils.sysconfig to sysconfig. This needs to happen,
   upstream, before distutils is gone from stdlib.
2. Explicitly select the correct system scheme when looking for
   Python3's headers, rather than the default install-to-/usr/local
   scheme.

Attached are a pair of patches to address the issue. I've forwarded them
upstream in https://github.com/pybind/pybind11/pull/3764

SR
From 5262ff794498b45c12f23f64e9adef30d51e667f Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Mon, 28 Feb 2022 12:49:51 -0400
Subject: [PATCH 1/2] Use sysconfig in Python >= 3.10

Rely on sysconfig for installation paths for Python >= 3.10. distutils
has been deprecated and will be removed.

Fixes: #3677
---
 tools/FindPythonLibsNew.cmake | 15 ---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/tools/FindPythonLibsNew.cmake b/tools/FindPythonLibsNew.cmake
index 7aeffa44..31eeffa0 100644
--- a/tools/FindPythonLibsNew.cmake
+++ b/tools/FindPythonLibsNew.cmake
@@ -112,11 +112,20 @@ endif()
 # VERSION. VERSION will typically be like "2.7" on unix, and "27" on windows.
 execute_process(
   COMMAND
-"${PYTHON_EXECUTABLE}" "-c" "from distutils import sysconfig as s;import sys;import struct;
+"${PYTHON_EXECUTABLE}" "-c" "
+import sys;import struct;
+import sysconfig as s
+USE_SYSCONFIG = sys.version_info >= (3, 10)
+if not USE_SYSCONFIG:
+from distutils import sysconfig as ds
 print('.'.join(str(v) for v in sys.version_info));
 print(sys.prefix);
-print(s.get_python_inc(plat_specific=True));
-print(s.get_python_lib(plat_specific=True));
+if USE_SYSCONFIG:
+print(s.get_path('platinclude'))
+print(s.get_path('platlib'))
+else:
+print(ds.get_python_inc(plat_specific=True));
+print(ds.get_python_lib(plat_specific=True));
 print(s.get_config_var('EXT_SUFFIX') or s.get_config_var('SO'));
 print(hasattr(sys, 'gettotalrefcount')+0);
 print(struct.calcsize('@P'));
-- 
2.34.1

From 697e8e1fca67bb48e477a61a9bbfa049c653ecd2 Mon Sep 17 00:00:00 2001
From: Stefano Rivera 
Date: Mon, 28 Feb 2022 13:11:45 -0400
Subject: [PATCH 2/2] Explicitly select the posix_prefix scheme for platinclude
 on Debian

Debian's default scheme is posix_local, for installing locally-built
packages to /usr/local/.  We want to find the Python headers in /usr/,
so search posix_prefix.
---
 tools/FindPythonLibsNew.cmake | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/tools/FindPythonLibsNew.cmake b/tools/FindPythonLibsNew.cmake
index 31eeffa0..6ad5fe15 100644
--- a/tools/FindPythonLibsNew.cmake
+++ b/tools/FindPythonLibsNew.cmake
@@ -121,7 +121,11 @@ if not USE_SYSCONFIG:
 print('.'.join(str(v) for v in sys.version_info));
 print(sys.prefix);
 if USE_SYSCONFIG:
-print(s.get_path('platinclude'))
+scheme = s.get_default_scheme()
+if scheme == 'posix_local':
+# Debian's default scheme installs to /usr/local/ but we want to find headers in /usr/
+scheme = 'posix_prefix'
+print(s.get_path('platinclude', scheme))
 print(s.get_path('platlib'))
 else:
 print(ds.get_python_inc(plat_specific=True));
-- 
2.34.1

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

[Daniel Stenberg]

On Tue, 15 Mar 2022, Paul Gevers wrote:

This is likely this same issue:

 https://github.com/curl/curl/issues/8559

Fixed in curl (after the 7.82.0 release) via this PR:

 https://github.com/curl/curl/pull/8560

--

 / daniel.haxx.se

Bug#1007010: marked as done (python3.10: autopkgtest regression: FAIL: test_get_scheme_names)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 22:26:53 +
with message-id <20220315222653.jyu3oapalnxlp...@satie.tumbleweed.org.za>
and subject line Re: Bug#1007010: python3.10: autopkgtest regression: FAIL: 
test_get_scheme_names
has caused the Debian Bug report #1007010,
regarding python3.10: autopkgtest regression: FAIL: test_get_scheme_names
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.)


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

Source: python3.10
Version: 3.10.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python3.10 from testing3.10.2-5
all others from testingfrom testing

I copied some of the output at the bottom of this report. To be fair, 
I'm not sure if this isn't related to the missing arch:all build (bug 
#1000188).


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.10/19859148/log.gz

test_get_scheme_names (test.test_sysconfig.TestSysConfig) ... FAIL

==
FAIL: test_get_scheme_names (test.test_sysconfig.TestSysConfig)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/test/test_sysconfig.py", line 269, in 
test_get_scheme_names

self.assertEqual(get_scheme_names(), tuple(sorted(wanted)))
AssertionError: Tuples differ: ('deb_system', 'nt', 'nt_user', 
'osx_framew[64 chars]ser') != ('nt', 'nt_user', 'osx_framework_user', 
'po[35 chars]ser')


First differing element 0:
'deb_system'
'nt'

First tuple contains 2 additional elements.
First extra element 6:
'posix_prefix'

- ('deb_system',
-  'nt',
? ^

+ ('nt',
? ^

   'nt_user',
   'osx_framework_user',
   'posix_home',
-  'posix_local',
   'posix_prefix',
   'posix_user')

--
Ran 1 test in 0.001s

FAILED (failures=1)
test test_sysconfig failed
1 test failed again:
test_sysconfig



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.10.2-6

> I assume you forgot to close it in one of the uploads that happened.

Ooops, yes. I closed the underlying issue (timeout) but not this bug.

There is a new regression, now. Would be fixed by using the new
python3-stdlb-extensions (3.9.10-2).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272--- End Message ---

Bug#1005580: marked as done (entangle: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 22:34:05 +
with message-id 
and subject line Bug#1005580: fixed in entangle 3.0-2
has caused the Debian Bug report #1005580,
regarding entangle: FTBFS: ../src/meson.build:42:5: ERROR: Function does not 
take positional arguments.
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with gir --buildsystem=meson --no-parallel
>dh_update_autotools_config -O--buildsystem=meson -O--no-parallel
>dh_autoreconf -O--buildsystem=meson -O--no-parallel
>dh_auto_configure -O--buildsystem=meson -O--no-parallel
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: entangle
> Project version: 3.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Program pod2man found: YES (/usr/bin/pod2man)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency gthread-2.0 found: YES 2.70.3
> Run-time dependency gmodule-2.0 found: YES 2.70.3
> Run-time dependency gdk-pixbuf-2.0 found: YES 2.42.6
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency pango found: YES 1.50.3
> Run-time dependency pangocairo found: YES 1.50.3
> Run-time dependency libgphoto2 found: YES 2.5.27
> Run-time dependency gudev-1.0 found: YES 237
> Run-time dependency gobject-introspection-1.0 found: YES 1.70.0
> Run-time dependency lcms2 found: YES 2.12
> Run-time dependency libpeas-1.0 found: YES 1.30.0
> Run-time dependency libpeas-gtk-1.0 found: YES 1.30.0
> Run-time dependency gexiv2 found: YES 0.14.0
> Run-time dependency xext found: YES 1.3.4
> Library raw_r found: YES
> Run-time dependency gstreamer-1.0 found: YES 1.20.0
> Run-time dependency gstreamer-video-1.0 found: YES 1.20.0
> Compiler for C supports arguments -W: YES 
> Compiler for C supports arguments -Waddress: YES 
> Compiler for C supports arguments -Waggressive-loop-optimizations: YES 
> Compiler for C supports arguments -Wall: YES 
> Compiler for C supports arguments -Warray-bounds: YES 
> Compiler for C supports arguments -Wattributes: YES 
> Compiler for C supports arguments -Wbuiltin-macro-redefined: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Wchar-subscripts: YES 
> Compiler for C supports arguments -Wclobbered: YES 
> Compiler for C supports arguments -Wcomment: YES 
> Compiler for C supports arguments -Wcomments: YES 
> Compiler for C supports arguments -Wcoverage-mismatch: YES 
> Compiler for C supports arguments -Wcpp: YES 
> Compiler for C supports arguments -Wdate-time: YES 
> Compiler for C supports arguments -Wdeprecated-declarations: YES 
> Compiler for C supports arguments -Wdisabled-optimization: YES 
> Compiler for C supports arguments -Wdiv-by-zero: YES 
> Compiler for C supports arguments -Wdouble-promotion: YES 
> Compiler for C supports arguments -Wempty-body: YES 
> Compiler for C supports arguments -Wendif-labels: YES 
> Compiler for C supports arguments -Wenum-compare: YES 
> Compiler for C supports arguments -Wextra: YES 
> Compiler for C supports arguments -Wformat-contains-nul: YES 
> Compiler for C supports arguments -Wformat-extra-args: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wformat-y2k: YES 
> Compiler for C supports arguments -Wformat-zero-length: YES 
> Compiler for C supports arguments -Wfree-nonheap-object: YES 
> Compiler for C supports arguments -Wignored-qualifiers: YES 
> Compiler for C supports arguments -Wimplicit: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wimplicit-int: YES 
> Compiler for C supports arguments -Winit-self: YES 
> Compiler 

Bug#1007744: dovecot: FTBFS on ppc64el

[Sebastian Ramacher]

Source: dovecot
Version: 1:2.3.18+dfsg1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

dovecot FTBFS on ppc64el:

0 / 77 tests failed
slow server .. : ok
slow client .. : ok
hanging command payload .. : ok
bad command .. : ok
many bad commands  : ok
long command . : ok
SERVER: Fatal: Server timed out
make[4]: *** [Makefile:1346: check-local] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=dovecot=ppc64el=1%3A2.3.18%2Bdfsg1-1%2Bb1=1647334386=0

Cheers
-- 
Sebastian Ramacher

Bug#1007743: kldap: BD-Uninstallable on s390x

[Sebastian Ramacher]

Source: kldap
Version: 21.08.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)


kldap build-depends on missing:
- qt5keychain-dev:s390x

Please get this fixed or request the removal of the s390x binaries of
kldap.

Cheers
-- 
Sebastian Ramacher

Bug#1006620: marked as done (src:httpie: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 21:35:42 +
with message-id 
and subject line Bug#1006620: fixed in httpie 2.6.0-1.1
has caused the Debian Bug report #1006620,
regarding src:httpie: fails to migrate to testing for too long: uploader built 
arch:all binary
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.)


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

Source: httpie
Version: 2.4.0-1
Severity: serious
Control: close -1 2.6.0-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: httpie
Source-Version: 2.6.0-1.1
Done: Paul Gevers 

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated httpie package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Feb 2022 21:04:38 +0100
Source: httpie
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Bartosz Fenski 
Changed-By: Paul Gevers 
Closes: 1006620
Changes:
 httpie (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1006620)
Checksums-Sha1:
 8ec981c32ca57d92277f1127eeb40ab3416a899b 1597 httpie_2.6.0-1.1.dsc
 5e2d26b9307da9538bc875c4d97f0b1cc4fc4047 7452 httpie_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 3f4e8d26287899f1928f82d900b422e3a8774573297ab4625f0b34018c10b6ae 1597 
httpie_2.6.0-1.1.dsc
 488fcb893f4c66c0e937c916b5466daacd48abbce2b83fe7f796290ff3800767 7452 
httpie_2.6.0-1.1.debian.tar.xz
Files:
 f38f12f7f0d174557064bf750b22ae71 1597 web optional httpie_2.6.0-1.1.dsc
 cd99707b1d2d8af09ad98355cae84ee4 7452 web optional 
httpie_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmIdKvwACgkQnFyZ6wW9
dQonNggAsbW+iWX/7kg9QPQNfvwvEkVZyeAfpj0Vi3eKBJUv8I4qJns5oj92gKXk
hxbyLwFAvOp00l2r7/3s2GuBOPvvPLpAFnp7fchFX5hauGa2zxqdHNWvqpWX48A8
o+heQabXYuYxYx2C/kW4/rKRGNcfMfPaEL8Qy/OzHJvwEVxH+JIzayBj7I40opny
4jzWsxgDQWW+ZfhgFeFrjPb+1+ovXzj1QpC4OVpxF74fBNsw6CxhNf3uND8I5p/u
wXqcXvQNqqzwQC8/KrXbUa1KiqS7u9mz/1ON3PaLu5ohM0/Sa+1GBQzGnXDs/kgY
Rh+lhq01438IPzHav2exGqODIl3cFg==
=ZbEv
-END PGP SIGNATURE End Message ---

Bug#1006624: marked as done (src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 21:34:08 +
with message-id 
and subject line Bug#1006624: fixed in ats2-lang 0.4.2-1.1
has caused the Debian Bug report #1006624,
regarding src:ats2-lang: fails to migrate to testing for too long: uploader 
built arch:all binaries
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.)


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

Source: ats2-lang
Version: 0.4.0-1
Severity: serious
Control: close -1 0.4.2-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ats2-lang
Source-Version: 0.4.2-1.1
Done: Paul Gevers 

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ats2-lang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Feb 2022 21:22:33 +0100
Source: ats2-lang
Architecture: source
Version: 0.4.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matthew Danish 
Changed-By: Paul Gevers 
Closes: 1006624
Changes:
 ats2-lang (0.4.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1006624)
Checksums-Sha1:
 47a3aabef97cf10da95212f9ebc2ced021fc712f 1589 ats2-lang_0.4.2-1.1.dsc
 fbb0a5f9e30be64aec7adc2154e4501d267626a1 34512 
ats2-lang_0.4.2-1.1.debian.tar.xz
Checksums-Sha256:
 6cb47bf4c7b4ecb311ed4f2917fb45bf94cbe39e591b62e290929611586c0ff6 1589 
ats2-lang_0.4.2-1.1.dsc
 0056e14d50e66b5997020c67d2b3a99592817e52b52e533a70c38784b0fc03c5 34512 
ats2-lang_0.4.2-1.1.debian.tar.xz
Files:
 9cb192c22ffd92d10aef6e533f8e5413 1589 devel optional ats2-lang_0.4.2-1.1.dsc
 fa28ef6e051e948eb5545e4678df1ae2 34512 devel optional 
ats2-lang_0.4.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmIdLzIACgkQnFyZ6wW9
dQoVcAgAt1BCzrWitvLf2YmbenH/GkyapRLfLQXw8mYzDmz4L9Aia5vPZZE7mBU5
csjkwHV3qWNVtqLVi+sbH75suGHtQcuHQZgdP12siD5Oi4apx6CUUnWpkraOWamf
NePH4RxqZYaUK7W4Zx4sfzeeqLQS2rawlhM1OFK9AwL7F94chQIPRy94WNEmPpUx
IKxb55zODCTNEguRxrifoxSEVJJfuxrbfIcrbJ9iihoa8Hvf+95jVYyXl3l7fC7k
BHA6Jqu9KjYyKYEXUGc5HZAyDOPp6uoOuV0S2fTdzVhnYMv9+jhfAMp3Sjr1YTVA
+tIxW1lJym+5aqey0JUUeSohyOTapw==

Bug#1007010: marked as done (python3.10: autopkgtest regression: FAIL: test_get_scheme_names)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 22:32:10 +0100
with message-id <33e39694-9c91-ccee-bcea-ea77942d9...@debian.org>
and subject line Re: Bug#1007010: python3.10: autopkgtest regression: FAIL: 
test_get_scheme_names
has caused the Debian Bug report #1007010,
regarding python3.10: autopkgtest regression: FAIL: test_get_scheme_names
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.)


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

Source: python3.10
Version: 3.10.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python3.10 from testing3.10.2-5
all others from testingfrom testing

I copied some of the output at the bottom of this report. To be fair, 
I'm not sure if this isn't related to the missing arch:all build (bug 
#1000188).


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.10/19859148/log.gz

test_get_scheme_names (test.test_sysconfig.TestSysConfig) ... FAIL

==
FAIL: test_get_scheme_names (test.test_sysconfig.TestSysConfig)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/test/test_sysconfig.py", line 269, in 
test_get_scheme_names

self.assertEqual(get_scheme_names(), tuple(sorted(wanted)))
AssertionError: Tuples differ: ('deb_system', 'nt', 'nt_user', 
'osx_framew[64 chars]ser') != ('nt', 'nt_user', 'osx_framework_user', 
'po[35 chars]ser')


First differing element 0:
'deb_system'
'nt'

First tuple contains 2 additional elements.
First extra element 6:
'posix_prefix'

- ('deb_system',
-  'nt',
? ^

+ ('nt',
? ^

   'nt_user',
   'osx_framework_user',
   'posix_home',
-  'posix_local',
   'posix_prefix',
   'posix_user')

--
Ran 1 test in 0.001s

FAILED (failures=1)
test test_sysconfig failed
1 test failed again:
test_sysconfig



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Fri, 11 Mar 2022 23:38:56 -0400 Stefano Rivera  
wrote:

Hi Paul (2022.03.10_10:05:50_-0400)
> I copied some of the output at the bottom of this report. To be fair, I'm
> not sure if this isn't related to the missing arch:all build (bug #1000188).

Aha, that explains why I was unable to reproduce this locally.

Yes, I assume that's the issue here.


I assume you forgot to close it in one of the uploads that happened.

Paul


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

Processed: affects 1006615

[Debian Bug Tracking System]

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

> affects 1006615 src:dolfin
Bug #1006615 [python3-pybind11] python3-pybind11: Handle Python 3.10's default 
sysconfig paths
Added indication that 1006615 affects src:dolfin
> thanks
Stopping processing here.

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

Processed: severity of 1006615 is serious

[Debian Bug Tracking System]

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

> severity 1006615 serious
Bug #1006615 [python3-pybind11] python3-pybind11: Handle Python 3.10's default 
sysconfig paths
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1007740: curl breaks xmltooling autopkgtest

[Paul Gevers]

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

Dear maintainer(s),

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


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

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

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


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

Paul

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

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

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

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

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

.. contents:: :depth: 2

FAIL: xmltoolingtest


Running cxxtest tests (125 tests)..1647332074 WARN XMLTooling.XMLHelper 
: DEPRECATED: attribute "ignoreCase" encountered in configuration. Use 
"caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : DEPRECATED: attribute 
"ignoreCase" encountered in configuration. Use "caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : DEPRECATED: attribute 
"ignoreCase" encountered in configuration. Use "caseSensitive".
1647332074 WARN XMLTooling.XMLHelper : Attribute "ignoreCase" and 
"caseSensitive" should not be used in the same element.
.1647332074 WARN DirectoryWalkerTest : Unable to open directory 
(invalid)
...1647332074 ERROR XMLTooling.ParserPool : fatal error on line 
2, column 10, message: invalid document structure
.1647332074 ERROR XMLTooling.XMLObject : no default builder 
installed, found unknown child element (test:UnknownElement)
..1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping 
invalid ds:KeyValue (Modulus must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Exponent must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Modulus must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (RSAKeyValue must have Modulus.)
1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (DSKeyValue cannot have P without Q.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (P must have TextContent.)
...1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (DSKeyValue cannot have P without Q.)
..1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Q must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (P must have TextContent.)
1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (G must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping 
invalid ds:KeyValue (DSAKeyValue must have Y.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Y must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (J must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping 
invalid ds:KeyValue (DSKeyValue cannot have Seed without PgenCounter.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (Seed must have TextContent.)
..1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (DSKeyValue cannot have Seed without PgenCounter.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : skipping invalid 
ds:KeyValue (PgenCounter must have TextContent.)
.1647332074 WARN XMLTooling.KeyInfoResolver.Inline : resolving 
ds11:ECKeyValue
.1647332074 ERROR XMLTooling.KeyResolver.Inline : caught XML-Security 
exception loading certificate: OpenSSL:EC - Error translating Base64 
octets into OpenSSL 

Processed: curl breaks xmltooling autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 curl/7.82.0-1
Bug #1007740 [src:curl, src:xmltooling] curl breaks xmltooling autopkgtest
Marked as found in versions curl/7.82.0-1.
> found -1 xmltooling/3.2.1-1
Bug #1007740 [src:curl, src:xmltooling] curl breaks xmltooling autopkgtest
Marked as found in versions xmltooling/3.2.1-1.

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

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

[Paul Gevers]

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

Dear maintainer(s),

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


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

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

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


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

Paul

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

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

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

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

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


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

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

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


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

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: curl breaks stenographer autopkgtest: curl: (27) Out of memory

[Debian Bug Tracking System]

Processing control commands:

> found -1 curl/7.82.0-1
Bug #1007739 [src:curl, src:stenographer] curl breaks stenographer autopkgtest: 
curl: (27) Out of memory
Marked as found in versions curl/7.82.0-1.
> found -1 stenographer/1.0.1-2
Bug #1007739 [src:curl, src:stenographer] curl breaks stenographer autopkgtest: 
curl: (27) Out of memory
Marked as found in versions stenographer/1.0.1-2.

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

Bug#1007738: webcamoid: autopkgtest regression: Unknown failure encountered running a test

[Paul Gevers]

Source: webcamoid
Version: 9.0.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
webcamoid  from testing9.0.0-3
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/w/webcamoid/19983920/log.gz

[100%] Built target StandAlone
make[2]: Leaving directory 
'/tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_start 
/tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu/CMakeFiles 
0
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu'

   dh_auto_test -a
rm -fr -- /tmp/dh-xdg-rundir-ifBRypUJ
   create-stamp debian/debhelper-build-stamp
test_exists
ASSERT:Unknown failure encountered running a test

Ran 2 tests.

FAILED (failures=1)
autopkgtest [03:06:45]: test check-auto-tests.sh



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007736: backbone: autopkgtest regression: node: command not found

[Paul Gevers]

Source: backbone
Version: 1.4.1~dfsg+~1.4.15-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
backbone   from testing1.4.1~dfsg+~1.4.15-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looks like 
you're missing a test dependency.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/b/backbone/20012303/log.gz

bash: line 1: node: command not found
autopkgtest [16:13:17]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007733: golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386:

[Paul Gevers]

Source: golang-github-getkin-kin-openapi
Version: 0.90.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


 passfail
golang-github-getkin-kin-openapi from testing0.90.0-1
all others   from testingfrom testing

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

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


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

Paul

[1] 
https://qa.debian.org/excuses.php?package=golang-github-getkin-kin-openapi


https://ci.debian.net/data/autopkgtest/testing/armhf/g/golang-github-getkin-kin-openapi/19997695/log.gz


=== RUN   TestValidator/invalid_POST_request;_wrong_property_type
2022/03/15 08:17:25 invalid request: request body has an error: doesn't 
match the schema: Error at "/actual": Field must be set to number or not 
be present

Schema:
  {
"type": "number"
  }

Value:
  "string"
=== CONT  TestValidator
middleware_test.go:333: test#6: invalid POST request; missing property
=== RUN   TestValidator/invalid_POST_request;_missing_property
2022/03/15 08:17:25 invalid request: request body has an error: doesn't 
match the schema: Error at "/actual": property "actual" is missing

Schema:
  {
"additionalProperties": false,
"properties": {
  "actual": {
"type": "number"
  },
  "expected": {
"type": "number"
  },
  "name": {
"type": "string"
  }
},
"required": [
  "name",
  "expected",
  "actual"
],
"type": "object"
  }

Value:
  {
"expected": 9,
"name": "foo"
  }
=== CONT  TestValidator
middleware_test.go:333: test#7: invalid POST request; extra property
=== RUN   TestValidator/invalid_POST_request;_extra_property
2022/03/15 08:17:25 invalid request: request body has an error: doesn't 
match the schema: property "ideal" is unsupported

Schema:
  {
"additionalProperties": false,
"properties": {
  "actual": {
"type": "number"
  },
  "expected": {
"type": "number"
  },
  "name": {
"type": "string"
  }
},
"required": [
  "name",
  "expected",
  "actual"
],
"type": "object"
  }

Value:
  {
"actual": 10,
"expected": 9,
"ideal": 8,
"name": "foo"
  }
=== CONT  TestValidator
middleware_test.go:333: test#8: valid response; 404 error
=== RUN   TestValidator/valid_response;_404_error
=== CONT  TestValidator
middleware_test.go:333: test#9: invalid response; invalid error
=== RUN   TestValidator/invalid_response;_invalid_error
2022/03/15 08:17:25 invalid response: response body doesn't match the 
schema: Field must be set to object or not be present

Schema:
  {
"additionalProperties": false,
"properties": {
  "code": {
"type": "string"
  },
  "message": {
"type": "string"
  }
},
"required": [
  "code",
  "message"
],
"type": "object"
  }

Value:
  "string"
=== CONT  TestValidator
middleware_test.go:333: test#10: invalid POST response; not strict
=== RUN   TestValidator/invalid_POST_response;_not_strict
2022/03/15 08:17:25 invalid response: response body doesn't match the 
schema: property "extra" is unsupported

Schema:
  {
"additionalProperties": false,
"properties": {
  "contents": {
"$ref": "#/components/schemas/TestContents"
  },
  "id": {
"type": "string"
  }
},
"required": [
  "id",
  "contents"
],
"type": "object"
  }

Value:
  {
"contents": {
  "actual": 10,
  "expected": 9,
  "name": "foo"
},
"extra": true,
"id": "42"
  }



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1007734: golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match

[Paul Gevers]

Source: golang-github-alecthomas-chroma, golang-github-niklasfasching-go-org
Control: found -1 golang-github-alecthomas-chroma/0.10.0-1
Control: found -1 golang-github-niklasfasching-go-org/1.6.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of golang-github-alecthomas-chroma the autopkgtest 
of golang-github-niklasfasching-go-org fails in testing when that 
autopkgtest is run with the binary packages of 
golang-github-alecthomas-chroma from unstable. It passes when run with 
only packages from testing. In tabular form:


  passfail
golang-github-alecthomas-chroma   from testing0.10.0-1
golang-github-niklasfasching-go-org   from testing1.6.0-1
all othersfrom testingfrom testing

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

Currently this regression is blocking the migration of 
golang-github-alecthomas-chroma 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=golang-github-alecthomas-chroma


https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-niklasfasching-go-org/19989847/log.gz

=== RUN   TestBlorg
config_test.go:39: PublicDir hashes do not match: 
'ab73939658896f4b21a1486bd7862751  -' -> 
'0add254dc2d8cb398cb9b9dc9e495e85  -'

--- FAIL: TestBlorg (0.04s)
FAIL
FAILgithub.com/niklasfasching/go-org/blorg  0.059s
=== RUN   TestHTMLWriter
html_writer_test.go:30: testdata/blocks.org: passed!
html_writer_test.go:30: testdata/captions.org: passed!
html_writer_test.go:30: testdata/east_asian_line_breaks.org: passed!
html_writer_test.go:30: testdata/footnotes.org: passed!
html_writer_test.go:30: testdata/footnotes_in_headline.org: passed!
html_writer_test.go:30: testdata/headlines.org: passed!
html_writer_test.go:30: testdata/inline.org: passed!
html_writer_test.go:30: testdata/keywords.org: passed!
html_writer_test.go:30: testdata/latex.org: passed!
html_writer_test.go:30: testdata/lists.org: passed!
html_writer_test.go:30: testdata/misc.org: passed!
html_writer_test.go:30: testdata/options.org: passed!
html_writer_test.go:30: testdata/paragraphs.org: passed!
html_writer_test.go:30: testdata/tables.org: passed!
--- PASS: TestHTMLWriter (0.01s)
=== RUN   TestExtendedHTMLWriter
--- PASS: TestExtendedHTMLWriter (0.00s)
=== RUN   TestPrettyRelativeLinks
=== RUN   TestPrettyRelativeLinks/[[file:/hello.org]]
=== RUN   TestPrettyRelativeLinks/[[file:hello.org]]
=== RUN   TestPrettyRelativeLinks/[[http://hello.org]]
=== RUN   TestPrettyRelativeLinks/[[/foo.png]]
=== RUN   TestPrettyRelativeLinks/[[foo.png]]
=== RUN   TestPrettyRelativeLinks/[[/foo.png][foo]]
=== RUN   TestPrettyRelativeLinks/[[/hello.org][hello]]
=== RUN   TestPrettyRelativeLinks/[[hello.org][hello]]
=== RUN   TestPrettyRelativeLinks/[[foo.png][foo]]
--- PASS: TestPrettyRelativeLinks (0.00s)
--- PASS: TestPrettyRelativeLinks/[[file:/hello.org]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[file:hello.org]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[http://hello.org]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[/foo.png]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[foo.png]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[/foo.png][foo]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[/hello.org][hello]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[hello.org][hello]] (0.00s)
--- PASS: TestPrettyRelativeLinks/[[foo.png][foo]] (0.00s)
=== RUN   TestOrgWriter
org_writer_test.go:35: testdata/blocks.org: passed!
org_writer_test.go:35: testdata/captions.org: passed!
org_writer_test.go:35: testdata/east_asian_line_breaks.org: passed!
org_writer_test.go:35: testdata/footnotes.org: passed!
org_writer_test.go:35: testdata/footnotes_in_headline.org: passed!
org_writer_test.go:35: testdata/headlines.org: passed!
org_writer_test.go:35: testdata/inline.org: passed!
org_writer_test.go:35: testdata/keywords.org: passed!
org_writer_test.go:35: testdata/latex.org: passed!
org_writer_test.go:35: testdata/lists.org: passed!
org_writer_test.go:35: testdata/misc.org: passed!
org_writer_test.go:35: testdata/options.org: passed!
org_writer_test.go:35: testdata/paragraphs.org: passed!
org_writer_test.go:35: testdata/tables.org: passed!
--- PASS: TestOrgWriter (0.01s)
=== RUN   TestExtendedOrgWriter
--- PASS: TestExtendedOrgWriter (0.00s)
PASS
ok  github.com/niklasfasching/go-org/org0.035s
FAIL
dh_auto_test: error: cd _build && go test -vet=off -v -p 56 

Processed: golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match

[Debian Bug Tracking System]

Processing control commands:

> found -1 golang-github-alecthomas-chroma/0.10.0-1
Bug #1007734 [src:golang-github-alecthomas-chroma, 
src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma breaks 
golang-github-niklasfasching-go-org autopkgtest: hashes do not match
Marked as found in versions golang-github-alecthomas-chroma/0.10.0-1.
> found -1 golang-github-niklasfasching-go-org/1.6.0-1
Bug #1007734 [src:golang-github-alecthomas-chroma, 
src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma breaks 
golang-github-niklasfasching-go-org autopkgtest: hashes do not match
Marked as found in versions golang-github-niklasfasching-go-org/1.6.0-1.

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

Bug#1007732: ccache: autopkgtest regression: cannot execute 'cc1plus'

[Paul Gevers]

Source: ccache
Version: 4.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
ccache from testing4.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you 
missing a new test dependency?


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccache/19983906/log.gz

Compiler: gcc (/usr/bin/gcc)
Compiler version: gcc (Debian 11.2.0-16) 11.2.0
CUDA compiler:not available

Running test suite 
basegcc: 
fatal error: cannot execute 'cc1plus': execvp: No such file or directory

compilation terminated.

FAILED

Test suite: base (line 1457)
Test case:  .incbin
Failure reason: Expected cache_miss to be 1, actual 0

Actual statistics counters
==
autoconf_test0
bad_compiler_arguments   0
bad_output_file  0
cache_miss   0
cache_size_kibibyte  0
called_for_link  0
called_for_preprocessing 0
cleanups_performed   0
compile_failed   0
compiler_check_failed0
compiler_produced_empty_output   0
compiler_produced_no_output  0
compiler_produced_stdout 0
could_not_find_compiler  0
could_not_use_modules0
could_not_use_precompiled_header 0
direct_cache_hit 0
direct_cache_miss0
error_hashing_extra_file 0
files_in_cache   0
internal_error   0
missing_cache_file   0
multiple_source_files0
no_input_file0
output_to_stdout 0
preprocessed_cache_hit   0
preprocessed_cache_miss  0
preprocessor_error   1
primary_storage_hit  0
primary_storage_miss 0
recache  0
secondary_storage_error  0
secondary_storage_hit0
secondary_storage_miss   0
secondary_storage_timeout0
unsupported_code_directive   2
unsupported_compiler_option  0
unsupported_source_language  0

Test data and log file have been left in testdir/1139 / testdir/failed
autopkgtest [02:56:37]: test run-testsuites



OpenPGP_signature
Description: OpenPGP digital signature

Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

[Paul Gevers]

Hi,

On Fri, 18 Jun 2021 08:43:53 +0300 Andrius Merkys  wrote:

I must have overlooked this. I will see what I can do, but indeed this
is quite late in the release cycle.


Ping.

Your package regularly times out on our amd64 infrastructure too.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001801: closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#1001801: fixed in dogtag-pki 11.0.3-1)

[Paul Gevers]

Control: reopen -1

Hi

On 15-03-2022 13:09, Debian Bug Tracking System wrote:

#1001801: dogtag-pki: hits autopkgtest timeout on powerful workers

It has been closed by Debian FTP Masters  (reply to 
Timo Aaltonen ).


Sorry to say, but this seems to not have solved the issue:

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dogtag-pki/20012305/log.gz

INFO: Creating /etc/pki/pki-tomcat/Catalina/localhost/kra.xml
INFO: Waiting for web application to start
autopkgtest [19:00:59]: ERROR: timed out on command "su -s /bin/bash 
root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.vldupxz2/downtmp/build.Mob/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.vldupxz2/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.vldupxz2/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=56; unset 
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY 
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo 
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f 
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export 
AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x 
/tmp/autopkgtest-lxc.vldupxz2/downtmp/build.Mob/src/debian/tests/pkispawn; 
touch /tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-stdout 
/tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-stderr; 
/tmp/autopkgtest-lxc.vldupxz2/downtmp/build.Mob/src/debian/tests/pkispawn 2> 
>(tee -a /tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-stderr >&2) > 
>(tee -a /tmp/autopkgtest-lxc.vldupxz2/downtmp/pkispawn-stdout);" 
(kind: test)


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1001801 closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#1001801: fixed in dogtag-pki 11.0.3-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1001801 {Done: Timo Aaltonen } [src:dogtag-pki] 
dogtag-pki: hits autopkgtest timeout on powerful workers
'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 dogtag-pki/11.0.3-1.

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

Processed: update bts meta info

[Debian Bug Tracking System]

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

> reassign 1006659 src:python-django-celery-beat 2.2.1-1
Bug #1006659 {Done: Michael Fladischer } 
[src:python-django-timezone-field, src:python-django-celery-beat] 
python-django-timezone-field breaks python-django-celery-beat autopkgtest: type 
object 'TimeZoneField' has no attribute 'default_choices'
Bug reassigned from package 'src:python-django-timezone-field, 
src:python-django-celery-beat' to 'src:python-django-celery-beat'.
No longer marked as found in versions python-django-timezone-field/5.0-1 and 
python-django-celery-beat/2.2.1-1.
No longer marked as fixed in versions python-django-celery-beat/2.2.1-2.
Bug #1006659 {Done: Michael Fladischer } 
[src:python-django-celery-beat] python-django-timezone-field breaks 
python-django-celery-beat autopkgtest: type object 'TimeZoneField' has no 
attribute 'default_choices'
Marked as found in versions python-django-celery-beat/2.2.1-1.
> fixed 1006659 2.2.1-2
Bug #1006659 {Done: Michael Fladischer } 
[src:python-django-celery-beat] python-django-timezone-field breaks 
python-django-celery-beat autopkgtest: type object 'TimeZoneField' has no 
attribute 'default_choices'
Marked as fixed in versions python-django-celery-beat/2.2.1-2.
> affects 1006659 src:python-django-timezone-field
Bug #1006659 {Done: Michael Fladischer } 
[src:python-django-celery-beat] python-django-timezone-field breaks 
python-django-celery-beat autopkgtest: type object 'TimeZoneField' has no 
attribute 'default_choices'
Added indication that 1006659 affects src:python-django-timezone-field
> thanks
Stopping processing here.

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

Bug#994456: now also FTBFS

[Antonio Terceiro]

On Fri, 11 Mar 2022 19:17:43 +0100 Paul Gevers  wrote:
> severity 994456 serious
> tags 994456 ftbfs
> thanks
> 
> Now also causing FTBFS during the ruby2.7 removal transition.

Testing this locally, the tests fail randomly aproximately 10% of the
times like this:

8<8<8<-
Failure:
StackProfTest#test_cputime 
[/tmp/autopkgtest.t74Yoq/build.KKC/real-tree/test/test_stackprof.rb:83]:
Expected # encoding: ASCII-8BIT
#valid: true
"Integer#times" to include "StackProfTest#math".
8<8<8<-


signature.asc
Description: PGP signature

Bug#1005456: marked as done (osmo-pcu: FTBFS: | gcc: error: unrecognized command-line option '-V')

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 18:22:34 +
with message-id 
and subject line Bug#1005456: fixed in osmo-pcu 1.0.0-2
has caused the Debian Bug report #1005456,
regarding osmo-pcu: FTBFS: | gcc: error: unrecognized command-line option '-V'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests'
> :;{ \
>echo '# Signature of the current package.' && \
>echo 'm4_define([AT_PACKAGE_NAME],' && \
>echo '  [osmo-pcu])' && \
>echo 'm4_define([AT_PACKAGE_TARNAME],' && \
>echo '  [osmo-pcu])' && \
>echo 'm4_define([AT_PACKAGE_VERSION],' && \
>echo '  [0.8.0])' && \
>echo 'm4_define([AT_PACKAGE_STRING],' && \
>echo '  [osmo-pcu 0.8.0])' && \
>echo 'm4_define([AT_PACKAGE_BUGREPORT],' && \
>echo '  [osmocom-net-g...@lists.osmocom.org])'; \
>echo 'm4_define([AT_PACKAGE_URL],' && \
>echo '  [])'; \
>  } >'./package.m4'
> /bin/bash ../missing --run autom4te --language=autotest -I '.' -o 
> testsuite.tmp testsuite.at
> mv testsuite.tmp testsuite
> /bin/bash './testsuite' 
> ## -- ##
> ## osmo-pcu 0.8.0 test suite. ##
> ## -- ##
> 
> Regression tests
> 
>   1: rlcmac  ok
>   2: multi_slot  FAILED (testsuite.at:15)
>   3: ts_allocFAILED (testsuite.at:22)
>   4: tbf FAILED (testsuite.at:28)
>   5: bitcomp ok
>   6: edgeFAILED (testsuite.at:42)
>   7: types   FAILED (testsuite.at:49)
>   8: ms  FAILED (testsuite.at:56)
>   9: llc FAILED (testsuite.at:63)
>  10: llist   ok
>  11: codel   ok
>  12: fn  FAILED (testsuite.at:82)
>  13: app_infoFAILED (testsuite.at:89)
> 
> ## - ##
> ## Test results. ##
> ## - ##
> 
> ERROR: All 13 tests were run,
> 9 failed unexpectedly.
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
> 
> Please send `tests/testsuite.log' and all information you think might help:
> 
>To: 
>Subject: [osmo-pcu 0.8.0] testsuite: 2 3 4 6 7 8 9 12 13 failed
> 
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point.  Its output may
> be found below `tests/testsuite.dir'.
> 
> make[4]: *** [Makefile:1356: check-local] Error 1
> make[4]: Leaving directory '/<>/tests'
> make[3]: *** [Makefile:1156: check-am] Error 2
> make[3]: Leaving directory '/<>/tests'
> make[2]: *** [Makefile:412: check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
> ## -- ##
> ## osmo-pcu 0.8.0 test suite. ##
> ## -- ##
> 
> testsuite: command line was:
>   $ ./testsuite 
> 
> ## - ##
> ## Platform. ##
> ## - ##
> 
> hostname = ip-10-84-232-148
> uname -m = x86_64
> uname -r = 5.10.0-9-cloud-amd64
> uname -s = Linux
> uname -v = #1 SMP Debian 5.10.70-1 (2021-09-30)
> 
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
> 
> /bin/arch  = unknown
> /usr/bin/arch -k   = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo  = unknown
> /bin/machine   = unknown
> /usr/bin/oslevel   = unknown
> /bin/universe  = unknown
> 
> PATH: /<>/tests/
> PATH: /usr/local/sbin/
> PATH: /usr/local/bin/
> PATH: /usr/sbin/
> PATH: /usr/bin/
> PATH: /sbin/
> PATH: /bin/
> PATH: /usr/games/
> 
> testsuite: atconfig:
> | # Configurable variable values for building test suites.
> | # 

Bug#1006300: marked as pending in libvirt

[Andrea Bolognani]

Control: tag -1 pending

Hello,

Bug #1006300 in libvirt reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/libvirt-team/libvirt/-/commit/a06d5e56fb01acf2765700c9ad2a1bdce0454178


control: Drop i386 from Xen arches

Starting with Xen version 4.16, Xen is no longer built on
the i386 architecture in Debian.

Closes: #1006300


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006300

Processed: Bug#1006300 marked as pending in libvirt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006300 [src:libvirt] src:libvirt: libvirt should no longer build the 
libvirt-daemon-driver-xen package on i386
Added tag(s) pending.

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

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Chris Chang]

Just a heads-up, today's release contains a fix for an
infinite-loop-instead-of-error bug in the previous release.

On Sun, Feb 20, 2022 at 12:36 PM Andreas Tille  wrote:

> Cool!  This finally works.  Thanks a lot for your patience, Andreas.
>
> Am Sun, Feb 20, 2022 at 09:43:10AM -0800 schrieb Chris Chang:
> > Hmm.  Ordinarily, that download link would be fine.  I had not updated it
> > this time because the issue only affects gcc 11+, so it did not affect
> any
> > of the precompiled binaries and I wanted to keep the posted source
> > identical to that used to compile those binaries.
> >
> > On the other hand, the only difference (in the non-gcc-11+ case) between
> > the binaries and the updated source is the version date.  I guess this is
> > insignificant enough that a temporary discordance is less disruptive than
> > making you change your packing process, so I've updated the website
> source
> > link to point to the newer code; let me know if you still run into any
> > problems.
> >
> > On Sat, Feb 19, 2022 at 11:53 PM Andreas Tille  wrote:
> >
> > > Hi Chris,
> > >
> > > Am Sat, Feb 19, 2022 at 11:37:34PM -0800 schrieb Chris Chang:
> > > > To elaborate: when I look at
> > > > https://salsa.debian.org/med-team/plink2/-/tree/master , I can see
> that
> > > > plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't
> have
> > > the
> > > > same contents as the v2.00a3-20220218 GitHub tag/release.  So I don't
> > > know
> > > > where you grabbed the code from this time, but it does not appear to
> be
> > > > from GitHub.
> > >
> > > That's true since on Github the source code of plink1.9 and plink2 is
> not
> > > separated.  Thus I download the tarball from
> > >
> > >https://www.cog-genomics.org/plink/2.0/
> > >
> > > which points to
> > >
> > >https://www.cog-genomics.org/static/bin/plink2_src_220217.zip
> > >
> > > I confirm that the tag on Github says v2.00a3-20220218 which seems to
> be
> > > later than 220217.  In principle I could point the packaging metadata
> to
> > > Github and exclude everything that I do not need for plink2 packaging
> (so
> > > remove 1.9 directory and code copies of libdeflate, simde and zstd in
> 2.0)
> > >
> > > In case you consider this the safer way to download plink2 code I'll
> do so.
> > >
> > > Kind regards and thanks a lot for comparing the code base
> > >
> > >  Andreas.
> > >
> > > > On Sat, Feb 19, 2022 at 7:54 AM Chris Chang 
> > > wrote:
> > > >
> > > > > If you build off the current head, the version string should say
> "18
> > > Feb
> > > > > 2022", not "17 Feb 2022".
> > > > >
> > > > > On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille 
> > > wrote:
> > > > >
> > > > >> Hi again,
> > > > >>
> > > > >> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> > > > >> > Ok, new release/tag created.
> > > > >>
> > > > >> I've built the new version now.  The bad news is that it keeps on
> > > > >> SEGFAULTing for me:
> > > > >>
> > > > >> ...
> > > > >> (gdb) run
> > > > >> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile
> tmp_data
> > > > >> --export vcf vcf-dosage=DS --out tmp_data2
> > > > >> [Thread debugging using libthread_db enabled]
> > > > >> Using host libthread_db library
> > > "/lib/x86_64-linux-gnu/libthread_db.so.1".
> > > > >> [New Thread 0x74cc7640 (LWP 985019)]
> > > > >> [New Thread 0x744c6640 (LWP 985020)]
> > > > >> [New Thread 0x7fffebcc5640 (LWP 985021)]
> > > > >> PLINK v2.00a3 64-bit (17 Feb 2022)
> > > > >> www.cog-genomics.org/plink/2.0/
> > > > >> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General
> Public
> > > > >> License v3
> > > > >> Logging to tmp_data2.log.
> > > > >> Options in effect:
> > > > >>   --debug
> > > > >>   --export vcf vcf-dosage=DS
> > > > >>   --out tmp_data2
> > > > >>   --pfile tmp_data
> > > > >>
> > > > >> Start time: Sat Feb 19 16:00:00 2022
> > > > >> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
> > > > >> Using up to 4 compute threads.
> > > > >> [New Thread 0x77fc5640 (LWP 985022)]
> > > > >>
> > > > >> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation
> fault.
> > > > >> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60
> > > > >> "tmp_data.psam", pheno_range_list_ptr=,
> fam_cols=...,
> > > > >> pheno_ct_max=,
> > > > >> missing_pheno=, affection_01=0,
> max_thread_ct=4,
> > > > >> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
> > > > >> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
> > > > >> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
> > > > >> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
> > > > >> pheno_ct_ptr=0x7fff8720,
> > > > >> max_pheno_name_blen_ptr=0x7fff87b0) at
> ../plink2_psam.cc:611
> > > > >> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
> > > > >>
> > > > >>
> > > > >> Please let me know if I can do further checks.
> > > > >>
> > > > >> Kind regards
> > > > >>
> > > > >>   Andreas.
> > > > 

Bug#993350: Still problems

[David Ward]

On 3/15/2022 7:15 AM, ael wrote:
In fact there are still outstanding problems which are mentioned 
earlier in this bug.


Separate problems need to be tracked in separate bugs, even if they 
affect the same hardware.

Please see: https://www.debian.org/Bugs/Reporting


This bug in Debian was reported by Hans Georg Colle when using 
sane-backends version 1.0.32-4. It was fixed by a upstream change to the 
epson2 driver in sane-backends version 1.1.1, related to setting the 
focusSupport flag on specific hardware. He has confirmed this fix.


https://gitlab.com/sane-project/backends/-/issues/445
https://gitlab.com/sane-project/backends/-/merge_requests/604


Wolfram Sang, the upstream maintainer, is aware of the remaining bugs. 
I infer that he hasn't had time to track them down as yet, but he has 
said that he is investigating.


The same is true upstream: different problems in each backend are 
tracked as separate issues. It is more helpful to the upstream 
maintainers to use their issue tracker to report and follow individual 
issues, rather than their mailing list. It avoids that question by 
making clear the status of each issue.


https://gitlab.com/sane-project/backends/-/issues


As I recall, the main problem is with very large scans which fail. 
Less important is that xsane "hangs" when the [CANCEL] button is 
pressed instead of recovering gracefully.


It is very important to distinguish where the bugs are occurring here.

An issue should only be attributed to xsane if it cannot be reproduced 
by using the "scanimage" command (or a different frontend, such as 
simple-scan). The issues that have been identified so far are in the 
epson2 backend. The sane backends and the xsane frontend are in two 
different code bases that have separate upstream maintainers, and are 
separately packaged in Debian.


https://gitlab.com/sane-project/backends/
https://gitlab.com/sane-project/frontend/xsane


Thanks for your help!

David

Bug#1007254: marked as done (apache2-dev: Missing dependency on libpcre2-dev for apxs2)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 14:45:14 +
with message-id 
and subject line Bug#1007254: fixed in apache2 2.4.53-2
has caused the Debian Bug report #1007254,
regarding apache2-dev: Missing dependency on libpcre2-dev for apxs2
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.)


-- 
1007254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2-dev
Version: 2.4.53-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:mod-vhost-ldap

https://buildd.debian.org/status/logs.php?pkg=mod-vhost-ldap=2.4.0-1%2Bb3

...
make[1]: Entering directory '/<>'
# Try building with per request document root and if it fails, do the normal 
build (kinda ugly, but should work)
apxs2 -Wc,-Wall -Wc,-Werror -Wc,-g -Wc,-DDEBUG 
-Wc,-DMOD_VHOST_LDAP_VERSION=\\\"mod_vhost_ldap/2.4.0\\\" 
-Wc,-DHAS_PER_REQUEST_DOCUMENT_ROOT -c -lldap_r mod_vhost_ldap.c || \
apxs2 -Wc,-Wall -Wc,-Werror -Wc,-g -Wc,-DDEBUG 
-Wc,-DMOD_VHOST_LDAP_VERSION=\\\"mod_vhost_ldap/2.4.0\\\" -c -lldap_r 
mod_vhost_ldap.c
/usr/share/apr-1.0/build/libtool  --mode=compile --tag=disable-static 
x86_64-linux-gnu-gcc -prefer-pic -pipe -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2   -DLINUX -D_REENTRANT 
-D_GNU_SOURCE  -pthread  -I/usr/include/apache2  -I/usr/include/apr-1.0   
-I/usr/include/apr-1.0 -I/usr/include -Wall -Werror -g -DDEBUG 
-DMOD_VHOST_LDAP_VERSION=\"mod_vhost_ldap/2.4.0\" 
-DHAS_PER_REQUEST_DOCUMENT_ROOT  -c -o mod_vhost_ldap.lo mod_vhost_ldap.c && 
touch mod_vhost_ldap.slo
libtool: compile:  x86_64-linux-gnu-gcc -pipe -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DLINUX 
-D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/include/apache2 
-I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -Wall -Werror -g 
-DDEBUG -DMOD_VHOST_LDAP_VERSION=\"mod_vhost_ldap/2.4.0\" 
-DHAS_PER_REQUEST_DOCUMENT_ROOT -c mod_vhost_ldap.c  -fPIC -DPIC -o 
.libs/mod_vhost_ldap.o
/usr/share/apr-1.0/build/libtool  --mode=link --tag=disable-static 
x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -lpcre2-8 
-L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0-o mod_vhost_ldap.la  -lldap_r 
-rpath /usr/lib/apache2/modules -module -avoid-versionmod_vhost_ldap.lo
libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
.libs/mod_vhost_ldap.o   -lpcre2-8 -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 
-lldap_r  -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
-Wl,mod_vhost_ldap.so -o .libs/mod_vhost_ldap.so
/usr/bin/ld: cannot find -lpcre2-8: No such file or directory
collect2: error: ld returned 1 exit status
apxs:Error: Command failed with rc=65536
.
/usr/share/apr-1.0/build/libtool  --mode=compile --tag=disable-static 
x86_64-linux-gnu-gcc -prefer-pic -pipe -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security  -Wdate-time -D_FORTIFY_SOURCE=2   -DLINUX -D_REENTRANT 
-D_GNU_SOURCE  -pthread  -I/usr/include/apache2  -I/usr/include/apr-1.0   
-I/usr/include/apr-1.0 -I/usr/include -Wall -Werror -g -DDEBUG 
-DMOD_VHOST_LDAP_VERSION=\"mod_vhost_ldap/2.4.0\"  -c -o mod_vhost_ldap.lo 
mod_vhost_ldap.c && touch mod_vhost_ldap.slo
libtool: compile:  x86_64-linux-gnu-gcc -pipe -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DLINUX 
-D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/include/apache2 
-I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -Wall -Werror -g 
-DDEBUG -DMOD_VHOST_LDAP_VERSION=\"mod_vhost_ldap/2.4.0\" -c mod_vhost_ldap.c  
-fPIC -DPIC -o .libs/mod_vhost_ldap.o
/usr/share/apr-1.0/build/libtool  --mode=link --tag=disable-static 
x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -lpcre2-8 
-L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0-o mod_vhost_ldap.la  -lldap_r 
-rpath /usr/lib/apache2/modules -module -avoid-versionmod_vhost_ldap.lo
libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  
.libs/mod_vhost_ldap.o   -lpcre2-8 -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 
-lldap_r  -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
-Wl,mod_vhost_ldap.so -o .libs/mod_vhost_ldap.so
/usr/bin/ld: cannot find -lpcre2-8: No such file or directory
collect2: error: ld returned 1 exit status
apxs:Error: Command failed with rc=65536
.
make[1]: *** [Makefile:22: mod_vhost_ldap.o] Error 1
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.53-2
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
apache2, which is due 

Processed: Bug#1007254 marked as pending in apache2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007254 [apache2-dev] apache2-dev: Missing dependency on libpcre2-dev for 
apxs2
Ignoring request to alter tags of bug #1007254 to the same tags previously set

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

Bug#1007254: marked as pending in apache2

[Yadd]

Control: tag -1 pending

Hello,

Bug #1007254 in apache2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/apache-team/apache2/-/commit/121d6456d1b1b00a82ed414aab5139beeb635bff


apache2-dev: add missing dependency on libpcre2-dev

Closes: #1007254


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007254

Bug#1007254: marked as pending in apache2

[Yadd]

Control: tag -1 pending

Hello,

Bug #1007254 in apache2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/apache-team/apache2/-/commit/151943f1e0be7ad9052f0eade3cc76785a869371


apache2-dev: add missing dependency on libpcre2-dev

Closes: #1007254


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007254

Processed: Bug#1007254 marked as pending in apache2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007254 [apache2-dev] apache2-dev: Missing dependency on libpcre2-dev for 
apxs2
Added tag(s) pending.

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

Bug#994178: marked as done (libnginx-mod-http-lua - init_worker_by_lua_block segfaults)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 12:09:40 +
with message-id 
and subject line Bug#994178: fixed in nginx 1.18.0-7
has caused the Debian Bug report #994178,
regarding libnginx-mod-http-lua - init_worker_by_lua_block segfaults
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.)


-- 
994178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnginx-mod-http-lua
Version: 1.18.0-6.1
Severity: serious

The nginx source bundles the http-lua module in a version incompatible
with nginx 1.18.  It segfaults immediately with a minimal config if a
"init_worker_by_lua_block" block is defined.  (I haven't looked much
further.)

This looks to be the same bug as
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1915391

This is broken in Stable.

Bastian

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

Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: nginx
Source-Version: 1.18.0-7
Done: Ondřej Nový 

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated nginx 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: Tue, 15 Mar 2022 11:50:18 +0100
Source: nginx
Architecture: source
Version: 1.18.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Nginx Maintainers 

Changed-By: Ondřej Nový 
Closes: 994178
Changes:
 nginx (1.18.0-7) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/p/CVE-2019-20372.patch: Drop, applied upstream.
   * http-auth-pam: Upgrade to 1.5.3.
   * http-echo: Upgrade to 0.62.
   * nchan: Upgrade to 1.2.15.
   * http-fancyindex: Upgrade to 0.5.2.
   * rtmp: Upgrade to 1.2.2.
   * http-lua: Upgrade to 0.10.15 (Closes: #994178).
   * http-lua: Rebase patch.
   * nchan: Drop GCC 10 patch, applied upstream.
   * d/watch: Bump version to 4.
   * Bump standards version to 4.6.1 (no changes).
   * d/copyright: Bump my copyright year.
 .
   [ Ondřej Surý ]
   * Add arm64 and ppc64el to list of luajit platforms.
 .
   [ Athos Ribeiro ]
   * d/nginx-common.nginx.service: Fix service shutdown desctiption to mention
 SIGQUIT instead of SIGSTOP (LP: #1919965).
Checksums-Sha1:
 eedc4445ed188a8f7b4ce3920b0bb670f19a4827 4780 nginx_1.18.0-7.dsc
 d1330cc95b5bd12d13efed7a5080d08f6ee3a3a4 1092372 nginx_1.18.0-7.debian.tar.xz
 83dbcf21171e06f5276bc7ee0b57c5166b2e4032 25637 nginx_1.18.0-7_amd64.buildinfo
Checksums-Sha256:
 2a5c844bb7b770ab1ed3b182473dcaa71ad2e4259a2421854206406cd1a308c6 4780 
nginx_1.18.0-7.dsc
 dd108c535811db9d7d24e1e1f7ce62b88bf6fdb645acb2255dc88ab16a899bb0 1092372 
nginx_1.18.0-7.debian.tar.xz
 1f9d1d63acca0302548f65d104a6ade211b3fb1c6ac18205315024c708bb3a5f 25637 
nginx_1.18.0-7_amd64.buildinfo
Files:
 9570fee307f9127156bbe45bbbe62ddf 4780 httpd optional nginx_1.18.0-7.dsc
 e8e82549d73578756f3c3b80d5c411ff 1092372 httpd optional 
nginx_1.18.0-7.debian.tar.xz
 5bb2b72a4e4314164e7987a968b97f36 25637 httpd optional 
nginx_1.18.0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAmIwdwUACgkQNXMSVZ0e
BksR4A/+MvrchZFNY06S7mcnCjFfw62a7gU8nBclBAyUKn/tSouGNFRO+5hyYVEM
n4wap7BREil5sbO0KzXgCReojH7wTRfiatROJ7bqcXs39aqHMBl3AvmFxWvr4Ehl
1pfTD6HfBfDmSii6eLrfT+dMoK4+vkHVN37bShI0xsAvAVC74UKvPSL9nk8GAzpW
Ly7nc4JBBRnB9fYRwrkYLYnph8DwdaM45okPvX0AThzN+OrfRcajBE4A+t2Un+gJ
AIfrn7iWYH+Nxo4Iog6RBK4ajaE4jC/yeHuhrpslBZaqCThXyp80VE4ZB97S0/bc
3wr+6Q/9r7EhlTZaSdFrmoCVWkARGG7V2xsl0+/DtkbLva1zvz2ApiGXIlrwoWb1
Jb7aW2xoLeCwpFK9RgEA2gyOaU0aVBPBMQWTdq/OsAZIZZkxJPBbNI5iz6bJC0LZ
WaT2J9KDGDtwUCFaWrj4NGtQeXJ6GUOPXxmuoMKekBi7Eims4WkHKeaIiMTz8ZKZ

Bug#1001801: marked as done (dogtag-pki: hits autopkgtest timeout on powerful workers)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 12:04:39 +
with message-id 
and subject line Bug#1001801: fixed in dogtag-pki 11.0.3-1
has caused the Debian Bug report #1001801,
regarding dogtag-pki: hits autopkgtest timeout on powerful workers
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.)


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

Source: dogtag-pk
Version: 11.0.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, because of some failure
"caused" by another package, I looked into the history of your 
autopkgtest [1] and I noticed it fails regularly on amd64 and armhf 
because it hits the autopkgtest timeout after 2:47 hours.


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

In this case I noticed that at least the failures on amd64 that I looked 
at all happened on ci-worker13, which is our 48 core, 256 GB machine, 
while the test on other amd64 workers passed (as far as I checked). 
Similar, our armhf worker is also powerful: 160 core, 255 GB. Is there 
anything in the test that you can think of that can't handle so much 
resources?


The last entry in one of the amd64 logs is this (maybe add at least a 
timeout on calls like that):

INFO: Creating /etc/pki/pki-tomcat/Catalina/localhost/kra.xml
INFO: Waiting for web application to start

If you need help to investigate this on the workers in question, don't 
hesitate to reach out.


Paul

[1] https://ci.debian.net/packages/d/dogtag-pki/


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 11.0.3-1
Done: Timo Aaltonen 

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated dogtag-pki 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: Tue, 15 Mar 2022 13:21:56 +0200
Source: dogtag-pki
Built-For-Profiles: noudeb
Architecture: source
Version: 11.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 1001801
Changes:
 dogtag-pki (11.0.3-1) unstable; urgency=medium
 .
   * New upstream release.
   * defauilt-webapp-timeout.diff: Force default webapp start timeout to
 120 seconds. (Closes: #1001801)
   * tests: Dump selftests.log if pkispawn fails, and also drop dumping
 pkispawn log since we have --debug now.
Checksums-Sha1:
 589930f5e6fcdfb36ceb2f5b015d06e0cc3ac0eb 3789 dogtag-pki_11.0.3-1.dsc
 2168bc78ca771abf997226ba379c148cf9ce4046 6846448 dogtag-pki_11.0.3.orig.tar.xz
 5f4d7edaae49ba94459235d8734e5fab8cfa2428 42860 
dogtag-pki_11.0.3-1.debian.tar.xz
 2e23e85ac49145b34093a668d1811f13ac4d369c 13254 
dogtag-pki_11.0.3-1_source.buildinfo
Checksums-Sha256:
 ceb97eeace955f765bdbcf4745d01bbf7050ad073cad1dc51f3c5d81fd5d0335 3789 
dogtag-pki_11.0.3-1.dsc
 1e342a149926911142945a5df8a3ae02f3807c201e67843dbeb3e56a2fbf34d1 6846448 
dogtag-pki_11.0.3.orig.tar.xz
 f4f81d39ef48228a29097158f6dc6cf40f5aa0cb7367ebb7b3ebdeabb5d87b44 42860 
dogtag-pki_11.0.3-1.debian.tar.xz
 3eaa1365c4d1baa02981484fa43c67c0e26714b65023334ef02cdcbc1cf585f9 13254 
dogtag-pki_11.0.3-1_source.buildinfo
Files:
 7a3dec18a6e305f8c40ac97ec876295c 3789 java optional dogtag-pki_11.0.3-1.dsc
 5a083abf0dccd7a928571edbd88ad21c 6846448 java optional 
dogtag-pki_11.0.3.orig.tar.xz
 7caf20ca6d6900eeb96fb710c4858040 42860 java optional 
dogtag-pki_11.0.3-1.debian.tar.xz
 10b8747162633f685c6bc2c09b8bc849 13254 java optional 
dogtag-pki_11.0.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1000336: Upgrading tbb

[Nilesh Patra]

On 3/14/22 11:51 AM, Andreas Tille wrote:

Hi,

Am Mon, Mar 14, 2022 at 12:13:50AM + schrieb Torrance, Douglas:

On Sun 13 Mar 2022 04:50:32 PM EDT, M. Zhou  wrote:

Recently I'm not able to test the build of libtbb-dev's reverse dependencies
as my build machine was out of access. That blocks my submission of the
transition bug and hence I'm stalled at this point.
According to some archlinux developers, this transition breaks a lot of
reverse dependencies since some of the core APIs have been changed.
Please expect a relatively negative rebuild result.

Help is welcome.


I've built both mathicgb and macaulay2 in unstable against TBB 2021 from
experimental and they're both ready to go for the transition.


If you ask me we should simply start the transition and see what needs
fixing ... may be asking release team for temporary removal from
testing.  We are in a quite early [...]


I just came to know a method to run salsa-CI for reverse-dependencies.
Probably we can use it


https://bzed.de/post/2021/01/building_reverse_build_dependencies_in_salsa_ci/

But since the reverse-deps might be large in number, we need to open an issue 
similar to this
to ask the CI admins once about it

https://salsa.debian.org/salsa/support/-/issues/291

Hope that helps.

Regards,
Nilesh



OpenPGP_signature
Description: OpenPGP digital signature

Bug#967228: marked as done (uftrace: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 10:48:55 +
with message-id 
and subject line Bug#967228: fixed in uftrace 0.11-1
has caused the Debian Bug report #967228,
regarding uftrace: Unversioned Python removal in sid/bullseye
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.)


-- 
967228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uftrace
Version: 0.9.4-0.2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: uftrace
Source-Version: 0.11-1
Done: Gürkan Myczko 

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated uftrace 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, 25 Nov 2021 11:14:00 +0100
Source: uftrace
Architecture: source
Version: 0.11-1
Distribution: experimental
Urgency: medium
Maintainer: paul cannon 
Changed-By: Gürkan Myczko 
Closes: 938745 966988 967228
Changes:
 uftrace (0.11-1) experimental; urgency=medium
 .
   * Add myself to Uploaders.
   * Team upload.
   * New upstream version. (Closes: #966988, #967228, #938745)
   * Bump standards version to 4.6.0.
   * Bump debhelper version to 12, drop d/compat.
   * d/clean: added.
Checksums-Sha1:
 5a48e7ea93c74a14f4a562428e5b500ba28e06b8 2006 uftrace_0.11-1.dsc
 c187f6fe26757faacebf101f60c097d8dcf588b1 1120956 uftrace_0.11.orig.tar.gz
 f04dc747e3290c146aa81e9771b3b5526ef79ba3 4856 uftrace_0.11-1.debian.tar.xz
 e1bf645af46dcf8c407b06e0954ff5dc3fdc08cf 7947 uftrace_0.11-1_source.buildinfo
Checksums-Sha256:
 145e34458830e148e36b48648895356891d686fee72ae3e1a6967ad91dfd3793 2006 
uftrace_0.11-1.dsc
 101dbb13cb3320ee76525ec26426f2aa1de4e3ee5af74f79cb403ae4d2c6c871 1120956 
uftrace_0.11.orig.tar.gz
 85d12f288b3a5460fccb685d9839bd5891e7b004f6c74fdc2830f2693389427a 4856 
uftrace_0.11-1.debian.tar.xz
 ce7cfa3a3a4a74f0abfebb1e28e483eb01f383737eec3f50787acaef50946e94 7947 
uftrace_0.11-1_source.buildinfo
Files:
 b16e6394023cd1a843947cf100c65413 2006 utils optional uftrace_0.11-1.dsc
 8f0966c636ba4b3985d1a9f2bfad05c7 1120956 utils optional 
uftrace_0.11.orig.tar.gz
 f3fbe76156763f07c5202070417c4cdc 4856 utils optional 
uftrace_0.11-1.debian.tar.xz
 95297a773a93eee938022b07c4536bc3 7947 utils optional 
uftrace_0.11-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmIwahQACgkQEWhSvN91
FcD7fQ//Qkz03o8+grycU6W8LHMTxFzZ24SiBA5LziKAxEZWHWFnWYocE7YgUfvd
tYF/T/TcGtcdhjguQptNp+ZLOmsH3zZOFp9Uo3kevkH9L3eQhIaAsfBCtAaOK75M
0jgFEc9oGQdYXO2A4XdRSzDlteFSV2W5zfAijUUbxT12oSjha0/4RrkQUs6KIoVs
SKUEKla1D1kJOPIjJgKdRql1EaqIqyr9J0wtLCFx8u7kTY+MILoydzuh8TU0Lt74
qZk/7quhw+z9h6xbUH0bEer38kRJOFVhSaxnemUXmNjqjp9rTnqyOgQKzMmuP+5l
E+EGEF7Dl7nUkLW/lxbOzM2SJqOi5+A3WWtbOXGHle0y7hytGEooXLc/MUWqOgUE
MJLeZw38tD+ZY1u4OAYkDZFT9jdBqSiMKFDLnpMV/kuruC8ah1bB5ePQiAt590lk
rU2XZjONe5K7f2iTC8iazV+h2rW3Jcx1zkQwWRGL3xO8puCul8bntjU435Fm35tj

Bug#966988: marked as done (uftrace: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 10:48:55 +
with message-id 
and subject line Bug#966988: fixed in uftrace 0.11-1
has caused the Debian Bug report #966988,
regarding uftrace: FTBFS: test failed
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.)


-- 
966988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uftrace
Version: 0.9.4-0.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gcc -o /<>/uftrace.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/uftrace.c
> gcc -o /<>/cmds/dump.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/dump.c
> gcc -o /<>/cmds/graph.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/graph.c
> gcc -o /<>/cmds/info.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/info.c
> gcc -o /<>/cmds/live.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/live.c
> gcc -o /<>/cmds/record.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/record.c
> gcc -o /<>/cmds/recv.ot -c -D_GNU_SOURCE 
> -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote 
> /<> -iquote /<> -iquote 
> /<>/arch/x86_64 -W -Wall -Wno-unused-parameter 
> -Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON2 
> -I/usr/include/python2.7 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW 
> -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_LIBELF 
> -DHAVE_LIBDW -DHAVE_LIBCAPSTONE -I/usr/include/capstone -DUNIT_TEST -include 
> /<>/tests/unittest.h -Wno-sign-compare -pg -g 
> /<>/cmds/recv.c
> gcc -o /<>/cmds/replay.ot 

Bug#1004662: prosody: postinst keeps messing with snakeoil certs

[Victor Seva]

Hi,

On 3/15/22 10:29, Martin wrote:

On 2022-02-01 23:07, Martin wrote:

There have been a number of prosody package bugs related to snakeoil
certs. I wonder, if it is worth the trouble?

For most real world installations, people get LE certs or buy them or
they have their own CA.

Maybe prosody package should just drop the whole snakeoil stuff?


Now that 0.12 is released, it would be nice to get rid of this blocker.
Is there a good reason to cling to snakeoil certificates?



No one that I'm aware of. I'm in favor of just remove that part.

--
-
|   ,''`. |
|  : :' : |
|  `. `'  Victor Seva |
|`-PGP Key ID: 0x51A09B18CF5A5068 |
 -


OpenPGP_0x51A09B18CF5A5068.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006948: gcc-12: FTBFS on mips64el

[Adrian Bunk]

On Wed, Mar 09, 2022 at 05:49:04PM +0800, YunQiang Su wrote:
> On Tue, 08 Mar 2022 20:53:46 +0100 Paul Gevers  wrote:
> > Source: gcc-12
> > Version: 12-20220222-1
> > Severity: serious
> > Tags: ftbfs
> > 
> > Dear Matthias, GCC maintainers,
> > 
> > gcc-12 fails to build from source on mips64el in unstable. Normally this 
> > isn't an issue, but it builds a Build-Depends of gcc-11 which now can't 
> > migrate because it can't be build on mips64el.
> > 
> 
> We are try our best to find the root cause of this problem:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104317 
> 
>...

It seems something (in the upstream D updates?) fixed it:
https://buildd.debian.org/status/logs.php?pkg=gcc-12=mips64el

cu
Adrian

Processed: found 1004662 in 0.11.9-2

[Debian Bug Tracking System]

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

> found 1004662 0.11.9-2
Bug #1004662 [prosody] prosody: postinst keeps messing with snakeoil certs
Marked as found in versions prosody/0.11.9-2.
> thanks
Stopping processing here.

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

Bug#1004662: prosody: postinst keeps messing with snakeoil certs

[Martin]

On 2022-02-01 23:07, Martin wrote:
> There have been a number of prosody package bugs related to snakeoil
> certs. I wonder, if it is worth the trouble?
>
> For most real world installations, people get LE certs or buy them or
> they have their own CA.
>
> Maybe prosody package should just drop the whole snakeoil stuff?

Now that 0.12 is released, it would be nice to get rid of this blocker.
Is there a good reason to cling to snakeoil certificates?

Processed: Re:

[Debian Bug Tracking System]

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

> # Had a typo in bug number
> reassign 993350 libsane1 1.0.32-4
Bug #993350 [xsane] sane-epson2: unable to start scanner (Perfection 1650)
Bug reassigned from package 'xsane' to 'libsane1'.
No longer marked as found in versions xsane/0.999-12.
Ignoring request to alter fixed versions of bug #993350 to the same values 
previously set
Bug #993350 [libsane1] sane-epson2: unable to start scanner (Perfection 1650)
Marked as found in versions sane-backends/1.0.32-4.
> forwarded 993350 https://gitlab.com/sane-project/backends/-/issues/445
Bug #993350 [libsane1] sane-epson2: unable to start scanner (Perfection 1650)
Set Bug forwarded-to-address to 
'https://gitlab.com/sane-project/backends/-/issues/445'.
> fixed 993350 1.1.1-2
Bug #993350 [libsane1] sane-epson2: unable to start scanner (Perfection 1650)
Marked as fixed in versions sane-backends/1.1.1-2.
>
End of message, stopping processing here.

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

Processed (with 3 errors): your mail

[Debian Bug Tracking System]

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

> retitle 993350 sane-epson2: unable to start scanner (Perfection 1650)
Bug #993350 [xsane] xsane: Scanimage detects scanner but Xsane won't start it
Changed Bug title to 'sane-epson2: unable to start scanner (Perfection 1650)' 
from 'xsane: Scanimage detects scanner but Xsane won't start it'.
> reassign 933350 libsane1 1.0.32-4
Failed to clear fixed versions and reopen on 933350: Not altering archived 
bugs; see unarchive.

> forwarded 933350 https://gitlab.com/sane-project/backends/-/issues/445
Failed to set the forwarded-to-address of 933350: Not altering archived bugs; 
see unarchive.

> fixed 933350 1.1.1-2
Failed to add fixed on 933350: Not altering archived bugs; see unarchive.

>
End of message, stopping processing here.

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

Bug#1002389: marked as done (pytest: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --system=custom returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2022 07:18:52 +
with message-id 
and subject line Bug#1002389: fixed in pytest 6.2.5-2
has caused the Debian Bug report #1002389,
regarding pytest: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.10 3.9" --system=custom returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom
> I: pybuild pybuild:286: mkdir -p 
> /<>/debian/tmp/test-working-directory
> I: pybuild base:237: cd /<>/debian/tmp/test-working-directory && 
> python3.10 -m pytest --lsof -rfsxX 
> --ignore=/<>/testing/test_entry_points.py 
> --ignore=/<>/testing/test_terminal.py -k 'not 
> test_code_highlight' /<>/testing
> = test session starts 
> ==
> platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: pyproject.toml
> plugins: hypothesis-5.43.3
> collected 2904 items / 4 deselected / 2900 selected
> 
> ../../../testing/acceptance_test.py ..   [  
> 0%]
> ../../../testing/deprecated_test.py .[  
> 0%]
> ../../../testing/test_argcomplete.py ..  [  
> 0%]
> ../../../testing/test_assertion.py . [  
> 2%]
> .[  
> 2%]
> ../../../testing/test_assertrewrite.py . [  
> 4%]
> ..   [  
> 4%]
> ../../../testing/test_capture.py ... [  
> 5%]
> .ss..[  
> 6%]
> ../../../testing/test_collection.py .[  
> 6%]
> ../../../testing/test_compat.py ...  [  
> 6%]
> ../../../testing/test_config.py  [  
> 8%]
>  [  
> 8%]
> ../../../testing/test_conftest.py ...[  
> 8%]
> ../../../testing/test_debugging.py ..[  
> 8%]
> ../../../testing/test_doctest.py ... [  
> 9%]
> ../../../testing/test_faulthandler.py ...[  
> 9%]
> ../../../testing/test_findpaths.py . [  
> 9%]
> ../../../testing/test_junitxml.py    [ 
> 10%]
> ../../../testing/test_main.py .  [ 
> 10%]
> ../../../testing/test_mark.py    [ 
> 10%]
> ../../../testing/test_mark_expression.py ... [ 
> 11%]
>  [ 
> 13%]
> ../../../testing/test_monkeypatch.py ... [ 
> 14%]
> ../../../testing/test_nodes.py ...   [ 
> 15%]
> ../../../testing/test_nose.py .. [ 
> 15%]
> ../../../testing/test_parseopt.py    [ 
> 16%]
> ../../../testing/test_pastebin.py    [ 
> 16%]
> ../../../testing/test_pathlib.py ... [ 
> 17%]
> s[ 
> 18%]
> ../../../testing/test_pluginmanager.py . [ 
> 18%]
> ../../../testing/test_pytester.py .  [ 
> 19%]
> ../../../testing/test_recwarn.py ... [ 
> 20%]
>  [ 
> 20%]
> ../../../testing/test_runner.py ..   [ 
> 21%]
> ../../../testing/test_skipping.py .  [ 
> 21%]
> ../../../testing/test_store.py . [ 
> 21%]
> 

Bug#1002389: marked as pending in pytest

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1002389 in pytest reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pytest/-/commit/0a89ada70a16253323430431cf904220496d0050


Add upstream patch to fix test failure

Closes: #1002389


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002389

Processed: Bug#1002389 marked as pending in pytest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002389 [src:pytest] pytest: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.10 3.9" --system=custom returned exit code 
13
Added tag(s) pending.

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

Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error

[Stefan Kropp]

Hello,

I just found this issue note on upstream project:
https://dev.gajim.org/gajim/gajim/-/issues/10779#note_204952

It's sounds quite similar. Maybe a corrupted internal gajim
db-file.

-- 
Stefan