Processed: bug 1000684 is forwarded to https://github.com/wagtail/django-modelcluster/issues/147

[Debian Bug Tracking System]

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

> forwarded 1000684 https://github.com/wagtail/django-modelcluster/issues/147
Bug #1000684 [src:python-django-modelcluster] python-django-modelcluster: 
autopkgtest fails with django-taggit >= 2.0.0
Set Bug forwarded-to-address to 
'https://github.com/wagtail/django-modelcluster/issues/147'.
> thanks
Stopping processing here.

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

Processed: Fix versions

[Debian Bug Tracking System]

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

> notfound 1000339 r-cran-raster/3.5-2-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-raster/3.5-2-1.
> notfound 1000339 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'
Ignoring request to alter found versions of bug #1000339 to the same values 
previously set
> reassign 1000339 r-cran-raster 3.5-2-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'
Bug reassigned from package 'src:r-cran-raster, src:r-cran-satellite' to 
'r-cran-raster'.
Ignoring request to alter found versions of bug #1000339 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1000339 to the same values 
previously set
Bug #1000339 [r-cran-raster] r-cran-raster breaks r-cran-satellite autopkgtest: 
unable to find an inherited method for function 'extend'
Marked as found in versions r-cran-raster/3.5-2-1.
> fixed 1000339 3.5-9-1
Bug #1000339 [r-cran-raster] r-cran-raster breaks r-cran-satellite autopkgtest: 
unable to find an inherited method for function 'extend'
Marked as fixed in versions r-cran-raster/3.5-9-1.
> close 1000339
Bug #1000339 [r-cran-raster] r-cran-raster breaks r-cran-satellite autopkgtest: 
unable to find an inherited method for function 'extend'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#988085: marked as done (Missing depends on python3-wheel and should not depend/recommend python3-pip)

[Debian Bug Tracking System]

Your message dated Sun, 12 Dec 2021 00:48:33 +
with message-id 
and subject line Bug#988085: fixed in python-build 0.7.0-2
has caused the Debian Bug report #988085,
regarding Missing depends on python3-wheel and should not depend/recommend 
python3-pip
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.)


-- 
988085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python3-build
Version: 0.1.0-3
Severity: important

0.1.0-3 started to depend on python3-pip.  I don't think this is the correct
solution for the Debian package, as it will pull in pip for nearly every package
build in the future, defaulting to download/online mode by default.

In #978674, this dependency was added. I don't have a good solution yet, but
what about considering to have a binary package operating in offline mode, and
one in online mode, so that the offline mode package can be used as a build
dependency by default for builds?
--- End Message ---
--- Begin Message ---
Source: python-build
Source-Version: 0.7.0-2
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-build 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: Sat, 11 Dec 2021 19:20:52 -0500
Source: python-build
Architecture: source
Version: 0.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Scott Kitterman 
Closes: 988085
Changes:
 python-build (0.7.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Update python3-build depends: (Closes: 988085)
 - Add missing Depends on python3-wheel
 - Move python3-pip and python3-venv to suggests
Checksums-Sha1:
 e5a8b9c79a66e216adaf51eeeb2a5dd034fbddf3 2100 python-build_0.7.0-2.dsc
 dc3c1890d3420c74ceb62718ba08faa4ffac2360 2960 
python-build_0.7.0-2.debian.tar.xz
 b09968a292b91d52c31c39201425a40d65e5daa5 5877 
python-build_0.7.0-2_source.buildinfo
Checksums-Sha256:
 9657cf09f02719db7c37c74ae5e6e11a8a8c63653bb04b63ea2bcdf94330bd3e 2100 
python-build_0.7.0-2.dsc
 70e769ef9b6541a0cd01f92714debc7c1c99d06eaf66fd12fdbe5246b5ce1b29 2960 
python-build_0.7.0-2.debian.tar.xz
 abca62ea7445ff6bf145988be1f7dce3a80eaa84bf02689249b4e1e2fb6b76c6 5877 
python-build_0.7.0-2_source.buildinfo
Files:
 ebe35ad82aef0aa1e1d469ff1f291c58 2100 python optional python-build_0.7.0-2.dsc
 528e1a9851e1b3e36df84157c8269af8 2960 python optional 
python-build_0.7.0-2.debian.tar.xz
 bce4782f24efd4d4791505ee606a4977 5877 python optional 
python-build_0.7.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAmG1QOYACgkQeNfe+5rV
mvHwABAAhmZlg/vIm11pt2Ht/6vikPY/cDWGDWmJGqh9eqNQJyc9PpL5Tskwja6j
B4sAVQCizCAetUPkGQLhWnQTUvMaNoSJVhjObH4ShF1Q6il5lThgbTm/vLHY/BSn
qGK168dYNwTx3yCR7nOx7ZdsiJQOJYRhDb2AKEEQAxpV4/07twfn4SaVDwB3u2gb
qncLTkwVaBCCh8DKSJE0AE8FS4L76g66e6qN479ATiUkHOERs6PMCO+Y1m77nMbI
RRVLJySVy5gTgG0W7taS4AEocBDlCZpjPPJm9H8J4rUZjDDgntX7r3bxf7D9cYaz
3ysQMs7MZO+39bLSRRfs2vO/ZlxdwkQnyIwh60PO2xMFvgX1OnYuPazIvkvE2lyo
867Mwf6+DzQFPQHbuzlsMl3ozp6e+HUsw+krkA15UewaXbJ+2+70rGfOJg60hcAS
CD3i5n7y/2ecAi3GeKjjoPOGKT69SBj6jyPAUEuUUu8F2udaQ2+qW14bMtenjTOb
ggInllA8LOjFahDDlLCb/v41idkjaNIMG/qJdJnk4U1e0iz5cFBk8jFMiymgeGMe
DX1HoFjF63gWkUhcEstu5fCA5i+qdx+siekFdwEzhzTleWipodmkgZJrzYFvoDN9
Vly7wQ0PhBXhX96+//tznbk9RFFLNsCLvP+vk8AaygvM2ldUHDc=
=FXCP
-END PGP SIGNATURE End Message ---

Processed: reassign 988085 to src:python-build

[Debian Bug Tracking System]

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

> reassign 988085 src:python-build
Bug #988085 [src:python3-build] Missing depends on python3-wheel and should not 
depend/recommend python3-pip
Warning: Unknown package 'src:python3-build'
Bug reassigned from package 'src:python3-build' to 'src:python-build'.
No longer marked as found in versions python3-build/0.1.0-3.
Ignoring request to alter fixed versions of bug #988085 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#997846: marked as done (httpbin: autopkgtest regression: KeyError: 'Content-Length')

[Debian Bug Tracking System]

Your message dated Sun, 12 Dec 2021 00:21:27 +
with message-id 
and subject line Bug#997846: fixed in httpbin 0.7.0+dfsg-2
has caused the Debian Bug report #997846,
regarding httpbin: autopkgtest regression: KeyError: 'Content-Length'
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.)


-- 
997846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httpbin
Version: 0.7.0+dfsg-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 httpbin the autopkgtest of httpbin fails in
testing when that autopkgtest is run with the binary packages of httpbin
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
httpbinfrom testing0.7.0+dfsg-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=httpbin

https://ci.debian.net/data/autopkgtest/testing/amd64/h/httpbin/15762030/log.gz

../usr/lib/python3/dist-packages/flask/json/__init__.py:211:
DeprecationWarning: Importing 'itsdangerous.json' is deprecated and will
be removed in ItsDangerous 2.1. Use Python's 'json' module instead.
  rv = _json.dumps(obj, **kwargs)
E.E..
==
ERROR: test_anything (__main__.HttpbinTestCase)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.nx05yeyf/downtmp/autopkgtest_tmp/test_httpbin.py",
line 161, in test_anything
self.assertEqual(data['headers']['Content-Length'], '0')
KeyError: 'Content-Length'

==
ERROR: test_get (__main__.HttpbinTestCase)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.nx05yeyf/downtmp/autopkgtest_tmp/test_httpbin.py",
line 147, in test_get
self.assertEqual(data['headers']['Content-Length'], '0')
KeyError: 'Content-Length'

--
Ran 63 tests in 5.996s

FAILED (errors=2)
autopkgtest [03:23:23]: test command1




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: httpbin
Source-Version: 0.7.0+dfsg-2
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated httpbin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Dec 2021 00:42:05 +0100
Source: httpbin
Architecture: source
Version: 0.7.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 997846
Changes:
 httpbin (0.7.0+dfsg-2) unstable; urgency=medium
 .
   * Modernize packaging
   * Fix test suite (Closes: #997846)
   * Adopt package by the Python Team
Checksums-Sha1:
 c09e9102509d054c1fefd6e6a6739b4e1d169a55 2141 httpbin_0.7.0+dfsg-2.dsc
 ddea8f5464aedd167941db0f3fe519a4b7fd0a5b 5564 
httpbin_0.7.0+dfsg-2.debian.tar.xz
 19e076d37f8d6c1193bd5dfea78ccd79031752e0 7118 
httpbin_0.7.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 fcedfc1157412d4e108037a47dbc5d5dd4263f67d6bfb0cc2ef9b2bb529c8494 2141 
httpbin_0.7.0+dfsg-2.dsc
 1078046abecddb3ee547d79e7ab51191842791531ce9c90ee451992721aefdee 5564 
httpbin_0.7.0+dfsg-2.debian.tar.xz
 d18a2440d0a30ce7e94721c6f32838389fae5bd28101a64b9fe59a196af1d81a 7118 

Bug#1001548: php-oscarotero-gettext, build-depends on package that is no longer in testing

[Peter Michael Green]

Package: php-oscarotero-gettext
Version: 4.8.2-6
Severity: serious
Justification: rc policy - "Packages must be buildable within the same release"

php-oscarotero-gettext build-depends on the php-illuminate-database binary 
package,
which is built by the php-laravel-framework source package which was recently 
removed
from testing, presumablly due to it's dependency on an old version of 
php-symphony.

I see two possible approaches to fixing this

1. Eliminate the build-dependency, given the content of the package I would 
assume
   it is most likely only used for testing
2. Get php-laravel-framework fixed and back into testing.

Processed: retitle 988085 to Missing depends on python3-wheel and should not depend/recommend python3-pip

[Debian Bug Tracking System]

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

> retitle 988085 Missing depends on python3-wheel and should not 
> depend/recommend python3-pip
Bug #988085 [src:python3-build] python3-build should not depend/recommend 
python3-pip
Warning: Unknown package 'src:python3-build'
Changed Bug title to 'Missing depends on python3-wheel and should not 
depend/recommend python3-pip' from 'python3-build should not depend/recommend 
python3-pip'.
Warning: Unknown package 'src:python3-build'
> thanks
Stopping processing here.

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

Processed: severity of 988085 is serious

[Debian Bug Tracking System]

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

> severity 988085 serious
Bug #988085 [src:python3-build] python3-build should not depend/recommend 
python3-pip
Warning: Unknown package 'src:python3-build'
Severity set to 'serious' from 'important'
Warning: Unknown package 'src:python3-build'
> thanks
Stopping processing here.

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

Bug#1001547: azure-cli: build-depends on removed package.

[Peter Michael Green]

Package: azure-cli
Version: 2.31.0-1
Severity: serious

azure-cli build-depends on pylint3 which is no longer built by the pylint
source package, it is still present in unstable as a cruft package, but is
completely gone from testing.

Since the package was previously an empty (other than /usr/share/doc
files) fixing this should be a simple matter of updating your 
build-depedency.

(I have not done a test build though)

Processed: Bug#997846 marked as pending in httpbin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997846 [src:httpbin] httpbin: autopkgtest regression: KeyError: 
'Content-Length'
Added tag(s) pending.

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

Bug#997846: marked as pending in httpbin

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #997846 in httpbin 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/httpbin/-/commit/58a6d6fdf80e69c8216c73b9e73f89c2e6234f1d


Fix test suite

Closes: #997846


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997846

Processed: re: cvise: Please upgrade to llvm-toolchain-12 or 13

[Debian Bug Tracking System]

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

> severity 1000892 serious
Bug #1000892 [src:cvise] cvise: Please upgrade to llvm-toolchain-12 or 13
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1001546: crystal, build-depends on package that is no longer in testing

[Peter Michael Green]

Package: crystal
Version: 1.2.1+dfsg-6
Severity: serious
Justification: rc policy - "Packages must be buildable within the same 
release"


crystal build-depends on libllvm9 or libllvm8, neither of these packages are
available in testing anymore. Please investigate migration to a newer 
version

of llvm.

(Also it's slightly strange to be build-depending on binary libraries 
rather than

dev packages, and also strange to have the build-dependencies without
corrsponding runtime dependencies)

Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Peter Michael Green]

Package: pyopencl
Tags: bookworm
Severity: serious
Justification: rc policy - "Packages must be buildable within the same 
release"


pyopencl build-depends on pocl-opencl-icd which is no longer in testing.

Processed: fixed 927931 in 1:9.13.3-1+rm, fixed 927935 in 1:9.13.3-1+rm, fixed 930747 in 1:9.13.3-1+rm

[Debian Bug Tracking System]

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

> fixed 927931 1:9.13.3-1+rm
Bug #927931 {Done: Salvatore Bonaccorso } [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'
The source 'bind' and version '1:9.13.3-1+rm' do not appear to match any binary 
packages
Marked as fixed in versions bind/1:9.13.3-1+rm.
Warning: Unknown package 'src:bind'
> fixed 927935 1:9.13.3-1+rm
Bug #927935 {Done: Salvatore Bonaccorso } [src:bind] bind: 
CVE-2018-5743: Limiting simultaneous TCP clients is ineffective
Warning: Unknown package 'src:bind'
The source 'bind' and version '1:9.13.3-1+rm' do not appear to match any binary 
packages
Marked as fixed in versions bind/1:9.13.3-1+rm.
Warning: Unknown package 'src:bind'
> fixed 930747 1:9.13.3-1+rm
Bug #930747 {Done: Salvatore Bonaccorso } [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'
The source 'bind' and version '1:9.13.3-1+rm' do not appear to match any binary 
packages
Marked as fixed in versions bind/1:9.13.3-1+rm.
Warning: Unknown package 'src:bind'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
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

Processed: severity of 1001541 is serious

[Debian Bug Tracking System]

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

> severity 1001541 serious
Bug #1001541 [ecl] run-time shared lib not placed in package with proper name
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 22:39:40 +
with message-id 
and subject line Bug#1001488: fixed in toolz 0.11.2-1
has caused the Debian Bug report #1001488,
regarding toolz: (autopkgtest) needs update for python3.10: Missing 
introspection for the following callables
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.)


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

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 

Processed: reassign 1001508 to wnpp, tagging 999781, tagging 999806, reassign 996814 to src:kdepim-addons ...

[Debian Bug Tracking System]

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

