Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1

[Andreas Tille]

Hi Sébastien,

Am Thu, Dec 01, 2022 at 08:30:04AM +0100 schrieb Sébastien Jodogne:
> > I admit I would have loved if you would have made some noise about this
> > conference on the Debian Med list.  I hope you had a successful
> > conference.
> 
> The conference was great success, and I advertised about it on the Debian
> Med mailing list back in August:
> https://lists.debian.org/debian-med/2022/08/msg00060.html
> 
> Unfortunately, I got no feedback from our community.

Ahhh, sorry, my fault for forgetting this!  And for sure a shame that
nobody joined.

> The openSUSE community
> was present, and I hope we'll get submissions from our community in the next
> edition of this joint conference.

Yes, I hope to be able to join next time.
 
> 
> > > I'll have a look by Wednesday 30th November.
> > 
> > Do you think you can work on this in the next couple of days?
> 
> Yes, as soon as I finalize a research application that could gather funding
> for Orthanc and GNU Health... sorry for the delay, I got feedback yesterday
> that required a rework for this application.

Good luck for the application

 Andreas.

-- 
http://fam-tille.de

Processed: let's retitle

[Debian Bug Tracking System]

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

> retitle 1005899 mplayer needs someone's commitment to be part of testing
Bug #1005899 [src:mplayer] mplayer: should not release with bookworm
Changed Bug title to 'mplayer needs someone's commitment to be part of testing' 
from 'mplayer: should not release with bookworm'.
> thanks
Stopping processing here.

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

Bug#1025227: agenda.app: flaky autopkgtest: seems to mix up dates with large timezone offsets

[Paul Gevers]

Source: agenda.app
Version: 0.46-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. It seems that the DateTime test fails if the 
date from date/time + timezone yields a different date than date/time 
alone. (But I could be misinterpreting the logs).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/a/agenda.app/28801138/log.gz

Failed test: (2022-11-29 23:30:52.885 -0600) DateTest.m:25 ... 
comparing with date only we have equality



https://ci.debian.net/data/autopkgtest/testing/arm64/a/agenda.app/28486849/log.gz

Failed test: (2022-11-20 07:23:21.228 +0800) DateTest.m:25 ... 
comparing with date only we have equality



https://ci.debian.net/data/autopkgtest/testing/armel/a/agenda.app/28101939/log.gz

Failed test: (2022-11-10 22:10:37.391 -0600) DateTest.m:25 ... 
comparing with date only we have equality



https://ci.debian.net/data/autopkgtest/testing/s390x/a/agenda.app/28776884/log.gz

Failed test: (2022-11-28 22:52:25.440 -0500) DateTest.m:25 ... 
comparing with date only we have equality


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025229: mksh: flaky autopkgtest on several architectures

[Paul Gevers]

Source: mksh
Version: 59c-19
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. Also the failures on arm64 seem consistent now 
in testing (but it has a pass in unstable).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mksh/28332115/log.gz

E: static-musl: regress did not pass

https://ci.debian.net/data/autopkgtest/testing/arm64/m/mksh/28784302/log.gz

E: full: regress did not pass

https://ci.debian.net/data/autopkgtest/testing/armhf/m/mksh/26990327/log.gz

E: static-dietlibc: regress did not pass


OpenPGP_signature
Description: OpenPGP digital signature

Processed: closing 1024687

[Debian Bug Tracking System]

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

> close 1024687 1.2.0-2
Bug #1024687 [libfm-qt11] libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt 
functionalities
There is no source info for the package 'libfm-qt11' at version '1.2.0-2' with 
architecture ''
Unable to make a source version for version '1.2.0-2'
Marked as fixed in versions 1.2.0-2.
Bug #1024687 [libfm-qt11] libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt 
functionalities
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1025112: marked as pending in python-os-win

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1025112 in python-os-win 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/openstack-team/libs/python-os-win/-/commit/692eac9ae845028024e455e80ba3469a2e725103


