Bug#1000336: numba: FTBFS with Python 3.10

[Andreas Tille]

Hi,

I've commited version 0.54.1 to Git since I assume that we have better
chances for Python3.10 support in the more recent upstream version.
Unfortunately the build stops with

dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:237: python3.10 setup.py clean 
...
  from distutils import sysconfig
Traceback (most recent call last):
  File "/build/numba-0.54.1/setup.py", line 51, in 
_guard_py_ver()
  File "/build/numba-0.54.1/setup.py", line 48, in _guard_py_ver
raise RuntimeError(msg.format(cur_py, min_py, max_py))
RuntimeError: Cannot install on Python version 3.10.1; only versions 
>=3.7,<3.10 are supported.
E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
python3.10 setup.py clean 


Hoping for an upstream fix of #7562 in their tracker now.

I think pushing for Python3.10 in Debian before such packages with lots
of rdepends (specifically python3-pandas) are ported is quite demanding.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: bug 1001425 is forwarded to https://github.com/OCA/odoorpc/issues/66

[Debian Bug Tracking System]

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

> forwarded 1001425 https://github.com/OCA/odoorpc/issues/66
Bug #1001425 [src:python-odoorpc] python-odoorpc: (autopkgtest) needs update 
for python3.10: module 'collections' has no attribute 'MutableMapping'
Set Bug forwarded-to-address to 'https://github.com/OCA/odoorpc/issues/66'.
> thanks
Stopping processing here.

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

Processed: bug 1001425 is forwarded to https://github.com/osiell/odoorpc/issues/54

[Debian Bug Tracking System]

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

> forwarded 1001425 https://github.com/osiell/odoorpc/issues/54
Bug #1001425 [src:python-odoorpc] python-odoorpc: (autopkgtest) needs update 
for python3.10: module 'collections' has no attribute 'MutableMapping'
Changed Bug forwarded-to-address to 
'https://github.com/osiell/odoorpc/issues/54' from 
'https://github.com/OCA/odoorpc/issues/66'.
> thanks
Stopping processing here.

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

Bug#1001425: python-odoorpc: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableMapping'

[Philipp Huebner]

Hi,

there is a patch available at
https://github.com/OCA/odoorpc/pull/67/commits/7335e594b02ce7645beefa67d541d5b34df0daaf,
I will give that a try.

Regards
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bug 1001425 is forwarded to https://github.com/OCA/odoorpc/issues/66

[Debian Bug Tracking System]

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

> forwarded 1001425 https://github.com/OCA/odoorpc/issues/66
Bug #1001425 [src:python-odoorpc] python-odoorpc: (autopkgtest) needs update 
for python3.10: module 'collections' has no attribute 'MutableMapping'
Changed Bug forwarded-to-address to 'https://github.com/OCA/odoorpc/issues/66' 
from 'https://github.com/osiell/odoorpc/issues/54'.
> thanks
Stopping processing here.

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

Bug#1001345: marked as done (jupyterlab-pygments: autopkgtest tests for all supported python3s but fails to install them)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 09:04:13 +
with message-id 
and subject line Bug#1001345: fixed in jupyterlab-pygments 0.1.2-8
has caused the Debian Bug report #1001345,
regarding jupyterlab-pygments: autopkgtest tests for all supported python3s but 
fails to install them
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.)


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

Source: jupyterlab-pygments
Version: 0.1.2-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.9.8-1
jupyterlab-pygmentsfrom testing0.1.2-7
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test tries to test for all supported Python3 versions, but fails to 
ensure all those versions are actually installed during the test.


Currently this regression is blocking the migration of python3-defaults 
to testing [1].


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-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jupyterlab-pygments/17376875/log.gz

Testing with python3.10:
bash: line 1: python3.10: command not found
autopkgtest [21:40:34]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jupyterlab-pygments
Source-Version: 0.1.2-8
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
jupyterlab-pygments, 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.
Julien Puydt  (supplier of updated jupyterlab-pygments 
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: Fri, 10 Dec 2021 09:39:54 +0100
Source: jupyterlab-pygments
Architecture: source
Version: 0.1.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julien Puydt 
Closes: 1001345
Changes:
 jupyterlab-pygments (0.1.2-8) unstable; urgency=medium
 .
   * Detect if the Python version is installed before running
   it. (Closes: #1001345)
Checksums-Sha1:
 5772295f4ddf29c1b1509a792f4d3ce901da4fe3 2223 jupyterlab-pygments_0.1.2-8.dsc
 7fb7e583504b7dfdf5660430813c1edb6a4a94b1 2396 
jupyterlab-pygments_0.1.2-8.debian.tar.xz
 aa4b72c3939da2e00ba4cfe0dd8e143b342cd0a7 7042 
jupyterlab-pygments_0.1.2-8_source.buildinfo
Checksums-Sha256:
 7c9eb27061a3089e1dac8a62f2bbd638521df5043823554d3dca123a5607c8e5 2223 
jupyterlab-pygments_0.1.2-8.dsc
 8d6feee7eff162d9b1d2a9fc735b8c098a3846229860d59b1827af929867da49 2396 
jupyterlab-pygments_0.1.2-8.debian.tar.xz
 bf2a2b485be1c6391ef33f4e0de945e6cdc3661e5267fb65e3fc9df799a95c84 7042 
jupyterlab-pygments_0.1.2-8_source.buildinfo
Files:
 450237f5190596106de1a102964448af 2223 python optional 
jupyterlab-pygments_0.1.2-8.dsc
 f013438ec99c5997a6fdffe95eebae20 2396 python optional 
jupyterlab-pygments_0.1.2-8.debian.tar.xz
 a4d9a7d2d53675966902726bd92fbb06 7042 python optional 
jupyterlab-pygments_0.1.2-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmGzEpUSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRrKMP/1ht4CVEYrdc11BuvktG/v/HxWCmSObZ
C4CLA8hZp3T4QUQtwWtgfkR80hIc/0Le4S8mdqnu2BvXgvovQajT/Q9fMnaBHgcY
FRY7N52/4SmFZqH2faD5LYEG+HPjwQ7sYxB1ZDnU4lvZtJtLSdM8v/clc9bLXF3V
hqqlU6RpA6YBsCB2dALOqlOTpYkuiYQiOlVenBJILaDi2nLTfC4kaQtnkIAb+g63
madwW2Z/4wmCjmR26qOHVpe3AYY/hmMVCen82/9Rn41OGqDhqkz2gDSBWM3pkbpe
1NkJrYTKIpcOcU4vENkL

Bug#1001447: missing Depends on cl-esrap and cl-ppcre

[Sébastien Villemot]

Package: cl-abnf
Version: 20150608-1.1
Severity: serious
Tags: patch

The subject says it all. The abnf system requires the esrap and cl-ppcre
systems, but this is not reflected at the level of Debian dependencies.

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1000573: Upstream uninterested

[Stéphane Glondu]

Hi,

On Fri, 10 Dec 2021 07:57:09 +0100 Julien Puydt 
wrote:
> after some discussion with upstream, they're not ready to support those
> architectures, so we can just drop them.

Then, could you have the (old) binaries of unsupported architectures
removed from unstable?


Cheers,

-- 
Stéphane

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

[Sébastien Villemot]

Le jeudi 09 décembre 2021 à 16:10 +0100, Christoph Berg a écrit :
> Re: To Sébastien Villemot
> > Unfortunately, pgloader still doesn't compile:
> 
> > While evaluating the form starting at line 21, column 0
> >   of 
> > #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal 
> > SIMPLE-ERROR:
> >   Compilation failed: * is not permitted as an argument to the FUNCTION 
> > type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp
> 
> Looking around for something else I discovered #999625 in cl-esrap
> which fixes this problem. I uploaded the fix in an NMU. (I guess you
> might also take over that package?)
> 
> But pgloader still doesn't build: :(
> 
> ; wrote 
> /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf-tmp5FHTGX61.fasl
> ; compilation finished in 0:00:00.080
> While evaluating the form starting at line 21, column 0
>   of 
> #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal 
> TYPE-ERROR:
>   The values
> (#   :IN
>   
> "/srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf.fasl")
>  {53C1EADB}>
>  NIL NIL)
> 
>   are not of type
> (VALUES FUNCTION &OPTIONAL)

The problem seems again related to cl-esrap. I noticed that the Debian
package tracks an old (dead) upstream, while there is a new alive fork.
I’ll take over that package and hopefully fix the problem.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#1001426: marked as done (python-pbr: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableSet')

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 11:16:38 +0100
with message-id <0b662c67-1c28-4492-8239-7672e1fc3...@debian.org>
and subject line Bug was in testresources
has caused the Debian Bug report #1001426,
regarding python-pbr: (autopkgtest) needs update for python3.10: module 
'collections' has no attribute 'MutableSet'
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.)


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

Source: python-pbr
Version: 5.6.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-pbr fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-pbr from testing5.6.0-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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pbr/17420663/log.gz

=
Failures during discovery
=
--- import errors ---
Failed to import test module: pbr.tests.test_commands
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in 
_find_test_path

module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
_get_module_from_name

__import__(name)
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/test_commands.py", 
line 43, in 

from pbr.tests import base
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/base.py", 
line 48, in 

import testresources
  File "/usr/lib/python3/dist-packages/testresources/__init__.py", line 
195, in 

class _OrderedSet(collections.MutableSet):
AttributeError: module 'collections' has no attribute 'MutableSet'

Failed to import test module: pbr.tests.test_core
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in 
_find_test_path

module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
_get_module_from_name

__import__(name)
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/test_core.py", 
line 48, in 

from pbr.tests import base
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/base.py", 
line 48, in 

import testresources
  File "/usr/lib/python3/dist-packages/testresources/__init__.py", line 
195, in 

class _OrderedSet(collections.MutableSet):
AttributeError: module 'collections' has no attribute 'MutableSet'

Failed to import test module: pbr.tests.test_files
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in 
_find_test_path

module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
_get_module_from_name

__import__(name)
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/test_files.py", 
line 23, in 

from pbr.tests import base
  File 
"/tmp/autopkgtest-lxc.8jbfzfdi/downtmp/build.1ju/src/pbr/tests/base.py", 
line 48, in 

import testresources
  File "/usr/lib/python3/dist-packages/testresources/__init__.py", line 
195, in 

class _OrderedSet(collections.M

Processed: Mention fixed in 2.x series

[Debian Bug Tracking System]

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

> fixed 996366 2.1.1-1
Bug #996366 {Done: Daniel Leidert } 
[src:ruby-regexp-parser] ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test 
"ruby3.0" failed:   Failure/Error: (min..max).tap { |r| 
r.define_singleton_method(:minmax) { [min, max] } }
Marked as fixed in versions ruby-regexp-parser/2.1.1-1.
> thanks
Stopping processing here.

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

Bug#984027: marked as done (darkice: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 11:34:36 +
with message-id 
and subject line Bug#984027: fixed in darkice 1.3-0.3
has caused the Debian Bug report #984027,
regarding darkice: ftbfs with GCC-11
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.)


-- 
984027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:darkice
Version: 1.3-0.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/darkice_1.3-0.2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
In file included from AudioSource.cpp:37:
Util.h:83:49: error: ISO C++17 does not allow dynamic exception specifications
   83 | Util ( void )   throw ( Exception )
  | ^
Util.h:94:49: error: ISO C++17 does not allow dynamic exception specifications
   94 | Util ( const Util &   e )   throw ( Exception )
  | ^
Util.h:105:49: error: ISO C++17 does not allow dynamic exception specifications
  105 | ~Util ( void )  throw ( Exception )
  | ^
Util.h:117:49: error: ISO C++17 does not allow dynamic exception specifications
  117 | operator= ( const Util &   u )  throw ( Exception )
  | ^
Util.h:134:53: error: ISO C++17 does not allow dynamic exception specifications
  134 | strLen (const char* str )   throw ( Exception );
  | ^
Util.h:146:53: error: ISO C++17 does not allow dynamic exception specifications
  146 | const char* src )   throw ( Exception );
  | ^
Util.h:159:53: error: ISO C++17 does not allow dynamic exception specifications
  159 | const char* src )   throw ( Exception );
  | ^
Util.h:169:53: error: ISO C++17 does not allow dynamic exception specifications
  169 | strDup (const char* str )   throw ( Exception );
  | ^
Util.h:184:53: error: ISO C++17 does not allow dynamic exception specifications
  184 | unsigned intlen = 0 )   throw ( Exception );
  | ^
Util.h:194:39: error: ISO C++17 does not allow dynamic exception specifications
  194 | strToL ( const char* str) throw ( Exception );
  |   ^
Util.h:204:53: error: ISO C++17 does not allow dynamic exception specifications
  204 | strToD ( const char* str )  throw ( Exception );
  | ^
Util.h:218:57: error: ISO C++17 does not allow dynamic exception specifications
  218 | 

Bug#1001425: marked as pending in python-odoorpc

[Philipp Huebner]

Control: tag -1 pending

Hello,

Bug #1001425 in python-odoorpc 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/python-odoorpc/-/commit/5b3388ca726c6b2e9db1518a68f00e13125f8313