> reassign 1001508 wnpp
Bug #1001508 [simplesok] ITP:simplesok -- Simple Sokoban is a (simple) Sokoban 
game.
Warning: Unknown package 'simplesok'
Bug reassigned from package 'simplesok' to 'wnpp'.
Ignoring request to alter found versions of bug #1001508 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1001508 to the same values 
previously set
> tags 999781 + sid bookworm
Bug #999781 [pythonmagick] pythonmagick: Misbuild when multiple supported 
python versions present
Added tag(s) sid and bookworm.
> tags 999806 + sid bookworm
Bug #999806 [pygattlib] pygattlib: Misbuild with multiple supported python 
versions
Added tag(s) sid and bookworm.
> reassign 996814 src:kdepim-addons
Bug #996814 {Done: Norbert Preining } [kaddressbook] 
Missing import and export in Kaddressbook
Bug reassigned from package 'kaddressbook' to 'src:kdepim-addons'.
No longer marked as found in versions kaddressbook/4:21.08.1-1.
No longer marked as fixed in versions kdepim-addons/21.08.1-2.
> fixed 996814 21.08.1-2
Bug #996814 {Done: Norbert Preining } 
[src:kdepim-addons] Missing import and export in Kaddressbook
Marked as fixed in versions kdepim-addons/21.08.1-2.
> affects 996814 + src:kaddressbook
Bug #996814 {Done: Norbert Preining } 
[src:kdepim-addons] Missing import and export in Kaddressbook
Added indication that 996814 affects src:kaddressbook
> reassign 910822 python3-docker
Bug #910822 {Done: Anthony Fok } 
[golang-docker-credential-helpers] Subject: golang-docker-credential-helpers: 
headless gnome-keyring failure
Bug reassigned from package 'golang-docker-credential-helpers' to 
'python3-docker'.
No longer marked as found in versions 
golang-github-docker-docker-credential-helpers/0.6.1-1.
No longer marked as fixed in versions python-docker/4.1.0-1.
> fixed 910822 4.1.0-1
Bug #910822 {Done: Anthony Fok } [python3-docker] Subject: 
golang-docker-credential-helpers: headless gnome-keyring failure
Marked as fixed in versions python-docker/4.1.0-1.
> affects 910822 + golang-docker-credential-helpers
Bug #910822 {Done: Anthony Fok } [python3-docker] Subject: 
golang-docker-credential-helpers: headless gnome-keyring failure
Added indication that 910822 affects golang-docker-credential-helpers
> notfound 993731 1.5.17-2
Bug #993731 {Done: Alexandre Detiste } 
[systemd-cron] systemd-cron: CVE-2017-9525: group crontab to root escalation 
via postinst
No longer marked as found in versions systemd-cron/1.5.17-2.
> unarchive 993781
Bug #993781 {Done: Alastair McKinstry } 
[src:python-xarray] missing Depends: python3-jinja2: xarray uses dask widgets
Unarchived Bug 993781
> fixed 993781 0.19.0-6
Bug #993781 {Done: Alastair McKinstry } 
[src:python-xarray] missing Depends: python3-jinja2: xarray uses dask widgets
Marked as fixed in versions python-xarray/0.19.0-6.
> reassign 993694 python3-xarray
Bug #993694 {Done: Alastair McKinstry } [python3-dask] 
missing Depends: python3-jinja2
Bug reassigned from package 'python3-dask' to 'python3-xarray'.
No longer marked as found in versions dask/2021.08.1+dfsg-1.
No longer marked as fixed in versions python-xarray/0.19.0-6.
> fixed 993694 0.19.0-6
Bug #993694 {Done: Alastair McKinstry } [python3-xarray] 
missing Depends: python3-jinja2
Marked as fixed in versions python-xarray/0.19.0-6.
> affects 993694 + python3-dask
Bug #993694 {Done: Alastair McKinstry } [python3-xarray] 
missing Depends: python3-jinja2
Added indication that 993694 affects python3-dask
> notfixed 929116 241-4
Bug #929116 {Done: Michael Biebl } [src:systemd] systemd: 
CVE-2018-20839
Bug #954094 {Done: Michael Biebl } [src:systemd] 
/bin/systemd: Running startx in X session switches to VC, input duplicated to 
X, login at getty exfiltrates creds
No longer marked as fixed in versions systemd/241-4.
No longer marked as fixed in versions systemd/241-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001508
910822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910822
929116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929116
954094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954094
993694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993694
993731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993731
993781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993781
996814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996814
999781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999781
999806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1001541: run-time shared lib not placed in package with proper name

[Jochen Sprickerhof]

Package: ecl
Version: 21.2.1+ds-1
Severity: critical
X-Debbugs-Cc: jspri...@debian.org

Hi,

according to policy:

"The run-time shared library must be placed in a package whose name
changes whenever the SONAME of the shared library changes."

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html

This breaks unrelated software, for example sagemath:

$ sage -c "solve(x, x)"
Traceback (most recent call last):
  File "/usr/share/sagemath/bin/sage-eval", line 10, in 
eval(compile(s,'','exec'))
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sage/symbolic/relation.py", line 1044, 
in solve
return _solve_expression(f, x, explicit_solutions, multiplicities, 
to_poly_solve, solution_dict, algorithm, domain)
  File "/usr/lib/python3/dist-packages/sage/symbolic/relation.py", line 1283, 
in _solve_expression
m = ex._maxima_()
  File "sage/symbolic/expression.pyx", line 1015, in 
sage.symbolic.expression.Expression._maxima_ 
(build/cythonized/sage/symbolic/expression.cpp:7931)
  File "sage/structure/sage_object.pyx", line 680, in 
sage.structure.sage_object.SageObject._interface_ 
(build/cythonized/sage/structure/sage_object.c:5480)
  File "sage/misc/lazy_import.pyx", line 329, in 
sage.misc.lazy_import.LazyImport.__getattr__ 
(build/cythonized/sage/misc/lazy_import.c:3870)
  File "sage/misc/lazy_import.pyx", line 191, in 
sage.misc.lazy_import.LazyImport.get_object 
(build/cythonized/sage/misc/lazy_import.c:2435)
  File "sage/misc/lazy_import.pyx", line 228, in 
sage.misc.lazy_import.LazyImport._get_object 
(build/cythonized/sage/misc/lazy_import.c:2842)
  File "sage/misc/lazy_import.pyx", line 224, in 
sage.misc.lazy_import.LazyImport._get_object 
(build/cythonized/sage/misc/lazy_import.c:2704)
  File "/usr/lib/python3/dist-packages/sage/interfaces/maxima_lib.py", line 92, 
in 
from sage.libs.ecl import EclObject, ecl_eval
ImportError: libecl.so.20.4: cannot open shared object file: No such file or 
directory


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

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

Versions of packages ecl depends on:
ii  gcc   4:11.2.0-2
ii  libatomic-ops-dev 7.6.12-1
ii  libc6 2.32-5
ii  libffi-dev3.4.2-3
ii  libffi8   3.4.2-3
ii  libgc-dev 1:8.0.6-1.1
ii  libgc11:8.0.6-1.1
ii  libgmp-dev2:6.2.1+dfsg-3
ii  libgmp10  2:6.2.1+dfsg-3
ii  libncurses-dev [libncurses5-dev]  6.3-1
ii  libncurses5-dev   6.3-1

ecl recommends no packages.

Versions of packages ecl suggests:
pn  ecl-doc  
pn  slime

-- no debconf information

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

[Diane Trout]

On Sat, 2021-12-11 at 10:48 -0800, Steve Langasek wrote:
> Package: toolz
> Version: 0.11.1-1
> Followup-For: Bug #1001488
> 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.
> 

Upstream announced 0.11.2 is supposed to be compatible with Python 3.10
and they handled anext in a different way from your patch, the tests
run on my system both at build time and in autopkgtests (amd64) with
Python 3.10

https://github.com/pytoolz/toolz/commit/da81b1e8ab96b22ed81e6414099aba066633f3ff

I'm pushed the new version which should fix this bug.

Diane

Bug#999632: marked as done (r-bioc-isoformswitchanalyzer FTBFS: ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 21:40:57 +
with message-id 
and subject line Bug#999632: fixed in r-bioc-isoformswitchanalyzer 1.16.0+ds-1
has caused the Debian Bug report #999632,
regarding r-bioc-isoformswitchanalyzer FTBFS: ERROR: dependencies ‘DRIMSeq’, 
‘tximeta’ are not available
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.)


-- 
999632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-isoformswitchanalyzer
Version: 1.14.0+ds-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/r-bioc-isoformswitchanalyzer.html
https://buildd.debian.org/status/package.php?p=r-bioc-isoformswitchanalyzer=sid

...
I: Using built-time from d/changelog: Tue, 28 Sep 2021 16:22:23 +0200
mkdir -p 
/<>/r-bioc-isoformswitchanalyzer-1.14.0\+ds/debian/r-bioc-isoformswitchanalyzer/usr/lib/R/site-library
R CMD INSTALL -l 
/<>/r-bioc-isoformswitchanalyzer-1.14.0\+ds/debian/r-bioc-isoformswitchanalyzer/usr/lib/R/site-library
 --clean . "--built-timestamp='Tue, 28 Sep 2021 16:22:23 +0200'"
ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available for package 
‘IsoformSwitchAnalyzeR’
* removing 
‘/<>/debian/r-bioc-isoformswitchanalyzer/usr/lib/R/site-library/IsoformSwitchAnalyzeR’
dh_auto_install: error: R CMD INSTALL -l 
/<>/r-bioc-isoformswitchanalyzer-1.14.0\+ds/debian/r-bioc-isoformswitchanalyzer/usr/lib/R/site-library
 --clean . "--built-timestamp='Tue, 28 Sep 2021 16:22:23 +0200'" returned exit 