Add py3.11-use-getfullargspec-not-getargspec.patch (Closes: #1025112).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025112

Processed: Bug#1025112 marked as pending in python-os-win

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025112 [src:python-os-win] python-os-win: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Added tag(s) pending.

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

Bug#1025231: r-cran-performance: autopkgtest regression in testing

[Graham Inggs]

Source: r-cran-performance
Version: 0.9.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2022-07-24, the autopkgtests of r-cran-performance
regressed in testing [1].  It seems this regression then allowed
subsequent versions of r-cran-performance to migrate without their
tests passing.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-performance/testing/amd64/

Bug#1025232: hdf5: Build dependencies on openjdk-11 that will not be in bookworm

[Sebastian Ramacher]

Source: hdf5
Version: 1.10.8+repack-4
Severity: serious
Tags: sid bookworm
X-Debbugs-Cc: sramac...@debian.org

openjdk-11 will not be be part of bookworm (see #1023237). Please adapt
the package to use the default JDK version (openjdk-17) in its build
dependencies.

Cheers
-- 
Sebastian Ramacher

Bug#1025112: marked as done (python-os-win: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 09:37:33 +
with message-id 
and subject line Bug#1025112: fixed in python-os-win 5.7.1-3
has caused the Debian Bug report #1025112,
regarding python-os-win: (autopkgtest) needs update for python3.11: module 
'inspect' has no attribute 'getargspec'
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.)


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

Source: python-os-win
Version: 5.7.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-os-win  from testing5.7.1-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-os-win/28750378/log.gz

==
FAIL: 
os_win.tests.unit.test_utilsfactory.TestHyperVUtilsFactory.test_utils_public_signatures

os_win.tests.unit.test_utilsfactory.TestHyperVUtilsFactory.test_utils_public_signatures
--
testtools.testresult.real._StringException: Traceback (most recent call 
last):
  File 
"/tmp/autopkgtest-lxc.f4g2jevo/downtmp/build.Pwx/src/os_win/tests/unit/test_utilsfactory.py", 
line 167, in test_utils_public_signatures

self.assertPublicAPISignatures(base_class, tested_class)
  File 
"/tmp/autopkgtest-lxc.f4g2jevo/downtmp/build.Pwx/src/os_win/tests/unit/test_utilsfactory.py", 
line 189, in assertPublicAPISignatures

baseargs = inspect.getargspec(basemethods[name])
   ^^
AttributeError: module 'inspect' has no attribute 'getargspec'


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-os-win
Source-Version: 5.7.1-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-os-win package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Dec 2022 10:09:59 +0100
Source: python-os-win
Architecture: source
Version: 5.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1025112
Changes:
 python-os-win (5.7.1-3) unstable; urgency=medium
 .
   * Add py3.11-use-getfullargspec-not-getargspec.patch (Closes: #1025112).
Checksums-Sha1:
 61cb7bbcdff2a5b488aa88118e5397d47dc0b62f 2504 python-os-win_5.7.1-3.dsc
 c7665c64cff8c971ff8e834257e4f40ca9a361da 4248 
python-os-win_5.7.1-3.debian.tar.xz
 f5d52d59eaf348cf6207fa7dc7dead66ee90f302 11508 
python-os-win_5.7.1-3_amd64.buildinfo
Checksums-Sha256:
 59cf8bff83c0e7940dd93957a76d7b33c27c98d151915aa930c432869c8d380e 2504 
python-os-win_5.7.1-3.dsc
 e1af6866a50da6277504e053015f31cd7e9671ac3725034200099e77c432a084 4248 
python-os-win_5.7.1-3.debian.tar.xz
 582278979124f7c26411

Bug#1025234: prometheus: flaky autopkgtest (on 32 bit archs?)

[Paul Gevers]

Source: prometheus
Version: 2.33.5+ds1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package (because it 
blocked glibc). I noticed that it regularly fails. At least on 32 bits 
architectures, I think the test (and maybe the general use of the 
package?) is nearing memory limititations? Maybe the failures on 64 bit 
architectures were due to non-available test dependencies (I didn't 
check all logs).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/p/prometheus/28799146/log.gz

FAIL
FAILgithub.com/prometheus/prometheus/promql 9.743s


--- FAIL: TestQueryHistogramFromBlocksWithCompaction (11.14s)
--- PASS: 
TestQueryHistogramFromBlocksWithCompaction/serial_blocks_with_only_histograms 
(1.23s)
--- PASS: 
TestQueryHistogramFromBlocksWithCompaction/serial_blocks_with_either_histograms_or_floats_in_a_block_and_not_both 
(2.57s)
--- PASS: 
TestQueryHistogramFromBlocksWithCompaction/serial_blocks_with_mix_of_histograms_and_float64 
(2.59s)
--- PASS: 
TestQueryHistogramFromBlocksWithCompaction/overlapping_blocks_with_only_histograms 
(1.68s)
--- PASS: 
TestQueryHistogramFromBlocksWithCompaction/overlapping_blocks_with_only_histograms_and_only_float_in_a_series 
(2.63s)
--- FAIL: 
TestQueryHistogramFromBlocksWithCompaction/overlapping_blocks_with_mix_of_histograms_and_float64 
(0.44s)

panic: mmap, size 134217728: cannot allocate memory [recovered]
panic: mmap, size 134217728: cannot allocate memory

goroutine 11328 [running]:
testing.tRunner.func1.2({0x88a108, 0x4c04030})
/usr/lib/go-1.19/src/testing/testing.go:1396 +0x27c
testing.tRunner.func1()
/usr/lib/go-1.19/src/testing/testing.go:1399 +0x3f4
panic({0x88a108, 0x4c04030})
/usr/lib/go-1.19/src/runtime/panic.go:884 +0x23c
github.com/prometheus/prometheus/tsdb.handleChunkWriteError({0xbe5844, 
0x4c04030})


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:1225
 +0x88
github.com/prometheus/prometheus/tsdb/chunks.(*ChunkDiskMapper).WriteChunk(0x4bba000, 
0x1, 0x0, 0xafc80, {0xbe9cd8, 0x4b9a6b0}, 0x93e6b8)


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks.go:418
 +0x130
github.com/prometheus/prometheus/tsdb.(*memSeries).mmapCurrentHeadChunk(0x4baa120, 
0x4bba000)


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:1214
 +0xa0
github.com/prometheus/prometheus/tsdb.(*memSeries).cutNewHeadChunk(0x4baa120, 
0xdbba0, 0x1, 0x4bba000, 0x6ddd00)


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:1149
 +0x24
github.com/prometheus/prometheus/tsdb.(*memSeries).appendPreprocessor(0x4baa120, 
0xdbba0, 0x1, 0x4bba000, 0x6ddd00)


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:1101
 +0x19c
github.com/prometheus/prometheus/tsdb.(*memSeries).append(0x4baa120, 
0xdbba0, 0x3fe1b0583e7c7c6a, 0x2, 0x4bba000, 0x6ddd00)


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:983
 +0x4c
github.com/prometheus/prometheus/tsdb.(*headAppender).Commit(0x4be6140)

/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/head_append.go:876
 +0x1410
github.com/prometheus/prometheus/tsdb.CreateBlock({0x3eea780, 0xa, 0xa}, 
{0x3d12000, 0x72}, 0x0, {0xbe57e0, 0x105b3f8})


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/tsdbblockutil.go:63
 +0x570
github.com/prometheus/prometheus/tsdb.createBlock({0xbeb950, 0x35e6960}, 
{0x3d12000, 0x72}, {0x3eea780, 0xa, 0xa})


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/block_test.go:474
 +0x5c
github.com/prometheus/prometheus/tsdb.TestQueryHistogramFromBlocksWithCompaction.func2(0x35e6960, 
{0x6142000, 0x4, 0x4})


/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/db_test.go:6035
 +0x95c
github.com/prometheus/prometheus/tsdb.TestQueryHistogramFromBlocksWithCompaction.func8(0x35e6960)

/tmp/autopkgtest-lxc.mtbe33dm/downtmp/autopkgtest_tmp/.build/src/github.com/prometheus/prometheus/tsdb/db_test.go:6133
 +0x43c
testing.tRunner(0x

Bug#1025195: marked as done (watcher-dashboard: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 09:51:54 +
with message-id 
and subject line Bug#1025195: fixed in watcher-dashboard 8.0.0-2
has caused the Debian Bug report #1025195,
regarding watcher-dashboard: (autopkgtest) needs update for python3.11: module 
'inspect' has no attribute 'getargspec'
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.)


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

Source: watcher-dashboard
Version: 8.0.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
watcher-dashboard  from testing8.0.0-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/w/watcher-dashboard/28796452/log.gz

Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0001_initial... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying auth.0009_alter_user_last_name_max_length... OK
  Applying auth.0010_alter_group_name_max_length... OK
  Applying auth.0011_update_proxy_permissions... OK
  Applying auth.0012_alter_user_first_name_max_length... OK
  Applying sessions.0001_initial... OK
Destroying test database for alias 'default' 
('file:memorydb_default?mode=memory&cache=shared')...

Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.2p5z09al/downtmp/build.k2W/src/manage.py", 
line 23, in 

execute_from_command_line(sys.argv)
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 419, in execute_from_command_line

utility.execute()
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 413, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
line 23, in run_from_argv

super().run_from_argv(argv)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 354, in run_from_argv

self.execute(*args, **cmd_options)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 398, in execute

output = self.handle(*args, **options)
 ^
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
line 55, in handle

failures = test_runner.run_tests(test_labels)
   ^^
  File "/usr/lib/python3/dist-packages/django/test/runner.py", line 
728, in run_tests

self.run_checks(databases)
  File "/usr/lib/python3/dist-packages/django/test/runner.py", line 
665, in run_checks

call_command('check', verbosity=self.verbosity, databases=databases)
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 181, in call_command

return command.execute(*args, **defaults)
   ^^
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 398, in execute

output = self.handle(*args, **options)
 

Bug#1025237: scalene: FTBFS with python3.11

[Andrius Merkys]

Source: scalene
Severity: serious
Version: 1.4.1-1

Hello,

scalene FTBFS with added support for python3.11:

building 'scalene.pywhere' extension
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I. -Isrc -Isrc/include -I/usr/include/python3.11 -c 
src/source/pywhere.cpp -o 
build/temp.linux-x86_64-cpython-311/src/source/pywhere.o -std=c++14
src/source/pywhere.cpp: In function ‘int whereInPython(std::string&, 
int&, int&)’:
src/source/pywhere.cpp:176:40: error: ‘PyThreadState’ {aka ‘struct _ts’} 
has no member named ‘frame’; did you mean ‘cframe’?

  176 |   if (threadState == 0 || threadState->frame == 0) {
  |^
  |cframe
src/source/pywhere.cpp:190:34: error: ‘PyThreadState’ {aka ‘struct _ts’} 
has no member named ‘frame’; did you mean ‘cframe’?

  190 |   for (auto frame = threadState->frame; frame != nullptr;
  |  ^
  |  cframe
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.11 setup.py build


Andrius

Bug#1025238: python-uvicorn: FTBFS with python3.11

[Andrius Merkys]

Source: python-uvicorn
Severity: serious
Version: 0.17.6-1

Hello,

python-uvicorn FTBFS with added support for python3.11:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
http_proxy= https_proxy= dh_auto_test
I: pybuild pybuild:300: cp -r /<>/tests 
/<>/.pybuild/cpython3_3.11/build
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
python3.11 -m pytest -s --verbose -k 'not test_run and not 
test_invalid_upgrade and not test_default_headers and not 
test_trace_logging and not test_websocket_auto' 
--ignore=tests/protocols/test_websocket.py
= test session starts 
==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- 
/usr/bin/python3.11

cachedir: .pytest_cache
rootdir: /<>, configfile: setup.cfg
plugins: asyncio-0.19.0, mock-3.8.2, anyio-3.6.2
asyncio: mode=Mode.STRICT
collecting ... collected 201 items / 8 errors / 1 deselected / 200 selected

 ERRORS 

_ ERROR collecting 
.pybuild/cpython3_3.11/build/tests/test_default_headers.py __

tests/test_default_headers.py:1: in 
import httpx
/usr/lib/python3/dist-packages/httpx/__init__.py:2: in 
from ._api import delete, get, head, options, patch, post, put, 
request, stream

/usr/lib/python3/dist-packages/httpx/_api.py:4: in 
from ._client import Client
/usr/lib/python3/dist-packages/httpx/_client.py:9: in 
from ._auth import Auth, BasicAuth, FunctionAuth
/usr/lib/python3/dist-packages/httpx/_auth.py:10: in 
from ._models import Request, Response
/usr/lib/python3/dist-packages/httpx/_models.py:1: in 
import cgi
/usr/lib/python3.11/cgi.py:57: in 
warnings._deprecated(__name__, remove=(3,13))
/usr/lib/python3.11/warnings.py:514: in _deprecated
warn(msg, DeprecationWarning, stacklevel=3)
E   DeprecationWarning: 'cgi' is deprecated and slated for removal in 
Python 3.13


Many similar failures follow as well, skipped here for brevity.

Andrius

Bug#1025222: marked as done (clblas: ftbfs due to Could NOT find PythonInterp)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 10:19:29 +
with message-id 
and subject line Bug#1025222: fixed in clblas 2.12-3
has caused the Debian Bug report #1025222,
regarding clblas: ftbfs due to Could NOT find PythonInterp
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.)


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

Dear Maintainer,

The package has ftbfs issue due to:

```
-- Found OPENCL: /usr/lib/x86_64-linux-gnu/libOpenCL.so (found version "2.0") 
-- FindOpenCL /usr/lib/x86_64-linux-gnu/libOpenCL.so, /usr/include
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake 
(found suitable version "1.74.0", minimum required is "1.33.0") found 
components: program_options 
-- Boost_PROGRAM_OPTIONS_LIBRARY: Boost::program_options
CMake Error at 
/usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
Call Stack (most recent call first):
  /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.25/Modules/FindPythonInterp.cmake:170 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  library/CMakeLists.txt:17 (find_package)
...

```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=clblas&arch=amd64&ver=2.12-2&stamp=1669843177&raw=0

It is easy to fix the issue and I will update it once verifing.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: clblas
Source-Version: 2.12-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated clblas 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: Thu, 01 Dec 2022 11:04:47 +0100
Source: clblas
Architecture: source
Version: 2.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Bastian Germann 
Closes: 1025222
Changes:
 clblas (2.12-3) unstable; urgency=medium
 .
   * Team upload.
   * Move Vcs to salsa
 .
   [ Bo YU ]
   * Fix ftbfs due to missing python_interp. (Closes: #1025222)
Checksums-Sha1:
 899701487e9b2d60fde7d7445557d3f22ea49499 2139 clblas_2.12-3.dsc
 3dac235f69df84bb79034dc23649d72d17f050df 8652 clblas_2.12-3.debian.tar.xz
 3d52d44980d86d5b5067710d395f4c1c8b0ca7ff 7510 clblas_2.12-3_source.buildinfo
Checksums-Sha256:
 177a86023cad4a620ba60e37db354bbdfea4d6809e97ab3deb981f2d7730824b 2139 
clblas_2.12-3.dsc
 8ee712e974bdd87f87b196cec065b00b2bf9e53a42123786def617231c9f5ba3 8652 
clblas_2.12-3.debian.tar.xz
 de9d590f3e0f2447bd270f34a9b3575ea542f7105661c288eb958a965c22a458 7510 
clblas_2.12-3_source.buildinfo
Files:
 275303d8ef833eeda34033827984ab91 2139 science optional clblas_2.12-3.dsc
 9d785627d37a2f76851f0dbcaf15d8bf 8652 science optional 
clblas_2.12-3.debian.tar.xz
 4b8a65729365d58e292b810753f7d312 7510 science optional 
clblas_2.12-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOIfiUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIsoDACDnm0cT8348uSjgQ8Tqenc1cxnu4b0S1/v
ThuvlaCGSOwjA3tLgNLrKgDhPWrxdZsx8pMjkVMlix47V3vhLX9xONsLMW9OKt4p
uzD2MrL+LbKM3bBsgoyq0D2sfqGYoFkn07HZa5+GzCnyGvsv+OxkUzdsNORtqR7s
IgRyTrN58pwoVgDEQFbn8LU4oG8FUmAb5nIJBDtWTctLTKOaMcFK6S5uZUICrRmM
OQmgG4juRAoldvoIHt/RWPFKc16ke6aQSHqWfbZWPZhLNZ+kRlFkKIFgmaj928hV
ABCPvcekZqsE3MvEiMLX2NwQNki53OLtO922Dp4NYlFBGi0v3ggzPYRHOeZ/TwAM
ty7/wtQNNDDwidf/W0FmjUJzTXAKgvNNwxu/DT4J6ukPZzRYv/wkQoLvoEypz+2j
LbwIguLL27AXY9Es7P8zx3UQeuI4KXqI2irQDwbUlHYXqYBXKklgoX93Tg09+5i5
aXG7IOKhR8sao5z/RMMKU3o9iDc8Yy8=
=NQlN
-END PGP SIGNATURE End Message ---

Bug#1024898: mozc: FTBFS on armel

[Gunnar Hjalmarsson]

How important is it that mozc is available on armel? Would it be an 
option to drop the armel support in bookworm?


--
Gunnar

Bug#969609: marked as done (rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 10:36:46 +
with message-id 
and subject line Bug#969609: fixed in rust-zstd 0.11.2-1
has caused the Debian Bug report #969609,
regarding rust-zstd: unbuildable, uninstallable, depends on non-existent 
rust-zstd-safe
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.)


-- 
969609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-zstd
Version: 0.5.1-1
Severity: grave

The rust-zstd package has both a dependency and a build-dependency on
librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in
Debian.  Presumably it would be built by a rust-zstd-safe package, but no
such package exists, including in the Debian NEW queue.

The binaries of rust-zstd that are in Debian were clearly not built on the
autobuilders, and all other architectures besides amd64 are unable to build
this package.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-zstd
Source-Version: 0.11.2-1
Done: Peter Michael Green 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Dec 2022 10:16:02 +
Source: rust-zstd
Architecture: source
Version: 0.11.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 969609
Changes:
 rust-zstd (0.11.2-1) unstable; urgency=medium
 .
   * Package zstd 0.11.2+zstd.1.5.2 from crates.io using debcargo 2.6.0 
(Closes: #969609)
 .
   [ Blair Noctis ]
   * Package zstd 0.11.2+zstd.1.5.2 from crates.io using debcargo 2.5.0
   * Remove unavailable zstd features
   * Make bindgen and pkg-config empty features as zstd-sys patch mandates them
   * Fix tests where fixtures are absent
   * Remove partial-io as it's archived upstream
 .
   [ Sylvestre Ledru ]
   * Team upload.
   * Package zstd 0.5.3+zstd.1.4.5 from crates.io using debcargo 2.4.3
Checksums-Sha1:
 333ee30f347802c2dfd811b4dcd9ac77f1dc8fa7 2387 rust-zstd_0.11.2-1.dsc
 563e5740cebef0ee0a64b03c96b144eaf4f786cc 28987 rust-zstd_0.11.2.orig.tar.gz
 bb9a13bd8583ba9c5293857f06f2f1a8842f6bb9 4412 rust-zstd_0.11.2-1.debian.tar.xz
 5868a069f39be353767f9aba1bd9915a42f4305a 14468 
rust-zstd_0.11.2-1_source.buildinfo
Checksums-Sha256:
 a0422de4fa2406e27d49ca1f2acc0e3b36e6c699a56610effaa0624132d16e1d 2387 
rust-zstd_0.11.2-1.dsc
 20cc960326ece64f010d2d2107537f26dc589a6573a316bd5b1dba685fa5fde4 28987 
rust-zstd_0.11.2.orig.tar.gz
 e0c42632743ee0de82683055f2154a4a5cf0cc8c948bce370c6646c2ec2741f9 4412 
rust-zstd_0.11.2-1.debian.tar.xz
 30c0f80321d621b7d739368f561e7f3e068984101e474fb5a950dc0fe7c9129f 14468 
rust-zstd_0.11.2-1_source.buildinfo
Files:
 50976fa6f188417d9d5bbca6d5104850 2387 rust optional rust-zstd_0.11.2-1.dsc
 073a49c0bbf42567732c431ac924d9d1 28987 rust optional 
rust-zstd_0.11.2.orig.tar.gz
 368be4bd25f378206d28b6b9e0f10d25 4412 rust optional 
rust-zstd_0.11.2-1.debian.tar.xz
 98da0428310111d38d1d1eed922aefe0 14468 rust optional 
rust-zstd_0.11.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmOIfykUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xtxnw//WAcIcQGUUij2OS43pfTetKDRGEB2
LMXBvSU50FcXeNDr/w3TpmeshAY5IUt/XfQ5RSaSN3V0hOx1CUvEeEdg6TxNcRkl
e9hgTcRl/b9Q9clvodCnqMmvadW2Ijvj1Lixs7FOLjwkiEWCxZQQrsKcLroYDu+z
NcYES+6aL+i+tXhsKBdAly5BCABCxzMXbNCySRaJD5Al5KuZ24wJUGgu7Ng/2Cmq
lP2+AcIvU+ktenf7jtPar3vuJDb7w5f8ZqexBHSzWulBjIpvcNfT2tfqIvoLnk/d
aQlu8qf4surH5pO9ho6Xq4HvJWc1gqPgewvfVwD75BJr3wRa/0OJfPYQC2h6qyts
O/LZWV/qqEs635MQjR2LVjs493K4w2NWyPrplIF

Processed: reassign 1021311 to src:faad2, fixed 1021311 in 2.10.1-1, affects 1021311, reassign 1025156 to wnpp ...

[Debian Bug Tracking System]

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

> reassign 1021311 src:faad2 2.10.0-2
Bug #1021311 {Done: Sebastian Ramacher } [vlc] vlc: No 
sound with some AAC encoded MKV videos
Bug reassigned from package 'vlc' to 'src:faad2'.
No longer marked as found in versions vlc/3.0.17.4-5.
No longer marked as fixed in versions 2.10.1-1.
Bug #1021311 {Done: Sebastian Ramacher } [src:faad2] vlc: 
No sound with some AAC encoded MKV videos
Marked as found in versions faad2/2.10.0-2.
> fixed 1021311 2.10.1-1
Bug #1021311 {Done: Sebastian Ramacher } [src:faad2] vlc: 
No sound with some AAC encoded MKV videos
Marked as fixed in versions faad2/2.10.1-1.
> affects 1021311 + src:vlc
Bug #1021311 {Done: Sebastian Ramacher } [src:faad2] vlc: 
No sound with some AAC encoded MKV videos
Added indication that 1021311 affects src:vlc
> reassign 1025156 wnpp
Bug #1025156 [olivetin] [ITP]: OliveTin -- Give safe and simple access to 
predefined shell commands from a web interface.
Warning: Unknown package 'olivetin'
Bug reassigned from package 'olivetin' to 'wnpp'.
Ignoring request to alter found versions of bug #1025156 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1025156 to the same values 
previously set
> tags 1025232 - sid bookworm
Bug #1025232 [src:hdf5] hdf5: Build dependencies on openjdk-11 that will not be 
in bookworm
Removed tag(s) sid and bookworm.
> tags 1024898 - sid bookworm
Bug #1024898 [src:mozc] mozc: FTBFS on armel
Removed tag(s) sid and bookworm.
> tags 951902 + sid bookworm
Bug #951902 [src:duktape] duktape: python2 is required to regenerate some 
source files
Added tag(s) bookworm and sid.
> tags 1025185 - sid bookworm
Bug #1025185 [src:sphinx] sphinx: (autopkgtest) needs update for python3.11: 
AssertionError
Removed tag(s) sid and bookworm.
> tags 945665 - bullseye
Bug #945665 [src:dump1090-mutability] dump1090-mutability: Python2 removal in 
sid/bullseye
Removed tag(s) bullseye.
> tags 1025135 + sid bookworm
Bug #1025135 [src:libcoap2] libcoap2: Do not ship in bookworm
Added tag(s) bookworm and sid.
> found 1024877 5.9.8-2
Bug #1024877 [src:python-softlayer] python-softlayer: tests fail with python 
3.11
Marked as found in versions python-softlayer/5.9.8-2.
> tags 1024829 + experimental
Bug #1024829 {Done: Paul Gevers } [src:mozc] src:mozc: fails 
to migrate to testing for too long: unresolved RC bug and FTBFS on armel
Added tag(s) experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021311
1024829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024829
1024877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024877
1024898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024898
1025135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025135
1025156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025156
1025185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025185
1025232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025232
945665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945665
951902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024032: marked as done (rust-criterion: FTBFS: needs to be compiled against librust-cast (>> 0.3))

[Debian Bug Tracking System]

Your message dated Thu, 1 Dec 2022 11:02:54 +
with message-id <316b22db-ad10-0aca-5856-95af3c477...@debian.org>
and subject line re: rust-criterion - inconsistent dependencies on cast.
has caused the Debian Bug report #1023842,
regarding rust-criterion: FTBFS: needs to be compiled against librust-cast (>> 
0.3)
to be marked as done.

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

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


-- 
1023842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-criterion+async-futures-dev
Severity: serious
X-Debbugs-Cc: none, Reinhard Tartler 

The rust-cast crate has been updated from version 0.2 to 0.3 on 2022/11/11.

Can you please build against that new version of rust-cast?

-rt


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

Version: 0.3.6-2

This was fixed in 0.3.6-2--- End Message ---

Bug#1023842: marked as done (rust-criterion - inconsistent dependencies on cast.)

[Debian Bug Tracking System]

Your message dated Thu, 1 Dec 2022 11:02:54 +
with message-id <316b22db-ad10-0aca-5856-95af3c477...@debian.org>
and subject line re: rust-criterion - inconsistent dependencies on cast.
has caused the Debian Bug report #1023842,
regarding rust-criterion - inconsistent dependencies on cast.
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.)


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

Package: rust-criterion
Version: 0.3.6-1
Severity: serious
Tags: patch

The rust-criterion package has inconsistent dependencies on the cast crate, the
dependency in the main Cargo.toml is on version 0.3, but the dependencies in the
debian packaging and in the embedded copy of the criterion-plot crate are at 0.2

I have updated the cast crate in Debian to 0.3, and prepared an update for the
rust-criterion package to use 0.3 consistently. I tested that the package built
succesfully and the autopkgtests passed with these changes.

While working on the fix, I discovered the clean target wasn't cleaning up
properly, so I fixed it to do so.

Debdiff attatched, If I get no response I will probablly NMU this in a week or
so.
diff -Nru rust-criterion-0.3.6/debian/changelog 
rust-criterion-0.3.6/debian/changelog
--- rust-criterion-0.3.6/debian/changelog   2022-11-07 07:51:45.0 
+
+++ rust-criterion-0.3.6/debian/changelog   2022-11-10 20:23:39.0 
+
@@ -1,3 +1,13 @@
+rust-criterion (0.3.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update inconsistent cast dependencies to a consistent 0.3
++ The cast dependency in the main Cargo.toml was at 0.3 while the Debian
+  Dependency and the cast dependency in the plot subcrate were at 0.2.
+  * Fix clean target.
+
+ -- Peter Michael Green   Thu, 10 Nov 2022 20:23:39 +
+
 rust-criterion (0.3.6-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-criterion-0.3.6/debian/control 
rust-criterion-0.3.6/debian/control
--- rust-criterion-0.3.6/debian/control 2022-11-07 07:50:12.0 +
+++ rust-criterion-0.3.6/debian/control 2022-11-10 20:23:39.0 +
@@ -7,7 +7,7 @@
  gnuplot-nox ,
  librust-approx-0.5+default-dev ,
  librust-atty-0.2+default-dev ,
- librust-cast-0.2+default-dev ,
+ librust-cast-0.3+default-dev ,
  librust-clap-2-dev (>= 2.33) ,
  librust-criterion-plot-0.4+default-dev (>= 0.4.4) ,
  librust-csv-1+default-dev (>= 1.1) ,
@@ -40,7 +40,7 @@
 Depends:
  gnuplot-nox,
  librust-atty-0.2+default-dev,
- librust-cast-0.2+default-dev,
+ librust-cast-0.3+default-dev,
  librust-clap-2-dev (>= 2.33),
  librust-criterion-plot-0.4+default-dev,
  librust-csv-1+default-dev,
diff -Nru 
rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch 
rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
--- rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
1970-01-01 00:00:00.0 +
+++ rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
2022-11-10 20:23:39.0 +
@@ -0,0 +1,28 @@
+Description: Bump cast dependency in plot subcrate.
+ Taken from 
https://github.com/bheisler/criterion.rs/commit/06be43cda0169f5b9c91eb0298545c253ba8830f
+Author: Peter Michael Green 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2022-11-10
+
+--- rust-criterion-0.3.6.orig/plot/Cargo.toml
 rust-criterion-0.3.6/plot/Cargo.toml
+@@ -12,7 +12,7 @@ categories = ["visualization"]
+ license = "MIT/Apache-2.0"
+ 
+ [dependencies]
+-cast = "0.2"
++cast = "0.3"
+ itertools = "0.10"
+ 
+ [dev-dependencies]
diff -Nru rust-criterion-0.3.6/debian/patches/series 
rust-criterion-0.3.6/debian/patches/series
--- rust-criterion-0.3.6/debian/patches/series  2022-11-07 07:45:44.0 
+
+++ rust-criterion-0.3.6/debian/patches/series  2022-11-10 20:23:39.0 
+
@@ -2,3 +2,4 @@
 1002_modernize_macro_syntax.patch
 2001_plotters.patch
 2002_no_unstable_features.patch
+-bump-plot-cast-dependency.patch
diff -Nru rust-criterion-0.3.6/debian/rules rust-criterion-0.3.6/debian/rules
--- rust-criterion-0.3.6/debian/rules   2022-06-22 12:00:18.0 +
+++ rust-criterion-0.3.6/debian/rules   2022-11-10 20:23:39.0 +
@@ -7,3

Bug#1019206: marked as done (librust-criterion+async-std-dev: Package is uninstallable, rust-async-std missing in debian)

[Debian Bug Tracking System]

Your message dated Thu, 1 Dec 2022 11:12:43 +
with message-id <3712c529-bd01-8539-8a22-198ebcea5...@debian.org>
and subject line re: librust-criterion+async-std-dev: Package is uninstallable, 
rust-async-std missing in debian
has caused the Debian Bug report #1019206,
regarding librust-criterion+async-std-dev: Package is uninstallable, 
rust-async-std missing in debian
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.)


-- 
1019206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-criterion+async-std-dev
Severity: serious
Justification: packages must be installable, prevents other packages from 
reaching testing
X-Debbugs-Cc: d...@jones.dk, debian-r...@lists.debian.org

The package librust-criterion+async-std-dev is currently uninstallable in
unstable and testing, which prevents it and other dependent packages (like
rust-rustls) from reaching testing. Currently, this even threats the removal
unrelated packages from testing, cf. #1018225

I see two options out here:

 a) disable the 'async-std' feature
 b) package 'async-std'

Note that while working on the rust-rtnetlink package, a similar issue popped 
up, and I've
opted for option a). Should 'async-std' become available, I'd be happy to 
change 'rust-rtnetlink'
to enable the 'async-std' feature.

Best,
-rt


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

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

Versions of packages librust-criterion+async-std-dev depends on:
pn  librust-async-std-1+default-dev  
pn  librust-criterion-dev

librust-criterion+async-std-dev recommends no packages.

librust-criterion+async-std-dev suggests no packages.
--- End Message ---
--- Begin Message ---

The package librust-criterion+async-std-dev is currently uninstallable in
unstable and testing, which prevents it and other dependent packages (like
rust-rustls) from reaching testing. Currently, this even threats the removal
unrelated packages from testing, cf. #1018225

I see two options out here:

 a) disable the 'async-std' feature
 b) package 'async-std'


rust-async-std is now in Debian.--- End Message ---

Bug#1025242: fastapi: FTBFS with python3.11

[Andrius Merkys]

Source: fastapi
Severity: serious
Version: 0.85.0-2

Hello,

fastapi FTBFS with added support for python3.11:

