Bug#1057171: marked as done (libitext5-java: FTBFS with bouncycastle 1.77)

[Debian Bug Tracking System]

Your message dated Tue, 12 Dec 2023 07:19:57 +
with message-id 
and subject line Bug#1057171: fixed in libitext5-java 5.5.13.3-3
has caused the Debian Bug report #1057171,
regarding libitext5-java: FTBFS with bouncycastle 1.77
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.)


-- 
1057171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libitext5-java
Version: 5.5.13.3-2
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

libitext5-java fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.

BUILD FAILURE
[INFO] 
[INFO] Total time:  12.832 s
[INFO] Finished at: 2023-11-30T13:27:49+01:00
[INFO] 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.10.1:compile (default-compile) on project itextpdf: Compilation
failure: Compilation failure: 
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[223,95] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: class org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[246,109] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: class org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[346,70] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[350,70] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[1286,28] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: variable tag of type org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja
va:[1287,48] cannot find symbol
[ERROR]   symbol:   method getObject()
[ERROR]   location: variable tag of type org.bouncycastle.asn1.ASN1TaggedObject
[ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/Certificate
Util.java:[123,67] incompatible types: org.bouncycastle.asn1.ASN1IA5String
cannot be converted to org.bouncycastle.asn1.DERIA5String
[ERROR] -> [Help 1]
[ERROR] 


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libitext5-java
Source-Version: 5.5.13.3-3
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libitext5-java 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, 11 Dec 2023 22:47:32 -0800
Source: libitext5-java
Architecture: source
Version: 5.5.13.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1057171
Changes:
 libitext5-java (5.5.13.3-3) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Standards-Version: 4.6.2 (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Fix watchfile to detect new versions on github
 .
   [ tony mancill ]
   * Add patch to compile against BouncyCastle 1.77 (Closes: #1057171)
   * Add lintian-override for long HTML and JS lines
Checksums-Sha1:
 fe2b4ba276d598388626c11faec04f66508ba109 2234 libitext5-java_5.5.13.3-3.dsc
 b3736a59cfe1194948051825a1c56bbdcfe993da 19056 
libitext5-java_5.5.13.3-3.debian.tar.xz
 

Bug#1057171: libitext5-java: FTBFS with bouncycastle 1.77

[tony mancill]

On Thu, Nov 30, 2023 at 11:06:56PM +0100, Markus Koschany wrote:
> Source: libitext5-java
> Version: 5.5.13.3-2
> Severity: serious
> Tags: ftbfs sid
> User: a...@debian.org
> Usertags: bouncycastle-1.77

There are PDF signature and encryption test cases running as part of the
build, and I did some desk-testing of programs that depend on
libitext5-java: jameica/hibiscus and mobile-atlas-creator, which I was
able to use to generates a PDF - and everything seems fine at runtime.

I'll keep an eye out for any runtime issues with digitally signed PDFs
and move on to libitext-java.

Processed: Re: [Pkg-javascript-devel] Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1058078 [node-eslint-plugin-eslint-plugin] FTBFS: ESLint couldn't find the 
config "not-an-aardvark/node" to extend from
Added tag(s) patch.

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

Bug#1058078: [Pkg-javascript-devel] Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

[Yadd]

Control: tags -1 + patch

On 12/12/23 09:59, Yadd wrote:

Package: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-4
Severity: serious
Tags: ftbfs
Justification: ftbfs

Hi,

when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild
fails. Below relevant logs:

eslint --format tap Xcomposer
TAP version 13
1..2
ok 1 - /<>/Xcomposer/lib/rule-composer.js
ok 2 - /<>/Xcomposer/tests/lib/rule-composer.js

eslint --format tap . --ignore-pattern '!.*'

Oops! Something went wrong! :(

ESLint: 6.4.0.

ESLint couldn't find the config "not-an-aardvark/node" to extend from. Please 
check that the name of the config is correct.

The config "not-an-aardvark/node" was referenced from the config file in 
"/<>/.pc/2002_avoid_eslint-plugin-self.patch/.eslintrc.yml".

If you still have problems, please stop by https://gitter.im/eslint/eslint to 
chat with the team.

make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2


Hi Jonas,

this patch seems to fix the problem:

--- a/debian/rules
+++ b/debian/rules
@@ -35,7 +35,7 @@ override_dh_auto_build: $(DOCS) $(CHANGELOGS)

 override_dh_auto_test:
$(ESLINT) Xcomposer
-   $(ESLINT) . --ignore-pattern '!.*'
+   $(ESLINT) . --ignore-pattern .pc
$(MOCHA) --recursive Xcomposer/tests
$(MOCHA) --recursive tests

Bug#1055684: marked as done (beancount fails tests with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 12 Dec 2023 06:04:17 +
with message-id 
and subject line Bug#1055684: fixed in beancount 2.3.6-1
has caused the Debian Bug report #1055684,
regarding beancount fails tests with Python 3.12
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.)


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

Package: src:beancount
Version: 2.3.5-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

=== short test summary info 

FAILED beancount/ops/summarize_test.py::TestOpenClose::test_open - 
UnboundLoc...

FAILED beancount/ops/summarize_test.py::TestOpenClose::test_open_close_clear
FAILED beancount/ops/summarize_test.py::TestOpenCloseWithOptions::test_open
FAILED 
beancount/ops/summarize_test.py::TestOpenCloseWithOptions::test_open_close_clear
FAILED beancount/ops/summarize_test.py::TestClamp::test_clamp - 
UnboundLocalE...
FAILED 
beancount/ops/summarize_test.py::TestTransferBalances::test_transfer_balances__end_assets_implicit
FAILED 
beancount/ops/summarize_test.py::TestTransferBalances::test_transfer_balances__middle_assets
FAILED 
beancount/ops/summarize_test.py::TestTransferBalances::test_transfer_balances__middle_at_cost
FAILED 
beancount/ops/summarize_test.py::TestTransferBalances::test_transfer_balances__middle_income
FAILED 
beancount/query/query_execute_test.py::TestFilterEntries::test_filter_open_dated
FAILED beancount/query/shell_test.py::TestUseCases::test_balance_sheet - 
Asse...
FAILED beancount/query/shell_test.py::TestUseCases::test_conversions - 
Assert...
FAILED 
beancount/query/shell_test.py::TestUseCases::test_income_statement - A...
FAILED beancount/query/shell_test.py::TestUseCases::test_journal - 
AssertionE...
FAILED 
beancount/scripts/bake_test.py::TestScriptBake::test_bake_directory - ...
FAILED 
beancount/scripts/bake_test.py::TestScriptArchive::test_bake_archive__known
FAILED 
beancount/scripts/bake_test.py::TestScriptArchive::test_bake_directory
FAILED beancount/web/views_test.py::TestViews::test_YearView - 
UnboundLocalEr...
FAILED beancount/web/web_test.py::TestWeb::test_scrape_basic - 
urllib.error.H...
FAILED beancount/web/web_test.py::TestWeb::test_scrape_basic_view - 
urllib.er...
FAILED beancount/web/web_test.py::TestWeb::test_scrape_empty_file - 
urllib.er...
FAILED beancount/web/web_test.py::TestWeb::test_scrape_in_incognito - 
urllib
FAILED beancount/web/web_test.py::TestWeb::test_scrape_starterkit - 
urllib.er...
 23 failed, 1682 passed, 22 skipped, 2 xfailed, 2487 warnings in 
35.79s 
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest -v


complete build log at
https://launchpadlibrarian.net/696984020/buildlog_ubuntu-noble-amd64.beancount_2.3.5-3build1_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
Source: beancount
Source-Version: 2.3.6-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated beancount 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, 12 Dec 2023 00:31:17 -0500
Source: beancount
Architecture: source
Version: 2.3.6-1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 1055684
Changes:
 beancount (2.3.6-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream release.
 + Fix compatibility with python3.12. (Closes: #1055684)
   * debian/control:
 + Add new build-dependency to python3-oauth2client.
 + Add new build-test-dependency python3-pdfminer.
 + Mark python3-pytest and python3-pdfminer as .
 + Replace dh-python with dh-sequence-python3.
 + Bump Standards-Version to 4.6.2.
   * debian/rules:
 + Do not override dh_missing.
 + Remove now useless "--with python3" parameter.
 + Use 

Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

[Yadd]

Package: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-4
Severity: serious
Tags: ftbfs
Justification: ftbfs

Hi,

when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild
fails. Below relevant logs:

eslint --format tap Xcomposer
TAP version 13
1..2
ok 1 - /<>/Xcomposer/lib/rule-composer.js
ok 2 - /<>/Xcomposer/tests/lib/rule-composer.js

eslint --format tap . --ignore-pattern '!.*'

Oops! Something went wrong! :(

ESLint: 6.4.0.

ESLint couldn't find the config "not-an-aardvark/node" to extend from. Please 
check that the name of the config is correct.

The config "not-an-aardvark/node" was referenced from the config file in 
"/<>/.pc/2002_avoid_eslint-plugin-self.patch/.eslintrc.yml".

If you still have problems, please stop by https://gitter.im/eslint/eslint to 
chat with the team.

make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2

Bug#1056534: marked as done (tkcalendar's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 12 Dec 2023 03:04:08 +
with message-id 
and subject line Bug#1056534: fixed in tkcalendar 1.6.1-4
has caused the Debian Bug report #1056534,
regarding tkcalendar's autopkg tests fail with Python 3.12
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.)


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

Package: src:tkcalendar
Version: 1.6.1-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

tkcalendar's autopkg tests fail with Python 3.12:

[...]
232s ==
232s ERROR: test_calendar_buttons_functions 
(tests.test_calendar.TestCalendar.test_calendar_buttons_functions)

232s --
232s Traceback (most recent call last):
232s   File 
"/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/test_calendar.py", line 
194, in test_calendar_buttons_functions

232s widget.selection_set(format_date(date(2018, 12, 31), 'short'))
232s  
232s   File "/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/__init__.py", 
line 30, in format_date

232s return babel.dates.format_date(date, length, locale)
232s^
232s   File "/usr/lib/python3/dist-packages/babel/dates.py", line 726, 
in format_date

232s locale = Locale.parse(locale)
232s  
232s   File "/usr/lib/python3/dist-packages/babel/core.py", line 330, in 
parse

232s raise UnknownLocaleError(input_id)
232s babel.core.UnknownLocaleError: unknown locale 'c'
232s
232s ==
232s ERROR: test_calendar_init 
(tests.test_calendar.TestCalendar.test_calendar_init)

232s --
232s Traceback (most recent call last):
232s   File 
"/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/test_calendar.py", line 
38, in test_calendar_init

232s today = format_date(date.today(), 'short')
232s ^^
232s   File "/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/__init__.py", 
line 30, in format_date

232s return babel.dates.format_date(date, length, locale)
232s^
232s   File "/usr/lib/python3/dist-packages/babel/dates.py", line 726, 
in format_date

232s locale = Locale.parse(locale)
232s  
232s   File "/usr/lib/python3/dist-packages/babel/core.py", line 330, in 
parse

232s raise UnknownLocaleError(input_id)
232s babel.core.UnknownLocaleError: unknown locale 'c'
232s
232s ==
232s ERROR: test_dateentry_functions 
(tests.test_dateentry.TestDateEntry.test_dateentry_functions)

232s --
232s Traceback (most recent call last):
232s   File 
"/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/test_dateentry.py", line 
114, in test_dateentry_functions

232s widget.set_date(format_date(date(2018, 12, 31), 'short'))
232s 
232s   File "/tmp/autopkgtest.Ikr8jw/autopkgtest_tmp/tests/__init__.py", 
line 30, in format_date

232s return babel.dates.format_date(date, length, locale)
232s^
232s   File "/usr/lib/python3/dist-packages/babel/dates.py", line 726, 
in format_date

232s locale = Locale.parse(locale)
232s  
232s   File "/usr/lib/python3/dist-packages/babel/core.py", line 330, in 
parse

232s raise UnknownLocaleError(input_id)
232s babel.core.UnknownLocaleError: unknown locale 'c'
232s
232s --
232s Ran 15 tests in 0.538s
232s
232s FAILED (errors=3)
--- End Message ---
--- Begin Message ---
Source: tkcalendar
Source-Version: 1.6.1-4
Done: Bo YU 

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

Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

[Steve VanDevender]

Salvatore Bonaccorso writes:
 > Control: tags -1 + moreinfo
 > 
 > Hi Steve,
 > 
 > On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote:
 > > Package: src:linux
 > > Version: 6.1.66-1
 > > Severity: grave
 > > Tags: upstream
 > > Justification: renders package unusable
 > > 
 > > I would have tried to report this from the 6.1.66 kernel but once a
 > > suspend is attempted network access is also broken so I have had to
 > > reboot into a working kernel in order to report the bug.
 > > 
 > > The problem may be related to the wireless network drivers since some
 > > processes that can't be frozen for suspend are NetworkManager,
 > > wpa-supplicant, and iw.
 > > 
 > > I have included boot messages from the affected kernel through an
 > > attempt to suspend the system including the traces from the processes
 > > that seem to get wedged by an attempt to suspend.
 >
 > I cannot test for the regression explicitly myself, but 6.1.67 was
 > released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
 > non-range use""). Would you be in the position of do a test build with
 > that commit (or with 6.1.67 upstream) to verify your issue goes away?

I was able to build a test kernel from the Debian sources for 6.1.66
and the patch from 6.1.67 (thanks to Diederik's instructions) and
install it on my laptop and it does solve the problem with
suspend/resume.

I did forget to include that this problem must have been introduced
after 6.1.64 (which I ran for a few days) since that kernel version
did not have the suspend/resume problem.  But the commit reverted in
6.1.67 was clearly the cause of the problem.

 > Regards,
 > Salvatore

Bug#1058074: rust-hyper-rustls - autopkgtest failure

[Peter Green]

Package: rust-hyper-rustls
Version: 0.24.2-1
Severity: serious
Tags: patch

The autopkgtest for rust-hyper-rustls is failing, because the code in
test_alpn_http2 requires a runtime, but the feature requirements for
the test do not specify one.

A debdiff fixing this is attatched.diff -Nru rust-hyper-rustls-0.24.2/debian/changelog 
rust-hyper-rustls-0.24.2/debian/changelog
--- rust-hyper-rustls-0.24.2/debian/changelog   2023-12-02 20:25:28.0 
+
+++ rust-hyper-rustls-0.24.2/debian/changelog   2023-12-12 01:18:39.0 
+
@@ -1,3 +1,11 @@
+rust-hyper-rustls (0.24.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix feature requirements for test_alpn_http to prevent autopkgtest
+failure.
+
+ -- Peter Michael Green   Tue, 12 Dec 2023 01:18:39 +
+
 rust-hyper-rustls (0.24.2-1) unstable; urgency=medium
 
   * unfuzz patches
diff -Nru 
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch 
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
--- rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
1970-01-01 00:00:00.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
2023-12-12 01:18:17.0 +
@@ -0,0 +1,20 @@
+Description: tests_alpn_http2 fails to build if no runtime is enabled
+ Add feature guards so it doesn't cause autopkgtest failure.
+Author: Peter Michael Green 
+Last-Update: 2023-12-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+Index: rust-hyper-rustls-0.24.2/src/connector/builder.rs
+===
+--- rust-hyper-rustls-0.24.2.orig/src/connector/builder.rs
 rust-hyper-rustls-0.24.2/src/connector/builder.rs
+@@ -353,7 +353,7 @@ mod tests {
+ }
+ 
+ #[test]
+-#[cfg(all(not(feature = "http1"), feature = "http2"))]
++#[cfg(all(not(feature = "http1"), feature = "http2", any(feature = 
"native-tokio", feature = "tokio-runtime")))]
+ fn test_alpn_http2() {
+ let roots = rustls::RootCertStore::empty();
+ let tls_config = rustls::ClientConfig::builder()
diff -Nru rust-hyper-rustls-0.24.2/debian/patches/series 
rust-hyper-rustls-0.24.2/debian/patches/series
--- rust-hyper-rustls-0.24.2/debian/patches/series  2022-12-06 
11:57:28.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/series  2023-12-12 
01:16:36.0 +
@@ -1,3 +1,4 @@
 1001_http1.patch
+1002_test-requires-runtime.patch
 2001_webpki-roots.patch
 2004_tests_broken.patch

Bug#1057579: marked as done (mplayer: FTBFS: error: 'INT_MAX' undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Tue, 12 Dec 2023 00:35:01 +
with message-id 
and subject line Bug#1057579: fixed in mplayer 2:1.5+svn38446-1
has caused the Debian Bug report #1057579,
regarding mplayer: FTBFS: error: 'INT_MAX' undeclared (first use in this 
function)
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.)


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

Package: src:mplayer
Version: 2:1.5+svn38423-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure-arch
make[1]: Entering directory '/<>'
./configure --prefix=/usr --confdir=/etc/mplayer --enable-debug --enable-xvmc --enable-menu --disable-arts 
--language=all --disable-libmpeg2-internal --disable-ffmpeg_a --disable-esd --extra-cflags="-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" 
--extra-ldflags="-Wl,-z,relro -Wl,-z,now"  --enable-runtime-cpudetection --enable-joystick 
--enable-radio --enable-radio-capture --enable-gui --enable-nls
Checking for ffmpeg/libavcodec/allcodecs.c ... not found
Checking for ffmpeg/libavcodec/hwaccels.h ... not found
Checking for ffmpeg/libavformat/allformats.c ... not found
Checking for ffmpeg/libavcodec/bitsteram_filters.c ... not found
Checking for ffmpeg/libavcodec/cbs_internal.h ... not found
Checking for ffmpeg/libavformat/protocols.c ... not found
Checking for ffmpeg/libavfilter/allfilters.c ... not found

[... snipped ...]

  766 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:845:13: note: in expansion of macro 
'REORDER_SELF_SWAP_5_STEP_1'
  845 | 
REORDER_SELF_SWAP_5_STEP_1(src_32,tmp,samples,8,s0,s1,s2,s3,s4);
  | ^~
libaf/reorder_ch.c:766:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  766 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:848:13: note: in expansion of macro 
'REORDER_SELF_SWAP_5_STEP_1'
  848 | 
REORDER_SELF_SWAP_5_STEP_1(src_32,tmp,samples,5,s0,s1,s2,s3,s4);
  | ^~
libaf/reorder_ch.c:766:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  766 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:857:13: note: in expansion of macro 
'REORDER_SELF_SWAP_5_STEP_1'
  857 | 
REORDER_SELF_SWAP_5_STEP_1(src_64,tmp,samples,6,s0,s1,s2,s3,s4);
  | ^~
libaf/reorder_ch.c:766:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  766 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:860:13: note: in expansion of macro 
'REORDER_SELF_SWAP_5_STEP_1'
  860 | 
REORDER_SELF_SWAP_5_STEP_1(src_64,tmp,samples,8,s0,s1,s2,s3,s4);
  | ^~
libaf/reorder_ch.c:766:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  766 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:863:13: note: in expansion of macro 
'REORDER_SELF_SWAP_5_STEP_1'
  863 | 
REORDER_SELF_SWAP_5_STEP_1(src_64,tmp,samples,5,s0,s1,s2,s3,s4);
  | ^~
libaf/reorder_ch.c: In function 'reorder_self_2_3':
libaf/reorder_ch.c:877:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  877 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:897:9: note: in expansion of macro 'REORDER_SELF_SWAP_2_3'
  897 | REORDER_SELF_SWAP_2_3(src_8,tmp,samples,6,s0,s1,s2,s3,s4);
  | ^
libaf/reorder_ch.c:877:15: warning: comparison of integer expressions of 
different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  877 | for (i = 0; i < SAMPLES; i += CHNUM) {\
  |   ^
libaf/reorder_ch.c:904:9: note: in expansion of macro 'REORDER_SELF_SWAP_2_3'
  904 | 

Processed: reassign 1056461 to python3-future

[Debian Bug Tracking System]

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

> reassign 1056461 python3-future
Bug #1056461 [src:python-canmatrix] python-canmatrix's autopkg tests fail with 
Python 3.12
Bug reassigned from package 'src:python-canmatrix' to 'python3-future'.
No longer marked as found in versions python-canmatrix/1.0~github-1.
Ignoring request to alter fixed versions of bug #1056461 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1042049: lintian: FTBFS: 3 tests failed

[Richard Lewis]

On Thu, 7 Dec 2023 22:05:29 +1300 Vladimir Petko
 wrote:
> As of today there are more test failures:



> Test Summary Report
> ---
> debian/test-out/eval/checks/documentation/manual/manpage-errors-from-man/generic.t
> debian/test-out/eval/checks/documentation/manual/surplus-manpage/generic.t
> debian/test-out/eval/checks/documentation/manual/manpages-general/generic.t

think these are already fixed in git

> debian/test-out/eval/checks/systemd/kill-mode-none/generic.t
(etc).

This MR fixes these failures:
https://salsa.debian.org/lintian/lintian/-/merge_requests/487

these are all because of usrmerge putting service files in
usr/lib/systemd rather than lib/systemd -- add "usr/" to the message
in the hints file for each

(and updates the description of the tests in CONTRIBUTING.md and
t/recipes/README)

It also includes https://salsa.debian.org/lintian/lintian/-/merge_requests/485

Thanks for considering

Bug#1056461: python-canmatrix's autopkg tests fail with Python 3.12

[IOhannes m zmoelnig]

Source: python-canmatrix
Followup-For: Bug #1056461


This seems to really be a bug in python3-future:


```sh
$ python3-c "import past.builtins"

$ python3.12 -c "import past.builtins"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/past/builtins/__init__.py", line 54, in 

from past.builtins.misc import (apply, chr, cmp, execfile, intern, oct,
  File "/usr/lib/python3/dist-packages/past/builtins/misc.py", line 45, in 

from imp import reload
ModuleNotFoundError: No module named 'imp'

```
i've therefore reassigned this bug.



Doing a quick check on python-future, it seems that the v0.18.3 release
(available since 2023-01-13) fixes the issue at hand, as it includes


so i wonder, why we still ship 0.18.2

(i see that andreas has updated the package to 0.18.2 *today* :-))

cheers,
gfmdsa
IOhannes

Bug#1058038: texlive-extra: Blocker bug

[Preuße]

On 11.12.2023 21:30, Chris Hofstaedtler wrote:

On Mon, Dec 11, 2023 at 02:57:35PM +, Hilmar Preusse wrote:


Hi,


Severity: normal



This bug blocks the migration for now, I'll close
it, once the other two packages tend to migrate.


Pretty sure severity: normal does not block => raising.

Thanks for pointing that out. reportbug must have have downgraded my bug 
b/c I did not specify justification for "serious".


H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1000112: kjs: depends on obsolete pcre3 library

[Bastian Germann]

okular and khelpcenter make kjs a key package via khtml.
While it is optional in okular, khelpcenter requires khtml.
This is changing with the 24.08.x versions, which will be part of Plasma 6.
When khelpcenter upgrades to a khtml-free version, this should be followed-up.

Processed: pyopengl's autopkg tests fail with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1058031
Bug #1056440 [src:pyopengl] pyopengl's autopkg tests fail with Python 3.12
1056440 was not blocked by any bugs.
1056440 was not blocking any bugs.
Added blocking bug(s) of 1056440: 1058031

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

Bug#1056440: pyopengl's autopkg tests fail with Python 3.12

[Sebastiaan Couwenberg]

Control: block -1 by 1058031

This seems to be fixed upstream:

 https://github.com/mcfletch/pyopengl/issues/99

The pyopengl test suite fails because pygame FTBFS with Python 3.12 
(#1058031) this likely also affects the autopkgtest.


--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Kevin Price]

Breaking news:

Am 11.12.23 um 19:14 schrieb Salvatore Bonaccorso:
> I have put binary packages for amd64 built in
> https://people.debian.org/~carnil/tmp/linux/1057967/

I confirm this test kernel is working fine for me, even with non-free
broadcom-sta.

(sent from
"
cat /proc/version

Linux version 6.1.0-0.a.test-amd64 (debian-ker...@lists.debian.org)
(gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian)
2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1a~test (2023-12-11)
"

through

"
modinfo wl

filename:   /lib/modules/6.1.0-0.a.test-amd64/updates/dkms/wl.ko
license:MIXED/Proprietary
alias:  pci:v*d*sv*sd*bc02sc80i*
depends:cfg80211
…"
)

Thank you Salvatore. Let's get this into stable soon.
-- 
Kevin Price

Bug#1058062: marked as done (python-cloup accesses the network while building the docs)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 21:06:45 +
with message-id 
and subject line Bug#1058062: fixed in python-cloup 3.0.3-2
has caused the Debian Bug report #1058062,
regarding python-cloup accesses the network while building the docs
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.)


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

Package: src:python-cloup
Version: 3.0.3-1
Severity: serious
Tags: sid trixie

python-cloup accesses the network while building the docs:

[...]
[autosummary] generating autosummary for: index.rst, pages/aliases.rst, 
pages/arguments.rst, pages/changelog.rst, pages/constraints.rst, 
pages/contributing.rst, pages/credits.rst, pages/formatting.rst, 
pages/installation.rst, pages/misc.rst, pages/option-groups.rst, 
pages/sections.rst

loading intersphinx inventory from https://docs.python.org/objects.inv...
loading intersphinx inventory from 
https://click.palletsprojects.com/objects.inv...

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries 
exceeded with url: /objects.inv (Caused by ProxyError('Cannot connect to 
proxy.', NewConnectionError('at 0x7ffbe549a4d0>: Failed to establish a new connection: [Errno 111] 
Connection refused')))

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://click.palletsprojects.com/objects.inv' 
not fetchable due to : 
HTTPSConnectionPool(host='click.palletsprojects.com', port=443): Max 
retries exceeded with url: /objects.inv (Caused by ProxyError('Cannot 
connect to proxy.', 
NewConnectionError('0x7ffbe54fcb90>: Failed to establish a new connection: [Errno 111] 
Connection refused')))

building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 12 source files that are out of date
--- End Message ---
--- Begin Message ---
Source: python-cloup
Source-Version: 3.0.3-2
Done: Timo Röhling 

We believe that the bug you reported is fixed in the latest version of
python-cloup, 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 1058...@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-cloup 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, 11 Dec 2023 21:42:27 +0100
Source: python-cloup
Architecture: source
Version: 3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1058062
Changes:
 python-cloup (3.0.3-2) unstable; urgency=medium
 .
   * Prevent sphinx-build from accessing the network (Closes: #1058062)
Checksums-Sha1:
 738e89c6f5261065a686c026213a03e84ad4a174 3388 python-cloup_3.0.3-2.dsc
 1eae05eef12207c6df3d5dd6978b96689e3d89ea 4628 
python-cloup_3.0.3-2.debian.tar.xz
Checksums-Sha256:
 df28bc95c378b9c7cab2842b3c347b87b71a102b5bf9e1c8656c4371d47a6c6b 3388 
python-cloup_3.0.3-2.dsc
 1ec25acb64dbe174d1deb77be735e1fb20e691190f4608bf0f50c49ee530bf63 4628 
python-cloup_3.0.3-2.debian.tar.xz
Files:
 3a192c4e189b47ac0909cd5b4b16fb4a 3388 python optional python-cloup_3.0.3-2.dsc
 97efe13d021a83effa9ec0c649b21c53 4628 python optional 
python-cloup_3.0.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmV3eCoUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVl6HAwA38SpS2r6PMvD2QVMDZn3hN6piul+
FXRED4WiBGEz/YcuiMKWob3rZ8nlUyEBUjVXpIqGRwcm1svYFlSsBsRwJZ5qq4rP
Fxfq+658yKNXwBIgf7KyLg6gd1znRTpBoZUbzsgeo3Vpv9+gMewyRkX46AJtfP3u
u13hiYQLwRQwl+V262NBwrXVQin5oJvcM91SjTn/K3Xptff/i9LFz55hWrF0tsJP
5PMzVgO29NUz55eyYOxWlvoqKa249ia/ELGR949CS5EQbsvzlgJrKt9JbC2Bi+AP
XEjg0y3IHG1r3SBjHlNnRM2P/TXD27/MpOX8pwHB1QP7Yegrw0h0lwF+EstV/gVT
b2mgpPNcKuz2ho8bP4uFc49d7JqdtrEjyKfVuSOBe2a9uRxXwedNQqMKehi3NASe
5uZB+tHk6s+6zmZPhggooXgBpw4QG7mI7NG78TFYhok8NMZiBeMpRMgfQiFuK1eA
/8n9bi1vKFhiNrLBBxrG1M0/9rdNyjXtDYcv
=lW+p
-END PGP SIGNATURE End Message ---

Processed: Bug#1058062 marked as pending in python-cloup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058062 [src:python-cloup] python-cloup accesses the network while 
building the docs
Added tag(s) pending.

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

Bug#1058062: marked as pending in python-cloup

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1058062 in python-cloup 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-cloup/-/commit/db824151c6bc94bf9b5edd3dd84fb64fc8feaee3


Prevent sphinx-build from accessing the network

Closes: #1058062


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058062

Processed: Re: Bug#1058038: texlive-extra: Blocker bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1058038 [src:texlive-extra] texlive-extra: Blocker bug
Severity set to 'serious' from 'normal'

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

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Andreas Tille]

Hi Alexandre,

Am Mon, Dec 11, 2023 at 09:18:16PM +0100 schrieb Alexandre Detiste:
> > https://github.com/lebigot/uncertainties/releases/tag/3.1.7
> 
> +1

OK.
 
> > Also we should probably get rid of python-future at some point.
> 
> I removed it from three games this week-end
> and filled 6 more bugs since to remove extraneous stale dependency.
> 
> There are in fact more fake stale dependencies than remaining true ones
> It takes like 10 minutes to review one package.
> It's a peaceful life.
> 
> https://salsa.debian.org/games-team/ardentryst/-/commit/fc6901b0e90b6bb3ec19b23c1c2d458d653b2d4a
> 
> I will continue this review.

I've seen your bug reports on some Debian Med packages and will try
to fix these as quickly as possible.
 
Thanks a lot for your invesigation and the bug reports
   Andreas.

-- 
http://fam-tille.de

Bug#1058062: python-cloup accesses the network while building the docs

[Matthias Klose]

Package: src:python-cloup
Version: 3.0.3-1
Severity: serious
Tags: sid trixie

python-cloup accesses the network while building the docs:

[...]
[autosummary] generating autosummary for: index.rst, pages/aliases.rst, 
pages/arguments.rst, pages/changelog.rst, pages/constraints.rst, 
pages/contributing.rst, pages/credits.rst, pages/formatting.rst, 
pages/installation.rst, pages/misc.rst, pages/option-groups.rst, 
pages/sections.rst

loading intersphinx inventory from https://docs.python.org/objects.inv...
loading intersphinx inventory from 
https://click.palletsprojects.com/objects.inv...

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries 
exceeded with url: /objects.inv (Caused by ProxyError('Cannot connect to 
proxy.', NewConnectionError('at 0x7ffbe549a4d0>: Failed to establish a new connection: [Errno 111] 
Connection refused')))

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://click.palletsprojects.com/objects.inv' 
not fetchable due to : 
HTTPSConnectionPool(host='click.palletsprojects.com', port=443): Max 
retries exceeded with url: /objects.inv (Caused by ProxyError('Cannot 
connect to proxy.', 
NewConnectionError('0x7ffbe54fcb90>: Failed to establish a new connection: [Errno 111] 
Connection refused')))

building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 12 source files that are out of date

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Alexandre Detiste]

Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof  a écrit :
> I think the right thing here is to package the new uncertainties version
> which drops the past import:
>
> https://github.com/lebigot/uncertainties/releases/tag/3.1.7

+1

> Also we should probably get rid of python-future at some point.

I removed it from three games this week-end
and filled 6 more bugs since to remove extraneous stale dependency.

There are in fact more fake stale dependencies than remaining true ones
It takes like 10 minutes to review one package.
It's a peaceful life.

https://salsa.debian.org/games-team/ardentryst/-/commit/fc6901b0e90b6bb3ec19b23c1c2d458d653b2d4a

I will continue this review.

The existing bugs can be tagged someway if that helps.

Greetings


python3-gnocchi  0
python3-mir-eval 1
dioptas  2
python3-bioxtasraw   2
openqa-client3
rocketcea3
graide   5
python3-emperor  5
python3-grapefruit   6
python3-stomper  6
python3-junitparser  7
python3-pyhamtools   8
python3-pyxnat   11
onionbalance 16
python3-graphite216
python3-picopore 16
turing   16
autoradio17 #1054207
python3-biomaj3  24
python3-flask-autoindex  25
python3-scikit-rf26
radon29
osdlyrics30
python3-pyswarms 30
python3-pyocd34
bugwarrior   40
python3-gnocchiclient47
buildbot-worker  63
python3-bibtexparser 71
weechat-matrix   71
gnome-keysign82---> upstream
python3-proselint83
python3-cpuset   90
python3-mdp  143   old_div
python3-yade 192   c++
python3-plaso212   RM
python3-uncertainties262   package new version
chirp321   non
duplicity10757

Processed: Re: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1058018 [libadios2-common-core-dev] libadios2-common-core-dev has an 
undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake
Severity set to 'important' from 'serious'

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

Bug#1058018: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

[Drew Parsons]

Source: adios2
Followup-For: Bug #1058018
Control: severity -1 important

Call it teething issues. This is a new package, so I'm trying to avoid
making debian/control more verbose than it needs to be by not crowding
the fields with the strict specifications needed to avoid this error.

Once the new version migrates to testing, I'll close this bug and we
can pretend it never happened.

Bug#1057843: linux: ext4 data corruption in 6.1.64-1

[Salvatore Bonaccorso]

As there were some questions along in this thread let me summarize
some points:

The issue affects fs/ext4 code, so no other filesystems are affected
(e.g. btrfs).

The issue affects all kernels which have the commit 91562895f803
("ext4: properly sync file size update after O_SYNC direct IO") from
6.7-rc1 (which is present in 6.6.3, 6.5.13 and 6.1.64) but when commit
936e114a245b ("iomap: update ki_pos a little later in
iomap_dio_complete") from 6.5-rc1 is missing (which was backported to
5.15.142 and 6.1.66 additionally).

The only upstream combination where that reverse and missing commit
happened was 6.1.64 and 6.1.65. 

Debian is affected as per 6.1.64-1 upload which was the kernel aimed
for 12.3 point release.

The issue affects file corruption when direct IO writes are involved.
O_DIRECT writes did not properly update current file position after
the write so data and file was getting mangled.

While this does not affect every write ever happend on the system on a
ext4 filesystem with a broken kernel, O_DIRECT writes might be quite
common in in programms trying to get high performance. It might be
argued that it is not that common, but it's not inexistant.

TTOMK, such file corruptions cannot be easily detected. Candidates to
check are every modified file written since booted with the broken
kernel 6.1.64-1.

Poeple still not having booted into 6.1.66-1 are urged to do so.

Regards,
Salvatore

Bug#1056531: cython 3.x (for Python 3.12)

[Julian Gilbey]

On Mon, Dec 11, 2023 at 08:06:41PM +0100, Matthias Klose wrote:
> > [...]
> > Excellent - I didn't know about that.  Are you OK for me to upload
> > versions of cython and cython-legacy which depend on this to fix the
> > Python 3.12 breakage?
> 
> not for cython, which won't need that soonish for 3.0.x.  and if you have to
> update the b-d to cython3-legacy, why not add the zombie-imp dependency as
> well manually for the few packages that need it?

The problem is not with other packages importing imp (which need to
be fixed in such a case), rather that pyximport (in
cython/cython-legacy) imports imp.  So it's cython that needs to be
patched.

I'm wondering what the provisional timescale for cython 3.0.x is?
Should I just leave my package with an autopkgtest failure until
cython 3.0.x is in unstable or ideally testing?  That's why I was
thinking of also patching cython in the short term until we are ready
for cython 3.0.x to enter unstable.

Best wishes,

   Julian

Bug#1056531: cython 3.x (for Python 3.12)

[Matthias Klose]

On 11.12.23 19:55, Julian Gilbey wrote:

On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:

On 11.12.23 16:19, Julian Gilbey wrote:

On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:

[...]
You could package a non-conflicting cython-legacy, however that would
require more changes, also how to build it.


Hi Matthias,

Unfortunately, at least some of cython3-legacy doesn't currently work
with Python 3.12, and is the primary cause of (at least) #1056531.
cython3 provides the pyximport module, and that uses the imp module
which has been removed from Python 3.12.

Two possible ways forward on this particular bug:

- Disable all of the cython tests for this package for the time being,
until cython 3.x migrates to testing - this is simple and effective.

- Patch cython3-legacy to use importlib rather than imp.  This is
probably a good thing to do anyway.  (It may also be good to do this
with cython3 version 0.x currently in testing/unstable until cython
3.x is able to be uploaded to unstable.)  Then have my package's
autopkgtest depend on cython3-legacy (unless cython3 0.x is also
patched).


I won't working on this. Have you tried to depend on the python3-zombie-imp
instead?


Excellent - I didn't know about that.  Are you OK for me to upload
versions of cython and cython-legacy which depend on this to fix the
Python 3.12 breakage?


not for cython, which won't need that soonish for 3.0.x.  and if you 
have to update the b-d to cython3-legacy, why not add the zombie-imp 
dependency as well manually for the few packages that need it?

Bug#1056531: cython 3.x (for Python 3.12)

[Julian Gilbey]

On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
> On 11.12.23 16:19, Julian Gilbey wrote:
> > On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> > > [...]
> > > You could package a non-conflicting cython-legacy, however that would
> > > require more changes, also how to build it.
> > 
> > Hi Matthias,
> > 
> > Unfortunately, at least some of cython3-legacy doesn't currently work
> > with Python 3.12, and is the primary cause of (at least) #1056531.
> > cython3 provides the pyximport module, and that uses the imp module
> > which has been removed from Python 3.12.
> > 
> > Two possible ways forward on this particular bug:
> > 
> > - Disable all of the cython tests for this package for the time being,
> >until cython 3.x migrates to testing - this is simple and effective.
> > 
> > - Patch cython3-legacy to use importlib rather than imp.  This is
> >probably a good thing to do anyway.  (It may also be good to do this
> >with cython3 version 0.x currently in testing/unstable until cython
> >3.x is able to be uploaded to unstable.)  Then have my package's
> >autopkgtest depend on cython3-legacy (unless cython3 0.x is also
> >patched).
> 
> I won't working on this. Have you tried to depend on the python3-zombie-imp
> instead?

Excellent - I didn't know about that.  Are you OK for me to upload
versions of cython and cython-legacy which depend on this to fix the
Python 3.12 breakage?

Best wishes,

   Julian

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Salvatore Bonaccorso]

Hi,

On Mon, Dec 11, 2023 at 01:27:07PM +0100, Kevin Price wrote:
> Thank you Salvatore!
> 
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> > It still would be helpfull if you can get to the logs of the previous
> > boot. After booting back in the working kernel, do you have anything
> > sensible logged in the previous boot log? If so can you share that
> > please?
> 
> Sure. Here's my boot.log.

I was more interested to get some nformation from the kernel. If you
get dmesg output that would be good, maybe the journalctl from the bug
otherwise, which will help to get more context.

> 
> The first one at "Mon Dec 11 00:54:03 CET 2023" is the faulty 6.1.0-15.
> 
> The 2nd one at "Mon Dec 11 01:13:38 CET 2023" is the working 6.1.0-13.
> 
> Need any more logfiles or testing? I intend to test
> debian-live-12.4.0-amd64-gnome.iso on my computer, IOT rule out any
> local config peculiarities, FWIW.
> 
> > I'm right now curious to find out if we see the same as
> > #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> > cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> > issue.
> 
> Please let me know what kernel version you want me to test, if they're
> provides as debian binaries. I'd be glad to help, probably not only for
> my own sake. Bear with me I'm unwilling to build kernel packages myself,
> due to lack of computing resources. HTH

I have put binary packages for amd64 built in
https://people.debian.org/~carnil/tmp/linux/1057967/

*but* they are completely unofficial builds. To give assurance of
provenance I have generated a sha256sum file as well for the uploaded
files and signed it with my key in the Debian keyring.

If you personal policy allows you to install such packages please test
with those, otherwise we need you to have built your own packages.

Regards,
Salvatore

Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4

[Alexander Kjäll]

Hi

I'm sorry for the semver breakage, the last version was a bit stressed
out due to the security problems with libgit2 not verifying server
signatures (that has since been fixed).

I think the best path forward might be to package the latest versions,
I have started that but not finished yet due to some real life things
taking all my free time lately.

best regards
Alexander Kjäll

Bug#1057843: Bug patching

[Sergiu]

Hi

Any new information, when will this be patched?
There are packages that can not be installed like nvidia-driver because
while installing it updates the system and the process fails.

Isn't possible to remove from the repo the corrupted kernel so that people
can install other packages?


Regards,
Sergiu

Bug#1058047: gammapy: FTBFS with Python 3.12

[Graham Inggs]

Source: gammapy
Version: 1.1-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

gammapy FTBFS [1] with Python 3.12 as a supported version.  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=gammapy


=== FAILURES ===
_ test_parameter_name __

def test_parameter_name():
with pytest.raises(RuntimeError):

>   class MyTestModel:

gammapy/modeling/models/tests/test_core.py:256:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = Parameter(name='wrong-name', value=3.0, factor=3.0, scale=1.0,
unit=Unit(dimensionless), min=nan, max=nan, frozen=False,
id=0x8e307aa0)
owner = .MyTestModel'>
name = 'par'

def __set_name__(self, owner, name):
if not self._name == name:
>   raise ValueError(f"Expected parameter name '{name}', got 
> {self._name}")
E   ValueError: Expected parameter name 'par', got wrong-name
E   Error calling __set_name__ on 'Parameter' instance 'par'
in 'MyTestModel'

gammapy/modeling/parameter.py:165: ValueError

Bug#1057843: linux: ext4 data corruption in 6.1.64-1

[Dennis Grevenstein]

On Mon, 11 Dec 2023 10:38:40 +0100 helios.sola...@gmx.ch wrote:
> I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
> how can I find out whether the file system has been corrupted?

yes, I would also appreciate an explanation who could be affected,
how to diagnose the problem, and what needs to be done.
Please note that not all the users of Debian stable are kernel hackers
who will be able to look at the filesystem code and understand the
full extent of the problem.

thanks,
Dennis

Bug#1057614: marked as done (python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 16:52:56 +
with message-id 
and subject line Bug#1057614: fixed in python-kaptan 0.6.0-1
has caused the Debian Bug report #1057614,
regarding python-kaptan: FTBFS: chmod: cannot access 
'/<>/kaptan.egg-info/*': No such file or directory
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.)


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

Package: src:python-kaptan
Version: 0.5.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
Warning: 'classifiers' should be a list, got type 'tuple'
running config
I: pybuild base:310: python3.11 setup.py config
Warning: 'classifiers' should be a list, got type 'tuple'
running config
   debian/rules execute_before_dh_auto_build
make[1]: Entering directory '/<>'
chmod -x /<>/kaptan.egg-info/*
chmod: cannot access '/<>/kaptan.egg-info/*': No such file or 
directory
make[1]: *** [debian/rules:9: execute_before_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-kaptan
Source-Version: 0.6.0-1
Done: Jeroen Ploemen 

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

Debian distribution maintenance software
pp.
Jeroen Ploemen  (supplier of updated python-kaptan 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, 11 Dec 2023 16:38:41 +
Source: python-kaptan
Built-For-Profiles: noudeb
Architecture: source
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jeroen Ploemen 
Closes: 1057614
Changes:
 python-kaptan (0.6.0-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream version 0.6.0
   * Rules: remove chmod of egg-info. (Closes: #1057614)
   * Bump Standards-Version to 4.6.2 (from 4.6.0; no further changes).
   * Control: set Testsuite: autopkgtest-pkg-pybuild.
Checksums-Sha1:
 4d5bbc851cc3902fdc61df4db5732959cdcaecca 2050 python-kaptan_0.6.0-1.dsc
 f8825dd5a5d22e41589fe0627718ef9568513e19 11861 python-kaptan_0.6.0.orig.tar.gz
 33547a948acefcdb2f4c2b9b42dfc606c64728f5 3292 
python-kaptan_0.6.0-1.debian.tar.xz
 8a23e19ff56ffd4cff176274f82258566856e0d0 15183 
python-kaptan_0.6.0-1_source.buildinfo
Checksums-Sha256:
 713c67fe02e870b06e338ca2d6278efdfaa718817a64b0dc34dc75c24d00c542 2050 
python-kaptan_0.6.0-1.dsc
 101330a44fdede888586f3010bd145c0ec48a4806bc56429fa5487a6774021f8 11861 
python-kaptan_0.6.0.orig.tar.gz
 507caa48036f1b7deaf04634810a2c89ecc65f2204e7665a1d2ba3ba12b5a3e8 3292 
python-kaptan_0.6.0-1.debian.tar.xz
 6b3004c481f06b3e81d0a2f72a4751962ab7e1eb74e8bbe4fe74d900d890e5ea 15183 
python-kaptan_0.6.0-1_source.buildinfo
Files:
 

Bug#1055597: marked as done (libmail-message-perl: off-by-one error wrt to newlines after a multipart separator)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 16:49:43 +
with message-id 
and subject line Bug#1055597: fixed in libmail-message-perl 3.015-1
has caused the Debian Bug report #1055597,
regarding libmail-message-perl: off-by-one error wrt to newlines after a 
multipart separator
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.)


-- 
1055597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmail-box-perl
Version: 3.010-1
Severity: serious
Tags: upstream ftbfs trixie sid
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=150141

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.debian.net, e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmail-box-perl/39681951/log.gz
and also upstream at https://rt.cpan.org/Public/Bug/Display.html?id=150141
- --> 
https://www.cpantesters.org/cpan/report/4063279a-6e7d-11ee-a059-85ce9d387f07
libmail-box-perl's t/505parser-bodymp.t fails with
libmail-message-perl_3.014-1

#   Failed test '1 lines 0'
#   at t/505parser-bodymp.t line 68.
#  got: 22
# expected: 21
   
#   Failed test '1 lines 1'
#   at t/505parser-bodymp.t line 68.
#  got: 83
# expected: 82

#   Failed test '1 lines 2'
#   at t/505parser-bodymp.t line 68.
#  got: 35
# expected: 34
# Looks like you failed 3 tests of 313.
t/505parser-bodymp.t .
1..313
ok 1 - creation of parser
ok 2 - 1 from 0
ok 3 - 1 head count
ok 4 - 1 from 0
ok 5 - 1 head count
ok 6 - 1 from 0
ok 7 - 1 head count
ok 8 - 1 from 0
ok 9 - 1 head count
ok 10 - 1 from 0
ok 11 - 1 head count
ok 12 - 1 from 0
ok 13 - 1 head count
ok 14 - 1 from 0
ok 15 - 1 head count
ok 16 - 1 from 0
ok 17 - 1 head count
ok 18 - 1 from 0
ok 19 - 1 head count
ok 20 - 1 from 0
ok 21 - 1 head count
ok 22 - 1 from 0
ok 23 - 1 head count
ok 24 - 1 from 0
ok 25 - 1 head count
ok 26 - 1 from 0
ok 27 - 1 head count
ok 28 - 1 from 0
ok 29 - 1 head count
ok 30 - 1 from 0
ok 31 - 1 head count
ok 32 - 1 from 0
ok 33 - 1 head count
ok 34 - 1 from 0
ok 35 - 1 head count
ok 36 - 1 from 0
ok 37 - 1 head count
ok 38 - 1 from 0
ok 39 - 1 head count
ok 40 - 1 from 0
ok 41 - 1 head count
ok 42 - 1 from 0
ok 43 - 1 head count
ok 44 - 1 body 0
not ok 45 - 1 lines 0
ok 46 - 1 size 0
ok 47 - 1 from 1
ok 48 - 1 head count
ok 49 - 1 from 1
ok 50 - 1 head count
ok 51 - 1 from 1
ok 52 - 1 head count
ok 53 - 1 from 1
ok 54 - 1 head count
ok 55 - 1 from 1
ok 56 - 1 head count
ok 57 - 1 body 1
not ok 58 - 1 lines 1
ok 59 - 1 size 1
ok 60 - 1 from 2
ok 61 - 1 head count
ok 62 - 1 from 2
ok 63 - 1 head count
ok 64 - 1 body 2
not ok 65 - 1 lines 2
ok 66 - 1 size 2
ok 67 - 1 from 3
ok 68 - 1 head count
ok 69 - 1 from 3
ok 70 - 1 head count
ok 71 - 1 from 3
ok 72 - 1 head count
ok 73 - 1 from 3
ok 74 - 1 head count
ok 75 - 1 from 3
ok 76 - 1 head count
ok 77 - 1 from 3
ok 78 - 1 head count
ok 79 - 1 from 3
ok 80 - 1 head count
ok 81 - 1 from 3
ok 82 - 1 head count
ok 83 - 1 from 3
ok 84 - 1 head count
ok 85 - 1 from 3
ok 86 - 1 head count
ok 87 - 1 from 3
ok 88 - 1 head count
ok 89 - 1 from 3
ok 90 - 1 head count
ok 91 - 1 from 3
ok 92 - 1 head count
ok 93 - 1 from 3
ok 94 - 1 head count
ok 95 - 1 from 3
ok 96 - 1 head count
ok 97 - 1 from 3
ok 98 - 1 head count
ok 99 - 1 from 3
ok 100 - 1 head count
ok 101
ok 102 - 2 from 0
ok 103 - 2 head 0
ok 104 - 2 from 0
ok 105 - 2 head 0
ok 106 - 2 from 0
ok 107 - 2 head 0
ok 108 - 2 from 0
ok 109 - 2 head 0
ok 110 - 2 from 0
ok 111 - 2 head 0
ok 112 - 2 from 0
ok 113 - 2 head 0
ok 114 - 2 from 0
ok 115 - 2 head 0
ok 116 - 2 from 0
ok 117 - 2 head 0
ok 118 - 2 from 0
ok 119 - 2 head 0
ok 120 - 2 from 0
ok 121 - 2 head 0
ok 122 - 2 from 0
ok 123 - 2 head 0
ok 124 - 2 from 0
ok 125 - 2 head 0
ok 126 - 2 from 0
ok 127 - 2 head 0
ok 128 - 2 from 0
ok 129 - 2 head 0
ok 130 - 2 from 0
ok 131 - 2 head 0
ok 132 - 2 from 0
ok 133 - 2 head 0
ok 134 - 2 from 0
ok 135 - 2 head 0
ok 136 - 2 from 0
ok 137 - 2 head 0
ok 138 - 2 from 0
ok 139 - 2 head 0
ok 140 - 2 from 0
ok 141 - 2 head 0
ok 142 - 2 from 0
ok 143 - 2 head 0
ok 144 - 2 body 0
ok 145 - 2 size 0
ok 146 - 2 lines 0
ok 147 - 2 names 0
ok 148 - 2 sep 0
ok 149 - 2 from 1
ok 150 - 2 head 1
ok 151 - 2 from 1
ok 152 - 2 head 1
ok 153 - 2 from 1
ok 154 - 2 head 1
ok 155 - 2 from 1
ok 156 - 2 head 1
ok 157 - 2 from 1
ok 158 - 2 head 1
ok 159 - 2 body 1
ok 160 - 2 size 1
ok 161 - 2 lines 1
ok 162 - 2 subject 1
ok 163 - 2 names 1
ok 164 - 2 sep 1
ok 165 - 2 from 2
ok 166 - 2 head 2
ok 167 - 2 from 2
ok 168 - 2 head 2
ok 169 - 2 body 2

Bug#1056493: marked as done (python-pulp's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 16:38:06 +
with message-id 
and subject line Bug#1056493: fixed in python-pulp 2.7.0+dfsg-2
has caused the Debian Bug report #1056493,
regarding python-pulp's autopkg tests fail with Python 3.12
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.)


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

Package: src:python-pulp
Version: 2.7.0+dfsg-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-pulp's autopkg tests fail with Python 3.12, although I cannot see 
from the test log, what exactly is failing. Please could you have a look 
at the build log?


complete test log at
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/p/python-pulp/20231118_184757_b46d3@/log.gz
--- End Message ---
--- Begin Message ---
Source: python-pulp
Source-Version: 2.7.0+dfsg-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated python-pulp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Dec 2023 21:49:10 +0530
Source: python-pulp
Architecture: source
Version: 2.7.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Nilesh Patra 
Closes: 1056493
Changes:
 python-pulp (2.7.0+dfsg-2) unstable; urgency=medium
 .
   * Specify the test dir to fix autopkgtests (Closes: #1056493)
Checksums-Sha1:
 42f3036b07bea96c9e1bcd075ff80d0b002d1ea7 1571 python-pulp_2.7.0+dfsg-2.dsc
 2b0d324b056971e049a305b7d1a4473f9efbb175 13044 
python-pulp_2.7.0+dfsg-2.debian.tar.xz
 d28340e200d3d107b1bb55bf54abdcc5dc9fea60 6180 
python-pulp_2.7.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 b3625c9fab95b68eeb5d80258f3668e5cc2ee13f112ecf5550349ba3458bd562 1571 
python-pulp_2.7.0+dfsg-2.dsc
 114f66a2e9aa523c96a5e8af545e127b5d1592b603267bdacbbd31ef02d5e73a 13044 
python-pulp_2.7.0+dfsg-2.debian.tar.xz
 dc1c482ae80939407bd399352f069799ec2ecb6f307211518633892c13fb4983 6180 
python-pulp_2.7.0+dfsg-2_amd64.buildinfo
Files:
 49743c1fc402b029cf94ca778a66f824 1571 python optional 
python-pulp_2.7.0+dfsg-2.dsc
 ebf388ac11bb37e530b1226f58934b89 13044 python optional 
python-pulp_2.7.0+dfsg-2.debian.tar.xz
 7dd47541ab5334ae08cb2c6b7be4288d 6180 python optional 
python-pulp_2.7.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZXc3fwAKCRAqJ5BL1yQ+
2mLeAQCdqLWGyZZJy4D8D6E/4ftqkLLrlGezHYXWZpAMf/O7YAD9Hm6LIatb9OjE
icdBSPMB3k32ZcggXxRNhqO5iwxu0g4=
=dSkU
-END PGP SIGNATURE End Message ---

Processed: Re: gst-python1.0 ftbfs with Python 3.12

[Debian Bug Tracking System]

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

> forwarded 1055575 
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3170
Bug #1055575 [src:gst-python1.0] gst-python1.0 ftbfs with Python 3.12
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3170'.
>
End of message, stopping processing here.

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

Bug#1056487: marked as done (python-multipletau's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 16:22:54 +
with message-id 
and subject line Bug#1056487: fixed in python-multipletau 0.3.3+ds-5
has caused the Debian Bug report #1056487,
regarding python-multipletau's autopkg tests fail with Python 3.12
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.)


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

Package: src:python-multipletau
Version: 0.3.3+ds-4
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-multipletau's autopkg tests fail with Python 3.12:

[...]
319s autopkgtest [18:46:07]: test command1: [---
319s = test session starts 
==

319s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
319s rootdir: /tmp/autopkgtest.flrZSi/build.lZH/src
319s collected 0 items / 8 errors
319s
319s  ERRORS 

319s _ ERROR collecting tests/test_ac_cc.py 
_
319s ImportError while importing test module 
'/tmp/autopkgtest.flrZSi/build.lZH/src/tests/test_ac_cc.py'.

319s Hint: make sure your test modules/packages have valid Python names.
319s Traceback:
319s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
319s return _bootstrap._gcd_import(name[level:], package, level)
319s tests/test_ac_cc.py:10: in 
319s import multipletau
319s multipletau/__init__.py:75: in 
319s from ._version import version as __version__  # noqa: F401
319s multipletau/_version.py:15: in 
319s import imp
319s E   ModuleNotFoundError: No module named 'imp'
319s _ ERROR collecting tests/test_autocorrelate.py 
_
319s ImportError while importing test module 
'/tmp/autopkgtest.flrZSi/build.lZH/src/tests/test_autocorrelate.py'.

319s Hint: make sure your test modules/packages have valid Python names.
319s Traceback:
319s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
319s return _bootstrap._gcd_import(name[level:], package, level)
319s tests/test_autocorrelate.py:12: in 
319s import multipletau
319s multipletau/__init__.py:75: in 
319s from ._version import version as __version__  # noqa: F401
319s multipletau/_version.py:15: in 
319s import imp
319s E   ModuleNotFoundError: No module named 'imp'
319s _ ERROR collecting tests/test_basic.py 
_
319s ImportError while importing test module 
'/tmp/autopkgtest.flrZSi/build.lZH/src/tests/test_basic.py'.

319s Hint: make sure your test modules/packages have valid Python names.
319s Traceback:
319s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
319s return _bootstrap._gcd_import(name[level:], package, level)
319s tests/test_basic.py:6: in 
319s from multipletau import autocorrelate, correlate
319s multipletau/__init__.py:75: in 
319s from ._version import version as __version__  # noqa: F401
319s multipletau/_version.py:15: in 
319s import imp
319s E   ModuleNotFoundError: No module named 'imp'
319s ___ ERROR collecting tests/test_compress.py 

319s ImportError while importing test module 
'/tmp/autopkgtest.flrZSi/build.lZH/src/tests/test_compress.py'.

319s Hint: make sure your test modules/packages have valid Python names.
319s Traceback:
319s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
319s return _bootstrap._gcd_import(name[level:], package, level)
319s tests/test_compress.py:6: in 
319s from multipletau import autocorrelate, correlate
319s multipletau/__init__.py:75: in 
319s from ._version import version as __version__  # noqa: F401
319s multipletau/_version.py:15: in 
319s import imp
319s E   ModuleNotFoundError: No module named 'imp'
319s ___ ERROR collecting tests/test_correlate.py 
___
319s ImportError while importing test module 
'/tmp/autopkgtest.flrZSi/build.lZH/src/tests/test_correlate.py'.

319s Hint: make sure your test modules/packages have valid Python names.
319s Traceback:
319s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
319s return _bootstrap._gcd_import(name[level:], package, level)
319s tests/test_correlate.py:11: in 
319s import multipletau
319s multipletau/__init__.py:75: in 
319s from ._version import version as __version__  # noqa: F401
319s multipletau/_version.py:15: in 
319s import imp
319s E   

Processed: reassign 1055597 to libmail-message-perl, affects 1055597, tagging 1055597 ...

[Debian Bug Tracking System]

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

> reassign 1055597 libmail-message-perl 3.014-1
Bug #1055597 [src:libmail-box-perl] FTBFS: test failure with Mail-Message 3.014
Bug reassigned from package 'src:libmail-box-perl' to 'libmail-message-perl'.
No longer marked as found in versions libmail-box-perl/3.010-1.
Ignoring request to alter fixed versions of bug #1055597 to the same values 
previously set
Bug #1055597 [libmail-message-perl] FTBFS: test failure with Mail-Message 3.014
Marked as found in versions libmail-message-perl/3.014-1.
> affects 1055597 = libmail-box-perl
Bug #1055597 [libmail-message-perl] FTBFS: test failure with Mail-Message 3.014
Added indication that 1055597 affects libmail-box-perl
> tags 1055597 + fixed-upstream
Bug #1055597 [libmail-message-perl] FTBFS: test failure with Mail-Message 3.014
Added tag(s) fixed-upstream.
> retitle 1055597 libmail-message-perl: off-by-one error wrt to newlines after 
> a multipart separator
Bug #1055597 [libmail-message-perl] FTBFS: test failure with Mail-Message 3.014
Changed Bug title to 'libmail-message-perl: off-by-one error wrt to newlines 
after a multipart separator' from 'FTBFS: test failure with Mail-Message 3.014'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Added indication that 1057967 affects src:broadcom-sta and 
linux-image-6.1.0-15-amd64

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

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Kevin Price]

Control: affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64

@other affected users: What wifi drivers are you using, and do they
taint your kernel?

Am 11.12.23 um 13:27 schrieb Kevin Price:
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:

> Need any more logfiles or testing?

Is it syslog that might help you better, or any other log? Just let me
know please. I'd love to help figure this out with mutual support.

> I intend to test debian-live-12.4.0-amd64-gnome.iso

*drumroll* Now this comes as a surprise to me.
debian-live-12.4.0-amd64-gnome displays none of the bad behavior, even
when actively using wifi. Apart from firmware, there's no non-free
involved in debian-live.

So could it be just some local configuration choice of mine, and of all
the other affected users? Some years-old but possibly now poor choice of
drivers/firmware maybe? I faintly remember having tried a free driver on
this card at least two debian releases ago, but it worked so bad I had
to switch to a non-free one:
https://packages.debian.org/bookworm/broadcom-sta-dkms

Which since has been upgraded with each debian release.

Another Test: My old hardware has a physical RF kill switch. So I booted
up 6.1.0-15 with it turned off: *drumroll* Works fine. So wifi seems to
be singled out as the culprit in my case. (or possibly bluetooth, but I
strongly doubt)

See attachments regarding my wifi. Shame on me, if anyone ever
suggested: "Never file a bug against a tainted kernel", because I did.
But maybe it was good to do so. Because this bug is still very relevant,
as it affects not only me, but renders multiple people's computers
practically unusable when upgrading to 6.1.0-15. Not like "wifi gone
bad", but "computer gone bad". This shouldn't happen within a stable
debian release IMHO, and thus justifies some fairly high level of
severity, IMHO. "critical", IDK. You own this bug, you decide.

Now I conclude that 6.1.0-15 not only breaks src:broadcom-sta, but also
vice versa. Are there any other wifi drivers affected?

>> I'm right now curious to find out if we see the same as
>> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
>> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
>> issue.

Now that sounds to me like exactly what caused this. Good to know that
upstream has already reverted this regression. Please let me know what
else to test or contribute, so that we can look forward to a debian
stable 6.1 kernel without this bug.

@Salvatore: Thanks a ton for your excellent work. Very much appreciated.

HTH
-- 
Kevin Pricesudo lspci -vvs2:0
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn 
Wireless Network Adapter (rev 01)
Subsystem: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless 
Network Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
SlotPowerLimit 10W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- 
ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog:    
Capabilities: [13c v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
  

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Jochen Sprickerhof]

Hi Andreas,

* Andreas Tille  [2023-12-11 16:42]:

Control: tags -1 help

[Bug #1056419 in CC since the issue seems to be caused by python-future]

Hi Vincent,

I tried to upgrade python-future to the latest upstream version in the
hope that this would solve the issue reported in bug #1042244.
Unfortunately this is not the case and now with Python3.12 we also
have to deal with the removal of imp (which affects bug #1056419).

I'd like to ask for help on debian-python list since I'm pretty
overworked with other stuff.  Please also review my rude patch[1] to
hack around a shinx issue.  It would be great to have some better
solution here.

You can find a full build log of the latest upstream version in
Salsa CI[2].


I think the right thing here is to package the new uncertainties version 
which drops the past import:


https://github.com/lebigot/uncertainties/releases/tag/3.1.7

Also we should probably get rid of python-future at some point.

Cheers Jochen


signature.asc
Description: PGP signature

Processed: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1042244 [src:python-future] python-future: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) help.

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

Processed: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1056419 [src:lmfit-py] lmfit-py's autopkg tests fail with Python 3.12
Added tag(s) help.

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

Bug#1042244: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Andreas Tille]

Control: tags -1 help

[Bug #1056419 in CC since the issue seems to be caused by python-future]

Hi Vincent,

I tried to upgrade python-future to the latest upstream version in the
hope that this would solve the issue reported in bug #1042244.
Unfortunately this is not the case and now with Python3.12 we also
have to deal with the removal of imp (which affects bug #1056419).

I'd like to ask for help on debian-python list since I'm pretty
overworked with other stuff.  Please also review my rude patch[1] to
hack around a shinx issue.  It would be great to have some better
solution here.

You can find a full build log of the latest upstream version in
Salsa CI[2].

Kind regards
   Andreas.


[1] 
https://salsa.debian.org/python-team/packages/python-future/-/blob/master/debian/patches/hack_around_missing_toint_in_sphinx.patch
[2] https://salsa.debian.org/python-team/packages/python-future/-/jobs/5027089

-- 
http://fam-tille.de

Bug#1056531: cython 3.x (for Python 3.12)

[Matthias Klose]

On 11.12.23 16:19, Julian Gilbey wrote:

On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:

[...]
You could package a non-conflicting cython-legacy, however that would
require more changes, also how to build it.


Hi Matthias,

Unfortunately, at least some of cython3-legacy doesn't currently work
with Python 3.12, and is the primary cause of (at least) #1056531.
cython3 provides the pyximport module, and that uses the imp module
which has been removed from Python 3.12.

Two possible ways forward on this particular bug:

- Disable all of the cython tests for this package for the time being,
   until cython 3.x migrates to testing - this is simple and effective.

- Patch cython3-legacy to use importlib rather than imp.  This is
   probably a good thing to do anyway.  (It may also be good to do this
   with cython3 version 0.x currently in testing/unstable until cython
   3.x is able to be uploaded to unstable.)  Then have my package's
   autopkgtest depend on cython3-legacy (unless cython3 0.x is also
   patched).


I won't working on this. Have you tried to depend on the 
python3-zombie-imp instead?

Bug#1056506: marked as done (python-stone's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 15:19:15 +
with message-id 
and subject line Bug#1056506: fixed in python-stone 3.3.1-3
has caused the Debian Bug report #1056506,
regarding python-stone's autopkg tests fail with Python 3.12
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.)


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

Package: src:python-stone
Version: 3.3.1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-stone's autopkg tests fail with Python 3.12:

[...]
440s = test session starts 
==

440s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
440s rootdir: /tmp/autopkgtest.nD4l2V/autopkgtest_tmp
440s collected 168 items
440s
440s test/test_backend.py ... 
 [  6%]
440s test/test_cli.py . 
 [  7%]
440s test/test_js_client.py ... 
 [  8%]
440s test/test_python_client.py .. 
 [ 14%]
448s test/test_python_gen.py 
FF.F [ 43%]
451s FF 
 [ 51%]
451s test/test_python_type_stubs.py  
 [ 56%]
451s test/test_python_types.py . 
 [ 59%]
457s test/test_stone.py . 
 [ 83%]
457s test/test_stone_internal.py  
 [ 88%]
458s test/test_stone_route_whitelist.py  
 [ 93%]
458s test/test_tsd_client.py ... 
 [ 95%]
458s test/test_tsd_types.py .FFF 
 [100%]

458s
458s === FAILURES 
===
458s __ TestGeneratedPython.test_alias_validators 
___

458s
458s self = testMethod=test_alias_validators>

458s
458s def setUp(self):
458s
458s # Sanity check: stone must be importable for the compiler 
to work

458s importlib.import_module('stone')
458s
458s # Compile spec by calling out to stone
458s p = subprocess.Popen(
458s [sys.executable,
458s  '-m',
458s  'stone.cli',
458s  'python_types',
458s  'output',
458s  '-',
458s  '--',
458s  '--package',
458s  'output'],
458s stdin=subprocess.PIPE,
458s stderr=subprocess.PIPE)
458s _, stderr = p.communicate(
458s input=(test_spec + test_ns2_spec).encode('utf-8'))
458s if p.wait() != 0:
458s >   raise AssertionError('Could not execute stone tool: %s' %
458s  stderr.decode('utf-8'))
458s E   AssertionError: Could not execute stone tool: Traceback 
(most recent call last):

458s E File "", line 198, in _run_module_as_main
458s E File "", line 88, in _run_code
458s E File "/usr/lib/python3/dist-packages/stone/cli.py", 
line 8, in 

458s E   import imp  # pylint: disable=deprecated-module
458s E   ^^
458s E   ModuleNotFoundError: No module named 'imp'
458s
458s test/test_python_gen.py:838: AssertionError
--- End Message ---
--- Begin Message ---
Source: python-stone
Source-Version: 3.3.1-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-stone 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, 11 Dec 2023 15:55:42 +0100
Source: python-stone
Architecture: source
Version: 3.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1056506
Changes:
 python-stone (3.3.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix python3.12 FTBFS
 (Closes: #1056506)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
 8db3ec8d1b85e936e1a71f1d74d28c3f3710cc7b 2219 python-stone_3.3.1-3.dsc
 

Bug#1056531: cython 3.x (for Python 3.12)

[Julian Gilbey]

On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> [...]
> You could package a non-conflicting cython-legacy, however that would
> require more changes, also how to build it.

Hi Matthias,

Unfortunately, at least some of cython3-legacy doesn't currently work
with Python 3.12, and is the primary cause of (at least) #1056531.
cython3 provides the pyximport module, and that uses the imp module
which has been removed from Python 3.12.

Two possible ways forward on this particular bug:

- Disable all of the cython tests for this package for the time being,
  until cython 3.x migrates to testing - this is simple and effective.

- Patch cython3-legacy to use importlib rather than imp.  This is
  probably a good thing to do anyway.  (It may also be good to do this
  with cython3 version 0.x currently in testing/unstable until cython
  3.x is able to be uploaded to unstable.)  Then have my package's
  autopkgtest depend on cython3-legacy (unless cython3 0.x is also
  patched).

Thoughts?

   Julian

Bug#1058040: pymatgen: FTBFS with Python 3.12

[Graham Inggs]

Source: pymatgen
Version: 2023.06.23+dfsg1-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

pymatgen FTBFS [1] with Python 3.12 as a supported version.  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=pymatgen


 ERRORS 
_ ERROR collecting
.pybuild/test_python3.11/pymatgen/analysis/tests/test_chempot_diagram.py
_
ImportError while importing test module
'/<>/.pybuild/test_python3.11/pymatgen/analysis/tests/test_chempot_diagram.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
.pybuild/test_python3.11/pymatgen/analysis/tests/test_chempot_diagram.py:17:
in 
from pymatgen.entries.entry_tools import EntrySet
.pybuild/test_python3.11/pymatgen/entries/entry_tools.py:18: in 
from monty.string import unicode2str
E   ImportError: cannot import name 'unicode2str' from 'monty.string'
(/usr/lib/python3/dist-packages/monty/string.py)
_ ERROR collecting
.pybuild/test_python3.11/pymatgen/analysis/tests/test_cost.py _
ImportError while importing test module
'/<>/.pybuild/test_python3.11/pymatgen/analysis/tests/test_cost.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
.pybuild/test_python3.11/pymatgen/analysis/tests/test_cost.py:8: in 
from pymatgen.analysis.cost import CostAnalyzer, CostDBCSV, CostDBElements
.pybuild/test_python3.11/pymatgen/analysis/cost.py:19: in 
from monty.string import unicode2str
E   ImportError: cannot import name 'unicode2str' from 'monty.string'
(/usr/lib/python3/dist-packages/monty/string.py)
_ ERROR collecting
.pybuild/test_python3.11/pymatgen/analysis/tests/test_phase_diagram.py
_
ImportError while importing test module
'/<>/.pybuild/test_python3.11/pymatgen/analysis/tests/test_phase_diagram.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
.pybuild/test_python3.11/pymatgen/analysis/tests/test_phase_diagram.py:32:
in 
from pymatgen.entries.entry_tools import EntrySet
.pybuild/test_python3.11/pymatgen/entries/entry_tools.py:18: in 
from monty.string import unicode2str
E   ImportError: cannot import name 'unicode2str' from 'monty.string'
(/usr/lib/python3/dist-packages/monty/string.py)
_ ERROR collecting
.pybuild/test_python3.11/pymatgen/entries/tests/test_entry_tools.py _
ImportError while importing test module
'/<>/.pybuild/test_python3.11/pymatgen/entries/tests/test_entry_tools.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
.pybuild/test_python3.11/pymatgen/entries/tests/test_entry_tools.py:12:
in 
from pymatgen.entries.entry_tools import EntrySet,
group_entries_by_composition, group_entries_by_structure
.pybuild/test_python3.11/pymatgen/entries/entry_tools.py:18: in 
from monty.string import unicode2str
E   ImportError: cannot import name 'unicode2str' from 'monty.string'
(/usr/lib/python3/dist-packages/monty/string.py)
_ ERROR collecting
.pybuild/test_python3.11/pymatgen/entries/tests/test_mixing_scheme.py
_
ImportError while importing test module
'/<>/.pybuild/test_python3.11/pymatgen/entries/tests/test_mixing_scheme.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
.pybuild/test_python3.11/pymatgen/entries/tests/test_mixing_scheme.py:116:
in 
from pymatgen.entries.mixing_scheme import MaterialsProjectDFTMixingScheme
.pybuild/test_python3.11/pymatgen/entries/mixing_scheme.py:25: in 
from pymatgen.entries.entry_tools import EntrySet
.pybuild/test_python3.11/pymatgen/entries/entry_tools.py:18: in 
from monty.string import unicode2str
E   ImportError: cannot import name 'unicode2str' from 'monty.string'
(/usr/lib/python3/dist-packages/monty/string.py)

Bug#1058039: cctbx: FTBFS with Python 3.12

[Graham Inggs]

Source: cctbx
Version:  2022.9+ds2+~3.11.2+ds1-6
Severity: serious
Tags: ftbfs sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

cctbx FTBFS [1] with Python 3.12 as a supported version.  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=cctbx


In file included from
/usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
 from
/usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
 from /usr/include/boost/shared_ptr.hpp:17,
 from
/usr/include/boost/python/converter/shared_ptr_to_python.hpp:12,
 from /usr/include/boost/python/converter/arg_to_python.hpp:15,
 from /usr/include/boost/python/call.hpp:15,
 from /usr/include/boost/python/object_core.hpp:14,
 from /usr/include/boost/python/object.hpp:9,
 from /<>/boost_adaptbx/graph/graph_type.hpp:4,
 from /<>/boost_adaptbx/graph/metric_ext.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice
of declaring the Bind placeholders (_1, _2, ...) in the global
namespace is deprecated. Please use  + using
namespace boost::placeholders, or define
BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
  | ^~~~
/<>/boost_adaptbx/meta_ext.cpp: In function
‘boost::python::list {anonymous}::str_or_unicode_as_char_list(const
boost::python::api::object&)’:
/<>/boost_adaptbx/meta_ext.cpp:439:11: error:
‘PyUnicode_GET_DATA_SIZE’ was not declared in this scope
  439 |   n = PyUnicode_GET_DATA_SIZE(obj);
  |   ^~~
/<>/boost_adaptbx/meta_ext.cpp:440:11: error:
‘PyUnicode_AS_DATA’ was not declared in this scope; did you mean
‘PyUnicode_DATA’?
  440 |   c = PyUnicode_AS_DATA(obj);
  |   ^
  |   PyUnicode_DATA

Bug#1056493: python-pulp's autopkg tests fail with Python 3.12

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/coin-or/pulp/issues/709


-- 
http://fam-tille.de

Processed: Re: python-pulp's autopkg tests fail with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1056493 [src:python-pulp] python-pulp's autopkg tests fail with Python 3.12
Added tag(s) upstream.
> forwarded -1 https://github.com/coin-or/pulp/issues/709
Bug #1056493 [src:python-pulp] python-pulp's autopkg tests fail with Python 3.12
Set Bug forwarded-to-address to 'https://github.com/coin-or/pulp/issues/709'.

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

Processed: python-skbio ftbfs with Python 3.12 (and cython 3.0.5)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1056047 [src:python-skbio] python-skbio ftbfs with Python 3.12 (and cython 
3.0.5)
Severity set to 'important' from 'serious'

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

Bug#1056047: python-skbio ftbfs with Python 3.12 (and cython 3.0.5)

[Graham Inggs]

Control: severity -1 important

This was worked around in 0.5.8-4.1.  Downgrading severity for now.

Bug#1057951: marked as done (promod3: FTBFS: No such file or directory: 'model.pdb')

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 14:51:36 +
with message-id 
and subject line Bug#1057951: fixed in promod3 3.3.1+ds-2
has caused the Debian Bug report #1057951,
regarding promod3: FTBFS: No such file or directory: 'model.pdb'
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.)


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

Package: src:promod3
Version: 3.3.1+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON -DOST_ROOT=/usr 
-DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON 
-DOST_ROOT=/usr -DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib ..
-- The CXX compiler identification is GNU 13.2.0
-- The C compiler identification is GNU 13.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped

[... snipped ...]

make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f loop/pymod/CMakeFiles/loop_pymod.dir/build.make 
loop/pymod/CMakeFiles/loop_pymod.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/loop/pymod && /usr/bin/cmake -E copy_if_different 
/<>/loop/pymod/__init__.py 
/<>/obj-x86_64-linux-gnu/stage/lib64/python3.11/site-packages//promod3/loop/__init__.py
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./backbone.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./backbone.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  0%] Built target loop_pymod
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/scoring/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/scoring/src 
/<>/obj-x86_64-linux-gnu/scoring/src/CMakeFiles/promod3_scoring_headers.dir/DependInfo.cmake "--color="
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./bb_trace_param.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./bb_trace_param.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/build
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./data_bag.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./data_bag.hh
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_score_base.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_score_base.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_overall_scorer.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_overall_scorer.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_hash_table.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_hash_table.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./scoring_object_loader.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./scoring_object_loader.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_map.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_map.hh
cd 

Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

[JP Pozzi]

Hello, 

The script /etc/init.d/qemu-guest-agent was modified by me to look at the 
problem, 
it is not the original one. 
I use also a "home made" script to get clear informations through a dedicated 
logfile : 
#!/bin/bash 

METHOD='virtio-serial' 
ZPATH='/dev/virtio-ports/org.qemu.guest_agent.0' 
LOGFILE='/var/log/qemu-ga.log' 

OPTIONS=' --verbose --daemon ' 
/usr/sbin/qemu-ga --method=$METHOD --path=$ZPATH --logfile=$LOGFILE $OPTIONS 

Hope this helps, 

Regards 

Bug#997720: marked as done (wims: FTBFS: configure.ac: error: required file 'config.sub' not found)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 14:39:04 +
with message-id 
and subject line Bug#997720: fixed in wims 2:4.27a+dfsg1-1
has caused the Debian Bug report #997720,
regarding wims: FTBFS: configure.ac: error: required file 'config.sub' not found
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd wims/src; autoreconf && ./configure --without-units --without-chemeq 
> --without-wimsd CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security" 
> CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" DFLAGS="-frelease" FCFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong" FFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong" GCJFLAGS="-g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong" 
> LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" 
> configure.ac:5: warning: The macro `AC_CONFIG_HEADER' is obsolete.
> configure.ac:5: You should run autoupdate.
> ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
> configure.ac:5: the top level
> configure.ac:39: warning: AC_PROG_LEX without either yywrap or noyywrap is 
> obsolete
> ./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from...
> ./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from...
> configure.ac:39: the top level
> configure.ac:74: warning: AC_CHECK_FUNCS($fun): you should use literals
> ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from...
> configure.ac:74: the top level
> configure.ac:83: warning: AC_CHECK_FUNCS($fun): you should use literals
> ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from...
> configure.ac:83: the top level
> configure.ac:93: warning: AC_CHECK_FUNCS($fun): you should use literals
> ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from...
> configure.ac:93: the top level
> configure.ac:98: warning: AC_CHECK_FUNCS($fun): you should use literals
> ./lib/autoconf/functions.m4:117: AC_CHECK_FUNCS is expanded from...
> configure.ac:98: the top level
> configure.ac:109: warning: The macro `AC_HEADER_STDC' is obsolete.
> configure.ac:109: You should run autoupdate.
> ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
> configure.ac:109: the top level
> configure.ac:111: warning: The macro `AC_MEMORY_H' is obsolete.
> configure.ac:111: You should run autoupdate.
> ./lib/autoconf/headers.m4:853: AC_MEMORY_H is expanded from...
> configure.ac:111: the top level
> configure.ac:122: warning: The macro `AC_HEADER_TIME' is obsolete.
> configure.ac:122: You should run autoupdate.
> ./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from...
> configure.ac:122: the top level
> configure.ac:145: warning: The macro `AC_TYPE_SIGNAL' is obsolete.
> configure.ac:145: You should run autoupdate.
> ./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from...
> configure.ac:145: the top level
> configure.ac: error: required file 'config.sub' not found
> configure.ac: error: required file 'config.guess' not found
> configure.ac:   try running autoreconf --install
> make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/wims_4.22~dfsg1-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: wims
Source-Version: 2:4.27a+dfsg1-1
Done: Jean Charles Delépine 

We believe that the bug you reported is fixed in the latest version of

Bug#1057032: marked as done (wims: An updated package of wims closing all bugs exists.)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 14:39:04 +
with message-id 
and subject line Bug#1057032: fixed in wims 2:4.27a+dfsg1-1
has caused the Debian Bug report #1057032,
regarding wims: An updated package of wims closing all bugs exists.
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.)


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

Hello,

I use an updated package for wims 4.27a closing all actual bugs of version: 
2:4.22~dfsg1-2 :

wims (2:4.27a~dfsg1-1) UNRELEASED; urgency=medium

  * New upstream release
  * Non-maintainer upload.
  * refreshed debian patches
  * terser replace uglifyjs.terser #1001029
  * remove autoconf from debian rules #997720
  * add ctime.h to wims_mathml.cc
  * Force MathML=yes
  * add dependency to libwebservice-validator-html-w3c-perl
to make SSO CAS working
  * wims-modules: don't fail on postrm if /var/lib/wims is a mount point
  * wims-modules: add dependency to libjs-mootools, jsxgraph, yui-compressor and
asciidoc-common #988894
  * backport to bookworm

 -- Jean Charles Delépine   Wed, 22 Nov 2023 08:37:09 
+0100

Source package can be found here :
deb-src  "http://debian-upjv.u-picardie.fr/reprepro; bookworm wims

I'm not a debian developper (but using and patching Debian for 25 years) so 
please 
double check my work.

Sincerly,
Jean Charles Delépine
--- End Message ---
--- Begin Message ---
Source: wims
Source-Version: 2:4.27a+dfsg1-1
Done: Jean Charles Delépine 

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

Debian distribution maintenance software
pp.
Jean Charles Delépine  (supplier of updated wims 
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, 29 Nov 2023 18:10:09 +0100
Source: wims
Architecture: source
Version: 2:4.27a+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Jean Charles Delépine 
Closes: 988894 997720 1001029 1057032
Changes:
 wims (2:4.27a+dfsg1-1) unstable; urgency=medium
 .
   [ Jean Charles Delépine ]
   * New upstream release 4.27a+dfsg1 Closes: #1057032
   * Non-maintainer upload.
   * refreshed debian patches
   * terser replace uglifyjs.terser Closes: #1001029
   * remove autoconf from debian rules Closes: #997720
   * add ctime.h to wims_mathml.cc
   * Force MathML=yes
   * add dependency to libwebservice-validator-html-w3c-perl
 to make SSO CAS working
   * wims-modules: don't fail on postrm if /var/lib/wims is a mount point
   * wims-modules: add dependency to libjs-mootools, jsxgraph, yui-compressor 
and
 asciidoc-common Closes: #988894
   * wims-modules: add dependency to libjs-edit-area and remove it from
 third-parties
   * wims-modules: depend node-mathjax-full and make a symlink in scripts/js
   * wims-modules: various foundation.sh corrections
   * wims-modules: call foundation.sh from Makefile.for.debian
   * backport to bookworm
 .
   [ Georges Khaznadar ]
   * replaced the tilde "~" by a plus sign in the package name.
   * added lintian overrides for source files which triggered lintian errors
 but are human-readable.
   * modified the file tablesort.sh in the debian patches to delete a file which
 is sneaking in with a link to
 https://d2dq2ahtl5zl1z.cloudfront.net/analytics.js, and the
 subdirectory test/ which contains a file with too long lines.
   * modified debian/get-latest-source to remove more sourceless contents from
 the upstream source package
   * patched the Makefile.in files to introduce $(CPPFLAGS) into default
 build commands for C sources.
Checksums-Sha1:
 05048d3604057c93d3019ac04a618135c99f9942 2181 wims_4.27a+dfsg1-1.dsc
 60f453b4714d6695bfd2851c66a135573f747078 50675910 wims_4.27a+dfsg1.orig.tar.gz
 31f9d43faf1b97b8f2b175382da17f681a57756a 44640 wims_4.27a+dfsg1-1.debian.tar.xz
 

Processed: yt ftbfs with Python 3.11/3.12

[Debian Bug Tracking System]

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

> tags 1056043 + ftbfs
Bug #1056043 [src:yt] yt ftbfs with Python 3.12 (and cython 3.0.5)
Added tag(s) ftbfs.
> tags 1057864 + ftbfs
Bug #1057864 [src:yt] yt ftbfs with Python 3.11/3.12
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Python 3.12 tagging

[Debian Bug Tracking System]

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

> tags 1057860 + ftbfs
Bug #1057860 [src:breezy] breezy ftbfs with Python 3.12:
Added tag(s) ftbfs.
> tags 1055733 + ftbfs
Bug #1055733 [src:pytango] pytango ftbfs with Python 3.12 (test failures)
Added tag(s) ftbfs.
> tags 1057863 + ftbfs
Bug #1057863 [src:slepc4py] slepc4py ftbfs with Python 3.12
Added tag(s) ftbfs.
> merge 1055733 1057862
Bug #1055733 [src:pytango] pytango ftbfs with Python 3.12 (test failures)
Bug #1057862 [src:pytango] pytango ftbfs with Python 3.12
Added tag(s) ftbfs.
Merged 1055733 1057862
> thanks
Stopping processing here.

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

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 
'model.pdb'
Owner recorded as Andrius Merkys .

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

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Andrius Merkys]

Control: owner -1 !

Hi,

On 2023-12-11 14:04, Santiago Vila wrote:

# Also happens in bookworm
found 1057951 3.2.1+ds-6
thanks

El 11/12/23 a las 12:06, Andrius Merkys escribió:
I can reproduce this in clean chroot on barriere.d.o. Interestingly, 
FTBFS happens only when building on two threads, four thread build 
succeeds. I have a feeling that the test execution order is important 
somehow. Will give a look and/or forward upstream. New upstream 
release is out, need to check first if the issue persists there.


More to the point: This has never failed for me on single-CPU systems
(where I've also tried a lot of times).

I see in the build log that the tests are invoked in this way:

    dh_auto_test
     cd obj-x86_64-linux-gnu && make -j2 check ARGS\+=--verbose 
ARGS\+=-j2


so maybe forcing -j1 at such point would serve as a workaround.


Good catch, and indeed seems to fix the issue. I will fix and upload 
shortly.


Thanks,
Andrius

Bug#1056501: marked as done (python-qrcode's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 13:07:24 +
with message-id 
and subject line Bug#1056501: fixed in python-qrcode 7.4.2-4
has caused the Debian Bug report #1056501,
regarding python-qrcode's autopkg tests fail with Python 3.12
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.)


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

Package: src:python-qrcode
Version: 7.4.2-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-qrcode's autopkg tests fail with Python 3.12:

[...]
309s autopkgtest [18:50:26]: test qrcode: [---
309s = test session starts 
==

309s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
309s rootdir: /tmp/autopkgtest.A3lFBV/autopkgtest_tmp
309s collected 79 items
309s
309s tests/test_example.py . 
 [  1%]
312s tests/test_qrcode.py 
... [ 65%]
312s ... 
 [ 69%]
312s tests/test_qrcode_svg.py .. 
 [ 77%]
312s tests/test_release.py F... 
 [ 82%]
312s tests/test_script.py . 
 [ 98%]
312s tests/test_util.py . 
 [100%]

312s
312s === FAILURES 
===
312s  UpdateManpageTests.test_change 


312s
312s self = 
312s mock_file = 
312s
312s @mock.patch(OPEN, new_callable=mock.mock_open, read_data=DATA)
312s def test_change(self, mock_file):
312s update_manpage({"name": "qrcode", "new_version": "3.11"})
312s expected = re.split(r"([^\n]*(?:\n|$))", DATA)[1::2]
312s expected[1] = (
312s expected[1]
312s .replace("version", "3.11")
312s .replace("date", datetime.datetime.now().strftime("%-d 
%b %Y"))

312s )
312s >   mock_file().write.has_calls([mock.call(line) for line in 
expected])

312s
312s tests/test_release.py:40:
312s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _

312s
312s self = , name = 
'has_calls'

312s
312s def __getattr__(self, name):
312s if name in {'_mock_methods', '_mock_unsafe'}:
312s raise AttributeError(name)
312s elif self._mock_methods is not None:
312s if name not in self._mock_methods or name in _all_magics:
312s raise AttributeError("Mock object has no attribute 
%r" % name)

312s elif _is_magic(name):
312s raise AttributeError(name)
312s if not self._mock_unsafe and (not self._mock_methods or 
name not in self._mock_methods):
312s if name.startswith(('assert', 'assret', 'asert', 
'aseert', 'assrt')) or name in _ATTRIB_DENY_LIST:

312s >   raise AttributeError(
312s f"{name!r} is not a valid assertion. Use a spec "
312s f"for the mock if {name!r} is meant to be an 
attribute.")
312s E   AttributeError: 'has_calls' is not a valid 
assertion. Use a spec for the mock if 'has_calls' is meant to be an 
attribute.

312s
312s /usr/lib/python3.12/unittest/mock.py:663: AttributeError
312s === warnings summary 
===

312s tests/test_script.py::ScriptTest::test_bad_factory
312s   /usr/lib/python3/dist-packages/qrcode/console_scripts.py:43: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html

312s from pkg_resources import get_distribution
312s
312s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
312s === short test summary info 

312s FAILED tests/test_release.py::UpdateManpageTests::test_change - 
AttributeErro...
312s === 1 failed, 78 passed, 1 warning in 3.34s 

--- End Message ---
--- Begin Message ---
Source: python-qrcode
Source-Version: 7.4.2-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier 

Processed: Re: [Debichem-devel] Bug#1057556: elpa: FTBFS: not enough slots available

[Debian Bug Tracking System]

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

> severity 1057556 normal
Bug #1057556 [src:elpa] elpa: FTBFS: not enough slots available
Severity set to 'normal' from 'serious'
> retitle 1057556 elpa: FTBFS unless machine has more than one vcore
Bug #1057556 [src:elpa] elpa: FTBFS: not enough slots available
Changed Bug title to 'elpa: FTBFS unless machine has more than one vcore' from 
'elpa: FTBFS: not enough slots available'.
> thanks
Stopping processing here.

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

Bug#1057556: [Debichem-devel] Bug#1057556: elpa: FTBFS: not enough slots available

[Michael Banck]

severity 1057556 normal
retitle 1057556 elpa: FTBFS unless machine has more than one vcore
thanks

Hi Santiago,

On Tue, Dec 05, 2023 at 11:05:01PM +0100, Santiago Vila wrote:
> Package: src:elpa
> Version: 2022.11.001-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> During a rebuild of all packages in unstable, your package failed to build:
> 
> 
> [...]
>  debian/rules build
> dh build --max-parallel=1 --builddir=build
>dh_update_autotools_config -O--max-parallel=1 -O--builddir=build
>dh_autoreconf -O--max-parallel=1 -O--builddir=build
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:298: warning: The macro `AC_PROG_CC_C99' is obsolete.
> configure.ac:298: You should run autoupdate.
> 
> [... snipped ...]
> 
> --
> FAIL validate_complex_double_invert_triangular_default.sh (exit status: 1)
> 
> FAIL: validate_real_double_explicit_invert_triangular_default.sh
> 
> 
> --
> There are not enough slots available in the system to satisfy the 2
> slots that were requested by the application:
> 
>   ./validate_real_double_explicit_invert_triangular

[...]


> About the archive rebuild: The build was made using virtual machines
> from AWS, with enough memory, enough disk, and either one or two
> CPUs, using a reduced chroot with only build-essential packages.

So you are building elpa on a machine/vm with one cpu/vcore apparently?

I guess it is useful information that elpa requires at least two cores
to executes its MPI-based testsuite, but I don't think that this should
be a general requirement for an RC bug, so downgrading to normal for
now. If you indeed have more than 1 cpu core/vcore available, then I
agree that this is RC.


Michael

Bug#1057967: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

[Diederik de Haas]

On Monday, 11 December 2023 12:29:01 CET Salvatore Bonaccorso wrote:
> I cannot test for the regression explicitly myself, but 6.1.67 was
> released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
> non-range use""). Would you be in the position of do a test build with
> that commit (or with 6.1.67 upstream) to verify your issue goes away?

On Monday, 11 December 2023 12:37:44 CET Salvatore Bonaccorso wrote:
> I'm right now curious to find out if we see the same as
> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> issue.

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
describes an easy way to test it and the patch you should use is attached.From db46c77f3d51d24402731ea181b2a591e7dd1ac3 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman 
Date: Mon, 11 Dec 2023 10:16:15 +0100
Subject: [PATCH] Revert "wifi: cfg80211: fix CQM for non-range use"
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This reverts commit 307a6525c82a5a1bc5364711ece92c2d2487e1ad which is
commit 7e7efdda6adb385fbdfd6f819d76bc68c923c394 upstream.

It needed to have commit 076fc8775daf ("wifi: cfg80211: remove wdev
mutex") applied to properly work, otherwise regressions happen.

Link: https://lore.kernel.org/r/e374bb16-5b13-44cc-b11a-2f4eefb1e...@manjaro.org
Link: https://lore.kernel.org/r/87sf4belmm@turtle.gmx.de
Link: https://lore.kernel.org/r/20231210213930.61378-1-...@leolam.fr
Reported-by: L??o Lam 
Reported-by: Sven Joachim 
Reported-by: Philip M??ller 
Cc: Johannes Berg 
Signed-off-by: Greg Kroah-Hartman 
---
 net/wireless/core.h|  1 -
 net/wireless/nl80211.c | 50 --
 2 files changed, 19 insertions(+), 32 deletions(-)

diff --git a/net/wireless/core.h b/net/wireless/core.h
index ee980965a7cf..e1accacc6f23 100644
--- a/net/wireless/core.h
+++ b/net/wireless/core.h
@@ -297,7 +297,6 @@ struct cfg80211_cqm_config {
 	u32 rssi_hyst;
 	s32 last_rssi_event_value;
 	enum nl80211_cqm_rssi_threshold_event last_rssi_event_type;
-	bool use_range_api;
 	int n_rssi_thresholds;
 	s32 rssi_thresholds[];
 };
diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 42c858219b34..b19b5acfaf3a 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@ -12574,6 +12574,10 @@ static int cfg80211_cqm_rssi_update(struct cfg80211_registered_device *rdev,
 	int i, n, low_index;
 	int err;
 
+	/* RSSI reporting disabled? */
+	if (!cqm_config)
+		return rdev_set_cqm_rssi_range_config(rdev, dev, 0, 0);
+
 	/*
 	 * Obtain current RSSI value if possible, if not and no RSSI threshold
 	 * event has been received yet, we should receive an event after a
@@ -12648,6 +12652,18 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 	wdev->iftype != NL80211_IFTYPE_P2P_CLIENT)
 		return -EOPNOTSUPP;
 
+	if (n_thresholds <= 1 && rdev->ops->set_cqm_rssi_config) {
+		if (n_thresholds == 0 || thresholds[0] == 0) /* Disabling */
+			return rdev_set_cqm_rssi_config(rdev, dev, 0, 0);
+
+		return rdev_set_cqm_rssi_config(rdev, dev,
+		thresholds[0], hysteresis);
+	}
+
+	if (!wiphy_ext_feature_isset(>wiphy,
+ NL80211_EXT_FEATURE_CQM_RSSI_LIST))
+		return -EOPNOTSUPP;
+
 	if (n_thresholds == 1 && thresholds[0] == 0) /* Disabling */
 		n_thresholds = 0;
 
@@ -12655,20 +12671,6 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 	old = rcu_dereference_protected(wdev->cqm_config,
 	lockdep_is_held(>mtx));
 
-	/* if already disabled just succeed */
-	if (!n_thresholds && !old)
-		return 0;
-
-	if (n_thresholds > 1) {
-		if (!wiphy_ext_feature_isset(>wiphy,
-	 NL80211_EXT_FEATURE_CQM_RSSI_LIST) ||
-		!rdev->ops->set_cqm_rssi_range_config)
-			return -EOPNOTSUPP;
-	} else {
-		if (!rdev->ops->set_cqm_rssi_config)
-			return -EOPNOTSUPP;
-	}
-
 	if (n_thresholds) {
 		cqm_config = kzalloc(struct_size(cqm_config, rssi_thresholds,
 		 n_thresholds),
@@ -12683,26 +12685,13 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 		memcpy(cqm_config->rssi_thresholds, thresholds,
 		   flex_array_size(cqm_config, rssi_thresholds,
    n_thresholds));
-		cqm_config->use_range_api = n_thresholds > 1 ||
-	!rdev->ops->set_cqm_rssi_config;
 
 		rcu_assign_pointer(wdev->cqm_config, cqm_config);
-
-		if (cqm_config->use_range_api)
-			err = cfg80211_cqm_rssi_update(rdev, dev, cqm_config);
-		else
-			err = rdev_set_cqm_rssi_config(rdev, dev,
-		   thresholds[0],
-		   hysteresis);
 	} else {
 		RCU_INIT_POINTER(wdev->cqm_config, NULL);
-		/* if enabled as range also disable via range */
-		if (old->use_range_api)
-			err = rdev_set_cqm_rssi_range_config(rdev, dev, 0, 0);
-		else
-			err = rdev_set_cqm_rssi_config(rdev, dev, 0, 0);
 	}
 
+	err = cfg80211_cqm_rssi_update(rdev, dev, cqm_config);
 	if (err) {
 		rcu_assign_pointer(wdev->cqm_config, old);
 		

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Grand T]

Hello
Up to now 6.1.67 is not available for my configuration

apt list | grep linux-image-6.1*

linux-image-6.1.0-11-686-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-686-pae-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-686-pae-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-686-pae/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-12-686-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-686-pae-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-686-pae-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-686-pae/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-13-686-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-686/stable 6.1.55-1 i386
linux-image-6.1.0-13-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-amd64/stable,now 6.1.55-1 amd64  [installé]
linux-image-6.1.0-13-cloud-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-cloud-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-cloud-amd64/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-686-pae-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-686-pae-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-686-pae/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-amd64/stable 6.1.55-1 amd64
linux-image-6.1.0-14-amd64/now 6.1.64-1 amd64  [installé, local]
linux-image-6.1.0-15-686-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-686/stable 6.1.66-1 i386
linux-image-6.1.0-15-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-amd64/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-686-pae-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-686-pae-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-686-pae/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-amd64/stable 6.1.66-1 amd64
linux-image-6.5.0-5-686-dbg/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae-dbg/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae-unsigned/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-unsigned/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-amd64-dbg/unstable,testing 6.5.13-1 amd64
linux-image-6.5.0-5-amd64-unsigned/unstable,testing 6.5.13-1 amd64

Bug#1056501: marked as pending in python-qrcode

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1056501 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/14473704bc0c8514771a64fe5c2cff6cb235f319


Patch: correct call on mock_file().write (Closes: #1056501)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056501

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056501 [src:python-qrcode] python-qrcode's autopkg tests fail with Python 
3.12
Added tag(s) pending.

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

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Kevin Price]

Thank you Salvatore!

Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> It still would be helpfull if you can get to the logs of the previous
> boot. After booting back in the working kernel, do you have anything
> sensible logged in the previous boot log? If so can you share that
> please?

Sure. Here's my boot.log.

The first one at "Mon Dec 11 00:54:03 CET 2023" is the faulty 6.1.0-15.

The 2nd one at "Mon Dec 11 01:13:38 CET 2023" is the working 6.1.0-13.

Need any more logfiles or testing? I intend to test
debian-live-12.4.0-amd64-gnome.iso on my computer, IOT rule out any
local config peculiarities, FWIW.

> I'm right now curious to find out if we see the same as
> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> issue.

Please let me know what kernel version you want me to test, if they're
provides as debian binaries. I'd be glad to help, probably not only for
my own sake. Bear with me I'm unwilling to build kernel packages myself,
due to lack of computing resources. HTH
-- 
Kevin Price Mon Dec 11 00:54:03 CET 2023 
/: clean, 635496/28696576 files, 99342237/114756608 blocks
 Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System...
[  OK  ] Finished systemd-cryptsetup@cryptswap1.service - Cryptography Setup for cryptswap1.
[  OK  ] Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
[  OK  ] Reached target blockdev@dev-mapper-cryptswap1.target - Block Device Preparation for /dev/mapper/cryptswap1.
[  OK  ] Reached target cryptsetup.target - Local Encrypted Volumes.
[  OK  ] Finished systemd-binfmt.service - Set Up Additional Binary Formats.
[  OK  ] Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
 Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
 Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
 Starting modprobe@loop.service - Load Kernel Module loop...
 Starting systemd-resolved.service - Network Name Resolution...
 Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
[  OK  ] Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[  OK  ] Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[  OK  ] Finished modprobe@loop.service - Load Kernel Module loop.
[  OK  ] Found device dev-mapper-cryptswap1.device - /dev/mapper/cryptswap1.
 Activating swap dev-mapper-cryptswap1.swap - /dev/mapper/cryptswap1...
[  OK  ] Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
[  OK  ] Activated swap dev-mapper-cryptswap1.swap - /dev/mapper/cryptswap1.
[  OK  ] Reached target swap.target - Swaps.
[  OK  ] Finished apparmor.service - Load AppArmor profiles.
[  OK  ] Started systemd-resolved.service - Network Name Resolution.
[  OK  ] Reached target nss-lookup.target - Host and Network Name Lookups.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Started anacron.timer - Trigger anacron every hour.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started ntpsec-rotate-stats.timer - Rotate ntpd stats daily.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
 Starting 

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Diederik de Haas]

On Monday, 11 December 2023 13:01:58 CET Grand T wrote:
> Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few
> days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range
> use." That patch ended up regressing Linux wireless support with deadlocks
> in the IWD wireless daemon hangs on shutdown, and related issues with
> user-space network managers

Kernel 6.6.6 fixes an issue introduced in 6.6.5, but both have NOT been 
uploaded to Debian. If they were, that would've been to Experimental or 
Unstable, where breakage from time to time should be expected.

Kernel 6.1.67 *is* relevant and is also a revert of that commit.

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

Bug#1058032: python-grpc-tools: FTBFS with Python 3.12

[Graham Inggs]

Source: python-grpc-tools
Version: 1.14.1-6
Severity: serious
Tags: ftbfs sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-grpc-tools FTBFS [1] with Python 3.12 as a supported version.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=python-grpc-tools


grpc_tools/_protoc_compiler.cpp: In function ‘long int
__Pyx_PyInt_As_long(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:2529:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
 2529 | const digit* digits = ((PyLongObject*)x)->ob_digit;
  |   ^~~~
grpc_tools/_protoc_compiler.cpp:2584:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
 2584 | const digit* digits = ((PyLongObject*)x)->ob_digit;
  |   ^~~~
grpc_tools/_protoc_compiler.cpp: In function ‘int
__Pyx_PyInt_As_int(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:2725:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
 2725 | const digit* digits = ((PyLongObject*)x)->ob_digit;
  |   ^~~~
grpc_tools/_protoc_compiler.cpp:2780:55: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
 2780 | const digit* digits = ((PyLongObject*)x)->ob_digit;
  |   ^~~~
grpc_tools/_protoc_compiler.cpp: In function ‘Py_ssize_t
__Pyx_PyIndex_AsSsize_t(PyObject*)’:
grpc_tools/_protoc_compiler.cpp:3231:47: error: ‘PyLongObject’ {aka
‘struct _longobject’} has no member named ‘ob_digit’
 3231 | const digit* digits = ((PyLongObject*)b)->ob_digit;
  |   ^~~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit
code=1: /usr/bin/python3.12 setup.py build

Bug#1057967:

[Jason Zarin]

I think it highly likely that it's that wifi reversion noted up thread.

On my system, wifi hangs (broadcom-sta-dkms) and causes network manager to
hit 100% according to top.

Problem not present in kernels 6.1.0-13&14 and back port 6.5.

Bug#1058031: pygame: FTBFS with Python 3.12

[Graham Inggs]

Source: pygame
Version: 2.5.2-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

pygame FTBFS [1] with Python 3.12 as a supported version.  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=pygame


loading pygame.tests.transform_test
Traceback (most recent call last):
  File "", line 198, in _run_module_as_main
  File "", line 88, in _run_code
  File 
"/<>/.pybuild/cpython3_3.12_pygame/build/pygame/tests/__main__.py",
line 143, in 
run_and_exit(*args, **kwds)
  File 
"/<>/.pybuild/cpython3_3.12_pygame/build/pygame/tests/test_utils/run_tests.py",
line 346, in run_and_exit
total, fails = run(*args, **kwargs)
   
  File 
"/<>/.pybuild/cpython3_3.12_pygame/build/pygame/tests/test_utils/run_tests.py",
line 303, in run
raise AssertionError(
AssertionError: Something went wrong in the Test Machinery:
total: 1807 != untrusty_total: 1840

Bug#1056132: marked as done (skimage: FTBFS in testing and unstable)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 12:20:11 +
with message-id 
and subject line Bug#1056132: fixed in skimage 0.22.0-3
has caused the Debian Bug report #1056132,
regarding skimage: FTBFS in testing and unstable
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.)


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

Hi Maintainer

As can be seen on reproducible builds [1], skimage currently FTBFS in
testing and unstable.  I've copied what I hope is the relevant part of
the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/skimage.html


dumping search index in English (code: en)... done
dumping object inventory... done

Sphinx-Gallery successfully executed 118 out of 118 files subselected by:

gallery_conf["filename_pattern"] = '/plot'
gallery_conf["ignore_pattern"]   = '__init__\\.py'

after excluding 0 files that had previously been run (based on MD5).

embedding documentation hyperlinks...
/usr/lib/python3/dist-packages/sphinx_gallery/docs_resolv.py:145:
RemovedInSphinx80Warning:

Sphinx 8 will drop support for representing paths as strings. Use
"pathlib.Path" or "os.fspath" instead.


Extension error:
Documentation options could not be found in index.
make[2]: *** [Makefile:50: html] Error 2
make[2]: Leaving directory '/build/reproducible-path/skimage-0.22.0/doc'
make[1]: *** [debian/rules:59: override_dh_installdocs-indep] Error 2
make[1]: Leaving directory '/build/reproducible-path/skimage-0.22.0'
make: *** [debian/rules:31: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.22.0-3
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated skimage 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, 11 Dec 2023 12:43:35 +0100
Source: skimage
Architecture: source
Version: 0.22.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 1056132 1056889 1058024
Changes:
 skimage (0.22.0-3) unstable; urgency=medium
 .
   [ Ole Streicher ]
   * Remove sphinx_gallery dependency (Closes: #1056132)
   * Remove intersphinx mapping (Closes: #1058024)
 .
   [ Bas Couwenberg ]
   * Switch to cython3-legacy (Closes: #1056889)
Checksums-Sha1:
 2983e47528ff30a5e309c2a9840c0706f7b03dce 2959 skimage_0.22.0-3.dsc
 7bd542dc9a54d7e655463571f43045a24c53b0b3 28508 skimage_0.22.0-3.debian.tar.xz
Checksums-Sha256:
 0a2a7f27114817516f32ca0981dbbcb91e129738269189275e8e07e6c9cde8b0 2959 
skimage_0.22.0-3.dsc
 4d0e21e2990f3d78b66c371400f7e12fe072f445c748b255365175d8f5439c5a 28508 
skimage_0.22.0-3.debian.tar.xz
Files:
 0267c958ee1e8642c09c53ff56deb817 2959 python optional skimage_0.22.0-3.dsc
 26cdef7306db3740200be7621802f8ff 28508 python optional 
skimage_0.22.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmV2+JUACgkQcRWv0HcQ
3PdKnBAAjsB1q0Clz3CrsD7I9JbSvY2Hl0KEHEsDDWHkm2yj7bb8VdQBPENErct8
Vq2Iv9+YWygyuLt8BO2KG+CWOByKJaO2NxheS8uzRjsGmlVOfutdmAtBlt8XnaSa
D1gKQu55VxH+MvzZTrcIXs2WTJsFWDY1uOUKYZScTwBt0lsSFMlKU75ENVXyJZcU
2VyCk4aBr8JbQzbxCXIbTqy4EKg9wJCYPVc1SOZOT94a698Bnor30vepRLuzkRU5
sRfkNiztlVVwJtrnBz94BH7jEAMq8Jksd3kIni+czrTjXGv5Uq2Tk9z4dOoderTS
+oRtB0HQ8+fwoVyzKUj8g+aqU+6k1zvZ+5QDljBc+u3zWV0jupzTVHRUIAw2t3FZ
547/j/xQGf+eiUFu8IBVfkxzqkb6kGA9nPS1s8ra74uOiGVrstUMQthiyTO8kDNy
3UeKJXUgUW2G8Qgr/J1JmK+tD7rh8uhRWxJJApD5bHCPF8ugXLbpGCJxU2Ibp6By
kEW33pPnVGZUCad7CzHV+HlG/HHqt6TexwC8avAtCL6a7Elk6wy3/CnZaEddIwyI
UspY3d3oBZ1/Ku9dBavS1VfzKbOvY6ZNki2W0XkiL6niJXnWvoJF5a96qAjEImdI
9KhQXwpj+i2WaacUOe9Lymb6hRGO1saPCcaJ0tUx0JOy/Dq//6E=
=5LZP
-END PGP SIGNATURE End Message ---

Bug#1058024: marked as done (skimage tries to access the net during the build)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 12:20:11 +
with message-id 
and subject line Bug#1058024: fixed in skimage 0.22.0-3
has caused the Debian Bug report #1058024,
regarding skimage tries to access the net during the build
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.)


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

Package: src:skimage
Version: 0.22.0-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

skimage tries to access the net during the build, only seen when the 
binary-indep packages are also built.


[...]
   debian/rules override_dh_installdocs-indep
make[1]: Entering directory '/<>'
# hotfix SPHINXBUILD -- remove in next release
\
	PYTHONPATH=/<>/.pybuild/cpython3_3.11/build:$(python3 -c 
'import sys;print(":".join(sys.path))') \

PYTHON=python3.11 \
SPHINXBUILD="python3.11 -m sphinx" \
SPHINXOPTS="-D mathjax_path=MathJax.js" \
/usr/bin/make -C doc html
make[2]: Entering directory '/<>/doc'
python3.11 tools/build_modref_templates.py
outdir:
19 files written
Build API docs...done.
python3.11 -m sphinx -b html -d build/doctrees  -D 
mathjax_path=MathJax.js source build/html

Running Sphinx v7.2.6
/usr/lib/python3/dist-packages/sphinx_gallery/sphinx_compatibility.py:71: 
RemovedInSphinx80Warning:


The alias 'sphinx.util.status_iterator' is deprecated, use 
'sphinx.util.display.status_iterator' instead. Check CHANGES for Sphinx 
API modifications.


making output directory... done
[autosummary] generating autosummary for: about/code_of_conduct.md, 
about/index.rst, about/report_handling_manual.rst, about/values.md, 
api/api.rst, api/skimage.color.rst, api/skimage.data.rst, 
api/skimage.draw.rst, api/skimage.exposure.rst, api/skimage.feature.rst, 
..., user_guide/index.rst, user_guide/install.rst, 
user_guide/numpy_images.rst, user_guide/plugins.rst, 
user_guide/transforming_image_data.rst, 
user_guide/tutorial_parallelization.rst, 
user_guide/tutorial_segmentation.rst, user_guide/tutorials.rst, 
user_guide/video.rst, user_guide/visualization.rst
loading intersphinx inventory from 
/usr/share/doc/python3.9/html/objects.inv...

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory '/usr/share/doc/python3.9/html/objects.inv' not 
fetchable due to : [Errno 2] No such file or 
directory: '/usr/share/doc/python3.9/html/objects.inv'

loading intersphinx inventory from ./_intersphinx/numpy-objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory './_intersphinx/numpy-objects.inv' not fetchable 
due to : [Errno 2] No such file or directory: 
'/<>/doc/source/./_intersphinx/numpy-objects.inv'

loading intersphinx inventory from ./_intersphinx/scipy-objects.inv...
loading intersphinx inventory from ./_intersphinx/sklearn-objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory './_intersphinx/scipy-objects.inv' not fetchable 
due to : [Errno 2] No such file or directory: 
'/<>/doc/source/./_intersphinx/scipy-objects.inv'

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory './_intersphinx/sklearn-objects.inv' not fetchable 
due to : [Errno 2] No such file or directory: 
'/<>/doc/source/./_intersphinx/sklearn-objects.inv'

loading intersphinx inventory from https://matplotlib.org/objects.inv...
loading intersphinx inventory from ./_intersphinx/matplotlib-objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://matplotlib.org/objects.inv' not fetchable 
due to : 
HTTPSConnectionPool(host='matplotlib.org', port=443): Max retries 
exceeded with url: /objects.inv (Caused by 
NewConnectionError('0x7f41b7cc5e90>: Failed to establish a new connection: [Errno -2] Name 
or service not known'))
intersphinx inventory './_intersphinx/matplotlib-objects.inv' not 
fetchable due to : [Errno 2] No such file or 
directory: 
'/<>/doc/source/./_intersphinx/matplotlib-objects.inv'

generating gallery...
Using Sphinx-Gallery to convert rst text blocks to markdown for .ipynb 
files.

generating gallery for auto_examples...
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.22.0-3
Done: Ole Streicher 

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

A summary of the changes between this version 

Bug#1058030: pyferret: b-d on python3-all-dev, but not built for all supported Python3 versions

[Graham Inggs]

Source: pyferret
Version: 7.6.5-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.12 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.12-add.html

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Stephan Verbücheln]

Hello everybody

Unfortunately, I can confirm the same problems for 2014 Macbook Pro
(Intel CPU and graphics).

At first I thought the network problem was due to the proprietary
Broadcom WLAN driver because network connectivity was the most obvious
problem. However, the problems persisted after removing all proprietary
(broadcom-sta) and custom (facetimehd) kernel modules.

Regards
Stephan


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

Bug#1056516: marked as done (qstylizer's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 12:04:31 +
with message-id 
and subject line Bug#1056516: fixed in qstylizer 0.2.2-2
has caused the Debian Bug report #1056516,
regarding qstylizer's autopkg tests fail with Python 3.12
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.)


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

Package: src:qstylizer
Version: 0.2.2-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

qstylizer's autopkg tests fail with Python 3.12:

[...]
177s autopkgtest [19:03:16]: test pytest: [---
177s Testing with python3.12:
178s = test session starts 
==

178s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
178s rootdir: /tmp/autopkgtest.JQ9ibf/autopkgtest_tmp
178s plugins: mock-3.11.1
178s collected 70 items
178s
178s test/integration/test_integration.py .. 
 [ 37%]
178s test/unit/test_style.py 
.F.. [100%]

178s
178s === FAILURES 
===
178s _ test_create_child_rule_list 
__

178s
178s mocker = 
178s style_class = , css = 
178s
178s def test_create_child_rule_list(mocker, style_class, css):
178s import qstylizer.style
178s style_list = "StyleListInstance"
178s name = "test"
178s mocker.patch.object(
178s qstylizer.style, "StyleRuleList", return_value=style_list
178s )
178s mocked_set_child_rule = mocker.patch.object(style_class, 
"set_child_rule")

178s assert css.create_child_rule_list(name) == style_list
178s >   mocked_set_child_rule.called_once_with(name, style_list)
178s
178s test/unit/test_style.py:187:
178s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _

178s
178s self = 
178s name = 'called_once_with'
178s
178s def __getattr__(self, name):
178s if name in {'_mock_methods', '_mock_unsafe'}:
178s raise AttributeError(name)
178s elif self._mock_methods is not None:
178s if name not in self._mock_methods or name in _all_magics:
178s raise AttributeError("Mock object has no attribute 
%r" % name)

178s elif _is_magic(name):
178s raise AttributeError(name)
178s if not self._mock_unsafe and (not self._mock_methods or 
name not in self._mock_methods):
178s if name.startswith(('assert', 'assret', 'asert', 
'aseert', 'assrt')) or name in _ATTRIB_DENY_LIST:

178s >   raise AttributeError(
178s f"{name!r} is not a valid assertion. Use a spec "
178s f"for the mock if {name!r} is meant to be an 
attribute.")
178s E   AttributeError: 'called_once_with' is not a valid 
assertion. Use a spec for the mock if 'called_once_with' is meant to be 
an attribute.. Did you mean: 'assert_called_once_with'?

178s
178s /usr/lib/python3.12/unittest/mock.py:663: AttributeError
178s === short test summary info 

178s FAILED test/unit/test_style.py::test_create_child_rule_list - 
AttributeError:...
178s = 1 failed, 69 passed in 0.29s 
=
--- End Message ---
--- Begin Message ---
Source: qstylizer
Source-Version: 0.2.2-2
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated qstylizer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Dec 2023 11:31:43 +
Source: qstylizer
Architecture: source
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1056516
Changes:
 qstylizer (0.2.2-2) unstable; 

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Debian Bug Tracking System]

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

> # Also happens in bookworm
> found 1057951 3.2.1+ds-6
Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 
'model.pdb'
Marked as found in versions promod3/3.2.1+ds-6.
> thanks
Stopping processing here.

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

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Santiago Vila]

# Also happens in bookworm
found 1057951 3.2.1+ds-6
thanks

El 11/12/23 a las 12:06, Andrius Merkys escribió:

I can reproduce this in clean chroot on barriere.d.o. Interestingly, FTBFS 
happens only when building on two threads, four thread build succeeds. I have a 
feeling that the test execution order is important somehow. Will give a look 
and/or forward upstream. New upstream release is out, need to check first if 
the issue persists there.


More to the point: This has never failed for me on single-CPU systems
(where I've also tried a lot of times).

I see in the build log that the tests are invoked in this way:

   dh_auto_test
cd obj-x86_64-linux-gnu && make -j2 check ARGS\+=--verbose ARGS\+=-j2

so maybe forcing -j1 at such point would serve as a workaround.

Thanks.

Processed: your mail

[Debian Bug Tracking System]

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

> affects 1057967 src:linux
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Added indication that 1057967 affects src:linux
> notfound 1057967 linux/6.1.64-1
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Ignoring request to alter found versions of bug #1057967 to the same values 
previously set
> found 1057967 linux/6.1.66-1
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Ignoring request to alter found versions of bug #1057967 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Grand T]

Hello
For my case:
Is that a surprise if the problem is that one?

wifi: cfg80211: fix CQM for non-range use



https://www.phoronix.com/news/Linux-6.6.6-Released
 Linux 6.6.6 is out with just a sole change for dealing with another headache: 
WiFi regressions.

Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few 
days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range use." 
That patch ended up regressing Linux wireless support with deadlocks in the IWD 
wireless daemon hangs on shutdown, and related issues with user-space network 
managers

Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

[Y]

Package: qemu-guest-agent
Version: 1:8.1.2+ds-1~bpo12+1
Severity: serious
Justification: 6

Dear Maintainer,

The problem arose after upgrading from bullseye to bookworm.
All was OK on bullseye, but on bookworm qemu-ga refuse to start with
following messages :

1702295113.963828: debug: disabling command: guest-get-devices
1702295113.963868: critical: error opening channel 
'/dev/virtio-ports/org.qemu.guest_agent.0': No such file or directory
1702295113.963873: critical: failed to create guest agent channel
1702295113.963875: critical: failed to initialize guest agent channel

The systemd command looks like :
[Unit]
Description=QEMU Guest Agent
BindsTo=dev-virtio\x2dports-org.qemu.guest_agent.0.device
After=dev-virtio\x2dports-org.qemu.guest_agent.0.device

[Service]
ExecStart=-/usr/sbin/qemu-ga
Restart=always
RestartSec=0

[Install]


Regards

JP P


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

Kernel: Linux 6.1.0-0.deb11.13-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qemu-guest-agent depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9+deb12u3
ii  libglib2.0-0 2.74.6-2
ii  libnuma1 2.0.16-1
ii  libudev1 252.19-1~deb12u1
ii  liburing22.3-3

qemu-guest-agent recommends no packages.

qemu-guest-agent suggests no packages.

-- Configuration Files:
/etc/init.d/qemu-guest-agent changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="QEMU Guest Agent"
NAME=qemu-ga
DAEMON=/usr/sbin/$NAME
PIDFILE=/var/run/$NAME.pid
set -x
DAEMON_ARGS=""
TRANSPORT=virtio-serial:/dev/virtio-ports/org.qemu.guest_agent.0
[ -x "$DAEMON" ] || exit 0
. /lib/init/vars.sh
do_check_transport() {
method=${TRANSPORT%%:*}; path=${TRANSPORT#*:}
case "$method" in
virtio-serial | isa-serial)
if [ ! -e "$path" ]; then
echo log_warning_msg "$NAME: transport endpoint not found, 
not starting"
return 1
fi
;;
*) echo 'Not virtio-serial or isa-serial'
   ;;
esac
}
do_start()
{
# Return
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started
echo start-stop-daemon -Sq -p $PIDFILE -x $DAEMON --test > /dev/null \
|| return 1
echo start-stop-daemon -Sq -p $PIDFILE -x $DAEMON -- --daemonize \
$DAEMON_ARGS -m "$method" -p "$path" \
|| return 2
}
do_stop()
{
# Return
#   0 if daemon has been stopped
#   1 if daemon was already stopped
#   2 if daemon could not be stopped
#   other if a failure occurred
echo start-stop-daemon -Kq --retry=TERM/30/KILL/5 -p $PIDFILE --name 
$NAME
}
case "$1" in
  start)
do_check_transport || exit 0
echo 'Apres check-transport'
exit 10
[ "$VERBOSE" != no ] && echo log_daemon_msg "Starting $DESC" $NAME
echo do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && echo log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && echo log_end_msg 1 ;;
esac
;;
  stop)
[ "$VERBOSE" != no ] && echo log_daemon_msg "Stopping $DESC" $NAME
echo do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && echo log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && echo log_end_msg 1 ;;
esac
;;
  status)
status_of_proc "$DAEMON" $NAME && exit 0 || exit $?
;;
  restart|force-reload) # we do not support reload
do_check_transport || exit 0
echo log_daemon_msg "Restarting $DESC" $NAME
echo do_stop
case "$?" in
  0|1)
echo do_start
case "$?" in
0) echo log_end_msg 0 ;;
1) echo log_end_msg 1 ;; # Old process is still running
*) echo log_end_msg 1 ;; # Failed to start
esac
;;
  *)
# Failed to stop
echo log_end_msg 1
;;
esac
;;
  *)
echo "Usage: /etc/init.d/qemu-guest-agent 
{start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac


-- no debconf information

Bug#1056425: marked as done (microsoft-authentication-extensions-for-python's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 11:49:01 +
with message-id 
and subject line Bug#1056425: fixed in 
microsoft-authentication-extensions-for-python 1.1.0-1
has caused the Debian Bug report #1056425,
regarding microsoft-authentication-extensions-for-python's autopkg tests fail 
with Python 3.12
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.)


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

Package: src:microsoft-authentication-extensions-for-python
Version: 1.0.0-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

microsoft-authentication-extensions-for-python's autopkg tests fail with 
Python 3.12:


[...]
564s autopkgtest [18:34:00]: test autodep8-python3: set -e ; for py in 
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing 
with $py:" ; $py -c "import msal_extensions; print(msal_extensions)" ; done

564s autopkgtest [18:34:00]: test autodep8-python3: [---
564s Testing with python3.12:
564s Traceback (most recent call last):
564s   File "", line 1, in 
564s   File 
"/usr/lib/python3/dist-packages/msal_extensions/__init__.py", line 11, 
in 

564s from .cache_lock import CrossPlatLock
564s   File 
"/usr/lib/python3/dist-packages/msal_extensions/cache_lock.py", line 7, 
in 

564s from distutils.version import LooseVersion
564s ModuleNotFoundError: No module named 'distutils'
565s autopkgtest [18:34:01]: test autodep8-python3: ---]
--- End Message ---
--- Begin Message ---
Source: microsoft-authentication-extensions-for-python
Source-Version: 1.1.0-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated 
microsoft-authentication-extensions-for-python 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, 11 Dec 2023 10:46:23 +
Source: microsoft-authentication-extensions-for-python
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Luca Boccassi 
Closes: 1056425
Changes:
 microsoft-authentication-extensions-for-python (1.1.0-1) unstable; 
urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/1.1.0' (Closes: #1056425)
   * Bump Standards-Version to 4.6.2, no changes
   * Bump copyright year ranges in d/copyright
Checksums-Sha1:
 da2c2a6647c5fcf903d1bc834648c503d46da87e 2578 
microsoft-authentication-extensions-for-python_1.1.0-1.dsc
 4ffe513eac6680e694bacfad5d44ddc435ce8514 26931 
microsoft-authentication-extensions-for-python_1.1.0.orig.tar.gz
 00ba9be509d63325bdd99877bac97080a8304428 3352 
microsoft-authentication-extensions-for-python_1.1.0-1.debian.tar.xz
 033dcd6e6424eba0615d885f32b435b6da1c4a57 8592 
microsoft-authentication-extensions-for-python_1.1.0-1_source.buildinfo
Checksums-Sha256:
 ca5d39039f68f5e0575fa3c730d9b8aec9f3e73f94637ea6ef202151147ac07f 2578 
microsoft-authentication-extensions-for-python_1.1.0-1.dsc
 e49fcc7f16228f9645aab2b1033479b6ee8b93655c70326392d19c4affb99a7b 26931 
microsoft-authentication-extensions-for-python_1.1.0.orig.tar.gz
 f08a1f1def1420506a247b898fb54964093505dfd59d71c4a80dafa18d074d61 3352 
microsoft-authentication-extensions-for-python_1.1.0-1.debian.tar.xz
 786a792abdee6c27756c1bcbf12aa26dfe8cd1225af203055febe27ec5910e62 8592 
microsoft-authentication-extensions-for-python_1.1.0-1_source.buildinfo
Files:
 e51323e7aa71748cb2f3ff792816029f 2578 python optional 
microsoft-authentication-extensions-for-python_1.1.0-1.dsc
 19deb5ab241212d8a6e8563810827d82 26931 python optional 
microsoft-authentication-extensions-for-python_1.1.0.orig.tar.gz
 549183e93ab7238b281492a2622c181d 3352 python optional 
microsoft-authentication-extensions-for-python_1.1.0-1.debian.tar.xz
 

Bug#1056516: marked as pending in qstylizer

[Julian Gilbey]

Control: tag -1 pending

Hello,

Bug #1056516 in qstylizer 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/qstylizer/-/commit/47cdadceaa15632148efd6015c5834841b75d8bd


Fix package tests for Python 3.12 (closes: #1056516)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056516

Processed: Bug#1056516 marked as pending in qstylizer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056516 [src:qstylizer] qstylizer's autopkg tests fail with Python 3.12
Added tag(s) pending.

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

Bug#1058027: pybj: FTBFS with Python 3.12

[Graham Inggs]

Source: pybj
Version: 0.2.6-1
Severity: serious
Tags: ftbfs sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

pybj FTBFS [1] with Python 3.12 as a supported version.  I've copied
what I hope is the relevant part of the log below.

Regards
Graham

[1] https://buildd.debian.org/status/package.php?p=pybj


==
FAIL: test_recursion (test.TestEncodeDecodeFpExt.test_recursion)
--
Traceback (most recent call last):
  File "/<>/.pybuild/cpython3_3.12_bjdata/build/test/test.py",
line 488, in test_recursion
with self.assert_raises_regex(RuntimeError, 'recursion'):
AssertionError: RuntimeError not raised

==
FAIL: test_recursion (test.TestEncodeDecodePlainExt.test_recursion)
--
Traceback (most recent call last):
  File "/<>/.pybuild/cpython3_3.12_bjdata/build/test/test.py",
line 488, in test_recursion
with self.assert_raises_regex(RuntimeError, 'recursion'):
AssertionError: RuntimeError not raised

--
Ran 120 tests in 4.563s

FAILED (failures=2)
E: pybuild pybuild:395: test: plugin distutils failed with: exit
code=1: cd /<>/.pybuild/cpython3_3.12_bjdata/build;
python3.12 -m unittest discover -v test/
I: pybuild base:310: cd
/<>/.pybuild/cpython3_3.11_bjdata/build; python3.11 -m
unittest discover -v test/

Bug#1057899: marked as done (libc++abi-18-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2023 11:34:29 +
with message-id 
and subject line Bug#1057899: fixed in llvm-toolchain-snapshot 
1:18~++20231211102647+75193b192ad9-1~exp1
has caused the Debian Bug report #1057899,
regarding libc++abi-18-dev has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libc++experimental.a
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.)


-- 
1057899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc++abi-18-dev
Version: 1:18~++20231203063627+9f78edbd20ed-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libc++-17-dev

libc++abi-18-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/libc++experimental.a is contained in
the packages
 * libc++-17-dev/1:17.0.6-2 as present in unstable
 * libc++abi-18-dev/1:18~++20231203063627+9f78edbd20ed-1~exp1 as present in 
experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:18~++20231211102647+75193b192ad9-1~exp1
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated 
llvm-toolchain-snapshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 11 Dec 2023 10:26:59 +0100
Source: llvm-toolchain-snapshot
Architecture: source
Version: 1:18~++20231211102647+75193b192ad9-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1057899
Changes:
 llvm-toolchain-snapshot (1:18~++20231211102647+75193b192ad9-1~exp1) 
experimental; urgency=medium
 .
   [ Matthias Klose ]
   * Set the cpu defaults for the ARM32 architectures:
 - armel: arm926ej-s. Addresses: #1056115.
 - armhf: cortex-a8.
 Thanks to Arnd Bergmann and Ard Biesheuvel for the fixes.
   * Apply the proposed fix for D158491, build failure on mips64el, still
 unreviewed upstream. Addresses: #1056116.
 .
   [ Sylvestre Ledru ]
   * New snapshot release
   * Fix a libc++ conflicts (Closes: #1057899)
Checksums-Sha1:
 2a702ea486445a1b8e79fe09b6c1e62777be5505 8412 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1.dsc
 419865d05f0ca180be6de04526c2caf4fa274df7 153910868 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9.orig.tar.xz
 fa52f2a24afa16157e630d76a140f8679931a66e 169568 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1.debian.tar.xz
 d56e14f40e6b7f45867b08131fc7b76bb6009fd6 42322 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1_amd64.buildinfo
Checksums-Sha256:
 f552e3e4aa76eff628d8744a96872f1638fbc99f1e8687905047a8be4773fc7c 8412 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1.dsc
 e3ce9ac92ca43f6573e9e8f9e429cbe7e76e9ac04dae217254f84b1de79f3fcc 153910868 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9.orig.tar.xz
 ec53cc5ffaaf0f5db835fd6c5745ded09e51ecd99c43aac5516e868005e9f3c3 169568 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1.debian.tar.xz
 21573fb2f45680d8ec57bbe7548fc86f577e1a50ff28d076f1e92ab292bb833b 42322 
llvm-toolchain-snapshot_18~++20231211102647+75193b192ad9-1~exp1_amd64.buildinfo
Files:
 73f454aa53bf69eb2c012e35db2bf5f3 8412 devel optional 

Processed: reassign 1057967 to src:linux

[Debian Bug Tracking System]

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

> reassign 1057967 src:linux 6.1.66-1
Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my 
physical bookworm/gnome computer largely unusable
Bug reassigned from package 'linux-image-6.1.0-15-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.1.66+1.
Ignoring request to alter fixed versions of bug #1057967 to the same values 
previously set
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Marked as found in versions linux/6.1.66-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my 
physical bookworm/gnome computer largely unusable
Added tag(s) moreinfo.

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

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Kevin,

On Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price wrote:
> Package: linux-image-6.1.0-15-amd64
> Version: 6.1.66-1
> Severity: critical
> Control: -1 notfound 6.1.64-1
> 
> When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
> misbehaves in many ways, rendering it largely unusable. With kernels up
> to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
> this seemed fine.
> 
> Misbehavior includes, not limited to:
> 
> 1. Most actions take considerably longer than usual.
> 
> 2. The GDM greeter has an English keyboard layout, which otherwise is
> German. (Login works.)
> 
> 3. There seems to be no network connectivity. No WiFi icon. "ping
> 8.8.8.8" returns IIRC network unreachable.
> 
> 4. Launching Firefox does apparently nothing.
> 
> 5. Launching gnome-terminal does work, but some basic commands just
> freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
> the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".
> 
> 6. Shutting down takes ages, with systemd waiting for a bunch of
> processes (sudo) and services to terminate, most of the latter seem to
> be somehow network-related, but you tell me which aren't.
> 
> After more that 10 min I used hard power-off, leaving my ext4 dirty, but
> being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
> -13 working properly, and -15 showing the exact same misbehavior
> reproducibly.
> 
> I'll attach all I could get out of reportbug running under 6.1.0-15, and
> please let me know what further testing I may perform IOT help you.
> Please also specify whether you'd like me to do that testing under
> 6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
> will do anything fine.

It still would be helpfull if you can get to the logs of the previous
boot. After booting back in the working kernel, do you have anything
sensible logged in the previous boot log? If so can you share that
please? I'm right now curious to find out if we see the same as
#1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
issue.

Regards,
Salvatore

Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Steve,

On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote:
> Package: src:linux
> Version: 6.1.66-1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> I would have tried to report this from the 6.1.66 kernel but once a
> suspend is attempted network access is also broken so I have had to
> reboot into a working kernel in order to report the bug.
> 
> The problem may be related to the wireless network drivers since some
> processes that can't be frozen for suspend are NetworkManager,
> wpa-supplicant, and iw.
> 
> I have included boot messages from the affected kernel through an
> attempt to suspend the system including the traces from the processes
> that seem to get wedged by an attempt to suspend.
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 2023-12-10T18:48:54.150384-08:00 glitch kernel: [0.00] microcode: 
> microcode updated early to revision 0x21, date = 2019-02-13
> 2023-12-10T18:48:54.151278-08:00 glitch kernel: [0.00] Linux version 
> 6.1.0-15-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 
> 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 
> 6.1.66-1 (2023-12-09)
> 2023-12-10T18:48:54.151283-08:00 glitch kernel: [0.00] Command line: 
> BOOT_IMAGE=/vmlinuz-6.1.0-15-amd64 root=/dev/mapper/glitch-root ro quiet
> 2023-12-10T18:48:54.151286-08:00 glitch kernel: [0.00] BIOS-provided 
> physical RAM map:
> 2023-12-10T18:48:54.151288-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x-0x0009d7ff] usable
> 2023-12-10T18:48:54.151289-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0009d800-0x0009] reserved
> 2023-12-10T18:48:54.151290-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x000e-0x000f] reserved
> 2023-12-10T18:48:54.151297-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0010-0x1fff] usable
> 2023-12-10T18:48:54.151298-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x2000-0x201f] reserved
> 2023-12-10T18:48:54.151299-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x2020-0x40003fff] usable
> 2023-12-10T18:48:54.151300-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x40004000-0x40004fff] reserved
> 2023-12-10T18:48:54.151301-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x40005000-0xcec2] usable
> 2023-12-10T18:48:54.151302-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xcec3-0xdae9efff] reserved
> 2023-12-10T18:48:54.151303-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdae9f000-0xdaf9efff] ACPI NVS
> 2023-12-10T18:48:54.151306-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdaf9f000-0xdaffefff] ACPI data
> 2023-12-10T18:48:54.151307-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdafff000-0xdf9f] reserved
> 2023-12-10T18:48:54.151308-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xf800-0xfbff] reserved
> 2023-12-10T18:48:54.151309-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfec0-0xfec00fff] reserved
> 2023-12-10T18:48:54.151310-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed08000-0xfed08fff] reserved
> 2023-12-10T18:48:54.151311-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed1-0xfed19fff] reserved
> 2023-12-10T18:48:54.151319-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed1c000-0xfed1] reserved
> 2023-12-10T18:48:54.151320-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfee0-0xfee00fff] reserved
> 2023-12-10T18:48:54.151321-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xffc0-0x] reserved
> 2023-12-10T18:48:54.151322-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0001-0x00011e5f] usable
> 2023-12-10T18:48:54.151323-08:00 glitch kernel: [0.00] NX (Execute 
> Disable) protection: active
> 2023-12-10T18:48:54.151324-08:00 glitch kernel: [0.00] SMBIOS 2.7 
> present.
> 2023-12-10T18:48:54.151327-08:00 glitch kernel: [0.00] DMI: LENOVO 
> 2306CTO/2306CTO, BIOS G2ETA7WW (2.67 ) 09/09/2016
> 2023-12-10T18:48:54.151328-08:00 glitch kernel: [0.00] tsc: Fast TSC 
> calibration using PIT
> 2023-12-10T18:48:54.151329-08:00 glitch kernel: [0.00] tsc: Detected 
> 2494.294 MHz processor
> 2023-12-10T18:48:54.151330-08:00 glitch kernel: [0.001086] e820: update 
> [mem 0x-0x0fff] usable ==> reserved
> 2023-12-10T18:48:54.151331-08:00 glitch kernel: [0.001089] e820: remove 
> [mem 0x000a-0x000f] usable
> 2023-12-10T18:48:54.151332-08:00 glitch kernel: [

Processed: Re: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1057969 [src:linux] linux-image-6.1.0-15-amd64: suspend/resume broken in 
6.1.66 on Lenovo Thinkpad X230
Added tag(s) moreinfo.

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

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 
'model.pdb'
Added tag(s) confirmed.

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

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Andrius Merkys]