add patch to become compatible with Python 3.10 (Closes: #1001425)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001425

Processed: Bug#1001425 marked as pending in python-odoorpc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001425 [src:python-odoorpc] python-odoorpc: (autopkgtest) needs update 
for python3.10: module 'collections' has no attribute 'MutableMapping'
Added tag(s) pending.

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

Processed: tagging 1001365

[Debian Bug Tracking System]

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

> tags 1001365 + pending
Bug #1001365 [src:pastel] pastel: autopkgtest tests for all supported python3s 
but fails to install them
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1001425: marked as done (python-odoorpc: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableMapping')

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 13:19:43 +
with message-id 
and subject line Bug#1001425: fixed in python-odoorpc 0.7.0-4
has caused the Debian Bug report #1001425,
regarding python-odoorpc: (autopkgtest) needs update for python3.10: module 
'collections' has no attribute 'MutableMapping'
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.)


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

Source: python-odoorpc
Version: 0.7.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-odoorpc fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-odoorpc from testing0.7.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. 
https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-odoorpc/17420662/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/odoorpc/__init__.py", line 59, 
in 

from odoorpc.odoo import ODOO
  File "/usr/lib/python3/dist-packages/odoorpc/odoo.py", line 24, in 


from odoorpc import rpc, error, tools
  File "/usr/lib/python3/dist-packages/odoorpc/rpc/__init__.py", line 
38, in 

from odoorpc.tools import v
  File "/usr/lib/python3/dist-packages/odoorpc/tools.py", line 31, in 


class Config(collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'
autopkgtest [13:31:41]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-odoorpc
Source-Version: 0.7.0-4
Done: Philipp Huebner 

We believe that the bug you reported is fixed in the latest version of
python-odoorpc, 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.
Philipp Huebner  (supplier of updated python-odoorpc 
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: Fri, 10 Dec 2021 13:52:31 +0100
Source: python-odoorpc
Architecture: source
Version: 0.7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Philipp Huebner 
Closes: 1001425
Changes:
 python-odoorpc (0.7.0-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + python-odoorpc-doc: Add Multi-Arch: foreign.
 .
   [ Philipp Huebner ]
   * Add patch to become compatible with Python 3.10 (Closes: #1001425)
   * debian/watch: remove filenamemangle
   * debian/copyright: update years
   * Update Standards-Version: 4.6.0 (no changes needed)
Checksums-Sha1:
 5f5845110da4e825648c63e49d1f8355c10d22e0 2172 python-odoorpc_0.7.0-4.dsc
 19af582c5138fa7164bfcb0

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 997080 1001136
Bug #997080 {Done: Mathieu Malaterre } [src:openvdb] openvdb: 
FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Bug #997080 {Done: Mathieu Malaterre } [src:openvdb] openvdb: 
FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Marked as found in versions openvdb/9.0.0-3.
Bug #1001136 [src:openvdb] openvdb binary-any FTBFS: help2man: can't get 
`--help' info from ./debian/tmp/usr/bin/vdb_view
Marked Bug as done
Added tag(s) bookworm, wontfix, and sid.
Merged 997080 1001136
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> block 997080 by 1001457
Bug #997080 {Done: Mathieu Malaterre } [src:openvdb] openvdb: 
FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Bug #1001136 {Done: Mathieu Malaterre } [src:openvdb] openvdb 
binary-any FTBFS: help2man: can't get `--help' info from 
./debian/tmp/usr/bin/vdb_view
997080 was not blocked by any bugs.
997080 was not blocking any bugs.
Added blocking bug(s) of 997080: 1001457
1001136 was not blocked by any bugs.
1001136 was not blocking any bugs.
Added blocking bug(s) of 1001136: 1001457
Warning: Unknown package 'src:libstdc++6'
> affects 1001457 src:openvdb
Bug #1001457 [src:libstdc++6] libstdc++: Possible miscompilation visible using 
pthread + exception
Warning: Unknown package 'src:libstdc++6'
Added indication that 1001457 affects src:openvdb
Warning: Unknown package 'src:libstdc++6'
>
End of message, stopping processing here.

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

Processed: closing 1001421

[Debian Bug Tracking System]

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

> close 1001421
Bug #1001421 [src:python-launchpadlib] python-launchpadlib: (autopkgtest) needs 
update for python3.10: module 'collections' has no attribute 'MutableSet'
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfound 1001421 in python-launchpadlib/1.10.15.1-1

[Debian Bug Tracking System]

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

> notfound 1001421 python-launchpadlib/1.10.15.1-1
Bug #1001421 {Done: Stefano Rivera } 
[src:python-launchpadlib] python-launchpadlib: (autopkgtest) needs update for 
python3.10: module 'collections' has no attribute 'MutableSet'
No longer marked as found in versions python-launchpadlib/1.10.15.1-1.
> thanks
Stopping processing here.

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

Bug#1001020: marked as done (python-anndata: FTBFS with sklearn 1.0.1-1: ModuleNotFoundError: No module named 'sklearn.utils.testing')

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 14:36:31 +
with message-id 
and subject line Bug#1001020: fixed in python-anndata 0.7.8-1
has caused the Debian Bug report #1001020,
regarding python-anndata: FTBFS with sklearn 1.0.1-1: ModuleNotFoundError: No 
module named 'sklearn.utils.testing'
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.)


-- 
1001020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-anndata
Version: 0.7.5+ds-3
Severity: serious

Dear Maintainer,

python-anndata FTBFS, it probably needs changes with new sklearn.
Log pasted below.

Regards,
Nilesh

copying anndata/tests/data/excel.xlsx -> 
/<>/.pybuild/cpython3_3.9_anndata/build/anndata/tests/data
   dh_auto_test -O--buildsystem=pybuild
I: pybuild pybuild:285: cp -R /<>/anndata.egg-info 
/<>/.pybuild/cpython3_3.10_anndata/build
I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_anndata/build; 
python3.10 -m pytest -v
= test session starts ==
platform linux -- Python 3.10.0+, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
/usr/bin/python3.10
cachedir: .pytest_cache
rootdir: /<>, configfile: pyproject.toml
plugins: cov-3.0.0
collecting ... collected 1449 items / 2 errors / 1447 selected

 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.10_anndata/build/anndata/tests/test_inplace_subset.py _
anndata/tests/test_inplace_subset.py:3: in 
from sklearn.utils.testing import assert_array_equal
E   ModuleNotFoundError: No module named 'sklearn.utils.testing'
_ ERROR collecting 
.pybuild/cpython3_3.10_anndata/build/anndata/tests/test_inplace_subset.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.10_anndata/build/anndata/tests/test_inplace_subset.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
anndata/tests/test_inplace_subset.py:3: in 
from sklearn.utils.testing import assert_array_equal
E   ModuleNotFoundError: No module named 'sklearn.utils.testing'
=== warnings summary ===
../../../../../../usr/lib/python3/dist-packages/natsort/compat/fastnumbers.py:7
  /usr/lib/python3/dist-packages/natsort/compat/fastnumbers.py:7: 
DeprecationWarning: The distutils package is deprecated and slated for removal 
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
from distutils.version import StrictVersion

anndata/core.py:3
  /<>/.pybuild/cpython3_3.10_anndata/build/anndata/core.py:3: 
DeprecationWarning: Please only import from anndata, not anndata.core
warn("Please only import from anndata, not anndata.core", 
DeprecationWarning)

anndata/readwrite.py:3
  /<>/.pybuild/cpython3_3.10_anndata/build/anndata/readwrite.py:3: 
DeprecationWarning: Please only import from anndata, not anndata.readwrite
warn("Please only import from anndata, not anndata.readwrite", 
DeprecationWarning)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 
ERROR anndata/tests/test_inplace_subset.py - ModuleNotFoundError: No module n...
ERROR anndata/tests/test_inplace_subset.py
!!! Interrupted: 2 errors during collection 
 3 warnings, 2 errors in 1.71s =
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.10_anndata/build; python3.10 -m pytest -v
I: pybuild pybuild:285: cp -R /<>/anndata.egg-info 
/<>/.pybuild/cpython3_3.9_anndata/build
I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9_anndata/build; 
python3.9 -m pytest -v
= test session starts ==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
/usr/bin/python3.9
cachedir: .pytest_cache
rootdir: /<>, configfile: pyproject.toml
plugins: cov-3.0.0
collecting ... collected 1449 items / 2 errors / 1447 selected

 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.9_anndata/build/anndata/tests/test_inplace_subset.py _
anndata/tests/test_inplace_subset.py:3: in 
from sklearn.utils.testing import assert_array_equal
E   ModuleNotFoundError: No module named 'sklearn.utils.testing'
_ ERROR collecti

Bug#1001349: marked as done (python-anndata: autopkgtest fail with pandas 1.3: missing openpyxl)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 14:36:31 +
with message-id 
and subject line Bug#1001349: fixed in python-anndata 0.7.8-1
has caused the Debian Bug report #1001349,
regarding python-anndata: autopkgtest fail with pandas 1.3: missing openpyxl
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.)


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

Package: python3-anndata
Version: 0.7.5+ds-3
Severity: serious
Tags: patch

pandas.read_excel() now defaults to using openpyxl only, not 
openpyxl-or-xlrd:

https://pandas.pydata.org/pandas-docs/version/1.3.4/whatsnew/v1.2.0.html

Please update your build and test dependencies.

(This didn't show up in my local test run because I did that in 
unstable, where #1001020 appears first.)
--- End Message ---
--- Begin Message ---
Source: python-anndata
Source-Version: 0.7.8-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
python-anndata, 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.
Andreas Tille  (supplier of updated python-anndata 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: Fri, 10 Dec 2021 14:38:15 +0100
Source: python-anndata
Architecture: source
Version: 0.7.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1001020 1001349
Changes:
 python-anndata (0.7.8-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #1001349, #1001020
   * Point watch file to Github
   * Drop unnecessary Files-Excluded
   * Standards-Version: 4.6.0 (routine-update)
   * Provide debian/tests/run-unit-test script
   * Remove unneeded debian/source/options
   * PYBUILD_SYSTEM=flit to deal with missing setup.py
   * Build-Depends: python3-openpyxl
   * Ignore test importing scanpy data
   * Deactivate test requiring python3-numba since this is not ported to
 Python3.10 yet
   * debian/salsa-ci.yaml: suppress build on i386 where several tests are
 failing
Checksums-Sha1:
 de4df0181abfb2fe065dbbfdf479b22184f3cc75 2713 python-anndata_0.7.8-1.dsc
 7bb564ce333691d228a718bea5788b53ea7b24e8 137261 
python-anndata_0.7.8.orig.tar.gz
 0385ecf0cac9b0825e4fe1bf238bd853bab1b848 5940 
python-anndata_0.7.8-1.debian.tar.xz
 ba7260f32d95d96af78ced87151d966f6b8e86db 10070 
python-anndata_0.7.8-1_amd64.buildinfo
Checksums-Sha256:
 f091a90b8541e6629aca3e3361ceea1f82ee26e9b3fd7daf922d928cfd05c761 2713 
python-anndata_0.7.8-1.dsc
 686fdc9dc046d842ccbbaf472409724585fb99b76c59385e302d2686f7797eb0 137261 
python-anndata_0.7.8.orig.tar.gz
 bf72191d01268ccbb79edf79d1157140e37b3271fac67bb77671f3d693108bd4 5940 
python-anndata_0.7.8-1.debian.tar.xz
 f542ddedde26bc906e042170e1163b0587098878a50fa623b03343df64b3486d 10070 
python-anndata_0.7.8-1_amd64.buildinfo
Files:
 3423677b9f01ff9000e9ce92e79373ce 2713 python optional 
python-anndata_0.7.8-1.dsc
 98d8a25434b64f2496a1a81e9e0543ed 137261 python optional 
python-anndata_0.7.8.orig.tar.gz
 fa68fe22bdab1aef6b07f9cd8e7d36a0 5940 python optional 
python-anndata_0.7.8-1.debian.tar.xz
 0067ae7ede0f50bf103049d99fc8e16b 10070 python optional 
python-anndata_0.7.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmGzWiURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFQeQ/7BgETt4Cd3mVckiqMFCflOaPqD/U3O32d
yadzQ4IT66rSA22g0zwPxYyUqPSbsRbF0GNRZDBx05tDEbSxcKqQ6nvTqQGJMnJw
B9M24LbI53KK2n0qr9XQ1m282vLod9L/VvTZ8DYioRweBBT0GL8FFv8FBQ7mVkHb
cXAP6X3JO8H4yLRUUsiwYYcrAhSGGjusz/nzZOsKSFdh9SEmwi1TQKVp95TWB5Ef
8G/v31LvVXQ4I/wVPjL/KEUOfDep0soqkRUX+95QeVIeryOD6NWPQee7uprw5KJN
DJbl7EJLQoA8etTtnUa2wHcn8VvFcIl8Ms1a6sBaJFBX4dyzGGNKy2T2sZjcZfMt
gxxZ+rGCZjKDBITR8TQyHFE+fDvEekxc1+fILpvAmrA8lQI+n+qeyRGd10MhShF9
B3rWA1eUeQ+Tqa695YNv02QeUtFRTRXB7L/blr/Fwx7W5IdHr+mK2sgzCan7ebTP
LeWdrykhYOzNn0NEXPWZlahvdK5Y/xySI/ZsO1M3DjhbTOSK0TRT659fPvLFfC1h
XAmRRNktosERDHJ1iXWXVQPHdxIHvwwnaPVQKdd2OlopUxlgKQGkHfKIp4mL988Z
tvF2hsPXJZlLV9aIS6xEsAhOjh/P2OGM4iLM5F8h3IbNQUwHLk/I4MXc0mlz+uoo
szgDQebcqBg=
=

Bug#1001311: marked as done (certmonger: FTBFS with openssl 3)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 15:23:02 +
with message-id 
and subject line Bug#1001311: fixed in certmonger 0.79.14+git20211010-3
has caused the Debian Bug report #1001311,
regarding certmonger: FTBFS with openssl 3
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.)


-- 
1001311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: certmonger
Version: 0.79.14+git20211010-2
Severity: serious
Tags: experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy

Hi Timo,

certmonger FTBFS against openssl 3 with an undefined symbol error:

[...]
gcc   -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-isystem /usr/include/mit-krb5   -I/usr/include/uuid -g -O2 
-ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -Wextra  -I/usr/include/libxml2 -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/x86_64-linux-gnu -g -O2 
-ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -Wextra -fPIC  -fPIC -pie -Wl,-z,relro,-z,now -o scep-submit 
scep_submit-scep.o scep_submit-submit-h.o scep_submit-util-m.o 
scep_submit-util-o.o scep_submit-submit-u.o scep_submit-util.o 
scep_submit-log.o scep_submit-pkcs7.o scep_submit-store-gen.o scep_submit-tm.o 
scep_submit-prefs.o scep_submit-prefs-o.o scep_submit-scep-o.o 
scep_submit-env-system.o -lcurl -lxml2 -lnss3 -lnssutil3 -lsmime3 -lssl3 
-lplds4 -lplc4 -lnspr4 -lcrypto -ltalloc  -luuid  -lpopt
../../src/submit-h.c: In function ‘cm_submit_h_run’:
../../src/submit-h.c:257:17: warning: call to 
‘_curl_easy_setopt_err_write_callback’ declared with attribute warning: 
curl_easy_setopt expects a curl_write_callback argument for this option 
[-Wattribute-warning]
  257 | curl_easy_setopt(ctx->curl, CURLOPT_WRITEFUNCTION,
  | ^
/usr/bin/ld: /tmp/ccPXkLF2.ltrans0.ltrans.o: in function `main':
./build/src/../../src/util-o.c:54: undefined reference to `OPENSSL_init_ssl'
collect2: error: ld returned 1 exit status
[...]

  
(https://launchpad.net/ubuntu/+source/certmonger/0.79.14+git20211010-2/+build/22293176)

openssl 3 is currently in experimental, and is expected to ship with the
next version of Debian.  It is also the version of openssl to be used for
the upcoming Ubuntu 22.04 LTS release.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: certmonger
Source-Version: 0.79.14+git20211010-3
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
certmonger, 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 certmonger 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: Fri, 10 Dec 2021 15:13:59 +0200
Source: certmonger
Built-For-Profiles: noudeb
Architecture: source
Version: 0.79.14+git20211010-3
Distribution: experimental
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 1001311
Changes:
 certmonger (0.79.14+git20211010-3) experimental; urgency=medium
 .
   * Fix build with OpenSSL 3.0. (Closes: #1001311)
Checksums-Sha1:
 b7a99cf2bf64ed2f36197e19b08ca3cb6656cd54 2333 
certmonger_0.79.14+git20211010-3.dsc
 09e1abf7dade3bd6772419c3ab319f04ca9f0cd1 10876 
certmonger_0.79.14+git20211010-3.debian.tar.xz
 84dcb984686c9a551d6efd6fab0fd084f1f83dcf 7819 
certmonger_0.79.14+git20211010-3_source.buildinfo
Checksums-Sha256:
 1f33feddf9e1bd478e051d8b37e5169dea09ed19a75d574d8eb481a0a8b6ac42 2333 
certmonger_0.79.14+git20211010-3.dsc
 8f05210bdd7393b12baaf931eb2b20f0e40

Bug#1000146: marked as done (cppcheck: incorrect dependencies: libc6 should be >= 2.32)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 17:18:30 +
with message-id 
and subject line Bug#1000146: fixed in cppcheck 2.6-2
has caused the Debian Bug report #1000146,
regarding cppcheck: incorrect dependencies: libc6 should be >= 2.32
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.)


-- 
1000146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cppcheck
Version: 2.6-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: colomar.6@gmail.com

Dear Maintainer,

I installed and run cppcheck on a system which I had not used for half a year.
For that reason, many of its packages were outdated.

glibc was on version 2.31.

When I run cppcheck, it failed with the following error:

cppcheck: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found 
(required by cppcheck)

I found the following dependencies' information:

$ apt-rdepends cppcheck | head -n2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
cppcheck
  Depends: libc6 (>= 2.29)


So it clearly is incorrect, AFAICS.
It should declare a dependency for libc6 2.32


Regards,
Alex


P.S.:
You'll find below that my installed libc6 is 2.32;
that's because I updated it to be able to use checkpatch,
prior to sending this bug report.
Please ignore that.


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cppcheck depends on:
ii  libc6 2.32-4
ii  libgcc-s1 11.2.0-10
ii  libpcre3  2:8.39-13
ii  libstdc++611.2.0-10
ii  libtinyxml2-9 9.0.0+dfsg-3
ii  libz3-4   4.8.12-1+b1
iu  python3   3.9.8-1
ii  python3-pygments  2.7.1+dfsg-2.1

cppcheck recommends no packages.

Versions of packages cppcheck suggests:
ii  clang 1:11.0-51+nmu5
ii  clang-tidy1:11.0-51+nmu5
pn  cppcheck-gui  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cppcheck
Source-Version: 2.6-2
Done: Joachim Reichel 

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

Debian distribution maintenance software
pp.
Joachim Reichel  (supplier of updated cppcheck package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 27 Nov 2021 12:00:41 +0100
Source: cppcheck
Architecture: source
Version: 2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Joachim Reichel 
Changed-By: Joachim Reichel 
Closes: 1000146
Changes:
 cppcheck (2.6-2) unstable; urgency=medium
 .
   * Rebuild against dpkg >= 1.21.0 (Closes: #1000146).
Checksums-Sha1:
 cdafef3c4ea27b6dfd126c77d235ad88fb416650 2131 cppcheck_2.6-2.dsc
 cb8cd07e40da5b8bb95fafd67ef2a3980ec2387b 11696 cppcheck_2.6-2.debian.tar.xz
 b116fddebe4511f12c469d1eea79c1063609afc8 12795 cppcheck_2.6-2_amd64.buildinfo
Checksums-Sha256:
 603a498af98533d63782baee98df5d6d949c6cfc619817ca3d537a15568e4557 2131 
cppcheck_2.6-2.dsc
 b09ada38f4638cc2ee32ab313dd6a6d9095bf9f7a6469b5719287de831672547 11696 
cppcheck_2.6-2.debian.tar.xz
 62ccb5f1584791df83ab9f239d247f316992f01beaf4fa0c1995afbdd2d2b941 12795 
cppcheck_2.6-2_amd64.buildinfo
Files:
 b781626ab9114c21b7ab06aac21c37c1 2131 devel optional cppcheck_2.6-2.dsc
 36020a6a3278890081fe7a72e7fd669b 11696 devel optional 
cppcheck_2.6-2.debian.tar.xz
 dd4552224c3ed2d61495cd9b2912d560 12795 devel optional 
cppcheck_2.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmGzh5YACgkQuPr/HEOI
Z3GEixAAgM2gcOe6kE7h0pWRrh2XFL9iWYdq3ozv60iIVWwh8K1mraEjlGvgwW8b
+6T0DLLgeDguy8vKtTQ7Z0V0JHVeP1Wyjro8oNmnGHKTa8rkgbNfn6inyR2dvyAW
ZR27k//wU9D0fLYU8W0S12hMNgb83mPyQ29M4oy90poRNoJniQTJzvtOg6+7Q2PL
PYtTit1fI4zHRKnlF1n/7eOrB+xmh/0ORNKweh+t

Bug#1000230: closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1000230: fixed in screenruler 0.960+bzr41+deb10-5)

[Peter Mueller]

On the other machine, libcanberra-gtk3-module IS installed, but screenruler 
still fals to start:
$ LANG=C sudo aptitude show screenruler | egrep "(State)|(Version)" Version: 
0.960+bzr41+deb10-4 State: installed $ LANG=C sudo aptitude show 
libcanberra-gtk3-module | egrep "(State)|(Version)" Version: 0.30-7 State: 
installed $ screenruler Loading libraries... Gtk-Message: 19:09:53.082: Failed 
to load module "canberra-gtk-module" /usr/bin/screenruler:61:in `block in 
': 'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'. 
/usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. Creating windows... Gtk-WARNING **: Unknown property: 
GtkWindow.has-resize-grip from 
/usr/share/screenruler/utils/glade_window.rb:29:in `initialize' from 
/usr/share/screenruler/ruler_window.rb:51:in `initialize' from 
/usr/bin/screenruler:76:in `new' from /usr/bin/screenruler:76:in `' 
Reading settings... Presenting ruler... Shutting down... $
So, the issue is unrelated to the libcanberra-gtk3-module or related to more 
than just that.
Does the screenruler version from unstable anyhow have this issue fixed or was 
only the (probably useless) dependency added?

Bug#1000230: screenruler still fails to start

[Peter Mueller]

reopen 1000230
found 1000230 0.960+bzr41+deb10-6
thanks
The updated screenruler still fails to start:
$ LANG=C sudo aptitude show screenruler | egrep "(State)|(Version)" Version: 
0.960+bzr41+deb10-6 State: installed $ LANG=C sudo aptitude show 
libcanberra-gtk3-module | egrep "(State)|(Version)" Version: 0.30-8 State: 
installed (0.30-7), upgrade available (0.30-8) $ screenruler Loading 
libraries... Gtk-Message: 19:15:32.635: Failed to load module 
"canberra-gtk-module" /usr/bin/screenruler:61:in `block in ': 
'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'. 
/usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead. Creating windows... Gtk-WARNING **: Unknown property: 
GtkWindow.has-resize-grip from 
/usr/share/screenruler/utils/glade_window.rb:29:in `initialize' from 
/usr/share/screenruler/ruler_window.rb:51:in `initialize' from 
/usr/bin/screenruler:76:in `new' from /usr/bin/screenruler:76:in `' 
Reading settings... Presenting ruler... Shutting down... $
Reopening the bug report. I'd be glad if I could ask that this bug finds 
attention.

Processed: screenruler still fails to start

[Debian Bug Tracking System]

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

> reopen 1000230
Bug #1000230 {Done: Georges Khaznadar } [screenruler] 
screenruler fails to start
'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 screenruler/0.960+bzr41+deb10-5.
> found 1000230 0.960+bzr41+deb10-6
Bug #1000230 [screenruler] screenruler fails to start
Marked as found in versions screenruler/0.960+bzr41+deb10-6.
> thanks
Stopping processing here.

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

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

[Nilesh Patra]

control: notfound -1 r-cran-satellite/1.0.4-1
control: fixed -1 r-cran-raster/3.5-9-1

The new release fixes things for me locally, I will check debci
and close the bug when debci runs the tests.

Please hold on until then.

Regards,
Nilesh


signature.asc
Description: PGP signature

Processed: Re: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 r-cran-satellite/1.0.4-1
Bug #1000339 [src:r-cran-raster, src:r-cran-satellite] r-cran-raster breaks 
r-cran-satellite autopkgtest: unable to find an inherited method for function 
'extend'
No longer marked as found in versions r-cran-satellite/1.0.4-1.
> fixed -1 r-cran-raster/3.5-9-1
Bug #1000339 [src:r-cran-raster, src:r-cran-satellite] r-cran-raster breaks 
r-cran-satellite autopkgtest: unable to find an inherited method for function 
'extend'
The source r-cran-raster and version 3.5-9-1 do not appear to match any binary 
packages
Marked as fixed in versions r-cran-raster/3.5-9-1.

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

Bug#1000960: Wrong permissions after fresh install

[Jörg Frings-Fürst]

Hello Marc,


this bug only occurs with the image from a German hoster. When
installing from an original image, everything is fine. 

I therefore close this bug.

Many thanks for your work.

CU
Jörg



Am Mittwoch, dem 01.12.2021 um 16:01 +0100 schrieb Marc Haber:
> On Wed, Dec 01, 2021 at 01:36:52PM +, Jörg Frings-Fürst wrote:
> > /etc/exim4/passwd.client
> > 2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if
> > exists{/etc/exim4/passwd.client}
> > {${lookup{$host}nwildlsearch{/etc/exim4/passwd.client}{$host_addres
> > s}}}{} }" while checking a list: failed to open
> > /etc/exim4/passwd.client for linear search: Permission denied
> > (euid=107 egid=111)
> 
> What are uid 107 and gid 111 on the affected system? Are there
> dpkg-statoverrides present in the system?
> 
> The maintainer scripts do only chown to Debian-exim, in the
> alphabetic
> representation.
> 
> > The same error on /var/log/exim4/mainlog.
> 
> The log gets created by exim proper. This having the wrong user/group
> means something "deeper".
> 
> Greetings
> Marc
> 

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D


Jörg Frings-Fürst
D-54470 Lieser

git:  https://jff.email/cgit/


Threema: SYR8SJXB
Skype: joergpenguin
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#1000960: marked as done (Wrong permissions after fresh install)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 19:47:57 +0100
with message-id 
and subject line Re: Bug#1000960: Wrong permissions after fresh install
has caused the Debian Bug report #1000960,
regarding Wrong permissions after fresh install
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.)


-- 
1000960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-daemon-light
Version: 4.94.2-7
Severity: grave
File: /usr/sbin/exim4

Hello,

on a fresh install exim4 files has wrong permissions:

/etc/exim4/passwd.client
2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if 
exists{/etc/exim4/passwd.client} 
{${lookup{$host}nwildlsearch{/etc/exim4/passwd.client}{$host_address}}}{} }" 
while checking a list: failed to open /etc/exim4/passwd.client for linear 
search: Permission denied (euid=107 egid=111)


The same error on /var/log/exim4/mainlog.


CU
Jörg

-- Package-specific info:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event I18N OCSP PIPE_CONNECT PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='satellite'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost='snct7'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='xxx'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:snct7
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /run/exim4/exim.pid
SMTPLISTENEROPTIONS=''

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/32 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages exim4-daemon-light depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  exim4-base 4.94.2-7
ii  libc6  2.31-13+deb11u2
ii  libcrypt1  1:4.4.18-4
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libgnutls-da

Bug#1001345: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1001345: fixed in jupyterlab-pygments 0.1.2-8)

[Paul Gevers]

Hi,

On 10-12-2021 10:09, Debian Bug Tracking System wrote:

  jupyterlab-pygments (0.1.2-8) unstable; urgency=medium
  .
* Detect if the Python version is installed before running
it. (Closes: #1001345)


To be fair I didn't mention it, but I would have expected instead that 
you would add python3-all to the test dependencies instead of what I 
read here.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001209: dnsmasq: Regression: Fails to direct queries to 127.0.1.1#10053

[Sven Mueller]

Hi

judging from the Dnsmasq list, the problem is that --local is supposed to
be an alias for --server, but the recent rewrite of the address logic
apparently made it an alias of --adress instead.

If I use --server instead of--local, everything works as expected. (At
least as far as I can tell.)

I can't say if the other version was also affected as we never tried that
one and I won't have a chance to check for a while.

Basically, AFAICT, this boils down to:
Make --local a proper alias for --server again.
The alternative would be to update the documentation, but since this is a
breaking change for existing installations, I don't think that would be
appropriate.

Cheers,
Sven


Michael Biebl  schrieb am Do., 9. Dez. 2021, 19:45:

> On Mon, 6 Dec 2021 14:20:51 +0100 Sven Mueller 
> wrote:
> > Package: dnsmasq
> > Version: 2.86-1.1
> > Severity: Serious
> >
> > We have this our /etc/NetworkManager/dnsmasq.d/local-proxy:
> >
> > local=/in.ourdoma.in/127.0.1.1#10053
> >
> > This leads to:
> >
> > dnsmasq: Bad address in --address at line 2 of
> > /etc/NetworkManager/dnsmasq.d/goobuntu-dnsproxy
> >
> > The syntax used is exactly as documented in `man dnsmasq`:
> > /domain/server#port
> >
> > Once I remove the port (#10053), the configuration "works" (except that
> it
> > of course doesn't find the server to resolve the relevant requests).
>
> Is that regression specific to 2.86-1.1 i.e. is my backport of the fix for
> [1] incomplete/broken or did you experience the problem with 2.86-1 as
> well?
>
> Looking at the upstream git repo and its log, there might be other fixes
> which need to be cherry-picked or we simply wait until Simon makes a 2.87
> release :-)
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
> [2] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git
>

Bug#995769: dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1)

[Tong Sun]

On Wed, Dec 8, 2021 at 11:49 PM Tong Sun wrote:
>
> On Sun, Nov 28, 2021 at 1:51 PM Boyuan Yang wrote:
>
> > Getting package autoremoved from testing is not end-of-the-world
>
> It might not be the end-of-the-world for you, but apparently it is for
> me already, even before the deadline.

Oh, sorry, my package was turn to NEW for another reason. I'll try to
find a sponsor for it myself.

> > -- once the
> > bug is fixed, it can get back to Debian Testing at any time. Meanwhile, the
> > previous bug is real and will need to be fixed sooner or later.
>
> I fixed the 1.5.7-1 problem in 1.5.7-2, but when I'm uploading the fix
> of 1.5.7-2, I got:
>
> --
> ACL dm: NEW uploads are not allowed
>
> binary:dbab is NEW.
> source:dbab is NEW.
> --
>
> The Debian FTP Masters explains that it means "DMs may not upload
> packages going to NEW. Need to use a sponsor for those".
>
> My package is already marked for autoremoval from testing
> -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769
>
> there isn't much time left for me but I have to go through a sponsor
> now, even that I've got everything ready.
>
> Can you help sponsor me please?
>
> > I may get back to look into the bug later, bug I don't have enough time
> > recently. Feel free to find help from others, or I may get involved when I
> > have enough time.
> >
> > Thanks,
> > Boyuan Yang
> >
> >
> > 在 2021-11-28星期日的 11:35 -0500，Tong Sun写道：
> > > Hi Boyuan, please please help.
> > >
> > > -- Forwarded message -
> > > From: Tong Sun 
> > > Date: Sun, Nov 28, 2021 at 11:33 AM
> > > Subject: Re: Bug#995769: dbab: v1.5.7 package fail to upgrade from
> > > bullseye (1.5.01-1)
> > > To: Boyuan Yang , <995...@bugs.debian.org>
> > >
> > >
> > > To Boyuan, or any mentors reading this issue.
> > >
> > > I've been trying to fix it myself, but all my previous attempts
> > > failed, because I don't understand what breaks and why, from the
> > > output of the package upgrade log.
> > >
> > > I've sent a help request to debian-mentors a few days ago, but nobody
> > > answers yet.
> > >
> > > My package is now marked for autoremoval from testing, with a wrong
> > > reason, and I don't know how to stop my package being autoremed from
> > > testing, and I got no answers/help on that either.
> > >
> > > Since I don't know how to fix it myself, and all my previous attempts
> > > failed, if nobody helps me by next weekend, I'll do the only thing
> > > that I know -- to change the severity of this bug to minor, because
> > > there is a simple solution to it as explained below. This will solve
> > > everything and win me the time it takes for me to do further
> > > investigation/testing.
> > >
> > > Really hope it won't be the case.
> > > Somebody help please.
> > > Thanks
> > >
> > > On Thu, Oct 7, 2021 at 9:31 PM Tong Sun wrote:
> > > >
> > > > On Tue, Oct 5, 2021 at 7:27 AM Boyuan Yang  wrote:
> > > >
> > > > > Package dbab/1.5.7-1 has broken maintscript and cannot be properly
> > > > > upgraded
> > > > > from dbab/1.5.01-1 to dbab/1.5.7-1:
> > > >
> > > > Thanks for reporting. I'll try to fix it ASAP.
> > > >
> > > > In the meantime, for anyone who doesn't want to wait for the fix to be
> > > > published --
> > > > do not do an upgrade -- remove the package completely, then do a fresh
> > > > install.
> > > >
> > > > thx
> >

Processed: Re: circuits: needs update for python3.10: 'Callable' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001244 [src:circuits] circuits: needs update for python3.10: 'Callable' 
from 'collections' is removed
Added tag(s) patch.

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

Bug#1001244: circuits: needs update for python3.10: 'Callable' from 'collections' is removed

[Steve Langasek]

Package: circuits
Version: 3.1.0+ds1-2
Followup-For: Bug #1001244
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru circuits-3.1.0+ds1/debian/patches/python-3.10.patch 
circuits-3.1.0+ds1/debian/patches/python-3.10.patch
--- circuits-3.1.0+ds1/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ circuits-3.1.0+ds1/debian/patches/python-3.10.patch 2021-12-10 
12:02:12.0 -0800
@@ -0,0 +1,18 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: circuits-3.1.0+ds1/circuits/core/handlers.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/core/handlers.py
 circuits-3.1.0+ds1/circuits/core/handlers.py
+@@ -7,7 +7,7 @@
+ """
+ 
+ from inspect import getargspec
+-from collections import Callable
++from collections.abc import Callable
+ 
+ 
+ def handler(*names, **kwargs):
diff -Nru circuits-3.1.0+ds1/debian/patches/series 
circuits-3.1.0+ds1/debian/patches/series
--- circuits-3.1.0+ds1/debian/patches/series2019-08-05 00:03:56.0 
-0700
+++ circuits-3.1.0+ds1/debian/patches/series2021-12-10 12:01:30.0 
-0800
@@ -3,3 +3,4 @@
 03_disable-address-check.patch
 04_remove-google-adsense.patch
 05_remove-privacy-breach-badges.patch
+python-3.10.patch

Processed: apache-log4j2: CVE-2021-44228:: Remote code injection via crafted log messages

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.11.1-2
Bug #1001478 [src:apache-log4j2] apache-log4j2: CVE-2021-44228:: Remote code 
injection via crafted log messages
Marked as found in versions apache-log4j2/2.11.1-2.
> found -1 2.7-2
Bug #1001478 [src:apache-log4j2] apache-log4j2: CVE-2021-44228:: Remote code 
injection via crafted log messages
Marked as found in versions apache-log4j2/2.7-2.

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

Bug#1001478: apache-log4j2: CVE-2021-44228:: Remote code injection via crafted log messages

[Salvatore Bonaccorso]

Source: apache-log4j2
Version: 2.13.3-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3198 
https://github.com/apache/logging-log4j2/pull/608
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.11.1-2
Control: found -1 2.7-2

Hi,

The following vulnerability was published for apache-log4j2.

I'm still choosing grave for the severity, though there are some
mitigating factors depending on the Java version used. See for details
the references, in particular [3].

Additionally according to latest comments in [4] the issue seems not
to be completely fixed. As the lookup is performed after formatting
the message, which includes the user input, the vulnerability could
still be triggered using a ParametrizedMessage. See [4] the comments
from Eric Everman and Volkan Yazici.

CVE-2021-44228[0]:
| Apache Log4j2 <=2.14.1 JNDI features used in configuration, log
| messages, and parameters do not protect against attacker controlled
| LDAP and other JNDI related endpoints. An attacker who can control log
| messages or log message parameters can execute arbitrary code loaded
| from LDAP servers when message lookup substitution is enabled. From
| log4j 2.15.0, this behavior has been disabled by default. In previous
| releases (>2.10) this behavior can be mitigated by setting system
| property "log4j2.formatMsgNoLookups" to “true” or
| by removing the JndiLookup class from the classpath (example: zip -q
| -d log4j-core-*.jar
| org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121
| (see
| https://www.oracle.com/java/technologies/javase/8u121-relnotes.html)
| protects against remote code execution by defaulting
| "com.sun.jndi.rmi.object.trustURLCodebase" and
| "com.sun.jndi.cosnaming.object.trustURLCodebase" to "false".


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-44228
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
[1] https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
[2] https://github.com/apache/logging-log4j2/pull/608
[3] https://www.lunasec.io/docs/blog/log4j-zero-day/
[4] https://issues.apache.org/jira/browse/LOG4J2-3198

Regards,
Salvatore

Processed: Re: colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001289 [src:colorclass] colorclass: needs update for python3.10: 
'Mapping' from 'collections' is removed
Added tag(s) patch.

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

Bug#1001289: colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed

[Steve Langasek]

Package: colorclass
Followup-For: Bug #1001289
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru colorclass-2.2.0/debian/patches/python-3.10.patch 
colorclass-2.2.0/debian/patches/python-3.10.patch
--- colorclass-2.2.0/debian/patches/python-3.10.patch   1969-12-31 
16:00:00.0 -0800
+++ colorclass-2.2.0/debian/patches/python-3.10.patch   2021-12-10 
12:09:15.0 -0800
@@ -0,0 +1,19 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001289
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: colorclass-2.2.0/colorclass/codes.py
+===
+--- colorclass-2.2.0.orig/colorclass/codes.py
 colorclass-2.2.0/colorclass/codes.py
+@@ -1,7 +1,7 @@
+ """Handles mapping between color names and ANSI codes and determining auto 
color codes."""
+ 
+ import sys
+-from collections import Mapping
++from collections.abc import Mapping
+ 
+ BASE_CODES = {
+ '/all': 0, 'b': 1, 'f': 2, 'i': 3, 'u': 4, 'flash': 5, 'outline': 6, 
'negative': 7, 'invis': 8, 'strike': 9,
diff -Nru colorclass-2.2.0/debian/patches/series 
colorclass-2.2.0/debian/patches/series
--- colorclass-2.2.0/debian/patches/series  1969-12-31 16:00:00.0 
-0800
+++ colorclass-2.2.0/debian/patches/series  2021-12-10 12:08:28.0 
-0800
@@ -0,0 +1 @@
+python-3.10.patch

Processed: Re: convertdate: autopkgtest tests for all supported python3s but fails to install them

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001290 [src:convertdate] convertdate: autopkgtest tests for all supported 
python3s but fails to install them
Added tag(s) patch.

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

Bug#995769: Fwd: dbab_1.5.7-2_source.changes REJECTED

[Tong Sun]

Hi Andrey,

I fixed the 1.5.7-1 problem in 1.5.7-2 and changed to contrib now as
well, however,

As per Joerg, my dbab package is now considered NEW because it is
moved to contrib now, thus it needs a sponsor.

Would you be able to help, uploading my dbab 1.5.7-2 please? All my
other sponsor requests for dbab 1.5.7-2 have failed so far.

thanks

-- Forwarded message -
From: Joerg Jaspert 
Date: Wed, Dec 8, 2021 at 3:20 PM
Subject: Re: dbab_1.5.7-2_source.changes REJECTED
To: Tong Sun , Debian FTP Masters



On 16340 March 1977, Tong Sun wrote:

>> ACL dm: NEW uploads are not allowed
>> binary:dbab is NEW.
>> source:dbab is NEW.
>> ===
>>
>> Please feel free to respond to this email if you don't understand why
>> your files were rejected, or if you upload new files which address
>> our
>> concerns.
> Indeed, I don't understand why my files were rejected.

As it says, DMs may not upload packages going to NEW. Need to use a
sponsor for those.

--
bye, Joerg

Bug#1001290: convertdate: autopkgtest tests for all supported python3s but fails to install them

[Steve Langasek]

Package: convertdate
Version: 2.3.2-1
Followup-For: Bug #1001290
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru convertdate-2.3.2/debian/tests/control 
convertdate-2.3.2/debian/tests/control
--- convertdate-2.3.2/debian/tests/control  2021-03-15 10:32:20.0 
-0700
+++ convertdate-2.3.2/debian/tests/control  2021-12-10 12:11:49.0 
-0800
@@ -1,3 +1,3 @@
 Tests: python3-unittest
 Restrictions: allow-stderr
-Depends: @
+Depends: @, python3-all

Processed: Re: deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001292 [src:deepdiff] deepdiff: needs update for python3.10: 'Mapping' 
from 'collections' is removed
Added tag(s) patch.

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

Processed: retitle 1001478 to apache-log4j2: CVE-2021-44228: Remote code injection via crafted log messages

[Debian Bug Tracking System]

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

> retitle 1001478 apache-log4j2: CVE-2021-44228: Remote code injection via 
> crafted log messages
Bug #1001478 [src:apache-log4j2] apache-log4j2: CVE-2021-44228:: Remote code 
injection via crafted log messages
Changed Bug title to 'apache-log4j2: CVE-2021-44228: Remote code injection via 
crafted log messages' from 'apache-log4j2: CVE-2021-44228:: Remote code 
injection via crafted log messages'.
> thanks
Stopping processing here.

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

Bug#1001292: deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed

[Steve Langasek]

Package: deepdiff
Version: 3.3.0-2
Followup-For: Bug #1001292
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru deepdiff-3.3.0/debian/patches/python-3.10.patch 
deepdiff-3.3.0/debian/patches/python-3.10.patch
--- deepdiff-3.3.0/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ deepdiff-3.3.0/debian/patches/python-3.10.patch 2021-12-10 
12:15:00.0 -0800
@@ -0,0 +1,51 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001292
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: deepdiff-3.3.0/deepdiff/diff.py
+===
+--- deepdiff-3.3.0.orig/deepdiff/diff.py
 deepdiff-3.3.0/deepdiff/diff.py
+@@ -16,8 +16,8 @@
+ 
+ from decimal import Decimal
+ 
+-from collections import Mapping
+-from collections import Iterable
++from collections.abc import Mapping
++from collections.abc import Iterable
+ 
+ from deepdiff.helper import py3, strings, bytes_type, numbers, 
ListItemRemovedOrAdded, notpresent, IndexedHash, Verbose
+ from deepdiff.model import RemapDict, ResultDict, TextResult, TreeResult, 
DiffLevel
+Index: deepdiff-3.3.0/deepdiff/contenthash.py
+===
+--- deepdiff-3.3.0.orig/deepdiff/contenthash.py
 deepdiff-3.3.0/deepdiff/contenthash.py
+@@ -3,8 +3,8 @@
+ from __future__ import absolute_import
+ from __future__ import print_function
+ import sys
+-from collections import Iterable
+-from collections import MutableMapping
++from collections.abc import Iterable
++from collections.abc import MutableMapping
+ from collections import defaultdict
+ from decimal import Decimal
+ from hashlib import sha1
+Index: deepdiff-3.3.0/deepdiff/search.py
+===
+--- deepdiff-3.3.0.orig/deepdiff/search.py
 deepdiff-3.3.0/deepdiff/search.py
+@@ -6,8 +6,8 @@
+ from __future__ import absolute_import
+ from __future__ import print_function
+ import sys
+-from collections import Iterable
+-from collections import MutableMapping
++from collections.abc import Iterable
++from collections.abc import MutableMapping
+ import logging
+ 
+ from deepdiff.helper import py3, strings, numbers, items
diff -Nru deepdiff-3.3.0/debian/patches/series 
deepdiff-3.3.0/debian/patches/series
--- deepdiff-3.3.0/debian/patches/series1969-12-31 16:00:00.0 
-0800
+++ deepdiff-3.3.0/debian/patches/series2021-12-10 12:14:03.0 
-0800
@@ -0,0 +1 @@
+python-3.10.patch

Processed: Re: dominate: needs update for python3.10: 'Callable' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001295 [src:dominate] dominate: needs update for python3.10: 'Callable' 
from 'collections' is removed
Added tag(s) patch.

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

Bug#1001295: dominate: needs update for python3.10: 'Callable' from 'collections' is removed

[Steve Langasek]

Package: dominate
Version: 2.3.1-2
Followup-For: Bug #1001295
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dominate-2.3.1/debian/patches/python-3.10.patch 
dominate-2.3.1/debian/patches/python-3.10.patch
--- dominate-2.3.1/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ dominate-2.3.1/debian/patches/python-3.10.patch 2021-12-10 
12:19:46.0 -0800
@@ -0,0 +1,20 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001295
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: dominate-2.3.1/dominate/dom_tag.py
+===
+--- dominate-2.3.1.orig/dominate/dom_tag.py
 dominate-2.3.1/dominate/dom_tag.py
+@@ -20,7 +20,8 @@
+ 
+ import copy
+ import numbers
+-from collections import defaultdict, namedtuple, Callable
++from collections import defaultdict, namedtuple
++from collections.abc import Callable
+ from functools import wraps
+ import threading
+ 
diff -Nru dominate-2.3.1/debian/patches/series 
dominate-2.3.1/debian/patches/series
--- dominate-2.3.1/debian/patches/series1969-12-31 16:00:00.0 
-0800
+++ dominate-2.3.1/debian/patches/series2021-12-10 12:18:37.0 
-0800
@@ -0,0 +1 @@
+python-3.10.patch

Bug#1001479: python-transitions: (autopkgtest) needs update for python3.10: There is no current event loop

[Paul Gevers]

Source: python-transitions
Version: 0.8.9-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-transitions fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-transitions from testing0.8.9-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-transitions/17446726/log.gz

=== FAILURES 
===
 TestAsync.test_multiple_models 



self = 

def test_multiple_models(self):
loop = asyncio.new_event_loop()
asyncio.set_event_loop(loop)
m1 = self.machine_cls(states=['A', 'B', 'C'], initial='A', 
name="m1")

m2 = self.machine_cls(states=['A'], initial='A', name='m2')
m1.add_transition(trigger='go', source='A', dest='B', 
before=self.cancel_soon)
m1.add_transition(trigger='fix', source='A', dest='C', 
after=self.cancel_soon)
m1.add_transition(trigger='check', source='C', dest='B', 
conditions=self.await_false)

m1.add_transition(trigger='reset', source='C', dest='A')
m2.add_transition(trigger='go', source='A', dest=None, 
conditions=m1.is_C, after=m1.reset)
>   loop.run_until_complete(asyncio.gather(m1.go(),  # should 
block before B


self.call_delayed(m1.fix, 0.05),  # should cancel task and go to C

self.call_delayed(m1.check, 0.07),  # should exit before m1.fix
   self.call_delayed(m2.go, 
0.1)))  # should cancel m1.fix


tests/test_async.py:144: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.10/asyncio/tasks.py:776: in gather

fut = _ensure_future(arg, loop=loop)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

coro_or_future = 

def _ensure_future(coro_or_future, *, loop=None):
if futures.isfuture(coro_or_future):
if loop is not None and loop is not 
futures._get_loop(coro_or_future):
raise ValueError('The future belongs to a different 
loop than '

'the one specified as the loop argument')
return coro_or_future
if not coroutines.iscoroutine(coro_or_future):
if inspect.isawaitable(coro_or_future):
coro_or_future = _wrap_awaitable(coro_or_future)
else:
raise TypeError('An asyncio.Future, a coroutine or an 
awaitable '

'is required')
if loop is None:

  loop = events._get_event_loop(stacklevel=4)

E   DeprecationWarning: There is no current event loop

/usr/lib/python3.10/asyncio/tasks.py:633: DeprecationWarning
=== short test summary info 

FAILED tests/test_async.py::TestAsync::test_multiple_models - 
DeprecationWarn...
!! stopping after 1 failures 
!!!
= 1 failed, 37 passed in 2.74s 
=

sys:1: RuntimeWarning: coroutine 'AsyncEvent.trigger' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
sys:1: RuntimeWarning: coroutine 'TestAsync.call_delayed' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
autopkgtest [14:16:05]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-transitions: (autopkgtest) needs update for python3.10: There is no current event loop

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001479 [src:python-transitions] python-transitions: (autopkgtest) needs 
update for python3.10: There is no current event loop
Added indication that 1001479 affects src:python3-defaults

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

Bug#1001480: python-validictory: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' is removed

[Paul Gevers]

Source: python-validictory
Version: 1.1.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-validictory fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-validictory from testing1.1.2-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-validictory/17446730/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/validictory/__init__.py", line 
3, in 
from validictory.validator import (SchemaValidator, 
FieldValidationError, MultipleValidationError,
  File "/usr/lib/python3/dist-packages/validictory/validator.py", line 
7, in 

from collections import Mapping, Container
ImportError: cannot import name 'Mapping' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

autopkgtest [14:16:13]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-validictory: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001480 [src:python-validictory] python-validictory: (autopkgtest) needs 
update for python3.10: 'Mapping' from 'collections' is removed
Added indication that 1001480 affects src:python3-defaults

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

Bug#995769: Fwd: dbab_1.5.7-2_source.changes REJECTED

[Nilesh Patra]

Hi Tong,

On Fri, 10 Dec 2021 15:12:20 -0500 Tong Sun  
wrote:
> The Debian FTP Masters explains that it means "DMs may not upload
> packages going to NEW. Need to use a sponsor for those".

If your changes are updated in salsa, I could help you with sponsoring.
Let me know if you'd like some help here. Please update salsa accordingly.

Regards,
Nilesh


signature.asc
Description: PGP signature

Processed: pythonmagick: (autopkgtest) needs update for python3.10: _PythonMagick.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZTIN5boost6python15instance_holderE

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001481 [src:pythonmagick] pythonmagick: (autopkgtest) needs update for 
python3.10: _PythonMagick.cpython-310-x86_64-linux-gnu.so: undefined symbol: 
_ZTIN5boost6python15instance_holderE
Added indication that 1001481 affects src:python3-defaults

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

Bug#1001481: pythonmagick: (autopkgtest) needs update for python3.10: _PythonMagick.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZTIN5boost6python15instance_holderE

[Paul Gevers]

Source: pythonmagick
Version: 0.9.19-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of pythonmagick fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
pythonmagick   from testing0.9.19-6
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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pythonmagick/17446732/log.gz

+ py3versions -r
+ cd /tmp/autopkgtest-lxc.0zub4xrx/downtmp/autopkgtest_tmp
Testing with python3.10:
+ echo Testing with python3.10:
+ python3.10
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/PythonMagick/__init__.py", line 
1, in 

from . import _PythonMagick
ImportError: 
/usr/lib/python3/dist-packages/PythonMagick/_PythonMagick.cpython-310-x86_64-linux-gnu.so: 
undefined symbol: _ZTIN5boost6python15instance_holderE

autopkgtest [14:16:57]: test python3



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001482: restrictedpython: (autopkgtest) needs update for python3.10: deprecation warning on stderr

[Paul Gevers]

Source: restrictedpython
Version: 4.0~b3-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of restrictedpython fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
restrictedpython   from testing4.0~b3-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. As mentioned 
in bug #909487 this test doesn't seem to be doing anything, and it can 
nevertheless fail. It's because there's a deprecation warning on stderr 
and autopkgtest fails on that by default. Unless a real test is added, I 
suggest to remove the autopkgtest.


Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/r/restrictedpython/17446736/log.gz

:1: DeprecationWarning: The distutils package is deprecated and 
slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
:1: DeprecationWarning: The distutils.sysconfig module is 
deprecated, use sysconfig instead
Running tests for python3.10: /usr/bin/zope-testrunner3 -k --test-path 
/usr/lib/python3/dist-packages -s RestrictedPython

Total: 0 tests, 0 failures, 0 errors and 0 skipped in 0.000 seconds.
Running tests for python3.9: /usr/bin/zope-testrunner3 -k --test-path 
/usr/lib/python3/dist-packages -s RestrictedPython

Total: 0 tests, 0 failures, 0 errors and 0 skipped in 0.000 seconds.
autopkgtest [14:17:09]: test all



OpenPGP_signature
Description: OpenPGP digital signature

Processed: restrictedpython: (autopkgtest) needs update for python3.10: deprecation warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001482 [src:restrictedpython] restrictedpython: (autopkgtest) needs 
update for python3.10: deprecation warning on stderr
Added indication that 1001482 affects src:python3-defaults

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

Processed: scoop: (autopkgtest) needs update for python3.10: 'Iterable' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001483 [src:scoop] scoop: (autopkgtest) needs update for python3.10: 
'Iterable' from 'collections' is removed
Added indication that 1001483 affects src:python3-defaults

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

Bug#1001483: scoop: (autopkgtest) needs update for python3.10: 'Iterable' from 'collections' is removed

[Paul Gevers]

Source: scoop
Version: 0.7.1.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of scoop fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
scoop  from testing0.7.1.1-7
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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/s/scoop/17446737/log.gz

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py", 
line 34, in 

from scoop import futures, _control, utils, shared
  File "/usr/lib/python3/dist-packages/scoop/futures.py", line 19, in 


from collections import namedtuple, Iterable
ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
/usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: 
Using or importing the ABCs from 'collections' instead of from 
'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
stop working

  from collections import namedtuple, Iterable
/usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: 
Using or importing the ABCs from 'collections' instead of from 
'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
stop working

  from collections import namedtuple, Iterable
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
./usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: 
Using or importing the ABCs from 'collections' instead of from 
'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
stop working

  from collections import namedtuple, Iterable
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: 
unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: 
Using or importing the ABCs from 'collections' instead of from 
'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
stop working

  from collections import namedtuple, Iterable
../tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: 
ResourceWarning: unclosed socket 

  scoop._control.execQueue = FutureQueue()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: 
Using or importing the ABCs from 'collections' instead of from 
'collections.abc' is deprecated s

Bug#1001484: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed

[Paul Gevers]

Source: sfepy
Version: 2020.4-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of sfepy fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
sfepy  from testing2020.4-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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sfepy/17446739/log.gz

run: python3.10
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.r9o8n8_b/downtmp/autopkgtest_tmp/laplace_shifted_periodic.py", 
line 140, in 

sfepy: dimensions: [1. 1.]
sfepy: centre: [0. 0.]
sfepy: shape:  [11 11]
sfepy: generating 121 vertices...
sfepy: ...done
sfepy: generating 100 cells...
sfepy: ...done
sfepy: updating variables...
sfepy: ...done
sfepy: setting up dof connectivities...
sfepy: ...done in 0.00 s
sfepy: lcbc: sper
sfepy: dofs: total 99, free 90, constrained 9, new 0
sfepy:  -> active 90
sfepy: matrix shape: (99, 99)
sfepy: assembling matrix graph...
sfepy: ...done in 0.00 s
sfepy: matrix structural nonzeros: 775 (7.91e-02% fill)
main()
  File 
"/tmp/autopkgtest-lxc.r9o8n8_b/downtmp/autopkgtest_tmp/laplace_shifted_periodic.py", 
line 125, in main

pb, state = run(fe_domain, 1)
  File 
"/tmp/autopkgtest-lxc.r9o8n8_b/downtmp/autopkgtest_tmp/laplace_shifted_periodic.py", 
line 82, in run

state = pb.solve()
  File "/usr/lib/python3/dist-packages/sfepy/discrete/problem.py", line 
1425, in solve

init_fun, prestep_fun, poststep_fun = self.get_tss_functions(
  File "/usr/lib/python3/dist-packages/sfepy/discrete/problem.py", line 
1234, in get_tss_functions

is_save = make_is_save(self.conf.options)
  File "/usr/lib/python3/dist-packages/sfepy/discrete/problem.py", line 
73, in make_is_save

is_save = IsSave(save_times)
  File "/usr/lib/python3/dist-packages/sfepy/discrete/problem.py", line 
42, in __init__

if is_sequence(save_times):
  File "/usr/lib/python3/dist-packages/sfepy/base/base.py", line 1049, 
in is_sequence

from collections import Sequence
ImportError: cannot import name 'Sequence' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

autopkgtest [14:19:44]: test build1



OpenPGP_signature
Description: OpenPGP digital signature

Processed: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001484 [src:sfepy] sfepy: (autopkgtest) needs update for python3.10: 
Sequence' from 'collections' is removed
Added indication that 1001484 affects src:python3-defaults

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

Bug#1001485: shellingham: autopkgtest tests all supported python3 versions but doesn't ensure they are installed

[Paul Gevers]

Source: shellingham
Version: 1.3.2-1.1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of shellingham fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
shellinghamfrom testing1.3.2-1.1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test tries to test for all supported Python3 versions, but fails to 
ensure all those versions are actually installed during the test. E.g. a 
test dependency on python3-all (or one of its siblings).


Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/s/shellingham/17446740/log.gz

+ cp -r tests /tmp/autopkgtest-lxc.7gre_wie/downtmp/autopkgtest_tmp
+ cd /tmp/autopkgtest-lxc.7gre_wie/downtmp/autopkgtest_tmp
+ py3versions -s
+ python3.10 -m pytest -v
/tmp/autopkgtest-lxc.7gre_wie/downtmp/build.zm9/src/debian/tests/testsuite: 
9: python3.10: not found

autopkgtest [14:17:35]: test testsuite



OpenPGP_signature
Description: OpenPGP digital signature

Processed: shellingham: autopkgtest tests all supported python3 versions but doesn't ensure they are installed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001485 [src:shellingham] shellingham: autopkgtest tests all supported 
python3 versions but doesn't ensure they are installed
Added indication that 1001485 affects src:python3-defaults

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

Bug#1001486: sortedcollections: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'MutableSet'

[Paul Gevers]

Source: sortedcollections
Version: 1.0.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of sortedcollections fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
sortedcollections  from testing1.0.1-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sortedcollections/17446742/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sortedcollections/__init__.py", 
line 14, in 

from .recipes import IndexableDict, IndexableSet
  File "/usr/lib/python3/dist-packages/sortedcollections/recipes.py", 
line 174, in 

class OrderedSet(co.MutableSet, co.Sequence):
AttributeError: module 'collections' has no attribute 'MutableSet'
autopkgtest [14:17:50]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Processed: sortedcollections: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'MutableSet'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001486 [src:sortedcollections] sortedcollections: (autopkgtest) needs 
update for python3.10: 'collections' has no attribute 'MutableSet'
Added indication that 1001486 affects src:python3-defaults

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

Bug#1001487: sphinx-argparse: (autopkgtest) needs update for python3.10: output changed

[Paul Gevers]

Source: sphinx-argparse
Version: 0.2.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of sphinx-argparse fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
sphinx-argparsefrom testing0.2.5-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sphinx-argparse/17446743/log.gz

[*] testing python3.10:
= test session starts 
==
platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 
-- /usr/bin/python3.10

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.xannnapd/downtmp/autopkgtest_tmp
collecting ... collected 16 items

test/test_parser.py::test_parse_options PASSED 
 [  6%]
test/test_parser.py::test_parse_default PASSED 
 [ 12%]
test/test_parser.py::test_parse_arg_choices PASSED 
 [ 18%]
test/test_parser.py::test_parse_opt_choices PASSED 
 [ 25%]
test/test_parser.py::test_parse_default_skip_default PASSED 
 [ 31%]
test/test_parser.py::test_parse_positional PASSED 
 [ 37%]
test/test_parser.py::test_parse_description PASSED 
 [ 43%]
test/test_parser.py::test_parse_nested FAILED 
 [ 50%]


=== FAILURES 
===
__ test_parse_nested 
___


def test_parse_nested():
parser = argparse.ArgumentParser(prog='test_parse_nested')
parser.add_argument('foo', default=False, help='foo help')
parser.add_argument('bar', default=False)
subparsers = parser.add_subparsers()
subparser = subparsers.add_parser('install', help='install 
help')

subparser.add_argument('ref', type=str, help='foo1 help')
subparser.add_argument('--upgrade', action='store_true', 
default=False, help='foo2 help')

data = parse_parser(parser)
assert data['action_groups'][0]['options'] == [
{
'name': ['foo'],
'help': 'foo help',
'default': False
}, {
'name': ['bar'],
'help': '',
'default': False
}
]
>   assert data['children'] == [
{
'name': 'install',
'help': 'install help',
'usage': 'usage: test_parse_nested install [-h] 
[--upgrade] ref',
'bare_usage': 'test_parse_nested install [-h] 
[--upgrade] ref',

'action_groups': [
{
'title': 'Positional Arguments',
'description': None,
'options': [
{
'name': ['ref'],
'help': 'foo1 help',
'default': None
}
]
},
{
'description': None,
'title': 'Named Arguments',
'options': [
{
'name': ['--upgrade'],
'default': False,
'help': 'foo2 help'
}
]
}
]
}
]
E   AssertionError: assert [{'action_gro...nstall', ...}] == 
[{'action_gro...nstall', ...}]
E At index 0 diff: {'name': 'install', 'help': 'install help', 
'usage': 'usage: test_parse_nested install [-h] [--upgrade] ref', 
'bare_usage': 'test_parse_nested install [-h] [--upgrade] ref', 
'action_groups': [{'title': 'Positional Arguments', 'description': None, 
'options': [{'name': ['ref'], 'default': None, 'help': 'foo1 help'}]}, 
{'title': 'options', 'description': None, 'options': [{'name'

Processed: sphinx-argparse: (autopkgtest) needs update for python3.10: output changed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001487 [src:sphinx-argparse] sphinx-argparse: (autopkgtest) needs update 
for python3.10: output changed
Added indication that 1001487 affects src:python3-defaults

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

Bug#1001488: toolz: (autopkgtest) needs update for python3.10: Missing introspection for the following callables

[Paul Gevers]

Source: toolz
Version: 0.11.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of toolz fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
toolz  from testing0.11.1-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/t/toolz/17446745/log.gz

Testing with python3.10:
= test session starts 
==

platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.ua55b3g2/downtmp/autopkgtest_tmp
collected 179 items

tests/test_curried.py .. 
 [  5%]
tests/test_curried_doctests.py . 
 [  6%]
tests/test_dicttoolz.py ... 
 [ 32%]
tests/test_functoolz.py .. 
 [ 53%]
tests/test_inspect_args.py ..F.. 
 [ 63%]
tests/test_itertoolz.py  
[ 89%]
.. 
 [ 91%]
tests/test_recipes.py .. 
 [ 92%]
tests/test_serialization.py . 
 [ 97%]
tests/test_signatures.py ... 
 [ 98%]
tests/test_tlz.py . 
 [ 99%]
tests/test_utils.py . 
 [100%]


=== FAILURES 
===
___ test_introspect_builtin_modules 



def test_introspect_builtin_modules():
mods = [builtins, functools, itertools, operator, toolz,
toolz.functoolz, toolz.itertoolz, toolz.dicttoolz, 
toolz.recipes]

blacklist = set()
def add_blacklist(mod, attr):
if hasattr(mod, attr):
blacklist.add(getattr(mod, attr))
add_blacklist(builtins, 'basestring')
add_blacklist(builtins, 'NoneType')
add_blacklist(builtins, '__metaclass__')
add_blacklist(builtins, 'sequenceiterator')
def is_missing(modname, name, func):
if name.startswith('_') and not name.startswith('__'):
return False
if name.startswith('__pyx_unpickle_') or 
name.endswith('_cython__'):

return False
try:
if issubclass(func, BaseException):
return False
except TypeError:
pass
try:
return (callable(func)
and func.__module__ is not None
and modname in func.__module__
and is_partial_args(func, (), {}) is not True
and func not in blacklist)
except AttributeError:
return False
missing = {}
for mod in mods:
modname = mod.__name__
for name, func in vars(mod).items():
if is_missing(modname, name, func):
if modname not in missing:
missing[modname] = []
missing[modname].append(name)
if missing:
messages = []
for modname, names in sorted(missing.items()):
msg = '{}:\n{}'.format(modname, '\n 
'.join(sorted(names)))

messages.append(msg)
message = 'Missing introspection for the following 
callables:\n\n'

  raise AssertionError(message + '\n\n'.join(messages))
E   AssertionError: Missing introspection for the following 
callables:

E   E   builtins:
E   anext

/usr/lib/python3/dist-packages/toolz/tests/test_inspect_args.py:433: 
AssertionError
=== warnings summary 
===

../../../../usr/lib/python3/dist-packages/toolz/compatibility.py:2
  /usr/lib/python3/dist-packages/toolz/compatibility.py:2: 
DeprecationWarning: The toolz.compatibility module is no longer needed 
in Python 3 and has been deprecated. Please import these utilities 
direc

Processed: toolz: (autopkgtest) needs update for python3.10: Missing introspection for the following callables

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001488 [src:toolz] toolz: (autopkgtest) needs update for python3.10: 
Missing introspection for the following callables
Added indication that 1001488 affects src:python3-defaults

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

Processed: twodict: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'KeysView'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001489 [src:twodict] twodict: (autopkgtest) needs update for python3.10: 
'collections' has no attribute 'KeysView'
Added indication that 1001489 affects src:python3-defaults

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

Bug#1001489: twodict: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'KeysView'

[Paul Gevers]

Source: twodict
Version: 1.2-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of twodict fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
twodictfrom testing1.2-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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be 
updated. https://docs.python.org/3.9/library/collections.html says:

"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/t/twodict/17446747/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/twodict.py", line 25, in 
class DictKeysView(collections.KeysView):
AttributeError: module 'collections' has no attribute 'KeysView'
autopkgtest [14:18:28]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature

Processed: vorta: (autopkgtest) needs update for python3.10: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001490 [src:vorta] vorta: (autopkgtest) needs update for python3.10: 
Segmentation fault
Added indication that 1001490 affects src:python3-defaults

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

Bug#995769: Fwd: dbab_1.5.7-2_source.changes REJECTED

[Tong Sun]

On Fri, Dec 10, 2021 at 3:50 PM Nilesh Patra  wrote:
>
> Hi Tong,
>
> On Fri, 10 Dec 2021 15:12:20 -0500 Tong Sun 
>  wrote:
> > The Debian FTP Masters explains that it means "DMs may not upload
> > packages going to NEW. Need to use a sponsor for those".
>
> If your changes are updated in salsa, I could help you with sponsoring.
> Let me know if you'd like some help here. Please update salsa accordingly.

Oh, thanks a lot Nilesh!

Everything is updated on salsa. pls double check, e.g.:

https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9

Do you need me to upload to mentor first, you can totally take care of
it from salsa?

Bug#1001490: vorta: (autopkgtest) needs update for python3.10: Segmentation fault

[Paul Gevers]

Source: vorta
Version: 0.7.8-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of vorta fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
vorta  from testing0.7.8-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vorta/17446748/log.gz

=== Testing with python3.10 ===
= test session starts 
==

platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
PyQt5 5.15.6 -- Qt runtime 5.15.2 -- Qt compiled 5.15.2
rootdir: /tmp/autopkgtest-lxc.cftveias/downtmp/autopkgtest_tmp/vorta
plugins: mock-3.6.1, forked-1.3.0, asyncio-0.16.0, qt-4.0.2
collected 69 items

tests/test_archives.py .Fatal Python error: Segmentation fault

Thread 0x7fc1e02c7740 (most recent call first):
  File "/usr/lib/python3/dist-packages/pytestqt/qt_compat.py", line 156 
in exec
  File "/usr/lib/python3/dist-packages/pytestqt/wait_signal.py", line 
51 in wait

  File "/usr/lib/python3/dist-packages/pytestqt/qtbot.py", line 435 in wait
  File "/usr/lib/python3/dist-packages/pytestqt/qtbot.py", line 528 in 
waitUntil
  File 
"/tmp/autopkgtest-lxc.cftveias/downtmp/autopkgtest_tmp/vorta/tests/test_archives.py", 
line 46 in test_repo_list
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 183 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in 

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1641 in 
runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 162 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in 

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 255 in 

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 311 in 
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 254 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 215 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 126 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 109 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in 

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 348 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in 

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in 
__call__

  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 323 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 269 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 316 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in 

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in 
_hookexec
  File "/usr

Bug#1001491: astroscrappy: autopkgtest regression on armhf

[Paul Gevers]

Source: astroscrappy
Version: 1.1.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
astroscrappy   from testing1.1.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=astroscrappy

https://ci.debian.net/data/autopkgtest/testing/armhf/a/astroscrappy/17430190/log.gz

= test session starts 
==

platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.ijtoh3o_/downtmp/autopkgtest_tmp
plugins: doctestplus-0.11.1, mock-3.6.1, arraydiff-0.3, 
filter-subpackage-0.1.1, cov-3.0.0, hypothesis-5.43.3, 
astropy-header-0.1.2, remotedata-0.3.2, openfiles-0.5.0

collected 25 items

tests/test_astroscrappy.py . 
 [  4%]
tests/test_cleaning.py F... 
 [ 20%]
tests/test_gmos.py . 
 [ 24%]
tests/test_utils.py ... 
 [100%]


=== FAILURES 
===
__ test_median_clean 
___


def test_median_clean():
# Because our image only contains single cosmics, turn off
# neighbor detection. Also, our cosmic rays are high enough
# contrast that we can turn our detection threshold up.
_mask, clean = detect_cosmics(imdata, readnoise=10., gain=1.0,
  sigclip=6, sigfrac=1.0, 
cleantype='median')

assert (clean[crmask] != imdata[crmask]).sum() == crmask.sum()
# Run it again on the clean data. We shouldn't find any new 
cosmic rays

_mask2, _clean2 = detect_cosmics(clean, readnoise=10., gain=1.0,
 sigclip=6, sigfrac=1.0, 
cleantype='median')

  assert _mask2.sum() == 0

E   assert 8780 == 0
E+  where 8780 = 0xf3630530>()
E+where 0xf3630530> = array([[False, False, False, ..., False, False, False],\n 
  [False, False, False, ..., False, False, False],\n 
...alse],\n   [False, False, False, ..., False, False, False],\n 
   [False, False, False, ..., False, False, False]]).sum


/usr/lib/python3/dist-packages/astroscrappy/tests/test_cleaning.py:22: 
AssertionError
=== short test summary info 


FAILED tests/test_cleaning.py::test_median_clean - assert 8780 == 0
 1 failed, 24 passed in 23.13s 
=

autopkgtest [21:12:12]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#995769: Fwd: dbab_1.5.7-2_source.changes REJECTED

[Nilesh Patra]

On 12/11/21 2:30 AM, Tong Sun wrote:

Oh, thanks a lot Nilesh!

Everything is updated on salsa. pls double check, e.g.:

https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9


Just one query: you reason for moving to contrib is not entirely clear to me.
You wrote here[2] that it installs external data after install, but I do not see
anything peculiar in the postinst script that does something of that sort 
although I do not
know much about this package.

So could you elaborate on this thing? Just for my understanding.
Also, I would suggest to add the reasoning in d/README.Debian instead of the 
copyright
for making it easier to review for ftp masters.

Additionally, have you checked with piuparts that the upgade from buster indeed 
goes smooth?
 

Do you need me to upload to mentor first, you can totally take care of
it from salsa?


I will manage from salsa.


[1]: 
https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9

[2]: 
https://salsa.debian.org/debian/dbab/-/commit/72ff079bc607b564966b24dc2ae598be4e8f5750

Regards,
Nilesh




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1001478: apache-log4j2: CVE-2021-44228:: Remote code injection via crafted log messages

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #1001478 [src:apache-log4j2] apache-log4j2: CVE-2021-44228: Remote code 
injection via crafted log messages
Owner recorded as Markus Koschany .

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

Bug#1001478: apache-log4j2: CVE-2021-44228:: Remote code injection via crafted log messages

[Markus Koschany]

Control: owner -1 !

I am currently investigating the fix for CVE-2021-44228.

Markus




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

Bug#1001009: Downloads external files on install

[Tong Sun]

Bringing the discussion to the right track...

On Fri, Dec 10, 2021 at 4:13 PM Nilesh Patra  wrote:
>
> On 12/11/21 2:30 AM, Tong Sun wrote:
> > Oh, thanks a lot Nilesh!
> >
> > Everything is updated on salsa. pls double check, e.g.:
> >
> >
https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9
>
> Just one query: you reason for moving to contrib is not entirely clear to
me.
> You wrote here[2] that it installs external data after install, but I do
not see
> anything peculiar in the postinst script that does something of that sort
although I do not
> know much about this package.
>
> So could you elaborate on this thing? Just for my understanding.

dbab moving to contrib is because of this Bug#1001009. I personally have no
idea, but as requested by Andrey.

I guess it is about this line that is called from the postinst script
https://salsa.debian.org/debian/dbab/-/blob/master/bin/dbab-get-list#L21

Here is the recap of what he had said in this thread before:

If the package cannot function without this or similar unpackaged file, it
> should be moved to contrib. If it can, the downloading should be done by
> the
> user/administrator.


I've asked some follow-up questions and his answer is enclosed *below*.

> Also, I would suggest to add the reasoning in d/README.Debian instead of
the copyright
> for making it easier to review for ftp masters.
>
> Additionally, have you checked with piuparts that the upgrade from buster
indeed goes smooth?

Hmm, no. This is the first time I heard of piuparts

I did some search, but I got two 404 for the two most important thing that
I need to read:


   1. piuparts itself has a README
   
   *from*
   
https://wiki.debian.org/piuparts?action=fullsearch&context=180&value=dbab&titlesearch=Titles
   2. A package I'm interested in is in an untestable state. How can I find
   out if it would pass the piuparts test?

   A) Run piuparts manually
   
,
   as described in that README.

   *from* https://wiki.debian.org/piuparts/FAQ


Is it a done-online thing or I need to download something and try to learn
how to use it?

> > Do you need me to upload to mentor first, you can totally take care of
> > it from salsa?
>
> I will manage from salsa.

Thanks, I'll add the reasoning into d/README.Debian once things are settled.

Thanks again.

> > [1]:
https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9
> [2]:
https://salsa.debian.org/debian/dbab/-/commit/72ff079bc607b564966b24dc2ae598be4e8f5750


On Tue, Dec 7, 2021 at 10:57 AM Andrey Rahmatullin  wrote:
>
> On Sun, Dec 05, 2021 at 09:56:02AM -0500, Tong Sun wrote:
> > Thanks Andrey,
> >
> > Two questions,
> >
> > By "moved to contrib", did you meant to change
> >
> > Section: net
> >
> > to
> >
> > Section: contrib
> >
> > in d/control?
> Please read
> https://www.debian.org/doc/debian-policy/ch-archive.html#archive-areas and
> https://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
>
> > Now, let's define what "package cannot function" actually means. If
> > functions normally without this or similar unpackaged file, but the
> > program is completely data driven, i.e., no ads sites from the list
> > are blocked unless the list is there.
> >
> > So, strictly speaking, the package indeed cannot function without this
> > or similar unpackaged file, right? And the solution is just above,
> > right?
> I don't know the current project consensus on this, if it exists.
> If the software can only work with certain non-free files it should go
> into contrib, if OTOH it can work with some user-provided files, or with
> free files if those exist, it can stay in main. But downloading external
> files in postinst is certainly not fit for main.
>
> --
> WBR, wRAR

Bug#1001346: knack: needs update for python3.10: 'Iterable' from 'collections' is removed

[Luca Boccassi]

Control: reassign -1 python3-tabulate 0.8.7-0.1
Control: close -1 0.8.7-0.2

On Wed, 8 Dec 2021 23:03:58 +0100 Paul Gevers 
wrote:
> Source: knack
> Version: 0.9.0-1
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:python3-defaults
> 
> Dear maintainer(s),
> 
> With a recent upload of python3-defaults the autopkgtest of knack
fails 
> in testing when that autopkgtest is run with the binary packages of 
> python3-defaults from unstable. It passes when run with only packages
> from testing. In tabular form:
> 
> pass    fail
> python3-defaults   from testing    3.9.8-1
> knack  from testing    0.9.0-1
> all others from testing    from testing
> 
> I copied some of the output at the bottom of this report. 
> https://docs.python.org/3.9/library/collections.html says:
> """
> Deprecated since version 3.3, will be removed in version 3.10: Moved 
> Collections Abstract Base Classes to the collections.abc module. For 
> backwards compatibility, they continue to be visible in this module 
> through Python 3.9.
> """
> Time to move on.
> 
> Currently this regression is blocking the migration of python3-
defaults 
> to testing [1].

Hi,

python3-knack doesn't call Iterable directly, it was coming from
python3-tabulate. This was fixed already, so reassigning and closing.

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: knack: needs update for python3.10: 'Iterable' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-tabulate 0.8.7-0.1
Bug #1001346 [src:knack] knack: needs update for python3.10: 'Iterable' from 
'collections' is removed
Bug reassigned from package 'src:knack' to 'python3-tabulate'.
No longer marked as found in versions knack/0.9.0-1.
Ignoring request to alter fixed versions of bug #1001346 to the same values 
previously set
Bug #1001346 [python3-tabulate] knack: needs update for python3.10: 'Iterable' 
from 'collections' is removed
Marked as found in versions python-tabulate/0.8.7-0.1.
> close -1 0.8.7-0.2
Bug #1001346 [python3-tabulate] knack: needs update for python3.10: 'Iterable' 
from 'collections' is removed
Marked as fixed in versions python-tabulate/0.8.7-0.2.
Bug #1001346 [python3-tabulate] knack: needs update for python3.10: 'Iterable' 
from 'collections' is removed
Marked Bug as done

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

Processed: reassign 927931 to src:bind9, reassign 927935 to src:bind9, reassign 930747 to src:bind9 ...

[Debian Bug Tracking System]

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

> # bugs from (removed) src:bind that might be relevant for src:bind9, too
> reassign 927931 src:bind9 1:9.13.3-1
Bug #927931 [src:bind] bind: CVE-2019-6467: An error in the nxdomain redirect 
feature can cause BIND to exit with an INSIST assertion failure in query.c
Warning: Unknown package 'src:bind'
Bug reassigned from package 'src:bind' to 'src:bind9'.
No longer marked as found in versions bind/1:9.13.3-1.
Ignoring request to alter fixed versions of bug #927931 to the same values 
previously set
Bug #927931 [src:bind9] bind: CVE-2019-6467: An error in the nxdomain redirect 
feature can cause BIND to exit with an INSIST assertion failure in query.c
The source 'bind9' and version '1:9.13.3-1' do not appear to match any binary 
packages
Marked as found in versions bind9/1:9.13.3-1.
> reassign 927935 src:bind9 1:9.13.3-1
Bug #927935 [src:bind] bind: CVE-2018-5743: Limiting simultaneous TCP clients 
is ineffective
Warning: Unknown package 'src:bind'
Bug reassigned from package 'src:bind' to 'src:bind9'.
No longer marked as found in versions bind/1:9.13.3-1.
Ignoring request to alter fixed versions of bug #927935 to the same values 
previously set
Bug #927935 [src:bind9] bind: CVE-2018-5743: Limiting simultaneous TCP clients 
is ineffective
The source 'bind9' and version '1:9.13.3-1' do not appear to match any binary 
packages
Marked as found in versions bind9/1:9.13.3-1.
> reassign 930747 src:bind9 1:9.13.3-1
Bug #930747 [src:bind] bind: CVE-2019-6471: A race condition when discarding 
malformed packets can cause BIND to exit with an assertion failure
Warning: Unknown package 'src:bind'
Bug reassigned from package 'src:bind' to 'src:bind9'.
No longer marked as found in versions bind/1:9.13.3-1.
Ignoring request to alter fixed versions of bug #930747 to the same values 
previously set
Bug #930747 [src:bind9] bind: CVE-2019-6471: A race condition when discarding 
malformed packets can cause BIND to exit with an assertion failure
The source 'bind9' and version '1:9.13.3-1' do not appear to match any binary 
packages
Marked as found in versions bind9/1:9.13.3-1.
> reassign 903586 src:bind9 1:9.13.1+dfsg-1
Bug #903586 [src:bind] bind: fails to build twice in a row
Warning: Unknown package 'src:bind'
Bug reassigned from package 'src:bind' to 'src:bind9'.
No longer marked as found in versions bind/1:9.13.1+dfsg-1.
Ignoring request to alter fixed versions of bug #903586 to the same values 
previously set
Bug #903586 [src:bind9] bind: fails to build twice in a row
The source 'bind9' and version '1:9.13.1+dfsg-1' do not appear to match any 
binary packages
Marked as found in versions bind9/1:9.13.1+dfsg-1.
> reassign 903761 src:bind9 1:9.13.1+dfsg-1
Bug #903761 [bind] bind: fails to install: rndc-confgen: The -r option has been 
deprecated.
Warning: Unknown package 'bind'
Bug reassigned from package 'bind' to 'src:bind9'.
No longer marked as found in versions bind/1:9.13.2-1~exp0, 
bind/1:9.13.1+dfsg-1, and bind/1:9.13.3-1.
Ignoring request to alter fixed versions of bug #903761 to the same values 
previously set
Bug #903761 [src:bind9] bind: fails to install: rndc-confgen: The -r option has 
been deprecated.
The source 'bind9' and version '1:9.13.1+dfsg-1' do not appear to match any 
binary packages
Marked as found in versions bind9/1:9.13.1+dfsg-1.
> thanks
Stopping processing here.

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

Bug#991505: marked as done (bind: duplicate, old version of bind9 source package, remove from experimental?)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 23:54:25 +0100
with message-id <09a66b1e-c439-8bd0-22c7-3538569f3...@debian.org>
and subject line src:bind was removed from experimental
has caused the Debian Bug report #991505,
regarding bind: duplicate, old version of bind9 source package, remove from 
experimental?
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.)


-- 
991505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind
Severity: serious
Version: 1:9.13.3-1
X-Debbugs-CC: Ondřej Surý , Bernhard Schmidt 


src:bind in Debian experimental seems to be an older version than
src:bind9 but still the same software. I suggest that src:bind be
removed from Debian experimental since it is a duplicate.

https://sources.debian.org/src/bind/experimental/debian/watch
https://sources.debian.org/src/bind9/unstable/debian/watch

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---

Version: 1:9.13.3-1+rm

See https://bugs.debian.org/1001404 for details of the removal of 
src:bind from experimental.



Andreas--- End Message ---

Bug#970417: marked as done (bind-host: missing 'host' binary)

[Debian Bug Tracking System]

Your message dated Fri, 10 Dec 2021 23:54:25 +0100
with message-id <09a66b1e-c439-8bd0-22c7-3538569f3...@debian.org>
and subject line src:bind was removed from experimental
has caused the Debian Bug report #970417,
regarding bind-host: missing 'host' 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.)


-- 
970417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind-host
Version: 1:9.13.3-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The `bind-host` package in experimental is missing both the executable
and the manpage.

esk@esk-xps:~$ dpkg -L bind-host
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
/usr/share/doc/bind-host
/usr/share/doc/bind-host/changelog.Debian.amd64.gz
/usr/share/doc/bind-host/changelog.Debian.gz
/usr/share/doc/bind-host/changelog.gz
/usr/share/doc/bind-host/copyright
/usr/share/man
/usr/share/man/man1
esk@esk-xps:~$

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

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

Versions of packages bind-host depends on:
ii  bind-libs  1:9.13.3-1+b1
ii  libc6  2.31-1
ii  libidn2-0  2.3.0-1
ii  libssl1.1  1.1.1g-1

bind-host recommends no packages.

bind-host suggests no packages.

-- debconf-show failed

-- 
Eldon Koyle
--- End Message ---
--- Begin Message ---

Version: 1:9.13.3-1+rm

See https://bugs.debian.org/1001404 for details of the removal of 
src:bind from experimental.



Andreas--- End Message ---

Processed: Re: ipywidgets: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001343 [src:ipywidgets] ipywidgets: (autopkgtest) needs update for 
python3.10: 'Mapping' from 'collections' is removed
Added tag(s) patch.

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

Bug#1001343: ipywidgets: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' is removed

[Steve Langasek]

Package: ipywidgets
Version: 6.0.0-8
Followup-For: Bug #1001343
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ipywidgets-6.0.0/debian/patches/python-3.10.patch 
ipywidgets-6.0.0/debian/patches/python-3.10.patch
--- ipywidgets-6.0.0/debian/patches/python-3.10.patch   1969-12-31 
16:00:00.0 -0800
+++ ipywidgets-6.0.0/debian/patches/python-3.10.patch   2021-12-10 
15:19:17.0 -0800
@@ -0,0 +1,32 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001343
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: ipywidgets-6.0.0/ipywidgets/widgets/widget_selection.py
+===
+--- ipywidgets-6.0.0.orig/ipywidgets/widgets/widget_selection.py
 ipywidgets-6.0.0/ipywidgets/widgets/widget_selection.py
+@@ -6,7 +6,7 @@
+ Represents an enumeration using a widget.
+ """
+ 
+-from collections import Mapping
++from collections.abc import Mapping
+ try:
+ from itertools import izip
+ except ImportError:  #python3.x
+Index: ipywidgets-6.0.0/ipywidgets/widgets/interaction.py
+===
+--- ipywidgets-6.0.0.orig/ipywidgets/widgets/interaction.py
 ipywidgets-6.0.0/ipywidgets/widgets/interaction.py
+@@ -26,7 +26,7 @@
+ from traitlets import HasTraits, Any, Unicode, observe
+ from numbers import Real, Integral
+ from warnings import warn
+-from collections import Iterable, Mapping
++from collections.abc import Iterable, Mapping
+ 
+ empty = Parameter.empty
+ 
diff -Nru ipywidgets-6.0.0/debian/patches/series 
ipywidgets-6.0.0/debian/patches/series
--- ipywidgets-6.0.0/debian/patches/series  2021-02-09 01:00:09.0 
-0800
+++ ipywidgets-6.0.0/debian/patches/series  2021-12-10 15:18:02.0 
-0800
@@ -7,3 +7,4 @@
 0009-Webpack-4-compatibility.patch
 0011-Simplify-sphinx-build.patch
 0012-Javascript-not-detected-hint.patch
+python-3.10.patch

Processed: Re: jaraco.itertools: needs update for python3.10: 'collections' has no attribute 'Mapping'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001344 [src:jaraco.itertools] jaraco.itertools: needs update for 
python3.10: 'collections' has no attribute 'Mapping'
Added tag(s) patch.

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

Bug#1001344: jaraco.itertools: needs update for python3.10: 'collections' has no attribute 'Mapping'

[Steve Langasek]

Package: jaraco.itertools
Version: 2.0.1-4
Followup-For: Bug #1001344
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 
jaraco.itertools-2.0.1/debian/patches/python-3.10.patch
--- jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 2021-12-10 
15:25:54.0 -0800
@@ -0,0 +1,28 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001344
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: jaraco.itertools-2.0.1/jaraco/itertools.py
+===
+--- jaraco.itertools-2.0.1.orig/jaraco/itertools.py
 jaraco.itertools-2.0.1/jaraco/itertools.py
+@@ -102,7 +102,7 @@
+   def __init__(self, sequence, func = lambda x: x):
+   self.sequence = iter(sequence)
+   self.func = func
+-  self.queues = collections.OrderedDict()
++  self.queues = collections.abc.OrderedDict()
+ 
+   def __getitem__(self, key):
+   try:
+@@ -863,7 +863,7 @@
+   item = ()
+   singleton = (
+   isinstance(item, six.string_types)
+-  or isinstance(item, collections.Mapping)
++  or isinstance(item, collections.abc.Mapping)
+   or not hasattr(item, '__iter__')
+   )
+   return (item,) if singleton else item
diff -Nru jaraco.itertools-2.0.1/debian/patches/series 
jaraco.itertools-2.0.1/debian/patches/series
--- jaraco.itertools-2.0.1/debian/patches/series2019-08-03 
12:41:53.0 -0700
+++ jaraco.itertools-2.0.1/debian/patches/series2021-12-10 
15:24:40.0 -0800
@@ -1 +1,2 @@
 Python3.7-support.patch
+python-3.10.patch

Processed: Re: jaraco.itertools: needs update for python3.10: 'collections' has no attribute 'Mapping'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001344 [src:jaraco.itertools] jaraco.itertools: needs update for 
python3.10: 'collections' has no attribute 'Mapping'
Ignoring request to alter tags of bug #1001344 to the same tags previously set

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

Bug#1001344: jaraco.itertools: needs update for python3.10: 'collections' has no attribute 'Mapping'

[Steve Langasek]

Package: jaraco.itertools
Version: 2.0.1-4
Followup-For: Bug #1001344
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Apologies, the previous patch was buggy and I didn't catch it in my
pre-upload testing.  Here is a fixed patch that builds successfully.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 
jaraco.itertools-2.0.1/debian/patches/python-3.10.patch
--- jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ jaraco.itertools-2.0.1/debian/patches/python-3.10.patch 2021-12-10 
15:47:20.0 -0800
@@ -0,0 +1,19 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001344
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: jaraco.itertools-2.0.1/jaraco/itertools.py
+===
+--- jaraco.itertools-2.0.1.orig/jaraco/itertools.py
 jaraco.itertools-2.0.1/jaraco/itertools.py
+@@ -863,7 +863,7 @@
+   item = ()
+   singleton = (
+   isinstance(item, six.string_types)
+-  or isinstance(item, collections.Mapping)
++  or isinstance(item, collections.abc.Mapping)
+   or not hasattr(item, '__iter__')
+   )
+   return (item,) if singleton else item
diff -Nru jaraco.itertools-2.0.1/debian/patches/series 
jaraco.itertools-2.0.1/debian/patches/series
--- jaraco.itertools-2.0.1/debian/patches/series2019-08-03 
12:41:53.0 -0700
+++ jaraco.itertools-2.0.1/debian/patches/series2021-12-10 
15:24:40.0 -0800
@@ -1 +1,2 @@
 Python3.7-support.patch
+python-3.10.patch

Bug#1001347: legacy-api-wrap: autopkgtest tests for all supported python3s but fails to install them

[Steve Langasek]

Package: legacy-api-wrap
Version: 1.2-2
Followup-For: Bug #1001347
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru legacy-api-wrap-1.2/debian/tests/control 
legacy-api-wrap-1.2/debian/tests/control
--- legacy-api-wrap-1.2/debian/tests/control2021-09-18 11:30:43.0 
-0700
+++ legacy-api-wrap-1.2/debian/tests/control2021-12-10 16:28:57.0 
-0800
@@ -5,4 +5,4 @@
  ; echo "Testing with $py:"
  ; http_proxy= $py -m pytest tests.py
  ; done
-Depends: @, python3-pytest
+Depends: @, python3-pytest, python3-all

Processed: Re: legacy-api-wrap: autopkgtest tests for all supported python3s but fails to install them

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001347 [src:legacy-api-wrap] legacy-api-wrap: autopkgtest tests for all 
supported python3s but fails to install them
Added tag(s) patch.

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

Bug#1001363: nlopt: needs update for python3.10 in supported versions: No module named '_nlopt'

[Steve Langasek]

Package: nlopt
Version: 2.7.1-1
Followup-For: Bug #1001363
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Hello,

This failure is because nlopt has an override to try to install the
python3.10 extension, but it installs it to the wrong path.  The attached
patch should get it to the right path so that the python interpreter can
find it and load it.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nlopt-2.7.1/debian/rules nlopt-2.7.1/debian/rules
--- nlopt-2.7.1/debian/rules2021-12-08 03:23:51.0 -0800
+++ nlopt-2.7.1/debian/rules2021-12-10 17:02:18.0 -0800
@@ -36,7 +36,7 @@
distdir=debian/python3-nlopt/usr/lib/python3/dist-packages; \
mkdir -p $$distdir; \
for py3alt in $(PY3_ALT); do \
-   py3short=`echo $${py3alt} | sed "s/\.//g"`; \
+   py3short=`echo $${py3alt} | sed "s/\.//g"`-`dpkg-architecture 
-qDEB_HOST_MULTIARCH`; \
cp $(BUILDDIR)-python$${py3alt}/src/swig/_nlopt.so 
$$distdir/_nlopt.cpython-$${py3short}.so; \
chrpath -d $$distdir/_nlopt.cpython-$${py3short}.so; \
done

Processed: Re: nlopt: needs update for python3.10 in supported versions: No module named '_nlopt'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001363 [src:nlopt] nlopt: needs update for python3.10 in supported 
versions: No module named '_nlopt'
Added tag(s) patch.

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

Bug#1001243: cloud-sptheme: autopkgtest needs update for new version of python3-defaults: python3.10: not found

[Steve Langasek]

Package: cloud-sptheme
Version: 1.10.1.post20200504175005-3
Followup-For: Bug #1001243
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru cloud-sptheme-1.10.1.post20200504175005/debian/tests/control 
cloud-sptheme-1.10.1.post20200504175005/debian/tests/control
--- cloud-sptheme-1.10.1.post20200504175005/debian/tests/control
2021-11-02 11:43:34.0 -0700
+++ cloud-sptheme-1.10.1.post20200504175005/debian/tests/control
2021-12-10 17:42:25.0 -0800
@@ -1,3 +1,3 @@
 Tests: unittests
-Depends: @, python3-mock
+Depends: @, python3-mock, python3-all
 Restrictions: allow-stderr

Processed: Re: cloud-sptheme: autopkgtest needs update for new version of python3-defaults: python3.10: not found

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001243 [src:cloud-sptheme] cloud-sptheme: autopkgtest needs update for 
new version of python3-defaults: python3.10: not found
Added tag(s) patch.

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

Processed: Re: circuits: needs update for python3.10: 'Callable' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001244 [src:circuits] circuits: needs update for python3.10: 'Callable' 
from 'collections' is removed
Ignoring request to alter tags of bug #1001244 to the same tags previously set

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

Bug#1001244: circuits: needs update for python3.10: 'Callable' from 'collections' is removed

[Steve Langasek]

Package: circuits
Version: 3.1.0+ds1-2
Followup-For: Bug #1001244
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Apologies, the previous patch let the import test pass in local testing
here, but is incomplete.  Please find attached a more complete patch that
should actually let autopkgtests pass.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru circuits-3.1.0+ds1/debian/patches/python-3.10.patch 
circuits-3.1.0+ds1/debian/patches/python-3.10.patch
--- circuits-3.1.0+ds1/debian/patches/python-3.10.patch 1969-12-31 
16:00:00.0 -0800
+++ circuits-3.1.0+ds1/debian/patches/python-3.10.patch 2021-12-10 
17:35:24.0 -0800
@@ -0,0 +1,97 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001244
+Last-Update: 2021-12-10
+Forwarded: no
+
+Index: circuits-3.1.0+ds1/circuits/core/handlers.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/core/handlers.py
 circuits-3.1.0+ds1/circuits/core/handlers.py
+@@ -7,7 +7,7 @@
+ """
+ 
+ from inspect import getargspec
+-from collections import Callable
++from collections.abc import Callable
+ 
+ 
+ def handler(*names, **kwargs):
+Index: circuits-3.1.0+ds1/circuits/core/components.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/core/components.py
 circuits-3.1.0+ds1/circuits/core/components.py
+@@ -9,7 +9,7 @@
+ from itertools import chain
+ from types import MethodType
+ from inspect import getmembers
+-from collections import Callable
++from collections.abc import Callable
+ 
+ from .manager import Manager
+ from .handlers import handler, HandlerMetaClass
+Index: circuits-3.1.0+ds1/circuits/web/controllers.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/web/controllers.py
 circuits-3.1.0+ds1/circuits/web/controllers.py
+@@ -9,7 +9,7 @@
+ 
+ import json
+ from inspect import getargspec
+-from collections import Callable
++from collections.abc import Callable
+ from functools import update_wrapper
+ 
+ from circuits.core import handler, BaseComponent
+Index: circuits-3.1.0+ds1/circuits/web/parsers/multipart.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/web/parsers/multipart.py
 circuits-3.1.0+ds1/circuits/web/parsers/multipart.py
+@@ -57,7 +57,7 @@
+ # Some of these were copied from bottle: http://bottle.paws.de/
+ 
+ try:
+-from collections import MutableMapping as DictMixin
++from collections.abc import MutableMapping as DictMixin
+ except ImportError: # pragma: no cover (fallback for Python 2.5)
+ from UserDict import DictMixin
+ 
+Index: circuits-3.1.0+ds1/circuits/web/tools.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/web/tools.py
 circuits-3.1.0+ds1/circuits/web/tools.py
+@@ -316,7 +316,7 @@
+ if not encrypt:
+ encrypt = _httpauth.DIGEST_AUTH_ENCODERS[_httpauth.MD5]
+ 
+-if isinstance(users, collections.Callable):
++if isinstance(users, collections.abc.Callable):
+ try:
+ # backward compatibility
+ users = users()  # expect it to return a dictionary
+Index: circuits-3.1.0+ds1/circuits/web/utils.py
+===
+--- circuits-3.1.0+ds1.orig/circuits/web/utils.py
 circuits-3.1.0+ds1/circuits/web/utils.py
+@@ -14,7 +14,7 @@
+ from math import sqrt
+ from io import TextIOWrapper
+ from cgi import FieldStorage
+-from collections import MutableMapping
++from collections.abc import MutableMapping
+ 
+ try:
+ from urllib.parse import urljoin as _urljoin
+Index: circuits-3.1.0+ds1/tests/conftest.py
+===
+--- circuits-3.1.0+ds1.orig/tests/conftest.py
 circuits-3.1.0+ds1/tests/conftest.py
+@@ -101,7 +101,7 @@
+ def wait_for(obj, attr, value=True, timeout=3.0):
+ from circuits.core.manager import TIMEOUT
+ for i in range(int(timeout / TIMEOUT)):
+-if isinstance(value, collections.Callable):
++if isinstance(value, collections.abc.Callable):
+ if value(obj, attr):
+ return True
+ elif getattr(obj, attr) == value:
diff -Nru circuits-3.1.0+ds1/debian/patches/series 
circuits-3.1.0+ds1/debian/patches/series
--- circuits-3.1.0+ds1/debian/patches/series2019-08-05 00:03:56.0 
-0700
+++ circuits-3.1.0+ds1/debian/patches/series2021-12-10 12:01:30.0 
-0800
@@ -3,3 +3,4 @@
 03_disa

Bug#1001419: marked as done (python-css-parser: (autopkgtest) needs update for python3.10: Right exception, wrong message: got 'can't set attribute 'literalname'' instead of 'can't set attribute')

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 03:18:46 +
with message-id 
and subject line Bug#1001419: fixed in python-css-parser 1.0.6-2
has caused the Debian Bug report #1001419,
regarding python-css-parser: (autopkgtest) needs update for python3.10: Right 
exception, wrong message: got 'can't set attribute 'literalname'' instead of 
'can't set attribute'
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.)


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

Source: python-css-parser
Version: 1.0.6-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-css-parser fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-css-parser  from testing1.0.6-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-css-parser/17420647/log.gz

=== FAILURES 
===
__ PropertyTestCase.test_literalname 
___


self = testMethod=test_literalname>

excClass = , msg = "can't set attribute"
callableObj = 0x7fd187f22d10>

args = ('literalname', 'color'), kwargs = {}
excMsg = "can't set attribute 'literalname'"

def assertRaisesMsg(self, excClass, msg, callableObj, *args, **kwargs):
"""
Just like unittest.TestCase.assertRaises,
but checks that the message is right too.
Usage::
self.assertRaisesMsg(
MyException, "Exception message",
my_function, (arg1, arg2)
)
from
http://www.nedbatchelder.com/blog/200609.html#e20060905T064418
"""
try:

  callableObj(*args, **kwargs)

E   AttributeError: can't set attribute 'literalname'

/tmp/autopkgtest-lxc.ysif6shm/downtmp/autopkgtest_tmp/python-css-parser/css_parser_tests/basetest.py:168: 
AttributeError


During handling of the above exception, another exception occurred:

self = testMethod=test_literalname>


def test_literalname(self):
"Property.literalname"
p = css_parser.css.property.Property(r'c\olor', 'red')
self.assertEqual(r'c\olor', p.literalname)

  self.assertRaisesMsg(AttributeError, "can't set attribute", p.__setattr__,

 'literalname', 'color')

/tmp/autopkgtest-lxc.ysif6shm/downtmp/autopkgtest_tmp/python-css-parser/css_parser_tests/test_property.py:165: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
self = testMethod=test_literalname>

excClass = , msg = "can't set attribute"
callableObj = 0x7fd187f22d10>

args = ('literalname', 'color'), kwargs = {}
excMsg = "can't set attribute 'literalname'"

def assertRaisesMsg(self, excClass, msg, callableObj, *args, **kwargs):
"""
Just like unittest.TestCase.assertRaises,
but checks that the message is right too.
Usage::
self.assertRaisesMsg(
MyException, "Exception message",
my_function, (arg1, arg2)
)
from
http://www.nedbatchelder.com/blog/200609.html#e20060905T064418
"""
try:
callableObj(*args, **kwargs)
except excClass as exc:
excMsg = str(exc)
if not msg:
# No message provided: any message is fine.
return
elif excMsg == msg:
   

Processed: Re: Bug#1001419: python-css-parser: (autopkgtest) needs update for python3.10: Right exception, wrong message: got 'can't set attribute 'literalname'' instead of 'can't set attribute'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ebook-utils/css-parser/issues/10
Bug #1001419 {Done: Nicholas D Steeves } 
[src:python-css-parser] python-css-parser: (autopkgtest) needs update for 
python3.10: Right exception, wrong message: got 'can't set attribute 
'literalname'' instead of 'can't set attribute'
Set Bug forwarded-to-address to 
'https://github.com/ebook-utils/css-parser/issues/10'.

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