pybuild --test --test-pytest -i python{version} -p "3.11 3.10"
I: pybuild base:240: PYTHONPATH=/<>/build/lib/ python3.11 
-m pytest tests/ --ignore=tests/test_default_response_class.py 
--ignore-glob=tests/test_tutorial/test_security/test_tutorial005* 
--ignore=te
sts/test_tutorial/test_custom_response/test_tutorial009c.py 
--ignore=tests/test_response_by_alias.py -k ' not 
test_get_custom_response and not test_root and not test_async_testing 
and not test_orjson_non_str_key

s'
= test session starts 
==

platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /<>, configfile: pyproject.toml
plugins: anyio-3.6.2
collected 35 items / 287 errors

 ERRORS 

_ ERROR collecting tests/test_additional_properties.py 
_

tests/test_additional_properties.py:3: in 
from fastapi import FastAPI
fastapi/__init__.py:7: in 
from .applications import FastAPI as FastAPI
fastapi/applications.py:15: in 
from fastapi import routing
fastapi/routing.py:23: in 
from fastapi.dependencies.models import Dependant
fastapi/dependencies/models.py:3: in 
from fastapi.security.base import SecurityBase
fastapi/security/__init__.py:1: in 
from .api_key import APIKeyCookie as APIKeyCookie
fastapi/security/api_key.py:3: in 
from fastapi.openapi.models import APIKey, APIKeyIn
fastapi/openapi/models.py:8: in 
import email_validator  # type: ignore
/usr/lib/python3/dist-packages/email_validator/__init__.py:6: in 
import dns.resolver
/usr/lib/python3/dist-packages/dns/resolver.py:38: in 
import dns.query
/usr/lib/python3/dist-packages/dns/query.py:52: in 
import httpx
/usr/lib/python3/dist-packages/httpx/__init__.py:2: in 
from ._api import delete, get, head, options, patch, post, put, 
request, stream

/usr/lib/python3/dist-packages/httpx/_api.py:4: in 
from ._client import Client
/usr/lib/python3/dist-packages/httpx/_client.py:9: in 
from ._auth import Auth, BasicAuth, FunctionAuth
/usr/lib/python3/dist-packages/httpx/_auth.py:10: in 
from ._models import Request, Response
/usr/lib/python3/dist-packages/httpx/_models.py:1: in 
import cgi
/usr/lib/python3.11/cgi.py:57: in 
warnings._deprecated(__name__, remove=(3,13))
/usr/lib/python3.11/warnings.py:514: in _deprecated
warn(msg, DeprecationWarning, stacklevel=3)
E   DeprecationWarning: 'cgi' is deprecated and slated for removal in 
Python 3.13


Many similar failures follow as well, skipped here for brevity.

Andrius

Bug#1025008: marked as done (deepin-movie-reborn: hardcoded dependency on libmpv1)

[Debian Bug Tracking System]

Your message dated Thu, 1 Dec 2022 17:04:01 +0545
with message-id 
and subject line Close bug #1025008 as it is fixed.
has caused the Debian Bug report #1025008,
regarding deepin-movie-reborn: hardcoded dependency on libmpv1
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.)


-- 
1025008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-movie-reborn
Version: 5.10.8-1
Severity: serious
Tags: sid bookworm

libmpv is currently transitioning from libmpv1 to libmpv2. Rebuild of
deepin-movie-reborn did not pick up the new dependency on libmpv2 since
it is hardcoded to libmpv1. In general, hardcoding shared library
dependencies is not necessary and if the binaries would be linked
properly, it would be taken care of by ${shlib:Depends}.

The build log indicates that with mpv 0.35.0, the mpv backend is no longer
built.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

Version: 5.10.8-2

Closing the bug as it is fixed in 5.10.8-2.


OpenPGP_0x4B542AF704F74516.asc
Description: OpenPGP public key


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

Bug#1025231: marked as done (r-cran-performance: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 11:25:02 +
with message-id 
and subject line Bug#1025231: fixed in r-cran-performance 0.10.1-1
has caused the Debian Bug report #1025231,
regarding r-cran-performance: autopkgtest regression in testing
to be marked as done.

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

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


-- 
1025231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-performance
Version: 0.9.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2022-07-24, the autopkgtests of r-cran-performance
regressed in testing [1].  It seems this regression then allowed
subsequent versions of r-cran-performance to migrate without their
tests passing.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-performance/testing/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-performance
Source-Version: 0.10.1-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-performance 
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: Thu, 01 Dec 2022 11:37:14 +0100
Source: r-cran-performance
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1025231
Changes:
 r-cran-performance (0.10.1-1) unstable; urgency=medium
 .
   * r-cran-estimatr is now available and can be used for testing
 Closes: #1025231
   * New upstream version
   * dh-update-R to update Build-Depends (routine-update)
Checksums-Sha1:
 61796653dedaedfa0b303a9856531305fbbf1bed 2808 r-cran-performance_0.10.1-1.dsc
 9af904a00b5712c1b6023340ac3a8243e162ab49 3182610 
r-cran-performance_0.10.1.orig.tar.gz
 16265e25c6c09aa18248622a611f6f303a65d942 3544 
r-cran-performance_0.10.1-1.debian.tar.xz
 08b540f207e075ef20a5b1be9a2a0e88531ba256 10956 
r-cran-performance_0.10.1-1_amd64.buildinfo
Checksums-Sha256:
 0f4b3ad10bf61812746f23631cb125342ea8095c321ead5dded2d065e4e1c4ba 2808 
r-cran-performance_0.10.1-1.dsc
 ff9ee7ddf034bc090501e03412eff3778641ee2e72f5096ac348d1e5ecff5fd4 3182610 
r-cran-performance_0.10.1.orig.tar.gz
 bee74d52d89737a833479cdfbe9b466a3d8b9aeba09b8c976ff4320d9c589371 3544 
r-cran-performance_0.10.1-1.debian.tar.xz
 fff58a188a6a5bc9521365003dc7bbc6d8c1076dab416ca8c5d5c347f3265db4 10956 
r-cran-performance_0.10.1-1_amd64.buildinfo
Files:
 49238301ae4bf3ac3b02be16a71c6b61 2808 gnu-r optional 
r-cran-performance_0.10.1-1.dsc
 f5099bb851a2508b672bcf2b98f66deb 3182610 gnu-r optional 
r-cran-performance_0.10.1.orig.tar.gz
 e9426722f6d5a2b25d9f28f151c3ef6d 3544 gnu-r optional 
r-cran-performance_0.10.1-1.debian.tar.xz
 da640b13ae9344df87f1c509d0ab39db 10956 gnu-r optional 
r-cran-performance_0.10.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmOIiYURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFD1hAAm1dtFQVf32NPGGS1Z7xuSuZXWAhWQ1Rk
WFqaX9q4+4evRCvbBv8VXKZ0glCCMTGujJRDITG92bAyGfey/CDiTFU5yU5BOXbj
OQ6foursq5wvX/w59pBGwg8mCLs8gjDviglZCw0sYgexDPpsNdOdPNTYpxFwKmqi
hEAGiHEu2wrrjnEPLbrUxnm9GEyDiKi6PdJJzIgzGkElUD89GH5Nx18pdWx+wdIE
tjqv5Rt6Wpog4QiJWuO1t4wa5u8wqojQlogwkLdNmoYcxpV9Nh9n1gfZ5aH0jEku
smRYHc56DZg5X+99TRtEwiFeJBDg2/VP8ur415zRI0FK59jtLefBc01h67SHmzzj
Xdh9hyBwLjDeMJbU8RoHBty/i6UFbRfC/RaMeGLBq1G/WW3AQ+5hhexFQ4B8cdIk
OBWhaNOMDE+6JUF8I1F0fXKdVXRkJviH8wivlYsEFRbT6zU4KSYy91FRdT4XtdRJ
2MFlD9D11QNsZSrbMQKbM7vlrHIMxXBs2X0M5+nGhPuJkUqxk3694XpBCnWCjsaY
ARFwunQwFVm0QVSPDL1b72Tcf4JaUgUvnoBAxuy+Gufp/U1jg3TZq7cR/jskJ9AL
z7N1bxaqoHPt+j60uztFEG48AwnO/aQHxJaTv1EOpPHPz/THrvHvRBhgFiQ+jNrS
+E4kETrG9XQ=
=TZWu
-END PGP SIGNATURE End Message ---

Bug#1013365: python-aiortc: autopkgtest regression on armhf: [Errno 542398533] Generic error in an external library

[Jonas Smedegaard]

Source: python-aiortc
Followup-For: Bug #1013365

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

eems this bug was not in aiortc after all: Disappeared in a rebuild.

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOIkNwACgkQLHwxRsGg
ASHFmg//cIthQQWrzU2bZdwZEIaIpM3Gym7wwdyIPFkonVbLEDJA3Qm4ZXJEVjh0
dl2IZR6BTTfkgdLAoQ3P5dBjk5YMTb7TQjwxpt/OJ1jK/Rx83htaGwm1IwIlr/Rq
YZQ0DlJxrHdKQ3Vv/H3xHxMKIibKc3G0o1LzZrZr4TfASOZVXyh4GIHME7t2kRF1
UByPE0Mq4SdY0MmI0bDV0xwgiIKVk5UYGz9bUOxAUkJnnp+KHSN7EFC5DNG20qUi
mp/LfVyN6ivt0mtSF7lAOhwZiZHJ+LFTPsx2ZVvmdedPxWa8UFLqr38+P2+ba/tf
MOdv1SH2M+OE21C3a/1C0A5BHPOWWpkwFrOPHwP3/MW5++S7osoO11EPFLbXm4z3
cidTPcp083M3taI86IiafMHuF1YkCEXQE+/R0+AW2QDub9vT+H8xrBHhIP1rvOCo
ekmzGceyMnL9QGkKXC68hzbAoYzLAfyPkpCTym87lY5wWKCL2frs7xXxq/oi4TLI
UpNWgavOrGKt6HTtCD3NIRbTxpkrgKN43GsqYLMD78588cAsAknAW7FHfApNSI9T
6F1Qc2Hwd+zHLmofNdxIfuJGa26KW6hRcke4HjEdTyRKf+MpoY26bSVQP39Xoyav
DKrGaKQ2wjvVJfY85sOtpAFjLsqgxFZOzsGrWaCneLCRlDs6k1E=
=qtEA
-END PGP SIGNATURE-

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Simon McVittie]

On Thu, 01 Dec 2022 at 01:11:15 +0100, Gert van de Kraats wrote:
> Recently a general upgrade was executed with gnome-shell
> upgrading from version 43.0-2 to 43.1-2.

Are you sure that the root cause was this gnome-shell upgrade, and not
an upgrade of the mesa packages that may have happened at the same time?

Does downgrading gnome-shell (and the mutter library that it depends on)
back to 43.0 resolve this? If not, then it is likely that there is no
gnome-shell change that will fix it.

Alternatively, does downgrading the Mesa packages (libgl1-mesa-dri and
related packages) to the version from Debian 11 (20.3.5-1) resolve this?

> Some user-friendly person has decided to stop support for the i915 dri
> driver.
> As a "service" the mesa-upgrade at Debian also automatically deletes this
> driver.

The old i915 driver was removed from the main mesa packaging and is now
in a separate driver collection, mesa-amber, consisting of drivers for
older hardware that are no longer actively maintained. The Mesa team
packaged mesa-amber () and it was in
the NEW queue for a while, but it seems to have disappeared. I'm not
sure what its status was, perhaps the archive administrators rejected it?

What CPU and GPU are you running this on? I see you're using an i686
kernel: is it a 32-bit system?

i686 (32-bit PC) systems are increasingly difficult to support or
test on, so it is looking as though Debian 12 is likely to be the last
version that can be installed on i686 hardware. It might be safer to
stick to Debian 11 on hardware this old, or upgrade to newer hardware
(second-hand 64-bit PCs are widely available, and any good-quality laptop
from the last 10 years would probably improve both performance and power
consumption compared with a 32-bit system, especially if it is a desktop).

If your GPU is old enough to be unsupported by the crocus and iris drivers
(which are the replacement for i915 for newer Intel GPUs), then your CPU
is probably also rather old, which can cause problems for the llvmpipe
(swrast) driver: that driver does some basic rendering on the CPU, but
to do that at an acceptable speed, it tries to make use of non-baseline
CPU extensions.

> Also if "Gnome on Xorg" is started there is no flickering problem.
> In that case swrast is used for software rendering.

If your GPU is too old for the drivers available in mesa, and the mesa-amber
drivers are not installed, then the intended fallback is llvmpipe
(swrast_dri.so). I would have expected that it would be used for both Xorg
and Wayland. However, GNOME in Wayland mode might have higher requirements
for the quality of the drivers than GNOME in Xorg mode, or just different
behaviour, resulting in flickering in Wayland mode but not in Xorg mode.

> I do not know which method gnome with wayland is using, but it is not
> swrast.

Do you have evidence that it is not using swrast? If yes, what?

smcv

Bug#1025182: marked as done (rich: (autopkgtest) needs update for python3.11: AssertionError)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 11:52:10 +
with message-id 
and subject line Bug#1025182: fixed in rich 12.6.0-1
has caused the Debian Bug report #1025182,
regarding rich: (autopkgtest) needs update for python3.11: AssertionError
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.)


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

Source: rich
Version: 12.4.4-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
rich   from testing12.4.4-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rich/28796437/log.gz

=== FAILURES 
===
__ test_inspect_text 
___


@skip_pypy3
def test_inspect_text():
expected = (
"╭  ─╮\n"
"│ str(object='') -> str  │\n"
"│ str(bytes_or_buffer[, encoding[, errors]]) ->  │\n"
"│ str│\n"
"││\n"
"│ 33 attribute(s) not shown. Run │\n"
"│ inspect(inspect) for options.  │\n"
"╰╯\n"
)
print(repr(expected))

  assert expected == render("Hello")
E   AssertionError: assert '╭───...──╯\n' == 
'╭───...──╯\n'

E Skipping 248 identical leading characters in diff, use -v to show
E Skipping 140 identical trailing characters in diff, use -v to show
E│
E - │ 34 attribut
E ?^
E + │ 33 attribut
E ?^

tests/test_inspect.py:102: AssertionError
- Captured stdout call 
-
"╭  ─╮\n│ str(object='') -> 
str  │\n│ str(bytes_or_buffer[, encoding[, 
errors]]) ->  │\n│ str│\n│ 
 │\n│ 33 attribute(s) not 
shown. Run │\n│ inspect(inspect) for options. 
  │\n╰╯\n"
 test_inspect_builtin_function 
_


@skip_pypy3
def test_inspect_builtin_function():
expected = (
"╭──  ───╮\n"
"│ def print(...) │\n"
"││\n"
"│ print(value, ..., sep=' ', end='\\n',   │\n"
"│ file=sys.stdout, flush=False)  │\n"
"││\n"
"│ 29 attribute(s) not shown. Run │\n"
"│ inspect(inspect) for options.  │\n"
"╰╯\n"
)

  assert expected == render(print)
E   AssertionError: assert '╭── ...──╯\n' == 
'╭── ...──╯\n'

E Skipping 53 identical leading characters in diff, use -v to show
E + def print(...) │
E - def print(*args, sep=' ', end='\n', fi

Bug#1025248: uwsgi: FTBFS with ruby3.1 as default

[Lucas Kanashiro]

Source: uwsgi
Version: 2.0.20-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User:debian-r...@lists.debian.org
Usertags: ruby3.1

Dear maintainer,

We tried to binNMU your package for the ongoing ruby3.1 as default ruby
transition. It failed:

https://buildd.debian.org/status/package.php?p=uwsgi

 CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
python3 uwsgiconfig.py -v --plugin plugins/rack_ruby30 debian/buildconf/uwsgi-plugin.ini rack_ruby30
using profile: debian/buildconf/uwsgi-plugin.ini
detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/12/include', 
'/usr/local/include', '/usr/include/x86_64-linux-gnu', '/usr/include']
*** uWSGI building and linking plugin plugins/rack_ruby30 ***
Error: unable to find directory 'plugins/rack_ruby30'
make: *** [debian/rules:426: debian/stamp-uwsgi-plugin-rack-ruby3.0] Error 1
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


The attached debdiff fixes the issue, converting the rack plugin binary name to 
ruby3.1.

--
Lucas Kanashiro
diff -Nru uwsgi-2.0.20/debian/changelog uwsgi-2.0.20/debian/changelog
--- uwsgi-2.0.20/debian/changelog   2022-03-21 08:00:44.0 -0300
+++ uwsgi-2.0.20/debian/changelog   2022-12-01 09:26:09.0 -0300
@@ -1,3 +1,10 @@
+uwsgi (2.0.20-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/control: rename uwsgi-plugin-rack-ruby3.0 to uwsgi-plugin-rack-ruby3.1.
+
+ -- Lucas Kanashiro   Thu, 01 Dec 2022 09:26:09 -0300
+
 uwsgi (2.0.20-4) unstable; urgency=medium
 
   [ Jonas Smedegaard ]
diff -Nru uwsgi-2.0.20/debian/control uwsgi-2.0.20/debian/control
--- uwsgi-2.0.20/debian/control 2022-03-21 08:00:44.0 -0300
+++ uwsgi-2.0.20/debian/control 2022-12-01 09:25:12.0 -0300
@@ -737,7 +737,7 @@
  This package provides Python 3 WSGI plugin for uWSGI
  (linked with Python 3 runtime).
 
-Package: uwsgi-plugin-rack-ruby3.0
+Package: uwsgi-plugin-rack-ruby3.1
 Architecture: any
 Depends:
  uwsgi-core (= ${binary:Version}),

Bug#1019684: marked as done (yard: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require "gettext/mo")

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 12:46:52 +
with message-id 
and subject line Bug#1019684: fixed in yard 0.9.28-1
has caused the Debian Bug report #1019684,
regarding yard: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:  
Failure/Error: require "gettext/mo"
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.)


