Bug#1029466: marked as done (esda: FTBFS with current numba version)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jul 2023 00:48:56 +
with message-id 
and subject line Bug#1029466: fixed in esda 2.4.3-4
has caused the Debian Bug report #1029466,
regarding esda: FTBFS with current numba version
to be marked as done.

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

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


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

Source: esda
Version: 0.1.0-1
Severity: serious

The package cannot be built due to the unit tests:

 short test summary info 

FAILED esda/tests/test_getisord.py::G_Local_Tester::test_G_Local_Binary - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::G_Local_Tester::test_G_Local_Row_Standardized - numba.core.errors.TypingError: 
Failed in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::G_Local_Tester::test_G_star_Local_Binary - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::G_Local_Tester::test_G_star_Row_Standardized - numba.core.errors.TypingError: Failed 
in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::G_Local_Tester::test_by_col - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::i::test_G_Local_Binary - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::i::test_G_Local_Row_Standardized - numba.core.errors.TypingError: Failed in nopython 
mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::i::test_G_star_Local_Binary - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::i::test_G_star_Row_Standardized - numba.core.errors.TypingError: Failed in nopython 
mode pipeline (step: nopython frontend)
FAILED esda/tests/test_getisord.py::i::test_by_col - numba.core.errors.TypingError: Failed in nopython mode pipeline 
(step: nopython frontend)
FAILED esda/tests/test_ljc.py::Join_Counts_Locals_Tester::test_Join_Counts_Locals - numba.core.errors.TypingError: 
Failed in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_ljc.py::i::test_Join_Counts_Locals - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_ljc_bv.py::Local_Join_Counts_BV_Tester::test_Local_Join_Counts_BV - 
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_ljc_bv.py::i::test_Local_Join_Counts_BV - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_ljc_mv.py::Local_Join_Counts_MV_Tester::test_Local_Join_Counts_MV - 
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_ljc_mv.py::i::test_Local_Join_Counts_MV - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Tester::test_z_consistency - numba.core.errors.TypingError: Failed in nopython 
mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Local_Tester::test_Moran_Local - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Local_Tester::test_Moran_Local_parallel - numba.core.errors.TypingError: Failed 
in nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Local_Tester::test_local_moments - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Local_BV_Tester::test_Moran_Local_BV - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::Moran_Local_Rate_Tester::test_moran_rate - numba.core.errors.TypingError: Failed in 
nopython mode pipeline (step: nopython frontend)
FAILED esda/tests/test_moran.py::i::test_moran_rate - numba.core.errors.TypingError: Failed in nopython mode pipeline 
(step: nopython frontend)
FAILED esda/tests/test_util.py::Fdr_Tester::test_fdr - numba.core.errors.TypingError: Failed in nopython mode pipeline 
(step: nopython frontend)
FAILED esda/tests/test_util.py::i::test_fdr - numba.core.errors.TypingError: 

Processed: tagging 1040320

[Debian Bug Tracking System]

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

> tags 1040320 + pending
Bug #1040320 [libmediastreamer13] libmediastreamer13: undeclared file conflict 
with libmediastreamer12
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1040579: marked as done (python-gflanguages: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 21:03:10 +
with message-id 
and subject line Bug#1040579: fixed in python-gflanguages 0.4.0-3
has caused the Debian Bug report #1040579,
regarding python-gflanguages: implicitly depends on python3-pkg-resources
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.)


-- 
1040579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gflanguages
Version: 0.4.0-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-gflanguages/35451512/log.gz

 21s  ERRORS 

 21s  ERROR collecting tests/test_gflanguages_api.py 

 21s ImportError while importing test module 