code 1
make[1]: *** [debian/rules:7: override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Source: r-bioc-isoformswitchanalyzer
Source-Version: 1.16.0+ds-1
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
r-bioc-isoformswitchanalyzer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Dec 2021 02:12:12 +0530
Source: r-bioc-isoformswitchanalyzer
Architecture: source
Version: 1.16.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 999632
Changes:
 r-bioc-isoformswitchanalyzer (1.16.0+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.16.0+ds
   * d/control: Run dh-update-R
   * Add B-D on r-cran-drimseq (Closes: #999632)
Checksums-Sha1:
 8f0bf7bdbe6f55725309ac1c59bffbb5fbf43e0a 2745 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.dsc
 fb5dfceba07e144b9a05fab6e487b1d38e9e7ab1 2721968 
r-bioc-isoformswitchanalyzer_1.16.0+ds.orig.tar.xz
 0c574c627e1aa3b6665273c481d3fecf0903dd85 2660 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.debian.tar.xz
 7c66b784ff70347c4bf2132f48a7fe6a208e503e 16069 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 a533c9522d003bb10fb9bc256bc8af8a86d05ce075eecc481dcb0bc7803c426d 2745 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.dsc
 cb95e23fd7ad16194f64066a2e8f51fb37c770d67469e898ac7c6da3313bc7f7 2721968 
r-bioc-isoformswitchanalyzer_1.16.0+ds.orig.tar.xz
 70fd9be1e49ae2cacc75f416ba4081d46986171f7cad33aa0b60536d5d9a4a0f 2660 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.debian.tar.xz
 97e7fb08dc98bf68b918d51dcb9cdc6e939b63e6237697333ab4d64839edb977 16069 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1_amd64.buildinfo
Files:
 ec8c5e7824ac94ddbaf48f278aee8603 2745 gnu-r optional 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.dsc
 c874d0c40a5e4760325895828ce05347 2721968 gnu-r optional 
r-bioc-isoformswitchanalyzer_1.16.0+ds.orig.tar.xz
 8ee69de571b03a7b6dc025001c982be6 2660 gnu-r optional 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1.debian.tar.xz
 136e3c8bf8bc045f82dde51562579665 16069 gnu-r optional 
r-bioc-isoformswitchanalyzer_1.16.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmG1F9MSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nx/ZkQAI93ptR429etJaHzqGffNgQUJ/087zQZ

Bug#1001538: python-hypothesis: test failures with python3.10

[Graham Inggs]

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

Hi Maintainer

As can be seen in autopkgtests [1] and reproducible builds [2], the
tests of python-hypothesis fail when python3.10 is a supported
version.  This currently blocks the migration of python3-defaults to
testing [3].

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-hypothesis/unstable/amd64/
[2] https://tests.reproducible-builds.org/debian/rb-pkg/python-hypothesis.html
[3] https://qa.debian.org/excuses.php?package=python3-defaults


=== FAILURES ===
 test_resolves_NewType _

def test_resolves_NewType():
typ = typing.NewType("T", int)
nested = typing.NewType("NestedT", typ)
uni = typing.NewType("UnionT", typing.Optional[int])
>   assert isinstance(from_type(typ).example(), int)

tests/cover/test_lookup.py:448:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:314:
in example
example_generating_inner_function()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:302:
in example_generating_inner_function
@settings(
/usr/lib/python3/dist-packages/hypothesis/core.py:441: in
process_arguments_to_given
search_strategy.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/collections.py:39:
in do_validate
s.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:638:
in do_validate
self.mapped_strategy.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/lazy.py:118:
in do_validate
w.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:638:
in do_validate
self.mapped_strategy.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/collections.py:39:
in do_validate
s.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:377:
in validate
self.do_validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/lazy.py:118:
in do_validate
w.validate()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:378:
in validate
self.is_empty
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:125:
in accept
recur(self)
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/strategies.py:121:
in recur
mapping[strat] = getattr(strat, calculation)(recur)
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/deferred.py:80:
in calc_is_empty
return recur(self.wrapped_strategy)
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/deferred.py:43:
in wrapped_strategy
result = self.__definition()
/usr/lib/python3/dist-packages/hypothesis/strategies/_internal/core.py:1417:
in 
lambda thing: deferred(lambda: _from_type(thing)),
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

thing = tests.cover.test_lookup.T

def _from_type(thing: Type[Ex]) -> SearchStrategy[Ex]:
# TODO: We would like to move this to the top level, but
pending some major
# refactoring it's hard to do without creating circular imports.
from hypothesis.strategies._internal import types

if (
hasattr(typing, "_TypedDictMeta")
and type(thing) is typing._TypedDictMeta  # type: ignore
or hasattr(types.typing_extensions, "_TypedDictMeta")
and type(thing) is types.typing_extensions._TypedDictMeta
# type: ignore
):  # pragma: no cover
# The __optional_keys__ attribute may or may not be
present, but if there's no
# way to tell and we just have to assume that everything
is required.
# See https://github.com/python/cpython/pull/17214 for details.
optional = getattr(thing, "__optional_keys__", ())
anns = {k: from_type(v) for k, v in thing.__annotations__.items()}
return 

Processed: python-hypothesis: test failures with python3.10

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001538 [src:python-hypothesis] python-hypothesis: test failures with 
python3.10
Added indication that 1001538 affects src:python3-defaults

-- 
1001538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001538
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'

[Steve Langasek]

Package: twodict
Version: 1.2-2
Followup-For: Bug #1001489
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 twodict-1.2/debian/patches/python-3.10.patch 
twodict-1.2/debian/patches/python-3.10.patch
--- twodict-1.2/debian/patches/python-3.10.patch1969-12-31 
16:00:00.0 -0800
+++ twodict-1.2/debian/patches/python-3.10.patch2021-12-11 
10:50:51.0 -0800
@@ -0,0 +1,19 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001489
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: twodict-1.2/twodict.py
+===
+--- twodict-1.2.orig/twodict.py
 twodict-1.2/twodict.py
+@@ -6,7 +6,7 @@
+ """
+ 
+ import sys
+-import collections
++import collections.abc as collections
+ 
+ 
+ __all__ = ["TwoWayOrderedDict"]
diff -Nru twodict-1.2/debian/patches/series twodict-1.2/debian/patches/series
--- twodict-1.2/debian/patches/series   1969-12-31 16:00:00.0 -0800
+++ twodict-1.2/debian/patches/series   2021-12-11 10:49:49.0 -0800
@@ -0,0 +1 @@
+python-3.10.patch

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001489 [src:twodict] twodict: (autopkgtest) needs update for python3.10: 
'collections' has no attribute 'KeysView'
Added tag(s) patch.

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

Bug#1001535: busco: (autopkgtest) needs update for python3.10

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://gitlab.com/ezlab/busco/-/issues/513


-- 
http://fam-tille.de

Processed: Re: Bug#1001535: busco: (autopkgtest) needs update for python3.10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1001535 [src:busco] busco: (autopkgtest) needs update for python3.10
Added tag(s) upstream.
> forwarded -1 https://gitlab.com/ezlab/busco/-/issues/513
Bug #1001535 [src:busco] busco: (autopkgtest) needs update for python3.10
Set Bug forwarded-to-address to 'https://gitlab.com/ezlab/busco/-/issues/513'.

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

Processed: affects 1000716

[Debian Bug Tracking System]

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

> affects 1000716 src:supysonic
Bug #1000716 [src:ponyorm] ponyorm: FTBFS on Python 3.10
Added indication that 1000716 affects src:supysonic
> thanks
Stopping processing here.

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

Bug#1001009: Downloads external files on install

[Nilesh Patra]

Hi Tong,

On 12/12/21 1:06 AM, Tong Sun wrote:

Thank you Nilesh for such detailed explanation. Weighted on all the
options, I decided it still needs to go to contrib and have put a note
in d/README.Debian --
https://salsa.debian.org/debian/dbab/-/commit/fa771322e1342c532637e17baa863cca8ac80488


You reasoning looks okay to me, since you know the package better, I would 
simply agree.

However suggestions from my end: maybe it'd be a bit better to add the 
information about conffiles and change to contrib
in d/NEWS instead, so the user/system administrator actually sees it.
You could also trigger some script to manually remove the leftover conffiles, 
as I said on the other email, take a look here[1]
However, they are not a very high prio.

[1]: https://wiki.debian.org/DpkgConffileHandling


Now everything is updated on salsa for the final release. Please
double check, and let me know if I need to do anything else.


I made a few checks, fair enough. I just uploaded to NEW.
If at all there is something important missing, we could fix it later. Plenty 
of time :-)


Thanks a lot for all your help!


Thanks to _you_ for your work on this!

Regards,
Nilesh




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed

[Thomas Goirand]

On 12/11/21 7:15 PM, Noah Meyerhans wrote:
> On Thu, Dec 09, 2021 at 04:02:24PM +0100, Paul Gevers wrote:
>> Source: python-boto
>> Version: 2.49.0-3
>> Severity: serious
> 
> We should probably pursue the removal of this package before the
> bookworm release rather than trying to drag it forward for another
> release.  It's dead upstream in favor of the python-boto3 branch.
> 
> On sid we currently see the follow rdeps:
> root@c93c6872f764:/# grep-aptavail -w -s Package -F Depends python3-boto 
> Package: augur
> Package: debian-cloud-images-packages
> Package: python3-glance
> Package: heat-cfntools
> Package: python3-bioblend
> 
> Does anybody strongly object to this approach?
> 
> noah
> 

Speaking for those I maintain.

Looks like at least glance should be switched to boto3. I just did that,
but it FTBFS with something unrelated in tests... :(

I don't think I'd mind so much removing heat-cfntools from Debian. I'm
not sure if it's still even maintained upstream. The last release was in
2016 ... I've just asked the OpenStack mailing list.

Cheers,

Thomas Goirand (zigo)

Bug#1001535: busco: (autopkgtest) needs update for python3.10

[Graham Inggs]

Source: busco
Version: 5.2.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Hi Maintainer

As can be seen [1], the autopkgtests of busco fail when python3.10 is
a supported version.
This currently blocks the migration of python3-defaults to testing [2].

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/b/busco/unstable/amd64/
[2] https://qa.debian.org/excuses.php?package=python3-defaults


==
ERROR: test_init_tools_eukaryota_metaeuk
(tests.unittests.GenomeAnalysis_unittests.TestConfigManager)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/mock.py", line 1366, in patched
with self.decoration_helper(patched,
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
return next(self.gen)
  File "/usr/lib/python3.10/unittest/mock.py", line 1348, in decoration_helper
arg = exit_stack.enter_context(patching)
  File "/usr/lib/python3.10/contextlib.py", line 492, in enter_context
result = _cm_type.__enter__(cm)
  File "/usr/lib/python3.10/unittest/mock.py", line 1528, in __enter__
raise InvalidSpecError(
unittest.mock.InvalidSpecError: Cannot autospec attr 'config' from
target 'BuscoAnalysis' as it has already been mocked out.
[target=,
attr=]

==
ERROR: test_init_tools_prokaryota
(tests.unittests.GenomeAnalysis_unittests.TestConfigManager)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/mock.py", line 1366, in patched
with self.decoration_helper(patched,
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
return next(self.gen)
  File "/usr/lib/python3.10/unittest/mock.py", line 1348, in decoration_helper
arg = exit_stack.enter_context(patching)
  File "/usr/lib/python3.10/contextlib.py", line 492, in enter_context
result = _cm_type.__enter__(cm)
  File "/usr/lib/python3.10/unittest/mock.py", line 1528, in __enter__
raise InvalidSpecError(
unittest.mock.InvalidSpecError: Cannot autospec attr 'config' from
target 'BuscoAnalysis' as it has already been mocked out.
[target=,
attr=]

==
ERROR: test_run_analysis_metaeuk
(tests.unittests.GenomeAnalysis_unittests.TestConfigManager)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/mock.py", line 1366, in patched
with self.decoration_helper(patched,
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
return next(self.gen)
  File "/usr/lib/python3.10/unittest/mock.py", line 1348, in decoration_helper
arg = exit_stack.enter_context(patching)
  File "/usr/lib/python3.10/contextlib.py", line 492, in enter_context
result = _cm_type.__enter__(cm)
  File "/usr/lib/python3.10/unittest/mock.py", line 1528, in __enter__
raise InvalidSpecError(
unittest.mock.InvalidSpecError: Cannot autospec attr 'config' from
target 'BuscoAnalysis' as it has already been mocked out.
[target=,
attr=]

--
Ran 99 tests in 2.065s

FAILED (errors=3, skipped=1)
autopkgtest [19:49:27]: test run-unit-test: ---]
autopkgtest [19:49:28]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1

Processed: busco: (autopkgtest) needs update for python3.10

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001535 [src:busco] busco: (autopkgtest) needs update for python3.10
Added indication that 1001535 affects src:python3-defaults

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

Bug#997003: closing 997003

[Salvatore Bonaccorso]

close 997003 7.4.26-1
thanks

Processed: closing 997003

[Debian Bug Tracking System]

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

> close 997003 7.4.26-1
Bug #997003 {Done: Salvatore Bonaccorso } [src:php7.4] php: 
CVE-2021-21703
The source 'php7.4' and version '7.4.26-1' do not appear to match any binary 
packages
Marked as fixed in versions php7.4/7.4.26-1.
Bug #997003 {Done: Salvatore Bonaccorso } [src:php7.4] php: 
CVE-2021-21703
Bug 997003 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1001347: marked as done (legacy-api-wrap: autopkgtest tests for all supported python3s but fails to install them)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 19:39:53 +
with message-id 
and subject line Bug#1001347: fixed in legacy-api-wrap 1.2-3
has caused the Debian Bug report #1001347,
regarding legacy-api-wrap: 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.)


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

Source: legacy-api-wrap
Version: 1.2-2
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 
legacy-api-wrap 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
legacy-api-wrapfrom testing1.2-2
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/l/legacy-api-wrap/17376877/log.gz

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: legacy-api-wrap
Source-Version: 1.2-3
Done: Diane Trout 

We believe that the bug you reported is fixed in the latest version of
legacy-api-wrap, 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.
Diane Trout  (supplier of updated legacy-api-wrap 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: Sat, 11 Dec 2021 11:06:08 -0800
Source: legacy-api-wrap
Architecture: source
Version: 1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Diane Trout 
Closes: 1001347
Changes:
 legacy-api-wrap (1.2-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Diane Trout ]
   * python3-all to autopkgtests to make sure all supported interpreters
 are available. (Closes: #1001347), and thanks Steve Langasek for the
 simple solution.
   * Use py3versions -s instead -r as we're not using requested a set of
 interpreters.
Checksums-Sha1:
 f5b38b14f0cb0124fd7a2d3ed51e7b113dd1732c 2161 legacy-api-wrap_1.2-3.dsc
 75a9ed155e1efcc2493ea5a9494131ebf9516cb4 2428 
legacy-api-wrap_1.2-3.debian.tar.xz
 692e5a6f214b4c64f03066fffe7d3ff9b38cd6ff 6813 
legacy-api-wrap_1.2-3_amd64.buildinfo
Checksums-Sha256:
 25daaf273b112fb51e28326b0b0129e6ff8907bd626e45a8ad21598aea51a6cc 2161 
legacy-api-wrap_1.2-3.dsc
 23e1e42a955ea02ecd3b6a0fca1e9fe87da05605d217059eec06e78e81ea7e86 2428 
legacy-api-wrap_1.2-3.debian.tar.xz
 5fc8a428f84056670abd2ffe3b23070c6a35bc894cb1fe593ff0ad24dd985c44 6813 
legacy-api-wrap_1.2-3_amd64.buildinfo
Files:
 7e37066d34c6415139da8e81c7468663 2161 python optional legacy-api-wrap_1.2-3.dsc
 f37eec64a9e8906fb7c9d8ae21ad1070 2428 python optional 
legacy-api-wrap_1.2-3.debian.tar.xz
 86bd8a4dab12d034f61e4d0ebc98bb0a 6813 python optional 
legacy-api-wrap_1.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAmG099UACgkQmQ04NnM0
13DhthAArxT7qGAzqHtPGjy389r5nMfFl6fEb0NKvjYDD7KBQmHRw/7AzCNzKxA2

Bug#1001009: Downloads external files on install

[Tong Sun]

On Sat, Dec 11, 2021 at 12:39 AM Nilesh Patra wrote:

> >*from* https://wiki.debian.org/piuparts/FAQ
>
> Yeah. Or maybe try to manually upgrade in a buster chroot, and see what 
> happens.

The dbab can upgrade from oldstable (Buster) just fine, but I had some problem
removing the outdated conffile files, as we had discussed in the other
thread. So,

As I know that the people that will be upgrading from buster can be
counted using a single hand, so I decided to put a note in
d/README.Debian instead. See
https://salsa.debian.org/debian/dbab/-/commit/a8fe8295cafa7506ad87b7f8a726325d45a3a335

> On Fri, Dec 10, 2021 at 05:05:03PM -0500, Tong Sun wrote:
> > 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.
>
> OK, it looks like because of this line:
>
> https://salsa.debian.org/debian/dbab/-/blob/master/bin/dbab-get-list#L21
>
> It tries to curl something. Now, two questions+suggestions.
>
> Agreeing with wrar on this point 1:
> 1. Is the data non-free?
>- If so, is it a hard requirement to download that data for package to 
> function?
>   Can sys admins not manually get this?
>   -> If it is a hard-bound need, then it should be moved to contrib
>   -> If not a hard-bound need, just mention downloading this in d/NEWS to 
> inform the sys admin.
>  This was it can continue to stay in free section (major benefit)
>
> * Is the data free software?
>- If so, is it a hard-bound/necessary need?
>  -> Now, if so, you can do something like this:
>  instead of pulling it in postinst, you could download it locally, 
> and put it in, say
>  a debian/resources directory, Simply install it to the needed 
> locations with a d/install.
>  This could serve as an example for you[1]. Only demerit is that you 
> might need to update
>  it when you do a new version, but it gives the benfit of keeping it 
> in main rather than contrib.
>  -> If not, same thingy, add a d/NEWS and ask sys admin.
>
> [1]: 
> https://salsa.debian.org/go-team/packages/golang-mvdan-editorconfig/-/commit/edf2d06b904bc45296080bed4acf2631dc2e9ece
>
> So, in a nutshell if the data is non-free and it is needed for the package to 
> function, we need to go ahead with contrib.
> Otherwise there are workarounds. Please let me know if that's the case, and 
> it really needs to go to contrib?

Thank you Nilesh for such detailed explanation. Weighted on all the
options, I decided it still needs to go to contrib and have put a note
in d/README.Debian --
https://salsa.debian.org/debian/dbab/-/commit/fa771322e1342c532637e17baa863cca8ac80488

copied below:

--

Moving to contrib
=

dbab moving to contrib is because of the Bug#1001009, first spotted by wrar
then consented by nilesh, as it needs to download external files in postinst,
which is not fit for main.

The data is free software, however it's a living and breathing one, thus using
a local copy (in package) means that

- it will almost always be outdated, and
- it will complicate the simple program & solution, and
- it will make the core content more than doubled in size (9828 + 130499)

The problem is initially spotted in 1.5.7-1 and get fixed in 1.5.7-2. Only
changing to contrib section is made in d/control file, nothing else is
changed, and the program behaves exactly as before.

--

Now everything is updated on salsa for the final release. Please
double check, and let me know if I need to do anything else.

Thanks a lot for all your help!

Processed: Re: astroscrappy: autopkgtest regression on armhf

[Debian Bug Tracking System]

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

> forwarded 1001491 https://github.com/astropy/astroscrappy/issues/71
Bug #1001491 [src:astroscrappy] astroscrappy: autopkgtest regression on armhf
Set Bug forwarded-to-address to 
'https://github.com/astropy/astroscrappy/issues/71'.
> thanks
Stopping processing here.

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

Bug#1001491: astroscrappy: autopkgtest regression on armhf

[Ole Streicher]

forwarded 1001491 https://github.com/astropy/astroscrappy/issues/71
thanks

On 10.12.21 22:06, Paul Gevers wrote:

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:


    pass    fail
astroscrappy   from testing    1.1.0-1
all others from testing    from 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

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

[Markus Koschany]

Am Samstag, dem 11.12.2021 um 10:52 -0800 schrieb tony mancill:
> On Fri, Dec 10, 2021 at 10:42:24PM +0100, Markus Koschany wrote:
> > Control: owner -1 !
> > 
> > I am currently investigating the fix for CVE-2021-44228.
> 
> Hi Markus,
> 
> Thank you both for the quick turn-around on this and for claiming
> ownership of the bug in the BTS.  I had started looking at the update
> and appreciate that we were able to avoid duplication of effort.
> 
> Cheers,
> tony

Hi tony,

sure, anytime. The fix for Bullseye and Buster will be released shortly.

Cheers,

Markus




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

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

[tony mancill]

On Fri, Dec 10, 2021 at 10:42:24PM +0100, Markus Koschany wrote:
> Control: owner -1 !
> 
> I am currently investigating the fix for CVE-2021-44228.

Hi Markus,

Thank you both for the quick turn-around on this and for claiming
ownership of the bug in the BTS.  I had started looking at the update
and appreciate that we were able to avoid duplication of effort.

Cheers,
tony


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001488 [src:toolz] toolz: (autopkgtest) needs update for python3.10: 
Missing introspection for the following callables
Added tag(s) patch.

-- 
1001488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001488
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

[Steve Langasek]

Package: toolz
Version: 0.11.1-1
Followup-For: Bug #1001488
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 toolz-0.11.1/debian/patches/python-3.10.patch 
toolz-0.11.1/debian/patches/python-3.10.patch
--- toolz-0.11.1/debian/patches/python-3.10.patch   1969-12-31 
16:00:00.0 -0800
+++ toolz-0.11.1/debian/patches/python-3.10.patch   2021-12-11 
10:47:23.0 -0800
@@ -0,0 +1,18 @@
+Description: compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001488
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: toolz-0.11.1/toolz/tests/test_inspect_args.py
+===
+--- toolz-0.11.1.orig/toolz/tests/test_inspect_args.py
 toolz-0.11.1/toolz/tests/test_inspect_args.py
+@@ -396,6 +396,7 @@
+ add_blacklist(builtins, 'NoneType')
+ add_blacklist(builtins, '__metaclass__')
+ add_blacklist(builtins, 'sequenceiterator')
++add_blacklist(builtins, 'anext')
+ 
+ def is_missing(modname, name, func):
+ if name.startswith('_') and not name.startswith('__'):
diff -Nru toolz-0.11.1/debian/patches/series toolz-0.11.1/debian/patches/series
--- toolz-0.11.1/debian/patches/series  1969-12-31 16:00:00.0 -0800
+++ toolz-0.11.1/debian/patches/series  2021-12-11 10:45:46.0 -0800
@@ -0,0 +1 @@
+python-3.10.patch

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

[Steve Langasek]

Package: sortedcollections
Version: 1.0.1-1
Followup-For: Bug #1001486
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 sortedcollections-1.0.1/debian/patches/python-3.10.patch 
sortedcollections-1.0.1/debian/patches/python-3.10.patch
--- sortedcollections-1.0.1/debian/patches/python-3.10.patch1969-12-31 
16:00:00.0 -0800
+++ sortedcollections-1.0.1/debian/patches/python-3.10.patch2021-12-11 
10:38:43.0 -0800
@@ -0,0 +1,32 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001486
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: sortedcollections-1.0.1/sortedcollections/recipes.py
+===
+--- sortedcollections-1.0.1.orig/sortedcollections/recipes.py
 sortedcollections-1.0.1/sortedcollections/recipes.py
+@@ -2,7 +2,7 @@
+ 
+ """
+ 
+-import collections as co
++import collections.abc as co
+ from itertools import count
+ from sortedcontainers import SortedKeyList, SortedDict, SortedSet
+ from sortedcontainers.sortedlist import recursive_repr
+Index: sortedcollections-1.0.1/sortedcollections/ordereddict.py
+===
+--- sortedcollections-1.0.1.orig/sortedcollections/ordereddict.py
 sortedcollections-1.0.1/sortedcollections/ordereddict.py
+@@ -2,7 +2,7 @@
+ 
+ """
+ 
+-import collections as co
++import collections.abc as co
+ from itertools import count
+ from operator import eq
+ import sys
diff -Nru sortedcollections-1.0.1/debian/patches/series 
sortedcollections-1.0.1/debian/patches/series
--- sortedcollections-1.0.1/debian/patches/series   2018-06-18 
14:09:16.0 -0700
+++ sortedcollections-1.0.1/debian/patches/series   2021-12-11 
10:37:49.0 -0800
@@ -1,2 +1,3 @@
 0001-Remove-Google-analytics-account-ID.patch
 0002-remove-github-buttons.patch
+python-3.10.patch

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001486 [src:sortedcollections] sortedcollections: (autopkgtest) needs 
update for python3.10: 'collections' has no attribute 'MutableSet'
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001485 [src:shellingham] shellingham: autopkgtest tests all supported 
python3 versions but doesn't ensure they are installed
Added tag(s) patch.

-- 
1001485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001485
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

[Steve Langasek]

Package: shellingham
Followup-For: Bug #1001485
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 shellingham-1.3.2/debian/tests/control 
shellingham-1.3.2/debian/tests/control
--- shellingham-1.3.2/debian/tests/control  2021-01-15 06:55:19.0 
-0800
+++ shellingham-1.3.2/debian/tests/control  2021-12-11 10:28:56.0 
-0800
@@ -1,3 +1,3 @@
 Tests: testsuite
-Depends: python3-pytest, python3-pytest-mock, @
+Depends: python3-pytest, python3-pytest-mock, python3-all, @
 Restrictions: allow-stderr

Bug#995452: libpam-ssh breaks the agent-forwarding of normal ssh

[Jerome BENOIT]

On Mon, 29 Nov 2021 11:19:36 +0100 Jerome BENOIT  wrote:

Thanks for sharing your file.
I will have a closer look soon,
Cheers,
Jerome


ping,
cheers,
Jerome

--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



OpenPGP_signature
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #1001490 [src:vorta] vorta: (autopkgtest) needs update for python3.10: 
Segmentation fault
Added tag(s) help.

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

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

[Nicholas D Steeves]

Control: tag -1 help

Dear DPT,

With the timing of the Python 3.10 migration+holidays, I won't be able
to resolve this bug in a timely manner.  I've contacted upstream about
their recommended resolution, and they recommend switching to the 0.8.x
series at this time--so I merged my experimental branch to master,
because this RC bug justifies switching to 0.8.2 without delay.

The reason that I'm asking for help is because 0.8.2 currently FTBFS and
as far as I can tell it will not be possible for me to make time before
2022.  If waiting is acceptable then I'll resume work then, but if not,
assistance would be sincerely appreciated.

Regards,
Nicholas


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

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

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

[Steve Langasek]

Package: scoop
Version: 0.7.1.1-7
Followup-For: Bug #1001483
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch

Please find attached a trivial patch for this bug.

-- 
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 scoop-0.7.1.1/debian/patches/python-3.10.patch 
scoop-0.7.1.1/debian/patches/python-3.10.patch
--- scoop-0.7.1.1/debian/patches/python-3.10.patch  1969-12-31 
16:00:00.0 -0800
+++ scoop-0.7.1.1/debian/patches/python-3.10.patch  2021-12-11 
10:14:53.0 -0800
@@ -0,0 +1,20 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001483
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: scoop-0.7.1.1/scoop/futures.py
+===
+--- scoop-0.7.1.1.orig/scoop/futures.py
 scoop-0.7.1.1/scoop/futures.py
+@@ -16,7 +16,8 @@
+ #
+ import os
+ from inspect import ismethod
+-from collections import namedtuple, Iterable
++from collections import namedtuple
++from collections.abc import Iterable
+ from functools import partial, reduce
+ import itertools
+ import copy
diff -Nru scoop-0.7.1.1/debian/patches/series 
scoop-0.7.1.1/debian/patches/series
--- scoop-0.7.1.1/debian/patches/series 2020-04-21 10:05:49.0 -0700
+++ scoop-0.7.1.1/debian/patches/series 2021-12-11 10:13:39.0 -0800
@@ -4,3 +4,4 @@
 sphinx.ext.pngmath.patch
 Call-wait-on-killed-child-processes.patch
 Adapt-conf.py-for-sphinx-2.0.patch
+python-3.10.patch

Bug#1001524: marked as done (calcium needs a source-only upload for testing migration)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 18:18:42 +
with message-id 
and subject line Bug#1001524: fixed in calcium 0.4.1-2
has caused the Debian Bug report #1001524,
regarding calcium needs a source-only upload for testing migration
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.)


-- 
1001524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calcium
Version: 0.4.1-1
Severity: serious

https://tracker.debian.org/pkg/calcium

Migration status for calcium (- to 0.4.1-1): BLOCKED: Rejected/violates 
migration policy/introduces a regression
Issues preventing migration:
Not built on buildd: arch amd64 binaries uploaded by julien.pu...@laposte.net
Not built on buildd: arch all binaries uploaded by julien.pu...@laposte.net, a 
ew source-only upload is needed to allow migration
--- End Message ---
--- Begin Message ---
Source: calcium
Source-Version: 0.4.1-2
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
calcium, 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 calcium 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: Sat, 11 Dec 2021 18:56:03 +0100
Source: calcium
Architecture: source
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Julien Puydt 
Closes: 1001524
Changes:
 calcium (0.4.1-2) unstable; urgency=medium
 .
   * Move to the math team.
   * Upload source-only to unstable. (Closes: #1001524)
Checksums-Sha1:
 d1350efa20223550c8ecf7a7724daa397a01cdf0 2120 calcium_0.4.1-2.dsc
 164d8f3aab9d843f23876224a1c9f932262f0823 3544 calcium_0.4.1-2.debian.tar.xz
 152b25c39b50a6f1a69fc346612be82741fe42f0 8203 calcium_0.4.1-2_source.buildinfo
Checksums-Sha256:
 373cb93a532cc7b32c4b725f985086735ad601472bd878ad77e3ef2983f324b0 2120 
calcium_0.4.1-2.dsc
 237bafd46431ac389e7a8b46bfbe8cecb4656a1d88fb10a2eb903ef2f9150e96 3544 
calcium_0.4.1-2.debian.tar.xz
 8d6c374069700f52b6b03fb8684f0fa141c83f837608f0769f8aeff03976f05c 8203 
calcium_0.4.1-2_source.buildinfo
Files:
 430e6e6aee8c7514abbd705a6b94cede 2120 math optional calcium_0.4.1-2.dsc
 63412916d7cf269bad43fa81ca6064bb 3544 math optional 
calcium_0.4.1-2.debian.tar.xz
 b34edb2283732b62ebfdd8895acce09a 8203 math optional 
calcium_0.4.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmG05pESHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVR9agP/A+Jwp45iiI9CvHyMLQkl1hBmmNU+TFu
eIF7achTjkILbIwdX1OnClXtfsBoNANkpJZ6axU7nXzffCXZACq0LfKdzxtVG7zT
KEPZHNzvDjIyxRo5R/XpoVJXX2E0qcN3tmDF1Z0q3cCHcJprXug+Yq3r8CLJLap/
kQOElJQn76Yjlr/lvXA14dMbc0HvncSHeWOTzxQnTOCqjH1AahWdKWKQomcaMtRM
wzl3bL91vZjSE6Mp4Ik2yiOlhaSgMzi5yQtQec/35+oeGPRE8ldfpnqoYei6+Yk1
nAQKGUzG4uhvY/EcP8zidscECdSQXV6B8xQ4rxfxyk+V8GbAZ/hJo0k55QgZ7wX4
Dy6l6U/eSvHP1ZdzBH9NGHUxG9nv0TRiGtDuXFzyDzMYSLEfSlkAm371bh1ByrWZ
D8VUSxlCVOWhfaipHt1/HJOOQIMiMdLpy+LSoAJF0pJSpAr6Pzge53QyWsFt+NeV
UVx9kwNDEF/kNsdqCOSM5Nw4DXQLiaEj/UsgWnuBsrYV1kOCBxKQYC3e3hA0F0ZE
sftqE71izgwJe7tkbvU6wAogrlivP9kw2ODDaVZ0pjFQNLrJmbxl2LzWAG/yKFVj
mw4KrGg/434zJ5nedciwdIDwXX2YnBLDvFGH9LYtGpta5tpV5esWXcgxStM705+E
sqeFP+oASZOg
=Ywyi
-END PGP SIGNATURE End Message ---

Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed

[Noah Meyerhans]

On Thu, Dec 09, 2021 at 04:02:24PM +0100, Paul Gevers wrote:
> Source: python-boto
> Version: 2.49.0-3
> Severity: serious

We should probably pursue the removal of this package before the
bookworm release rather than trying to drag it forward for another
release.  It's dead upstream in favor of the python-boto3 branch.

On sid we currently see the follow rdeps:
root@c93c6872f764:/# grep-aptavail -w -s Package -F Depends python3-boto 
Package: augur
Package: debian-cloud-images-packages
Package: python3-glance
Package: heat-cfntools
Package: python3-bioblend

Does anybody strongly object to this approach?

noah

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

[Steve Langasek]

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

Hello,

Attached is a small patch to ignore the stderr noise about deprecation
warnings and allow the autopkgtests to continue to pass.

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 restrictedpython-4.0~b3/debian/tests/control 
restrictedpython-4.0~b3/debian/tests/control
--- restrictedpython-4.0~b3/debian/tests/control2018-09-24 
05:50:04.0 -0700
+++ restrictedpython-4.0~b3/debian/tests/control2021-12-11 
10:10:24.0 -0800
@@ -1,2 +1,3 @@
 Tests: all
 Depends: @, python3-distutils, python3-zope.testrunner, python3-all
+Restrictions: allow-stderr

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001482 [src:restrictedpython] restrictedpython: (autopkgtest) needs 
update for python3.10: deprecation warning on stderr
Added tag(s) patch.

-- 
1001482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001482
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

[Steve Langasek]

Package: python-validictory
Followup-For: Bug #1001480
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 python-validictory-1.1.2/debian/patches/python-3.10.patch 
python-validictory-1.1.2/debian/patches/python-3.10.patch
--- python-validictory-1.1.2/debian/patches/python-3.10.patch   1969-12-31 
16:00:00.0 -0800
+++ python-validictory-1.1.2/debian/patches/python-3.10.patch   2021-12-11 
10:05:22.0 -0800
@@ -0,0 +1,18 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: python-validictory-1.1.2/validictory/validator.py
+===
+--- python-validictory-1.1.2.orig/validictory/validator.py
 python-validictory-1.1.2/validictory/validator.py
+@@ -4,7 +4,7 @@
+ import socket
+ from datetime import datetime
+ from decimal import Decimal
+-from collections import Mapping, Container
++from collections.abc import Mapping, Container
+ 
+ if sys.version_info[0] == 3:
+ _str_type = str
diff -Nru python-validictory-1.1.2/debian/patches/series 
python-validictory-1.1.2/debian/patches/series
--- python-validictory-1.1.2/debian/patches/series  1969-12-31 
16:00:00.0 -0800
+++ python-validictory-1.1.2/debian/patches/series  2021-12-11 
10:04:27.0 -0800
@@ -0,0 +1 @@
+python-3.10.patch

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

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: usertag python3.10 bugs

[Debian Bug Tracking System]

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

> severity 999781 serious
Bug #999781 [pythonmagick] pythonmagick: Misbuild when multiple supported 
python versions present
Severity set to 'serious' from 'important'
> severity 999806 serious
Bug #999806 [pygattlib] pygattlib: Misbuild with multiple supported python 
versions
Severity set to 'serious' from 'normal'
> tags 999781 + ftbfs
Bug #999781 [pythonmagick] pythonmagick: Misbuild when multiple supported 
python versions present
Added tag(s) ftbfs.
> tags 999806 + ftbfs
Bug #999806 [pygattlib] pygattlib: Misbuild with multiple supported python 
versions
Added tag(s) ftbfs.
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was gin...@debian.org).
> usertag 999781 + python3.10 python3-all-dev
There were no usertags set.
Usertags are now: python3-all-dev python3.10.
> usertag 999806 + python3.10 python3-all-dev
There were no usertags set.
Usertags are now: python3-all-dev python3.10.
> usertag 1001500 + python3.10
There were no usertags set.
Usertags are now: python3.10.
> thanks
Stopping processing here.

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

Processed: Re: python-pyknon: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableSequence'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1001428 [src:python-pyknon] python-pyknon: (autopkgtest) needs update for 
python3.10: module 'collections' has no attribute 'MutableSequence'
Added tag(s) patch.

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

Bug#1001428: python-pyknon: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableSequence'

[Steve Langasek]

Package: python-pyknon
Version: 1.2-3
Followup-For: Bug #1001428
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 python-pyknon-1.2/debian/patches/python-3.10.patch 
python-pyknon-1.2/debian/patches/python-3.10.patch
--- python-pyknon-1.2/debian/patches/python-3.10.patch  1969-12-31 
16:00:00.0 -0800
+++ python-pyknon-1.2/debian/patches/python-3.10.patch  2021-12-11 
09:59:59.0 -0800
@@ -0,0 +1,16 @@
+Description: Compatibility with python 3.10
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1001428
+Last-Update: 2021-12-11
+Forwarded: no
+
+Index: python-pyknon-1.2/pyknon/music.py
+===
+--- python-pyknon-1.2.orig/pyknon/music.py
 python-pyknon-1.2/pyknon/music.py
+@@ -1,4 +1,4 @@
+-import collections
++import collections.abc as collections
+ import copy
+ from pyknon import notation
+ 
diff -Nru python-pyknon-1.2/debian/patches/series 
python-pyknon-1.2/debian/patches/series
--- python-pyknon-1.2/debian/patches/series 2020-01-20 04:49:49.0 
-0800
+++ python-pyknon-1.2/debian/patches/series 2021-12-11 09:59:00.0 
-0800
@@ -1 +1,2 @@
 remove_pngmath.diff
+python-3.10.patch

Bug#999606: marked as done (fetchmail: configuration requires TLS for SSH authentication)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 17:48:42 +
with message-id 
and subject line Bug#999606: fixed in fetchmail 6.4.25-1
has caused the Debian Bug report #999606,
regarding fetchmail: configuration requires TLS for SSH authentication
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.)


-- 
999606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fetchmail
Version: 6.4.22-1
Severity: serious

Hi,

With version 6.4.22-1 and 6.4.23-1 I get the following error:
configuration requires TLS, but STARTTLS is not permitted because of 
authenticated state (PREAUTH). Aborting connection.  Server permitting, try 
--ssl instead (see manual).

But I'm using ssh authentication (auth ssh), and using the plugin
command I'm remotely start the imap server (doveadm exec imap).
The imap server does not require authentication. As far as fetchmail
is concerned, it should not talk SSL/SSH, or do any authentication,
it's all done externally.

This worked until version 6.4.21-1.


Kurt
--- End Message ---
--- Begin Message ---
Source: fetchmail
Source-Version: 6.4.25-1
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fetchmail 
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: Sat, 11 Dec 2021 16:41:33 +0100
Source: fetchmail
Architecture: source
Version: 6.4.25-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 981464 999606
Changes:
 fetchmail (6.4.25-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add user systemd unit configuration file (closes: #981464).
   * Document upstream ssh authentication change due to CVE-2021-39272 fix
 (closes: #999606).
Checksums-Sha1:
 01ad1e7019c451bcc2ddd14d92493ca453cf7dc4 2175 fetchmail_6.4.25-1.dsc
 5873e59292f91c5f4a7b980cfded1124d139b9c1 1343360 fetchmail_6.4.25.orig.tar.xz
 96aee2a2b94ef738038e9bc0b19526d522f076be 833 fetchmail_6.4.25.orig.tar.xz.asc
 03fb54b45187dce5ed28f4df072db62b83e3331c 54984 fetchmail_6.4.25-1.debian.tar.xz
Checksums-Sha256:
 2ee5e26f2a52f9cd58dd7f4aaecc6322fea608ab66e77a417849bf53938c0a58 2175 
fetchmail_6.4.25-1.dsc
 7ebefbe89172fd59f0fd8317d8743a8436f375ccdcab3900e4c3ec06a8fbf27f 1343360 
fetchmail_6.4.25.orig.tar.xz
 6b214b8633a8bc043e33e336d0e372247f1b9a4cbe3aeeed8c787e1ab6b44a56 833 
fetchmail_6.4.25.orig.tar.xz.asc
 fe155a9eea3afb3dfba91ab6afe953b8c749d068562b86fb3ba98f7184c087ef 54984 
fetchmail_6.4.25-1.debian.tar.xz
Files:
 5eef661f278155860071567497eaa643 2175 mail optional fetchmail_6.4.25-1.dsc
 4ad354bdaaecb7b2564e4e2d070d0f50 1343360 mail optional 
fetchmail_6.4.25.orig.tar.xz
 2695e1e6576ba595668940352b778ea6 833 mail optional 
fetchmail_6.4.25.orig.tar.xz.asc
 fa0a5e82a7d605035b4991be0650d830 54984 mail optional 
fetchmail_6.4.25-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmG03ygACgkQ3OMQ54ZM
yL/+6xAAqSsGe7uawCs+MDuORBCTmG7faAq5C3kLWaavvPaFGkMmasXn8ydnEEF6
1k9gCiyc2nhV+stkxnDcJF6auqn8kOVIzqfa83l1VhwMpqpYp+IggARmP7oH+qxQ
EIQt8gfY8V2vLgXayE0mkXc47kGAYOFl8sAW+gROiDDZUdQNIl+x/NrMJ7w8L8Vz
kZz0UNBnQ0jVHA9jrGKQSk9iAn9AXfNDQdprJs/ep8o+ioHXPt+4pOZ4mj7l4LDj
lxRefTmYwWbMP7892/0kmgQvOSZFx57CSiJqWChx7v+YpEXtgr8tIOQWSG09H1bI
2PUrkq98la8jTDyGLDyiQy+qKE/xmVw9MGNvyG1XKUCvcnnLkFGETpcBmAYmj/Ha
t2ZF9+X7fPXXsSgdZn5KkjeYUzi5Twuvo1JbtjFFbqerj2aRYXmprVRVlX6iBpMZ
okftEi7sbnsxYGjrA/yeaBg8wLC1pNUhfcTtE/sR1aRnBntFiDA/XOwtv3JtFTXu
t6dBgon7N+CFErgDZCHCzjo4iOwmNnXPYOeC76NPcjrpzbzGQuj7KWMR8s3tY0dm
rWoJt0Kp5NwevrppgSJalyDvEKjKCBlGaNPFhsJVuYNRjapWm3Mt2Qku8+t5WFn8
eMw2ohxYGsgEOZYj2JWHz0wZMd2rsTRy6kPOoTi3R8qrTFXcO+E=
=WJd5
-END PGP SIGNATURE End Message ---

Bug#1001528: FTBFS with eigen3/3.4.0

[Ole Streicher]

Control: forwarded -1 https://github.com/astro-informatics/purify/issues/290

I am afraid that I am unable to fix this: the Debian version of purify 
uses a patched version of Eigen3, and since the patch still succeeds 
(with some offsets) I assume that it is not applied upstream yet.


There is a newer upstream version 3.0.1 of purify (which doesn't require 
the patch); however this doesn't compile for me as well -- with the same 
error as you see now. There are other compilation errors which I saw 
with earlier versions of purify.


These errors were reported upstream already two years ago in

https://github.com/astro-informatics/purify/issues/290

and I also reported some test failures; however without response. The 
last commit in the repository was on May 2021.


Unless the communication with upstream improves, we probably don't get 
this fixed (except you have an idea yourself).


Best

Ole

Processed: Re: Bug#1001528: FTBFS with eigen3/3.4.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/astro-informatics/purify/issues/290
Bug #1001528 [src:purify] FTBFS with eigen3/3.4.0
Set Bug forwarded-to-address to 
'https://github.com/astro-informatics/purify/issues/290'.

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

Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

[Arnaldo Pirrone]

I just learned about pipewire and love it.

By following this I was able to work around this
https://wiki.debian.org/PipeWire#For_JACK

May this issue report help in getting a jackd2 install that works right
away for the future releases. (Not sure if that's already true on a clean
install)

Il ven 3 dic 2021, 13:00 Cráudio  ha scritto:

> 08:57:37.986 Reiniciar estatísticas.
> 08:57:38.009 Alteração de conexão ALSA.
> Cannot connect to server socket err = Arquivo ou diretório inexistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> 08:57:38.044 Alteração no gráfico de conexão ALSA.
> 08:57:44.807 JACK está iniciando...
> 08:57:44.808 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -Xseq
> Cannot connect to server socket err = Arquivo ou diretório inexistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> 08:57:44.829 JACK inicializou com PID=2198.
> no message buffer overruns
> no message buffer overruns
> no message buffer overruns
> jackdmp 1.9.19
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2016 Grame.
> Copyright 2016-2021 Filipe Coelho.
> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> audio_reservation_init
> Device reservation request with priority 2147483647 denied for "Audio0":
> org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not
> implemented on interface org.freedesktop.ReserveDevice1)
> Failed to acquire device name : Audio0 error : Method RequestRelease is
> not implemented on interface org.freedesktop.ReserveDevice1
> Audio device hw:0 cannot be acquired...
> Cannot initialize driver
> JackServer::Open failed with -1
> Failed to open server
> 08:57:44.964 JACK foi parado
> 08:57:46.923 Não foi possível conectar-se ao servidor JACK como cliente. -
> Operação global falhou. - Não foi possível conectar-se ao servidor. Por
> favor, verifique a janela de mensagens para mais informações.
> Cannot connect to server socket err = Arquivo ou diretório inexistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> Em sexta-feira, 3 de dezembro de 2021 às 08:51, Cráudio <
> claudio...@protonmail.com> escreveu:
>
> I have the same problem!
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> Em sábado, 27 de novembro de 2021 às 18:14, Arnaldo Pirrone <
> it9...@gmail.com> escreveu:
>
> I guess so, I have both pipewire and pipewire-pulse in the output of ps
> Altgough I have no idea what that is for
>
> Il lun 22 nov 2021, 11:50 Sebastian Ramacher  ha
> scritto:
>
>> Control: tags -1 moreinfo
>>
>> On 2021-11-21 00:55:50, Arnaldo Pirrone wrote:
>> > Package: jackd2
>> > Version: 1.9.19~dfsg-2
>> > Severity: grave
>> > X-Debbugs-Cc: it9...@gmail.com
>> >
>> > Apparently there is something wrong with Jack and dbus.
>> > Also reported here:
>> >
>> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/
>> > Find below the jack server logs.
>> >
>> > 00:41:32.228 Resetta le statistiche.
>> > 00:41:32.269 Connessioni di ALSA cambiate.
>> > 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka
>> jackdbus).
>> > Cannot connect to server socket err = File o directory non esistente
>> > Cannot connect to server request channel
>> > jack server is not running or cannot be started
>> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping
>> > unlock
>> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping
>> > unlock
>> > 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA.
>> > 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace
>> > Sun Nov 21 00:41:47 2021: Starting jack server...
>> > Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with
>> priority
>> > 10
>> > Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self
>> connect
>> > requests"
>> > Cannot connect to server socket err = File o directory non esistente
>> > Cannot connect to server request channel
>> > jack server 

Bug#1001290: marked as done (convertdate: autopkgtest tests for all supported python3s but fails to install them)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 16:18:35 +
with message-id 
and subject line Bug#1001290: fixed in convertdate 2.3.2-2
has caused the Debian Bug report #1001290,
regarding convertdate: 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.)


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

Source: convertdate
Version: 2.3.2-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 convertdate 
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
convertdatefrom testing2.3.2-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.


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/c/convertdate/17344289/log.gz

+ cp -r tests/ /tmp/autopkgtest-lxc.9wwlakm4/downtmp/autopkgtest_tmp
+ cd /tmp/autopkgtest-lxc.9wwlakm4/downtmp/autopkgtest_tmp/
+ export PYTHONWARNINGS=d
+ py3versions -s
+ echo --
+ echo Testing with python3.10
+ echo --
+ LC_ALL=C python3.10 -m unittest discover --verbose
/tmp/autopkgtest-lxc.9wwlakm4/downtmp/build.aU4/src/debian/tests/python3-unittest: 
11: python3.10: not found

--
Testing with python3.10
--
autopkgtest [20:13:28]: test python3-unittest



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: convertdate
Source-Version: 2.3.2-2
Done: Håvard Flaget Aasen 

We believe that the bug you reported is fixed in the latest version of
convertdate, 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.
Håvard Flaget Aasen  (supplier of updated convertdate 
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: Sat, 11 Dec 2021 16:04:27 +
Source: convertdate
Architecture: source
Version: 2.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Håvard Flaget Aasen 
Closes: 1001290
Changes:
 convertdate (2.3.2-2) unstable; urgency=medium
 .
   * Team upload.
   * autopkgtest: Add python3-all as dependency. Closes: #1001290
   * autopkgtest: Mark d/tests/python3-unittest as executable.
   * d/watch:
 - Update to version 4.
 - Point URL to GitHub, which includes unittests. Current version
   is also downloaded from GitHub.
   * Bump debhelper to version 13.
   * d/changelog: remove trailing whitespace.
   * Add upstream metadata file with fields: Bug-Database, Bug-Submit,
 Repository and Repository-Browse.
   * Document Rules-Requires-Root
   * Convert first letter to lower case and remove punctuation
 in short description
   * Remove fields Recommends and Suggests from binary package, not used.
   * Update Standards-Version to 4.6.0.
   * Enable salsa CI.
   * Renamed repository, to match source name.
Checksums-Sha1:
 4acb7ddda79120c2a449972a242495d32e7493de 2094 convertdate_2.3.2-2.dsc
 e2a800bbc4944b598339fdcdfad9437259b6f096 3340 convertdate_2.3.2-2.debian.tar.xz
 

Processed: your mail

[Debian Bug Tracking System]

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

> # We need to fix some stuff here in the bug because
> # of some nasty formatting done by Thunderbird.
> # Let's start with the severity.
> severity 1001498 grave
Bug #1001498 [src:xca] No OpenSSL 3.0 support in XCA 2.3.0 and later
Severity set to 'grave' from 'normal'
> # This affects 2.3.0-1 which is in Experimental and Unstable
> found 1001498 2.3.0-1
Bug #1001498 [src:xca] No OpenSSL 3.0 support in XCA 2.3.0 and later
Marked as found in versions xca/2.3.0-1.
> # This was forwarded to upstream
> forwarded 1001498 https://github.com/chris2511/xca/issues/320
Bug #1001498 [src:xca] No OpenSSL 3.0 support in XCA 2.3.0 and later
Set Bug forwarded-to-address to 'https://github.com/chris2511/xca/issues/320'.
> # And some tags - it's an upstream code problem,
> # it's an FTBFS problem, but it only affects experimental
> # due to OpenSSL 3.0 only being in Experimental right now.
> tags 1001498 + upstream ftbfs experimental
Bug #1001498 [src:xca] No OpenSSL 3.0 support in XCA 2.3.0 and later
Added tag(s) ftbfs, upstream, and experimental.
> # And now we're done!
> thanks
Stopping processing here.

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

Bug#1001528: FTBFS with eigen3/3.4.0

[Shengjing Zhu]

Source: purify
Version: 2.0.0-6
Severity: serious
X-Debbugs-Cc: z...@debian.org
Control: affects -1 src:eigen3

Hi,

When rebuild this package in unstable, I find it FTBFS.
Please see the log at:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/purify_2.0.0-6.rbuild.log.gz

/build/1st/purify-2.0.0/cpp/purify/kernels.cc:152:55: error: no match for 
'operator=' (operand types are 'Eigen::internal::enable_if, double, 
Eigen::internal::SingleRange> >::type' {aka 
'Eigen::IndexedView, double, 
Eigen::internal::SingleRange>'} and 'double')
  152 | samples(i) = kernelu(i / total_samples * J - J / 2);
  |   ^
In file included from /build/1st/purify-2.0.0/eigen3/Eigen/Core:273,
 from /build/1st/purify-2.0.0/cpp/purify/types.h:6,
 from /build/1st/purify-2.0.0/cpp/purify/kernels.h:8,
 from /build/1st/purify-2.0.0/cpp/purify/kernels.cc:2:


I believe this is caused by eigen3/3.4.0-1 in unstable.

Processed: FTBFS with eigen3/3.4.0

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:eigen3
Bug #1001528 [src:purify] FTBFS with eigen3/3.4.0
Added indication that 1001528 affects src:eigen3

-- 
1001528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001528
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'

[Andreas Tille]

Am Sat, Dec 11, 2021 at 02:33:40PM +0530 schrieb Nilesh Patra:
> On 12/11/21 12:14 PM, Nilesh Patra wrote:
> > Tests are still failing, see here[1]. It is not a problem of terra version, 
> > as it seems, it is installed in the
> > way pretty much every other package is. I face the same stuff locally as 
> > well now.
> > Would you have some other fix in mind?
> 
> When I try running tests as root, the error vanishes. I have no idea what's 
> up :(

Well, root has write permissions to /usr.  I'd suggest to check the md5 sum
of the files of the package after running the test as root.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#997939: marked as done (giara FTBFS with meson 0.60.0: meson.build:10:11: ERROR: stdlib is not a valid path name)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 15:19:18 +
with message-id 
and subject line Bug#997939: fixed in giara 0.3-3
has caused the Debian Bug report #997939,
regarding giara FTBFS with meson 0.60.0: meson.build:10:11: ERROR: stdlib is 
not a valid path name
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.)


-- 
997939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giara
Version: 0.3-2
Severity: serious
Tags: ftbfs bookworm sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/giara.html

...
../data/ui/meson.build:10:11: ERROR: stdlib is not a valid path name
--- End Message ---
--- Begin Message ---
Source: giara
Source-Version: 0.3-3
Done: Federico Ceratto 

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated giara 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: Sat, 11 Dec 2021 14:53:44 +
Source: giara
Architecture: source
Version: 0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 997939
Changes:
 giara (0.3-3) unstable; urgency=medium
 .
   * Fix import path (Closes: #997939)
Checksums-Sha1:
 c82643afb019f0115d904db526ee46d596c8447b 1995 giara_0.3-3.dsc
 02ab519240c04f64dac2f3bf9eeb76b559d0cd3f 2508 giara_0.3-3.debian.tar.xz
 5dcd35904d8204db88c93b35e2c856a5fae77663 14614 giara_0.3-3_amd64.buildinfo
Checksums-Sha256:
 428fbcadfa806e758acbcecce7cc1d4688a2d4c324d4a2c2419cd17a3a8f45f5 1995 
giara_0.3-3.dsc
 9e96581f0ae1f35312a9d6d8446c7af14e07ec31aeeca8d7231b1003a1dd3c02 2508 
giara_0.3-3.debian.tar.xz
 5cb20322e0134324f348b96b328497768be7658a57ac83bda8ca1d81337a8079 14614 
giara_0.3-3_amd64.buildinfo
Files:
 1c9680f72d3e7e9ed5089c911674ae4a 1995 utils optional giara_0.3-3.dsc
 d5db0a77fe74dbd6fd8968ee44201428 2508 utils optional giara_0.3-3.debian.tar.xz
 60033069e89c2734cdd467c7a0fdd731 14614 utils optional 
giara_0.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAmG0vCwACgkQbzG8RPUX
fapIhRAAoU+ILvJsQRbuTY6lQ+OcOXftrYyLp1M+zytdINl2LrAncJ3GynqK8zSk
xuwoFVd1UgF/WqkcLev/m1QVkfBtQSDc+wl8bzVQncKJSJgLJPDq+ApC1NXRTuYt
GUGD9eFkBgMOqYoH/GRqjH1dnEzgZvcdMNRS5BaFN/Tdhy6gOvvTcC+8RiesPY2S
m4dzHdtQWr8Gnty8YFcB9j6A2zNEsMoZdpgQuhDPEszaHFn6cOXkdLb6jpXzXL4F
Ffr4gpYHuCOJ5ge1cEhppwkbdSRhhbXJtFA7lCYDMQOYRRLAHxVKMjLKs47TBZWR
lHNEUetQeXpt91MY5Ou7MdK9AyDepmRjZ1H639zSCpVo6iKx1DSY6PNL6JfMQBAV
P2O7KgOYQk5ay+xptqz+3IPt65CvGL2o2JpFt1KFKYkKaWKu7nBmgBGb0F2YOg6t
XSDHgsTH0CCbfXw4GbuBG6QMtsOp9xH6mHK0tl+2mfvNPGg6MnReL/2PAxU6lhmg
Bjdc1NJyk/Y04ZACTPtRN/Gz5HzKIzxVhFojvrCvS+eX2KOdcmdhHAEhKqBlD1IJ
NcsBsv3vNH9tNvd0kmoATJbpfZ/TDUlEZO6+S/oJtgjUP2iYw4mJfVU+AP1ult27
ivGklXhGqv/krXBqyNKCCrBM1yiN+8MpJ8oJkcKWvOccLkqdZFA=
=JFUW
-END PGP SIGNATURE End Message ---

Bug#1001478: marked as done (apache-log4j2: CVE-2021-44228: Remote code injection via crafted log messages)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 15:18:38 +
with message-id 
and subject line Bug#1001478: fixed in apache-log4j2 2.15.0-1
has caused the Debian Bug report #1001478,
regarding apache-log4j2: CVE-2021-44228: Remote code injection via crafted log 
messages
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.)


-- 
1001478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 #8220;true#8221; 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
--- End Message ---
--- Begin Message ---
Source: apache-log4j2
Source-Version: 2.15.0-1
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
apache-log4j2, 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.
Markus Koschany  (supplier of updated apache-log4j2 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: Sat, 11 Dec 2021 15:01:57 +0100
Source: apache-log4j2
Architecture: source
Version: 2.15.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 1001478
Changes:
 apache-log4j2 (2.15.0-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream version 2.15.0.
 - Fix CVE-2021-44228:
   Chen Zhaojun of Alibaba Cloud Security Team discovered that 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 version 2.15.0, this behavior has been
   disabled by default. 

Processed: gap-float: failed to build on i386 arch: object must be an MPFR, not a integer

[Debian Bug Tracking System]

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

> forwarded 998413 https://github.com/gap-packages/float/issues/59
Bug #998413 [src:gap-float] gap-float: failed to build on i386 arch: object 
must be an MPFR, not a integer
Set Bug forwarded-to-address to 
'https://github.com/gap-packages/float/issues/59'.
> thanks
Stopping processing here.

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

Bug#1001524: calcium needs a source-only upload for testing migration

[Adrian Bunk]

Source: calcium
Version: 0.4.1-1
Severity: serious

https://tracker.debian.org/pkg/calcium

Migration status for calcium (- to 0.4.1-1): BLOCKED: Rejected/violates 
migration policy/introduces a regression
Issues preventing migration:
Not built on buildd: arch amd64 binaries uploaded by julien.pu...@laposte.net
Not built on buildd: arch all binaries uploaded by julien.pu...@laposte.net, a 
ew source-only upload is needed to allow migration

Bug#996871: marked as done (wmnet: crashes on launch)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 13:35:38 +
with message-id 
and subject line Bug#996871: fixed in wmnet 1.06-1.1
has caused the Debian Bug report #996871,
regarding wmnet: crashes on launch
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.)


-- 
996871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wmnet
Version: 1.06-1+b2
Severity: grave
Justification: renders package unusable

Launching wmnet causes it to crash on launch with the following output:
$ wmnet
wmnet: using devstats driver to monitor eth0
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  36
  Current serial number in output stream:  39

I expect it to launch an Xwindow and display things. If it requires a specific 
font I expect that to be part of the package's dependencies.


-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages wmnet depends on:
ii  libc6 2.31-13+deb11u2
ii  libx11-6  2:1.7.2-1
ii  libxext6  2:1.3.3-1.1
ii  netbase   6.3

wmnet recommends no packages.

Versions of packages wmnet suggests:
pn  wmaker  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wmnet
Source-Version: 1.06-1.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated wmnet 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, 03 Dec 2021 01:16:27 +0200
Source: wmnet
Architecture: source
Version: 1.06-1.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Lazar 
Changed-By: Adrian Bunk 
Closes: 996871
Changes:
 wmnet (1.06-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Recommend xfonts-base, thanks to Thomas Groman. (Closes: #996871)
Checksums-Sha1:
 6b045313d783fa3c142bc2ee2679e5b92599f634 1717 wmnet_1.06-1.1.dsc
 3b629954d57d5fa4f854d28f940a518590e55491 10528 wmnet_1.06-1.1.debian.tar.xz
Checksums-Sha256:
 b5e7d34464ef7393db05b5900e84284b14f97f182983139f3ad7dc0d45d16570 1717 
wmnet_1.06-1.1.dsc
 c866b7f8d9d5d8a954e010df838301def4e5bbe3158bdfcdf8f563d2963c45e6 10528 
wmnet_1.06-1.1.debian.tar.xz
Files:
 5a24f13794c1612be1333d80db76c371 1717 x11 optional wmnet_1.06-1.1.dsc
 5906e6b40a0b2addca1ecde8754bd4e1 10528 x11 optional 
wmnet_1.06-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGpVqcACgkQiNJCh6LY
mLGoPw/+M/T3IXUT3SiiQeeHuTUD6217zLqqpLLjMokO7BfVICt1DAneCraOga9R
66BRSrrJlW8Cm7ktK57Xw7qQndGpYQvb8lFfqFCD/RwMAZI7EjwCHnrZNcVu2vj2
qnrC7xQzbxq442XgdFkRZokIquQ3lKUY6zR4PHtIzXCUuOGhgXKnbJqqaTkoKhDL
VWsU1iu0bXOA0qjqegJbPjHgAij3V5Jqd8uzbzrIHSBzIweOw0Han8xnh967/WI9
Hq27BCvKMxN01MgXPKWCEyz5/ZFe4DggRdonbqezm6T21dZz00PRLa8bNW9x8zdD
TC8CV6STKSh3xRKuPnc/YlcrLpt/kC9BN8wWfAKHn253Z+6zFqaUg/NeYLD4XoJT
LFCLVO5ZVjx3ZteAg/FUAKa0SPNasnVoTimTZ1SicZLUVfaqv+G29UjElyfZmHHB
OZKFWtwat5CJLHi1W7wYYyfKxbbtkRPIwrmE3qORT0L1X1NKkJqL2QivWPF/NmK2
1bU14bTsWJJSNDG48uQJOJK7ktrO+Ld7UL7YrvDu4no5Sx7dakGipluYwaFwKPUZ
e2IW9sVSdxUj1RtooEIB9wGXb4pgnKol4J6sV24myEJNyIPRlBh5CMvtL8F2Jkk/
VlMI9zyFeU8GkoJ9uP/6qgjLyNHjUE9m07kTbMz3uGA2iOWcIxc=
=cEHC
-END PGP SIGNATURE End Message ---

Bug#995202: marked as done (horst FTBFS: error: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 13:34:05 +
with message-id 
and subject line Bug#995202: fixed in horst 5.1-2.1
has caused the Debian Bug report #995202,
regarding horst FTBFS: error: format not a string literal and no format 
arguments
to be marked as done.

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

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


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

horst fails to build from source in unstable on amd64 due to ncurses
having become stricter about format strings. A build now ends as
follows:

| cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -std=gnu99 -Wall -Wextra -g -I. 
-DVERSION=\"5.1\" -DDO_DEBUG -I/usr/include/libnl3 -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o display-main.o display-main.c
| display-main.c: In function ‘print_dump_win’:
| display-main.c:56:2: error: format not a string literal and no format 
arguments [-Werror=format-security]
|56 |  wprintw(dump_win, str);
|   |  ^~~
| display-main.c: In function ‘print_node_list_line’:
| display-main.c:255:40: warning: format ‘%d’ expects argument of type ‘int’, 
but argument 5 has type ‘long unsigned int’ [-Wformat=]
|   255 |  mvwprintw(list_win, line, COL_SIG, "%3d", 
-ewma_read(>phy_sig_avg));
|   |  ~~^   ~~~
|   ||   |
|   |int long unsigned int
|   |  %3ld
| display-main.c: In function ‘update_dump_win’:
| display-main.c:455:21: warning: too many arguments for format 
[-Wformat-extra-args]
|   455 |   wprintw(dump_win, "%-7s", "ARP", ip_sprintf(p->ip_src));
|   | ^~
| display-main.c:481:31: warning: format ‘%llx’ expects argument of type ‘long 
long unsigned int’, but argument 4 has type ‘uint64_t’ {aka ‘long unsigned 
int’} [-Wformat=]
|   481 |wprintw(dump_win, "'%s' %llx", p->wlan_essid,
|   |~~~^
|   |   |
|   |   long long unsigned int
|   |%lx
|   482 | p->wlan_tsf);
|   | ~~~
|   |  |
|   |  uint64_t {aka long unsigned int}
| display-main.c: In function ‘sort_input’:
| display-main.c:129:11: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
|   129 |   do_sort = c;
|   |   ^~~
| display-main.c:131:2: note: here
|   131 |  case '\r': case KEY_ENTER:
|   |  ^~~~
| cc1: some warnings being treated as errors
| make[1]: *** [: display-main.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:19: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: horst
Source-Version: 5.1-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated horst package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 28 Nov 2021 20:51:58 +0200
Source: horst
Architecture: source
Version: 5.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Adrian Bunk 
Closes: 995202
Changes:
 horst (5.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Sven Joachim to fix FTBFS with new ncurses.
 (Closes: #995202)
Checksums-Sha1:
 2192c0182514507415df6916e0fbc3e766e5a15f 1879 horst_5.1-2.1.dsc
 b42dfeabf72c7a229da969d21fd3e269888d801d 6940 horst_5.1-2.1.debian.tar.xz
Checksums-Sha256:
 7bb43a76414e7238b0a77679b6c578ea4abadbf2e0295d794f0f1fe1a1bf33d4 1879 
horst_5.1-2.1.dsc
 b1d2d8efe10e11a8a1c76ec12a483fd66c79e1f31a142a4b82f34a2b45d83f37 6940 
horst_5.1-2.1.debian.tar.xz

Bug#984268: marked as done (ogmtools: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 13:35:27 +
with message-id 
and subject line Bug#984268: fixed in ogmtools 1:1.5-4.1
has caused the Debian Bug report #984268,
regarding ogmtools: 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.)


-- 
984268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ogmtools
Version: 1:1.5-4
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/ogmtools_1.5-4_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.

[...]
ogmmerge.cpp:95:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   95 |{"mp3", TYPEMP3, "MPEG1 layer III audio (CBR and VBR/ABR)"},
  | ^
ogmmerge.cpp:95:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   95 |{"mp3", TYPEMP3, "MPEG1 layer III audio (CBR and VBR/ABR)"},
  | ^
ogmmerge.cpp:96:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   96 |{"ac3", TYPEAC3, "A/52 (aka AC3)"},
  | ^
ogmmerge.cpp:96:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   96 |{"ac3", TYPEAC3, "A/52 (aka AC3)"},
  | ^~~~
ogmmerge.cpp:97:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   97 |{"output modules:", -1, ""},
  | ^
ogmmerge.cpp:97:28: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   97 |{"output modules:", -1, ""},
  |^~
ogmmerge.cpp:98:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   98 |{"   ", -1,  "Vorbis audio"},
  | ^
ogmmerge.cpp:98:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   98 |{"   ", -1,  "Vorbis audio"},
  | ^~
ogmmerge.cpp:99:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   99 |{"   ", -1,  "Video (not MPEG1/2)"},
  | ^
ogmmerge.cpp:99:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
   99 |{"   ", -1,  "Video (not MPEG1/2)"},
  | ^
ogmmerge.cpp:100:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  100 |{"   ", -1,  "uncompressed PCM audio"},
  | ^
ogmmerge.cpp:100:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  100 |{"   ", -1,  "uncompressed PCM audio"},
  | ^~~~
ogmmerge.cpp:101:5: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  101 |{"   ", -1,  "text subtitles"},
  | ^
ogmmerge.cpp:101:21: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  101 |{"   ", -1,  "text 

Bug#1000230: screenruler still fails to start

[Georges Khaznadar]

Peter Mueller a écrit :
> reopen 1000230
> found 1000230 0.960+bzr41+deb10-6
> thanks

Dear Peter,

the getter and the setter for the property GtkWindow.has-resize-grip are
defined in the file /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.20 on
my computer; the last message reported before the crash is 
"Unknown property: GtkWindow.has-resize-grip from 
/usr/share/screenruler/utils/glade_window.rb"

Please can you tell me the version number of your package libgtk-3-0?

Best regards,   Georges.



signature.asc
Description: PGP signature

Processed: httping: diff for NMU version 2.5-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 995625 + pending
Bug #995625 [src:httping] httping FTBFS: error: format not a string literal and 
no format arguments [-Werror=format-security]
Added tag(s) pending.

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

Bug#995625: httping: diff for NMU version 2.5-5.2

[Adrian Bunk]

Control: tags 995625 + pending

Dear maintainer,

I've prepared an NMU for httping (versioned as 2.5-5.2) and uploaded
it to DELAYED/12. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog
--- httping-2.5/debian/changelog	2020-05-08 09:30:50.0 +0300
+++ httping-2.5/debian/changelog	2021-12-11 14:36:20.0 +0200
@@ -1,3 +1,10 @@
+httping (2.5-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with new ncurses. (Closes: #995625)
+
+ -- Adrian Bunk   Sat, 11 Dec 2021 14:36:20 +0200
+
 httping (2.5-5.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru httping-2.5/debian/patches/0001-theoretical-security-problem-fix.patch httping-2.5/debian/patches/0001-theoretical-security-problem-fix.patch
--- httping-2.5/debian/patches/0001-theoretical-security-problem-fix.patch	1970-01-01 02:00:00.0 +0200
+++ httping-2.5/debian/patches/0001-theoretical-security-problem-fix.patch	2021-12-11 14:36:20.0 +0200
@@ -0,0 +1,25 @@
+From 4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0 Mon Sep 17 00:00:00 2001
+From: Folkert van Heusden 
+Date: Sun, 3 Oct 2021 20:33:21 +0200
+Subject: theoretical security problem fix
+
+---
+ nc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/nc.c b/nc.c
+index ffb6d17..e60fbe8 100644
+--- a/nc.c
 b/nc.c
+@@ -235,7 +235,7 @@ void myprint(WINDOW *w, const char *what)
+ 	}
+ 	else
+ 	{
+-		wprintw(w, what);
++		wprintw(w, "%s", what);
+ 	}
+ }
+ 
+-- 
+2.20.1
+
diff -Nru httping-2.5/debian/patches/series httping-2.5/debian/patches/series
--- httping-2.5/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ httping-2.5/debian/patches/series	2021-12-11 14:36:20.0 +0200
@@ -0,0 +1 @@
+0001-theoretical-security-problem-fix.patch

Bug#1001170: marked as done (gnudatalanguage: FTBFS on mipsel: relocation truncated to fit: R_MIPS_GOT16 against `CpuTPOOL_MAX_ELTS')

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 12:34:19 +
with message-id 
and subject line Bug#1001170: fixed in gnudatalanguage 1.0.1-3
has caused the Debian Bug report #1001170,
regarding gnudatalanguage: FTBFS on mipsel: relocation truncated to fit: 
R_MIPS_GOT16 against `CpuTPOOL_MAX_ELTS'
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.)


-- 
1001170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnudatalanguage
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

| [ 97%] Linking CXX shared library libgnudatalanguage.so
| cd /<>/obj-mipsel-linux-gnu/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/gnudatalanguage.dir/link.txt --verbose=1
| /usr/bin/c++ -fPIC -DBUILD_DATE="\"Dec  4 2021\"" -std=gnu++11 -g1 
-DBUILD_DATE="\"Dec  4 2021\"" -std=gnu++11 -g1 -Wdate-time -D_FORTIFY_SOURCE=2 
-fopenmp -Wl,-z,relro -Wl,-z,now -Wl,--allow-multiple-definition -shared 
-Wl,-soname,libgnudatalanguage.so.0 -o libgnudatalanguage.so.0 
CMakeFiles/gnudatalanguage.dir/CFMTLexer.cpp.o 
CMakeFiles/gnudatalanguage.dir/FMTIn.cpp.o 
CMakeFiles/gnudatalanguage.dir/FMTLexer.cpp.o 
CMakeFiles/gnudatalanguage.dir/FMTOut.cpp.o 
CMakeFiles/gnudatalanguage.dir/FMTParser.cpp.o 
CMakeFiles/gnudatalanguage.dir/GDLInterpreter.cpp.o 
CMakeFiles/gnudatalanguage.dir/GDLLexer.cpp.o 
CMakeFiles/gnudatalanguage.dir/GDLParser.cpp.o 
CMakeFiles/gnudatalanguage.dir/GDLTreeParser.cpp.o 
CMakeFiles/gnudatalanguage.dir/datatypes.cpp.o 
CMakeFiles/gnudatalanguage.dir/convol.cpp.o 
CMakeFiles/gnudatalanguage.dir/convol2.cpp.o 
CMakeFiles/gnudatalanguage.dir/smooth.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op_new.cpp.o 
CMakeFiles/gnudatalanguage.dir/getas.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op_add.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op_sub.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op_mult.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_op_div.cpp.o 
CMakeFiles/gnudatalanguage.dir/default_io.cpp.o 
CMakeFiles/gnudatalanguage.dir/ifmt.cpp.o 
CMakeFiles/gnudatalanguage.dir/ofmt.cpp.o 
CMakeFiles/gnudatalanguage.dir/datatypes_minmax.cpp.o 
CMakeFiles/gnudatalanguage.dir/allix.cpp.o 
CMakeFiles/gnudatalanguage.dir/arrayindex.cpp.o 
CMakeFiles/gnudatalanguage.dir/assocdata.cpp.o 
CMakeFiles/gnudatalanguage.dir/basegdl.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_fun.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_fun_cl.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_fun_jmg.cpp.o 
CMakeFiles/gnudatalanguage.dir/calendar.cpp.o 
CMakeFiles/gnudatalanguage.dir/color.cpp.o 
CMakeFiles/gnudatalanguage.dir/convert2.cpp.o 
CMakeFiles/gnudatalanguage.dir/dcommon.cpp.o 
CMakeFiles/gnudatalanguage.dir/dcompiler.cpp.o 
CMakeFiles/gnudatalanguage.dir/dialog.cpp.o 
CMakeFiles/gnudatalanguage.dir/dinterpreter.cpp.o 
CMakeFiles/gnudatalanguage.dir/dnode.cpp.o 
CMakeFiles/gnudatalanguage.dir/dpro.cpp.o 
CMakeFiles/gnudatalanguage.dir/dstructdesc.cpp.o 
CMakeFiles/gnudatalanguage.dir/dstructfactory.cxx.o 
CMakeFiles/gnudatalanguage.dir/dstructgdl.cpp.o 
CMakeFiles/gnudatalanguage.dir/dvar.cpp.o 
CMakeFiles/gnudatalanguage.dir/envt.cpp.o 
CMakeFiles/gnudatalanguage.dir/extrat.cpp.o 
CMakeFiles/gnudatalanguage.dir/exists_fun.cpp.o 
CMakeFiles/gnudatalanguage.dir/fftw.cpp.o 
CMakeFiles/gnudatalanguage.dir/file.cpp.o 
CMakeFiles/gnudatalanguage.dir/fmtnode.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdleventhandler.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlexception.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlgstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/dSFMT/dSFMT.c.o 
CMakeFiles/gnudatalanguage.dir/otherdevices/gdlxstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdljournal.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlhelp.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlpsstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlsvgstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlwidget.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlwidgeteventhandler.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlwxstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/gdlzstream.cpp.o 
CMakeFiles/gnudatalanguage.dir/getfmtast.cpp.o 
CMakeFiles/gnudatalanguage.dir/graphicsdevice.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_pro.cpp.o 
CMakeFiles/gnudatalanguage.dir/basic_pro_jmg.cpp.o 
CMakeFiles/gnudatalanguage.dir/brent.cpp.o 
CMakeFiles/gnudatalanguage.dir/grib.cpp.o 
CMakeFiles/gnudatalanguage.dir/gsl_fun.cpp.o 
CMakeFiles/gnudatalanguage.dir/gsl_matrix.cpp.o 
CMakeFiles/gnudatalanguage.dir/hash.cpp.o 

Bug#1001170: marked as pending in gnudatalanguage

[Ole Streicher]

Control: tag -1 pending

Hello,

Bug #1001170 in gnudatalanguage 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/debian-astro-team/gnudatalanguage/-/commit/4eb28d9adb9c95c1afc8af0fb464cb5bfdd4021b


Lift the usual restrictions on the size of the global offset table

Closes: #1001170


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001170

Processed: Bug#1001170 marked as pending in gnudatalanguage

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001170 [src:gnudatalanguage] gnudatalanguage: FTBFS on mipsel: relocation 
truncated to fit: R_MIPS_GOT16 against `CpuTPOOL_MAX_ELTS'
Added tag(s) pending.

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

Bug#1001512: libkshark2: broken multiarch paths on !amd64

[Helmut Grohne]

Package: libkshark2
Version: 2.0.2-1
Severity: serious
Tags: patch

libkshark2 uses the amd64 multiarch triplet for all architectures. This
is broken. The attached patch fixes that.

Helmut
diff --minimal -Nru kernelshark-2.0.2/debian/changelog 
kernelshark-2.0.2/debian/changelog
--- kernelshark-2.0.2/debian/changelog  2021-11-08 21:39:44.0 +0100
+++ kernelshark-2.0.2/debian/changelog  2021-12-08 12:35:15.0 +0100
@@ -1,3 +1,10 @@
+kernelshark (2.0.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not hardcode amd64 multiarch in *.links files. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 08 Dec 2021 12:35:15 +0100
+
 kernelshark (2.0.2-1) unstable; urgency=medium
 
   * Upload to unstable.
diff --minimal -Nru kernelshark-2.0.2/debian/libkshark-dev.links 
kernelshark-2.0.2/debian/libkshark-dev.links
--- kernelshark-2.0.2/debian/libkshark-dev.links2021-06-17 
23:12:08.0 +0200
+++ kernelshark-2.0.2/debian/libkshark-dev.links2021-12-08 
12:35:14.0 +0100
@@ -1,2 +1,2 @@
-usr/lib/x86_64-linux-gnu/libkshark-gui.so.2 
usr/lib/x86_64-linux-gnu/libkshark-gui.so
-usr/lib/x86_64-linux-gnu/libkshark-plot.so.2 
usr/lib/x86_64-linux-gnu/libkshark-plot.so
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2 
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2 
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so
diff --minimal -Nru kernelshark-2.0.2/debian/libkshark2.links 
kernelshark-2.0.2/debian/libkshark2.links
--- kernelshark-2.0.2/debian/libkshark2.links   2021-06-17 23:12:08.0 
+0200
+++ kernelshark-2.0.2/debian/libkshark2.links   2021-12-08 12:35:06.0 
+0100
@@ -1,2 +1,2 @@
-usr/lib/x86_64-linux-gnu/libkshark-gui.so.2.0.0 
usr/lib/x86_64-linux-gnu/libkshark-gui.so.2
-usr/lib/x86_64-linux-gnu/libkshark-plot.so.2.0.0 
usr/lib/x86_64-linux-gnu/libkshark-plot.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2.0.0 
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2.0.0 
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2

Bug#997504: marked as done (terminator: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 11:49:52 +
with message-id 
and subject line Bug#997504: fixed in terminator 2.1.1-1
has caused the Debian Bug report #997504,
regarding terminator: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; 
> python3.9 -m pytest --doctest-modules
> = test session starts 
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> collecting ... Trace/breakpoint trap
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=133: cd 
> /<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest 
> --doctest-modules
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/terminator_2.1.0-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: terminator
Source-Version: 2.1.1-1
Done: Markus Frosch 

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

Debian distribution maintenance software
pp.
Markus Frosch  (supplier of updated terminator 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: Sat, 11 Dec 2021 12:35:33 +0100
Source: terminator
Architecture: source
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Markus Frosch 
Closes: 997504
Changes:
 terminator (2.1.1-1) unstable; urgency=medium
 .
   * [007ce5f] Add missing dependency for gsettings-desktop-schemas
 (Closes: #997504)
   * [d8526f8] New upstream version 2.1.1
   * [d747216] Remove obsolete patch fix-white-background
   * [69c870c] Bump Standards-Version to 4.6.0
Checksums-Sha1:
 21e92b9a7933f7bf5fed211944d82d74b0d83c79 2545 terminator_2.1.1-1.dsc
 c33d2970e5c1e443530d0e1ec0d46e84d4330835 1033153 terminator_2.1.1.orig.tar.gz
 120680fcb2fd9c85c05f33ce536a36b66275b0c0 866 terminator_2.1.1.orig.tar.gz.asc
 394a7a999e6e3796dc6a182ace7f13efe35a4172 15424 terminator_2.1.1-1.debian.tar.xz
 0814257d7c06feb7c6a1ea4262e93c30871cb135 12232 
terminator_2.1.1-1_amd64.buildinfo
Checksums-Sha256:
 dfc24610afb0e954bec238f444bd1b429a68b5d67fe1d021b383b747e8cebe40 2545 
terminator_2.1.1-1.dsc
 bcb5ea52a612893451d0961ac3907a308f3907978f28349ee1ddc277af75 1033153 
terminator_2.1.1.orig.tar.gz
 c1900f625281dd68701aff16caab83a25737bdbd1e11b8ecaa834d9dfc1c5151 866 
terminator_2.1.1.orig.tar.gz.asc
 9472dd8150c5b92e95155bb7c4db11f78104c1c49b03d56ac02271a527764698 15424 
terminator_2.1.1-1.debian.tar.xz
 402da6c3a7298f06e12ff575bff43527b3bf8d628f94117e73bfe1a2871de2a1 12232 
terminator_2.1.1-1_amd64.buildinfo
Files:
 5513704b6ae9cb639326e5caf1aef4cf 2545 misc optional terminator_2.1.1-1.dsc
 a22e65eae47b34ccd42055725573bbb9 1033153 misc optional 
terminator_2.1.1.orig.tar.gz
 407dbe01b082cf43e7856e2216671603 866 misc optional 

Bug#997504: terminator: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Markus Frosch]

Hi Jochen,

On Sun, 2021-11-28 at 15:30 +0100, Jochen Sprickerhof wrote:
> The actual problem is that libgtk-3-0 version 3.24.30-1 drops the 
> dependency on librest-0.7-0 which brought in gsettings-desktop-schemas 
> which seems to be the missing build dependency as this works for unstable:
> 
> sbuild terminator --add-depends gsettings-desktop-schemas
> 
> Assigning back, accordingly, though I'm not sure if there should be an 
> other bug for python3-gi or the gtk backtrace above.

Thank you very much for the analysis, I'm not very deep into desktop basics
around GTK yet.

Will push a fix soon.

Best Regards
Markus Frosch

Processed: Bug#997504 marked as pending in terminator

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997504 [terminator] terminator: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.

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

Bug#997504: marked as pending in terminator

[Markus Frosch]

Control: tag -1 pending

Hello,

Bug #997504 in terminator 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/terminator/-/commit/007ce5f5390880edeea8cf8a12b00408f398b362


Add missing dependency for gsettings-desktop-schemas

Closes: #997504


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997504

Bug#984063: itk libtiff test issues (Was: Bug#984063)

[Steven Robbins]

On Saturday, December 11, 2021 3:02:02 A.M. CST Étienne Mollier wrote:

> I considered pushing a change yesterday to disable those tests
> on insighttoolkit4, 

Let's please agree to NEVER do that.


> not to hide dust under the carpet, but to
> give a chance to reverse dependencies to make it to testing in a
> decent enough shape hopefuly.  

I appreciate the sentiment, but medical & scientific software -- probably the 
only consumers of ITK -- is generally the sort that you never want to 
knowingly ship with failed tests.  

-Steve


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

Bug#998559: marked as done (django-tables: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 --system=custom "--test-args={interpreter} -Wd manage.py test" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 10:04:08 +
with message-id 
and subject line Bug#998559: fixed in django-tables 2.4.1-2
has caused the Debian Bug report #998559,
regarding django-tables: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p 3.9 --system=custom "--test-args={interpreter} -Wd manage.py 
test" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} -Wd manage.py test"
> I: pybuild base:232: python3.9 -Wd manage.py test
> Creating test database for alias 'default'...
> System check identified no issues (0 silenced).
> .F/usr/lib/python3.9/unittest/case.py:550:
>  DeprecationWarning: Use '__' to separate path components, not '.' in 
> accessor 'a.b' (fallback will be removed in django_tables2 version 3).
>   method()
> ...
> ==
> FAIL: test_should_support_custom_dataset_kwargs 
> (tests.test_export.ExportViewTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_export.py", line 227, in 
> test_should_support_custom_dataset_kwargs
> self.assertIn(title, wb.sheetnames)
> AssertionError: 'The Sheet Name' not found in ['-']
> 
> --
> Ran 377 tests in 0.715s
> 
> FAILED (failures=1)
> Destroying test database for alias 'default'...
> E: pybuild pybuild:354: test: plugin custom failed with: exit code=1: 
> python3.9 -Wd manage.py test
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 --system=custom 
> "--test-args={interpreter} -Wd manage.py test" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/django-tables_2.4.1-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: django-tables
Source-Version: 2.4.1-2
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated django-tables 
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: Sat, 11 Dec 2021 10:37:30 +0100
Source: django-tables
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Carsten Schoenert 
Closes: 998559
Changes:
 django-tables (2.4.1-2) unstable; urgency=medium
 .
   * Team upload.
   * [d8d1be3] Rebuild patch queue from patch-queue branch
 Added patch:
 debian-hacks/Ignore-test_export.ExportViewTest-for-now.patch
 (Closes: #998559)
 Other existing patches got renamed and added into topic folders, but
 there are no modifications 

Bug#997341: marked as done (sphinx-autoapi: FTBFS: ModuleNotFoundError: No module named 'typing_extensions')

[Debian Bug Tracking System]

Your message dated Sat, 11 Dec 2021 09:50:05 +
with message-id 
and subject line Bug#997341: fixed in sphinx-autoapi 1.8.4-1
has caused the Debian Bug report #997341,
regarding sphinx-autoapi: FTBFS: ModuleNotFoundError: No module named 
'typing_extensions'
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.)


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

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package sphinx-autoapi
> dpkg-buildpackage: info: source version 1.5.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Félix Sipma 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_sphinx-autoapi/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building sphinx-autoapi using existing 
> ./sphinx-autoapi_1.5.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building sphinx-autoapi in 
> sphinx-autoapi_1.5.1-2.debian.tar.xz
> dpkg-source: info: building sphinx-autoapi in sphinx-autoapi_1.5.1-2.dsc
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/inheritance_diagrams.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/backends.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/extension.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/documenters.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/_version.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/toctree.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/directives.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> copying autoapi/settings.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi
> creating 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> copying autoapi/mappers/go.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> copying autoapi/mappers/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> copying autoapi/mappers/dotnet.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> copying autoapi/mappers/javascript.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> copying autoapi/mappers/base.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers
> creating 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> copying autoapi/mappers/python/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> copying autoapi/mappers/python/parser.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> copying autoapi/mappers/python/astroid_utils.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> copying autoapi/mappers/python/objects.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> copying autoapi/mappers/python/mapper.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-autoapi/build/autoapi/mappers/python
> running egg_info
> 

Bug#990224: [Pkg-pascal-devel] Bug#990224: leaves diversion after upgrade from sid to experimental

[Abou Al Montacir]

Hi Paul,

Thank you for spotting this out, I did not notice it during my tests before
uploading.

On Thu, 2021-12-09 at 08:50 +0100, Paul Gevers wrote:
> Hi
> 
> As a note, this doesn't look pretty during upgrade:
> 
> Unpacking lazarus-src-2.0 (2.0.12+dfsg-6) over (2.0.12+dfsg-5) ...
> Removing 'diversion of 
> /usr/lib/lazarus/2.0.12/components/codetools/ide/cody.lpk to 
> /usr/lib/lazarus/2.0.12/components/codetools/ide/cody.lpk.orig by 
> lazarus-src-2.0'
> dpkg-divert: error: rename involves overwriting 
> '/usr/lib/lazarus/2.0.12/components/codetools/ide/cody.lpk' with
>    different file 
> '/usr/lib/lazarus/2.0.12/components/codetools/ide/cody.lpk.orig', not 
> allowed
> dpkg: warning: old lazarus-src-2.0 package post-removal script 
> subprocess returned error exit status 2
> dpkg: trying script from the new package instead ...
> dpkg: ... it looks like that went OK
It looks like the logic does not account for upgrading for the same upstream
version. 
This is really annoying and I'll appreciate any help for it.
I'm more and more convinced that using arch:all packages for distributing the
.lpk files is the right solution for this problem.
This diversion stuff looks really ugly.
-- 
Cheers,
Abou Al Montacir



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

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

[Nilesh Patra]

On 12/11/21 12:14 PM, Nilesh Patra wrote:

control: notfixed -1 r-cran-raster/3.5-9-1

Hi Robert,

On 12/11/21 12:10 AM, Nilesh Patra wrote:

On 12/10/21 11:43 PM, Robert J. Hijmans wrote:

The new release of raster should first update terra if indeed it finds an older 
version. So let's hope I am right.


I just uploaded the new version (3.5-9) and it seems to fix the problem 
locally. We will see if it works on the debci
infrastructure as well. I will report whatever it says. Thanks a lot for the 
help.


Tests are still failing, see here[1]. It is not a problem of terra version, as 
it seems, it is installed in the
way pretty much every other package is. I face the same stuff locally as well 
now.
Would you have some other fix in mind?


When I try running tests as root, the error vanishes. I have no idea what's up 
:(

== ROOT =

# bash ./debian/tests/run-unit-test
BEGIN TEST testthat.R

R version 4.1.2 (2021-11-01) -- "Bird Hippie"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.


library(testthat)
library(satellite)

Loading required package: raster
Loading required package: sp



### functions to create test data sets -

### Utility functions to quickly create test data sets for various sensors
### Florian Detsch, last modified on 2017-07-24

tst_obj <- function(type = c("LC08", "LC8", "LE07", "LE7", "LT05")) {

+   if (type[1] == "LC08")
+ tst_obj_lc08()
+   else if (type[1] == "LC8")
+ tst_obj_lc8()
+   else if (type[1] == "LE07")
+ tst_obj_le07()
+   else if (type[1] == "LE7")
+ tst_obj_le7()
+   else if (type[1] == "LT05")
+ tst_obj_lt05()
+   else
+ stop("Sensor test data not available, yet.\n")
+ }



### collection 1 level-1 -

## landsat 8
tst_obj_lc08 <- function() {

+   path <- system.file("extdata", package = "satellite")
+   files <- list.files(path, pattern = glob2rx("LC08*.TIF"), full.names = TRUE)
+   satellite(files)
+ }


## landsat 7
tst_obj_le07 <- function() {

+   path <- system.file("extdata", package = "satellite")
+   files <- list.files(path, pattern = glob2rx("LE07*.TIF"), full.names = TRUE)
+   satellite(files)
+ }


## landsat 5
tst_obj_lt05 <- function() {

+   path <- system.file("testdata/LT05", package = "satellite")
+   files <- list.files(path, pattern = glob2rx("LT05*.TIF"), full.names = TRUE)
+   satellite(files)
+ }



### precollection level-1 -

## landsat 8
tst_obj_lc8 <- function() {

+   path <- system.file("testdata/LC8", package = "satellite")
+   files <- list.files(path, pattern = glob2rx("LC8*.TIF"), full.names = TRUE)
+   satellite(files)
+ }


## landsat 7
tst_obj_le7 <- function() {

+   path <- system.file("testdata/LE7", package = "satellite")
+   files <- list.files(path, pattern = glob2rx("LE7*.TIF"), full.names = TRUE)
+   satellite(files)
+ }



### perform tests -

test_check("satellite")

== Skipped tests 

* empty test (12)

[ FAIL 0 | WARN 0 | SKIP 12 | PASS 145 ]





 NORMAL USER =

$ bash ./debian/tests/run-unit-test
BEGIN TEST testthat.R

R version 4.1.2 (2021-11-01) -- "Bird Hippie"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.


library(testthat)
library(satellite)

Loading required package: raster
Loading required package: sp
Warning messages:
1: multiple methods tables found for 'crop'
2: multiple methods tables found for 'extend'



### functions to create test data sets -

### Utility functions to quickly create test data sets for various sensors
### Florian Detsch, last modified on 2017-07-24

tst_obj <- function(type = c("LC08", "LC8", "LE07", "LE7", "LT05")) {

+   if (type[1] == "LC08")
+ tst_obj_lc08()
+   else if (type[1] == "LC8")
+ tst_obj_lc8()
+   

Bug#930747: reassign 930747 to src:bind, closing 930747

[Salvatore Bonaccorso]

reassign 930747 src:bind 1:9.13.3-1
# this was the src:bind specific cloned bug
close 930747 
thanks

Processed: reassign 930747 to src:bind, closing 930747

[Debian Bug Tracking System]

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

> reassign 930747 src:bind 1:9.13.3-1
Bug #930747 [src:bind9] bind: CVE-2019-6471: A race condition when discarding 
malformed packets can cause BIND to exit with an assertion failure
Bug reassigned from package 'src:bind9' to 'src:bind'.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
No longer marked as found in versions bind9/1:9.13.3-1.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
Ignoring request to alter fixed versions of bug #930747 to the same values 
previously set
Warning: Unknown package 'src:bind'
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'
Marked as found in versions bind/1:9.13.3-1.
Warning: Unknown package 'src:bind'
> # this was the src:bind specific cloned bug
> close 930747
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'
Marked Bug as done
Warning: Unknown package 'src:bind'
> thanks
Stopping processing here.

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

Bug#927935: reassign 927935 to src:bind, closing 927935

[Salvatore Bonaccorso]

reassign 927935 src:bind 1:9.13.3-1
# this was the src:bind specific cloned bug
close 927935 
thanks

Processed: reassign 927935 to src:bind, closing 927935

[Debian Bug Tracking System]

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

> reassign 927935 src:bind 1:9.13.3-1
Bug #927935 [src:bind9] bind: CVE-2018-5743: Limiting simultaneous TCP clients 
is ineffective
Bug reassigned from package 'src:bind9' to 'src:bind'.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
No longer marked as found in versions bind9/1:9.13.3-1.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
Ignoring request to alter fixed versions of bug #927935 to the same values 
previously set
Warning: Unknown package 'src:bind'
Bug #927935 [src:bind] bind: CVE-2018-5743: Limiting simultaneous TCP clients 
is ineffective
Warning: Unknown package 'src:bind'
Marked as found in versions bind/1:9.13.3-1.
Warning: Unknown package 'src:bind'
> # this was the src:bind specific cloned bug
> close 927935
Bug #927935 [src:bind] bind: CVE-2018-5743: Limiting simultaneous TCP clients 
is ineffective
Warning: Unknown package 'src:bind'
Marked Bug as done
Warning: Unknown package 'src:bind'
> thanks
Stopping processing here.

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

Bug#927931: reassign 927931 to src:bind, closing 927931

[Salvatore Bonaccorso]

reassign 927931 src:bind 1:9.13.3-1
close 927931 
thanks

Processed: reassign 927931 to src:bind, closing 927931

[Debian Bug Tracking System]

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

> reassign 927931 src:bind 1:9.13.3-1
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
Bug reassigned from package 'src:bind9' to 'src:bind'.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
No longer marked as found in versions bind9/1:9.13.3-1.
Warning: Unknown package 'src:bind'
Warning: Unknown package 'src:bind'
Ignoring request to alter fixed versions of bug #927931 to the same values 
previously set
Warning: Unknown package 'src:bind'
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'
Marked as found in versions bind/1:9.13.3-1.
Warning: Unknown package 'src:bind'
> close 927931
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'
Marked Bug as done
Warning: Unknown package 'src:bind'
> thanks
Stopping processing here.

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

Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

[Marc Haber]

On Sat, Feb 20, 2021 at 08:29:05PM +0100, Dennis Filder wrote:
> Jean-Christophe, are you still interested in figuring this out?  If so
> you need to provide more information.  You also don't say what else
> you have tried to investigate this.

I intend to close this bug by the end of February 2022 if we don't get
more information.

Greetings
Marc