-- 
1019684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yard
Version: 0.9.27-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild yard with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>  Failure/Error: require "gettext/mo"
> 
># received :exist? with unexpected arguments
>  expected: ("foo/fr.po")
>   got: 
> ("/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/extensions/x86_64-linux/3.1.0/RedCloth-4.3.2/gem.build_complete")
>  # ./lib/yard/i18n/po_parser.rb:21:in `'
>  # ./lib/yard/i18n/po_parser.rb:8:in `'
>  # ./lib/yard/i18n/po_parser.rb:3:in `'
>  # ./lib/yard/i18n/po_parser.rb:2:in `'
>  # ./lib/yard/i18n/locale.rb:50:in `load'
>  # ./spec/i18n/locale_spec.rb:62:in `block (3 levels) in '
>  # ./spec/spec_helper.rb:121:in `block (2 levels) in '
>  # --
>  # --- Caused by: ---
>  # LoadError:
>  #   cannot load such file -- prime
>  #   ./lib/yard/i18n/po_parser.rb:21:in `'
> 
> Top 5 slowest examples (1.36 seconds, 29.1% of total time):
>   YARD::RegistryStore#save never saves as single object db if 
> single_object_db is false
> 1.02 seconds ./spec/registry_store_spec.rb:152
>   YARD::Registry Thread local maintains two Registries in separate threads
> 0.10087 seconds ./spec/registry_spec.rb:396
>   YARD::Registry Thread local allows setting of yardoc_file in separate 
> threads
> 0.10043 seconds ./spec/registry_spec.rb:417
>   YARD::Registry Thread local allows setting of po_dir in separate threads
> 0.10031 seconds ./spec/registry_spec.rb:442
>   YARD::Server::Commands::LibraryCommand#call sets :rdoc as the default 
> markup in regular mode
> 0.04345 seconds ./spec/server/commands/library_command_spec.rb:34
> 
> Top 5 slowest example groups:
>   YARD::Server::Commands::LibraryCommand
> 0.04285 seconds average (0.12856 seconds / 3 examples) 
> ./spec/server/commands/library_command_spec.rb:4
>   YARD::RegistryStore
> 0.03318 seconds average (1.09 seconds / 33 examples) 
> ./spec/registry_store_spec.rb:3
>   YARD::Parser::C::CParser
> 0.02566 seconds average (0.46193 seconds / 18 examples) 
> ./spec/parser/c_parser_spec.rb:3
>   
> YARD::Templates::Engine::Template__build_yard_Y2Z3fT_yard_0_9_27_templates_default_module
> 0.02072 seconds average (0.14503 seconds / 7 examples) 
> ./spec/templates/module_spec.rb:4
>   YARD::CLI::Display
> 0.01929 seconds average (0.05787 seconds / 3 examples) 
> ./spec/cli/display_spec.rb:3
> 
> Finished in 4.68 seconds (files took 0.61565 seconds to load)
> 1938 examples, 1 failure, 9 pending
> 
> Failed examples:
> 
> rspec ./spec/i18n/locale_spec.rb:43 # YARD::I18n::Locale#load returns true 
> for existent PO
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/yard/yard_0.9.27-1+rebuild1663008419_amd64-2022-09-12T18:47:00Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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


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

Bug#1024155: Fixed in Git [Re: libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)]

[Aaron M. Ucko]

Andreas Tille  writes:

> I have fixed this issue in Git.

Thanks!

> I'm wondering about the status of the
> ncbi-vdb transition[1].  Isn't it time to upload the packages to
> unstable now?  Just let me know if you need any help.

I first want to get a better picture of where sra-sdk 3.x stands in
terms of architecture support, which may be clearer with upgrades to
3.0.1 in place.  I've been working on them, but a power outage last
weekend delayed me; I'll try to wrap them up this weekend.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#1025249: wtdbg2: flaky autopkgtest: Segmentation fault

[Paul Gevers]

Source: wtdbg2
Version: 2.5-7
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it 
was blocking glibc. I noticed that it regularly fails (particularly on 
ppc64el, but not exclusively there).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/stable/ppc64el/w/wtdbg2/28644876/log.gz

[Sat Nov 26 06:40:02 2022] masked 154 repeat-like nodes by local 
subgraph analysis

[Sat Nov 26 06:40:02 2022] generating edges
/tmp/autopkgtest-lxc.t8xpx53w/downtmp/build.dY0/src/debian/tests/run-unit-test: 
line 23:  1447 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg



https://ci.debian.net/data/autopkgtest/testing/ppc64el/w/wtdbg2/27771576/log.gz

[Thu Nov  3 00:50:18 2022] sorting regs ...  Done
[Thu Nov  3 00:50:19 2022] generating intervals ... 
/tmp/autopkgtest-lxc.wcfl1vkh/downtmp/build.kT7/src/debian/tests/run-unit-test: 
line 23:  1310 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg



https://ci.debian.net/data/autopkgtest/testing/arm64/w/wtdbg2/26361496/log.gz

[Fri Sep 23 22:33:59 2022] masked 154 repeat-like nodes by local 
subgraph analysis

[Fri Sep 23 22:33:59 2022] generating edges
/tmp/autopkgtest-lxc.7iunliwg/downtmp/build.Yi1/src/debian/tests/run-unit-test: 
line 23:  2686 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg


OpenPGP_signature
Description: OpenPGP digital signature

Bug#912485: childsplay: Please migrate to python3-pygame

[Bastian Germann]

On Tue, 20 Oct 2020 21:19:16 +0200 Markus Koschany  wrote:

I have started to port childsplay to python3. There are no estimates
when it's done but I hope I can finish the work before we freeze.


Will you make it to the bookworm freeze? If not, please consider removing the 
package.

Bug#912485: childsplay: Please migrate to python3-pygame

[Markus Koschany]

Am Donnerstag, dem 01.12.2022 um 14:31 +0100 schrieb Bastian Germann:
> On Tue, 20 Oct 2020 21:19:16 +0200 Markus Koschany  wrote:
> > I have started to port childsplay to python3. There are no estimates
> > when it's done but I hope I can finish the work before we freeze.
> 
> Will you make it to the bookworm freeze? If not, please consider removing the
> package.

Probably not because there are other issue I have to attend to first. I don't
intend to remove the game, just to introduce it later again.


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

Processed: bug 1023327 is forwarded to https://salsa.debian.org/debian/notepadqq/-/merge_requests/1

[Debian Bug Tracking System]

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

> forwarded 1023327 https://salsa.debian.org/debian/notepadqq/-/merge_requests/1
Bug #1023327 [notepadqq] notepadqq: Fail to build with rollup 3
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/notepadqq/-/merge_requests/1'.
> thanks
Stopping processing here.

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

Bug#1025229: mksh: flaky autopkgtest on several architectures

[Thorsten Glaser]

Hi Paul,

> I looked at the results of the autopkgtest of your package. I noticed that it
> regularly fails. Also the failures on arm64 seem consistent now in testing 
> (but
> it has a pass in unstable).

thanks for bringing this to my attention. This is a bug in the
autopkgtest script in that it doesn’t take those tests whose
failure should be ignored into account, combined with these
tests failing much more than they used to on build infrastructure
(for which I *still* have not been able to find the underlying
reason).

I’ll fix the scripts (and the repro-builds issue) and upload RSN,
to ignore the allowed failures.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Processed: bug 1023341 is forwarded to https://github.com/pimutils/khal/issues/1092

[Debian Bug Tracking System]

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

> forwarded 1023341 https://github.com/pimutils/khal/issues/1092
Bug #1023341 [khal] Fails to add any event due to too new python3-tzlocal
Set Bug forwarded-to-address to 'https://github.com/pimutils/khal/issues/1092'.
> thanks
Stopping processing here.

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

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Gert van de Kraats]

Hello Simon,

Unfortunately my 32-bit Dell-laptop does not crash and I think the 
software-boys should not stop delivery of


software for older hardware, forcing to waste good working hardware.

Therefore I will use Debian testing as long as it supports 32-bit, so at 
least some one is testing something at 32-bit.


My previous upgrade was 2022-11-06, the next failing upgrade was 2022-11-27.

It contains 921 packages; also upgrade libgl1-mesa-dri:i386 22.2.0-1 
22.2.4-1 .


I am not sure problem is at gnome-shell itself.

I am almost sure it is not at mesa/swrast. I ran lsof for gnome-shell to 
check the open files.


If the i915 driver is present at X and wayland the i915 shared library 
is shown.


If the driver is not present at X the swrast library is shown, but not 
at wayland.


Perhaps gtk/pango is used for software-rendering at wayland.

I will try to downgrade gnome-shell and dependent packages.

Bug#1024395: grub-efi-amd64-signed: related to #1024447?

[Garrett McLean]

Package: grub-efi-amd64-bin
Version: 1+2.06+3~deb11u4
Followup-For: Bug #1024395

Dear Maintainer,

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

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

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

Hello,

Chiming in to say that I too am not seeing my mok in
mokutil --list-enrolled, which is strange because the drivers are
definitely signed, loaded and working just swell with sb enabled.

Also: when I select my stable installation on the grub menu, the screen turns
mostly black and I see something about about an efi stub and secure boot
being enabled. After a few seconds of this, kernel messages appear as normal.

GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX both seem to be ignored, or at
least, don't display the requested resolution.