Control: tags -1 + confirmed

Hi,

On 2023-12-10 22:51, Santiago Vila wrote:

Package: src:promod3
Version: 3.3.1+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]


[...]


==
ERROR: testExit0 (__main__.HelpActionTests.testExit0)
--
Traceback (most recent call last):
   File "/<>/actions/tests/test_action_build-model.py", 
line 48, in testExit0

     os.remove('model.pdb')
FileNotFoundError: [Errno 2] No such file or directory: 'model.pdb'

--
Ran 3 tests in 5.583s


I can reproduce this in clean chroot on barriere.d.o. Interestingly, 
FTBFS happens only when building on two threads, four thread build 
succeeds. I have a feeling that the test execution order is important 
somehow. Will give a look and/or forward upstream. New upstream release 
is out, need to check first if the issue persists there.


Andrius

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

[Santiago Vila]

El 10/12/23 a las 23:31, tony mancill escribió:

I'm not able to reproduce this locally, and the only potentially
relevant difference I see between the AWS testbed and my local
environment is that I am running Intel and the AWS system is AMD.


Well spotted! Yes, I believe that could explain the difference.

In fact, I have failed builds on AWS instances of type t3a.small,
t3a.large, c6a.large and r6a.large, all of which (I believe) have
AMD processors, and I still keep some successful builds logs
made in the past on GCP instances of type t2d (Intel).

Thanks.