'/tmp/autopkgtest-lxc.ll4xso7j/downtmp/autopkgtest_tmp/tests/test_gflanguages_api.py'.
 21s Hint: make sure your test modules/packages have valid Python names.
 21s Traceback:
 21s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 21s return _bootstrap._gcd_import(name[level:], package, level)
 21s tests/test_gflanguages_api.py:17: in 
 21s from pkg_resources import resource_filename
 21s E   ModuleNotFoundError: No module named 'pkg_resources'


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSoUVQACgkQ+C8H+466
LVnOPgv+POeeVi0QGha7bcbH+IHbS2MJURn3XWaTpodBHfnaHg1lpNr93o+WejYc
288aNe+f2pWXGvTlkBat0rock+hfeJO+oYo2akhRJ+OGams9QV+Jh/vXCFv7VkQk
2hZ9Py4xjHTpQggU3u36I6Au5j+JPbG152vKc3vbdCtD6CBjeSPD4a3GMciWVsmP
q+EGRxtq8WtNGtHvDDwVdgezeElCzrylDZoJjJOZgIweBYfLVFlTP1d96oMOYfHm
5o6t/C41xJsJjThOD1H3aFIjFdOcooCvxPg0Q5ye3sLOm4udROzF7CnBFqxI44GO
D0rwq3yNCFk6wZdHDBJEKglf6WlxoPGSdZ1z9asaXCjw9CBda8NDLFWZ1XCxcPRq
5LX4CrdUIgHtF6r90aW/79VxJYSs9ADKDBdleoOk3Y3xb4VIrkah3nBSuyq1W1rb
AJb3/UL7x9HMbE2f5TfQj9xrkHDBT665qOCRdvUqskF2DutAW4SIWqykyVqcxyzy
nympYQkE
=Qa60
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-gflanguages
Source-Version: 0.4.0-3
Done: Timo Röhling 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 21:33:36 +0200
Source: python-gflanguages
Architecture: source
Version: 0.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1040579
Changes:
 python-gflanguages (0.4.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing depend on python3-pkg-resources (Closes: #1040579)
Checksums-Sha1:
 f7b4cd17472171d26843e29632d369231d3ebf84 2164 python-gflanguages_0.4.0-3.dsc
 72da76db168cb05c3c259483a9dc28542e7eb7d3 4536 
python-gflanguages_0.4.0-3.debian.tar.xz
 e418ab87852859b821bd17b598e28dca4db5ad39 6822 
python-gflanguages_0.4.0-3_amd64.buildinfo
Checksums-Sha256:
 bb99a8c0f0e48f841684d60abc1594cc8ac0d044c74f21823baf67a2d888c999 2164 
python-gflanguages_0.4.0-3.dsc
 06dd4241318a8a5058450e366a5b915ae35f907d3fc54b2ab067da69302f2418 4536 
python-gflanguages_0.4.0-3.debian.tar.xz
 23412e9658d28d8642bf24f4a80b941a02c3fde53d9532cf74e7abecca8c985d 6822 
python-gflanguages_0.4.0-3_amd64.buildinfo
Files:
 c774e04c0fc73673960383db33bd2de4 2164 python optional 
python-gflanguages_0.4.0-3.dsc
 a10a06d33b61ce68dbc0cdc8df433ca9 4536 python optional 
python-gflanguages_0.4.0-3.debian.tar.xz
 

Bug#1040714: marked as done (dhcpcd: Missing epoch from souce package version)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 20:58:07 +
with message-id 
and subject line Bug#1040714: fixed in dhcpcd 1:10.0.1-3
has caused the Debian Bug report #1040714,
regarding dhcpcd: Missing epoch from souce package version
to be marked as done.

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

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


-- 
1040714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dhcpcd
Version: 10.0.1-1
Severity: serious
Justification: Debian version goes backwards from previous released versions
X-Debbugs-Cc: car...@debian.org

Hi

The new src:dhcpcd has a lower version of any previous released
src:dhcpd version, which had an epoch:

1:3.2.3-11+deb7u1
1:3.2.3-11
1:3.2.3-10
1:3.2.3-9
1:3.2.3-8
1:3.2.3-7
1:3.2.3-6
1:3.2.3-5+squeeze2
1:3.2.3-5+squeeze1
1:3.2.3-5
1:3.2.3-4
1:3.2.3-3
1:3.2.3-2
1:3.2.3-1.1
1:3.2.3-1
1:3.2.2-1
1:3.0.17-2
1:3.0.17-1
1:2.0.3-1
1:2.0.2-1
1:2.0.1-1
1:2.0.0-2
1:2.0.0-1
1:1.3.22pl4-22
1:1.3.22pl4-21sarge1
1:1.3.22pl4-21
1:1.3.22pl4-20
1:1.3.17pl2-8.1
1:1.3.17pl2-8
1:0.70-5
1.3.8-0.1
0.70-3
0.6-1
0.4-1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: dhcpcd
Source-Version: 1:10.0.1-3
Done: Martin-Éric Racine 

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

Debian distribution maintenance software
pp.
Martin-Éric Racine  (supplier of updated dhcpcd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Jul 2023 18:49:15 +0300
Source: dhcpcd
Architecture: source
Version: 1:10.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Martin-Éric Racine 
Changed-By: Martin-Éric Racine 
Closes: 1040714
Changes:
 dhcpcd (1:10.0.1-3) unstable; urgency=medium
 .
   * Reintroduce epoch for the whole package (Closes: #1040714).
 Since src:package dropped the 5, it too has a version older than Wheezy.
   * [rules]
 - Remove override_dh_gencontrol recipe as a result of the above.
Checksums-Sha1:
 0043650e2f6c87f65fb91011a128dfc5db4f2a86 2069 dhcpcd_10.0.1-3.dsc
 b0f4235b2cbf8f6b6f5bb97913b3e74fba6ee267 356237 dhcpcd_10.0.1.orig.tar.gz
 450d52a04e4ef781dce8151039d8482d3d2e49be 16164 dhcpcd_10.0.1-3.debian.tar.xz
 5303738b0f4c37a9ac7d368577dc9879ed5d 6768 dhcpcd_10.0.1-3_amd64.buildinfo
Checksums-Sha256:
 126ca6d4c5bf744c2e0199af479ca11798fb29d7a7eede115830b29e6c9d1d67 2069 
dhcpcd_10.0.1-3.dsc
 2bd3480bc93e6bff530872b8bc80cbcaa821449f7bf6aaf202fa12fb8c2e6f55 356237 
dhcpcd_10.0.1.orig.tar.gz
 f390c2fac2881c47dccb62c77cfc3b29a615ef4cdc14fdad7ab147abd0a4a90d 16164 
dhcpcd_10.0.1-3.debian.tar.xz
 82ff6260d44226649cd8453d6f03301b47f7ededcfbb4ae9ba0f065210571d06 6768 
dhcpcd_10.0.1-3_amd64.buildinfo
Files:
 fa061768da94115b8fda9fe99cc29dec 2069 net optional dhcpcd_10.0.1-3.dsc
 5091650aac228a389a51ef1bc890eeca 356237 net optional dhcpcd_10.0.1.orig.tar.gz
 3c051873d3485cad1d1c1bfa5f586755 16164 net optional 
dhcpcd_10.0.1-3.debian.tar.xz
 a0ea2dc5d2b7f23c4922c6ab2eb7caa9 6768 net optional 
dhcpcd_10.0.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmSvB2IACgkQwpPntGGC
Ws46ow/9FfF9A7tZzBpWrDu5Jrcq1Cl584QImJniZP/BXQAgyqabPvXOZ9MBNyMd
kjgMy+HEupkOu2qVLhn6hP6PrOtcQ3tmuaQvMjTwIzv/6g80QOzF7DeitJvl+lD/
54LwSH4xRQwJvjGtyotE/UE6OGcXAFv8imgct7y7dyw7nDKkn4BOSxltAjzp6gRJ
DovAhAnLXjZj1d59SmzM45lx6RzrHZAWb0nqzbAjxE0obM5jk2Bx1DqNcwBzMkzb
XA9aa2fijZ28Guo0SXIu71wd5tJSrl3BNbmC32ppMuNazX7lEsJwbO7juUM01AtG
/e3bRBQuCUdw8RvXYpWU5Waq4u/YQ+0uqpX4cE255fQ4fozCw7dOQIwCFeVp3i8W
mNOoNj/mZdfckW/hdN5XrxwMCfwb0weqLspZJ9jzue/iEP9QV80fOhYkXPFeHzyX
GdtV51s9AZEmqgfWAZnLVCzI9eq+80lLhlE5/PJWoTzIJLVx4yeTxktN45K+dQX4
uL3OslAdmm8uhUPX0gd0NyT514ThhRphMc0lTyDAkYzgtOFi/Izq/8ITurkFqvm/
j7jFl/aLpkhUZgJtOaaLRfmzgryoeNqFjAdAektPCe3A7jlKTkhzudYv4pu/Fe/Z
Ri3mIB1MOGXPHkvsBsdltGti6r57N03OlPWQqAiNgHyVbjhE710=
=QuOO
-END PGP SIGNATURE End Message ---

Bug#1040581: marked as done (mdp: implicitly depends on python3-py)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 21:01:00 +
with message-id 
and subject line Bug#1040581: fixed in mdp 3.6-3
has caused the Debian Bug report #1040581,
regarding mdp: implicitly depends on python3-py
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.)


-- 
1040581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.6-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-py for its autopkgtest, which used
to be provided by python3-pytest. However, pytest has dropped that dependency,
breaking your autopkgtest and possibly your package.

Note that you can replace py.test.foo with pytest.foo and avoid the
dependency on python3-py altogether.


Cheers
Timo

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mdp/35449827/log.gz


 29s  ERRORS 

 29s _ ERROR collecting mdp/test/test_NormalizingRecursiveExpansionNode.py 
__
 29s ImportError while importing test module 
'/tmp/autopkgtest-lxc.lsh0veg9/downtmp/build.Ujr/src/mdp/test/test_NormalizingRecursiveExpansionNode.py'.
 29s Hint: make sure your test modules/packages have valid Python names.
 29s Traceback:
 29s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 29s return _bootstrap._gcd_import(name[level:], package, level)
 29s mdp/test/test_NormalizingRecursiveExpansionNode.py:10: in 
 29s import py.test
 29s E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
 29s ___ ERROR collecting mdp/test/test_RecursiveExpansionNode.py 
___
 29s ImportError while importing test module 
'/tmp/autopkgtest-lxc.lsh0veg9/downtmp/build.Ujr/src/mdp/test/test_RecursiveExpansionNode.py'.
 29s Hint: make sure your test modules/packages have valid Python names.
 29s Traceback:
 29s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 29s return _bootstrap._gcd_import(name[level:], package, level)
 29s mdp/test/test_RecursiveExpansionNode.py:11: in 
 29s import py.test
 29s E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSoUowACgkQ+C8H+466
LVlvMAwA1FH2THkigYTPZWTpOOaeAsktk6oq/KMg9iDEmAoiX9gSHi2MrE4m/Syw
AlRvWE0UVGRgwCgVUtq1c2DNkG8u78HILvoHDo0y76at/NwdaGV7mDkSyDrlFfhx
elFxFVixX6MwMf6lHmX5TB+zP2oDLbybhfWxB7qqR9P5Ep2bEzZTYnTYbGHG7QN9
1Gg+7WqTMwohVBF++HdUTVe036HBlJOO4opqvnF2go1GA0ZoRw2rbNi6kiEiti/Y
Dzhb9k4H77T9d2McqLCDmwrbGwoYQVcpKaJM5kLEWuNZxuqQPGmuDV3KDO3CQ7pZ
K1EZxvkgW5HY5t6wl2ucQVZ3IOioi+2dDoT2OikURdz9zR+1dzvde1o/HojvySET
/X5YHb+Vn/aOpR0tm4dUbJo8mugQGHzZJSwrfj0Fd9AYScpjGMYorFcMTZGPGIiw
5Qvqg0PFmmsmugcEEyPNovxdi9InAdMaZQ8SAOP+HDVUTUCxQiYwb8WrVKbpxo7m
tyQMjG4F
=CTSA
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: mdp
Source-Version: 3.6-3
Done: Timo Röhling 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 22:05:11 +0200
Source: mdp
Architecture: source
Version: 3.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1040581
Changes:
 mdp (3.6-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop obsolete import of py.test (Closes: #1040581)
Checksums-Sha1:
 e5388a69a58fa1212707299643940041910e 2131 mdp_3.6-3.dsc
 2a71c91e400bb53457ab44c36abe9ceb878dbd87 5616 mdp_3.6-3.debian.tar.xz
 19e147ca8d2350ed2fb5a76c0566caaa9aa71a98 7787 mdp_3.6-3_amd64.buildinfo
Checksums-Sha256:
 ac6e97e75cbf039f17dc396cc37ea2ff957e5158c5ab20d13c82f5dd395bad58 2131 
mdp_3.6-3.dsc
 4eb0f11f44ef9e60a673c2c33e16be683f8735f5b4786d4b751206fcef606216 5616 
mdp_3.6-3.debian.tar.xz
 

Bug#1040257: marked as done (schleuder-cli does not work with Ruby >= 3.0.0)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 20:47:12 +
with message-id 
and subject line Bug#1040257: fixed in schleuder-cli 0.1.0-4+deb12u1
has caused the Debian Bug report #1040257,
regarding schleuder-cli does not work with Ruby >= 3.0.0
to be marked as done.

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

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


-- 
1040257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: schleuder-cli
Version: 0.1.0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

schleuder-cli 0.1.0 was designed for Ruby 2.7 in mind; Ruby 3.0
comes with a breaking change that breaks schleuder-cli.  As bookworm
comes with Ruby 3.1, schleuder-cli crashes when used due to this
breaking change:

  root@localhost:/# schleuder-cli lists new t...@schleuder.example.org 
ad...@example.org /tmp/ad...@example.org.asc
  ::1 - - [03/Jul/2023:20:56:58 +] "POST /lists.json HTTP/1.1" 200 1102 
1.5971
  List t...@schleuder.example.org successfully created! Don't forget to hook it 
into your MTA.
  /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:22:in `block in url': 
undefined method `escape' for URI:Module (NoMethodError)

  "#{URI.escape(k.to_s)}=#{URI.escape(v.to_s)}"
^^^
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `each'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `map'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `url'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:191:in 
`import_key'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:170:in 
`import_key_and_find_fingerprint'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/lists.rb:30:in `new'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/command.rb:27:in 
`run'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:127:in
 `invoke_command'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:392:in 
`dispatch'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:116:in
 `invoke'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:243:in `block 
in subcommand'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/command.rb:27:in 
`run'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:127:in
 `invoke_command'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:392:in 
`dispatch'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/base.rb:485:in 
`start'
from /usr/bin/schleuder-cli:7:in `'


Upstream has fixed the issue on the main branch, but has not yet
created a new release containing the fix.  The fix is quite small,
only two lines diff:

https://0xacab.org/schleuder/schleuder-cli/-/commit/68754cf94cc2d9b2a400ff19d2e48a7ffa2ec1f2

With this patch applied manually, schleuder-cli works as expected:

  root@localhost:/# schleuder-cli lists new t...@schleuder.example.org 
ad...@example.org /tmp/ad...@example.org.asc
  ::1 - - [03/Jul/2023:21:33:04 +] "POST /lists.json HTTP/1.1" 200 1108 
4.6595
  List t...@schleuder.example.org successfully created! Don't forget to hook it 
into your MTA.
  ::1 - - [03/Jul/2023:21:33:04 +] "POST 
/keys.json?list_id=test%40schleuder.example.org HTTP/1.1" 200 327 0.0120
  Key 48F817C6EF39DE78AEEF5D0AD6A09061E4E11475: imported
  ::1 - - [03/Jul/2023:21:33:04 +] "POST 
/subscriptions.json?list_id=test%40schleuder.example.org HTTP/1.1" 201 - 0.1797


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

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

Versions of packages schleuder-cli depends on:
ii  ruby   1:3.1
ii  ruby-thor  1.2.1-2

schleuder-cli recommends no packages.

schleuder-cli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: schleuder-cli
Source-Version: 0.1.0-4+deb12u1
Done: Georg Faerber 

We believe that the bug you reported is fixed in the latest version of
schleuder-cli, 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.

Bug#1032904: marked as done (node-webpack: CVE-2023-28154)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 20:47:12 +
with message-id 
and subject line Bug#1032904: fixed in node-webpack 
5.75.0+dfsg+~cs17.16.14-1+deb12u1
has caused the Debian Bug report #1032904,
regarding node-webpack: CVE-2023-28154
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.)


-- 
1032904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-webpack
Version: 5.75.0+dfsg+~cs17.16.14-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/webpack/webpack/pull/16500
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for node-webpack.

CVE-2023-28154[0]:
| Webpack 5 before 5.76.0 does not avoid cross-realm object access.
| ImportParserPlugin.js mishandles the magic comment feature. An
| attacker who controls a property of an untrusted object can obtain
| access to the real global object.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-28154
https://www.cve.org/CVERecord?id=CVE-2023-28154
[1] https://github.com/webpack/webpack/pull/16500

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: node-webpack
Source-Version: 5.75.0+dfsg+~cs17.16.14-1+deb12u1
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-webpack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 May 2023 07:53:16 +0400
Source: node-webpack
Architecture: source
Version: 5.75.0+dfsg+~cs17.16.14-1+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1032904
Changes:
 node-webpack (5.75.0+dfsg+~cs17.16.14-1+deb12u1) bookworm; urgency=medium
 .
   * Team upload
   * Avoid cross-realm objects (Closes: #1032904, CVE-2023-28154)
Checksums-Sha1: 
 04d65c6add6b7b00030d5b24025b299f4bd1d71c 4730 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.dsc
 425d42ef6b7bce09ed0a7bcb8a5880a4c610ca58 32824 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.debian.tar.xz
Checksums-Sha256: 
 be618f638b3f211282bd237deceb8c5a03887c99ac3dcb36468468feb54f0f87 4730 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.dsc
 b7d0b4dc568d221da31c2c8b445422f7cc4a5ca8e76637164e4ab48f49c6e542 32824 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.debian.tar.xz
Files: 
 0e747a3807da3622b33396d1c07243c0 4730 javascript optional 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.dsc
 6cfddcd1069f1958caf8d3b59d7ad54d 32824 javascript optional 
node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmSuIaAACgkQ9tdMp8mZ
7ukzsxAAhpQc2aZlD6g73Gb3ZG2lfuNiG+wC9Jmjp9SHEQ+0WXeD80KgABlG+kgQ
WhHkGARwlly4PpZ4zWMh5Fx8g2aGCEgJ4du5la4xob37D5NUirlvy7NFuBriMSf8
v5Fk9EybBQVSukpohD90c5eh1A0pSi7Vw2FFiGD1yzq8hqssVA1PbmCDO5YYSbu4
HwgyTm67MSACNV32VvAiqZVvNenb4u9FkBEmCmuY94n/XJsL2sP9fWWqxTgCZsYA
PvzDRWaVwYKZ72FRDQGJWpnjbpZRGarnb3vJwCHIjveyStT4IDAiOr6SAPyDm4HK
N9g5nlraX48lOzHAvi6IVc35udOJimqsjDfahSD+3RwCZ1X+K+fEu6vkp8/RDR4i
oaLlaAjlKzhvWyyfW6loWBGVzZBrL1Oz4VxW1sI4CCqTV+u8s8YtNEEcmvU3yJMT
Wp1mi438f+nRObFtAjHEXTk2RilhLFrsaG9ohWpojBQJM0FEsuYceq0EzD2ueRkK
iR4PdEuLN+IIkAjix4OhAkG5hPgju6epZ7lVVGt2kYZMo/PHnHiDmA6KXXKaVASb
RsUtV/Ak9ktuO2cpO3agL0uQFLsJmbJ3bxi7pXWxiKaL2YwnFSSbDmlxUtvntScB
uEcP3lrOfGHME6d8p5eJvpcLjijrxokDI6Dlgfc3RfJtMR6+72M=
=R7oo
-END PGP SIGNATURE End Message ---

Bug#1040714: dhcpcd: Missing epoch from souce package version

[Boyuan Yang]

Hi,

在 2023-07-11星期二的 21:54 +0200，Salvatore Bonaccorso写道：
> Hi,
> 
> On Tue, Jul 11, 2023 at 10:37:44PM +0300, Martin-Éric Racine wrote:
> > On Tue, Jul 11, 2023 at 10:05 PM Salvatore Bonaccorso  
> > wrote:
> > > On Tue, Jul 11, 2023 at 06:30:38PM +0300, Martin-Éric Racine wrote:
> > > > Reintroducing the epoch produces the following Lintian ERROR:
> > > > 
> > > > E: dhcpcd source:
> > > > epoch-changed-but-upstream-version-did-not-go-backwards 10.0.1-2 ->
> > > > 1:10.0.1-3 [debian/changelog:1]
> > > 
> > > The lintian tag in it's intention is clear. But I believe in this case
> > > it reports in error. Because the history of the dhcpcd source package
> > > is as follows, cutting of some irrelevant inbetween steps:
> > > 
> > > 0.4-1 -> 1.3.8-0.1 -> 1:0.70-5 (epoch introduced here), then moved
> > > upwards -> 1:3.2.3-11 / 1:3.2.3-11+deb7u1 which was the last version
> > > available for a while.
> > > 
> > > But then we dropped to 10.0.1-1 (which already missed the epoch).
> > > 
> > > Now the lintian just only checks 10.0.1-2 -> 1:10.0.1-3 and thinks to
> > > report that the epoch addition is an error, but it would not if all
> > > the 10.0.1-1, 10.0.1-2 versions already had the epoch still.
> > > 
> > > Does this make sense?
> > 
> > Makes sense to me.
> > 
> > Uploaded to Mentors. Please note that Mentors forces me to 'debuild
> > -sa' because it cannot find the 'orig' on its repository even though
> > it's already in unstable.
> 
> Thanks! Boyuan (CC'ed), can you take it from there and would you be
> willing to sponsor Martin-Éric's work as you did for the previous two
> uploads?

Thanks. Reviewed and uploaded.

Best,
Boyuan Yang


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

Bug#1022957: golang-github-blynn-nex: diff for NMU version 0.0.0+git.2021.03.30.1a3320dab9-2.1

[Shengjing Zhu]

On Thu, Jul 13, 2023 at 2:00 AM Boyuan Yang  wrote:
>
> Control: tags 1022957 + patch
> Control: tags 1022957 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for golang-github-blynn-nex (versioned as 
> 0.0.0+git.2021.03.30.1a3320dab9-2.1) and
> uploaded it to DELAYED/14. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>
> diff -Nru 
> golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog 
> golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog
> --- golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog  
>   2022-11-01 08:33:32.0 -0400
> +++ golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog  
>   2023-07-12 13:51:55.0 -0400
> @@ -1,3 +1,11 @@
> +golang-github-blynn-nex (0.0.0+git.2021.03.30.1a3320dab9-2.1) unstable; 
> urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/control: Mark package nex to conflict with package nvi
> +due to file conflict of /usr/bin/nex. (Closes: #1022957)
> +
> + -- Boyuan Yang   Wed, 12 Jul 2023 13:51:55 -0400
> +
>  golang-github-blynn-nex (0.0.0+git.2021.03.30.1a3320dab9-2) unstable; 
> urgency=medium
>
>* Re-upload source-only.
> diff -Nru 
> golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control 
> golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control
> --- golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control
>   2022-11-01 08:33:32.0 -0400
> +++ golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control
>   2023-07-12 13:51:40.0 -0400
> @@ -20,6 +20,8 @@
>   ${shlibs:Depends},
>  Suggests:
>   graphviz,
> +Conflicts:
> + nvi,
>  Description: lexer similar to Lex/Flex - cli
>   Nex is a lexer similar to Lex/Flex that:
>* generates Go code instead of C code

This is not right as per debian policy 10.1.

"Two different packages must not install programs with different
functionality but with the same filenames".

Please cancel the NMU.

-- 
Shengjing Zhu

Bug#1040578: marked as done (python-molotov: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 19:43:41 +
with message-id 
and subject line Bug#1040578: fixed in python-molotov 2.1-6
has caused the Debian Bug report #1040578,
regarding python-molotov: implicitly depends on python3-pkg-resources
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.)


-- 
1040578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-molotov
Version: 2.1-5
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/35451514/log.gz

 29s  ERRORS 

 29s _ ERROR collecting molotov/tests/test_slave.py 
_
 29s ImportError while importing test module 
'/tmp/autopkgtest-lxc.jd5622c7/downtmp/build.Iu1/src/molotov/tests/test_slave.py'.
 29s Hint: make sure your test modules/packages have valid Python names.
 29s Traceback:
 29s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 29s return _bootstrap._gcd_import(name[level:], package, level)
 29s molotov/tests/test_slave.py:9: in 
 29s from molotov.slave import main
 29s molotov/slave.py:9: in 
 29s import pkg_resources
 29s E   ModuleNotFoundError: No module named 'pkg_resources'


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSoUPYACgkQ+C8H+466
LVnfGgwAt3Qsym11wXf2B7CPM1F3o83JXU+eRenaZAWSYJfRf8686l4Sby4ybgIW
Ig0B4tY8LLqfVl86gKJ/H6URvj/8TodfyWzZA24duzG7MnAN778qPXCxFrI7N5DQ
VTn9lmOnXJAegQpY7b6HyXLdsUu9571AWd0MiJPWIOIY5NHeRrBcssce9bJwOJmV
hTLQxj0WTE7KvDiE9D+ZTox7uu17XKlYnawxLfp/mU2yKty83MVz88VTd7cezhNB
mJEPvRubHRDUyPem48asEUZcpsgqXfcZ1nclijPAhpS2joY6M0K9JTAdLfaAl699
uP/ddgJFk9h13fbIOG4zuP5ljTdiakp8jI6tIsa4xzVv9k56yHs0efaRS4pCNm6q
ldfdjXzEsHSnjdDT5xnzKT/VxpBp3dyTg602+2Pt5ZXxDJ00TI/Tvx+3boYZCtnJ
AO17sJT1eufrYsyKnfYuw+3v1WvvEvJdY4AiMrbVZIclttL9v615BtMwOflim/yn
SIeVMd8h
=riny
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-molotov
Source-Version: 2.1-6
Done: Timo Röhling 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 20:43:44 +0200
Source: python-molotov
Architecture: source
Version: 2.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1040578
Changes:
 python-molotov (2.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Add missing depend on python3-pkg-resources (Closes: #1040578)
Checksums-Sha1:
 96422c492388a7b154cc9412daad3e623f463f83 2096 python-molotov_2.1-6.dsc
 2f77f18f5a92e1e0c65b2e38cc5ea0f44953f529 5664 
python-molotov_2.1-6.debian.tar.xz
 63cc152d9949ccdf57278a45b98f3614d2871ba6 7050 
python-molotov_2.1-6_amd64.buildinfo
Checksums-Sha256:
 a4503e4b8ceb0dd6d62ceb912d85519e60a145f8a6f744d8ebee0ba20640b076 2096 
python-molotov_2.1-6.dsc
 e52d71a4af0dc4fc7f5ffcafa5e0df78de0d70dca535b3d75a2bdc909e0fccfa 5664 
python-molotov_2.1-6.debian.tar.xz
 1b81f688760d20f82ffafd2c61273172970e08e442d4eb906e74764fa5167f1f 7050 
python-molotov_2.1-6_amd64.buildinfo
Files:
 c142fbdf4b00f741870ea190489e4a9a 2096 python optional python-molotov_2.1-6.dsc
 58ad5d1d1d2085851c605e8d0a676612 5664 python optional 
python-molotov_2.1-6.debian.tar.xz
 5d0e310d4fabecd566d3aef7552b 7050 python optional 

Bug#1040576: marked as done (python-mongomock: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 19:43:49 +
with message-id 
and subject line Bug#1040576: fixed in python-mongomock 4.1.2-2
has caused the Debian Bug report #1040576,
regarding python-mongomock: implicitly depends on python3-pkg-resources
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-mongomock/35451515/log.gz


 24s  ERRORS 

 24s ___ ERROR collecting tests/test__bulk_operations.py 

 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.2jeup6d8/downtmp/build.egq/src/tests/test__bulk_operations.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s tests/test__bulk_operations.py:3: in 
 24s import mongomock
 24s mongomock/__init__.py:79: in 
 24s from mongomock.__version__ import __version__
 24s mongomock/__version__.py:1: in 
 24s import pkg_resources
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s __ ERROR collecting tests/test__client_api.py 
__
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.2jeup6d8/downtmp/build.egq/src/tests/test__client_api.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s tests/test__client_api.py:16: in 
 24s import mongomock
 24s mongomock/__init__.py:79: in 
 24s from mongomock.__version__ import __version__
 24s mongomock/__version__.py:1: in 
 24s import pkg_resources
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s  ERROR collecting tests/test__collection_api.py 

 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.2jeup6d8/downtmp/build.egq/src/tests/test__collection_api.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s tests/test__collection_api.py:15: in 
 24s import mongomock
 24s mongomock/__init__.py:79: in 
 24s from mongomock.__version__ import __version__
 24s mongomock/__version__.py:1: in 
 24s import pkg_resources
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s _ ERROR collecting tests/test__database_api.py 
_
 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.2jeup6d8/downtmp/build.egq/src/tests/test__database_api.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s tests/test__database_api.py:7: in 
 24s import mongomock
 24s mongomock/__init__.py:79: in 
 24s from mongomock.__version__ import __version__
 24s mongomock/__version__.py:1: in 
 24s import pkg_resources
 24s E   ModuleNotFoundError: No module named 'pkg_resources'
 24s  ERROR collecting tests/test__gridfs.py 

 24s ImportError while importing test module 
'/tmp/autopkgtest-lxc.2jeup6d8/downtmp/build.egq/src/tests/test__gridfs.py'.
 24s Hint: make sure your test modules/packages have valid Python names.
 24s Traceback:
 24s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
 24s return _bootstrap._gcd_import(name[level:], package, level)
 24s 

Bug#1040574: marked as done (python-qrcode: implicitly depends on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 19:43:57 +
with message-id 
and subject line Bug#1040574: fixed in python-qrcode 7.4.2-3
has caused the Debian Bug report #1040574,
regarding python-qrcode: implicitly depends on python3-pkg-resources
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.)


-- 
1040574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-qrcode
Version: 7.4.2-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainer,

your package implicitly depends on python3-pkg-resources for its autopkgtest,
which used to be provided through python3-pytest. However, pytest has dropped
that dependency, breaking your autopkgtest and possibly your package.

Note that pkg_resources is deprecated in favor of importlib.resources [1],
which is part of the Python Standard Library and has better performance.

Cheers
Timo

[1] https://docs.python.org/3/library/importlib.resources.html

- ---

Relevant excerpt from
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-qrcode/35451521/log.gz


 26s === FAILURES 
===
 26s _ ScriptTest.test_bad_factory 
__
 26s 
 26s self = 
 26s mock_stderr = 
 26s 
 26s @mock.patch("sys.stderr")
 26s def test_bad_factory(self, mock_stderr):
 26s >   self.assertRaises(SystemExit, main, "testtext --factory 
fish".split())
 26s 
 26s tests/test_script.py:68: 
 26s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 26s 
 26s def main(args=None):
 26s if args is None:
 26s args = sys.argv[1:]
 26s >   from pkg_resources import get_distribution
 26s E   ModuleNotFoundError: No module named 'pkg_resources'
 26s 
 26s /usr/lib/python3/dist-packages/qrcode/console_scripts.py:43: 
ModuleNotFoundError
 26s ___ ScriptTest.test_factory 

 26s 
 26s self = 
 26s mock_stdout = 
 26s 
 26s @mock.patch("sys.stdout")
 26s def test_factory(self, mock_stdout):
 26s >   main("testtext --factory svg".split())
 26s 
 26s tests/test_script.py:64: 
 26s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 26s 
 26s args = ['testtext', '--factory', 'svg']
 26s 
 26s def main(args=None):
 26s if args is None:
 26s args = sys.argv[1:]
 26s >   from pkg_resources import get_distribution
 26s E   ModuleNotFoundError: No module named 'pkg_resources'
 26s 
 26s /usr/lib/python3/dist-packages/qrcode/console_scripts.py:43: 
ModuleNotFoundError
 26s  ScriptTest.test_factory_drawer 

 26s 
 26s self = 
 26s mock_stderr = <_io.StringIO object at 0x7faec4596b90>
 26s 
 26s @mock.patch("sys.stderr", new_callable=io.StringIO)
 26s def test_factory_drawer(self, mock_stderr):
 26s >   main("testtext --factory svg --factory-drawer circle".split())
 26s 
 26s tests/test_script.py:98: 
 26s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 26s 
 26s args = ['testtext', '--factory', 'svg', '--factory-drawer', 'circle']
 26s 
 26s def main(args=None):
 26s if args is None:
 26s args = sys.argv[1:]
 26s >   from pkg_resources import get_distribution
 26s E   ModuleNotFoundError: No module named 'pkg_resources'
 26s 
 26s /usr/lib/python3/dist-packages/qrcode/console_scripts.py:43: 
ModuleNotFoundError
 26s __ ScriptTest.test_factory_drawer_bad 
__
 26s 
 26s self = 
 26s mock_stderr = <_io.StringIO object at 0x7faec4b97e20>
 26s 
 26s @mock.patch("sys.stderr", new_callable=io.StringIO)
 26s def test_factory_drawer_bad(self, mock_stderr):
 26s with self.assertRaises(SystemExit):
 26s >   main("testtext --factory svg --factory-drawer sobad".split())
 26s 
 26s tests/test_script.py:93: 
 26s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 26s 
 26s def main(args=None):
 26s if args is None:
 26s args = sys.argv[1:]
 26s >   from pkg_resources import get_distribution
 26s E   ModuleNotFoundError: No module named 'pkg_resources'
 26s 
 26s /usr/lib/python3/dist-packages/qrcode/console_scripts.py:43: 
ModuleNotFoundError
 26s _ ScriptTest.test_factory_drawer_none 
__
 26s 
 26s self = 
 26s mock_stderr = <_io.StringIO 

Processed: Bug#1040579 marked as pending in python-gflanguages

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040579 [src:python-gflanguages] python-gflanguages: implicitly depends on 
python3-pkg-resources
Added tag(s) pending.

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

Bug#1040579: marked as pending in python-gflanguages

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-gflanguages/-/commit/170fc0c19807b63e08069345adb7c0af8b74a608


Add missing depend on python3-pkg-resources

Closes: #1040579


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040579

Bug#1034565: marked as done (ftbfs tests fail on ppc64el and mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jul 2023 00:46:23 +0530
with message-id 
and subject line fixed in 0.23
has caused the Debian Bug report #1034565,
regarding ftbfs tests fail on ppc64el and mips64el
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.)


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

Package: ruby-prometheus-client-mmap
Version: 0.17.0+spec-1
Severity: serious
Control: forwarded -1 
https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/43


Version in testing is not affected as we did not have tests enabled.

Failures:

  1) Prometheus::Client::Helper::MmapedFile file does not exist creates 
a file with minimum initial size
 Failure/Error: expect(File.size(subject.filepath)).to 
eq(subject.send(:initial_mmap_file_size))


   expected: 4096
got: 16384

   (compared using ==)
 # ./spec/prometheus/client/helpers/mmaped_file_spec.rb:30:in 
`block (3 levels) in '


  2) Prometheus::Client::MmapedDict#initialize empty mmap'ed file is 
initialized with correct size
 Failure/Error: expect(File.size(tmp_file.path)).to 
eq(tmp_mmaped_file.send(:initial_mmap_file_size))


   expected: 4096
got: 16384

   (compared using ==)
 # ./spec/prometheus/client/mmaped_dict_spec.rb:19:in `block (4 
levels) in '


  3) Prometheus::Client::MmapedDict#initialize mmap'ed file that is 
above minimum size is initialized with the a page size

 Failure/Error: expect(tmp_file.size).to eq(4096);

   expected: 4096
got: 16384

   (compared using ==)
 # ./spec/prometheus/client/mmaped_dict_spec.rb:34:in `block (4 
levels) in '


Full build logs 
https://buildd.debian.org/status/fetch.php?pkg=ruby-prometheus-client-mmap=ppc64el=0.19.1-1=1681745611=0 
https://buildd.debian.org/status/fetch.php?pkg=ruby-prometheus-client-mmap=mips64el=0.19.1-1=1681745649=0


Forwarded upstream at 
https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/43


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


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

Control: fixed -1 0.23.1-3--- End Message ---

Processed: fixed in 0.23

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.23.1-3
Bug #1034565 [ruby-prometheus-client-mmap] ftbfs tests fail on ppc64el and 
mips64el
There is no source info for the package 'ruby-prometheus-client-mmap' at 
version '0.23.1-3' with architecture ''
Unable to make a source version for version '0.23.1-3'
Marked as fixed in versions 0.23.1-3.

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

Bug#1034565: fixed in 0.23

[Pirate Praveen]

Control: fixed -1 0.23.1-3

Bug#1040578: marked as pending in python-molotov

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-molotov/-/commit/867c94eb4a2f87c24a63df05d1acc9dd63f24147


Add missing depend on python3-pkg-resources

Closes: #1040578


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040578

Processed: Bug#1040578 marked as pending in python-molotov

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040578 [src:python-molotov] python-molotov: implicitly depends on 
python3-pkg-resources
Added tag(s) pending.

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

Processed: Bug#1040576 marked as pending in python-mongomock

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040576 [src:python-mongomock] python-mongomock: implicitly depends on 
python3-pkg-resources
Added tag(s) pending.

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

Bug#1040576: marked as pending in python-mongomock

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-mongomock/-/commit/2eceec91e76e6e09434f76abb8efa08e8b1fe0c4


Add missing depend on python3-pkg-resources

Closes: #1040576


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040576

Bug#1040574: marked as pending in python-qrcode

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-qrcode/-/commit/6862815ba5769403c7352eeade12d4d7ad9feace


Add missing depend on python3-pkg-resources

Closes: #1040574


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040574

Processed: Bug#1040574 marked as pending in python-qrcode

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040574 [src:python-qrcode] python-qrcode: implicitly depends on 
python3-pkg-resources
Added tag(s) pending.

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

Bug#1022957: golang-github-blynn-nex: diff for NMU version 0.0.0+git.2021.03.30.1a3320dab9-2.1

[Boyuan Yang]

Control: tags 1022957 + patch
Control: tags 1022957 + pending

Dear maintainer,

I've prepared an NMU for golang-github-blynn-nex (versioned as 
0.0.0+git.2021.03.30.1a3320dab9-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru 
golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog 
golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog
--- golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog
2022-11-01 08:33:32.0 -0400
+++ golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/changelog
2023-07-12 13:51:55.0 -0400
@@ -1,3 +1,11 @@
+golang-github-blynn-nex (0.0.0+git.2021.03.30.1a3320dab9-2.1) unstable; 
urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Mark package nex to conflict with package nvi
+due to file conflict of /usr/bin/nex. (Closes: #1022957)
+
+ -- Boyuan Yang   Wed, 12 Jul 2023 13:51:55 -0400
+
 golang-github-blynn-nex (0.0.0+git.2021.03.30.1a3320dab9-2) unstable; 
urgency=medium
 
   * Re-upload source-only.
diff -Nru 
golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control 
golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control
--- golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control  
2022-11-01 08:33:32.0 -0400
+++ golang-github-blynn-nex-0.0.0+git.2021.03.30.1a3320dab9/debian/control  
2023-07-12 13:51:40.0 -0400
@@ -20,6 +20,8 @@
  ${shlibs:Depends},
 Suggests:
  graphviz,
+Conflicts:
+ nvi,
 Description: lexer similar to Lex/Flex - cli
  Nex is a lexer similar to Lex/Flex that:
   * generates Go code instead of C code


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

Processed: golang-github-blynn-nex: diff for NMU version 0.0.0+git.2021.03.30.1a3320dab9-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1022957 + patch
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
Added tag(s) patch.
> tags 1022957 + pending
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
Added tag(s) pending.

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

Bug#1040837: [Pkg-rust-maintainers] Bug#1040837: rust-log: breaks API without coordination

[Fabian Grünbichler]

On Tue, Jul 11, 2023 at 01:47:53PM +0200, Jonas Smedegaard wrote:
> Source: rust-log
> Version: 0.4.19-2
> Severity: serious
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> rust-log 0.4.19-2 apparently removed upstream feature kv_unstable
> (according to inspection of source of that packaging release -
> related changelog entry does not mention that feature).
> 
> This change to upstream API was done without coordination with
> reverse dependencies, and breaks at least librust-async-std-dev
> and its 17 reverse dependencies.
> 
> Yes, I am aware that changelog entry indicates this being a temporary
> change, pending packages lingering in NEW queue.  Please don't release
> breaking changes without prior coordination with reverse dependencies
> (e.g. the changes that cause bug#1040702), and in cases that is not
> possible (e.g. when accidentally ending at bug#1040702) then please
> notify reverse dependencies e.g. using a bugreport with tag "affects".

This was by mistake, and not on purpose.

The feature in question is probably not a good candidate for packaging
though, given the lack of stability guarantees provided by upstream[0]:

> This module is unstable and breaking changes may be made at any time.
> See the tracking issue for more details.

The referenced tracking issue can be found here[1].

While the required crates (multiple ones from sval-rs/value-bag) are
being packaged (mostly done, pending a re-upload to NEW and review
there), I wonder whether enabling the feature was not a
mistake/premature in the first place.

I did a quick test with ratt with the attached diff applied, and except
for rust-sequoia-net (which fails for other reasons which are already
fixed in experimental and just need a re-upload of the version there to
unstable), building at least worked fine. I am not too familiar with
either async-std, nor the kv feature of log to say whether this approach
would be feasible - I'd be happy to hear your thoughts though! IMHO
keeping this unstable aspect out of the archive for the time being would
save us all from periodic breakage, with log itself (without the KV
feature) being rather widely used.

In a slightly related note, there will be two upcoming transitions that
will affect (rust) packages of yours (bindgen to 0.65, and toml to 0.7)
as part of updating rust-cargo to 0.70. Would you appreciate bugs with
patches filed before the transition starts, or do you want to handle
those on your own? You can find some details in the (WIP) tracking
issue[2]. bindgen should be pretty straight-forward, for toml we will
likely opt for a period of semver-suffixing since the versions do have
breaking changes where breakage is not detected at compile time.

0: https://docs.rs/log/latest/log/kv/index.html
1: https://github.com/rust-lang/log/issues/328
2: https://salsa.debian.org/rust-team/debcargo-conf/-/issues/48
diff --git a/rust-async-std-1.12.0/debian/changelog 
b/rust-async-std-1.12.0-patched/debian/changelog
index dfa43a8..5d6258f 100644
--- a/rust-async-std-1.12.0/debian/changelog
+++ b/rust-async-std-1.12.0-patched/debian/changelog
@@ -1,3 +1,9 @@
+rust-async-std (1.12.0-12.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+ -- Fabian Grünbichler   Wed, 12 Jul 2023 13:43:22 
+0200
+
 rust-async-std (1.12.0-12) unstable; urgency=medium
 
   * tighten autopkgtests
diff --git a/rust-async-std-1.12.0/debian/control 
b/rust-async-std-1.12.0-patched/debian/control
index 767ca01..84a3e66 100644
--- a/rust-async-std-1.12.0/debian/control
+++ b/rust-async-std-1.12.0-patched/debian/control
@@ -12,15 +12,12 @@ Build-Depends:
  librust-async-lock-2+default-dev ,
  librust-async-process-1+default-dev ,
  librust-crossbeam-utils-0.8+default-dev ,
- librust-femme-2+default-dev ,
  librust-futures-0.3+default-dev ,
  librust-futures-core-0.3+alloc-dev ,
  librust-futures-core-0.3+std-dev ,
  librust-futures-io-0.3+default-dev ,
  librust-futures-lite-1+default-dev ,
- librust-kv-log-macro-1+default-dev ,
  librust-log-0.4+default-dev ,
- librust-log-0.4+kv-unstable-dev ,
  librust-memchr-2+default-dev ,
  librust-once-cell-1+default-dev ,
  librust-pin-project-lite-0.2+default-dev ,
@@ -53,9 +50,7 @@ Depends:
  librust-futures-core-0.3+alloc-dev,
  librust-futures-io-0.3+default-dev,
  librust-futures-lite-1+default-dev,
- librust-kv-log-macro-1+default-dev,
  librust-log-0.4+default-dev,
- librust-log-0.4+kv-unstable-dev,
  librust-memchr-2+default-dev,
  librust-once-cell-1+default-dev,
  librust-pin-project-lite-0.2+default-dev,
diff --git 
a/rust-async-std-1.12.0-patched/debian/patches/disable-unstable-log-kv.diff 
b/rust-async-std-1.12.0-patched/debian/patches/disable-unstable-log-kv.diff
new file mode 100644
index 000..33b5de9
--- /dev/null
+++ b/rust-async-std-1.12.0-patched/debian/patches/disable-unstable-log-kv.diff
@@ -0,0 +1,77 @@
+Index: rust-async-std-1.12.0/Cargo.toml
+===
+--- 

Processed: Bug#1040568 marked as pending in weresync

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040568 [src:weresync] weresync: implicitly depends on python3-py
Added tag(s) pending.

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

Bug#1040568: marked as pending in weresync

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1040568 in weresync 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/weresync/-/commit/45c8041c7c9bb8a7f0954bdb3bfa3f1e922bf3c8


Use pytest, not py.test

Closes: #1040568


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040568

Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2

[Jeremy Bícha]

On Wed, Jul 12, 2023 at 1:16 PM Christoph Biedl
 wrote:
>
> Control: tags 1040924 moreinfo
>
> Jeremy Bícha wrote...
>
> > clevis-udisks2 depends on libblockdev-crypto2 which is no longer built
> > by libblockdev in Unstable. Please update the manual dependency to
> > libblockdev-crypto3
>
> I fail to understand what is happening here. Is this supposed to be a
> transition? Then it didn't quite follow the procedure as outlined in
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Yes, it's a transition. Sorry that it didn't follow the recommended procedure.

Thank you,
Jeremy Bícha

Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2

[Christoph Biedl]

Control: tags 1040924 moreinfo

Jeremy Bícha wrote...

> clevis-udisks2 depends on libblockdev-crypto2 which is no longer built
> by libblockdev in Unstable. Please update the manual dependency to
> libblockdev-crypto3

I fail to understand what is happening here. Is this supposed to be a
transition? Then it didn't quite follow the procedure as outlined in
https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Christoph


signature.asc
Description: PGP signature

Processed: Re: Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2

[Debian Bug Tracking System]

Processing control commands:

> tags 1040924 moreinfo
Bug #1040924 [clevis-udisks2] clevis-udisks2: Depends on NBS libblockdev-crypto2
Added tag(s) moreinfo.

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

Processed: tagging 1040924

[Debian Bug Tracking System]

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

> tags 1040924 + sid trixie
Bug #1040924 [clevis-udisks2] clevis-udisks2: Depends on NBS libblockdev-crypto2
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1040940: rmlint-gui fails to start: SyntaxError: source code cannot contain null bytes

[Julian Gilbey]

Package: rmlint-gui
Version: 2.9.0-2.4
Severity: grave

euler:~ $ rmlint --gui
  File "/tmp/.shredder-bootstrap.py.KFWS71", line 23

SyntaxError: source code cannot contain null bytes


The generated temporary source file has a null byte at the end of the
file.  This is quite possibly already fixed upstream.

Bug#1040524: libboost1.74-dev: g++-12 fails to compile interval.hpp on ppc64el: error: narrowing conversion

[Gianfranco Costamagna]

control: tags -1 patch fixed-upstream
control: forwarded -1 https://github.com/boostorg/interval/pull/30

Looks like upstream has a pull request fixing this issue.

G.

On Fri, 07 Jul 2023 11:25:45 +0200 Andreas Beckmann  wrote:

Package: libboost1.74-dev
Version: 1.74.0+ds1-21.1
Severity: serious

This is a regression from g++-11:

$ echo '#include ' | g++-11 -x c++ -c -
$ echo '#include ' | g++-12 -x c++ -c -
In file included from /usr/include/boost/numeric/interval/hw_rounding.hpp:28,
 from /usr/include/boost/numeric/interval.hpp:18,
 from :1:
/usr/include/boost/numeric/interval/detail/ppc_rounding_control.hpp:31:56: 
error: narrowing conversion of '1892273895866370' from 'long long unsigned 
int' to 'boost::long_long_type' {aka 'long long int'} [-Wnarrowing]
   31 | static const rounding_mode_struct mode_upward  = { 
0xFFF80002LL };
  |
^~~~
/usr/include/boost/numeric/interval/detail/ppc_rounding_control.hpp:32:56: 
error: narrowing conversion of '1892273895866371' from 'long long unsigned 
int' to 'boost::long_long_type' {aka 'long long int'} [-Wnarrowing]
   32 | static const rounding_mode_struct mode_downward= { 
0xFFF80003LL };
  |
^~~~
/usr/include/boost/numeric/interval/detail/ppc_rounding_control.hpp:33:56: 
error: narrowing conversion of '1892273895866368' from 'long long unsigned 
int' to 'boost::long_long_type' {aka 'long long int'} [-Wnarrowing]
   33 | static const rounding_mode_struct mode_to_nearest  = { 
0xFFF8LL };
  |
^~~~
/usr/include/boost/numeric/interval/detail/ppc_rounding_control.hpp:34:56: 
error: narrowing conversion of '1892273895866369' from 'long long unsigned 
int' to 'boost::long_long_type' {aka 'long long int'} [-Wnarrowing]
   34 | static const rounding_mode_struct mode_toward_zero = { 
0xFFF80001LL };
  |
^~~~

The same behavior is observable with libboost1.81-dev.


Andreas




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: libboost1.74-dev: g++-12 fails to compile interval.hpp on ppc64el: error: narrowing conversion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #1040524 [libboost1.74-dev] libboost1.74-dev: g++-12 fails to compile 
interval.hpp on ppc64el: error: narrowing conversion
Added tag(s) patch and fixed-upstream.
> forwarded -1 https://github.com/boostorg/interval/pull/30
Bug #1040524 [libboost1.74-dev] libboost1.74-dev: g++-12 fails to compile 
interval.hpp on ppc64el: error: narrowing conversion
Set Bug forwarded-to-address to 'https://github.com/boostorg/interval/pull/30'.

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

Processed: libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libutop-ocaml-dev
Bug #1040937 [libdune-ocaml-dev] libdune-ocaml-dev: Missing libdune-ocaml-dev-* 
Provides
Added indication that 1040937 affects libutop-ocaml-dev

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

Bug#1040937: libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides

[Adrian Bunk]

Package: libdune-ocaml-dev
Version: 3.9.0-2
Severity: serious
Control: affects -1 libutop-ocaml-dev

The following packages have unmet dependencies:
 libutop-ocaml-dev : Depends: libdune-ocaml-dev-v9190 but it is not installable

libdune-ocaml-dev does not have any libdune-ocaml-dev-* Provides.

Looking at the dependencies of libdune-ocaml-dev, the loss of
the libcsexp-ocaml-dev-* dependency (that is present in bookworm)
might also be a bug.

Bug#1040888: marked as done (rust-condure FTBFS on architectures with unsigned char)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 15:37:12 +
with message-id 
and subject line Bug#1040888: fixed in rust-condure 1.10.0-2
has caused the Debian Bug report #1040888,
regarding rust-condure FTBFS on architectures with unsigned char
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=rust-condure=ppc64el=1.10.0-1=1689116835=0

...
error[E0308]: mismatched types
   --> src/lib.rs:161:13
|
158 | if libc::getpwnam_r(
| arguments to this function are incorrect
...
161 | buf.as_mut_ptr() as *mut i8,
| ^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut u8`
   found raw pointer `*mut i8`
note: function defined here

error[E0308]: mismatched types
   --> src/lib.rs:188:13
|
185 | if libc::getgrnam_r(
| arguments to this function are incorrect
...
188 | buf.as_mut_ptr() as *mut i8,
| ^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut u8`
   found raw pointer `*mut i8`
note: function defined here

For more information about this error, try `rustc --explain E0308`.
error: could not compile `condure` due to 2 previous errors
...
--- End Message ---
--- Begin Message ---
Source: rust-condure
Source-Version: 1.10.0-2
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-condure 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jul 2023 15:14:13 +
Source: rust-condure
Architecture: source
Version: 1.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1040888
Changes:
 rust-condure (1.10.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package condure 1.10.0 from crates.io using debcargo 2.6.0
   * Fix build on systems with unsigned char (Closes: #1040888)
Checksums-Sha1:
 d3e4e7188fc162c23f44849169ea5c3caeca8bc5 3128 rust-condure_1.10.0-2.dsc
 cd80b5cf47cd1017fb5962573977e402bebd2a13 4396 
rust-condure_1.10.0-2.debian.tar.xz
 3375248b2d0cc36118e03539e4acbdea67e7d417 12246 
rust-condure_1.10.0-2_source.buildinfo
Checksums-Sha256:
 9bec061bb95ec122abb0a420f98f366e862cd3d6d4b12217f795c18c500848bb 3128 
rust-condure_1.10.0-2.dsc
 b2287aac63a3e309a688b492d42ea719ce49a0ad81ec0e83145f78a1e0fec3ea 4396 
rust-condure_1.10.0-2.debian.tar.xz
 4bf164f0e1d26541ecacb1e1b7745524345b3490c2fc42c5bb4c45033383dc18 12246 
rust-condure_1.10.0-2_source.buildinfo
Files:
 e59a7a668727a4fba196ec925e4e3e6d 3128 net optional rust-condure_1.10.0-2.dsc
 bd22baccb31d5feeef2f38ec7f2e5ee6 4396 net optional 
rust-condure_1.10.0-2.debian.tar.xz
 86687ee38605633617965739eded490b 12246 net optional 
rust-condure_1.10.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmSuxYwUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xt1Zg/5AT30cjM1iDe2DKX9FQ/53d2mBSw8
HQTy1B8nOazrUf9UlSINT29/u1+BjWkRqgjpZpbHp5l1CfRCGaYi7aeZ8JEpYXKw
ozg/606jm2rud+PVBsXzjSE/TolhWFNSZbyKSr9PtdlE0pgp5JdDpuWpRJf+SaCI
9YLyQPDSiZw8OcDrSJSnLq5a4Ky4Qpm4JTMTZ4U2ciBqHJKjkO1va/oJrDMC6o05
aPMPQl8wUiLnUX5/eiNUbo7shOzsBwM7eU0Q0V2BuuV1KZJtTm3/dzMJ4wLJXW7l
LQHCexiNm4HDR8bYVhzlwHr6QSUSe7ID7f5uUCWAHB6SPQLdKl6k4St24vtrGs9t
0h/ghPMC0leX8+nMq/++VDAcO/aYNONzGwJtRhVtnxojaNhUPd2Gl7mWFUk6nmWV
OLYoGjAWd2yNTx4HtlSIUMfBCQzZzak5yDPKECwCIJXvsg+FUGW/kiYZBpbXbfg9
pAE+RmtASWX2cZ27oQLtCkLasfPa1DBbBACFyb00dbfqCmoZnCz9kpC+ShyOigDN
2hHQbvbPYuXIPyTcwZnX+Rxi+f7zb1P+wiZsztUJpevZ3jMNxCcGdHj1WZxwxcsk
PsPkUHHIMbBMQV2Akqp/kYlCnXrCro/wERjBr7LdNVkLDl50nsbVTKIjwRwT9HNz
JqS4TPmCXMzS1cs=
=mTR+

Bug#1039685: marked as done (nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 15:37:04 +
with message-id 
and subject line Bug#1039685: fixed in nvidia-graphics-drivers-tesla 
525.125.06-1
has caused the Debian Bug report #1039685,
regarding nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.125.06-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jul 2023 16:56:19 +0200
Source: nvidia-graphics-drivers-tesla
Architecture: source
Version: 525.125.06-1
Distribution: unstable

Processed: Re: Bug#1031183: grub-installer: postinst fails if efivarfs cannot be mounted

[Debian Bug Tracking System]

Processing control commands:

> affects 1039710 grub-installer
Bug #1039710 [busybox-udeb] busybox-udeb: /var/log/syslog is empty
Added indication that 1039710 affects grub-installer

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

Bug#1036641: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1036641: fixed in gcc-12 12.3.0-3)

[Andreas Beckmann]

Please try to get this fixed in bookworm, too.

Thanks

Andreas

Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload

[Julian Andres Klode]

On Wed, Jul 12, 2023 at 10:05:03AM +0200, Julian Andres Klode wrote:
> Source: linux
> Version: 6.3.0-7.7
> Severity: grave
> Tags: security
> X-Debbugs-Cc: j...@debian.org
> 
> I know there's some work in progress but it appears we don't have a bug
> for it yet. I raised this yesterday in our weekly upstream shim/grub
> cabal meetings and Debian's current approach to sign modules with the
> same key and not bump ABI on every upload should be considered a bug.

FWIW, I'm adding this formally as a requirement to the shim-review
process in

https://github.com/rhboot/shim-review/pull/337

So that we do not accidentally accept submissions with this bug
anymore.
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1004253: marked as done (broken for BIND in stable)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 15:49:13 +0200
with message-id <79046a4c-f996-e175-b72e-ab3fa2107...@debian.org>
and subject line 
has caused the Debian Bug report #1004253,
regarding broken for BIND in stable
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.)


-- 
1004253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-bind-exporter
Version: 0.4.0+ds-1+b5
Severity: grave

It just does not work due to 
https://github.com/prometheus-community/bind_exporter/issues/96:

Jan 23 16:31:43 dns2 prometheus-bind-exporter[14800]: level=error 
ts=2022-01-23T15:31:43.292Z caller=bind_exporter.go:427 msg="Couldn't retrieve 
BIND stats" err="failed to unmarshal XML response: strconv.ParseUint: parsing 
\"-\": invalid syntax"

-- 
ciao,
Marco


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

Tags: wontfix

This bug was already fixed some time ago in bookworm (now stable). 
Bugfix will not be backported to oldstable.


Please consider upgrading to bookworm if you are still affected by it.


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

Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

[Michael Ablassmeier]

hi,

On Wed, Jul 12, 2023 at 01:21:26PM +, Sijmen Mulder wrote:
> Should this ben in stable yet? Running
> 
>   apt-get update &&
>   apt-get upgrade -y &&
>   apt-get install -y openjdk-17-jre-headless git
> 
> on a fresh debian:12 container yields
> 
> ...
> Setting up git (1:2.39.2-1.1) ...
> Setting up ca-certificates-java (20230103) ...
> Exception in thread "main" java.lang.InternalError: Error loading 
> java.security file

same here, our internal CI tests fail due to a package pulling JRE
and failure during install:

> [2023-07-12 15:10:21] default: Setting up ca-certificates-java (20230103) 
> ...
> [2023-07-12 15:10:21] default: Exception in thread "main" 
> java.lang.InternalError: Error loading java.security file
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.Security.initialize(Security.java:106)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.Security$1.run(Security.java:84)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.Security$1.run(Security.java:82)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.Security.(Security.java:82)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.ProviderList.(ProviderList.java:178)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.Providers.(Providers.java:55)
> [2023-07-12 15:10:21] default:at 
> java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156)
> [2023-07-12 15:10:21] default:at 
> java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193)
> [2023-07-12 15:10:21] default:at 
> org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50)
> [2023-07-12 15:10:21] default:at 
> org.debian.security.UpdateCertificates.(UpdateCertificates.java:65)
> [2023-07-12 15:10:21] default:at 
> org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51)
> [2023-07-12 15:10:21] default: dpkg: error processing package 
> ca-certificates-java (--configure):
> [2023-07-12 15:10:21] default:  installed ca-certificates-java package 
> post-installation script subprocess returned error exit status 1
> [2023-07-12 15:10:21] default: dpkg: dependency problems prevent 
> configuration of openjdk-17-jre-headless:amd64:
> [2023-07-12 15:10:21] default:  openjdk-17-jre-headless:amd64 depends on 
> ca-certificates-java (>= 20190405~); however:
> [2023-07-12 15:10:21] default:   Package ca-certificates-java is not 
> configured yet.

bye,
- michael

Bug#1029412: marked as done (rt-extension-resetpassword: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 13:28:48 +
with message-id 
and subject line Bug#1029412: fixed in rt-extension-resetpassword 1.12-3
has caused the Debian Bug report #1029412,
regarding rt-extension-resetpassword: autopkgtest failure
to be marked as done.

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

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


-- 
1029412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-extension-resetpassword
Version: 1.07-1
Severity: serious

https://ci.debian.net/packages/r/rt-extension-resetpassword/unstable/amd64/

...
autopkgtest [12:13:07]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 
exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/ResetPassword.pm in @INC (you 
may need to install the RT::Extension::ResetPassword module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/ResetPassword.pm in @INC (you 
may need to install the RT::Extension::ResetPassword module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist
# Looks like you failed 4 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install 
the RT::Extension::ResetPassword module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 1 -  /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 
produced no (non-whitelisted) output
# Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install 
the RT::Extension::ResetPassword module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/4 subtests 

Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) 
Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
Files=1, Tests=4,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.11 cusr  0.01 
csys =  0.14 CPU)
Result: FAIL
autopkgtest [12:13:08]: test autodep8-perl: ---]
autopkgtest [12:13:08]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -
autodep8-perlFAIL non-zero exit status 1
autopkgtest [12:13:08]: test autodep8-perl:  - - - - - - - - - - stderr - - - - 
- - - - - -

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 
exited 

Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

[Sijmen Mulder]

Hi,

On Wed, 12 Jul 2023 12:00:50 +0200 Matthias Klose  wrote:
> Version: 20230710
>
> should be fixed now.

Should this ben in stable yet? Running

  apt-get update &&
  apt-get upgrade -y &&
  apt-get install -y openjdk-17-jre-headless git

on a fresh debian:12 container yields

...
Setting up git (1:2.39.2-1.1) ...
Setting up ca-certificates-java (20230103) ...
Exception in thread "main" java.lang.InternalError: Error loading 
java.security file
at java.base/java.security.Security.initialize(Security.java:106)
at java.base/java.security.Security$1.run(Security.java:84)
at java.base/java.security.Security$1.run(Security.java:82)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at java.base/java.security.Security.(Security.java:82)
at 
java.base/sun.security.jca.ProviderList.(ProviderList.java:178)
at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96)
at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at 
java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93)
at java.base/sun.security.jca.Providers.(Providers.java:55)
at 
java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156)
at 
java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193)
at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50)
at 
org.debian.security.UpdateCertificates.(UpdateCertificates.java:65)
at 
org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51)
dpkg: error processing package ca-certificates-java (--configure):
 installed ca-certificates-java package post-installation script subprocess 