videoinfo and videotest are "prohibited due to sb policy" (I paraphrase,
but that's the gist).

And, as in #1024447, I see ?s instead of lines bordering the grub menu.

Disabling sb fixes all these errors.

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

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

Versions of packages grub-efi-amd64-signed depends on:
ii  grub-common  2.06-3~deb11u4

Versions of packages grub-efi-amd64-signed recommends:
ii  shim-signed  1.38+15.4-7

grub-efi-amd64-signed suggests no packages.

Versions of packages grub-efi-amd64-bin depends on:
ii  grub-common  2.06-3~deb11u4

Versions of packages grub-efi-amd64-bin recommends:
ii  efibootmgr  17-1

-- no debconf information

Bug#1025249: wtdbg2: flaky autopkgtest: Segmentation fault

[Andreas Tille]

Hi Paul,

Am Thu, Dec 01, 2022 at 01:54:09PM +0100 schrieb Paul Gevers:
> https://ci.debian.net/data/autopkgtest/stable/ppc64el/w/wtdbg2/28644876/log.gz
> 
> [Sat Nov 26 06:40:02 2022] masked 154 repeat-like nodes by local subgraph
> analysis
> [Sat Nov 26 06:40:02 2022] generating edges
> /tmp/autopkgtest-lxc.t8xpx53w/downtmp/build.dY0/src/debian/tests/run-unit-test:
> line 23:  1447 Segmentation fault  wtdbg2 -x rs -g 4.6m -i
> pacbio_filtered.fastq -t 16 -fo dbg
> 
> 
> https://ci.debian.net/data/autopkgtest/testing/ppc64el/w/wtdbg2/27771576/log.gz
> 
> [Thu Nov  3 00:50:18 2022] sorting regs ...  Done
> [Thu Nov  3 00:50:19 2022] generating intervals ... 
> /tmp/autopkgtest-lxc.wcfl1vkh/downtmp/build.kT7/src/debian/tests/run-unit-test:
> line 23:  1310 Segmentation fault  wtdbg2 -x rs -g 4.6m -i
> pacbio_filtered.fastq -t 16 -fo dbg

OK, I excluded ppc64el.
 
> https://ci.debian.net/data/autopkgtest/testing/arm64/w/wtdbg2/26361496/log.gz
> 
> [Fri Sep 23 22:33:59 2022] masked 154 repeat-like nodes by local subgraph
> analysis
> [Fri Sep 23 22:33:59 2022] generating edges
> /tmp/autopkgtest-lxc.7iunliwg/downtmp/build.Yi1/src/debian/tests/run-unit-test:
> line 23:  2686 Segmentation fault  wtdbg2 -x rs -g 4.6m -i
> pacbio_filtered.fastq -t 16 -fo dbg

I decided to restrict the package to amd64 only since this is the
architecture which is most probably used and tested by upstream.

BTW, the autopkgtest for riscv64 does not have "Segmentation fault"
but

  
https://ci.debian.net/data/autopkgtest/unstable/riscv64/w/wtdbg2/27987776/log.gz

has:

1 contigs 2500 edges 0 basesautopkgtest [14:18:48]: ERROR: timed out on command 
"su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile 
>/dev/null 2>&1 || true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.a93se6k6/downtmp/build.2Wn/src"; mkdir -p -m 
1777 -- "/tmp/autopkgtest-lxc.a93se6k6/downtmp/run-unit-test-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.a93se6k6/downtmp/run-unit-test-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.a93se6k6/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.a93se6k6/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=4; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;cd 
"$buildtree"; chmod +x 
/tmp/autopkgtest-lxc.a93se6k6/downtmp/build.2Wn/src/debian/tests/run-unit-test; 
exec /tmp/autopkgtest-lxc.a93se6k6/downtmp/wrapper.sh 
--script-pid-file=/tmp/autopkgtest_script_pid 
--stderr=/tmp/autopkgtest-lxc.a93se6k6/downtmp/run-unit-test-stderr 
--stdout=/tmp/autopkgtest-lxc.a93se6k6/downtmp/run-unit-test-stdout -- 
/tmp/autopkgtest-lxc.a93se6k6/downtmp/build.2Wn/src/debian/tests/run-unit-test 
;" (kind: test)


This does not make the testing itself better, but I wanted to mention
this in case the debci setup needs to adjust some timeouts.

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1025171: [Pkg-zfsonlinux-devel] Bug#1025171: zfs-dkms FTBFS against 6.0.0-5-amd64

[M. Zhou]

Control: reassign -1 dkms 3.0.8-2
Control: retitle -1 regression: dkms/3.0.8-2 renders zfs-dkms FTBFS
Control: severity -1 serious

Hi,

Thank you for the information! I can confirm that this is the same issue
that you have encountered. By commenting out the --environment-overrides,
the current zfs-dkms package can be built against 6.0.0-5-amd64 successfully.

According to the build log when I filed the bug report, the problem is indeed
that the compiler cannot find the header files. I believed it was some -I ...
flags missing due to some reason.

So it is a regression bug in dkms/3.0.8-2, as -I flags needed for zfs-dkms
are accidentally removed.

On Wed, 2022-11-30 at 22:56 +, Heikki Kallasjoki wrote:
> There isn't enough detail to be sure, but this might be the same issue I
> hit on sid yesterday, so adding it here. It might also count as a dkms
> bug for all I know.
> 
> In my case, zfs-dkms fails to build against either of my currently
> installed kernels (5.19.0-1-amd64, 6.0.0-5-amd64), but only after
> updating the package dkms to version 3.0.8-2 (from 3.0.8-1).
> 
> This appears to be the result of the changes to the export-CC.patch:
> https://sources.debian.org/patches/dkms/3.0.8-2/export-CC.patch/
> 
> The 3.0.8-2 version adds the following commands to the prepare_build()
> function:
> 
> export CC=$CC
> export MAKEFLAGS="--environment-overrides"
> 
> I've verified that zfs-dkms builds fine for me if I temporarily comment
> out the second line from /usr/sbin/dkms.
> 
> A build log for a failed attempt (with the flag present) is at:
> https://0x0.st/o0fu.txt
> 
> The log also includes a dump of the environment variables at the start
> of the build, from a command I added to the dkms script.
> 
> Digging a little deeper, it appears that when `--environment-overrides`
> is set, a number of required command-line options (in particular, an -I
> option to add /var/lib/dkms/zfs/2.1.6/build/include in the include
> search path) fail to be set. I didn't manage to trace why exactly that
> is, but you can see both a failing and a working example (for one object
> file) at:
> https://0x0.st/o0EC.txt
> 
> FWIW, it seems like the build environment dkms uses inherits whatever
> was present in the environment when apt was called. If this is the case,
> then it feels to me including the `--environment-overrides` flag has
> potential to make things brittle. The effect of the flag is to: "Give
> variables taken from the environment precedence over variables from
> makefiles." Any arbitrary environment variables the user may have set
> for their own purposes might be unexpectedly overriding important
> variables from the Makefile(s).
> 
> ___
> Pkg-zfsonlinux-devel mailing list
> pkg-zfsonlinux-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-zfsonlinux-devel

Processed: Re: [Pkg-zfsonlinux-devel] Bug#1025171: zfs-dkms FTBFS against 6.0.0-5-amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dkms 3.0.8-2
Bug #1025171 [zfs-dkms] zfs-dkms FTBFS against 6.0.0-5-amd64
Bug reassigned from package 'zfs-dkms' to 'dkms'.
No longer marked as found in versions zfs-linux/2.1.6-3.
Ignoring request to alter fixed versions of bug #1025171 to the same values 
previously set
Bug #1025171 [dkms] zfs-dkms FTBFS against 6.0.0-5-amd64
Marked as found in versions dkms/3.0.8-2.
> retitle -1 regression: dkms/3.0.8-2 renders zfs-dkms FTBFS
Bug #1025171 [dkms] zfs-dkms FTBFS against 6.0.0-5-amd64
Changed Bug title to 'regression: dkms/3.0.8-2 renders zfs-dkms FTBFS' from 
'zfs-dkms FTBFS against 6.0.0-5-amd64'.
> severity -1 serious
Bug #1025171 [dkms] regression: dkms/3.0.8-2 renders zfs-dkms FTBFS
Ignoring request to change severity of Bug 1025171 to the same value.

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

Bug#1025261: vagrant: Broken with ruby3.1

[Guillem Jover]

Package: vagrant
Version: 2.2.19+dfsg-1
Severity: serious

Hi!

After the upgrade of ruby to the 3.1 version vagrant has stopped
working completely, I'm getting the following errors repeated multiple
times:

,---
/usr/lib/ruby/vendor_ruby/rubygems/resolver/conflict.rb:47:in 
`conflicting_dependencies': undefined method `request' for nil:NilClass 
(NoMethodError)

[@failed_dep.dependency, @activated.request.dependency]
   
from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:61:in 
`conflicting_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:55:in `initialize'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `exception'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `raise'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `rescue in 
resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:191:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in 
`resolve_current'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in 
activate_bin_path'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
from /usr/bin/vagrant:25:in `'
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:317:in
 `raise_error_unless_state': Unable to satisfy the following requirements: 
(Gem::Resolver::Molinillo::VersionConflict)

- `vagrant (= 2.2.19)` required by `user-specified dependency`
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:299:in
 `block in unwind_for_conflict'
from :90:in `tap'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:297:in
 `unwind_for_conflict'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:682:in
 `attempt_to_activate'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:254:in
 `process_topmost_state'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:182:in
 `resolve'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:43:in
 `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:190:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in 
`resolve_current'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in 
activate_bin_path'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
from /usr/bin/vagrant:25:in `'
`---

Installing ruby3.0 and forcing the «/usr/bin/ruby» symlink back to
ruby3.0 make vagrant work again.

Thanks,
Guillem

Bug#1025262: mir FTBFS, symbols files issues.

[Peter Green]

Source: mir
Version: 1.8.2+dfsg-3
Severity: serious
Tags: ftbfs

mir FTBFS on all architectures with symbols files issues
(there was previously a bug report for hppa, but since it now fails on release
architectures I feel a seperate bug report is deserved).

https://buildd.debian.org/status/fetch.php?pkg=mir&arch=amd64&ver=1.8.2%2Bdfsg-4%2Bb1&stamp=1669159921&raw=0

--- debian/libmirprotobuf3.symbols (libmirprotobuf3_1.8.2+dfsg-4+b1_amd64)
+++ dpkg-gensymbolskixGS3   2022-11-22 23:31:49.399075926 +
@@ -8,75 +8,85 @@
  MIR_PROTOBUF_PROTOBUF_3.6.0@MIR_PROTOBUF_PROTOBUF_3.6.0 1.7
  MIR_PROTOBUF_UBSAN@MIR_PROTOBUF_UBSAN 1.7
  _ZN3mir8protobuf10Connection12InternalSwapEPS1_@MIR_PROTOBUF_FEDORA 1.7
- _ZN3mir8protobuf10Connection16default_instanceEv@MIR_PROTOBUF_3 1.7
+#MISSING: 1.8.2+dfsg-4+b1# 
_ZN3mir8protobuf10Connection16default_instanceEv@MIR_PROTOBUF_3 1.7
  
_ZN3mir8protobuf10Connection21CheckTypeAndMergeFromERKN6google8protobuf11MessageLiteE@MIR_PROTOBUF_3
 1.7
  _ZN3mir8protobuf10Connection5ClearEv@MIR_PROTOBUF_3 1.7
  _ZN3mir8protobuf10Connection8CopyFromERKS1_@MIR_PROTOBUF_3 1.7
  _ZN3mir8protobuf10Connection9MergeFromERKS1_@MIR_PROTOBUF_3 1.7
- (arch=alpha amd64 arm64 armel armhf i386 m68k mips64el mipsel powerpc ppc64 
ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+#MISSING: 1.8.2+dfsg-4+b1# (arch=alpha amd64 arm64 armel armhf i386 m68k 
mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+ _ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaEb@MIR_PROTOBUF_3 
1.8.2+dfsg-4+b1
  _ZN3mir8protobuf10ConnectionC1ERKS1_@MIR_PROTOBUF_3 1.7
  (arch=hppa)_ZN3mir8protobuf10ConnectionC1Ev@MIR_PROTOBUF_3 1.8.0+dfsg1
- (arch=alpha amd64 arm64 armel armhf i386 m68k mips64el mipsel powerpc ppc64 
ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+#MISSING: 1.8.2+dfsg-4+b1# (arch=alpha amd64 arm64 armel armhf i386 m68k 
mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+ _ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaEb@MIR_PROTOBUF_3 
1.8.2+dfsg-4+b1
  _ZN3mir8protobuf10ConnectionC2ERKS1_@MIR_PROTOBUF_3 1.8.0+dfsg1
  (arch=hppa)_ZN3mir8protobuf10ConnectionC2Ev@MIR_PROTOBUF_3 1.8.0+dfsg1

and so on.

I presume this is related to the new version of protobuf.

Bug#1025249: marked as done (wtdbg2: flaky autopkgtest: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 17:18:27 +
with message-id 
and subject line Bug#1025249: fixed in wtdbg2 2.5-9
has caused the Debian Bug report #1025249,
regarding wtdbg2: flaky autopkgtest: Segmentation fault
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.)


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

Source: wtdbg2
Version: 2.5-7
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it 
was blocking glibc. I noticed that it regularly fails (particularly on 
ppc64el, but not exclusively there).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/stable/ppc64el/w/wtdbg2/28644876/log.gz

[Sat Nov 26 06:40:02 2022] masked 154 repeat-like nodes by local 
subgraph analysis

[Sat Nov 26 06:40:02 2022] generating edges
/tmp/autopkgtest-lxc.t8xpx53w/downtmp/build.dY0/src/debian/tests/run-unit-test: 
line 23:  1447 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg



https://ci.debian.net/data/autopkgtest/testing/ppc64el/w/wtdbg2/27771576/log.gz

[Thu Nov  3 00:50:18 2022] sorting regs ...  Done
[Thu Nov  3 00:50:19 2022] generating intervals ... 
/tmp/autopkgtest-lxc.wcfl1vkh/downtmp/build.kT7/src/debian/tests/run-unit-test: 
line 23:  1310 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg



https://ci.debian.net/data/autopkgtest/testing/arm64/w/wtdbg2/26361496/log.gz

[Fri Sep 23 22:33:59 2022] masked 154 repeat-like nodes by local 
subgraph analysis

[Fri Sep 23 22:33:59 2022] generating edges
/tmp/autopkgtest-lxc.7iunliwg/downtmp/build.Yi1/src/debian/tests/run-unit-test: 
line 23:  2686 Segmentation fault  wtdbg2 -x rs -g 4.6m -i 
pacbio_filtered.fastq -t 16 -fo dbg


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wtdbg2
Source-Version: 2.5-9
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated wtdbg2 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: Thu, 01 Dec 2022 17:13:05 +0100
Source: wtdbg2
Architecture: source
Version: 2.5-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1025249
Changes:
 wtdbg2 (2.5-9) unstable; urgency=medium
 .
   * Set  Architecture: amd64  since this seems to be the only architecture
 without autopkgtest issues
 Closes: #1025249
   * Fix download name of upstream tarball
   * Standards-Version: 4.6.1 (routine-update)
Checksums-Sha1:
 5d779923326c99b54e92342728a3b3e8013c4830 2079 wtdbg2_2.5-9.dsc
 f2ced207c5c4249c6716dddc4c1a9dd82246e0ad 121142972 wtdbg2_2.5-9.debian.tar.xz
 77f9dda4eb12187b38548eb14911a8add3ca902e 6579 wtdbg2_2.5-9_amd64.buildinfo
Checksums-Sha256:
 ff72830d288a6598d62b8d9c67ba1fcd732771de103f5b9db2f1f285495d2be3 2079 
wtdbg2_2.5-9.dsc
 6e1225be94d7596c2559599883e4a7b3041558619ce196eb8911208ea313da44 121142972 
wtdbg2_2.5-9.debian.tar.xz
 df7bf6a01a1ac3ae149bfe5277c7281a82ed91db4873acdb9e90540938fcb7c3 6579 
wtdbg2_2.5-9_amd64.buildinfo
Files:
 d040524ecbf2a3c5ce995abf64a09efc 2079 science optional wtdbg2_2.5-9.dsc
 7e6850ccdd309c072aac596c4f7f808e 121142972 science optional 
wtdbg2_2.5-9.debian.tar.xz
 6c2d5f884fea251a3728fb8122e6191a 6579 science optional 
wtdbg2_2.5-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmOI2c0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFGTw/8DiB+0oGr8

Bug#1023020: cmark-gfm: FTBFS on s390x

[Keith Packard]

Scott Talbert  writes:

> On Wed, 30 Nov 2022, Keith Packard wrote:
>
>> Scott Talbert  writes:
>>
>>> @Keith, do you have time to upload this patch?  Unfortunately, this is
>>> blocking a large number of packages from migrating to testing.
>>> Alternatively, any objections to an NMU?
>>
>> Thanks for the NMU! Did you happen to create a git repo with this
>> change? I just noticed that the salsa repo is in my private space.
>>
>>g...@salsa.debian.org:keithp/cmark-gfm.git
>
> No, I didn't, since I wasn't aware you were using a Vcs for packaging (no 
> Vcs listed in d/control).
>
> I can send you a merge request with the changes, if you'd like?

That would be great. I'll see about moving this out of my personal salsa
area and do a new upload with control pointing at the vcs.

-- 
-keith


signature.asc
Description: PGP signature

Bug#1025021: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

[Håvard F . Aasen]

> 
> ==
> ERROR: test suite for  '/usr/lib/python3/dist-packages/bayespy/tests/__init__.py'>
> --
> Traceback (most recent call last):
>File "/usr/lib/python3/dist-packages/nose/suite.py", line 209, in run
>  self.setUp()
>File "/usr/lib/python3/dist-packages/nose/suite.py", line 292, in setUp
>  self.setupContext(ancestor)
>File "/usr/lib/python3/dist-packages/nose/suite.py", line 315, in 
> setupContext
>  try_run(context, names)
>File "/usr/lib/python3/dist-packages/nose/util.py", line 453, in try_run
>  inspect.getargspec(func)
>  ^^
> AttributeError: module 'inspect' has no attribute 'getargspec'
> 
> --
> Ran 127 tests in 26.429s
> 
> FAILED (errors=1)


This looks to be an error with nose, not python-bayespy. See bug #1024235 [1]


Håvard

[1] https://bugs.debian.org/1024235

Processed: bug 994510 is forwarded to https://github.com/libunwind/libunwind/issues/69

[Debian Bug Tracking System]

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

> forwarded 994510 https://github.com/libunwind/libunwind/issues/69
Bug #994510 [libunwind8] libunwind8 abuses setcontext() causing SIGSEGV on i386 
with glibc >= 2.32
Set Bug forwarded-to-address to 
'https://github.com/libunwind/libunwind/issues/69'.
> thanks
Stopping processing here.

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

Bug#1022404: raqm: diff for NMU version 0.7.0-4.1

[Adrian Bunk]

On Fri, Nov 25, 2022 at 05:16:03AM -0600, Jeremy Bicha wrote:
> Adrian,
> 
> Do you think it would be useful to include Ubuntu's change in your NMU
> to add an autopkgtest so that these build failures are detected sooner
> next time? It would have blocked the new harfbuzz from migrating to
> Testing.

Sounds reasonable to me, but let's give the maintainer a chance to
agree or disagree to that.

> https://patches.ubuntu.com/r/raqm/raqm_0.7.0-4ubuntu1.patch

  Depends: @, @builddeps@
would be better than the duplication in Ubuntu's change.

> Thank you,
> Jeremy Bicha

cu
Adrian

Bug#1025197: marked as done (zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' object has no attribute 'tb_lasti')

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 19:38:02 +
with message-id 
and subject line Bug#1025197: fixed in zope.exceptions 4.6-1
has caused the Debian Bug report #1025197,
regarding zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' 
object has no attribute 'tb_lasti'
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.)


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

Source: zope.exceptions
Version: 4.5-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
zope.exceptionsfrom testing4.5-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/z/zope.exceptions/28796455/log.gz

=== FAILURES 
===
 
TextExceptionFormatterTests.test_formatException_recursion_in_tb_stack 


self = 
testMethod=test_formatException_recursion_in_tb_stack>


def test_formatException_recursion_in_tb_stack(self):
import traceback
fmt = self._makeOne()
err = ValueError('testing')
tb_recurse = DummyTB()
tb_recurse.tb_lineno = 27
r_f = tb_recurse.tb_frame = DummyFrame()
r_f.f_lineno = 27
r_f.f_locals['__exception_formatter__'] = 1
tb = DummyTB()
tb.tb_frame = DummyFrame()
tb.tb_next = tb_recurse

  lines = fmt.formatException(ValueError, err, tb)


/usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:347: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/zope/exceptions/exceptionformatter.py:186: 
in formatException

result.extend(traceback.format_tb(tb))
/usr/lib/python3.11/traceback.py:59: in format_tb
return extract_tb(tb, limit=limit).format()
/usr/lib/python3.11/traceback.py:74: in extract_tb
return StackSummary._extract_from_extended_frame_gen(
/usr/lib/python3.11/traceback.py:416: in _extract_from_extended_frame_gen
for f, (lineno, end_lineno, colno, end_colno) in frame_gen:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
tb = 0x7fea63c25110>


def _walk_tb_with_full_positions(tb):
# Internal version of walk_tb that yields full code positions 
including

# end line and column information.
while tb is not None:

  positions = _get_code_position(tb.tb_frame.f_code, tb.tb_lasti)

E   AttributeError: 'DummyTB' object has no attribute 'tb_lasti'

/usr/lib/python3.11/traceback.py:353: AttributeError
=== warnings summary 
===

../../../../usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:869

/usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:869: 
PytestCollectionWarning: cannot collect test class 
'TestingTracebackSupplement' because it has a __init__ constructor 
(from: tests/test_exceptionformatter.py)

class TestingTracebackSupplement(object):

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 

FAILED 
tests/test_exceptionformatter.py::TextExceptionFormatterTests::test_formatException_recursion_in_tb_stack
=== 1 failed, 79 passed, 1 warning in 0.18s 


autopkgtest [0

Bug#1000653: Fix php-mail build

[Athos Ribeiro]

On Wed, Nov 30, 2022 at 05:11:15PM +0100, Christoph Martin wrote:

Hi

I have uploaded a fixed package as NMU to the deferred queue.

Am 17.11.22 um 13:55 schrieb Christoph Martin:


do you plan to release a new version with the proposed fix anytime soon?
I build it locally with the fix and it builds fine.
I could upload the package if this is ok for you.



Christoph


Thanks, Christoph.

FYI, I had forwarded the fix upstream at
https://github.com/pear/Mail/pull/21. They requested the change to be
backwards compatible. I did so by supporting backwards compatibility
when on PHP < 8.

--
Athos Ribeiro

Bug#1025021: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

[Paul Gevers]

Control: reassign -1 python3-nose
Control: tags -1 ftbfs patch pending upstream
Control: tags -1 - bookworm sid
Control: merge 1024235 -1
Control: affects -1 src:python-bayespy

Hi Håvard,

On 01-12-2022 19:16, Håvard F. Aasen wrote:

File "/usr/lib/python3/dist-packages/nose/util.py", line 453, in try_run
  inspect.getargspec(func)
  ^^
AttributeError: module 'inspect' has no attribute 'getargspec'



This looks to be an error with nose, not python-bayespy. See bug #1024235 [1]


Indeed, reassigning (and merging hopefully).

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed (with 1 error): Re: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-nose
Bug #1025021 [src:python-bayespy] python-bayespy: (autopkgtest) needs update 
for python3.11: module 'inspect' has no attribute 'getargspec'
Bug reassigned from package 'src:python-bayespy' to 'python3-nose'.
No longer marked as found in versions python-bayespy/0.5.22-2.
Ignoring request to alter fixed versions of bug #1025021 to the same values 
previously set
> tags -1 ftbfs patch pending upstream
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Added tag(s) ftbfs, patch, upstream, and pending.
> tags -1 - bookworm sid
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Removed tag(s) bookworm and sid.
> merge 1024235 -1
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Unable to merge bugs because:
affects of #1025021 is 'src:python3-defaults' not ''
Failed to merge 1024235: Did not alter merged bugs.

> affects -1 src:python-bayespy
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Added indication that 1025021 affects src:python-bayespy

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

Processed: Bug#1025192 marked as pending in sublime-music

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025192 [src:sublime-music] sublime-music: (autopkgtest) needs update for 
python3.11: mutable default for field current_album_search_query is not allowed
Added tag(s) pending.

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

Bug#1025192: marked as pending in sublime-music

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1025192 in sublime-music 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/sublime-music/-/commit/139847707ac6cca516a1869e0700dbdec6fcb5be


d/patches: add 0004 to fix Python 3.11 issue. (Closes: #1025192)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025192

Processed (with 1 error): Re: Processed (with 1 error): Re: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

[Debian Bug Tracking System]

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

> # let's try the merge again
> affects 1024235 src:python3-default src:python-bayespy
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Added indication that 1024235 affects src:python3-default and src:python-bayespy
> merge 1024235 1025021
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Unable to merge bugs because:
affects of #1025021 is 'src:python-bayespy,src:python3-defaults' not 
'src:python-bayespy,src:python3-default'
Failed to merge 1024235: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Processed (with 1 error): Re: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

[Debian Bug Tracking System]

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

> # three is a charm
> affects 1024235 - src:python3-default
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Removed indication that 1024235 affects src:python3-default
> affects 1024235 src:python3-defaults
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Added indication that 1024235 affects src:python3-defaults
> merge 1024235 1025021
Bug #1024235 [python3-nose] python3-nose: nose doesn't work with Python 3.11 
due to use of removed inspect.getargspec()
Unable to merge bugs because:
affects of #1025021 is 'src:python-bayespy,src:python3-defaults' not 
'src:python3-defaults,src:python-bayespy'
Failed to merge 1024235: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: libfcft-dev: Missing dependencies

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:fuzzel src:foot src:yambar
Bug #1025275 [libfcft-dev] libfcft-dev: Missing dependencies
Added indication that 1025275 affects src:fuzzel, src:foot, and src:yambar

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

Bug#1024957: marked as done (metalfinder: (autopkgtest) needs update for python3.11: DID NOT RAISE )

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 20:49:10 +
with message-id 
and subject line Bug#1024957: fixed in metalfinder 2.1.6-1
has caused the Debian Bug report #1024957,
regarding metalfinder: (autopkgtest) needs update for python3.11: DID NOT RAISE 

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


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

Source: metalfinder
Version: 2.1.5-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
metalfinderfrom testing2.1.5-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/m/metalfinder/28726285/log.gz

=== FAILURES 
===
_ test_date_lint_not_iso_8601 
__


def test_date_lint_not_iso_8601():
"""Test date_lint() errors when input is not ISO 8601"""

  with pytest.raises(SystemExit):

E   Failed: DID NOT RAISE 

tests/test_cli.py:47: Failed


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: metalfinder
Source-Version: 2.1.6-1
Done: Louis-Philippe Véronneau 

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated metalfinder 
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: Thu, 01 Dec 2022 15:26:02 -0500
Source: metalfinder
Architecture: source
Version: 2.1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Louis-Philippe Véronneau 
Closes: 1024957
Changes:
 metalfinder (2.1.6-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #1024957)
   * d/patches: remove 0001, as it has been upstreamed.
Checksums-Sha1:
 46e50121219917cf315babf7278691cf1a3be391 1594 metalfinder_2.1.6-1.dsc
 0bb911329fb4363f648bfc6ac64c30f672a363f5 25308 metalfinder_2.1.6.orig.tar.xz
 f1764284f8cc406391eb6dc79920cf599865556a 3528 metalfinder_2.1.6-1.debian.tar.xz
 964a2ba47d6f865e7f3592ad35518dc5602ae70e 7497 
metalfinder_2.1.6-1_amd64.buildinfo
Checksums-Sha256:
 316472d8a7181cecfd0705cf363c58f1be5249486e92f4c26fe9872c47a9d38f 1594 
metalfinder_2.1.6-1.dsc
 e14297293642a982f563ecc2fbfca24052684950dbc61fca3446bfeb9fdc5a21 25308 
metalfinder_2.1.6.orig.tar.xz
 b5334ae7f051a4d09891c9ad2a279cc303d1022a86a7a71ef9967f6cddfd87d7 3528 
metalfinder_2.1.6-1.debian.tar.xz
 5e9c1e2500c27b379890baafead473d5dcd81e07049f26e12f69be68f3b9cc14 7497 
metalfinder_2.1.6-1_amd64.buildinfo
Files:
 470f7b30de755a0b454dd14be73e8433 1594 sound optional metalfinder_2.1.6-1.dsc
 79873828bf710d4d734f42ea0a9e0120 25308 sound optional 
metalfinder_2.1.6.orig.tar.xz
 1be7b9f099e3f7e2164fd7156b3d029f 3528 sound optional 
metalfinder_2.1.6-1.debian.tar.xz
 ee31fb57a9c

Bug#1025275: libfcft-dev: Missing dependencies

[Adrian Bunk]

Package: libfcft-dev
Version: 2.3.1-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:fuzzel src:foot src:yambar

$ pkg-config --cflags fcft
Package fontconfig was not found in the pkg-config search path.
Perhaps you should add the directory containing `fontconfig.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fontconfig', required by 'fcft', not found
Package 'freetype2', required by 'fcft', not found
Package 'harfbuzz', required by 'fcft', not found
Package 'libutf8proc', required by 'fcft', not found
Package 'pixman-1', required by 'fcft', not found
Package 'tllist', required by 'fcft', not found

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/fcft.pc
...
Requires.private: fontconfig, freetype2, harfbuzz, libutf8proc, pixman-1, 
tllist >= 1.0.1
...
$



These dependencies are an implementation detail of libfcft-dev
that must be expressed in the package dependencies, not something
every user has to copy and update all the time (like when libutf8proc
usage was enabled in fcft).

As of 3.1.5-2 the missing dependencies are:
 libpixman-1-dev, libfreetype6-dev, libfontconfig-dev,
 libtllist-dev, libharfbuzz-dev, libutf8proc-dev

Adding the dependencies to libfcft-dev fixes this bug.


Only pixman.h is used in the headers in libfcft-dev,
an alternative fix would be to add only a dependency
on libpixman-1-dev and reduce Requires.private in fcft.pc to:
  Requires.private: pixman-1

Bug#1025192: marked as done (sublime-music: (autopkgtest) needs update for python3.11: mutable default for field current_album_search_query is not allowed)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 20:54:00 +
with message-id 
and subject line Bug#1025192: fixed in sublime-music 0.11.16-4
has caused the Debian Bug report #1025192,
regarding sublime-music: (autopkgtest) needs update for python3.11: mutable 
default for field current_album_search_query is not allowed
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.)


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

Source: sublime-music
Version: 0.11.16-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
sublime-music  from testing0.11.16-3
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sublime-music/28796444/log.gz

=== python3.11 ===
= test session starts 
==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- 
/usr/bin/python3.11

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.1ezw684c/downtmp/autopkgtest_tmp, 
configfile: setup.cfg

collecting ... collected 0 items / 12 errors

 ERRORS 

 ERROR collecting tests/config_test.py 
_

tests/config_test.py:6: in 
from sublime_music.adapters import ConfigurationStore
/usr/lib/python3/dist-packages/sublime_music/adapters/__init__.py:11: in 

from .manager import AdapterManager, DownloadProgress, Result, 
SearchResult
/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py:33: in 


from sublime_music.config import ProviderConfiguration
/usr/lib/python3/dist-packages/sublime_music/config.py:12: in 
from .ui.state import UIState
/usr/lib/python3/dist-packages/sublime_music/ui/state.py:41: in 
@dataclass
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
/usr/lib/python3.11/dataclasses.py:815: in _get_field
raise ValueError(f'mutable default {type(f.default)} for field '
E   ValueError: mutable default 'sublime_music.adapters.adapter_base.AlbumSearchQuery'> for field 
current_album_search_query is not allowed: use default_factory
 ERROR collecting tests/config_test.py 
_

tests/config_test.py:6: in 
from sublime_music.adapters import ConfigurationStore
/usr/lib/python3/dist-packages/sublime_music/adapters/__init__.py:11: in 

from .manager import AdapterManager, DownloadProgress, Result, 
SearchResult
/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py:33: in 


from sublime_music.config import ProviderConfiguration
/usr/lib/python3/dist-packages/sublime_music/config.py:12: in 
from .ui.state import UIState
/usr/lib/python3/dist-packages/sublime_music/ui/state.py:41: in 
@dataclass
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
/usr/lib/python3.11/dataclasses.py:815: in _get_field
raise ValueError(f'mut

Processed: deepdiff: forward 1024907

[Debian Bug Tracking System]

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

> forwarded 1024907 https://github.com/seperman/deepdiff/issues/358
Bug #1024907 [src:deepdiff] deepdiff: (autopkgtest) needs update for 
python3.11: AssertionError
Set Bug forwarded-to-address to 
'https://github.com/seperman/deepdiff/issues/358'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1023355 src:limereg
Bug #1023355 [limereg] limereg: depends on non-existing 
libboost-program-options1.67.0
Bug reassigned from package 'limereg' to 'src:limereg'.
No longer marked as found in versions limereg/1.4.1-4.
Ignoring request to alter fixed versions of bug #1023355 to the same values 
previously set
> forcemerge 922584 1023355
Bug #922584 [src:limereg] FTBFS against opencv 4.0.1 (exp)
Bug #1023355 [src:limereg] limereg: depends on non-existing 
libboost-program-options1.67.0
Failed to forcibly merge 922584: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> affects 922584 limereg
Bug #922584 [src:limereg] FTBFS against opencv 4.0.1 (exp)
Added indication that 922584 affects limereg
> thanks
Stopping processing here.

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

Bug#1024907: deepdiff: (autopkgtest) needs update for python3.11: AssertionError

[Louis-Philippe Véronneau]

found 1024907 6.2.1
thanks

Note that I've updated this package to the latest upstream version 
(6.2.1) on Salsa and the problem is still there.


--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024953: jsonpickle: (autopkgtest) needs update for python3.11: 'NoneType' object has no attribute 'keys'

[Louis-Philippe Véronneau]

fixed 1024953 3.0.0
tags 1024953 fixed-upstream
thanks

Hi!

Note that this bug has been fixed upstream, but haven't been released in 
a git tag yet.


I think the changes are too substantial (major version) to patch the 
issue in Debian via quilt.


I asked the upstream maintainer to make a release here: 
https://github.com/jsonpickle/jsonpickle/issues/416


Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Processed: jsonpickle: (autopkgtest) needs update for python3.11: 'NoneType' object has no attribute 'keys'

[Debian Bug Tracking System]

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

> fixed 1024953 3.0.0
Bug #1024953 [src:jsonpickle] jsonpickle: (autopkgtest) needs update for 
python3.11: 'NoneType' object has no attribute 'keys'
The source 'jsonpickle' and version '3.0.0' do not appear to match any binary 
packages
Marked as fixed in versions jsonpickle/3.0.0.
> tags 1024953 fixed-upstream
Bug #1024953 [src:jsonpickle] jsonpickle: (autopkgtest) needs update for 
python3.11: 'NoneType' object has no attribute 'keys'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 915721
Bug #915721 {Done: Paul Gevers } [release.debian.org] 
transition: opencv
Unarchived Bug 915721
> forcemerge 922584 1023355
Bug #922584 [src:limereg] FTBFS against opencv 4.0.1 (exp)
Bug #1023355 [src:limereg] limereg: depends on non-existing 
libboost-program-options1.67.0
915721 was blocked by: 922569 922582 922578 922574 922583 922591 922596 922593 
922586 922579 922592 922570 922600 922597 922573 922584 922599 915708 915712 
922566 922595 922590 922588 943603 922585 922587 922589 915711 943602
915721 was not blocking any bugs.
Added blocking bug(s) of 915721: 1023355
Added indication that 1023355 affects limereg
Marked as found in versions limereg/1.4.1-4.
Added tag(s) ftbfs, bullseye, and help.
Merged 922584 1023355
> thanks
Stopping processing here.

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

Processed: Re: deepdiff: (autopkgtest) needs update for python3.11: AssertionError

[Debian Bug Tracking System]

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

> found 1024907 6.2.1
Bug #1024907 [src:deepdiff] deepdiff: (autopkgtest) needs update for 
python3.11: AssertionError
The source 'deepdiff' and version '6.2.1' do not appear to match any binary 
packages
Marked as found in versions deepdiff/6.2.1.
> thanks
Stopping processing here.

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

Bug#1024395: grub-efi-amd64-signed: update

[Garrett McLean]

Package: grub-efi-amd64-bin
Version: 1+2.06+3~deb11u4
Followup-For: Bug #1024395
X-Debbugs-Cc: t...@security.debian.org

Wanted to update and say that even with sb enabled, mok doesn't show up
with mokutil --list-enrolled. In my case this may be because mokutil
doesn't work with my mobo (ASUS X99-Deluxe/U3.1) and I had to manually
add my mok in BIOS settings.

Hopefully this info is useful. It seems superfluous but I'm including it
just in case.

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

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

Versions of packages grub-efi-amd64-signed depends on:
ii  grub-common  2.06-3~deb11u4

Versions of packages grub-efi-amd64-signed recommends:
ii  shim-signed  1.38+15.4-7

grub-efi-amd64-signed suggests no packages.

Versions of packages grub-efi-amd64-bin depends on:
ii  grub-common  2.06-3~deb11u4

Versions of packages grub-efi-amd64-bin recommends:
ii  efibootmgr  17-1

-- no debconf information

Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

[Adrian Bunk]

On Mon, Nov 23, 2020 at 05:49:42PM +0100, Andreas Tille wrote:
> Control: tags -1 help
> 
> Hi,
> 
> the configure step checks for the existence of opencv and only if
> available builds the executable limereg.  I found a (hackish) solution
> in Git[1] to convince configure that opencv is available.  However, the
> code tries to include cv.h which is not available any more.  I have no
> knowledge about opencv and thus I have no idea to proceed.  My only idea
> is to drop the limereg binary package and just keep the liblimereg
> packages alive.
> 
> Any help is welcome

[1] contains a patch from a Debian porter, but considering the facts 
that limereg already missed the current Debian stable bullseye and the 
comment from upstream (who is also the original Debian packager) in [2], 
removal from Debian might be a better option?

I do not know how limereg compares to other tools like for example
elastix (based on ITK) or registrationx (part of CMTK) or other tools,
but neither the upstream bug tracker nor the Debian BTS indicate that
there would be an active userbase who report bugs or complained that
limereg is not in bullseye.

>Andreas.
>...

cu
Adrian

[1] https://github.com/RoelofBerg/limereg/issues/3
[2] https://github.com/RoelofBerg/limereg/issues/3#issuecomment-1296863979

Bug#1024807: marked as done (haskell-unicode-data: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 21:50:03 +
with message-id 
and subject line Bug#1024807: fixed in haskell-unicode-data 0.3.1-2
has caused the Debian Bug report #1024807,
regarding haskell-unicode-data: FTBFS on s390x
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=haskell-unicode-data&arch=s390x&ver=0.3.1-1&stamp=1666442604&raw=0

Failures:

  test/Unicode/CharSpec.hs:65:30: 
  1) Unicode.Char, Unicode blocks, Characters are in the definition of their 
corresponding block
   Character “'\128'” is not in the block “BasicLatin”.

  To rerun use: --match "/Unicode.Char/Unicode blocks/Characters are in the 
definition of their corresponding block/"

  test/Unicode/CharSpec.hs:75:22: 
  2) Unicode.Char, Unicode blocks, Characters in a block definition have the 
corresponding block
   Block is different for “'\128'”. Expected: “Just Latin1Supplement” but 
got: “Just BasicLatin”.

  To rerun use: --match "/Unicode.Char/Unicode blocks/Characters in a block 
definition have the corresponding block/"

Randomized with seed 1895901257

Finished in 0.3339 seconds
31 examples, 2 failures, 20 pending
Test suite test: FAIL
Test suite logged to: dist-ghc/test/unicode-data-0.3.1-test.log
0 of 1 test suites (0 of 1 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct 
returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 854.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test 
--builddir=dist-ghc --show-details"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 598
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test 
--builddir=dist-ghc --show-details"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 472
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test", 
"--builddir=dist-ghc", "--show-details=direct") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 686
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: haskell-unicode-data
Source-Version: 0.3.1-2
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated haskell-unicode-data 
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: Thu, 01 Dec 2022 16:23:19 -0500
Source: haskell-unicode-data
Architecture: source
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Scott Talbert 
Closes: 1024807
Changes:
 haskell-unicode-data (0.3.1-2) unstable; urgency=medium
 .
   * Fix FTBFS on s390x (Closes: #1024807)
Checksums-Sha1:
 a0044a92059cbc39aae61ff5cac23da6f21bb8e5 2449 haskell-unicode-data_0.3.1-2.dsc
 4f08f12e4794702c304599e3dafe96d5f3e62298 3300 
haskell-unicode-data_0.3.1-2.debian.tar.xz
 f1e7256861e866e52b915a6dea81b09f8b6252dc 9812 
haskell-unicode-data_0.3.1-2_amd64.buildinfo
Checksums-Sha256:
 276d67aef8d6aa7fc582409808be0ff5a7f4ae5c8a662ea5f17a944389425c96 2449 
haskell-unicode-data_0.3.1-2.dsc
 7da4c5aec0b0a443b5c6f35322d03380225fca0fb79567f094ac7f7c76c29d9a 3300 
haskell-unicode-data_0.3.1-2.debian.tar.xz
 57624446163b4cc82181be0d070f1d118b2640772f7859a7dd4328ae8610cfef 9812 
haskell-unicode-data_0.3.1-2_amd64.buildinfo
Files:
 eb6bed0439e927dbf44dc78c252dfb50 2449 haskell optional 
haskell-unicode-data_0.3.1-2.dsc
 b

Bug#1025275: marked as done (libfcft-dev: Missing dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 21:49:35 +
with message-id 
and subject line Bug#1025275: fixed in fcft 3.1.5-3
has caused the Debian Bug report #1025275,
regarding libfcft-dev: Missing dependencies
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.)


-- 
1025275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfcft-dev
Version: 2.3.1-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:fuzzel src:foot src:yambar