returned error exit status 1

This is my minimal repro, these two packages together. Installing just
ca-certificates-java by itself doesn't yield the issue.

Sijmen


smime.p7s
Description: S/MIME cryptographic signature

Bug#1040927: redmine: bashism in postinst script

[Jörg-Volker Peetz]

Package: redmine
Version: 5.0.4-7
Severity: serious

Dear Maintainer,

two bashisms in the postinst script in lines 7 and 57: `if [[ ...`
lead to message

  /var/lib/dpkg/info/redmine.postinst: 7: [[: not found

and

  /var/lib/dpkg/info/redmine.postinst: 57: [[: not found

Probably not what is intended.

Regards,
Jörg.

Bug#1029408: marked as done (rt-extension-assetautoname: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 12:50:41 +
with message-id 
and subject line Bug#1029408: fixed in rt-extension-assetautoname 0.05-5
has caused the Debian Bug report #1029408,
regarding rt-extension-assetautoname: autopkgtest failure
to be marked as done.

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

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


-- 
1029408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-extension-assetautoname
Version: 0.05-2
Severity: serious

https://ci.debian.net/packages/r/rt-extension-assetautoname/unstable/amd64/

...
autopkgtest [12:08:48]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [12:08:48]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 
exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/AssetAutoName.pm in @INC (you 
may need to install the RT::Extension::AssetAutoName module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/AssetAutoName.pm in @INC (you 
may need to install the RT::Extension::AssetAutoName module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist
# Looks like you failed 4 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install 
the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 1 -  /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 
produced no (non-whitelisted) output
# Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install 
the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/4 subtests 

Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) 
Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
Files=1, Tests=4,  0 wallclock secs ( 0.01 usr  0.00 sys +  0.07 cusr  0.01 
csys =  0.09 CPU)
Result: FAIL
autopkgtest [12:08:49]: test autodep8-perl: ---]
autopkgtest [12:08:49]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -
autodep8-perlFAIL non-zero exit status 1
autopkgtest [12:08:49]: test autodep8-perl:  - - - - - - - - - - stderr - - - - 
- - - - 

Bug#1040626: gcc-13-cross-mipsen ftbfs in unstable

[Emanuele Rocca]

Hi,

On 2023-07-08 08:43, Matthias Klose wrote:
> [...]
> checking linker soname option... yes
> checking linker --demangle support... no
> checking linker plugin support... 0
> checking assembler for explicit relocation support... no
> checking assembler for -mno-shared support... no
> checking assembler for .gnu_attribute support... no
> checking assembler for .module support... no
> configure: error: Requesting --with-fp-32= requires assembler support for 
> .module.
> make[4]: *** [Makefile:4569: configure-gcc] Error 1
> make[4]: Leaving directory '/<>/gcc/build'
> make[3]: *** [Makefile:1042: all] Error 2
> make[3]: Leaving directory '/<>/gcc/build'

FTR it seems that the issue affects arm64 and ppc64el but not other
architectures:
https://buildd.debian.org/status/package.php?p=gcc%2d13%2dcross%2dmipsen

For example, some interesting differences on the mips64el build: 

checking linker --demangle support... yes
checking linker plugin support... 2
checking assembler for explicit relocation support... yes
checking assembler for -mno-shared support... yes
checking assembler for .gnu_attribute support... yes
checking assembler for .module support... yes

Bug#1040179: marked as done (rmlint-gui: invalid Python version number breaks other packages)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 12:34:43 +
with message-id 
and subject line Bug#1040179: fixed in rmlint 2.9.0-2.4
has caused the Debian Bug report #1040179,
regarding rmlint-gui: invalid Python version number breaks other packages
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.)


-- 
1040179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spyder
Version: 5.4.2+ds-5
Severity: normal
X-Debbugs-Cc: mhaag85...@gmail.com

Dear Maintainer,

Ran $spyder --reset but, still get the missing dependency message.


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

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

Versions of packages spyder depends on:
ii  python3 3.11.2-1+b1
ii  python3-spyder  5.4.2+ds-5

spyder recommends no packages.

Versions of packages spyder suggests:
pn  python3-spyder-unittest  

Versions of packages python3-spyder depends on:
ii  ipython3   8.5.0-4
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-mathjax  2.7.9+dfsg-1
ii  pyflakes3  2.5.0-1
ii  pylint 2.16.2-2
ii  python33.11.2-1+b1
ii  python3-atomicwrites   1.4.1-1
ii  python3-autopep8   2.0.1-1
ii  python3-chardet5.1.0+dfsg-2
ii  python3-cloudpickle2.2.0-1
ii  python3-cookiecutter   1.7.3-3
ii  python3-diff-match-patch   20200713-2
ii  python3-docutils   0.19+dfsg-6
ii  python3-flake8 5.0.4-4
ii  python3-intervaltree   3.0.2-1.1
ii  python3-ipython8.5.0-4
ii  python3-jedi   0.18.2-1
ii  python3-jellyfish  0.8.9-1+b4
ii  python3-jsonschema 4.10.3-1
ii  python3-keyring23.9.3-2
ii  python3-mccabe 0.7.0-1
ii  python3-nbconvert  6.5.3-3
ii  python3-numpydoc   1.5.0-1
ii  python3-parso  0.8.3-1
ii  python3-pexpect4.8.0-4
ii  python3-pickleshare0.7.5-5
ii  python3-pkg-resources  66.1.1-1
ii  python3-psutil 5.9.4-1+b1
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.2.3-3
ii  python3-pygments   2.14.0+dfsg-1
ii  python3-pylint-venv2.3.0-2
ii  python3-pyls-spyder0.4.0-2
ii  python3-pylsp  1.7.1-1
ii  python3-pylsp-black1.2.1-2
ii  python3-pyqt5  5.15.9+dfsg-1
ii  python3-pyqt5.qtwebengine  5.15.6-1
ii  python3-qdarkstyle 3.1+ds1-1
ii  python3-qstylizer  0.2.2-1
ii  python3-qtawesome  1.2.2+dfsg-1
ii  python3-qtconsole  5.4.0-1
ii  python3-qtpy   2.3.0-1
ii  python3-rope   1.7.0-1
ii  python3-rtree  1.0.1-1
ii  python3-setuptools 66.1.1-1
ii  python3-sphinx 5.3.0-4
ii  python3-spyder-kernels 2.4.2-1
ii  python3-textdistance   4.5.0-1
ii  python3-three-merge0.1.1-4
ii  python3-watchdog   2.2.1-1
ii  python3-xdg0.28-2
ii  python3-zmq24.0.1-4+b1
ii  spyder-common  5.4.2+ds-5
ii  yapf3  0.32.0-1

python3-spyder recommends no packages.

Versions of packages python3-spyder suggests:
pn  cython3 
ii  python3-matplotlib  3.6.3-1+b1
ii  python3-numpy   1:1.24.2-1
ii  python3-pandas  1.5.3+dfsg-2
ii  python3-pil 9.4.0-1.1+b1
ii  python3-scipy   1.10.1-2
ii  python3-sympy   1.11.1-1

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.36-9
ii  libgcc-s1 12.2.0-14
ii  libpython3.11 3.11.2-6
ii  libqt5core5a [qtbase-abi-5-15-8]  5.15.8+dfsg-11
ii  libqt5dbus5   5.15.8+dfsg-11
ii  libqt5designer5   5.15.8-2
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5help5   5.15.8-2
ii  libqt5network55.15.8+dfsg-11
ii  libqt5printsupport5   5.15.8+dfsg-11
ii  libqt5test5   5.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5xml55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  python3   3.11.2-1+b1
ii  python3-pyqt5.sip 

Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2

[Jeremy Bícha]

Package: clevis-udisks2
Version: 19-2
Severity: serious

clevis-udisks2 depends on libblockdev-crypto2 which is no longer built
by libblockdev in Unstable. Please update the manual dependency to
libblockdev-crypto3

Thank you,
Jeremy Bícha

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

[Mathias Gibbens]

  Andreas, thanks for the report, and Richard, thanks for your work as
well. I think the changes look good, and if there's no other concerns
I'll merge the salsa MR, and upload a new version to unstable. Once
that's done, I'll also file a bug for uploading the updated version to
stable-proposed-updates; I know the deadline for the first bookworm
point release is this weekend, so it might get in for 12.1.

Mathias


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

Bug#1040541: marked as done (elpi FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 11:05:09 +
with message-id 
and subject line Bug#1040541: fixed in elpi 1.16.10-3
has caused the Debian Bug report #1040541,
regarding elpi FTBFS on i386
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=elpi=i386=1.16.10-2=1688713585=0

...
RUNNING  sepcomp1 (simple separate compilation)  dune
KO   sepcomp1 (simple separate compilation)  dune
RUNNING  sepcomp2 (simple separate compilation)  dune
KO   sepcomp2 (simple separate compilation)  dune
RUNNING  sepcomp3 (separate compilation double naming) dune
KO   sepcomp3 (separate compilation double naming) dune
RUNNING  sepcomp4 (separate compilation double naming) dune
KO   sepcomp4 (separate compilation double naming) dune
RUNNING  sepcomp5 (separate compilation different processes (step 1)) dune
KO   sepcomp5 (separate compilation different processes (step 1)) dune
RUNNING  sepcomp6 (separate compilation different processes (step 2)) dune
KO   sepcomp6 (separate compilation different processes (step 2)) dune
RUNNING  sepcomp_perf (separate compilation perf)dune
KO   sepcomp_perf (separate compilation perf)dune
...
--
Tests: 155
Passed: 148
Failed: 7
Skipped: 0
--
Log of the first failure: _log/dune+sepcomp1.log
--
executable: dune
args: exec tests/sources//sepcomp1.exe -- -I src/
Error: Thread.create: Resource temporarily unavailable
--
End log of the first failure: _log/dune+sepcomp1.log
--
make[2]: *** [Makefile:84: tests] Error 1
--- End Message ---
--- Begin Message ---
Source: elpi
Source-Version: 1.16.10-3
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated elpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 12:22:35 +0200
Source: elpi
Architecture: source
Version: 1.16.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040541
Changes:
 elpi (1.16.10-3) unstable; urgency=medium
 .
   * Team upload
   * Force STACK to a higher value for tests (Closes: #1040541)
Checksums-Sha1:
 2877dc5f0a13f294435250ff123882a172f64bc0 2207 elpi_1.16.10-3.dsc
 dcd0bbaa4b62d97aeded91c97e7eb4de548a2494 4244 elpi_1.16.10-3.debian.tar.xz
Checksums-Sha256:
 f91c385cb89a1dbc393640f6805bd9d9cd14a1d19b13784836c05ced466cfdc3 2207 
elpi_1.16.10-3.dsc
 3e3aa459775050f2f066cec0f5d6d4b3260c8af292a091ffc1e904f2fc25ce0f 4244 
elpi_1.16.10-3.debian.tar.xz
Files:
 0da8310d6c34fa4b6d9ee63e0f0c0380 2207 ocaml optional elpi_1.16.10-3.dsc
 12d6611dd925391ea3df7e36b347302a 4244 ocaml optional 
elpi_1.16.10-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSugI4SHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBscEH/1jYQCzzKrzY2cAgd7YLPzyim9jjLfDE
aRqI1ue4F8Gaw6aM8ezzE5QdEK3SYSX1BemaivifDNu69ISVfceLQIAaZow41/cR
GhwDG5WkONU60q4kyf9lOSFK7PprluakpGA6KaZA1MK0mahjkfeMvTW+Y9OzyWYo
Bql2oOLSHcPkEwtaKIc8V8dSpTqOG6vPEy7MLjK2vdZer75K7cqO9R7NI/xjpSn4
1OjI3P+eV5Fjjse/G8cc6VCyhtcflEh3o2wCzyFAddi3aXO+CCIgl3WkgdzykP6P
87P8b1Rg2onwtCkht24lkMovd/BNmuy9IU/uYP7Ig1Hhw56cPmsl5sY=
=M0Vk
-END PGP SIGNATURE End Message ---

Bug#1000120: checkit-tiff: Patch series for new upstream release dropping dependency on pcre3

[Elias Oltmanns]

Source: checkit-tiff
Version: 0.4.2-1
Followup-For: Bug #1000120
X-Debbugs-Cc: oltma...@zib.de
Control: tags -1 patch

Dear Maintainer,

please consider reviewing the attached patches for a new upstream
version of checkit-tiff. This would fix this bug flagged serious and
should prevent the tool from dropping out of Debian testing.

Thank you very much in advance for your assistance,

Elias
>From 634e808f1ac76ecdc3830e6691a1e240855ec359 Mon Sep 17 00:00:00 2001
From: Elias Oltmanns 
Date: Tue, 20 Jun 2023 18:57:42 +0200
Subject: [PATCH 01/10] Switch to new upstream repository

Closes: #969162
---
 debian/control   | 2 +-
 debian/copyright | 4 ++--
 debian/watch | 5 +++--
 3 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/debian/control b/debian/control
index d4dc58a..f978411 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Build-Depends: debhelper-compat (= 13),
 Standards-Version: 4.6.0
 Vcs-Browser: https://salsa.debian.org/debian-phototools-team/checkit-tiff
 Vcs-Git: https://salsa.debian.org/debian-phototools-team/checkit-tiff.git
-Homepage: https://github.com/SLUB-digitalpreservation/checkit_tiff
+Homepage: https://git.fsfe.org/art1pirat/checkit_tiff
 Rules-Requires-Root: no
 
 Package: checkit-tiff
diff --git a/debian/copyright b/debian/copyright
index 7903d4f..c233c16 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,10 +1,10 @@
 Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: checkit_tiff
 Upstream-Contact: Andreas Romeyke 
-Source: https://github.com/SLUB-digitalpreservation/checkit_tiff/releases
+Source: https://git.fsfe.org/art1pirat/checkit_tiff/releases
 
 Files: *
-Copyright: 2015-2016 Andreas Romeyke 
+Copyright: 2015-2023 Andreas Romeyke 
code is based on parts of libtiff:
1988-1997 Sam Leffler
1991-1997 Silicon Graphics, Inc.
diff --git a/debian/watch b/debian/watch
index f5dc74f..084fdfe 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,4 @@
 version=4
-
-https://github.com/SLUB-digitalpreservation/checkit_tiff/tags (?:.*?/)?v?(\d[\d.]*)\.tar\.gz
+opts="mode=git,filenamemangle=s%.*/v(@ANY_VERSION@)$%@PACKAGE@-$1%" \
+https://git.fsfe.org/art1pirat/checkit_tiff.git \
+^refs/tags/v(\d+(?:\.\d+)*)$
-- 
2.39.2

>From ea0a150b06f4529d8e638f197bbdde4208c94f95 Mon Sep 17 00:00:00 2001
From: Elias Oltmanns 
Date: Mon, 26 Jun 2023 18:50:24 +0200
Subject: [PATCH 02/10] Update build dependencies

Closes: #1000120
---
 debian/control | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index f978411..80cfc00 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,12 @@ Section: science
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
-   libpcre3-dev
+   dh-cmake,
+   dh-cmake-compat (= 1),
+   libpcre2-dev,
+   libdata-printer-perl,
+   libfile-slurp-perl,
+   libtest-base-perl
 Standards-Version: 4.6.0
 Vcs-Browser: https://salsa.debian.org/debian-phototools-team/checkit-tiff
 Vcs-Git: https://salsa.debian.org/debian-phototools-team/checkit-tiff.git
-- 
2.39.2

>From 2f84fc914eda967da2c2bf7f3246b158551c6da2 Mon Sep 17 00:00:00 2001
From: Elias Oltmanns 
Date: Wed, 28 Jun 2023 11:53:18 +0200
Subject: [PATCH 03/10] Build in directory "build" as expected by upstream test
 code

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 879abd8..92b6797 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-	dh $@ --sourcedirectory=src --buildsystem=cmake
+	dh $@ --sourcedirectory=src --builddirectory=build --buildsystem=cmake
 
 override_dh_install:
 	dh_install
-- 
2.39.2

>From 5adaaa86432a449ea6bb6b3a327336c11571dea3 Mon Sep 17 00:00:00 2001
From: Elias Oltmanns 
Date: Fri, 30 Jun 2023 18:47:48 +0200
Subject: [PATCH 04/10] Enforce non-parallel build preventing interference
 between tests

---
 debian/rules | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 92b6797..6f249fb 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,8 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-	dh $@ --sourcedirectory=src --builddirectory=build --buildsystem=cmake
+	dh $@ --sourcedirectory=src --builddirectory=build \
+		--no-parallel --buildsystem=cmake
 
 override_dh_install:
 	dh_install
-- 
2.39.2

>From c9c9d596d1b2307e68bb2f3647a50c8e6dd92657 Mon Sep 17 00:00:00 2001
From: Elias Oltmanns 
Date: Fri, 30 Jun 2023 20:07:33 +0200
Subject: [PATCH 05/10] Disable fortify from hardening feature area due to
 failing test

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 6f249fb..7853760 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,6 @@
 

Processed: checkit-tiff: Patch series for new upstream release dropping dependency on pcre3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1000120 [src:checkit-tiff] checkit-tiff: depends on obsolete pcre3 library
Added tag(s) patch.

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

Processed: bug 1040541 is forwarded to https://github.com/LPCIC/elpi/issues/187

[Debian Bug Tracking System]

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

> forwarded 1040541 https://github.com/LPCIC/elpi/issues/187
Bug #1040541 [src:elpi] elpi FTBFS on i386
Set Bug forwarded-to-address to 'https://github.com/LPCIC/elpi/issues/187'.
> thanks
Stopping processing here.

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

Bug#1040825: marked as done (crowbar FTBFS on bytecode architectures)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 10:05:50 +
with message-id 
and subject line Bug#1040825: fixed in crowbar 0.2.1-4
has caused the Debian Bug report #1040825,
regarding crowbar FTBFS on bytecode architectures
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=crowbar=armel=0.2.1-3=1689059725=0

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) 
"usr/lib/ocaml/crowbar/*.cmxs" (tried in ., debian/tmp)

dh_install: warning: libcrowbar-ocaml missing files: 
usr/lib/ocaml/crowbar/*.cmxs
dh_install: warning: Cannot find (any matches for) "usr/lib/ocaml/crowbar/*.a" 
(tried in ., debian/tmp)

dh_install: warning: libcrowbar-ocaml-dev missing files: 
usr/lib/ocaml/crowbar/*.a
dh_install: warning: Cannot find (any matches for) 
"usr/lib/ocaml/crowbar/*.cmx" (tried in ., debian/tmp)

dh_install: warning: libcrowbar-ocaml-dev missing files: 
usr/lib/ocaml/crowbar/*.cmx
dh_install: warning: Cannot find (any matches for) 
"usr/lib/ocaml/crowbar/*.cmxa" (tried in ., debian/tmp)

dh_install: warning: libcrowbar-ocaml-dev missing files: 
usr/lib/ocaml/crowbar/*.cmxa
dh_install: error: missing files, aborting
make: *** [debian/rules:7: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: crowbar
Source-Version: 0.2.1-4
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated crowbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 11:41:51 +0200
Source: crowbar
Architecture: source
Version: 0.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040825
Changes:
 crowbar (0.2.1-4) unstable; urgency=medium
 .
   * Team upload
   * Fix FTBFS on bytecode architectures (Closes: #1040825)
Checksums-Sha1:
 0701f4d453a41c6f97d942bb878bdd8c593e7cc2 2089 crowbar_0.2.1-4.dsc
 f3be7519454c1cd5c407c634cc2a49307abd8eb7 2428 crowbar_0.2.1-4.debian.tar.xz
Checksums-Sha256:
 51a9e79cfb4edd0dd8262f745fa4c23f63b5ba0416399a20c154718268bb502c 2089 
crowbar_0.2.1-4.dsc
 8ea88128171f0fa4ed21676b500c7294348227f43b1becc4ae362b9537a1ae32 2428 
crowbar_0.2.1-4.debian.tar.xz
Files:
 04ff9cd362eeefbc1e469bcbbbc37dd3 2089 ocaml optional crowbar_0.2.1-4.dsc
 38d4e11852a3d5ae26c45f5fbf198c08 2428 ocaml optional 
crowbar_0.2.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSudtASHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBZSEIAIo9uB9yUDwRBb5dXOSxC6uxv5Ue12Qw
lFZhuBVMAYeoO/SbGJYwuH9xC7igURj/0LiAMpH4hFdSrNZr9iiroNuDf6TvgmXj
38iZhmRH/SbPW4+z5+8u8gn1+5wiS1Y3ujH+NjVLaqYUHUilA+Hl1rGgHsJBr3v5
t/f8XGPS0QVLMR0LHylCgugwJw9Hl7SNG6fr5mz2I1A4DaDSIXlPhXaLAXwZrQcj
pGjKvPWzA0v40RSsOUtCMWTR0xZcL55QzdHDuteG0ZedkxwuQTWYC6sBmdctWOX9
bDdUy7ZORYdoGzhir4KnTcpPHgJu8WWMHEOBOLVxfndGD3ytIdkCUUM=
=FYaB
-END PGP SIGNATURE End Message ---

Bug#1037478: marked as done (ca-certificates-java: Loop in the execution of the trigger)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 12:05:44 +0200
with message-id <1b3cf06a-6e00-e83f-b0f3-97d46e1f7...@debian.org>
and subject line Re: ca-certificates-java: Loop in the execution of the trigger
has caused the Debian Bug report #1037478,
regarding ca-certificates-java: Loop in the execution of the trigger
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.)


-- 
1037478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20230103
Severity: serious

Hello,

While updating today, I got the following error:

dpkg: boucle détectée durant le traitement des actions différées :
 listes des paquets qui en sont responsables (normalement) :
  ca-certificates-java -> ca-certificates-java
 paquets bloqués par le traitement impossible d'actions différées requises :
  ca-certificates-java: update-ca-certificates-java: /usr/lib/jvm
  libc-bin: ldconfig
  dictionaries-common: aspell-autobuildhash

There seems to be a loop in the trigger execution

Kind regards
Laurent Bigonville


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

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

Versions of packages ca-certificates-java depends on:
ii  ca-certificates   20230311
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.19+7-1

ca-certificates-java recommends no packages.

ca-certificates-java suggests no packages.

-- Configuration Files:
/etc/default/cacerts [Errno 13] Permission non accordée: '/etc/default/cacerts'

-- no debconf information
--- End Message ---
--- Begin Message ---

Version: 20230710

Fixed now.--- End Message ---

Bug#1037478: ca-certificates-java: Loop in the execution of the trigger

[Matthias Klose]

Version: 20230710

Fixed now.

Bug#929685: ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency

[Matthias Klose]

Version. 20230710

Fixed now.

Bug#1030129: marked as done (ca-certificates-java - Fails to install: Error loading java.security file)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 12:00:50 +0200
with message-id 
and subject line Re: ca-certificates-java - Fails to install: Error loading 
java.security file
has caused the Debian Bug report #1030129,
regarding ca-certificates-java - Fails to install: Error loading java.security 
file
to be marked as done.

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

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


-- 
1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20230103
Severity: serious

ca-certificates-java fails to install with all dependencies fullfilled:

| Setting up ca-certificates-java (20230103) ...
| Exception in thread "main" java.lang.InternalError: Error loading 
java.security file
|   at java.base/java.security.Security.initialize(Security.java:105)
|   at java.base/java.security.Security.lambda$static$0(Security.java:84)
|   at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
|   at java.base/java.security.Security.(Security.java:83)
|   at java.base/sun.security.jca.ProviderList.(ProviderList.java:179)
|   at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96)
|   at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94)
|   at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:319)
|   at 
java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93)
|   at java.base/sun.security.jca.Providers.(Providers.java:55)
|   at 
java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156)
|   at 
java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193)
|   at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50)
|   at 
org.debian.security.UpdateCertificates.(UpdateCertificates.java:65)
|   at 
org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51)
| dpkg: error processing package ca-certificates-java (--configure):
|  installed ca-certificates-java package post-installation script subprocess 
returned error exit status 1
| dpkg: dependency problems prevent configuration of 
openjdk-21-jre-headless:arm64:
|  openjdk-21-jre-headless:arm64 depends on ca-certificates-java (>= 
20190405~); however:
|   Package ca-certificates-java is not configured yet.
| 
| dpkg: error processing package openjdk-21-jre-headless:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of openjdk-21-jre:arm64:
|  openjdk-21-jre:arm64 depends on openjdk-21-jre-headless (= 21~7ea-1); 
however:
|   Package openjdk-21-jre-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jre:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of 
openjdk-21-jdk-headless:arm64:
|  openjdk-21-jdk-headless:arm64 depends on openjdk-21-jre-headless (= 
21~7ea-1); however:
|   Package openjdk-21-jre-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jdk-headless:arm64 (--configure):
|  dependency problems - leaving unconfigured
| dpkg: dependency problems prevent configuration of openjdk-21-jdk:arm64:
|  openjdk-21-jdk:arm64 depends on openjdk-21-jre (= 21~7ea-1); however:
|   Package openjdk-21-jre:arm64 is not configured yet.
|  openjdk-21-jdk:arm64 depends on openjdk-21-jdk-headless (= 21~7ea-1); 
however:
|   Package openjdk-21-jdk-headless:arm64 is not configured yet.
| 
| dpkg: error processing package openjdk-21-jdk:arm64 (--configure):
|  dependency problems - leaving unconfigured
--- End Message ---
--- Begin Message ---

Version: 20230710

should be fixed now.--- End Message ---

Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

[Matthias Klose]

Version: 20230710

should be fixed now.

Bug#1040538: marked as done (ocaml-alcotest FTBFS on bytecode architectures)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:51:34 +
with message-id 
and subject line Bug#1040538: fixed in ocaml-alcotest 1.7.0-2
has caused the Debian Bug report #1040538,
regarding ocaml-alcotest FTBFS on bytecode architectures
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.)


-- 
1040538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-alcotest
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/mirage/alcotest/issues/391

https://buildd.debian.org/status/logs.php?pkg=ocaml-alcotest=1.7.0-1

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dune runtest -p alcotest
(cd _build/default/examples && ./floats.exe)
Testing `Float tests'.
This run has ID `W7QV3WZQ'.

  [OK]  Edge cases0   NaN.
  [OK]  Edge cases1   ∞.
  [OK]  Other floats  0   others.

Full test results in 
`/<>/_build/default/examples/_build/_tests/Float tests'.
Test Successful in 0.015s. 3 tests run.
(cd _build/default/examples && ./simple.exe)
Testing `Utils'.
This run has ID `EK5J5GJU'.

  [OK]  string-case0   Lower case.
  [OK]  string-case1   Capitalization.
  [OK]  string-concat  0   String mashing.
  [OK]  list-concat0   List mashing.

Full test results in 
`/<>/_build/default/examples/_build/_tests/Utils'.
Test Successful in 0.003s. 4 tests run.
File "test/e2e/alcotest/source_code_position/with-position.expected", line 1, 
characters 0-0:
(cd _build/default && /usr/bin/diff -u 
test/e2e/alcotest/source_code_position/with-position.expected 
test/e2e/alcotest/source_code_position/with-position.processed)
--- test/e2e/alcotest/source_code_position/with-position.expected   
2023-07-06 10:57:48.119001551 +
+++ test/e2e/alcotest/source_code_position/with-position.processed  
2023-07-06 10:58:46.188167901 +
@@ -8,7 +8,6 @@
 │ [FAIL]to_test  0   capitalise.   
│
 
└──┘
 ASSERT strings
-File "test/e2e/alcotest/source_code_position/test_source_code_position.ml", 
line 24, character 2:
 FAIL strings
 
Expected: `"A"'
@@ -24,7 +23,6 @@
 │ [FAIL]to_test  1   double all.   
│
 
└──┘
 ASSERT int lists 1
-File "test/e2e/alcotest/source_code_position/test_source_code_position.ml", 
line 28, character 2:
 FAIL int lists 1
 
Expected: `[1]'
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: ocaml-alcotest
Source-Version: 1.7.0-2
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocaml-alcotest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 11:25:54 +0200
Source: ocaml-alcotest
Architecture: source
Version: 1.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040538
Changes:
 ocaml-alcotest (1.7.0-2) unstable; urgency=medium
 .
   * Fix FTBFS on bytecode architectures (Closes: #1040538)
Checksums-Sha1:
 a5d15eff7168e73186514eb4093fb31eba28b8ff 1941 ocaml-alcotest_1.7.0-2.dsc
 b6dd5eae42b38f8571295e68185eb0dafcf30d94 3876 
ocaml-alcotest_1.7.0-2.debian.tar.xz
Checksums-Sha256:
 91c490b741675d7b32815e4db3fd2e505aca929c72d933c24edfc3227e35b266 1941 
ocaml-alcotest_1.7.0-2.dsc
 d2dd50840c58840c589c9345cd168933f36218ceba33bf045811e00f0ec4a4bd 3876 
ocaml-alcotest_1.7.0-2.debian.tar.xz
Files:
 40bb62b656743ecbb692614b56c029fd 1941 ocaml optional ocaml-alcotest_1.7.0-2.dsc
 a61061f825b7aa69fcc05ebf5be19f04 3876 ocaml optional 
ocaml-alcotest_1.7.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#1040879: marked as done (redis: CVE-2023-36824: Heap overflow in COMMAND GETKEYS and ACL evaluation)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:21:01 +
with message-id 
and subject line Bug#1040879: fixed in redis 5:7.2-rc3-1
has caused the Debian Bug report #1040879,
regarding redis: CVE-2023-36824: Heap overflow in COMMAND GETKEYS and ACL 
evaluation
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.)


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

Hi,

The following vulnerability was published for redis.

CVE-2023-36824[0]:
| Redis is an in-memory database that persists on disk. In Redit 7.0
| prior to 7.0.12, extracting key names from a command and a list of
| arguments may, in some cases, trigger a heap overflow and result in
| reading random heap memory, heap corruption and potentially remote
| code execution. Several scenarios that may lead to authenticated
| users executing a specially crafted `COMMAND GETKEYS` or `COMMAND
| GETKEYSANDFLAGS`and authenticated users who were set with ACL rules
| that match key names, executing a specially crafted command that
| refers to a variadic list of key names. The vulnerability is patched
| in Redis 7.0.12.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-36824
https://www.cve.org/CVERecord?id=CVE-2023-36824
[1] https://github.com/redis/redis/security/advisories/GHSA-4cfx-h9gq-xpx3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:7.2-rc3-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jul 2023 09:57:10 +0100
Source: redis
Built-For-Profiles: nocheck
Architecture: source
Version: 5:7.2-rc3-1
Distribution: experimental
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Closes: 1040879
Changes:
 redis (5:7.2-rc3-1) experimental; urgency=high
 .
   * New upstream security release.
 
 .
 - CVE-2022-24834: A specially-crafted Lua script executing in Redis could
   have triggered a heap overflow in the cjson and cmsgpack libraries and
   result in heap corruption and potentially remote code execution. The
   problem exists in all versions of Redis with Lua scripting support and
   affects only authenticated/authorised users.
 .
 - CVE-2023-36824: Extracting key names from a command and a list of
   arguments may, in some cases, have triggered a heap overflow and result
   in reading random heap memory, heap corruption and potentially remote
   code execution. (Specifically using COMMAND GETKEYS* and validation of
   key names in ACL rules). (Closes: #1040879)
 .
   * Refresh patches
Checksums-Sha1:
 b63d6087c49c6e79b562c946a5c2af6aa9d85ca4 2245 redis_7.2-rc3-1.dsc
 a52b4341b11246b6938ee71d59c2f50b78e112cb 3417862 redis_7.2-rc3.orig.tar.gz
 177e7fb946b1a8b41fd3e2382526d4084689894a 28528 redis_7.2-rc3-1.debian.tar.xz
 a2757732e612dc716a34c7ca3077238a296443c7 7496 redis_7.2-rc3-1_amd64.buildinfo
Checksums-Sha256:
 b4ec260b2f5d47b39bf2a471a8471f6a4b09e7f98f1620a8eb64e90d74a1a312 2245 
redis_7.2-rc3-1.dsc
 d4e116a7c968442523c00c20c65bc541ae8974964f340dbe07993e39e3fd48ef 3417862 
redis_7.2-rc3.orig.tar.gz
 13b1fd8e170278bfa2b563b70ab7e069b2ac8cb6fa9a970feb212903ba15324e 28528 
redis_7.2-rc3-1.debian.tar.xz
 d87d0bfc9fcd61c942ac9640dd2e64d0004f5a93f115f53304aea6567d93b1a3 7496 
redis_7.2-rc3-1_amd64.buildinfo
Files:
 3a961e24be27ab34805217b6c51a8a2d 2245 database optional redis_7.2-rc3-1.dsc
 a697dc73568c6dea45a16deb7e8668ef 3417862 database optional 
redis_7.2-rc3.orig.tar.gz
 

Bug#1040879: marked as done (redis: CVE-2023-36824: Heap overflow in COMMAND GETKEYS and ACL evaluation)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:20:45 +
with message-id 
and subject line Bug#1040879: fixed in redis 5:7.0.12-1
has caused the Debian Bug report #1040879,
regarding redis: CVE-2023-36824: Heap overflow in COMMAND GETKEYS and ACL 
evaluation
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.)


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

Hi,

The following vulnerability was published for redis.

CVE-2023-36824[0]:
| Redis is an in-memory database that persists on disk. In Redit 7.0
| prior to 7.0.12, extracting key names from a command and a list of
| arguments may, in some cases, trigger a heap overflow and result in
| reading random heap memory, heap corruption and potentially remote
| code execution. Several scenarios that may lead to authenticated
| users executing a specially crafted `COMMAND GETKEYS` or `COMMAND
| GETKEYSANDFLAGS`and authenticated users who were set with ACL rules
| that match key names, executing a specially crafted command that
| refers to a variadic list of key names. The vulnerability is patched
| in Redis 7.0.12.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-36824
https://www.cve.org/CVERecord?id=CVE-2023-36824
[1] https://github.com/redis/redis/security/advisories/GHSA-4cfx-h9gq-xpx3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:7.0.12-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jul 2023 10:07:09 +0100
Source: redis
Built-For-Profiles: nocheck
Architecture: source
Version: 5:7.0.12-1
Distribution: unstable
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Closes: 1040879
Changes:
 redis (5:7.0.12-1) unstable; urgency=high
 .
   * New upstream security release:
 .
 - CVE-2022-24834: A specially-crafted Lua script executing in Redis could
   have triggered a heap overflow in the cjson and cmsgpack libraries and
   result in heap corruption and potentially remote code execution. The
   problem exists in all versions of Redis with Lua scripting support and
   affects only authenticated/authorised users.
 .
 - CVE-2023-36824: Extracting key names from a command and a list of
   arguments may, in some cases, have triggered a heap overflow and result
   in reading random heap memory, heap corruption and potentially remote
   code execution. (Specifically using COMMAND GETKEYS* and validation of
   key names in ACL rules). (Closes: #1040879)
 .
 For more information, please see:
 .
   
Checksums-Sha1:
 cbdc088ee6756cbd2a3ad0f733e8585b2729ea8f 2273 redis_7.0.12-1.dsc
 8501fb1a782fd3050ef914763964ef123228a794 3023189 redis_7.0.12.orig.tar.gz
 4a808c73c1c7f20d29e5d1ae80e844d04d4683cf 28592 redis_7.0.12-1.debian.tar.xz
 216db95f9609f82497b019a88dae15d057a92d40 7474 redis_7.0.12-1_amd64.buildinfo
Checksums-Sha256:
 e011831d24088b9d946cbe0e9422663adbf52197d51293fb00b55f01d8a073f9 2273 
redis_7.0.12-1.dsc
 13d4689454e29e7b9f1161b544e6d08b0ddd27d057859fde7b1916869b3bf701 3023189 
redis_7.0.12.orig.tar.gz
 dd8db40f47f60e78514166de827f1e6802c7eaa181f4da17f2eeac743f4bc8b9 28592 
redis_7.0.12-1.debian.tar.xz
 990f2694dc3788fb7d1671e2b2598f85fdc5cf443df2ac49bfbe520e7e7c9e42 7474 
redis_7.0.12-1_amd64.buildinfo
Files:
 c66d1c9beac34f026b96491132c25fd7 2273 database optional redis_7.0.12-1.dsc
 4a51b64a7d2ec7b71aef4c972f116e0c 3023189 database optional 
redis_7.0.12.orig.tar.gz
 

Bug#1040814: marked as done (coq-quickchick build-depends on dropped transitional package.)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:19:23 +
with message-id 
and subject line Bug#1040814: fixed in coq-quickchick 2.0-2
has caused the Debian Bug report #1040814,
regarding coq-quickchick build-depends on dropped transitional package.
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.)


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

Package: coq-quickchick
Version: 2.0-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

coq-quickchick build-depends on dune, in bullseye this was a transitional 
package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.
--- End Message ---
--- Begin Message ---
Source: coq-quickchick
Source-Version: 2.0-2
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated coq-quickchick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 10:55:33 +0200
Source: coq-quickchick
Architecture: source
Version: 2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040814
Changes:
 coq-quickchick (2.0-2) unstable; urgency=medium
 .
   * Team upload
   * Build-depend on ocaml-dune (Closes: #1040814)
   * Fix Vcs-*
Checksums-Sha1:
 e236e3a8b77eb9f8c9e56a12b1289c4c5ea6a87e 2033 coq-quickchick_2.0-2.dsc
 45af7a19db27ae4def3876960864445205cd6480 2900 
coq-quickchick_2.0-2.debian.tar.xz
Checksums-Sha256:
 aa8fe8292b449b4edf7242153a7f522326e42932668fdfc046bd9466cb82 2033 
coq-quickchick_2.0-2.dsc
 6d2532b7b97a09404f642605ee7e1bb56adfc1ec69f8232136a61ff248845ca6 2900 
coq-quickchick_2.0-2.debian.tar.xz
Files:
 a3a08ffef47d3a1bbfa546fb542ea7a1 2033 ocaml optional coq-quickchick_2.0-2.dsc
 f0f9fcaec933c416f4df664968e2db51 2900 ocaml optional 
coq-quickchick_2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSua2ESHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBH2MIAJnPGpGZEs51Q0Qs+0IVeb4y+vl2xmuK
XTSvnitEX2u7dTCOKnXTaxl6p2OE+kRk3KlIE9LmWson2H7gI4jlX1oXZtTk2X4w
Y/8ZUJ5lufIYVQ0ZTVCoruYW67XLKdtUm/Ovl2v2Tq1XVyDYve8vgsHCYLo/6Igz
dkPq/DjwQbH73gdL85OAMbnUZTmas9aIEYJytN7Lw6kojiz7Zfulvc/Gu55bjpb5
OiYM6LRyvGiuvwLysQuDZY2VL4IlWFLp+GSSOWWVLQdwYDet/wK7hL+teAWZwfVy
bbPxm0qlG875eu21+w9/2gFdaWLcxWQdvaFnBLth7yFSlhp2m3X3oUk=
=zxwY
-END PGP SIGNATURE End Message ---

Bug#1039710: debian-installer: Grub installation fails and /var/log/syslog is empty

[Cyril Brulebois]

Hi Michael,

Cyril Brulebois  (2023-06-28):
> Control: reassign -1 busybox-udeb 1:1.36.1-3

[…]

> With a local build, confirmed -3 is buggy, and that reverting only
> busybox-udeb to -1 is sufficient to restore syslog support in the
> installer.
> 
> Reassigning there; the GRUB thing can be filed separately once we have
> actual information via syslog.

A fix would be appreciated, we've got reports piling up about things we
have no logs for.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1040813: marked as done (ocaml-unix-errno build-depends on dropped transitional package.)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:07:56 +
with message-id 
and subject line Bug#1040813: fixed in ocaml-unix-errno 0.6.1-3
has caused the Debian Bug report #1040813,
regarding ocaml-unix-errno build-depends on dropped transitional package.
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.)


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

Package: ocaml-unix-errno
Version: 0.6.1-2
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-pprint build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.
--- End Message ---
--- Begin Message ---
Source: ocaml-unix-errno
Source-Version: 0.6.1-3
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocaml-unix-errno 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 10:51:25 +0200
Source: ocaml-unix-errno
Architecture: source
Version: 0.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040813
Changes:
 ocaml-unix-errno (0.6.1-3) unstable; urgency=medium
 .
   * Team upload
   * Build-depend on ocaml-dune (Closes: #1040813)
Checksums-Sha1:
 09f396f5b5fb962f4da4f5dafd5afe004b854580 2036 ocaml-unix-errno_0.6.1-3.dsc
 4200587954301770fb5107b772c91d57813899b8 3028 
ocaml-unix-errno_0.6.1-3.debian.tar.xz
Checksums-Sha256:
 c48c816aeb7762ce9f12b6c71ead14383aff4c550790893e5cc1d30ce553637b 2036 
ocaml-unix-errno_0.6.1-3.dsc
 3a0084087511a42543844a8ffa59885fdaef675a8541c332ad21935d8710df0b 3028 
ocaml-unix-errno_0.6.1-3.debian.tar.xz
Files:
 85bd30bac3ff4674f843348096ac2762 2036 ocaml optional 
ocaml-unix-errno_0.6.1-3.dsc
 95a474a354f01175bf3d385849f6272d 3028 ocaml optional 
ocaml-unix-errno_0.6.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSuaeUSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBiOgH/jrxEnrTo58JAKDRTBsG7QVifHWxYeDX
Np92oKdc9HG7Cg1ZLP7XB/L8PZoFUvOjq6fEUw79RkbO5cLQXMMvp6SQq63+/oLF
1v/pwlzUwL+wik7ngmcUSU+J83BjRG8zp5ktfjQrdtIFzwJhY2RpYuLJcZCCBpZx
q/ZbmtdlY9qIZrIcR6C+ogtXUCfX9wdqMhftCuZhfWA/vmblwStfc6Hhxc4mEWOr
crIebJxtRKtNiJqsbXHBkWiRAUJSxXzKgqsM6gIskG1S9YWTnp+yAZmixxHwL5A7
UX7PsX5S/AcnlHTm/Qurv2vb2pRlwHeAIRgBpkslAAo8feD8con8zl8=
=5QhK
-END PGP SIGNATURE End Message ---

Bug#1040811: marked as done (ocaml-mm build-depends on dropped transitional package.)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 09:07:50 +
with message-id 
and subject line Bug#1040811: fixed in ocaml-mm 0.8.1-2
has caused the Debian Bug report #1040811,
regarding ocaml-mm build-depends on dropped transitional package.
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.)


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

Package: ocaml-mm
Version: 0.8.1-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-mm build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.
--- End Message ---
--- Begin Message ---
Source: ocaml-mm
Source-Version: 0.8.1-2
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocaml-mm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jul 2023 10:43:34 +0200
Source: ocaml-mm
Architecture: source
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1040811
Changes:
 ocaml-mm (0.8.1-2) unstable; urgency=medium
 .
   * Team upload
   * Build-depend on ocaml-dune (Closes: #1040811)
Checksums-Sha1:
 1122d16fa268992603121cfafe1aa53b3d48de36 2036 ocaml-mm_0.8.1-2.dsc
 3a3cb57de786b7e6141a04dd37ceade152107b53 4184 ocaml-mm_0.8.1-2.debian.tar.xz
Checksums-Sha256:
 6ed4962bbe7cf34bb8b876b308383766f1449980164fc92fd6adaa565173963a 2036 
ocaml-mm_0.8.1-2.dsc
 f8790507b8e0ac21f18c039b9dc4079bc46e90b753d6b2334ab8c77568c8396c 4184 
ocaml-mm_0.8.1-2.debian.tar.xz
Files:
 7b3774e1c8cadc90f44868011bc2b349 2036 ocaml optional ocaml-mm_0.8.1-2.dsc
 ec857737d8f58932d731cfec85113fc7 4184 ocaml optional 
ocaml-mm_0.8.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSuaDQSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBqnIIAJYW1J0cdF8GxYsYtkbqHPsUhzM1ixfU
/yd6naSQ1UwCYE8zEKEzZdpqGCNHmYcuidOVDs6HKVqYqeKz0rXdwLDh+H3pQ005
IQJ66ZzkqurXS/wXs9Omk11FW3lx8g6IsyCepZhmEBVRkfxw0jjUIHq4GpZh6AfO
gF8gIgo4xICp8JBuLMJYepMF5OhxWEKbw/iGugMxRDUKTV1vddWLBnOGWs0rEcB4
B3wTqiBelkebElynAC72vjbdNNjp22BlC1eyvMXegNAT6lpwzERcvogCPurZm4Qu
RG5OjLBn4WNe77EuG5CCQkhf+2u7jz6tb5jpC/jdpltTmQixWQlAFOo=
=CWv0
-END PGP SIGNATURE End Message ---

Bug#1040812: marked as done (ocaml-pprint build-depends on dropped transitional package.)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 10:49:14 +0200
with message-id 
and subject line Re: Bug#1040812: ocaml-pprint build-depends on dropped 
transitional package.
has caused the Debian Bug report #1040812,
regarding ocaml-pprint build-depends on dropped transitional package.
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.)


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

Package: ocaml-pprint
Version: 20220103-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-pprint build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.
--- End Message ---
--- Begin Message ---

Version: 20220103-2

Le 11/07/2023 à 04:13, Peter Green a écrit :
ocaml-pprint build-depends on dune, in bullseye this was a transitional 
package

built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.


Already fixed in last version, hence closing.


Cheers,

--
Stéphane--- End Message ---

Bug#1039678: marked as done (nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jul 2023 08:41:11 +
with message-id 
and subject line Bug#1039678: fixed in nvidia-graphics-drivers 525.125.06-1
has caused the Debian Bug report #1039678,
regarding nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 525.125.06-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jul 2023 09:52:32 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 525.125.06-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA 

Processed: notfound 1000051 in 1.7.2-1, tagging 1000051, reassign 1040669 to raspi-firmware ..., tagging 1040835

[Debian Bug Tracking System]

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

> notfound 151 1.7.2-1
Bug #151 {Done: Bastian Germann } [src:mle] mle: depends 
on obsolete pcre3 library
No longer marked as found in versions mle/1.7.2-1.
> tags 151 + sid trixie
Bug #151 {Done: Bastian Germann } [src:mle] mle: depends 
on obsolete pcre3 library
Added tag(s) trixie and sid.
> reassign 1040669 raspi-firmware
Bug #1040669 {Done: Ben Hutchings } [apt & 
linux-image-amd64 (w/associated 6.1.)] `sudo apt update && sudo apt 
upgrade` on amd64 calls z50-raspi-firmware for kernel upgrade
Warning: Unknown package '&'
Warning: Unknown package 'w/associated'
Warning: Unknown package '6.1.'
Bug reassigned from package 'apt & linux-image-amd64 (w/associated 6.1.)' 
to 'raspi-firmware'.
No longer marked as found in versions 12.
Ignoring request to alter fixed versions of bug #1040669 to the same values 
previously set
> reassign 1040859 mariadb-server
Bug #1040859 [mariadb-server-10.0] mariadb-server-10.0: logrotate returns error 
when server is stopped or disabled
Warning: Unknown package 'mariadb-server-10.0'
Bug reassigned from package 'mariadb-server-10.0' to 'mariadb-server'.
No longer marked as found in versions 10.0.38-0+deb8u1.
Ignoring request to alter fixed versions of bug #1040859 to the same values 
previously set
> tags 1040835 + sid trixie
Bug #1040835 [librust-async-std-dev] librust-async-std-dev: impossible to 
install: missing dependency librust-log-0.4+kv-unstable-dev
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: Re: linux modules must not be signed with CA key, bump ABI every upload

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 6.3.0-7.7
Bug #1040901 [src:linux] linux modules must not be signed with CA key, bump ABI 
every upload
The source 'linux' and version '6.3.0-7.7' do not appear to match any binary 
packages
No longer marked as found in versions linux/6.3.0-7.7.

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

Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload

[Julian Andres Klode]

Control: notfound -1 6.3.0-7.7

On Wed, Jul 12, 2023 at 10:05:03AM +0200, Julian Andres Klode wrote:
> Source: linux
> Version: 6.3.0-7.7
> Severity: grave
> Tags: security
> X-Debbugs-Cc: j...@debian.org

Sorry about that, it picked up the version from my work system's Ubuntu
kernel and I forgot to clean it.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload

[Julian Andres Klode]

Source: linux
Version: 6.3.0-7.7
Severity: grave
Tags: security
X-Debbugs-Cc: j...@debian.org

I know there's some work in progress but it appears we don't have a bug
for it yet. I raised this yesterday in our weekly upstream shim/grub
cabal meetings and Debian's current approach to sign modules with the
same key and not bump ABI on every upload should be considered a bug.

The current approach means that a kernel cannot be easily revoked,
you would need to add its kernel modules to the dbx as well, which
is a grave security bug.

The state of the art solution is to sign everything using an ephemeral key,
which yes, it will cause the package to be unreproducible, but if nobody
commits to working on that merkle tree of modules, than this is very
well going to have to be the solution to the issue.

A reasonable compromise at a first step for a limited time is to
ensure that

1) the kernel refuses to load modules for a different ABI in lockdown,
   for example, the modprobe --force-vermagic does not work anymore.
2) each upload bumps the ABI [this is also required for the ephemeral
   key and merkle tree approaches as otherwise the modules become
   no longer loadable]

This is still somewhat problematic as there may be bugs in the code
validating parsing the kernel module sections that could be exploited
if there were some weird modules, but it's a significant improvement
(turning this from grave to serious I guess).

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Processed: Re: Bug#1040899: debian-cd: "Failed to mount /target/proc" during GRUB installation

[Debian Bug Tracking System]

Processing control commands:

> affects 1039710 debian-cd
Bug #1039710 [busybox-udeb] busybox-udeb: /var/log/syslog is empty
Added indication that 1039710 affects debian-cd

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

Processed: Re: Bug#1040898: tp-smapi-dkms: Update to support Kernel 6.4+

[Debian Bug Tracking System]

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

> forcemerge 1038207 1040898
Bug #1038207 [tp-smapi-dkms] tp-smapi-dkms: module fails to build for Linux 
6.4: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given
Bug #1040898 [tp-smapi-dkms] tp-smapi-dkms: Update to support Kernel 6.4+
Severity set to 'important' from 'critical'
Added tag(s) sid and trixie.
Merged 1038207 1040898
> thanks
Stopping processing here.

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

Bug#1040898: tp-smapi-dkms: Update to support Kernel 6.4+

[Evgeni Golov]

forcemerge 1038207 1040898
thanks

On Wed, Jul 12, 2023 at 08:46:22AM +0200, Jan Volec wrote:
> Package: tp-smapi-dkms
> Version: 0.43-3
> Severity: critical
> Justification: breaks unrelated software

no it does not :)

> DKMS fails to compile the module with the 6.4 kernels; see 
> https://github.com/linux-thinkpad/tp_smapi,
> and the patch 
> https://github.com/linux-thinkpad/tp_smapi/commit/0c3398b1acf2a2cabd9cee91dc3fe3d35805fa8b

This has already been reported in https://bugs.debian.org/1038207
and I am merging these bugs.

Bug#1040840: tp-smapi-dkms: Thinkpad fails to wake from sleep correctly with tp-smapi-dkms after bookworm upgrade

[Evgeni Golov]

On Wed, Jul 12, 2023 at 09:06:36AM +0200, Caren Hern wrote:
> Hi Evgeni,
> 
> yes I have suspend active. Hibernate was never working.

Okay, I can at least double-check that against the machines I have here!

> I am also confused now, because I just reinstalled the package (no errors)
> but indead when I try to manually load it using modprobe it indead throws an
> error (ERROR: could not insert 'tp_smapi': No such device or address).

Yeah, that's more like what I've expected. The SMAPI interface was
removed in the *20/*30 series in favor of plain ACPI and the module
should (rightfully) refuse to load if it can't find SMAPI.

The `thinkpad_ec` module has a `force_io` parameter to make it load on
*some* half-supported models, but even that shouldn't do anything when
there is no SMAPI at all.

> I just don't understand how the issue suddenly disappeared after removing
> the package. I am wondering if its something with some other part of DKMS.
> Because straight after the upgrade the issue was there a lot, then I
> reinstalled the two packages which have kernel modules (tp-smapi-dkms and
> broadcom-sta-dkms) because I thought maybe they were built for the wrong
> kernel or something and the issue went away for two weeks, until it suddenly
> reappeared and subsequently disappeared again after I completely removed the
> tp-smapi package.

dkms *should* properly detect any kernel changes and rebuild stuff.

> One time after a freeze I read through dmesg but didn't find anything that
> looked of (to me!).
> 
> I will keep it installed now and will let you know if it happens again.

Thanks!

Bug#1040898: tp-smapi-dkms: Update to support Kernel 6.4+

[Jan Volec]

Package: tp-smapi-dkms
Version: 0.43-3
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: j...@ucw.cz

Dear Maintainer,

DKMS fails to compile the module with the 6.4 kernels; see 
https://github.com/linux-thinkpad/tp_smapi,
and the patch 
https://github.com/linux-thinkpad/tp_smapi/commit/0c3398b1acf2a2cabd9cee91dc3fe3d35805fa8b

Jan


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

Kernel: Linux 6.3.12-x64v4-xanmod1 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tp-smapi-dkms depends on:
ii  dkms  3.0.11-3

tp-smapi-dkms recommends no packages.

tp-smapi-dkms suggests no packages.

-- no debconf information