$ pkg-config --cflags fcft
Package fontconfig was not found in the pkg-config search path.
Perhaps you should add the directory containing `fontconfig.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fontconfig', required by 'fcft', not found
Package 'freetype2', required by 'fcft', not found
Package 'harfbuzz', required by 'fcft', not found
Package 'libutf8proc', required by 'fcft', not found
Package 'pixman-1', required by 'fcft', not found
Package 'tllist', required by 'fcft', not found

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/fcft.pc
...
Requires.private: fontconfig, freetype2, harfbuzz, libutf8proc, pixman-1, 
tllist >= 1.0.1
...
$



These dependencies are an implementation detail of libfcft-dev
that must be expressed in the package dependencies, not something
every user has to copy and update all the time (like when libutf8proc
usage was enabled in fcft).

As of 3.1.5-2 the missing dependencies are:
 libpixman-1-dev, libfreetype6-dev, libfontconfig-dev,
 libtllist-dev, libharfbuzz-dev, libutf8proc-dev

Adding the dependencies to libfcft-dev fixes this bug.


Only pixman.h is used in the headers in libfcft-dev,
an alternative fix would be to add only a dependency
on libpixman-1-dev and reduce Requires.private in fcft.pc to:
  Requires.private: pixman-1
--- End Message ---
--- Begin Message ---
Source: fcft
Source-Version: 3.1.5-3
Done: Birger Schacht 

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

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated fcft 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: Thu, 01 Dec 2022 22:03:33 +0100
Source: fcft
Architecture: source
Version: 3.1.5-3
Distribution: unstable
Urgency: medium
Maintainer: Birger Schacht 
Changed-By: Birger Schacht 
Closes: 1025275
Changes:
 fcft (3.1.5-3) unstable; urgency=medium
 .
   * Add missing dependencies to libfcft-dev (Closes: #1025275)
Checksums-Sha1:
 967be047fbfaa1a1158592f24fc0ace009c52cce 2077 fcft_3.1.5-3.dsc
 34a5d0c047d91923a7ea20ccf563278e4d7b5ac9 4980 fcft_3.1.5-3.debian.tar.xz
 da86a0b7d55d9d29843f327cd86181af50987ea0 9567 fcft_3.1.5-3_amd64.buildinfo
Checksums-Sha256:
 052dc54dce1e5cca6fa79f398ff9a63fcf75940d0c0b35643771c2bb249e2cad 2077 
fcft_3.1.5-3.dsc
 76719f1b981ca3acb5148b2a0036d6a9b8bf707168c742102fa9c68b835efc3c 4980 
fcft_3.1.5-3.debian.tar.xz
 ec90fdab3b0bc530c6c314ded01ab0adb0823bd6b81ce62f705a57c4f92b723c 9567 
fcft_3.1.5-3_amd64.buildinfo
Files:
 e5d3ff93a065e55dd79fb5f30a5f1302 2077 libdevel optional fcft_3.1.5-3.dsc
 84a32bb0e92739004150cf39241c940c 4980 libdevel optional 
fcft_3.1.5-3.debian.tar.xz
 83d9a11546a1e57803f73f40264df1cc 9567 libdevel optional 
fcft_3.1.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAmOJGE4SHGJpcmdlckBk
ZWJpYW4ub3JnAAoJECoMXWDyBL2wxzoP/0rA9hgxj1P52WbCHuahQ8alKauwGYAw
dZypyPtxwCIyOCVpZNNZMBvWBg9SHY4MN7SQZ7kGnPq/FepDG7oyFE9sq6B75s97
tZcbj7NwNSHbvcNxzKlYijmeiFUM8m6dpNtGotlBG3lg6Mths7iEPGR5Al0v17R5
XNWIAbCwkpvB1wSr8p9Amzod/9AC/hGgJgEueeK6G4ODupyIJCRf1rr0EX/cBhWt
gd7DLjkQsJd6vlBQnSSlnSGWL8PGGhEUPy4b+NZb2TYlDKuXMTudqedUEYPRugl8
aK2t7ckuhswyzxm+Sd3rSqiRgkqDYg+y/hDO+K8SUhXZlj655ANDk+iS2G9/UUL3
UD8rNavIhxziE4jojmTLO5i946EdjeWGAjrQWdn32E25C/+4EzJ/qKJJqhDSeucj
36xNgoJ5zCBc4I7lUH/cZC2iG6qZtg78yFBllbYnLOrqHI6KNkFSaKDdA9ZWvTXb
eBk6Fgdi/mlCNVqoNE6aCQCq/UgszlKRK1dLabaRdApz79/QDZowfr8mzg8pHv4R
YbAPkQ3ht1lVYwdr3enV5xqww2Pm2xZfLucLuVPutHFzoqr+BC3YH094zUxt8Y9E
I/NkqaWUtl2wTIpTq3bGoH3szSLXs4t36WCA/TZSLmXevaKOQYQvvViuUiz9vMCQ
nZ

Bug#1025108: marked as done (python-marshmallow-dataclass: (autopkgtest) needs update for python3.11: ValueError: mutable default for field data is not allowed)

[Debian Bug Tracking System]

Your message dated Thu, 01 Dec 2022 21:53:08 +
with message-id 
and subject line Bug#1025108: fixed in python-marshmallow-dataclass 8.5.10-1
has caused the Debian Bug report #1025108,
regarding python-marshmallow-dataclass: (autopkgtest) needs update for 
python3.11: ValueError: mutable default for field data is not allowed
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.)


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

Source: python-marshmallow-dataclass
Version: 8.5.8-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-marshmallow-dataclass from testing8.5.8-3
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-marshmallow-dataclass/28750374/log.gz

=== FAILURES 
===
_ TestClassSchema.test_final_infers_type_from_default 
__


self = testMethod=test_final_infers_type_from_default>


def test_final_infers_type_from_default(self):
# @dataclasses.dataclass
class A:
data: Final = "a"
# @dataclasses.dataclass
class B:
data: Final = A()
# NOTE: This workaround is needed to avoid a Mypy crash.
# See: 
https://github.com/python/mypy/issues/10090#issuecomment-865971891

if not TYPE_CHECKING:
A = dataclasses.dataclass(A)

  B = dataclasses.dataclass(B)


tests/test_class_schema.py:242: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.11/dataclasses.py:1220: in dataclass

return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
cls = 'tests.test_class_schema.TestClassSchema.test_final_infers_type_from_default..B'>

a_name = 'data', a_type = typing.Final, default_kw_only = False

def _get_field(cls, a_name, a_type, default_kw_only):
# Return a Field object for this field name and type. 
ClassVars and
# InitVars are also returned, but marked as such (see 
f._field_type).
# default_kw_only is the value of kw_only to use if there isn't 
a field()

# that defines it.
# If the default value isn't derived from Field, then it's 
only a

# normal default value.  Convert it to a Field().
default = getattr(cls, a_name, MISSING)
if isinstance(default, Field):
f = default
else:
if isinstance(default, types.MemberDescriptorType):
# This is a field in __slots__, so it has no default value.
default = MISSING
f = field(default=default)
# Only at this point do we know the name and the type.  Set 
them.

f.name = a_name
f.type = a_type
# Assume it's a normal field until proven otherwise.  We're 
next

# going to decide if it's a ClassVar or InitVar, everything else
# is just a normal field.
f._field_type = _FIELD
# In addition to checking for actual types here, also check for
# string annotations.  get_typ

Processed: python-pauvre ftbfs now serious

[Debian Bug Tracking System]

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

> # The issue became serious since biopython 1.80 reached sid (and even testing)
> severity 1024835 serious
Bug #1024835 [src:python-pauvre] python-pauvre: ftbfs with biopython 1.80
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#1025279: nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CV

[Andreas Beckmann]

Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1

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

CVE-2022-34670  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an unprivileged
regular user can cause truncation errors when casting a primitive to a
primitive of smaller size causes data to be lost in the conversion,
which may lead to denial of service or information disclosure.

CVE-2022-42263  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an Integer
overflow may lead to denial of service or information disclosure.

CVE-2022-34676  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an out-of-bounds
read may lead to denial of service, information disclosure, or data
tampering.

CVE-2022-42264  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged regular
user can cause the use of an out-of-range pointer offset, which may lead
to data tampering, data loss, information disclosure, or denial of
service.

CVE-2022-34674  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where a helper function
maps more physical pages than were requested, which may lead to
undefined behavior or an information leak.

CVE-2022-34678  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where an unprivileged user can
cause a null-pointer dereference, which may lead to denial of s

Processed: nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Bug #1025279 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: 
CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, 
CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, 
CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, 
CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Bug 1025279 cloned as bugs 1025280-1025287
> reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Bug #1025280 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: 
CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, 
CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, 
CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, 
CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Bug reassigned from package 'src:nvidia-graphics-drivers' to 
'src:nvidia-graphics-drivers-legacy-340xx'.
Ignoring request to alter found versions of bug #1025280 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1025280 to the same values 
previously set
Bug #1025280 [src:nvidia-graphics-drivers-legacy-340xx] 
nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, 
CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, 
CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.76-6.
> retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
> CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, 
> CVE-2022-42257, CVE-2022-42258, CVE-2022-42259
Bug #1025280 [src:nvidia-graphics-drivers-legacy-340xx] 
nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, 
CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, 
CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Changed Bug title to 'nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259' from 'nvidia-graphics-drivers: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264'.
> tag -2 + wontfix
Bug #1025280 [src:nvidia-graphics-drivers-legacy-340xx] 
nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, 
CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259
Added tag(s) wontfix.
> reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Bug #1025281 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: 
CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, 
CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, 
CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, 
CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Bug reassigned from package 'src:nvidia-graphics-drivers' to 
'src:nvidia-graphics-drivers-legacy-390xx'.
Ignoring request to alter found versions of bug #1025281 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1025281 to the same values 
previously set
Bug #1025281 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, 
CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, 
CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Marked as found in versions nvidia-graphics-drivers-legacy-390xx/390.48-4.
> retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
> CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, 
> CVE-2022-42257, CVE-2022-42258, CVE-2022-42259
Bug #1025281 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, 
CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, 
CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Changed Bug title to 'nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259'

Bug#1025261: marked as pending in vagrant

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #1025261 in vagrant 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/ruby-team/vagrant/-/commit/f89c5d4283f370fda5c2564221812ac1ef058317


Don't force an upper bound on Ruby versions

Closes: #1025261


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025261

Processed: Bug#1025261 marked as pending in vagrant

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025261 [vagrant] vagrant: Broken with ruby3.1
Added tag(s) pending.

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

Bug#1025261: marked as done (vagrant: Broken with ruby3.1)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 00:06:04 +
with message-id 
and subject line Bug#1025261: fixed in vagrant 2.2.19+dfsg-2
has caused the Debian Bug report #1025261,
regarding vagrant: Broken with ruby3.1
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.)


-- 
1025261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vagrant
Version: 2.2.19+dfsg-1
Severity: serious

Hi!

After the upgrade of ruby to the 3.1 version vagrant has stopped
working completely, I'm getting the following errors repeated multiple
times:

,---
/usr/lib/ruby/vendor_ruby/rubygems/resolver/conflict.rb:47:in 
`conflicting_dependencies': undefined method `request' for nil:NilClass 
(NoMethodError)

[@failed_dep.dependency, @activated.request.dependency]
   
from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:61:in 
`conflicting_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:55:in `initialize'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `exception'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `raise'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `rescue in 
resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:191:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in 
`resolve_current'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in 
activate_bin_path'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
from /usr/bin/vagrant:25:in `'
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:317:in
 `raise_error_unless_state': Unable to satisfy the following requirements: 
(Gem::Resolver::Molinillo::VersionConflict)

- `vagrant (= 2.2.19)` required by `user-specified dependency`
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:299:in
 `block in unwind_for_conflict'
from :90:in `tap'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:297:in
 `unwind_for_conflict'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:682:in
 `attempt_to_activate'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:254:in
 `process_topmost_state'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:182:in
 `resolve'
from 
/usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:43:in
 `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:190:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve'
from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in 
`resolve_current'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in 
activate_bin_path'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
from /usr/bin/vagrant:25:in `'
`---

Installing ruby3.0 and forcing the «/usr/bin/ruby» symlink back to
ruby3.0 make vagrant work again.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.2.19+dfsg-2
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated vagrant package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Dec 2022 16:25:04 -0300
Source: vagrant
Ar

Processed: Re: grep: inconsistent behaviour with anchored regex containing back-references

[Debian Bug Tracking System]

Processing control commands:

> found 930247 3.8-3
Bug #930247 [grep] grep: inconsistent behaviour with anchored regex containing 
back-references
Marked as found in versions grep/3.8-3.
> severity 930247 serious
Bug #930247 [grep] grep: inconsistent behaviour with anchored regex containing 
back-references
Severity set to 'serious' from 'normal'
> retitle 930247 grep: does not handle backreferences correctly, violating POSIX
Bug #930247 [grep] grep: inconsistent behaviour with anchored regex containing 
back-references
Changed Bug title to 'grep: does not handle backreferences correctly, violating 
POSIX' from 'grep: inconsistent behaviour with anchored regex containing 
back-references'.

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

Bug#1013365: marked as done (python-aiortc: autopkgtest regression on armhf: [Errno 542398533] Generic error in an external library)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 02:21:42 +0100
with message-id <166994410270.1178998.2231665922287168...@auryn.jones.dk>
and subject line Re: Bug#1013365: python-aiortc: autopkgtest regression on 
armhf: [Errno 542398533] Generic error in an external library
has caused the Debian Bug report #1013365,
regarding python-aiortc: autopkgtest regression on armhf: [Errno 542398533] 
Generic error in an external library
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.)


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

Source: python-aiortc
Version: 1.3.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python-aiortc  from testing1.3.2-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=python-aiortc

https://ci.debian.net/data/autopkgtest/testing/armhf/p/python-aiortc/22926423/log.gz

=== FAILURES 
===
_ MediaRecorderTest.test_video_mp4_uhd 
_


self = testMethod=test_video_mp4_uhd>


@asynctest
async def test_video_mp4_uhd(self):
path = self.temporary_path("test.mp4")
recorder = MediaRecorder(path)
recorder.addTrack(VideoStreamTrackUhd())
await recorder.start()
await asyncio.sleep(2)

  await recorder.stop()


tests/test_contrib_media.py:651: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/aiortc/contrib/media.py:383: in stop

for packet in context.stream.encode(None):
av/stream.pyx:164: in av.stream.Stream.encode
???
av/codec/context.pyx:492: in av.codec.context.CodecContext.encode
???
av/codec/context.pyx:411: in 
av.codec.context.CodecContext._send_frame_and_recv

???
av/codec/context.pyx:469: in av.codec.context.CodecContext._recv_packet
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???
E   av.error.ExternalError: [Errno 542398533] Generic error in an 
external library


av/error.pyx:336: ExternalError
- Captured stderr call 
-

[libx264 @ 0x1425410] using cpu capabilities: ARMv6 NEON
[libx264 @ 0x1425410] profile High, level 5.1, 4:2:0, 8-bit
[libx264 @ 0x1425410] 264 - core 164 r3095 baee400 - H.264/MPEG-4 AVC 
codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html - 
options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 
psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 
8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 
threads=33 lookahead_threads=16 sliced_threads=1 slices=33 nr=0 
decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 
b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 
keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 
rc=abr mbtree=1 bitrate=1024 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 
qpstep=4 ip_ratio=1.40 aq=1:1.00

x264 [error]: malloc of size 26198688 failed
x264 [error]: malloc of size 43687792 failed
 H264Test.test_encoder 
_


self = 
frame = 
force_keyframe = False

def _encode_frame(
self, frame: av.VideoFrame, force_keyframe: bool
) -> Iterator[bytes]:
if self.codec and (
frame.width != self.codec.width
or frame.height != self.codec.height
# we only adjust bitrate if it changes by over 10%
or abs(self.target_bitrate - self.codec.bit_rate) / 
self.codec.bit_rate

> 0.1
):
self.buffer_data = b""
self.buffer_pts = None
self.codec = None
# reset the picture type, otherwise no B-frames are produced
frame.pict_type 

Bug#1025214: was: regression: dkms/3.0.8-2 renders zfs-dkms FTBFS

[M. Zhou]

Control: merge 1025214 1025171

The "MAKEFLAGS="--environment-overrides" also caused zfs-dkms FTBFS.
The two bugs above are the same issue, hence the merge.

Processed (with 1 error): was: regression: dkms/3.0.8-2 renders zfs-dkms FTBFS

[Debian Bug Tracking System]

Processing control commands:

> merge 1025214 1025171
Bug #1025214 [dkms] dkms: --environment-overrides causes several module build 
failures
Unable to merge bugs because:
severity of #1025171 is 'serious' not 'grave'
Failed to merge 1025214: Did not alter merged bugs.


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

Bug#1025229: marked as done (mksh: flaky autopkgtest on several architectures)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 03:04:44 +
with message-id 
and subject line Bug#1025229: fixed in mksh 59c-20
has caused the Debian Bug report #1025229,
regarding mksh: flaky autopkgtest on several architectures
to be marked as done.

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

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


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

Source: mksh
Version: 59c-19
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. Also the failures on arm64 seem consistent now 
in testing (but it has a pass in unstable).


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mksh/28332115/log.gz

E: static-musl: regress did not pass

https://ci.debian.net/data/autopkgtest/testing/arm64/m/mksh/28784302/log.gz

E: full: regress did not pass

https://ci.debian.net/data/autopkgtest/testing/armhf/m/mksh/26990327/log.gz

E: static-dietlibc: regress did not pass


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mksh
Source-Version: 59c-20
Done: Thorsten Glaser 

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

Debian distribution maintenance software
pp.
Thorsten Glaser  (supplier of updated mksh 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: SHA384

Format: 1.8
Date: Fri, 02 Dec 2022 02:49:39 +0100
Source: mksh
Architecture: source
Version: 59c-20
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser 
Changed-By: Thorsten Glaser 
Closes: 1021085 1025229
Changes:
 mksh (59c-20) unstable; urgency=medium
 .
   * Update to CVS HEAD:
 - [tg] Pass the third argument to open(2) always for HP aCC
 - [tg] clang --version seems to be accepted these days
 - [tg] DragonFlyBSD defines NELEM in sys/param.h õÕ
 - [tg] Rewrite all code to not need PATH_MAX, fix some casts
 - [tg] Fix compatibility with systems where tv_sec is unsigned
 - [tg] Begin debugging the heredoc-tmpfile-8 test; help welcome
   * Omit D:loglibc lines from README.Debian (Closes: #1021085)
   * Fix autopkgtests to handle flaky tests (Closes: #1025229)
Checksums-Sha1:
 445f59154f3c81c26e9f87f2641495ca2b41b776 2590 mksh_59c-20.dsc
 cef278f4fc3ece4351b504598b62067f1702 285544 mksh_59c-20.debian.tar.xz
Checksums-Sha256:
 1ae1f4bdd0b1f4aea3b239c4486d119ec7a94ada525f3b5939842c624f8006c8 2590 
mksh_59c-20.dsc
 54dc48fe8cc269a6f38ee6b24bd3eadb8a9e45c76f61afb0a1c0eabf3a347ce0 285544 
mksh_59c-20.debian.tar.xz
Files:
 b056042399c0b17c5f5c142f132b3277 2590 shells optional mksh_59c-20.dsc
 e1bbc4ec757a053d711717d97341d528 285544 shells optional 
mksh_59c-20.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)

iQIcBAEBCQAGBQJjiWLZAAoJEHa1NLLpkAfgvSMQAI5DHLlPuqnUmjuhcgeZRPFz
MzJIXH9FQIMEa1k10zDdW1oKbumRJP46OPCVgwhWFv4yKyirG1ikwZcKVn6iM8H7
Q7kVAQ6iKSRkFsPIghu6QlitEehxKiskCIG8LEgBgXdYJRWGBOi0B+uM0MpgvFl/
T6BQqM4PssfgoTOou5xK6touhAgF/OLOnmf5n38km7Q3AyGRq2zT6udb+LFnjUDV
KjSjFV3PtKIX2LKmZm1Z9/QjCxv2etSAbPR4cqPE7GSthm18q1GuNjpnVcqTB1FC
m11Y51Us4IJqYmgrrq8qZGdQY5CO3PPnmWKitylp1DR5bVcoMGnG3QKLJUVQcrNi
cAh17hSFgi2DuOGZsm6HSbJyC55ZRpz1+34HeVWKZoCSHYuGqaZGzwRV1r7zEmig
P/3kUeS4z4HkaoEgs7U7Ls0zuWl2f5uRqVDA6tJV1mQkBigNzoidACEa6TKul1Kg
NZIIKBVXyvCoh+j2jUZ1mghU0IKic1gHstiYLZfUyEWALINpnWcrriPIleB244km
JkqmejsRzRXtY59mhamgbZ7T8oZtvAqjGqMQxmuTEHea8XFxfq6J8mYUCZPp52HH
qR92Dm9OqgaTOpJZqI1084KpJiHloWfVKObX1n3RQ0XSj3j4U1OLnq3etL4zAeKK
luDVPJiuBy2zWkQMFf3s
=62ZW
-END PGP SIGNATURE End Message ---

Bug#1016411: marked as done (ghdl FTBFS with LLVM 14 as default)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 04:06:24 +
with message-id 
and subject line Bug#1016411: fixed in ghdl 2.0.0+dfsg-1
has caused the Debian Bug report #1016411,
regarding ghdl FTBFS with LLVM 14 as default
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.)


-- 
1016411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghdl
Version: 1.0.0+dfsg-8
Severity: serious
Tags: ftbfs

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

...

Configuring with llvm backend

if [ -n "1" ]; then \
cd /build/1st/ghdl-1.0.0+dfsg/builddir/llvm; \
../../configure --srcdir=../.. --prefix=/usr \
--libdir=lib/ghdl/llvm --incdir=lib/ghdl/include \
--disable-libghdl --enable-gplcompat \
--with-llvm-config; \
fi
Build machine is: x86_64-linux-gnu
Unhandled version llvm 14.0.6
make[1]: *** [debian/rules:78: override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 2.0.0+dfsg-1
Done: Andreas Bombe 

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

Debian distribution maintenance software
pp.
Andreas Bombe  (supplier of updated ghdl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 02 Dec 2022 02:53:49 +0100
Source: ghdl
Architecture: source
Version: 2.0.0+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Andreas Bombe 
Closes: 1016411 1017672 1023681
Changes:
 ghdl (2.0.0+dfsg-1) experimental; urgency=medium
 .
   [ Andreas Bombe ]
   * Add file exclusions for new testsuites with unclear licensing in ghdl 2.0.0
   * New upstream version 2.0.0+dfsg
   * Update debian/copyright
   * Remove configure patches for LLVM 11.1, 12, 13, not needed anymore
   * Remove clean-more, versioning, fix-build patches, applied upstream
   * Refresh and adjust patches for new upstream release
   * Add Build-Depends on texinfo for GCC backend
   * Add gcc-12.patch to allow building for GCC 12
   * Switch to GCC/GNAT 12 (Closes: #1023681)
   * Change Build-Depends on gnat-$VER to versioned depends on gnat
   * Add patch llvm-14.0.patch to allow building with LLVM 14
 (Closes: #1016411, #1017672)
   * debian/rules: Propagate error codes properly.
 Thanks to Daniel Gröber for the patch this is based on
   * debian/rules: Configure with --disable-werror
   * Disable dh_dwz as dwz has bugs trying to handle GCC 12 / LLVM 14 outputs
   * Do not install ghwdump as that is provided by the gtkwave package
   * Disable gcc-verbose-lto-link gcc patch during build as there are quoting
 issues on the GHDL side where the LLINKER variable is used
   * Add parallelize-testsuite patch from upstream git
   * Add skip-unsupported-tests patch to disable tests for unsupported features
   * debian/watch: Use /tags rather than /releases page that stopped working
   * Add GCC 12 patch to reenable C source files in gengtype.cc
   * Add gcc-12-fix-move-pragma-suppress patch from upstream git
   * Add gcc-12-more-fix-move-pragma-suppress patch from upstream git
   * Bump Standards-Version to 4.6.1, no changes needed
 .
   [ Daniel Gröber ]
   * Fix unclean rebuild via debian/rules
Checksums-Sha1:
 db4f229b9b76a5460e2063a90fa3066c3a20286e 2651 ghdl_2.0.0+dfsg-1.dsc
 d7739c5191e2a734b6131cddac4faa56d22b544c 4244868 ghdl_2.0.0+dfsg.orig.tar.xz
 c68baf8bb89d3c95273be1b9ffc13851b706a3ba 25316 ghdl_2.0.0+dfsg-1.debian.tar.xz
 0cec906dc36a85bcc516232f90e8a22a4809af20 10884 
ghdl_2.0.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 204180d012ba105b75471cb108ffe173724dfd758b1e329ca6d8287a7a0a587d 2651 
ghdl_2.0.0+dfsg-1.dsc
 ff4a0cce3b762de18dc8d595675d79f0cc44a5b3f931d21e007352824b273573 4244868 
ghdl_2.0.0+dfsg.orig.tar.xz
 9224ac7c808e8d20c871e515b6be75d23d80844712908b783bbda912a3edc83a 25316 
ghdl_2.0.0+dfsg-1.

Bug#1023681: marked as done (ghdl build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 04:06:24 +
with message-id 
and subject line Bug#1023681: fixed in ghdl 2.0.0+dfsg-1
has caused the Debian Bug report #1023681,
regarding ghdl build depends on gcc-10 that should not be in bookworm
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.)


-- 
1023681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghdl
Version: 1.0.0+dfsg-8
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 2.0.0+dfsg-1
Done: Andreas Bombe 

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

Debian distribution maintenance software
pp.
Andreas Bombe  (supplier of updated ghdl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 02 Dec 2022 02:53:49 +0100
Source: ghdl
Architecture: source
Version: 2.0.0+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Andreas Bombe 
Closes: 1016411 1017672 1023681
Changes:
 ghdl (2.0.0+dfsg-1) experimental; urgency=medium
 .
   [ Andreas Bombe ]
   * Add file exclusions for new testsuites with unclear licensing in ghdl 2.0.0
   * New upstream version 2.0.0+dfsg
   * Update debian/copyright
   * Remove configure patches for LLVM 11.1, 12, 13, not needed anymore
   * Remove clean-more, versioning, fix-build patches, applied upstream
   * Refresh and adjust patches for new upstream release
   * Add Build-Depends on texinfo for GCC backend
   * Add gcc-12.patch to allow building for GCC 12
   * Switch to GCC/GNAT 12 (Closes: #1023681)
   * Change Build-Depends on gnat-$VER to versioned depends on gnat
   * Add patch llvm-14.0.patch to allow building with LLVM 14
 (Closes: #1016411, #1017672)
   * debian/rules: Propagate error codes properly.
 Thanks to Daniel Gröber for the patch this is based on
   * debian/rules: Configure with --disable-werror
   * Disable dh_dwz as dwz has bugs trying to handle GCC 12 / LLVM 14 outputs
   * Do not install ghwdump as that is provided by the gtkwave package
   * Disable gcc-verbose-lto-link gcc patch during build as there are quoting
 issues on the GHDL side where the LLINKER variable is used
   * Add parallelize-testsuite patch from upstream git
   * Add skip-unsupported-tests patch to disable tests for unsupported features
   * debian/watch: Use /tags rather than /releases page that stopped working
   * Add GCC 12 patch to reenable C source files in gengtype.cc
   * Add gcc-12-fix-move-pragma-suppress patch from upstream git
   * Add gcc-12-more-fix-move-pragma-suppress patch from upstream git
   * Bump Standards-Version to 4.6.1, no changes needed
 .
   [ Daniel Gröber ]
   * Fix unclean rebuild via debian/rules
Checksums-Sha1:
 db4f229b9b76a5460e2063a90fa3066c3a20286e 2651 ghdl_2.0.0+dfsg-1.dsc
 d7739c5191e2a734b6131cddac4faa56d22b544c 4244868 ghdl_2.0.0+dfsg.orig.tar.xz
 c68baf8bb89d3c95273be1b9ffc13851b706a3ba 25316 ghdl_2.0.0+dfsg-1.debian.tar.xz
 0cec906dc36a85bcc516232f90e8a22a4809af20 10884 
ghdl_2.0.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 204180d012ba105b75471cb108ffe173724dfd758b1e329ca6d8287a7a0a587d 2651 
ghdl_2.0.0+dfsg-1.dsc
 ff4a0cce3b762de18dc8d595675d79f0cc44a5b3f931d21e007352824b273573 4244868 
ghdl_2.0.0+dfsg.orig.tar.xz
 9224ac7c808e8d20c871e515b6be75d23d80844712908b783bbda912a3edc83a 25316 
ghdl_2.0.0+dfsg-1.debian.tar.xz
 6e1da6f539c41714f6762e0bda2142846f6c5ef7e2fdaeb2233e15265c4cf6ec 10884 
ghdl_2.0.0+dfsg-1_amd64.buildinfo
Files:
 7d9fdc94500983cba0eae62f48e3ce1e 2651 electronics optional 
ghdl_2.0.0+dfsg-1.dsc
 b722e42292a1559158878879fbca9609 4244868 electronics optional 
ghdl_2.0.0+dfsg.orig.tar.xz
 e9de17cc39e4924ec79f5f8b73892300 25316 electronics optional 
ghdl_2.0.0+dfsg-1.debian.tar.xz
 3a612e0257b2c6c5983ca4c5e895e494 10884 electronics optional 
ghdl_2.0.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/fJ3FAtt+ejNyKmCMWRwWx2jH

Bug#1025234: prometheus: flaky autopkgtest (on 32 bit archs?)

[Daniel Swarbrick]

Hi Paul,

I have also noticed the fairly frequent failures of the memory-intensive 
tests on 32-bit, and I am doing my best to keep on top of them with 
t.Skip() patches where appropriate. Several of the tests result in the 4 
GiB memory footprint threshold being exceeded.


Prometheus itself is still usable on 32-bit, but obviously only up to a 
certain size. The upstream developers don't seem to consider 32-bit when 
writing unit tests, thus the regular addition of new tests which fail.


Daniel.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024687: marked as done (libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities)

[Debian Bug Tracking System]

Your message dated Fri, 2 Dec 2022 13:30:34 +0800
with message-id 
and subject line Re: Wrong soversion in libfm-qt11=1.2.0-1
has caused the Debian Bug report #1024687,
regarding libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities
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.)


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

Package: libfm-qt11
Version: 1.2.0-1

After upgrading libfm-qt11 desktop restart with this error in a popup 
window:


Crash Report Desktop crashed too many times. Its autorestart has been 
disabled until next login.


lxqt configuration center -> Desktop can't be run anymore.

Downgrading fix the problem.

thanks

--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net
--- End Message ---
--- Begin Message ---
Version: 1.2.0-2

We have start the transition, and this will be fixed once the transition
has been done. Sorry for inconvenience.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


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

Processed: unarchiving 996067, reopening 996067, closing 996067

[Debian Bug Tracking System]

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

> # src:gnome-shell-extension-no-annoyance was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 996067
Bug #996067 {Done: Debian FTP Masters } 
[gnome-shell-extension-no-annoyance] gnome-shell-extension-no-annoyance: does 
not declare compatibility with GNOME Shell 41
Unarchived Bug 996067
> reopen 996067
Bug #996067 {Done: Debian FTP Masters } 
[gnome-shell-extension-no-annoyance] gnome-shell-extension-no-annoyance: does 
not declare compatibility with GNOME Shell 41
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0+20210717-12dc667-1+rm.
> close 996067 0+20220925-c6804a4-1
Bug #996067 [gnome-shell-extension-no-annoyance] 
gnome-shell-extension-no-annoyance: does not declare compatibility with GNOME 
Shell 41
Marked as fixed in versions 
gnome-shell-extension-no-annoyance/0+20220925-c6804a4-1.
Bug #996067 [gnome-shell-extension-no-annoyance] 
gnome-shell-extension-no-annoyance: does not declare compatibility with GNOME 
Shell 41
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1025296: clementine: Core dump at startup, libprotobuf version mismatch

[smarios]

Package: clementine
Version: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: smar...@jaist.ac.jp

Dear Maintainer,

Clementine core dumps on startup, complaining about mismatched versions
of libprotobuf.

   * What led up to the situation?
Updating packages (and possibly libprotobuf).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Tried starting clementine from the command line.

Also tried to LD_PRELOAD libprotobuf.so.23 but this has no
effect, as clementine explicitly depends on libprotobuf.so.32

   * What was the outcome of this action?
Clementine crashes on startup, producing a core dump.

   * What outcome did you expect instead?
Clementine to startup normally and allow playback of music.

Furthermore, this also affects strawberry.

I'm attaching raw output from clementine crashing, below:

redacted@redacted:~$ clementine
[libprotobuf FATAL google/protobuf/stubs/common.cc:83] This program was 
compiled against version 3.12.4 of the Protocol Buffer runtime library, which 
is not compatible with the installed version (3.21.9).  Contact the program 
author for an update.  If you compiled the program yourself, make sure that 
your headers are from the same version of Protocol Buffers as your link-time 
library.  (Version verification failed in "gen/proto_out/ipc/ipc.pb.cc".)
terminate called after throwing an instance of 
'google::protobuf::FatalException'
  what():  This program was compiled against version 3.12.4 of the Protocol 
Buffer runtime library, which is not compatible with the installed version 
(3.21.9).  Contact the program author for an update.  If you compiled the 
program yourself, make sure that your headers are from the same version of 
Protocol Buffers as your link-time library.  (Version verification failed in 
"gen/proto_out/ipc/ipc.pb.cc".)
Aborted (core dumped)



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.20.4-1
ii  gstreamer1.0-plugins-good   1.20.3-1+b1
ii  gstreamer1.0-plugins-ugly   1.20.3-1
ii  libasound2  1.2.8-1
ii  libc6   2.36-5
ii  libcdio19   2.1.0-4
ii  libchromaprint1 1.5.1-2+b1
ii  libcrypto++88.7.0+git220824-1
ii  libfftw3-double33.3.8-2
ii  libgcc-s1   12.2.0-9
ii  libglib2.0-02.74.1-2
ii  libgpod40.8.3-17
ii  libgstreamer-plugins-base1.0-0  1.20.4-1
ii  libgstreamer1.0-0   1.20.4-1
ii  liblastfm5-11.1.0-5
ii  libmtp9 1.1.20-1
ii  libmygpo-qt5-1  1.1.0-4
ii  libprotobuf32   3.21.9-5
ii  libpulse0   16.1+dfsg1-2+b1
ii  libqt5concurrent5   5.15.6+dfsg-4
ii  libqt5core5a5.15.6+dfsg-4
ii  libqt5dbus5 5.15.6+dfsg-4
ii  libqt5gui5  5.15.6+dfsg-4
ii  libqt5network5  5.15.6+dfsg-4
ii  libqt5sql5  5.15.6+dfsg-4
ii  libqt5sql5-sqlite   5.15.6+dfsg-4
ii  libqt5widgets5  5.15.6+dfsg-4
ii  libqt5x11extras55.15.6-2
ii  libsqlite3-03.40.0-1
ii  libstdc++6  12.2.0-9
ii  libtag1v5   1.13-1
ii  libx11-62:1.8.1-2
ii  zlib1g  1:1.2.11.dfsg-4.1

Versions of packages clementine recommends:
ii  gstreamer1.0-alsa1.20.4-1
ii  gstreamer1.0-pulseaudio  1.20.3-1+b1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.20.3-2+b1

-- no debconf information

Regards,

Bug#1025103: marked as done (python-h2: (autopkgtest) needs update for python3.11: AssertionError)

[Debian Bug Tracking System]

Your message dated Fri, 02 Dec 2022 07:34:28 +
with message-id 
and subject line Bug#1025103: fixed in python-h2 4.1.0-4
has caused the Debian Bug report #1025103,
regarding python-h2: (autopkgtest) needs update for python3.11: AssertionError
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.)


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

Source: python-h2
Version: 4.1.0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-h2  from testing4.1.0-3
all others from testingfrom testing

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

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


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

Paul

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

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

=== FAILURES 
===
 TestEventReprs.test_remotesettingschanged_repr 



self = 

def test_remotesettingschanged_repr(self):
"""
RemoteSettingsChanged has a useful debug representation.
"""
e = h2.events.RemoteSettingsChanged()
e.changed_settings = {
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE:
h2.settings.ChangedSetting(
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE, 
2**16, 2**15

),
}
>   assert repr(e) == (
""setting=SettingCodes.INITIAL_WINDOW_SIZE, 
original_value=65536, "

"new_value=32768)}>"
)
E   AssertionError: assert '' == 
''

E Skipping 54 identical leading characters in diff, use -v to show
E - g(setting=SettingCodes.INITIAL_WINDOW_SIZE, 
original_value=65536, new_value=32768)}>

E ?   
E + g(setting=4, original_value=65536, new_value=32768)}>
E ?   ^

test/test_events.py:210: AssertionError
_ TestEventReprs.test_streamreset_repr 
_


self = 

def test_streamreset_repr(self):
"""
StreamEnded has a useful debug representation.
"""
e = h2.events.StreamReset()
e.stream_id = 919
e.error_code = h2.errors.ErrorCodes.ENHANCE_YOUR_CALM
e.remote_reset = False
>   assert repr(e) == (
""
)
E   AssertionError: assert '' == 
''
E - error_code:ErrorCodes.ENHANCE_YOUR_CALM, remote_reset:False>
E ? 


E + 
E ?^^

test/test_events.py:252: AssertionError
 TestEventReprs.test_settingsacknowledged_repr 
_


self = 

def test_settingsacknowledged_repr(self):
"""
SettingsAcknowledged has a useful debug representation.
"""
e = h2.events.SettingsAcknowledged()
e.changed_settings = {
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE:
h2.settings.ChangedSetting(
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE, 
2**16, 2**15

),
}
>   assert repr(e) == (
""setting=SettingCodes.INITIAL_WINDOW_SIZE, 
original_value=65536, "

"new_value=32768)}>"
)
E   AssertionError: assert '' == 
''

E Skipping 53 identical leading characters in diff, use -v to show
E - g(setting=SettingCodes.INITIAL_WINDOW_SIZE, 
original_value=65536, new_value=32768)}>

E ?