Processed: bts

[Debian Bug Tracking System]

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

> block 1023453 by 1023620
Bug #1023453 [pgcli] pgcli: Can't handle PostgreSQL "special" commands
1023453 was not blocked by any bugs.
1023453 was not blocking any bugs.
Added blocking bug(s) of 1023453: 1015148 and 1023620
> thanks
Stopping processing here.

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

Processed (with 1 error): bts

[Debian Bug Tracking System]

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

> forcemerge 1015148 1023620
Bug #1015148 [python-pgspecial] new upstream (2.x)
Bug #1015148 [python-pgspecial] new upstream (2.x)
There is no source info for the package 'python-pgspecial' at version 
'1.11.10+dfsg1-2' with architecture ''
Unable to make a source version for version '1.11.10+dfsg1-2'
Marked as found in versions 1.11.10+dfsg1-2.
Bug #1023620 [python-pgspecial] new upstream required for pgcli
Merged 1015148 1023620
> severity 1023620 serious
Bug #1023620 [python-pgspecial] new upstream required for pgcli
Bug #1015148 [python-pgspecial] new upstream (2.x)
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> severity 1023453 serious
Bug #1023453 [pgcli] pgcli: Can't handle PostgreSQL "special" commands
Severity set to 'serious' from 'normal'
> block 1023453 by 1023453
Bug #1023453 [pgcli] pgcli: Can't handle PostgreSQL "special" commands
Failed to set blocking bugs of 1023453: It is nonsensical for a bug to block 
itself (or a merged partner): 1023453.

> thanks
Stopping processing here.

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

Bug#981713: graftcp: Change Architecture from "any" to "amd64"

[Yifan Xu]

Source: graftcp
Version: 0.1.3+ds1-1
Followup-For: Bug #981713

Dear Maintainer,

This package is only compatitable with amd64 (i386/amd64/aarch64 for upstream),
on amd64 it need  header file, which is only available on amd64 (for 
aarch64
it use some arm assembly code). maybe we should change debian/control from 
"any" to "amd64".

Debian salsa: v0.3 (amd64 only)  <-- current package
upstream stable:  v0.4 (amd64 only)
upstream latest:  v0.5.0-beta.1 (i386/amd64/aarch64)


Thanks,
Yifan Xu

Processed: tagging 1023963, retitle 1023273 to ocrmypdf: incompatible with ghostscript 10 ..., tagging 912271 ...

[Debian Bug Tracking System]

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

> tags 1023963 + experimental
Bug #1023963 {Done: Laszlo Boszormenyi (GCS) } [src:protobuf] 
protobuf FTBFS with Python 3.11 as supported version
Added tag(s) experimental.
> retitle 1023273 ocrmypdf: incompatible with ghostscript 10
Bug #1023273 [ocrmypdf] Breaks packages like ocrmypdf
Changed Bug title to 'ocrmypdf: incompatible with ghostscript 10' from 'Breaks 
packages like ocrmypdf'.
> notfixed 966590 3.1.1-1
Bug #966590 {Done: Jelmer Vernooij } [brz] git-remote-bzr(1) 
manual page: broken link
There is no source info for the package 'brz' at version '3.1.1-1' with 
architecture ''
Unable to make a source version for version '3.1.1-1'
No longer marked as fixed in versions 3.1.1-1.
> fixed 966590 3.2.0-1
Bug #966590 {Done: Jelmer Vernooij } [brz] git-remote-bzr(1) 
manual page: broken link
Marked as fixed in versions breezy/3.2.0-1.
> reassign 1001748 src:llvm-toolchain-13 
> 1:13~++20210731010128+6eaf46beb462-1~exp1
Bug #1001748 {Done: Sylvestre Ledru } [clang-tidy] 
clang-tidy: run-clang-tidy symlink is broken
Bug reassigned from package 'clang-tidy' to 'src:llvm-toolchain-13'.
No longer marked as found in versions llvm-defaults/0.53.
No longer marked as fixed in versions llvm-toolchain-13/1:13.0.1~+rc1-1~exp2.
Bug #1001748 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-13] clang-tidy: run-clang-tidy symlink is broken
Marked as found in versions 
llvm-toolchain-13/1:13~++20210731010128+6eaf46beb462-1~exp1.
> fixed 1001748 1:13.0.1~+rc1-1~exp2
Bug #1001748 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-13] clang-tidy: run-clang-tidy symlink is broken
Marked as fixed in versions llvm-toolchain-13/1:13.0.1~+rc1-1~exp2.
> tags 912271 - buster sid
Bug #912271 {Done: John Scott } [src:newlib] please provide 
a newlib source package
Removed tag(s) sid and buster.
> fixed 979545 1.0.14-2
Bug #979545 [courier-mlm] the stretch-pu: package courier/0.76.3-5+deb9u1 still 
are broken
Marked as fixed in versions courier/1.0.14-2.
> thanks
Stopping processing here.

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

Bug#968186: marked as done (python3-rgain3: API is potentially about to break)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2022 01:43:19 +
with message-id 
and subject line Bug#1023991: Removed package(s) from unstable
has caused the Debian Bug report #968186,
regarding python3-rgain3: API is potentially about to break
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.)


-- 
968186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rgain3
Version: 1.0.0-1
Severity: serious
Justification: maintainer says so
Tags: upstream
Forwarded: https://github.com/chaudum/rgain/issues/29

Upstream changes in rgain3 have broken the import ABI. This doesn't mean
anything for the replaygain and collectiongain CLI tools, but would break
compatibility if we had packages in Debian that imported it as a library.

I've asked for clarification on whether this was intentional, but until I
get an answer, this library probably shouldn't migrate.

smcv
--- End Message ---
--- Begin Message ---
Version: 1.1.1-3+rm

Dear submitter,

as the package rgain3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023991

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023317: marked as done (zsh: re-adds /bin/zsh to /etc/shells on upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 14 Nov 2022 01:22:23 +
with message-id 
and subject line Bug#1023317: fixed in zsh 5.9-2
has caused the Debian Bug report #1023317,
regarding zsh: re-adds /bin/zsh to /etc/shells on upgrade
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.)


-- 
1023317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zsh,zsh-static
Version: 5.9-1
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

When upgrading or reinstalling zsh or zsh-static, it adds /bin/zsh or
/bin/zsh-static respectively to /etc/shells even if one locally removed
it there. Such behaviour violates Debian policy section 10.7.3. I
propose managing the entry declaratively using dpkg triggers and am
attaching a patch for your convenience.

Helmut
diff --minimal -Nru zsh-5.9/debian/changelog zsh-5.9/debian/changelog
--- zsh-5.9/debian/changelog2022-05-15 01:20:26.0 +0200
+++ zsh-5.9/debian/changelog2022-11-02 10:35:53.0 +0100
@@ -1,3 +1,10 @@
+zsh (5.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Manage /etc/shells using dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 10:35:53 +0100
+
 zsh (5.9-1) unstable; urgency=low
 
   * [73d31738,d4d20348,2ae4a398] Import new upstream release 5.9.
diff --minimal -Nru zsh-5.9/debian/control zsh-5.9/debian/control
--- zsh-5.9/debian/control  2022-05-15 01:17:30.0 +0200
+++ zsh-5.9/debian/control  2022-11-02 10:35:51.0 +0100
@@ -56,7 +56,8 @@
 Architecture: any
 Depends: zsh-common (= ${source:Version}),
  ${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ debianutils (>= 5.3-1~)
 Pre-Depends: ${misc:Pre-Depends}
 Recommends: ${shlibs:Recommends}
 Suggests: zsh-doc
@@ -88,7 +89,8 @@
 
 Package: zsh-static
 Architecture: any
-Depends: ${misc:Depends}
+Depends: ${misc:Depends},
+ debianutils (>= 5.3-1~)
 Recommends: zsh-common
 Suggests: zsh-doc
 Built-Using: ${Built-Using}
diff --minimal -Nru zsh-5.9/debian/rules zsh-5.9/debian/rules
--- zsh-5.9/debian/rules2022-02-25 11:41:52.0 +0100
+++ zsh-5.9/debian/rules2022-11-02 10:35:22.0 +0100
@@ -158,6 +158,8 @@
  xargs sed -e 's@\.\./config\.h@config.h@;s@#\(\s*\)include 
"\([^"]\+\)"@#\1include @' -i
 
cd debian/zsh-dev/usr/share/aclocal; mv aczshoot.m4 zshoot.m4
+   install -D -m644 debian/zsh.shells 
debian/zsh/usr/share/debianutils/shells.d/zsh
+   install -D -m644 debian/zsh-static.shells 
debian/zsh-static/usr/share/debianutils/shells.d/zsh-static
 
 override_dh_gencontrol-arch:
dh_gencontrol -a -- -VBuilt-Using="$(BUILT_USING)"
diff --minimal -Nru zsh-5.9/debian/zsh-static.postinst 
zsh-5.9/debian/zsh-static.postinst
--- zsh-5.9/debian/zsh-static.postinst  2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh-static.postinst  2022-11-02 10:33:49.0 +0100
@@ -4,9 +4,6 @@
 
 case "$1" in
 (configure)
-#if test -z "$2"; then
-   add-shell /bin/zsh-static
-#fi
 ;;
 
 abort-upgrade|abort-remove|abort-deconfigure)
diff --minimal -Nru zsh-5.9/debian/zsh-static.postrm 
zsh-5.9/debian/zsh-static.postrm
--- zsh-5.9/debian/zsh-static.postrm2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh-static.postrm1970-01-01 01:00:00.0 +0100
@@ -1,11 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case "$1" in
-   (remove)
-   remove-shell /bin/zsh-static
-   ;;
-esac
-
-#DEBHELPER#
diff --minimal -Nru zsh-5.9/debian/zsh-static.shells 
zsh-5.9/debian/zsh-static.shells
--- zsh-5.9/debian/zsh-static.shells1970-01-01 01:00:00.0 +0100
+++ zsh-5.9/debian/zsh-static.shells2022-11-02 10:33:46.0 +0100
@@ -0,0 +1 @@
+/bin/zsh-static
diff --minimal -Nru zsh-5.9/debian/zsh.postinst zsh-5.9/debian/zsh.postinst
--- zsh-5.9/debian/zsh.postinst 2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh.postinst 2022-11-02 10:34:19.0 +0100
@@ -12,9 +12,6 @@
 
 case "$1" in
 (configure)
-add-shell /bin/zsh
-add-shell /usr/bin/zsh
-
# New hardcoded symlinks which unfortunately can't be shipped inside
# the package itself since some people want to merge /bin and /usr/bin
# against FHS and all Unix tradition.
diff --minimal -Nru zsh-5.9/debian/zsh.postrm zsh-5.9/debian/zsh.postrm
--- zsh-5.9/debian/zsh.postrm   2022-02-12 20:54:36.0 +0100
+++ zsh-5.9/debian/zsh.postrm   2022-11-02 10:34:27.0 +0100
@@ -4,9 +4,6 @@
 
 case "$1" in

Bug#1024050: python-cytoolz FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-cytoolz
Version: 0.11.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-cytoolz=0.11.0-2%2Bb2

...
=== FAILURES ===
__ test_random_sample __

def test_random_sample():
alist = list(range(100))

assert list(random_sample(prob=1, seq=alist, random_state=2016)) == 
alist

mk_rsample = lambda rs=1: list(random_sample(prob=0.1,
 seq=alist,
 random_state=rs))
rsample1 = mk_rsample()
assert rsample1 == mk_rsample()

rsample2 = mk_rsample(1984)
randobj = Random(1984)
assert rsample2 == mk_rsample(randobj)

assert rsample1 != rsample2

>   assert mk_rsample(object) == mk_rsample(object)

cytoolz/tests/test_itertoolz.py:545: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
cytoolz/tests/test_itertoolz.py:533: in 
mk_rsample = lambda rs=1: list(random_sample(prob=0.1,
cytoolz/itertoolz.pyx:1794: in cytoolz.itertoolz.random_sample.__cinit__
random_state = Random(random_state)
/usr/lib/python3.11/random.py:125: in __init__
self.seed(x)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , a = , version = 2

def seed(self, a=None, version=2):
"""Initialize internal state from a seed.

The only supported seed types are None, int, float,
str, bytes, and bytearray.

None or no argument seeds from current time or from an operating
system specific randomness source if available.

If *a* is an int, all bits are used.

For version 2 (the default), all of the bits are used if *a* is a str,
bytes, or bytearray.  For version 1 (provided for reproducing random
sequences from older versions of Python), the algorithm for str and
bytes generates a narrower range of seeds.

"""

if version == 1 and isinstance(a, (str, bytes)):
a = a.decode('latin-1') if isinstance(a, bytes) else a
x = ord(a[0]) << 7 if a else 0
for c in map(ord, a):
x = ((103 * x) ^ c) & 0x
x ^= len(a)
a = -2 if x == -1 else x

elif version == 2 and isinstance(a, (str, bytes, bytearray)):
if isinstance(a, str):
a = a.encode()
a = int.from_bytes(a + _sha512(a).digest())

elif not isinstance(a, (type(None), int, float, str, bytes, bytearray)):
>   raise TypeError('The only supported seed types are: None,\n'
'int, float, str, bytes, and bytearray.')
E   TypeError: The only supported seed types are: None,
E   int, float, str, bytes, and bytearray.

/usr/lib/python3.11/random.py:160: TypeError
=== warnings summary ===
cytoolz/compatibility.py:2
  
/<>/.pybuild/cpython3_3.11_cytoolz/build/cytoolz/compatibility.py:2:
 DeprecationWarning: The toolz.compatibility module is no longer needed in 
Python 3 and has been deprecated. Please import these utilities directly from 
the standard library. This module will be removed in a future release.
warnings.warn("The toolz.compatibility module is no longer "

.pybuild/cpython3_3.11_cytoolz/build/cytoolz/tests/test_tlz.py::test_tlz
  /usr/lib/python3.11/importlib/__init__.py:126: DeprecationWarning: The 
toolz.compatibility module is no longer needed in Python 3 and has been 
deprecated. Please import these utilities directly from the standard library. 
This module will be removed in a future release.
return _bootstrap._gcd_import(name[level:], package, level)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 
FAILED cytoolz/tests/test_itertoolz.py::test_random_sample - TypeError: The o...
== 1 failed, 186 passed, 2 warnings in 1.79s ===
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_cytoolz/build; python3.11 -m pytest
...

Processed: tagging 1019830

[Debian Bug Tracking System]

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

> tags 1019830 + bookworm sid
Bug #1019830 [src:codeblocks] codeblocks: Please transition to wxwidgets3.2
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1021852

[Debian Bug Tracking System]

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

> tags 1021852 + pending
Bug #1021852 [src:libvma] libvma FTBFS: error: ISO C++17 does not allow 
‘register’ storage class specifier
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1021541: lomiri-terminal-app: ships a copy of qml-module-qmltermwidget

[Andreas Beckmann]

Followup-For: Bug #1021541

There is now a separate source package src:qmltermwidget building
qml-module-termwidget. Please use that.


Andreas

Bug#1024049: python-clevercsv FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-clevercsv
Version: 0.7.4+ds-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-clevercsv=0.7.4%2Bds-2%2Bb1

...
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
python3.11 -m unittest discover -v -f -s tests/test_unit
test_get_best_set_1 (test_consistency.ConsistencyTestCase.test_get_best_set_1) 
... ok
test_get_best_set_2 (test_consistency.ConsistencyTestCase.test_get_best_set_2) 
... ok
test_code_1 (test_console.ConsoleTestCase.test_code_1) ... ERROR
/usr/lib/python3.11/unittest/case.py:622: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=3 mode='w' encoding='UTF-8'>
  with outcome.testPartExecutor(self):
ResourceWarning: Enable tracemalloc to get the object allocation traceback

==
ERROR: test_code_1 (test_console.ConsoleTestCase.test_code_1)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11/build/tests/test_unit/test_console.py",
 line 126, in test_code_1
tmpfname = self._build_file(table, dialect)
   
  File 
"/<>/.pybuild/cpython3_3.11/build/tests/test_unit/test_console.py",
 line 28, in _build_file
w = writer(tmpid, dialect=dialect)
^^
  File "/<>/.pybuild/cpython3_3.11/build/clevercsv/write.py", line 
32, in __init__
self._writer = csv.writer(csvfile, dialect=self.dialect)
   ^
TypeError: "quotechar" must be a 1-character string

--
Ran 3 tests in 0.004s

FAILED (errors=1)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover 
-v -f -s tests/test_unit
...

Bug#1024048: pyliblo FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pyliblo
Version: 0.10.0-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pyliblo=0.10.0-5%2Bb2

...
testSendReceive (test.test_liblo.DecoratorTestCase.testSendReceive) ... 
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 270, in testSendReceive
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testNoPermission (test.test_liblo.ServerCreationTestCase.testNoPermission) ... 
ok
testPort (test.test_liblo.ServerCreationTestCase.testPort) ... ok
testPortProto (test.test_liblo.ServerCreationTestCase.testPortProto) ... ok
testRandomPort (test.test_liblo.ServerCreationTestCase.testRandomPort) ... ok
testSendReceive (test.test_liblo.ServerTCPTestCase.testSendReceive) ... 
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 226, in testSendReceive
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testBundleCallbacksFire 
(test.test_liblo.ServerTestCase.testBundleCallbacksFire) ... AttributeError: 
module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 144, in testSendBundle
self.assertTrue(self.server.recv(100))
^
AttributeError: module 'inspect' has no attribute 'getargspec'
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 144, in testSendBundle
self.assertTrue(self.server.recv(100))
^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testMethodAfterFree (test.test_liblo.ServerTestCase.testMethodAfterFree) ... ok
testPort (test.test_liblo.ServerTestCase.testPort) ... ok
testRecvImmediate (test.test_liblo.ServerTestCase.testRecvImmediate) ... ok
testRecvTimeout (test.test_liblo.ServerTestCase.testRecvTimeout) ... ok
testSendBlob (test.test_liblo.ServerTestCase.testSendBlob) ... AttributeError: 
module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 75, in testSendBlob
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testSendBundle (test.test_liblo.ServerTestCase.testSendBundle) ... 
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 144, in testSendBundle
self.assertTrue(self.server.recv(100))
^
AttributeError: module 'inspect' has no attribute 'getargspec'
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 144, in testSendBundle
self.assertTrue(self.server.recv(100))
^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testSendInt (test.test_liblo.ServerTestCase.testSendInt) ... AttributeError: 
module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 65, in testSendInt
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testSendInvalid (test.test_liblo.ServerTestCase.testSendInvalid) ... ok
testSendLong (test.test_liblo.ServerTestCase.testSendLong) ... AttributeError: 
module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 128, in testSendLong
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testSendMessage (test.test_liblo.ServerTestCase.testSendMessage) ... 
AttributeError: module 'inspect' has no attribute 'getargspec'
Exception ignored in: 'liblo._msg_callback'
Traceback (most recent call last):
  File "/<>/test/test_liblo.py", line 118, in testSendMessage
self.assertTrue(self.server.recv())
^^
AttributeError: module 'inspect' has no attribute 'getargspec'
ERROR
testSendOthers (test.test_liblo.ServerTestCase.testSendOthers) ... 
AttributeError: module 'inspect' has no attribute 

Bug#1024047: python-line-profiler FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-line-profiler
Version: 2.1-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-line-profiler=2.1-3%2Bb4

...
_line_profiler.c: In function ‘__pyx_f_14_line_profiler_python_trace_callback’:
_line_profiler.c:5627:46: error: invalid use of incomplete typedef 
‘PyFrameObject’ {aka ‘struct _frame’}
 5627 | __pyx_t_1 = ((PyObject *)__pyx_v_py_frame->f_code);
  |  ^~
_line_profiler.c:5835:58: error: invalid use of incomplete typedef 
‘PyFrameObject’ {aka ‘struct _frame’}
 5835 | __pyx_t_1 = __Pyx_PyInt_From_int(__pyx_v_py_frame->f_lineno); 
if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 218, __pyx_L1_error)
  |  ^~
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

Bug#1024046: pyopencl FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pyopencl
Version: 2022.1.6-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pyopencl=amd64=2022.1.6-2%2Bb1=1668366441=0

...
=== FAILURES ===
_ test_elwise_kernel[>] _

ctx_factory = 

def test_elwise_kernel(ctx_factory):
context = ctx_factory()
queue = cl.CommandQueue(context)

from pyopencl.clrandom import rand as clrand

>   a_gpu = clrand(queue, (50,), np.float32)

test_algorithm.py:52: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
../pyopencl/clrandom.py:767: in rand
gen.fill_uniform(result, a=a, b=b)
../pyopencl/clrandom.py:681: in fill_uniform
return self._fill("uniform", ary,
../pyopencl/clrandom.py:658: in _fill
self.get_gen_kernel(ary.dtype, distribution)
/usr/lib/python3/dist-packages/pytools/__init__.py:696: in wrapper
result = function(obj, *args, **kwargs)
../pyopencl/clrandom.py:641: in get_gen_kernel
knl.set_scalar_arg_dtypes(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
arg_types = (, , , , , None, ...)

def kernel_set_arg_types(self, arg_types):
arg_types = tuple(arg_types)

# {{{ arg counting bug handling

# For example:
# https://github.com/pocl/pocl/issues/197
# (but Apple CPU has a similar bug)

work_around_arg_count_bug = False
warn_about_arg_count_bug = False

from pyopencl.characterize import has_struct_arg_count_bug

count_bug_per_dev = [
has_struct_arg_count_bug(dev, self.context)
for dev in self.context.devices]

from pytools import single_valued
if any(count_bug_per_dev):
if all(count_bug_per_dev):
work_around_arg_count_bug = single_valued(count_bug_per_dev)
else:
warn_about_arg_count_bug = True

# }}}

from pyopencl.invoker import generate_enqueue_and_set_args
enqueue, my_set_args = \
generate_enqueue_and_set_args(
self.function_name,
len(arg_types), self.num_args,
arg_types,
warn_about_arg_count_bug=warn_about_arg_count_bug,
work_around_arg_count_bug=work_around_arg_count_bug,
devs=self.context.devices)

# Make ourselves a kernel-specific class, so that we're able to override
# __call__. Inspired by https://stackoverflow.com/a/38541437
class KernelWithCustomEnqueue(type(self)):
__call__ = enqueue
set_args = my_set_args

>   self.__class__ = KernelWithCustomEnqueue
E   TypeError: __class__ assignment: 'KernelWithCustomEnqueue' object 
layout differs from 'pyopencl._cl.Kernel'

../pyopencl/__init__.py:878: TypeError
_ test_elwise_kernel_with_options[>] _

ctx_factory = 

def test_elwise_kernel_with_options(ctx_factory):
from pyopencl.clrandom import rand as clrand
from pyopencl.elementwise import ElementwiseKernel

context = ctx_factory()
queue = cl.CommandQueue(context)

>   in_gpu = clrand(queue, (50,), np.float32)
...
= 203 failed, 57 passed, 6 skipped, 1 deselected, 2 xfailed, 19 warnings in 
115.65s (0:01:55) =
E: pybuild pybuild:379: test: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build cp -r 
/<>/test /<>/.pybuild/cpython3_3.11/build && cd 
/<>/.pybuild/cpython3_3.11/build/test && python3.11 -m pytest 
--verbosity=2 -k 'not test_event_set_callback' && rm -rf 
/<>/.pybuild/cpython3_3.11/build/test
...

Bug#1024045: python-pomegranate FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-pomegranate
Version: 0.14.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-pomegranate=0.14.8-1%2Bb1

...
==
ERROR: test suite for >/.pybuild/cpython3_3.11_pomegranate/build/tests/test_profile_hmm.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 362 tests in 13.186s

FAILED (errors=10)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_pomegranate/build; python3.11 -m nose 
-v tests
...

Bug#1024044: python-ltfatpy FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-ltfatpy
Version: 1.0.16-7
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-ltfatpy=sid

...
=== FAILURES ===
 TestGabWin.test_composed_dictionnaries_entries 

self = 

def test_composed_dictionnaries_entries(self):
a = random.randint(10, 40)
M = random.randint(10, 40)
L = lcm(a, M)

# default
self.assertRaises(TypeError, gabwin, {'name': 1}, a, M, L)

# dual psech
tfr = 10
gd = {'name': ('dual', 'sech'), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertFalse(info['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(psech(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)

# dual pgauss
tfr = 10
gd = {'name': ('dual',), 'tfr': tfr}
mess = "a = {0:d}, M = {1:d}, L = {2:d}".format(a, M, L)
mess += str(gd)
(g, info) = gabwin(gd, a, M, L)
mess += "\ng = " + str(g)
mess += "\ninfo = " + str(info)
self.assertTrue(info['auxinfo']['gauss'], mess)
self.assertTrue(info['wasreal'], mess)
self.assertFalse(info['istight'], mess)
self.assertTrue(info['isdual'], mess)
self.assertFalse(info['wasrow'], mess)
self.assertFalse(info['isfir'], mess)
self.assertEqual(info['auxinfo']["tfr"], tfr, mess)
self.assertEqual(info["gl"], len(g), mess)
gt = gabdual(pgauss(L, tfr)[0], a, M, L)
mess += "\ngt = " + str(gt)
np.testing.assert_array_almost_equal(g, gt, 10, mess)
self.assertRaises(ValueError, gabwin, gd, a, M)

# dual fir
>   name = random.sample(arg_firwin(), 1)[0]

ltfatpy/tests/gabor/test_gabwin.py:356: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
population = {'bartlett', 'blackman', 'blackman2', 'cosine', 'hamming', 'hann', 
...}
k = 1

def sample(self, population, k, *, counts=None):
"""Chooses k unique random elements from a population sequence.

Returns a new list containing elements from the population while
leaving the original population unchanged.  The resulting list is
in selection order so that all sub-slices will also be valid random
samples.  This allows raffle winners (the sample) to be partitioned
into grand prize and second place winners (the subslices).

Members of the population need not be hashable or unique.  If the
population contains repeats, then each occurrence is a possible
selection in the sample.

Repeated elements can be specified one at a time or with the optional
counts parameter.  For example:

sample(['red', 'blue'], counts=[4, 2], k=5)

is equivalent to:

sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5)

To choose a sample from a range of integers, use range() for the
population argument.  This is especially fast and space efficient
for sampling from a large population:

sample(range(1000), 60)

"""

# Sampling without replacement entails tracking either potential
# selections (the pool) in a list or previous selections in a set.

# When the number of selections is small compared to the
# population, then tracking selections is efficient, requiring
# only a small set and an occasional reselection.  For
# a larger number of selections, the pool tracking method is
# preferred since the list takes less space than the
# set and it doesn't suffer from frequent reselections.

# The number of calls to _randbelow() is kept at or near k, the
# theoretical minimum.  This is important because running time
# is dominated by _randbelow() and because it extracts the
# least entropy from the underlying random number generators.

# Memory requirements are kept to the smaller of a k-length
# set or an n-length list.

# There are other sampling algorithms that do not require
# auxiliary memory, but they were rejected because they made
# too many calls to _randbelow(), making 

Bug#1024043: python-cassandra-driver FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-cassandra-driver
Version: 3.25.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-cassandra-driver=3.25.0-1%2Bb2

...
==
ERROR: Failure: AttributeError (module 'asyncio' has no attribute 'coroutine')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in 
loadTestsFromName
module = self.importer.importFromPath(
 ^
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
   
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  
  File "/usr/lib/python3.11/imp.py", line 235, in load_module
return load_source(name, filename, file)
   ^
  File "/usr/lib/python3.11/imp.py", line 172, in load_source
module = _load(spec)
 ^^^
  File "", line 721, in _load
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.11_cassandra/build/tests/unit/io/test_asyncioreactor.py",
 line 3, in 
from cassandra.io.asyncioreactor import AsyncioConnection
  File 
"/<>/.pybuild/cpython3_3.11_cassandra/build/cassandra/io/asyncioreactor.py",
 line 29, in 
class AsyncioTimer(object):
  File 
"/<>/.pybuild/cpython3_3.11_cassandra/build/cassandra/io/asyncioreactor.py",
 line 49, in AsyncioTimer
@asyncio.coroutine
 ^
AttributeError: module 'asyncio' has no attribute 'coroutine'

==
FAIL: test_immutable_predicate 
(tests.unit.test_policies.HostFilterPolicyInitTest.test_immutable_predicate)
--
AttributeError: property 'predicate' of 'HostFilterPolicy' object has no setter

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_cassandra/build/tests/unit/test_policies.py",
 line 1304, in test_immutable_predicate
with self.assertRaisesRegexp(AttributeError, expected_message_regex):
AssertionError: "can't set attribute" does not match "property 'predicate' of 
'HostFilterPolicy' object has no setter"

--
Ran 611 tests in 20.442s

FAILED (SKIP=28, errors=1, failures=1)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_cassandra/build; python3.11 -m nose -v 
tests

Bug#1023654: marked as done (liburing 2.3 breaks binary compatibility)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 23:34:42 +
with message-id 
and subject line Bug#1023654: fixed in liburing 2.3-2
has caused the Debian Bug report #1023654,
regarding liburing 2.3 breaks binary compatibility
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.)


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

liburing 2.3 broke binary compatibility without bumping the soname.

In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
their sizes. Both of these structures are parts of io_uring structure
which the main part of the API.  Here's the difference:

@@ -43,7 +79,9 @@
 struct io_uring_sq {
unsigned *khead;
unsigned *ktail;
+   // Deprecated: use `ring_mask` instead of `*kring_mask`
unsigned *kring_mask;
+   // Deprecated: use `ring_entries` instead of `*kring_entries`
unsigned *kring_entries;
unsigned *kflags;
unsigned *kdropped;
@@ -56,13 +94,18 @@
size_t ring_sz;
void *ring_ptr;
 
-   unsigned pad[4];
+   unsigned ring_mask;
+   unsigned ring_entries;
+
+   unsigned pad[2];
 };

...
struct io_uring {
  struct io_uring_sq sq;
  struct io_uring_cq cq;
  ...
}

So, a program which uses struct io_uring compiled with version 2.2 of the
library is completely incompatible when run with version 2.3 of the library,
and vise versa - since many user-visible members of this structure, even when
manipulated by the inline functions offered by uring.h, are completely
incompatible.

This breaks other software.  For example, samba compiled against liburing 2.3
will silently break when liburing 2.2 is used at the run time, and there's no
way for apt/dpkg to tell that liburing2.so upgrade is needed.  The same way,
samba compiled against liburing 2.2 breaks when liburing is upgraded to 2.3,
but in a different way.
--- End Message ---
--- Begin Message ---
Source: liburing
Source-Version: 2.3-2
Done: Guillem Jover 

We believe that the bug you reported is fixed in the latest version of
liburing, 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.
Guillem Jover  (supplier of updated liburing package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Nov 2022 00:15:08 +0100
Source: liburing
Architecture: source
Version: 2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 1023654
Changes:
 liburing (2.3-2) unstable; urgency=medium
 .
   * Artificially bump symbol versions to 2.3 for functions involved in a
 forward compatibility ABI break, for objects built against the new
 library and run-time linked against the old one, until upstream decides
 how to fix/improve this. Closes: #1023654
Checksums-Sha1:
 a1e5ee6739d95254e3d722ffbe9cfb81eec536dd 2241 liburing_2.3-2.dsc
 f0c027ab4dbcc5569f5f24217f3e2765b0c2cb25 14856 liburing_2.3-2.debian.tar.xz
 f2b3dd2aa401dcab79a1cc29b55b67eaadf82886 6335 liburing_2.3-2_amd64.buildinfo
Checksums-Sha256:
 d20a29c8fd452cf6dc03bfe99faac8c823f2fd6792603d6879fd63de7cd4f886 2241 
liburing_2.3-2.dsc
 bd0dd5a30547fd33e9c9e2ea96562ffcd8164cbe50244c42c4e41826959bd81f 14856 
liburing_2.3-2.debian.tar.xz
 ac3e8428bb308e71da8dfdb95e13875e41e3dfc2e5c34b26e23b653a4e6c854d 6335 
liburing_2.3-2_amd64.buildinfo
Files:
 0344f9c514f5d7bcbc1ec5391c79928b 2241 libs optional liburing_2.3-2.dsc
 6fba96894e400a209f6fdb5748aed7d5 14856 libs optional 
liburing_2.3-2.debian.tar.xz
 f02648aeada206dedc1d00395d11a435 6335 libs optional 
liburing_2.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAmNxe4sACgkQuXK/PqSu
V6MmOg//WfvLA6oCRkG9LAdLL2CXmazTk0G0w54JOaXTV5U9/fIoqQ43+zQDGy6O
mGa7ts11V+dQp+aLhooH7XJ6tZLVpg/TZ3T49c+4VNJGNbKfFQp+GzmBAJKMENsl
X4u6dlcp8uztpqpqIZLP4suQZ5StA8K+mbEcAg851gCTSLttYyLWJ/PJ8RPJ9MXM
TDfWa8fMIv9YL/VNqSXayurGLmAIaJmdN1CPcT+ggKWny33cBkbNMuWPpKOQ6UBY

Bug#1023654: in package liburing marked as pending

[Guillem Jover]

Control: tag 1023654 pending

Hi!

Bug #1023654 that you reported in package liburing has been fixed
in the debian/pkgs/liburing.git git repository. You can see the changelog below,
and you can check the diff of the fix at:

https://git.hadrons.org/cgit/debian/pkgs/liburing.git/diff/?id=b80de0d

---
commit b80de0dca45a2c0006d0cc2c4059d56f56898f57
Author: Guillem Jover 
Date:   Mon Nov 14 00:13:19 2022 +0100

Artificially bump some symbol versions to 2.3

Do this for functions involved in a forward compatibility ABI break,
for objects built against the new library and run-time linked against
the old one, until upstream decides how to fix/improve this.

Forwarded: https://github.com/axboe/liburing/issues/724
Closes: #1023654

diff --git a/debian/changelog b/debian/changelog
index 3855e86..d3b6c23 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+liburing (2.3-2) UNRELEASED; urgency=medium
+
+  * Artificially bump symbol versions to 2.3 for functions involved in a
+forward compatibility ABI break, for objects built against the new
+library and run-time linked against the old one, until upstream decides
+how to fix/improve this. Closes: #1023654
+
+ -- Guillem Jover   Mon, 14 Nov 2022 00:09:51 +0100
+
 liburing (2.3-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#1023654 in package liburing marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 1023654 pending
Bug #1023654 [src:liburing] liburing 2.3 breaks binary compatibility
Added tag(s) pending.

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

Bug#1024042: python-jpype FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-jpype
Version: 1.4.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-jpype=1.4.0-2%2Bb1

...
native/common/jp_exception.cpp: In function ‘PyTracebackObject* 
tb_create(PyTracebackObject*, PyObject*, const char*, const char*, int)’:
native/common/jp_exception.cpp:524:23: error: ‘PyThreadState’ {aka ‘struct 
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
  524 | state.frame = last_traceback->tb_frame;
  |   ^
  |   cframe
native/common/jp_exception.cpp:526:23: error: ‘PyThreadState’ {aka ‘struct 
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
  526 | state.frame = NULL;
  |   ^
  |   cframe
native/common/jp_exception.cpp:552:36: error: invalid use of incomplete type 
‘PyFrameObject’ {aka ‘struct _frame’}
  552 | traceback->tb_lasti = frame->f_lasti;
  |^~
In file included from /usr/include/python3.11/Python.h:42,
 from native/common/jp_exception.cpp:16:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
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 

Bug#1019674: marked as done (ruby-vcr: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 23:07:12 +
with message-id 
and subject line Bug#1019674: fixed in ruby-vcr 6.0.0+really5.0.0-4
has caused the Debian Bug report #1019674,
regarding ruby-vcr: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: test 
failures
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.)


-- 
1019674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-vcr
Version: 6.0.0+really5.0.0-3
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 ruby-vcr with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in 
> global_hook_disabled_requests': wrong number of arguments (given 1, expected 
> 0) (ArgumentError)
> /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/ruby-vcr/ruby-vcr_6.0.0+really5.0.0-3+rebuild1663008290_amd64-2022-09-12T18:44:51Z.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 ---
Source: ruby-vcr
Source-Version: 6.0.0+really5.0.0-4
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-vcr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 23:31:11 +0100
Source: ruby-vcr
Architecture: source
Version: 6.0.0+really5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1018882 1019674
Changes:
 ruby-vcr (6.0.0+really5.0.0-4) unstable; urgency=medium
 .
   * Team upload
   * Import upstream commits to make VCR::Cassette::Migrator compatible with
 newer psych (Closes: #1019674)
   * Disable shared example for tests failing on ipv6-only machines (Closes:
 #1018882)
Checksums-Sha1:
 a5b93b433473138f29fd2344af1db7ac54a8adc9 1722 ruby-vcr_6.0.0+really5.0.0-4.dsc
 363fd4129ef0fdd6dc37f9b9ae2392c9a033ea57 147602 
ruby-vcr_6.0.0+really5.0.0.orig.tar.gz
 ba18fe042373baf32e27902132e55061a4dc8b3e 7520 
ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz
 130453772582f5833d2fc6e21c5beb01e7bde7fb 11043 
ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo
Checksums-Sha256:
 6ad65737a2b3c601c22106f77c4b768dff38d18af588f874a940a16cd9bafe05 1722 
ruby-vcr_6.0.0+really5.0.0-4.dsc
 a1d54ee3df0f7d29e641fd45d6e7ee1c0b606e17d3ec45c0377bd70b3e211565 147602 
ruby-vcr_6.0.0+really5.0.0.orig.tar.gz
 c4dbc9aabc08c59e102aa5e5883db3266af7f776602d6d176a7bef13851d1e42 7520 
ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz
 353b3dd25842ddef7952bbd50f8f403e4fc7e0327d2bd01ca8a9fc2f4af24472 11043 
ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo
Files:
 cfd9733b74f4678c735391bd9c0f9230 1722 ruby optional 
ruby-vcr_6.0.0+really5.0.0-4.dsc
 36ac0193516f201510db562d084f6a34 147602 ruby optional 

Bug#1018882: marked as done (ruby-vcr FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 23:07:12 +
with message-id 
and subject line Bug#1018882: fixed in ruby-vcr 6.0.0+really5.0.0-4
has caused the Debian Bug report #1018882,
regarding ruby-vcr FTBFS on IPV6-only buildds
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.)


-- 
1018882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-vcr
Version: 6.0.0+really5.0.0-2
Severity: serious
Tags: ftbfs
Justification: ftbfs

Dear maintainers,

The last upload failed to build from source.

https://buildd.debian.org/status/fetch.php?pkg=ruby-vcr=all=6.0.0%2Breally5.0.0-3=1661725468=0

  when VCR.real_http_connections_allowed? is returning false
does not allow real HTTP requests or record them
when ignore_hosts is configured to "127.0.0.1", "localhost"
E: Build killed with signal TERM after 150 minutes of inactivity

Paul
--- End Message ---
--- Begin Message ---
Source: ruby-vcr
Source-Version: 6.0.0+really5.0.0-4
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-vcr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 23:31:11 +0100
Source: ruby-vcr
Architecture: source
Version: 6.0.0+really5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1018882 1019674
Changes:
 ruby-vcr (6.0.0+really5.0.0-4) unstable; urgency=medium
 .
   * Team upload
   * Import upstream commits to make VCR::Cassette::Migrator compatible with
 newer psych (Closes: #1019674)
   * Disable shared example for tests failing on ipv6-only machines (Closes:
 #1018882)
Checksums-Sha1:
 a5b93b433473138f29fd2344af1db7ac54a8adc9 1722 ruby-vcr_6.0.0+really5.0.0-4.dsc
 363fd4129ef0fdd6dc37f9b9ae2392c9a033ea57 147602 
ruby-vcr_6.0.0+really5.0.0.orig.tar.gz
 ba18fe042373baf32e27902132e55061a4dc8b3e 7520 
ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz
 130453772582f5833d2fc6e21c5beb01e7bde7fb 11043 
ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo
Checksums-Sha256:
 6ad65737a2b3c601c22106f77c4b768dff38d18af588f874a940a16cd9bafe05 1722 
ruby-vcr_6.0.0+really5.0.0-4.dsc
 a1d54ee3df0f7d29e641fd45d6e7ee1c0b606e17d3ec45c0377bd70b3e211565 147602 
ruby-vcr_6.0.0+really5.0.0.orig.tar.gz
 c4dbc9aabc08c59e102aa5e5883db3266af7f776602d6d176a7bef13851d1e42 7520 
ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz
 353b3dd25842ddef7952bbd50f8f403e4fc7e0327d2bd01ca8a9fc2f4af24472 11043 
ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo
Files:
 cfd9733b74f4678c735391bd9c0f9230 1722 ruby optional 
ruby-vcr_6.0.0+really5.0.0-4.dsc
 36ac0193516f201510db562d084f6a34 147602 ruby optional 
ruby-vcr_6.0.0+really5.0.0.orig.tar.gz
 881ea9f2d9dc214f8eda5bc9122bbb95 7520 ruby optional 
ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz
 75bb055f75ccc37239ba90b6168c5a33 11043 ruby optional 
ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY3F1rwAKCRBSaZq2P58r
wyIJAPwIGZQf8pnFLuNHoJwq11Vein14XxvblDpJRuWbiyVniQD/S2+JouQhLsHq
3NuldqDjda5/b8uRB6fM9TZ26UQBdgE=
=5CHT
-END PGP SIGNATURE End Message ---

Bug#1024038: consensuscore FTBFS: command class must subclass Command

[Adrian Bunk]

Source: consensuscore
Version: 1.1.1+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=consensuscore=amd64=1.1.1%2Bdfsg-3%2Bb3=1668361931=0

...
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3.11 setup.py build 
/<>/setup.py:4: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.command.build import build as _build
/<>/setup.py:6: DeprecationWarning: The distutils.sysconfig module 
is deprecated, use sysconfig instead
  from distutils import sysconfig
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
Distutils was imported before Setuptools, but importing Setuptools also 
replaces the `distutils` module in `sys.modules`. This may lead to undesirable 
behaviors or errors. To avoid these issues, avoid using distutils directly, 
ensure that setuptools is installed in the traditional way (e.g. not an 
editable install), and/or make sure that setuptools is always imported before 
distutils.
  warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
WARNING: '' not a valid package name; please use only .-separated package names 
in setup.py
Traceback (most recent call last):
  File "/<>/setup.py", line 96, in 
setup(name="ConsensusCore",
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
172, in setup
ok = dist.parse_command_line()
 ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
474, in parse_command_line
args = self._parse_command_opts(parser, args)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class  
must subclass Command
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.11 setup.py build 
I: pybuild base:240: /usr/bin/python3 setup.py build 
/<>/setup.py:4: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.command.build import build as _build
/<>/setup.py:6: DeprecationWarning: The distutils.sysconfig module 
is deprecated, use sysconfig instead
  from distutils import sysconfig
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
Distutils was imported before Setuptools, but importing Setuptools also 
replaces the `distutils` module in `sys.modules`. This may lead to undesirable 
behaviors or errors. To avoid these issues, avoid using distutils directly, 
ensure that setuptools is installed in the traditional way (e.g. not an 
editable install), and/or make sure that setuptools is always imported before 
distutils.
  warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
WARNING: '' not a valid package name; please use only .-separated package names 
in setup.py
Traceback (most recent call last):
  File "/<>/setup.py", line 96, in 
setup(name="ConsensusCore",
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
172, in setup
ok = dist.parse_command_line()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
474, in parse_command_line
args = self._parse_command_opts(parser, args)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class  
must subclass Command
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.10" 
returned exit code 13
make: *** [debian/rules:12: binary-arch] Error 25

Bug#1019647: marked as done (ruby-power-assert: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 22:22:00 +
with message-id 
and subject line Bug#1019647: fixed in ruby-power-assert 2.0.2-1
has caused the Debian Bug report #1019647,
regarding ruby-power-assert: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
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.)


-- 
1019647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-power-assert
Version: 1.1.7-2
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 ruby-power-assert with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-power-assert/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"power_assert\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-power-assert/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-power-assert/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/block_test.rb" "test/dyna_symbol_key_test.rb" "test/parser_test.rb" 
> "test/safe_op_test.rb" "test/trace_test.rb" "test/test_core_ext_helper.rb" 
> "test/test_helper.rb" -v
> Loaded suite 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader
> Started
> TestBlockContext: 
>   test_assertion_message_with_string: .: (0.014455)
>   test_colorized_pp[_colorize_message/_use_pp]:   .: (0.010077)
>   test_colorized_pp[_colorize_message]:   .: (0.006736)
>   test_colorized_pp[_use_pp]: .: (0.001601)
>   test_workaround_for_bug11182:   .: (0.56)
>   test_workaround_for_ruby_2_2:   .: (0.001612)
>   alias_method: 
> test: /<>/test/block_test.rb --location 400 :.: 
> (0.001681)
> test: /<>/test/block_test.rb --location 411 :.: 
> (0.001549)
>   assertion_message: 
> test: /<>/test/block_test.rb --location 105 :.: 
> (0.001161)
> test: /<>/test/block_test.rb --location 111 :.: 
> (0.001391)
> test: /<>/test/block_test.rb --location 120 :.: 
> (0.001416)
> test: /<>/test/block_test.rb --location 131 :.: 
> (0.001413)
> test: /<>/test/block_test.rb --location 140 :.: 
> (0.001622)
> test: /<>/test/block_test.rb --location 154 :.: 
> (0.001533)
> test: /<>/test/block_test.rb --location 167 :.: 
> (0.001718)
> test: /<>/test/block_test.rb --location 185 :.: 
> (0.001369)
> test: /<>/test/block_test.rb --location 195 :.: 
> (0.001439)
> test: /<>/test/block_test.rb --location 207 :.: 
> (0.001403)
> test: /<>/test/block_test.rb --location 218 :.: 
> (0.001576)
> test: /<>/test/block_test.rb --location 233 :.: 
> (0.001481)
> test: /<>/test/block_test.rb --location 244 :.: 
> (0.002198)
> test: /<>/test/block_test.rb --location 254 :.: 
> (0.002909)
> test: /<>/test/block_test.rb --location 264 :.: 
> (0.001618)
> test: /<>/test/block_test.rb --location 313 :.: 
> (10.007866)
> test: /<>/test/block_test.rb --location 335 :.: 
> (0.007029)
> test: /<>/test/block_test.rb --location 66 : .: (0.002944)
> test: /<>/test/block_test.rb 

Bug#1024037: pytaglib FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pytaglib
Version: 1.5.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pytaglib=1.5.0-2%2Bb1

...
src/taglib.cpp: In function ‘void __Pyx_AddTraceback(const char*, int, int, 
const char*)’:
src/taglib.cpp:463:62: error: invalid use of incomplete type ‘PyFrameObject’ 
{aka ‘struct _frame’}
  463 |   #define __Pyx_PyFrame_SetLineNumber(frame, lineno)  (frame)->f_lineno 
= (lineno)
  |  ^~
src/taglib.cpp:6507:5: note: in expansion of macro ‘__Pyx_PyFrame_SetLineNumber’
 6507 | __Pyx_PyFrame_SetLineNumber(py_frame, py_line);
  | ^~~
In file included from /usr/include/python3.11/Python.h:42,
 from src/taglib.cpp:23:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
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 

Bug#1024036: nipy FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: nipy
Version: 0.5.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=nipy=amd64=0.5.0-2%2Bb3=1668370732=0

...

Could not find datasource "nipy/templates" in data path 
"/usr/share/nipy:/usr/local/share/nipy:/<>/.pybuild/cpython3_3.10_nipy/.nipy";
 Is it possible you have not installed a data package?

You may need the package "nipy-templates"

You can download and install the package from:

http://nipy.org/data-packages/nipy-templates-0.2.tar.gz

Check the instructions in the ``doc/users/install_data.rst`` file in the nipy
source tree, or online at http://nipy.org/nipy/users/install_data.html

If you have the package, have you set the path to the package correctly?

Could not find datasource "nipy/data" in data path 
"/usr/share/nipy:/usr/local/share/nipy:/<>/.pybuild/cpython3_3.10_nipy/.nipy";
 Is it possible you have not installed a data package?

You may need the package "nipy-data"

You can download and install the package from:

http://nipy.org/data-packages/nipy-data-0.2.tar.gz

Check the instructions in the ``doc/users/install_data.rst`` file in the nipy
source tree, or online at http://nipy.org/nipy/users/install_data.html

If you have the package, have you set the path to the package correctly?
...

Bug#997877: marked as done (mailman3: autopkgtest needs update for new version of python-click: changed messages)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 22:05:01 +
with message-id 
and subject line Bug#997877: fixed in mailman3 3.3.7-1
has caused the Debian Bug report #997877,
regarding mailman3: autopkgtest needs update for new version of python-click: 
changed messages
to be marked as done.

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

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


-- 
997877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailman3
Version: 3.3.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-click

[X-Debbugs-CC: debian...@lists.debian.org, python-cl...@packages.debian.org]

Dear maintainer(s),

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

   passfail
python-click   from testing8.0.2-1
mailman3   from testing3.3.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It looks like
the messages from python-click became a bit more verbose and the
autopkgtest from mailman3 checks the messages verbatim.

Currently this regression is blocking the migration of python-click to
testing [1]. Of course, python-click shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-click was intended and your package needs to update to
the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-click should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

https://ci.debian.net/data/autopkgtest/testing/i386/m/mailman3/16216259/log.gz

==
FAIL: test_bad_filename
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.yd8254dv/downtmp/build.OCH/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 57, in test_bad_filename
self.assertEqual(
AssertionError: "Usag[110 chars]LENAME': 'bad': No such file or
directory\n" != "Usag[110 chars]LENAME': Could not open file: bad: No
such file or directory\n"
  Usage: syncmembers [OPTIONS] FILENAME LISTSPEC
  Try 'syncmembers --help' for help.
  - Error: Invalid value for 'FILENAME': 'bad': No such file or directory
?  ^   -
+ Error: Invalid value for 'FILENAME': Could not open file: bad: No such
file or directory
?  ^


==
FAIL: test_sync_delivery_bogus
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.yd8254dv/downtmp/build.OCH/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 372, in test_sync_delivery_bogus
self.assertEqual(
AssertionError: "Usag[123 chars]-d': 'bogus' is not one of 'regular',
'mime', [29 chars]'.\n" != "Usag[123 chars]-d': invalid choice: bogus.
(choose from regul[33 chars]d)\n"
  Usage: syncmembers [OPTIONS] FILENAME LISTSPEC
  Try 'syncmembers --help' for help.
  - Error: Invalid value for '--delivery' / '-d': 'bogus' is not one of
'regular', 'mime', 'plain', 'summary', 'disabled'.
?   ^ ^^^ ^^ ^^
  -  --  - -  -   -  -^^
+ Error: Invalid value for '--delivery' / '-d': invalid choice: bogus.
(choose from regular, mime, plain, summary, disabled)
?   
^^^  ^^   ^


==
FAIL: test_bad_filename

Bug#996806: marked as done (mailmain3: Expected test results for arc_validate tests need updating)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 22:05:01 +
with message-id 
and subject line Bug#996806: fixed in mailman3 3.3.7-1
has caused the Debian Bug report #996806,
regarding mailmain3: Expected test results for arc_validate tests need updating
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.)


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

mailman3 now fails tests with authheaders 0.14.1 since support for
comments in ARC results was added.  Although this isn't precisely an
FTBFS, a autopkgtest failure has similar effects.

Please update the expected results as this not an authheaders error.

==
FAIL: test_authentication_whitelist_hit 
(mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py",
 line 238, in test_authentication_whitelist_hit
self.assertEqual(msg["Authentication-Results"], ''.join(res))
AssertionError: 'exam[50 chars]ss header.d=valimail.com; arc=none (Message is 
not ARC signed)' != 'exam[50 chars]ss header.d=valimail.com; arc=none'
- example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass 
header.d=valimail.com; arc=none (Message is not ARC signed)
?   
  
+ example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass 
header.d=valimail.com; arc=none


==
FAIL: test_authentication_whitelist_miss 
(mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py",
 line 279, in test_authentication_whitelist_miss
self.assertEqual(msg["Authentication-Results"],
AssertionError: 'test[13 chars]ss header.d=valimail.com; arc=none (Message is 
not ARC signed)' != 'test[13 chars]ss header.d=valimail.com; arc=none'
- test.com; dkim=pass header.d=valimail.com; arc=none (Message is not ARC 
signed)
?

+ test.com; dkim=pass header.d=valimail.com; arc=none


==
FAIL: test_chain_validation_fail 
(mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py",
 line 195, in test_chain_validation_fail
self.assertEqual(msg["Authentication-Results"], ''.join(res))
AssertionError: 'list[94 chars] arc=fail (Most recent ARC-Message-Signature did 
not validate)' != 'list[94 chars] arc=fail'
- lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass 
header.i=@d1.example; dmarc=pass; arc=fail (Most recent ARC-Message-Signature 
did not validate)
?   
 
-
+ lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass 
header.i=@d1.example; dmarc=pass; arc=fail


--

Scott K
--- End Message ---
--- Begin Message ---
Source: mailman3
Source-Version: 3.3.7-1
Done: Pierre-Elliott Bécue 

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

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

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated mailman3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it 

Bug#995779: marked as done (autopkgtest fails with sqlalchemy 1.4.23+ds1)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 22:05:01 +
with message-id 
and subject line Bug#995779: fixed in mailman3 3.3.7-1
has caused the Debian Bug report #995779,
regarding autopkgtest fails with sqlalchemy 1.4.23+ds1
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.)


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

Hi,

As per this log:

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mailman3/15788073/log.gz

Mailman 3 fails with SQLA 1.4. Please fix this.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: mailman3
Source-Version: 3.3.7-1
Done: Pierre-Elliott Bécue 

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

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

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated mailman3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 22:48:39 +0100
Source: mailman3
Architecture: source
Version: 3.3.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team 
Changed-By: Pierre-Elliott Bécue 
Closes: 987592 995779 996806 997877 1010769 1015989 1023976
Changes:
 mailman3 (3.3.7-1) unstable; urgency=medium
 .
   [ Pierre-Elliott Bécue ]
   * New upstream release 3.3.7
 - Updated patches
 - Closes: #1010769, #995779, #996806, #1023976, #1015989, #997877
   * d/copyright: update years
   * d/control:
 - Bump debhelper-compat version to 13
 - Bump Standards-Version to 4.6.1
   * d/mailman3.lintian-overrides: updated
 .
   [ Camaleón ]
   * Add Spanish translation (Closes: #987592)
Checksums-Sha1:
 861b7952bed91bbc9410e24dd54c9e81ec42d9b7 3017 mailman3_3.3.7-1.dsc
 3f5c2812b518ae798108b7e1df1c084d28312cfa 1661573 mailman3_3.3.7.orig.tar.gz
 6324e1cf9088a23a911255770cb8dd754eec53da 833 mailman3_3.3.7.orig.tar.gz.asc
 9b561c6fcd54a49b45a10f4323f48115e5a6e526 26736 mailman3_3.3.7-1.debian.tar.xz
 dea425ee56ce81b5aecafaa65b0cf32931efc56a 10031 mailman3_3.3.7-1_amd64.buildinfo
Checksums-Sha256:
 67dfa5439ffbd83dda915d400c412ccde8b32ad005688f50fcb767aeacd1635f 3017 
mailman3_3.3.7-1.dsc
 e4c19b89ac3bd01ac1f96ab0fb587d51fdf6a73b1d76db4bc3252c79a20810c6 1661573 
mailman3_3.3.7.orig.tar.gz
 351339538894d858178dfc9944fbda3059a8b4113a21407c7aff14f999ecd2d0 833 
mailman3_3.3.7.orig.tar.gz.asc
 b65e8f418cf619c703a773b6073024bc95329da7decde3efe851e034fc1298a7 26736 
mailman3_3.3.7-1.debian.tar.xz
 926a0c00de70761e03321bbc8bb2e702098117f0e413aee9fd82da9d9f71424b 10031 
mailman3_3.3.7-1_amd64.buildinfo
Files:
 2d8f619700e72382e8882dd057cc0dcc 3017 mail optional mailman3_3.3.7-1.dsc
 6a92c9913a3bbed4104147dbd7ec654a 1661573 mail optional 
mailman3_3.3.7.orig.tar.gz
 9e3823f2f9bd39b01ead745ea9d728e8 833 mail optional 
mailman3_3.3.7.orig.tar.gz.asc
 c4f13dfb0ee88d2cd5ba20c45bcef44b 26736 mail optional 
mailman3_3.3.7-1.debian.tar.xz
 b0ec0dc243f748ba6472bbdcbb1503a5 10031 mail optional 
mailman3_3.3.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA8FiEE5CQeth7uIW7ehIz87iFbn7jEWwsFAmNxZuseHHBpZXJyZS1l
bGxpb3R0LmJlY3VlQGlucmlhLmZyAAoJEO4hW5+4xFsL1OMP+Kupz0Dg2ZBWYh+A
SWPVv1jkcr6Ut6NMifRy962uk6byMzyOeBYjy0/FmrXxwvBCLvmigoWrM80WWAqD
KdMCA0/717R3LU+T0o1VuZyBrirGhWmYXy1ABIcChVKau70NsaOde6M1oTXTcPzI
X7pG+OczaVD9xJ3DqGEkcMagKUZYZW8GHxDNbspH56TSAyuEB27LB0zviC2MR7N6
LvBfgDtih4dDDPOlVdt1ei8+cb8EN0Vod52DTRNmK8LgN9AtqR/eqKURz2CH650h
P4wxaak7bYmEI1JkdUTW9QwCZUeMTf0BnlwxAnhp9QSI0UaffMxmxDAvtrnQOu6C
GnhBZtTshvwFWpZwCFnBlZB5wNwli8wAxcHNCL90KWbcxu/aPeFWyGsWZ+0IuSp5
eRxqwxopmPhibR/Vpc/IHDz46j+JzTGYSr4uChw9zGV92Bj7NMvWiSHxOpFIIS94
CLPujPQdqCSYrNBw4UVAEQ75QGOqes7S6RksE6Pfeps8oXup0128nJGeWiGYtauz
aRfCZWrys/isBl4H3Mo+8rKVEyy8s9NawUM6BFXfXlqhr3gKwa7YWiWeKOsfgRce
1gIITue68Jo4lpYziXqTpooUqXxfipohUie1CMLLcLfNO+qKKxJuU7SgBUhermSX
HZnzA1b7ORsaxmGbovLUb9YfD4s=
=nP2Z
-END PGP SIGNATURE End Message ---

Bug#1024035: pycifrw FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pycifrw
Version: 4.4.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pycifrw=4.4.4-1%2Bb2

...
ERROR: 
/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_lex.py:163:
 Invalid regular expression for rule 't_ELSEIF'. global flags not at the start 
of the expression at position 13
...
==
ERROR: testMandatory (TestPyCIFRW.DDLmDicTestCase.testMandatory)
Test that missing mandatory items are found
--
Traceback (most recent call last):
  File "/<>/TestPyCIFRW.py", line 1729, in setUp
self.refdic = CifFile.CifDic('dictionaries/ddl.dic',grammar='auto')
  ^
  File 
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
 line 363, in __init__
self.initialise_drel()
  File 
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
 line 1392, in initialise_drel
self.transform_drel()   #parse the drel functions
^
  File 
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/CifFile_module.py",
 line 1396, in transform_drel
from .drel import drel_ast_yacc
  File 
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_ast_yacc.py",
 line 16, in 
from .drel_lex import lexer,tokens
  File 
"/<>/.pybuild/cpython3_3.11_pycifrw/build/CifFile/drel/drel_lex.py",
 line 226, in 
lexer = lex.lex(reflags=re.MULTILINE)
^
  File "/usr/lib/python3/dist-packages/ply/lex.py", line 916, in lex
raise SyntaxError("Can't build lexer")
SyntaxError: Can't build lexer

==
...
Ran 182 tests in 72.458s

FAILED (errors=34, skipped=1)

Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest

[Arthur de Jong]

On Sun, 2022-10-23 at 14:50 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

A fix has just been uploaded and is part of version 1.18-1.

If this ever needs to be backported for some reason the fix is trivial:
https://arthurdejong.org/git/python-stdnum/commit/?id=1003033fa0e97726d92f47231f96cf02fb35869a

-- 
-- arthur - art...@arthurdejong.org - https://arthurdejong.org/ --



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

Bug#1023995: starpu-contrib: requires rebuild for freeglut transition

[Samuel Thibault]

Hello,

Sebastian Ramacher, le dim. 13 nov. 2022 18:14:54 +0100, a ecrit:
> starpu-contrib requires a rebuild for the freeglut transition, but is
> not auto-buildable. Please upload a rebuild.

I have uploaded the rebuild.

Samuel

Bug#997877: marked as pending in mailman3

[Pierre-Elliott Bécue]

Control: tag -1 pending

Hello,

Bug #997877 in mailman3 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/mailman-team/mailman3/-/commit/f067c43715a74425d6441e643a664685e9bcbc1f


New upstream release 3.3.7

 - Updated patches

Closes: #1010769, #995779, #996806, #1023976, #1015989, #997877


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997877

Processed: Bug#997877 marked as pending in mailman3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997877 [src:mailman3] mailman3: autopkgtest needs update for new version 
of python-click: changed messages
Added tag(s) pending.

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

Bug#1024034: pynfft FTBFS: command class must subclass Command

[Adrian Bunk]

Source: pynfft
Version: 1.3.2-6
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pynfft=1.3.2-6%2Bb1

...
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean 
/<>/setup.py:99: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.core import Command
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
Distutils was imported before Setuptools, but importing Setuptools also 
replaces the `distutils` module in `sys.modules`. This may lead to undesirable 
behaviors or errors. To avoid these issues, avoid using distutils directly, 
ensure that setuptools is installed in the traditional way (e.g. not an 
editable install), and/or make sure that setuptools is always imported before 
distutils.
  warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
/<>/setup.py:219: DeprecationWarning: the imp module is deprecated 
in favour of importlib and slated for removal in Python 3.12; see the module's 
documentation for alternative uses
  import imp
Traceback (most recent call last):
  File "/<>/setup.py", line 314, in 
setup_package()
  File "/<>/setup.py", line 310, in setup_package
setup(**setup_args)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
172, in setup
ok = dist.parse_command_line()
 ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
474, in parse_command_line
args = self._parse_command_opts(parser, args)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
540, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class  must subclass Command
E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.10" 
returned exit code 13
make: *** [debian/rules:9: clean] Error 25

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

[Reinhard Tartler]

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

Bug#1022311: marked as done (python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 21:24:22 +
with message-id 
and subject line Bug#1022311: fixed in python-stdnum 1.18-1
has caused the Debian Bug report #1022311,
regarding python-stdnum: FTBFS: AssertionError: Failed doctest test for 
test_no_fodselsnummer.doctest
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.)


-- 
1022311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-stdnum
Version: 1.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args='TZ=Europe/Amsterdam 
> {interpreter} setup.py nosetests'
> I: pybuild base:240: TZ=Europe/Amsterdam python3.10 setup.py nosetests
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running nosetests
> running egg_info
> writing python_stdnum.egg-info/PKG-INFO
> writing dependency_links to python_stdnum.egg-info/dependency_links.txt
> writing requirements to python_stdnum.egg-info/requires.txt
> writing top-level names to python_stdnum.egg-info/top_level.txt
> reading manifest file 'python_stdnum.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> writing manifest file 'python_stdnum.egg-info/SOURCES.txt'
> nose.plugins.cover: ERROR: Coverage not available: unable to import coverage 
> module
> .SSS.S.SS...SS...F
> ==
> FAIL: Doctest: test_no_fodselsnummer.doctest
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/doctest.py", line 2221, in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
>   File "/<>/tests/test_no_fodselsnummer.doctest", line 0
> 
> --
> File "/<>/tests/test_no_fodselsnummer.doctest", line 94, in 
> test_no_fodselsnummer.doctest
> Failed example:
> fodselsnummer.validate('19102270846')
> Expected:
> Traceback (most recent call last):
> ...
> InvalidComponent: The birth date information is valid, but this person 
> has not been born yet.
> Got:
> '19102270846'
> 
> 
> --
> Ran 342 tests in 1.408s
> 
> FAILED (SKIP=8, failures=1)
> E: pybuild pybuild:379: test: plugin custom failed with: exit code=1: 
> TZ=Europe/Amsterdam python3.10 setup.py nosetests
> dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.10 
> --system=custom "--test-args=TZ=Europe/Amsterdam {interpreter} setup.py 
> nosetests" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-stdnum_1.17-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-stdnum
Source-Version: 1.18-1
Done: Arthur de Jong 

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

A summary of the changes between this version and the previous one 

Bug#1022285: marked as done (gnome-hwp-support: FTBFS: configure: error: Package requirements (libnautilus-extension libgsf-1) were not met)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 21:20:40 +
with message-id 
and subject line Bug#1022285: fixed in gnome-hwp-support 0.2.0-1
has caused the Debian Bug report #1022285,
regarding gnome-hwp-support: FTBFS: configure: error: Package requirements 
(libnautilus-extension libgsf-1) were not met
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.)


-- 
1022285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-hwp-support
Version: 0.1.6-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for xgettext... (cached) /usr/bin/xgettext
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for libgsf-1 gdk-pixbuf-2.0... yes
> checking for libnautilus-extension libgsf-1... no
> configure: error: Package requirements (libnautilus-extension libgsf-1) were 
> not met
> 
> No package 'libnautilus-extension' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables PROPERTIES_CFLAGS
> and PROPERTIES_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/gnome-hwp-support_0.1.6-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gnome-hwp-support
Source-Version: 0.2.0-1
Done: Changwoo Ryu 

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

Debian distribution maintenance software
pp.
Changwoo Ryu  (supplier of updated gnome-hwp-support package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Nov 2022 05:44:08 +0900
Source: gnome-hwp-support
Architecture: source
Version: 0.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Korean L10N 
Changed-By: Changwoo Ryu 
Closes: 1022285
Changes:
 gnome-hwp-support (0.2.0-1) unstable; urgency=medium
 .
   [ Changwoo Ryu ]
   * New upstream version (Closes: #1022285)
   * debian/watch: Updated to work with the github changes
   * debian/copyright: Updated
   * debian/control:
 - Use debhelper 13
 - Standards-Version: 4.6.1
 - Add Rules-Requires-Root
 - Update Build-Depends
   * debian/upstream/metadata: Set upstream metadata fields
   * debian/rules:
 - Install the nautilus properties page again
   * Add Salsa CI settings
Checksums-Sha1:
 ed190e302e6f7067c2ab2e43d0d77e55e0ce932d 2113 gnome-hwp-support_0.2.0-1.dsc
 0dd5122b94fd9a8473a489809bbae75240632044 21214 
gnome-hwp-support_0.2.0.orig.tar.gz
 20d5e2524c9afa02abb41975c5bb44b52408f4ff 2724 
gnome-hwp-support_0.2.0-1.debian.tar.xz
 638a6176ce59dcb7e7c325a4e6d7a50fcbebf395 15996 
gnome-hwp-support_0.2.0-1_source.buildinfo
Checksums-Sha256:
 65e418a0ddb366dad862a1ae164ab51594a3486898cfffc32ad929af283a6831 2113 
gnome-hwp-support_0.2.0-1.dsc
 4dd1ce5b717de2ac59aa34f9bc3e08bf3c67bb950511e48e2ddcf6d5ec590828 21214 
gnome-hwp-support_0.2.0.orig.tar.gz
 

Bug#1017711: marked as done (emacs-gtk: terminated with signal SIGABRT, 137 MB coredump)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 21:20:24 +
with message-id 
and subject line Bug#1017711: fixed in emacs 1:28.2+1-5
has caused the Debian Bug report #1017711,
regarding emacs-gtk: terminated with signal SIGABRT, 137 MB coredump
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.)


-- 
1017711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-gtk
Version: 1:28.1+1-1
Severity: important

I have noticed that Emacs left a 137 MB coredump.

gdb says:

Reading symbols from /usr/bin/emacs...
Reading symbols from 
/usr/lib/debug/.build-id/d0/b7c40dc33110b0623ea2ca797a6d3f3eb166b5.debug...
[New LWP 1483812]
[New LWP 1483816]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/emacs --batch -l 
/tmp/emacs-async-comp-cc-engine.el-2UV1nf.el'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
[Current thread is 1 (Thread 0x7fc24ae75380 (LWP 1483812))]

I've attached the full backtrace.

Note that I did not run "/usr/bin/emacs --batch -l ...".
I just ran "emacs".

The first time with Emacs 28, I got some ispell related errors, IIRC.
But this is not reproducible.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 emacs-gtk depends on:
ii  emacs-bin-common 1:28.1+1-1
ii  emacs-common 1:28.1+1-1
ii  libacl1  2.3.1-1
ii  libasound2   1.2.7.2-1
ii  libc62.34-4
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.0-2
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgccjit0   12.1.0-8
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgif7  5.2.1-2.5
ii  libglib2.0-0 2.72.3-1+b1
ii  libgmp10 2:6.2.1+dfsg1-1
ii  libgnutls30  3.7.7-2
ii  libgpm2  1.20.7-10
ii  libgtk-3-0   3.24.34-1
ii  libharfbuzz0b2.7.4-1+b1
ii  libice6  2:1.0.10-1
ii  libjansson4  2.14-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  liblcms2-2   2.13.1-1
ii  libm17n-01.8.0-4
ii  libotf1  0.9.16-3
ii  libpango-1.0-0   1.50.9+ds-1
ii  libpng16-16  1.6.37-5
ii  librsvg2-2   2.54.4+dfsg-1
ii  libselinux1  3.4-1+b1
ii  libsm6   2:1.2.3-1
ii  libsystemd0  251.4-1
ii  libtiff5 4.4.0-4
ii  libtinfo66.3+20220423-2
ii  libx11-6 2:1.8.1-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:6.0.0-1
ii  libxml2  2.9.14+dfsg-1+b1
ii  libxrender1  1:0.9.10-1.1
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages emacs-gtk recommends:
ii  fonts-noto-color-emoji  2.034-1

Versions of packages emacs-gtk suggests:
ii  emacs-common-non-dfsg  1:27.1+1-2

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Thread 2 (Thread 0x7fc2471e4640 (LWP 1483816)):
#0  0x7fc24befda3f in __GI___poll (fds=0x56167d88dc50, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1  0x7fc24f9c7dc6 in g_main_context_poll (priority=, 
n_fds=1, fds=0x56167d88dc50, timeout=, context=0x56167da7f450) 
at ../../../glib/gmain.c:4516
ret = 
errsv = 
poll_func = 0x7fc24f9d7600 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 1
allocated_nfds = 1
fds = 0x56167d88dc50
#2  g_main_context_iterate (context=context@entry=0x56167da7f450, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:4206

Bug#1019844: marked as done (golang-v2ray-core FTBFS: undefined: quic.Session)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 21:20:53 +
with message-id 
and subject line Bug#1019844: fixed in golang-v2ray-core 4.34.0-8
has caused the Debian Bug report #1019844,
regarding golang-v2ray-core FTBFS: undefined: quic.Session
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.)


-- 
1019844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-v2ray-core
Version: 4.34.0-7
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-v2ray-core=4.34.0-7%2Bb1

...
# v2ray.com/core/app/dns
src/v2ray.com/core/app/dns/nameserver_quic.go:41:19: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:319:22: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:328:45: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:329:19: undefined: quic.Session
src/v2ray.com/core/app/dns/nameserver_quic.go:362:46: undefined: quic.Session
...
make[1]: *** [debian/rules:31: override_dh_auto_build] Error 25
--- End Message ---
--- Begin Message ---
Source: golang-v2ray-core
Source-Version: 4.34.0-8
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated golang-v2ray-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 12:46:24 -0800
Source: golang-v2ray-core
Architecture: source
Version: 4.34.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Roger Shimizu 
Closes: 1019844
Changes:
 golang-v2ray-core (4.34.0-8) unstable; urgency=medium
 .
   * debian/patches:
 - Cherry pick from upstream to fix quic issue (Closes: #1019844).
Checksums-Sha1:
 198a4374e3e91fb43978531f40202ea0108c6ca0 2595 golang-v2ray-core_4.34.0-8.dsc
 7da5849e848a322a51383412470222ef6225135f 21132 
golang-v2ray-core_4.34.0-8.debian.tar.xz
 dc95e96b76f5e4c8200cb2c8c48b1f143f1fa4c7 10109 
golang-v2ray-core_4.34.0-8_amd64.buildinfo
Checksums-Sha256:
 d86d5d4e5808d4218a7b7eae04f45763a3901de197159af063d96c2c7c9ce1c2 2595 
golang-v2ray-core_4.34.0-8.dsc
 1cffb15ae0f72516bee257181520333621d655052d2c87525901835a9bdaa3ed 21132 
golang-v2ray-core_4.34.0-8.debian.tar.xz
 5cb750707b060f77377634b7bf331090e6454f678660d6f4adf816f7f0970fac 10109 
golang-v2ray-core_4.34.0-8_amd64.buildinfo
Files:
 7afcc8751cf04da0c7f5ed54bc80a27b 2595 devel optional 
golang-v2ray-core_4.34.0-8.dsc
 3a19cff37815fcd4b700e875d7efa94f 21132 devel optional 
golang-v2ray-core_4.34.0-8.debian.tar.xz
 bf26b8d79eb41f1be3a29d9454e1ccd4 10109 devel optional 
golang-v2ray-core_4.34.0-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAmNxWmQQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qGJoD/9EZ+Xquci61fp5ygkkl7lPSo40k5Qc4Usz
8CtDUQvXhT0sOo0dGEkLGMIFqMnDzyfbpA9bCX1t8NgFqHhfIPCL/O/vDDcGNuZQ
+iI4/RQSD2XMx+01qEaMajS4P7Ef4oR/g8mnq4vTM+VG49U6jNb9LQv75EILvbET
otaANmHKgoWb4LkNUP0giQGr/5vJ1jmvjp0rhqIR0lMGkXa7C8m+kuRoz2qtQhcI
RuQ6MsPszwhBEkuy6rdLu1+fygShBLeFyJ65oK9n6uPLKRjo7fNJU5x1JW8gnjUt
cyBUjv4cz3SxmpZ2OtUD/CtwKZmDKlWlLPZ3deXmDc0r9FMU6G75ONJtEUBZudfC
cX+NI3NIzuHN9BGe91jt86VQcpk2AEW1OT4EogZ1mZvSKsg6q8nAsNYECBdZvVCm
ArRLxXW93UgFU6C09J3h7oBB5aClfs5KUqyIYG/yn/k2M4jyuClA/DADrfRI/HT8
OmvW4hRBMR6VwOfOwzsxy26zjz5jXCkzv/2vlTvtpJZIPdlgI0RWqq3MFetCtTDT
B3vlv+P9EiLaG3M7aYQOTWQUyoAMCp7X/YO+vTUKhleNBr0pGxGZ06Y4GjS8nTVx
lZTIVV4+apL61MrCYB1yDp4ecPLCeCI+u34FLVvjGwuwSQtcMZzQ5xOifCgTSTXQ
stf9EY5+vQ==
=YNML
-END PGP SIGNATURE End Message ---

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

On Sat, Nov 12, 2022 at 03:11:49PM +0300, программист некто wrote:
>Hello. I rebuilt and tested grub only with patch
>0087-fs-f2fs-Do-not-read-past-the-end-of-nat-journal-entr.patch
>Result: error: unknown filesystem.

Yay! Thanks very much for following up on this. I'll raise this with
upstream. Are you happy for me to CC you on that discussion too?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone

Bug#1024031: numba FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: numba
Version: 0.56.2+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=numba=0.56.2%2Bdfsg-2%2Bb1

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean 
Traceback (most recent call last):
  File "/<>/setup.py", line 52, in 
_guard_py_ver()
  File "/<>/setup.py", line 49, in _guard_py_ver
raise RuntimeError(msg.format(cur_py, min_py, max_py))
RuntimeError: Cannot install on Python version 3.11.0; only versions 
>=3.7,<3.11 are supported.

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Sean Whitton]

Hello,

On Sat 12 Nov 2022 at 02:55AM +01, Vincent Lefevre wrote:

> Hi,
>
> On 2022-11-11 11:32:33 -0700, Sean Whitton wrote:
>> On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:
>> > On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
>> >> Are you able to test the patch?  Let me know if you need help getting an
>> >> installable .deb.  Thanks.
>> >
>> > Sorry, I couldn't test it yet, first because of an uninstallable
>> > package needed for the build because I couldn't upgrade libc6 yet
>> > and I couldn't get the previous version from snapshot.debian.org
>> > (bug 1023540). Now that I could upgrade libc6, I'll be able to
>> > test when I have some time, but perhaps not before the week-end.
>>
>> Okay, do let me know if I can help -- this is blocking Emacs from migrating.
>
> I've rebuilt the packages with the patch and couldn't reproduce
> the bug yet. So it may be the correct fix.

Many thanks for testing, and Eli and Paul for the patch.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023868: marked as done (caja-seahorse: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... failed])

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 20:49:38 +
with message-id 
and subject line Bug#1023868: fixed in caja-seahorse 1.18.5-2
has caused the Debian Bug report #1023868,
regarding caja-seahorse: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for 
gpgme-config... failed]
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.)


-- 
1023868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: caja-seahorse
Version: 1.18.5-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello,

caja-seahorse FTBFS due to removal of gpgme-config. Since caja-seahorse
already requires pkgconfig you can simply use this for gpgme, too.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru caja-seahorse-1.18.5/debian/changelog caja-seahorse-1.18.5/debian/changelog
--- caja-seahorse-1.18.5/debian/changelog	2020-08-24 10:00:41.0 +0200
+++ caja-seahorse-1.18.5/debian/changelog	2022-11-11 18:45:09.0 +0100
@@ -1,3 +1,11 @@
+caja-seahorse (1.18.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * 1010_gpgme_pkgconfig.diff: Use pkgconfig to locate gpgme instead of
+gpgme-config fixing FTBFS with libgpgme-dev >= 1.18.0-2.
+
+ -- Andreas Metzler   Fri, 11 Nov 2022 18:45:09 +0100
+
 caja-seahorse (1.18.5-1) unstable; urgency=medium
 
   [ Simon Quigley ]
diff -Nru caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff
--- caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff	1970-01-01 01:00:00.0 +0100
+++ caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff	2022-11-11 18:45:09.0 +0100
@@ -0,0 +1,54 @@
+Description: Use pkgconfig to locate gpgme instead of gpgme-config.
+Author: Andreas Metzler 
+Origin: vendor
+Last-Update: 2022-11-11
+
+--- a/configure.ac
 b/configure.ac
+@@ -85,45 +85,11 @@
+ 	else
+ 		AC_MSG_ERROR([Appropriate version of GnuPG not found. Please install one of versions: $accepted_versions])
+ 	fi
+ fi
+ 
+-ok="no"
+-min_gpgme_version=1.0.0
+-AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed")
+-if test $GPGME_CONFIG != "failed" ; then
+-	AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version)
+-	req_major=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-	req_minor=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
+-	req_micro=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
+-	gpgme_config_version=`$GPGME_CONFIG --version`
+-	major=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
+-	minor=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
+-	micro=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
+-
+-	if test "$major" -eq "$req_major"; then
+-		if test "$minor" -ge "$req_minor"; then
+-			if test "$micro" -ge "$req_micro"; then
+-ok="yes"
+-			fi
+-		fi
+-	fi
+-fi
+-
+-if test $ok = "yes"; then
+-	GPGME_CFLAGS=`$GPGME_CONFIG --cflags`
+-	GPGME_LIBS=`$GPGME_CONFIG --libs`
+-	AC_MSG_RESULT(yes)
+-else
+-	AC_MSG_ERROR(GPGME $min_gpgme_version or later needed)
+-fi
++PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0])
+ 
+ SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS"
+ SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS"
+ 
+ # -
diff -Nru caja-seahorse-1.18.5/debian/patches/series caja-seahorse-1.18.5/debian/patches/series
--- caja-seahorse-1.18.5/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ caja-seahorse-1.18.5/debian/patches/series	2022-11-11 18:43:29.0 +0100
@@ -0,0 +1 @@
+1010_gpgme_pkgconfig.diff
--- End Message ---
--- Begin Message ---
Source: caja-seahorse
Source-Version: 1.18.5-2
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
caja-seahorse, 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.
Mike Gabriel  (supplier of updated 

Bug#1024003: src:elpi: fails to migrate to testing for too long: make reverse (test) dependencies uninstallable

[julien . puydt]

Le dimanche 13 novembre 2022 à 19:08 +0100, Paul Gevers a écrit :
> Source: elpi
> Version: 1.16.5-1
> Severity: serious
> Control: close -1 1.16.7-2
> Tags: sid bookworm
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
> 
> Dear maintainer(s),
> 
> The Release Team considers packages that are out-of-sync between
> testing and unstable for more than 60 days as having a Release
> Critical bug in testing [1]. Your package src:elpi has been trying to
> migrate for 62 days [2]. Hence, I am filing this bug. I think
> something went wrong with the rebuilds (or the order of them or
> something), because elpi can't migrate because it would make libcoq-
> elpi on armhf not installable and  libcoq-elpi in unstable can't
> migrate because two reverse test dependencies fail to install during
> autopkgtesting on armhf.

I have filed bugs to get those armhf binary packages removed last
tuesday ; I expect they'll go away soon enough.

I waited too long for elpi's upstream to fix the arch-issues before
disabling them... sorry.

Hopefully things will go smooth afterwards.

Thanks,

J.Puydt

Bug#1024026: libgetdata FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: libgetdata
Version: 0.11.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libgetdata=amd64=0.11.0-4%2Bb2=1668369340=0

...
   dh_missing -a
dh_missing: warning: 
usr/local/lib/python3.11/dist-packages/pygetdata.cpython-311-x86_64-linux-gnu.so
 exists in debian/tmp but is not installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_fortran_mod: libgetdata-dev (1)
 * dh_install: libf95getdata7 (2), libfgetdata6 (2), libgetdata++7 (2), 
libgetdata-dev (27), libgetdata-doc (191), libgetdata-perl (1), 
libgetdata-tools (4), libgetdata8 (2), python3-pygetdata (1)
 * dh_installdocs: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7 
(0), libgetdata-dev (0), libgetdata-doc (3), libgetdata-perl (0), 
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
 * dh_installman: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7 
(0), libgetdata-dev (0), libgetdata-doc (0), libgetdata-perl (0), 
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.

Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:28: binary-arch] Error 25

Bug#1022527: ddupdate: diff for NMU version 0.6.6-1.2

[Alec Leamas]

Hi again,

On Sun, 13 Nov 2022 09:47:03 +0100 Alec Leamas  
wrote:


Thanks for taking care of this! That said, could you please delay this a 
little longer so I can make a regular release instead, avoiding an in my 
eyes somewhat painful NMU?




I have committed your patch upstream in your name [1], I hope it's ok. 
New release is pending on mentors [2]


--alec

[1] https://github.com/leamas/ddupdate/commit/a480bd9e5cdae
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024025

Processed: tagging 1024016

[Debian Bug Tracking System]

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

> tags 1024016 + upstream
Bug #1024016 [src:mysql-8.0] mysql-8.0: CVE-2022-39400 CVE-2022-39402 
CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 
CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21625 
CVE-2022-21632 CVE-2022-21633 CVE-2022-21637 CVE-2022-21640
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1012226: unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused

[Paul Gevers]

Control: tag -1 patch

On Wed, 01 Jun 2022 21:50:33 +0200 Paul Gevers  wrote:

unattended-upgrades showed up in the stable-proposed queue viewer [1]
because it appears to regress with the new xz-utils. However,
inspecing other failures in other suites, I think the test doesn't
behave well in archives where there are more than one version of
src:linux available. This happens regularly in pure unstable, in
unstable-to-testing and in stable-proposed-to-stable testing.

Can you please have a look? 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.


Looking at the error messages I think this is due to bug 983363 which 
isn't related to qemu, but the fact that the regexp for the running 
kernel in the test isn't closed, so it also matches the -dbg and 
-unsigned package with the same name.


Attached is a patch that fixes that part of the issue. I must confess 
that I don't fully grasp why this isn't always a problem (e.g. now on 
arm64/stable), but on my current bookworm amd64 system the test fails 
without this patch and passes with the patch.


Paul
From 6301dc299b6167db00881f9d1cb3b80adf28ad13 Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Sun, 13 Nov 2022 20:19:12 +0100
Subject: [PATCH] test: don't confuse -dbg and -unsigned with current running
 kernel

Closes: #983363, #1012226
---
 test/autopkgtest_kernel_patterns.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/autopkgtest_kernel_patterns.py b/test/autopkgtest_kernel_patterns.py
index 111c72d..f0ce3c5 100755
--- a/test/autopkgtest_kernel_patterns.py
+++ b/test/autopkgtest_kernel_patterns.py
@@ -18,7 +18,7 @@ class TestKernelPatterns(unittest.TestCase):
 running_regexp = running_kernel_pkgs_regexp()
 running_kernel_version = subprocess.check_output(
 ["uname", "-r"], universal_newlines=True).rstrip()
-running_escaped_regexp = ".*" + re.escape(running_kernel_version)
+running_escaped_regexp = ".*" + re.escape(running_kernel_version) + '$'
 try:
 running_noflavor_regexp = "linux.*-" + re.escape(
 re.match("[1-9][0-9]*\\.[0-9]+\\.[0-9]+-[0-9]+",
-- 
2.35.1



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1012226 [src:unattended-upgrades] unattended-upgrades: flaky autopkgtest: 
kernel-patterns seems to regularly get confused
Added tag(s) patch.

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

Processed: tagging 1024021

[Debian Bug Tracking System]

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

> tags 1024021 + upstream
Bug #1024021 [src:netatalk] netatalk: CVE-2022-45188
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1024016: mysql-8.0: CVE-2022-39400 CVE-2022-39402 CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21

[Robie Basak]

On Sun, Nov 13, 2022 at 08:31:24PM +0100, Moritz Mühlenhoff wrote:
> The following vulnerabilities were published for mysql-8.0.

FTR, an update to 8.0.31 to fix these is already prepared and being
tested at
https://salsa.debian.org/mariadb-team/mysql/-/merge_requests/65


signature.asc
Description: PGP signature

Bug#1024021: netatalk: CVE-2022-45188

[Moritz Mühlenhoff]

Source: netatalk
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for netatalk.

CVE-2022-45188[0]:
| Netatalk through 3.1.13 has an afp_getappl heap-based buffer overflow
| resulting in code execution via a crafted .appl file. This provides
| remote root access on some platforms such as FreeBSD (used for
| TrueNAS).

https://rushbnt.github.io/bug%20analysis/netatalk-0day/

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-45188
https://www.cve.org/CVERecord?id=CVE-2022-45188

Please adjust the affected versions in the BTS as needed.

Bug#1024019: iminuit FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: iminuit
Version: 2.11.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=iminuit=2.11.2-2%2Bb2

...
In file included from 
/<>/extern/pybind11/include/pybind11/cast.h:16,
 from 
/<>/extern/pybind11/include/pybind11/attr.h:13,
 from 
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
 from /<>/src/application.cpp:3:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In 
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
 error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  482 | frame = frame->f_back;
  |  ^~
In file included from /usr/include/python3.11/Python.h:42,
 from 
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
 from 
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
 from 
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
In file included from 
/<>/extern/pybind11/include/pybind11/cast.h:16,
 from 
/<>/extern/pybind11/include/pybind11/attr.h:13,
 from 
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
 from 
/<>/extern/pybind11/include/pybind11/numpy.h:12,
 from /<>/src/type_caster.hpp:2,
 from /<>/src/fcn.cpp:2:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In 
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
 error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  482 | frame = frame->f_back;
  |  ^~
In file included from /usr/include/python3.11/Python.h:42,
 from 
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
 from 
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
 from /<>/src/fcn.hpp:2,
 from /<>/src/fcn.cpp:1:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
In file included from 
/<>/extern/pybind11/include/pybind11/cast.h:16,
 from 
/<>/extern/pybind11/include/pybind11/attr.h:13,
 from 
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
 from /<>/src/contours.cpp:5:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In 
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
 error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  482 | frame = frame->f_back;
  |  ^~
In file included from /usr/include/python3.11/Python.h:42,
 from 
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
 from 
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
 from 
/<>/extern/pybind11/include/pybind11/cast.h:13:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
In file included from 
/<>/extern/pybind11/include/pybind11/cast.h:16,
 from 
/<>/extern/pybind11/include/pybind11/attr.h:13,
 from 
/<>/extern/pybind11/include/pybind11/pybind11.h:13,
 from 
/<>/extern/pybind11/include/pybind11/operators.h:12,
 from /<>/src/functionminimum.cpp:9:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h: In 
function ‘std::string pybind11::detail::error_string()’:
/<>/extern/pybind11/include/pybind11/detail/type_caster_base.h:482:26:
 error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  482 | frame = frame->f_back;
  |  ^~
In file included from /usr/include/python3.11/Python.h:42,
 from 
/<>/extern/pybind11/include/pybind11/detail/common.h:209,
 from 
/<>/extern/pybind11/include/pybind11/pytypes.h:12,
 from /<>/src/fcn.hpp:2,
 from /<>/src/functionminimum.cpp:2:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
gmake[4]: *** [CMakeFiles/_core.dir/build.make:79: 
CMakeFiles/_core.dir/src/application.cpp.o] Error 1
gmake[4]: *** Waiting for unfinished jobs
gmake[4]: *** [CMakeFiles/_core.dir/build.make:93: 
CMakeFiles/_core.dir/src/contours.cpp.o] Error 1
gmake[4]: *** 

Bug#1024016: mysql-8.0: CVE-2022-39400 CVE-2022-39402 CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21

[Moritz Mühlenhoff]

Source: mysql-8.0
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for mysql-8.0.

CVE-2022-39400[0]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows high privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2022-39402[1]:
| Vulnerability in the MySQL Shell product of Oracle MySQL (component:
| Shell: Core Client). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows unauthenticated
| attacker with logon to the infrastructure where MySQL Shell executes
| to compromise MySQL Shell. While the vulnerability is in MySQL Shell,
| attacks may significantly impact additional products (scope change).
| Successful attacks of this vulnerability can result in unauthorized
| read access to a subset of MySQL Shell accessible data. CVSS 3.1 Base
| Score 4.3 (Confidentiality impacts). CVSS Vector:
| (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).


CVE-2022-39403[2]:
| Vulnerability in the MySQL Shell product of Oracle MySQL (component:
| Shell: Core Client). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows low privileged
| attacker with logon to the infrastructure where MySQL Shell executes
| to compromise MySQL Shell. Successful attacks require human
| interaction from a person other than the attacker. Successful attacks
| of this vulnerability can result in unauthorized update, insert or
| delete access to some of MySQL Shell accessible data as well as
| unauthorized read access to a subset of MySQL Shell accessible data.
| CVSS 3.1 Base Score 3.9 (Confidentiality and Integrity impacts). CVSS
| Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N).


CVE-2022-39408[3]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows low privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).


CVE-2022-39410[4]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows low privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).


CVE-2022-21594[5]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Optimizer). Supported versions that are affected are 8.0.30
| and prior. Easily exploitable vulnerability allows high privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2022-21599[6]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| Server: Stored Procedure). Supported versions that are affected are
| 8.0.30 and prior. Easily exploitable vulnerability allows high
| privileged attacker with network access via multiple protocols to
| compromise MySQL Server. Successful attacks of this vulnerability can
| result in unauthorized ability to cause a hang or frequently
| repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score
| 4.9 (Availability impacts). CVSS Vector:
| (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).


CVE-2022-21604[7]:
| Vulnerability in the MySQL Server product of Oracle MySQL (component:
| InnoDB). Supported versions that are affected are 8.0.30 and prior.
| Easily exploitable vulnerability allows high privileged attacker with
| network access via multiple protocols to compromise MySQL Server.
| Successful attacks of this vulnerability can result in unauthorized
| ability to cause a hang or frequently repeatable crash (complete DOS)
| 

Bug#1024015: python-gevent FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-gevent
Version: 21.12.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-gevent=21.12.0-3%2Bb1

...
In file included from src/gevent/_greenlet_primitives.c:764:
/<>/deps/greenlet/greenlet.h:42:5: error: unknown type name 
‘CFrame’
   42 | CFrame* 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 

Bug#1023913: marked as done (sip4 FTBFS with Python 3.11 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 18:57:29 +
with message-id 
and subject line Bug#1023913: fixed in sip4 4.19.25+dfsg-5
has caused the Debian Bug report #1023913,
regarding sip4 FTBFS with Python 3.11 as supported version
to be marked as done.

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

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


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

https://buildd.debian.org/status/logs.php?pkg=sip4=4.19.25%2Bdfsg-4%2Bb1

...
/<>/siplib/siplib.c: In function ‘sip_api_get_frame’:
/<>/siplib/siplib.c:13750:22: error: invalid use of undefined type 
‘struct _frame’
13750 | frame = frame->f_back;
  |  ^~
...
--- End Message ---
--- Begin Message ---
Source: sip4
Source-Version: 4.19.25+dfsg-5
Done: Scott Talbert 

We believe that the bug you reported is fixed in the latest version of
sip4, 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.
Scott Talbert  (supplier of updated sip4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 13:36:22 -0500
Source: sip4
Architecture: source
Version: 4.19.25+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Scott Talbert 
Closes: 998897 1023913
Changes:
 sip4 (4.19.25+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS with Python 3.11 (Closes: #1023913)
   * Fix use-after-free bug in siplib (Closes: #998897)
Checksums-Sha1:
 804ae24a510b76a94c74a7b0808f9fc9a247584e 2294 sip4_4.19.25+dfsg-5.dsc
 510c7103b2dd324c4263d432de7d5f16111a5d2f 17900 
sip4_4.19.25+dfsg-5.debian.tar.xz
 a53efeae96883c9105dd425ece8eadad46852b2b 9886 
sip4_4.19.25+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 8bf9eaf6b01e6df46ed3d64cb40adff273a66a79242f3ddfb062628c5dc2c4c6 2294 
sip4_4.19.25+dfsg-5.dsc
 d051ece955c390205b67b156bbfb05da48c6688d200e94aecdc91994b2ebaf73 17900 
sip4_4.19.25+dfsg-5.debian.tar.xz
 3ec51e323f60befc3aa3bd21011d1b3fa23c049f4a1e88bb86aacf464f7063b6 9886 
sip4_4.19.25+dfsg-5_amd64.buildinfo
Files:
 d7816d393489da7fcc672f510e912fbd 2294 devel optional sip4_4.19.25+dfsg-5.dsc
 ee733fcc73e181413a953f3dacd6f713 17900 devel optional 
sip4_4.19.25+dfsg-5.debian.tar.xz
 1e524b8ab72df382bf80855ae25e57f2 9886 devel optional 
sip4_4.19.25+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNxOfYPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iidXgQALJuAETmPE5KFGnRP2ncJLY6jyzCDrKOfLQL
jzvnIcYmgz9wOXluwYKxWvsVxAA5C4XmRSOu6TR0v+Gz9HkXZBI4RhfHJekhXhxo
WCUr76W7cysghDv4GR53k4a8rfixYplZb6g8v4ebdbocYeOZmq+ochL5ScHQW6n7
Htpex1cGMG1UMm52HgelIpUdiN5gCmPRyFyY1L3vp/NnYWJEqx+t0Dnk5yGIuD/5
8lrvrn/hKfUNB+P5ZeS2Mlhg78FxHQqSlNKZ3mCMywH0gy2FGL42LQlLEiK1BQJL
322rb1XEZ3GdXl5Y7YAX090Cd6V2Kj0pGrJwfR2qTGa0JljtaLjy9pMHRqr19m0c
9RPnMghVlHg//a8GQ8N/PRdFWRrAmcK78j/S4rO4ZXNk7kkPwibruRVSbwGu++AD
JrZtYI5OwH7ZNONAqb9gqO0WpGJkqr8mXZw4GeJC2Nc9BqoX3Kdknw3ASQfA70SV
HsykhtK8lFiH8IPzAN+y9LwAcmL9cglcPIKfjNZIfNTSURdvOjIH2ec1j9W3B6GX
0oDC10BxrVVUNdNPMsMGgeWRtcdrpNcRnFyzt3EoPAWT1V6nb5jBtTxCX2obvi62
qntAWwr8V7dNuI+kOleGd31w5PfOezp+yaMbgLVYrfKnb8oLVyrIgDotRgfbN4DF
wmXlVIiC
=AjX6
-END PGP SIGNATURE End Message ---

Bug#1019669: marked as done (ruby-slim: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:130:in `block (3 levels) in define': Command fa

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 18:57:19 +
with message-id 
and subject line Bug#1019669: fixed in ruby-slim 4.1.0-2
has caused the Debian Bug report #1019669,
regarding ruby-slim: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
/usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:130:in `block (3 
levels) in define': Command failed with status (1) (RuntimeError)
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.)


-- 
1019669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-slim
Version: 4.1.0-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 ruby-slim with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:130:in `block 
> (3 levels) in define': Command failed with status (1) (RuntimeError)
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/file_utils.rb:57:in `sh'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/file_utils.rb:104:in `ruby'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:117:in `block 
> (2 levels) in define'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/file_utils_ext.rb:58:in 
> `verbose'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:111:in `block 
> in define'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in 
> `block in execute'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in 
> `each'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:281:in 
> `execute'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:219:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:243:in 
> `block in invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:241:in 
> `each'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:241:in 
> `invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:218:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:243:in 
> `block in invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:241:in 
> `each'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:241:in 
> `invoke_prerequisites'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:218:in 
> `block in invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `synchronize'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
>   from /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/task.rb:188:in 
> `invoke'
>   from debian/ruby-tests.rb:5:in `'
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-slim/ruby-slim_4.1.0-1+rebuild1663008220_amd64-2022-09-12T18:43:41Z.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 ---
Source: ruby-slim
Source-Version: 4.1.0-2
Done: Cédric 

Bug#899479: marked as done (combat: Invalid maintainer address pkg-corba-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 18:50:07 +
with message-id 
and subject line Bug#899479: fixed in combat 0.8.1-1.1
has caused the Debian Bug report #899479,
regarding combat: Invalid maintainer address 
pkg-corba-de...@lists.alioth.debian.org
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.)


-- 
899479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:combat
Version: 0.8.1-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of combat,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package combat since the list address
pkg-corba-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-corba-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: combat
Source-Version: 0.8.1-1.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated combat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 13:27:51 -0500
Source: combat
Architecture: source
Version: 0.8.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Girard 
Changed-By: Boyuan Yang 
Closes: 899479
Changes:
 combat (0.8.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/control:
 + Remove disappeared maintainer email address. (Closes: #899479)
 + Update Vcs-* fields.
 + Bump debhelper compat to v13.
 + Bump Standards-Version to 4.6.1.
   * d/copyright: Fix grammar errors.
 .
   [ Debian Janitor ]
   * Use versioned copyright format URI.
Checksums-Sha1:
 611f8ca6018354317d7d74f71e7dbaa782fe9dcd 1838 combat_0.8.1-1.1.dsc
 1d9c159226df50e3490a82f8a620510e996cfd82 331808 combat_0.8.1.orig.tar.gz
 6858f6c4a40050f105860a36184fd1173389b0c6 3660 combat_0.8.1-1.1.debian.tar.xz
 cd777941ca1504d0d19c04da440096252f60fd48 6091 combat_0.8.1-1.1_amd64.buildinfo
Checksums-Sha256:
 b6c35123e81fb15a50dab58806f93dcafd0abbd94b873b6cabd70d8ebb778b98 1838 
combat_0.8.1-1.1.dsc
 1923fa19f55a03f720f0444d6edffe7dad246c2c4be82453b8d2c5b4922d99a8 331808 
combat_0.8.1.orig.tar.gz
 7ba81fd8c992080699b054952e44f1bc4dc691bee0e2b25d21b8701692654e79 3660 
combat_0.8.1-1.1.debian.tar.xz
 

Bug#1024013: frozenlist FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: frozenlist
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=frozenlist=amd64=1.2.0-1%2Bb3=1668362318=0

...
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/usr/include/python3.11 -c frozenlist/_frozenlist.c -o 
build/temp.linux-x86_64-cpython-311/frozenlist/_frozenlist.o
frozenlist/_frozenlist.c:198:12: fatal error: longintrepr.h: No such file or 
directory
  198 |   #include "longintrepr.h"
  |^~~
compilation terminated.
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 

Bug#1024012: r-cran-xts: autopkgtest regression on i386

[Sebastian Ramacher]

Source: r-cran-xts
Version: 0.12.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-xts/28179801/log.gz

The following objects are masked from 'package:base':

as.Date, as.Date.numeric

Error in make.index.unique.xts(x, eps = eps) : 
  (converted from warning) index value is unique but will be replaced; it is 
less than the cumulative epsilon for the preceding duplicate index values
In addition: Warning messages:
1: In make.index.unique.xts(x, eps = 1e-06) :
  index value is unique but will be replaced; it is less than the cumulative 
epsilon for the preceding duplicate index values
2: In make.index.unique.xts(x, eps = eps) :
  index value is unique but will be replaced; it is less than the cumulative 
epsilon for the preceding duplicate index values
Error in try.xts(sample.data.frame[, 1]) : 
  Error in as.xts.double(x, ..., .RECLASS = TRUE) :   order.by must be either 
'names()' or otherwise specified
Error in diff.xts(x, 1L, -1L) : 
  'diff.xts' defined only for positive lag and differences arguments
Error in diff.xts(x, 1L, "a") : 'differences' must be integer
In addition: Warning message:
In diff.xts(x, 1L, "a") : NAs introduced by coercion
Error in diff.xts(x, -1L, 1L) : 
  'diff.xts' defined only for positive lag and differences arguments
Error in diff.xts(x, "a", 1L) : 'lag' must be integer
In addition: Warning message:
In diff.xts(x, "a", 1L) : NAs introduced by coercion
Error in endpoints(x, on = "years", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "years", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "quarters", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "quarters", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "months", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "months", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "weeks", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "weeks", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "days", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "days", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "hours", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "hours", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "minutes", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "minutes", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "seconds", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "seconds", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "ms", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "ms", k = -1) : 'k' must be > 0
Error in endpoints(x, on = "us", k = 0) : 'k' must be > 0
Error in endpoints(x, on = "us", k = -1) : 'k' must be > 0
Error in `tclass<-.xts`(x, value) : improperly specified value for tclass
In addition: There were 50 or more warnings (use warnings() to see the first 50)
Error in `tclass<-.xts`(x, value) : unsupported 'tclass' indexing type: 
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated"). 
Error in `tclass<-.xts`(x, value) : improperly specified value for tclass
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated"). 
Error in eval(expr, envir = parent.frame()) : object 'Date' not found
In addition: Warning message:
In rm(Date) : object 'Date' not found
Error in h(simpleError(msg, call)) : 
  error in evaluating the argument 'i' in selecting a method for function '[': 
'match' requires vector arguments
In addition: Warning message:
'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated"). 
Registered S3 method overwritten by 'quantmod':
  methodfrom
  as.zoo.data.frame zoo 
Error in periodicity(x) : 
  (converted from warning) can not calculate periodicity of 1 observation
In addition: There were 14 warnings (use warnings() to see them)
Error in periodicity(x) : 
  (converted from warning) can not calculate periodicity of empty object
In addition: Warning message:
In periodicity(x) : can not calculate periodicity of empty object
Timing stopped at: 0.013 0 0.014
Error in checkIdentical(nm_target, nm_ms, msg) : FALSE 
 microsecond data split by milliseconds
Error : Supply time-of-day subsetting in the format of T%H:%M:%OS/T%H:%M:%OS
Error : Supply time-of-day subsetting in the format of T%H:%M:%OS/T%H:%M:%OS
Error : (converted from warning) 'indexClass' is deprecated.
Use 'tclass' instead.
See help("Deprecated") and help("xts-deprecated").
In addition: Warning message:
In .parseISO8601(ii, .index(x)[1], .index(x)[nr], tz = tz) :
  cannot determine first and last time from 2012-02-30/2012-02-30
Error : (converted from warning) 'indexClass<-' is deprecated.
Use 'tclass<-' instead.
See help("Deprecated") and help("xts-deprecated").
Error : (converted from warning) 'indexFormat' is deprecated.
Use 'tformat' instead.
See help("Deprecated") and 

Processed: Bug#1023913 marked as pending in sip4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023913 [src:sip4] sip4 FTBFS with Python 3.11 as supported version
Added tag(s) pending.

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

Bug#1023913: marked as pending in sip4

[Scott Talbert]

Control: tag -1 pending

Hello,

Bug #1023913 in sip4 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/sip4/-/commit/e07db942427703904c5bf891eec17f6765b69b63


Fix FTBFS with Python 3.11 (Closes: #1023913)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023913

Bug#1024011: gtksourceview4: autopkgtest regression

[Sebastian Ramacher]

Source: gtksourceview4
Version: 4.8.4-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtksourceview4/27967119/log.gz

# Start of file-loader tests
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ?gio-vfs?
(/usr/libexec/installed-tests/gtksourceview-4/test-file-loader:6343): 
GLib-GIO-DEBUG: 15:17:49.746: _g_io_module_get_default: Found default 
implementation local (GLocalVfs) for ?gio-vfs?
ok 1 /file-loader/end-line-stripping
ok 2 /file-loader/end-new-line-detection
ok 3 /file-loader/begin-new-line-detection
# End of file-loader tests
PASS: gtksourceview-4/test-file-loader.test
Running test: gtksourceview-4/test-language-specs.test
**
GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 'srcdir' should 
not be NULL
Bail out! GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 
'srcdir' should not be NULL
FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 
6)
SUMMARY: total=23; passed=3; skipped=0; failed=20; user=0.9s; system=0.4s; 
maxrss=70476
FAIL: gtksourceview-4/test-completion-words.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-mark.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-printcompositor.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-regex.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-languagemanager.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-iter.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-completion-model.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-buffer.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-file-saver.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-stylescheme.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-region.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-styleschememanager.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-space-drawer.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-encoding.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-search-context.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-view.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-undo-manager.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-utils.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-language.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 
6)
autopkgtest [15:17:50]: test installed-tests: ---]
autopkgtest [15:17:50]: test installed-tests:  - - - - - - - - - - results - - 
- - - - - - - -
installed-tests  FAIL non-zero exit status 2
autopkgtest [15:17:50]:  summary
installed-tests  FAIL non-zero exit status 2

Cheers
-- 
Sebastian Ramacher

Bug#1024010: compreffor FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: compreffor
Version: 0.5.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=compreffor=0.5.1-2%2Bb2

...
src/cython/_compreffor.cpp:196:12: fatal error: longintrepr.h: No such file or 
directory
  196 |   #include "longintrepr.h"
  |^~~
compilation terminated.
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

Bug#1024008: python3-spyder is not installable

[Adrian Bunk]

Package: python3-spyder
Version: 5.3.3+dfsg-3
Severity: serious

The following packages have unmet dependencies:
 python3-spyder : Depends: python3-pylsp (< 1.6~) but 1.6.0-1 is to be installed
  Depends: python3-qtconsole (< 5.4~) but 5.4.0-1 is to be 
installed

Bug#1020253: marked as done (libghc-lambdabot-trusted-doc: Depends: haddock-interface-35 but it is not installable)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 18:26:33 +
with message-id 
and subject line Bug#1020253: fixed in haskell-lambdabot-trusted 5.3.1-1
has caused the Debian Bug report #1020253,
regarding libghc-lambdabot-trusted-doc: Depends: haddock-interface-35 but it is 
not installable
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.)


-- 
1020253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-lambdabot-trusted-doc
Version: 5.3-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

$ apt install libghc-lambdabot-trusted-doc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libghc-lambdabot-trusted-doc : Depends: haddock-interface-35 but it is not 
installable
Recommends: libghc-oeis-doc but it is not going 
to be installed
Recommends: libghc-quickcheck-safe-doc but it 
is not going to be installed
Recommends: libjs-mathjax but it is not going 
to be installed
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: haskell-lambdabot-trusted
Source-Version: 5.3.1-1
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated haskell-lambdabot-trusted 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 13:05:13 -0500
Source: haskell-lambdabot-trusted
Architecture: source
Version: 5.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Scott Talbert 
Closes: 1020253
Changes:
 haskell-lambdabot-trusted (5.3.1-1) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * Declare compliance with Debian policy 4.6.1
 .
   [ Scott Talbert ]
   * New upstream release (Closes: #1020253)
Checksums-Sha1:
 e242f0e0704971273ed6f90befb443d9c69c1443 2689 
haskell-lambdabot-trusted_5.3.1-1.dsc
 ef9c5981eafb9f527a4a9526dbbb4a5baba7fa15 1951 
haskell-lambdabot-trusted_5.3.1.orig.tar.gz
 8545414304830575f587c34968aea8cf641cbe09 2820 
haskell-lambdabot-trusted_5.3.1-1.debian.tar.xz
 6ec4f39e66ef2b13eacc4c874e688532524f3b7c 8807 
haskell-lambdabot-trusted_5.3.1-1_source.buildinfo
Checksums-Sha256:
 4c1e17889295068c01b66f405fd47330ffa159fb11073a6404440514b4bfeda8 2689 
haskell-lambdabot-trusted_5.3.1-1.dsc
 b046b78e44a9fd3bea73803beddf6af601ce0b40ae6341f10f65e579e899950f 1951 
haskell-lambdabot-trusted_5.3.1.orig.tar.gz
 4c44f740051432bc8a2dbaeabd265ef8a81e47ca83e6f386f60876ad4fbf405b 2820 
haskell-lambdabot-trusted_5.3.1-1.debian.tar.xz
 ed2fd946795af869083f6958add628c076a8236140e05bce0b5858b7913dc4a0 8807 
haskell-lambdabot-trusted_5.3.1-1_source.buildinfo
Files:
 d03a3f08095d58c1304a6ede6c006cc7 2689 haskell optional 
haskell-lambdabot-trusted_5.3.1-1.dsc
 6644071040c25a671fb6190e9d15c466 1951 haskell optional 
haskell-lambdabot-trusted_5.3.1.orig.tar.gz
 05142a4956b44c9711df685fb9c09791 2820 haskell optional 
haskell-lambdabot-trusted_5.3.1-1.debian.tar.xz
 8e09d18bf4dbda7c68571197008fa80d 8807 haskell optional 
haskell-lambdabot-trusted_5.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNxMhYPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iibg0QAKwZQnGGf1FgyjzUbFK7Yd/EAT6OIv7XcxxF
ZVGGdZ2lCl3DoQRv7A1e0/o8Ya9x+83S6anchFGGekMLu9UojPzdrtHKzYlV1Y1R
dTh/uVu0FnHTo2wz7rEbeyJC1U6QMABEkRwjLbD8+LbWfiPxnvLitFTEVYGHYJur
RfNCNiDW5t4nhxtI4qxXAQmgwfjgejYXulFtQvqdLOxtNGEbQW/KwFQ8y/J1OZRu

Bug#1024004: src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el

[Paul Gevers]

Source: vectorscan
Version: 5.4.7-1
Severity: serious
Control: close -1 5.4.8-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1021079

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:vectorscan has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. The package in unstable 
regressed its autopkgtest on ppc64el which I reported in bug 1021079.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=vectorscan



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.4.8-2
Bug #1024004 [src:vectorscan] src:vectorscan: fails to migrate to testing for 
too long: autopkgtest regression on ppc64el
Marked as fixed in versions vectorscan/5.4.8-2.
Bug #1024004 [src:vectorscan] src:vectorscan: fails to migrate to testing for 
too long: autopkgtest regression on ppc64el
Marked Bug as done
> block -1 by 1021079
Bug #1024004 {Done: Paul Gevers } [src:vectorscan] 
src:vectorscan: fails to migrate to testing for too long: autopkgtest 
regression on ppc64el
1024004 was not blocked by any bugs.
1024004 was not blocking any bugs.
Added blocking bug(s) of 1024004: 1021079

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

Processed: src:elpi: fails to migrate to testing for too long: make reverse (test) dependencies uninstallable

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.16.7-2
Bug #1024003 [src:elpi] src:elpi: fails to migrate to testing for too long: 
make reverse (test) dependencies uninstallable
Marked as fixed in versions elpi/1.16.7-2.
Bug #1024003 [src:elpi] src:elpi: fails to migrate to testing for too long: 
make reverse (test) dependencies uninstallable
Marked Bug as done

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

Bug#1024003: src:elpi: fails to migrate to testing for too long: make reverse (test) dependencies uninstallable

[Paul Gevers]

Source: elpi
Version: 1.16.5-1
Severity: serious
Control: close -1 1.16.7-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:elpi has been trying to migrate for 62 
days [2]. Hence, I am filing this bug. I think something went wrong with 
the rebuilds (or the order of them or something), because elpi can't 
migrate because it would make libcoq-elpi on armhf not installable and 
libcoq-elpi in unstable can't migrate because two reverse test 
dependencies fail to install during autopkgtesting on armhf.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=elpi



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023599: marked as done (mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 17:53:22 +
with message-id 
and subject line Bug#1023599: fixed in mutt 2.2.9-1
has caused the Debian Bug report #1023599,
regarding mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2
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.)


-- 
1023599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mutt
Version: 2.2.7-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Forwarded: https://gitlab.com/muttmua/mutt/-/issues/430

The gpgme-config utility was removed in gpgme1.0 1.18.0-2
(because it needs gpg-error-config, which has been removed).

As a consequence the use of --enable-gpgme to build Mutt yields
an error:

dh_auto_configure: error: cd debian/build && ../../configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl 
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop 
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses 
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-gsasl 
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet returned exit 
code 1
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 25

with debian/build/config.log containing

configure:7932: checking for gpgme-config
configure:7968: result: no
configure:8001: checking for GPGME - version >= 1.4.0
configure:8082: result: no
configure:8090: error: *** GPGME not found or version is older than 1.4.0 ***

A workaround would be to remove --enable-gpgme, with the consequence
that GPGME would no longer be supported in Mutt. But this may be bad
for the end user. I've reported a bug upstream, hoping a solution
would be found:

  https://gitlab.com/muttmua/mutt/-/issues/430

Alternatively, gpg-error-config and gpgme-config could be re-added
until things are resolved:

https://dev.gnupg.org/T5683 says "Now, we can consider deprecation
of gpg-error-config, to show preference to gpgrt-config. [...]
Distributions still can install it (by their own make rule), because
gpg-error-config will be kept distributed and built well."

-- Package-specific info:
Mutt 2.2.8+45 (c11015d0) vl-149028 (2022-11-06)
Copyright (C) 1996-2022 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 6.0.0-2-amd64 (x86_64)
ncurses: ncurses 6.3.20220423 (compiled with 6.3)
libidn: 1.41 (compiled with 1.41)

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-7' 
--with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-zpDQmA/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-zpDQmA/gcc-12-12.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-7) 

Configure options: --prefix=/home/vinc17 --enable-debug --enable-pop 
--enable-imap --with-ssl --enable-compressed 

Bug#1015776: marked as done (haskell-lambdabot-core FTBFS: error: Could not deduce)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 17:53:01 +
with message-id 
and subject line Bug#1015776: fixed in haskell-lambdabot-core 5.3.1-1
has caused the Debian Bug report #1015776,
regarding haskell-lambdabot-core FTBFS: error: Could not deduce
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.)


-- 
1015776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-core
Version: 5.3.0.1-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-lambdabot-core=sid

...
src/Lambdabot/Util.hs:66:15: error:
• Could not deduce (StatefulGen g0 IO)
arising from a use of ‘sample’
  from the context: MonadIO m
bound by the type signature for:
   random :: forall (m :: * -> *) a. MonadIO m => [a] -> m a
at src/Lambdabot/Util.hs:65:1-33
  The type variable ‘g0’ is ambiguous
  These potential instances exist:
three instances involving out-of-scope types
(use -fprint-potential-instances to see them all)
• In the first argument of ‘(.)’, namely ‘sample’
  In the second argument of ‘(.)’, namely ‘sample . randomElement’
  In the expression: io . sample . randomElement
   |
66 | random = io . sample . randomElement
   |   ^^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "build", "--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"build", "--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 642
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:160: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: haskell-lambdabot-core
Source-Version: 5.3.1-1
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated haskell-lambdabot-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 12:28:38 -0500
Source: haskell-lambdabot-core
Architecture: source
Version: 5.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Scott Talbert 
Closes: 1015776 1022841
Changes:
 haskell-lambdabot-core (5.3.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1015776, #1022841)
Checksums-Sha1:
 c39d2876989fac6e98b2cb2fff67e2e3dbb82fc4 4309 
haskell-lambdabot-core_5.3.1-1.dsc
 633957bfb91ea15a821e9747da67f2e4c7e409ce 42289 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 7f2c536824c7418dea267d7439a9a4c97aa15f40 3344 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 a8a09fe8647e56d111c7080fd76e3fef84de94f1 13166 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo
Checksums-Sha256:
 5e83cfdc7d747cd87f598e2af64a6f89b957377d20dff7c26675fb193d1c037a 4309 
haskell-lambdabot-core_5.3.1-1.dsc
 f04aca55f41d93764edc513c10faa78e35c435cfe884e013e9f93260200f38c2 42289 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 a0ab140c31d932b3687e481635ae0162fd245d2798cc77df480202d9c665f491 3344 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 125db0370f587858ca57b7d8bcf1c454fa3d3f2465697d8af9651dc1864121ca 13166 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo
Files:
 21a0593d4b5b29e6e968c9e581449365 4309 haskell optional 
haskell-lambdabot-core_5.3.1-1.dsc
 7f143da258549ff5938a891f77082ae6 42289 haskell optional 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 2746b1e0f1c1c9a084a51fc31d4740e7 3344 haskell optional 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 1121eabf36dda4d28a7e0bd7a9ccf614 13166 haskell optional 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo

-BEGIN PGP 

Bug#1022841: marked as done (libghc-lambdabot-core-doc: unsatisfiable sdependency on haddock-interface-35)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 17:53:01 +
with message-id 
and subject line Bug#1022841: fixed in haskell-lambdabot-core 5.3.1-1
has caused the Debian Bug report #1022841,
regarding libghc-lambdabot-core-doc: unsatisfiable sdependency on 
haddock-interface-35
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.)


-- 
1022841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-lambdabot-core-doc
Version: 5.3.0.1-1
Severity: serious

Hi, libghc-lambdabot-core-doc depends on haddock-interface-35 but that
package does not exist in the archive.

-Ralf
--- End Message ---
--- Begin Message ---
Source: haskell-lambdabot-core
Source-Version: 5.3.1-1
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated haskell-lambdabot-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 12:28:38 -0500
Source: haskell-lambdabot-core
Architecture: source
Version: 5.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Scott Talbert 
Closes: 1015776 1022841
Changes:
 haskell-lambdabot-core (5.3.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1015776, #1022841)
Checksums-Sha1:
 c39d2876989fac6e98b2cb2fff67e2e3dbb82fc4 4309 
haskell-lambdabot-core_5.3.1-1.dsc
 633957bfb91ea15a821e9747da67f2e4c7e409ce 42289 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 7f2c536824c7418dea267d7439a9a4c97aa15f40 3344 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 a8a09fe8647e56d111c7080fd76e3fef84de94f1 13166 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo
Checksums-Sha256:
 5e83cfdc7d747cd87f598e2af64a6f89b957377d20dff7c26675fb193d1c037a 4309 
haskell-lambdabot-core_5.3.1-1.dsc
 f04aca55f41d93764edc513c10faa78e35c435cfe884e013e9f93260200f38c2 42289 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 a0ab140c31d932b3687e481635ae0162fd245d2798cc77df480202d9c665f491 3344 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 125db0370f587858ca57b7d8bcf1c454fa3d3f2465697d8af9651dc1864121ca 13166 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo
Files:
 21a0593d4b5b29e6e968c9e581449365 4309 haskell optional 
haskell-lambdabot-core_5.3.1-1.dsc
 7f143da258549ff5938a891f77082ae6 42289 haskell optional 
haskell-lambdabot-core_5.3.1.orig.tar.gz
 2746b1e0f1c1c9a084a51fc31d4740e7 3344 haskell optional 
haskell-lambdabot-core_5.3.1-1.debian.tar.xz
 1121eabf36dda4d28a7e0bd7a9ccf614 13166 haskell optional 
haskell-lambdabot-core_5.3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNxKsgPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiZ5sP/ivhRv7iaHk85kxTI0d4mv050i3kb3AHaIw7
nB/nGsXhWKdk3lJR1v+dBvJiOZeq99y1udywPp8YKqo17HadL1gry4HmgTSIsvWl
yoBe/JBPfxwE36kF2qqALTX3/ezyyKbuqPv2A/PfgRpHT3qZY2BoTHFb9GP0EKPI
DSGlt/n6GXhtTi3v8XxXfhBwDpMLKV6tQGqDx916shZEL5ZHzJNivkDcCgKqp7rq
+me+wuTPkjsMQ20xqsqBtXgjcibTGWkIKl1iWIPLmF526iDjH0Ytc/CvwcH+3ZHJ
a3QGLhHV+xWF7Jm6F94UWFJOq2sKOMmBNRWl03x/ju7yU4XveRNCEZBjDmCkl7BC
S9LyYbm6nlyAMAcO0QFVxsupwOb4vzvA7R2tA71vf98ldpyU8Be0x0OxKm8OZKVb
jgBYCyxgJiX9TD2FhWxKDCnTmJP7g8KfW+nTpkWjN2AroQU9VZWpzbctCDx0wOSl
eOQtTQsex9kn4yfD4oN9LdnG6D8Mob8yziRZzqvpdnMbQHaCU77RoEDgEd/LadE/
gRO0Rrro1n7I9chl/uqzxw7CIIi37m3LQUp2Ifxv9dscK+um6UmBRYcfTa+sF3zy
HOFcoMQgFlkfqF79EpJe1/tWr+AW9id5DL49xzaQCAkWo0bbK+/COQpaTrLlWATr
KKWr5DUW
=XqbZ
-END PGP SIGNATURE End Message ---

Bug#1024002: ruby-nokogiri: FTBFS on s390x

[Sebastian Ramacher]

Source: ruby-nokogiri
Version: 1.13.8+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ruby-nokogiri=s390x=1.13.8%2Bdfsg-1=1665929973=0

Nokogiri::HTML4::Document#test_parse_works_with_an_object_that_responds_to_read 
:239: [BUG] Couldn't unprotect page 0x03ff905b4000, errno: 
Cannot allocate memory
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu]

-- Control frame information ---
c:0027 p:0003 s:0143 e:000142 METHOD :239
c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124
c:0025 p:0005 s:0135 e:000134 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103
c:0024 p:0002 s:0132 e:000131 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195
c:0023 p:0004 s:0127 e:000126 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH]
c:0022 p: s:0123 e:000122 CFUNC  :each
c:0021 p:0017 s:0119 e:000118 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101
c:0020 p:0015 s:0116 e:000115 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281
c:0019 p:0004 s:0111 e:000110 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94
c:0018 p:0029 s:0108 e:000107 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376
c:0017 p:0044 s:0100 E:001108 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221
c:0016 p:0004 s:0093 E:000eb0 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93
c:0015 p:0058 s:0089 e:88 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44
c:0014 p:0008 s:0082 e:81 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042
c:0013 p:0026 s:0075 e:73 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350
:239: [BUG] Segmentation fault at 0x03ff905ba000
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [s390x-linux-gnu]

-- Control frame information ---
c:0027 p:0003 s:0143 e:000142 METHOD :239
c:0026 p:0134 s:0139 e:000138 METHOD /<>/test/helper.rb:124
c:0025 p:0005 s:0135 e:000134 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:103
c:0024 p:0002 s:0132 e:000131 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:195
c:0023 p:0004 s:0127 e:000126 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:102 [FINISH]
c:0022 p: s:0123 e:000122 CFUNC  :each
c:0021 p:0017 s:0119 e:000118 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:101
c:0020 p:0015 s:0116 e:000115 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:281
c:0019 p:0004 s:0111 e:000110 BLOCK  
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:94
c:0018 p:0029 s:0108 e:000107 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:376
c:0017 p:0044 s:0100 E:001108 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:221
c:0016 p:0004 s:0093 E:000eb0 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest/test.rb:93
c:0015 p:0058 s:0089 e:88 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/reporters.rb:44
c:0014 p:0008 s:0082 e:81 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:1042
c:0013 p:0026 s:0075 e:73 METHOD 
/usr/lib/ruby/gems/3.1.0/gems/minitest-5.15.0/lib/minitest.rb:350
Segmentation fault
rake aborted!
Command failed with status (139): [ruby -w -I"test" 
/usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/css/test_css.rb" "test/css/test_css_integration.rb" 
"test/css/test_parser.rb" "test/css/test_tokenizer.rb" 
"test/css/test_xpath_visitor.rb" "test/decorators/test_slop.rb" 
"test/html4/sax/test_parser.rb" "test/html4/sax/test_parser_context.rb" 
"test/html4/sax/test_parser_text.rb" "test/html4/sax/test_push_parser.rb" 
"test/html4/test_attributes.rb" 
"test/html4/test_attributes_properly_escaped.rb" "test/html4/test_builder.rb" 
"test/html4/test_comments.rb" "test/html4/test_document.rb" 
"test/html4/test_document_encoding.rb" "test/html4/test_document_fragment.rb" 
"test/html4/test_element_description.rb" "test/html4/test_html_module.rb" 
"test/html4/test_named_characters.rb" "test/html4/test_node.rb" 
"test/html4/test_node_encoding.rb" "test/html5/test_api.rb" 
"test/html5/test_encoding.rb" "test/html5/test_monkey_patch.rb" 
"test/html5/test_nokogumbo.rb" "test/html5/test_null.rb" 
"test/html5/test_serialize.rb" "test/html5/test_tree-construction.rb" 
"test/namespaces/test_additional_namespaces_in_builder_doc.rb" 
"test/namespaces/test_namespaces_aliased_default.rb" 
"test/namespaces/test_namespaces_in_builder_doc.rb" 
"test/namespaces/test_namespaces_in_cloned_doc.rb" 

Bug#1024000: pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1

[Sebastian Ramacher]

Source: pink-pony
Version: 1.4.1-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org


scons: Reading SConscript files ...
Package IlmBase was not found in the pkg-config search path.
Perhaps you should add the directory containing `IlmBase.pc'
to the PKG_CONFIG_PATH environment variable
Package 'IlmBase', required by 'virtual:world', not found
OSError: 'pkg-config IlmBase --cflags --libs' exited 1:
  File "/<>/SConstruct.Debian", line 10:
env.ParseConfig("pkg-config IlmBase --cflags --libs")
  File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1674:
return function(self, self.backtick(command), unique)
  File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 597:
raise OSError("'%s' exited %d" % (command, status))
make: *** [debian/rules:37: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Cheers
-- 
Sebastian Ramacher

Processed: block 1023419 with 1023995 1023996 1023997 1023999 1023998

[Debian Bug Tracking System]

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

> block 1023419 with 1023995 1023996 1023997 1023999 1023998
Bug #1023419 [release.debian.org] transition: freeglut
1023419 was blocked by: 1023548
1023419 was not blocking any bugs.
Added blocking bug(s) of 1023419: 1023997, 1023998, 1023996, 1023999, and 
1023995
> thanks
Stopping processing here.

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

Bug#1022539: marked as done (librust-enumset-dev: impossible to install)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 17:14:44 +
with message-id <15d5bef0-7f94-41af-c38c-344bef36d...@debian.org>
and subject line re: librust-enumset-dev: impossible to install
has caused the Debian Bug report #1022539,
regarding librust-enumset-dev: impossible to install
to be marked as done.

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

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


-- 
1022539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-enumset-dev
Version: 1.0.11-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package
librust-enumset-derive-0.6+default-dev (and more).

(I notice that rust-enumset-derive is currently pending in NEW queue,
which I guess will solve this).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNVU5YACgkQLHwxRsGg
ASEDrg//c4ZbBpKDzswEz606GeK+vayIq+HiZyIlfOLwb4cUtTY/NwaRjL5H/D8i
BR0zeLge4H6p9FNZ+qa8fzEEzzynGoqhzBWaed1Eu0OiIy0bwWbDXntXZjUuvj1f
qXeRoIen4dYqQ/0mQhdjEfRZwrQM8Gt+dQuw7LHPdFY17knDH8pJiQkjmlQgheWg
VTh12xUymLJ6lV8gKjFBjhAC6myqihkTfCW1wW5GvilHYgknYcEBzyhRT4QvP4EA
A6W2b+S4xsnvydfm5zQNL0B4UToiMeI1p/OYdRFbGkHIJ6YiX8Tflh1Q3rq8Uz9r
98OW5VqD6iNtFk33pz56wndITwuFPMSgHI4Zs918f1Iy/mfqO5KuYYMbZakECNvP
UX2hY1mbd59U3o+vU4k1mzXqOJVxfV+xTRWs3icviODtW9NUnlf76tUoMCxzH+U+
7sbSOM9Rn+P8GhAK7jrwzbgUybGlFFJ2tI7+8jcgvaK2z+k+ceOiq2KXLt3QQtGH
StBK5OMvg8aelcwj65PfG7hiq/MnuExylH4K+u4+4zPTYdTt/N5i1uGxXdNejWH5
1P56Y6dfItbFSB3dC3ggIuuVLvZ0EhUavO4r54mjqRW8dCD2MekVFaV+2pqHY1Vq
EXXfcu/QMHSbdu8fGRT1W5fMeZd3yZLcuhQt/cv8ndTxXHbfz8A=
=ecoj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

rust-enumset-derive is now in Debian.--- End Message ---

Processed: severity of 1021262 is normal

[Debian Bug Tracking System]

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

> severity 1021262 normal
Bug #1021262 [src:ruby-stackprof] ruby-stackprof FTBFS on 32bit
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1023998: openuniverse: build-depends on missing: plib1.8.4-dev

[Sebastian Ramacher]

Source: openuniverse
Version: 1.0beta3.1+dfsg-7
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

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

openuniverse build-depends on missing:
- plib1.8.4-dev:armel

Cheers
-- 
Sebastian Ramacher

Bug#1023999: stormbaancoureur: build-depends on missing: plib1.8.4-dev

[Sebastian Ramacher]

Source: stormbaancoureur
Version: 2.1.6-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

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

stormbaancoureur build-depends on missing:
- plib1.8.4-dev:amd64

Cheers
-- 
Sebastian Ramacher

Bug#1023997: pfstools: FTBFS: collect2: error: ld returned 1 exit status

[Sebastian Ramacher]

Source: pfstools
Version: 2.2.0-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pfstools=amd64=2.2.0-4%2Bb2=1667855058=0

/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_histogram.cpp:990: 
undefined reference to `glutSetCursor'
/usr/bin/ld: 
CMakeFiles/pfsglview.dir/m_histogram.cpp.o:./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_histogram.cpp:995:
 more undefined references to `glutSetCursor' follow
/usr/bin/ld: CMakeFiles/pfsglview.dir/m_status.cpp.o: in function 
`SC_Status::redraw()':
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:74: undefined 
reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:74: undefined 
reference to `glutBitmapCharacter'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:79: undefined 
reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:79: undefined 
reference to `glutBitmapCharacter'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:84: undefined 
reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:84: undefined 
reference to `glutBitmapCharacter'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:90: undefined 
reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:90: undefined 
reference to `glutBitmapCharacter'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:97: undefined 
reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_status.cpp:97: undefined 
reference to `glutBitmapCharacter'
/usr/bin/ld: CMakeFiles/pfsglview.dir/m_on_screen_display.cpp.o: in function 
`M_OnScreenDisplay::println(std::__cxx11::basic_string, std::allocator >)':
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_on_screen_display.cpp:112:
 undefined reference to `glutBitmap8By13'
/usr/bin/ld: 
./obj-x86_64-linux-gnu/src/pfsglview/./src/pfsglview/m_on_screen_display.cpp:115:
 undefined reference to `glutBitmapCharacter'
/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
collect2: error: ld returned 1 exit status
make[4]: *** [src/pfsglview/CMakeFiles/pfsglview.dir/build.make:184: 
src/pfsglview/pfsglview] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1023996: taoframework: rebuild for freeglut transition

[Sebastian Ramacher]

Source: taoframework
Version: 2.1.svn20090801-15
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

taoframework provides Architecture: all packages that depend on
freeglut3 and requires a rebuild for freeglut transition.

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1023953

[Debian Bug Tracking System]

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

> tags 1023953 + bookworm sid
Bug #1023953 {Done: Jochen Sprickerhof } 
[python3-rosgraph] ros-geometry2 FTBFS with Python 3.11 as supported version
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1023995: starpu-contrib: requires rebuild for freeglut transition

[Sebastian Ramacher]

Source: starpu-contrib
Version: 1.3.9+dfsg-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

starpu-contrib requires a rebuild for the freeglut transition, but is
not auto-buildable. Please upload a rebuild.

Cheers
-- 
Sebastian Ramacher

Bug#1023325: marked as done (cron-daemon-common: insufficient Breaks+Replaces against cronie)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 17:04:02 +
with message-id 
and subject line Bug#1023325: fixed in cron 3.0pl1-151
has caused the Debian Bug report #1023325,
regarding cron-daemon-common: insufficient Breaks+Replaces against cronie
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.)


-- 
1023325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron-daemon-common
Version: 3.0pl1-150
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package has file conflicts
with cronie/experimental.
There are Breaks+Replaces: cronie (<< 1.6.1-4), but cronie had a new
upload yesterday without adding support for cron-daemon-common,
invalidating the B+R versions.
I don't see any bug (and patch) against cronie to make it use
cron-daemon-common ...

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../cron-daemon-common_3.0pl1-150_all.deb ...
  Unpacking cron-daemon-common (3.0pl1-150) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-150_all.deb (--unpack):
   trying to overwrite '/etc/cron.d/.placeholder', which is also in package 
cronie 1.6.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/cron-daemon-common_3.0pl1-150_all.deb


cheers,

Andreas


cronie=1.6.1-4_cron-daemon-common=3.0pl1-150.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-151
Done: Georges Khaznadar 

We believe that the bug you reported is fixed in the latest version of
cron, 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.
Georges Khaznadar  (supplier of updated cron 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: Sun, 13 Nov 2022 17:26:56 +0100
Source: cron
Architecture: source
Version: 3.0pl1-151
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Georges Khaznadar 
Closes: 1023325
Changes:
 cron (3.0pl1-151) unstable; urgency=medium
 .
   * bumped a breaks+replace clause, now against cronie (<< 1.6.1-5)
 Closes: #1023325
Checksums-Sha1:
 a4f0c3fe1259cba81972617c7771b302ef1bcef7 2100 cron_3.0pl1-151.dsc
 c8e27aa1fc133cebb072ad04b4e8289db57a8ac2 112236 cron_3.0pl1-151.debian.tar.xz
 326cb3c7412d077cbe48957a4d90b9e44b06f527 6676 cron_3.0pl1-151_amd64.buildinfo
Checksums-Sha256:
 ac31856dc799325215556127447ae1b8900e347ffc65526c05178d637a6d909f 2100 
cron_3.0pl1-151.dsc
 2bddd23d9fbd008b39307b84e44eee4138c3aa0d05f8803597b5426fde290b10 112236 
cron_3.0pl1-151.debian.tar.xz
 7e5033168f159b27419c84194c90bec0c3a895445b50d88f657eb59eee0970b9 6676 
cron_3.0pl1-151_amd64.buildinfo
Files:
 de31fb2d47ab6f5c79e2f9ab5f665c60 2100 admin important cron_3.0pl1-151.dsc
 8371b501eb7dad15d39c7813fa42e58c 112236 admin important 
cron_3.0pl1-151.debian.tar.xz
 ca50e9949e5a939feb43f5ead2cb3987 6676 admin important 
cron_3.0pl1-151_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmNxHgIACgkQHCgWkHE2
rjldCg/+NQVSw9UXM1gW5p2l9rnCdeHyKuZwAUfNt2edWf/4c1ad2DqBt0JmACr8
ZuUovimk7HfNkFsEzkC5pHA9WTcrWlwA1rpeRBPwWablL30+w6lmyFra7v8/OX7l
dw6pyeF4Kxe69nAk9zbWA67JBConm6+9vvDADt78M6hNBw0p8FvBjRu3Fge3Wug1
9I7T9pqLKKkxzqwK1RHcA4KD4xlFqMvQWmy/bnp7IZJVw2pLGmITj1nGf5m1D2ux
1Y1eWPiZin2zx+FQETk9ifryCF4WkRuDg7GhkAF6TOwETEhcF6s9G/yJ5si8Gmjk
H53tQCQsS5GMtBCbv3pmzH4nqoe4WYzRCiT5jmb2Tu+tx7Pftb45XV7lTOzjLGEZ
Fpoik+ZXzVL/q2z8M66ZDdeDRvmvdhOOtrkubSK4qIHDGVgKbdRKIi5+L53CWkzW
re2KDBZT585V9dS8/PbdLN7ZzWGVJaVFSiBH6MgSfjNxazn+fGAGOvU3bEfJYkJb
Glp66MaE8m/pFPtSHmYEeDu8VaaOabc6tj9sA/1Hx6jr5MQPUp4niIhJFs+PNxsm
B3tSvrC/QDuxXx4/n33Yljqmj5dLHxc/IrbJ3rCX7RkC9yZhBtCmRXXivqc1VZmL
hKj7lZD5y0tC9++rbxjLxTE66xfVXeLa6wtUfDhPTcQmpIhxwI0=
=r4BS
-END PGP SIGNATURE End Message ---

Bug#1023953: marked as done (ros-geometry2 FTBFS with Python 3.11 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 16:51:03 +
with message-id 
and subject line Bug#1023953: fixed in ros-ros-comm 1.15.14+ds-5
has caused the Debian Bug report #1023953,
regarding ros-geometry2 FTBFS with Python 3.11 as supported version
to be marked as done.

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

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


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

https://buildd.debian.org/status/logs.php?pkg=ros-geometry2=0.7.6-1%2Bb1

...
make  -f 
tf2_kdl/CMakeFiles/_run_tests_tf2_kdl_rostest_test_test.launch.dir/build.make 
tf2_kdl/CMakeFiles/_run_tests_tf2_kdl_rostest_test_test.launch.dir/depend
make[5]: Entering directory '/<>/.pybuild/cpython3_3.11/build'
cd /<>/.pybuild/cpython3_3.11/build && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /<> /<>/tf2_kdl 
/<>/.pybuild/cpython3_3.11/build 
/<>/.pybuild/cpython3_3.11/build/tf2_kdl 
/<>/.pybuild/cpython3_3.11/build/tf2_kdl/CMakeFiles/_run_tests_tf2_kdl_rostest_test_test.launch.dir/DependInfo.cmake
 --color=
make[5]: Leaving directory '/<>/.pybuild/cpython3_3.11/build'
make  -f 
tf2_kdl/CMakeFiles/_run_tests_tf2_kdl_rostest_test_test.launch.dir/build.make 
tf2_kdl/CMakeFiles/_run_tests_tf2_kdl_rostest_test_test.launch.dir/build
make[5]: Entering directory '/<>/.pybuild/cpython3_3.11/build'
cd /<>/.pybuild/cpython3_3.11/build/tf2_kdl && 
../catkin_generated/env_cached.sh /usr/bin/python3.11 
/usr/share/catkin/cmake/test/run_tests.py 
/<>/.pybuild/cpython3_3.11/build/test_results/tf2_kdl/rostest-test_test.xml
 "/usr/bin/python3.11 /usr/bin/rostest --pkgdir=/<>/tf2_kdl 
--package=tf2_kdl --results-filename test_test.xml --results-base-dir 
\"/<>/.pybuild/cpython3_3.11/build/test_results\" 
/<>/tf2_kdl/test/test.launch "
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: ros-ros-comm
Source-Version: 1.15.14+ds-5
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
ros-ros-comm, 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.
Jochen Sprickerhof  (supplier of updated ros-ros-comm 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 17:37:18 +0100
Source: ros-ros-comm
Architecture: source
Version: 1.15.14+ds-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1023953
Changes:
 ros-ros-comm (1.15.14+ds-5) unstable; urgency=medium
 .
   * Add rosgraph patch for Python 3.11 (Closes: #1023953)
Checksums-Sha1:
 114e2f2fd08293ea81c4b8693d533269a3af0427 5327 ros-ros-comm_1.15.14+ds-5.dsc
 ca795b21766fac8297a3c6f42b26e90fbcfe5e79 21488 
ros-ros-comm_1.15.14+ds-5.debian.tar.xz
 56d5045823e64a6447adadc85d692a2df5dbda4c 12675 
ros-ros-comm_1.15.14+ds-5_source.buildinfo
Checksums-Sha256:
 cc58dd88a4db885a48dbeafe44e9c277ee876fcda6a45448223a2431f1291410 5327 
ros-ros-comm_1.15.14+ds-5.dsc
 03fb719824b5561a144d2230bbc56272edf1782080da969f2550644081c21e04 21488 
ros-ros-comm_1.15.14+ds-5.debian.tar.xz
 4b754b3f0afa62e4e2577a9a8d24e235ac330c72e3e6eecd10e1fda2ad9e39b4 12675 
ros-ros-comm_1.15.14+ds-5_source.buildinfo
Files:
 8934d4398c8ee2fe0005288e7eaf5a30 5327 libs optional 
ros-ros-comm_1.15.14+ds-5.dsc
 79ea9fd2061968a5317de7b552abe732 21488 libs optional 
ros-ros-comm_1.15.14+ds-5.debian.tar.xz
 26604b5167d2d39b9608079f4e2c5ba2 12675 libs optional 
ros-ros-comm_1.15.14+ds-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmNxHVoACgkQW//cwljm
lDPWeRAAnl+H1XAKYxAa2fAtkj9L41X0pyZHjisTDFaLvVGmN3kEbGXrqb2ymscD
kTirOi1butcdjpsAIaCX02Vb2n5z2jYaowE1K6ZXwmtmXC8d46PVjALq6HqZf/Wa
Ju16G1/+RV28RkiL6PeEyVLOmYbH/etq6oLAsBbGQpnIotubH0CoxaXw34i2iurX
MnnPyKbhHNpcbGaXF/P82aXee5xZBNC8qrF9Xw9pxLkkHS/MI92OAVPTXEYwrklW
pqz1+Ki596Em0mbfVV9OJIgfK0WUaI0uI1wWcbm928NSn9Azvi0t+BgDMzXSmWp8
08LL0wL0kuj1jQfCDumlAKAId9WgsO3KqDaViYHpI+GlwmJIIZaABWmLzGmwvCTL

Bug#1023910: marked as done (python-snappy FTBFS with Python 3.11 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 16:50:16 +
with message-id 
and subject line Bug#1023910: fixed in python-snappy 0.5.3-1.2
has caused the Debian Bug report #1023910,
regarding python-snappy FTBFS with Python 3.11 as supported version
to be marked as done.

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

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


-- 
1023910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-snappy
Version: 0.5.3-1.1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/fetch.php?pkg=python-snappy=amd64=0.5.3-1.1%2Bb6=1668243268=0

...
In file included from /usr/include/python3.11/Python.h:44,
 from snappy/snappymodule.cc:28:
snappy/snappymodule.cc: In function ‘PyObject* maybe_resize(PyObject*, size_t, 
size_t)’:
/usr/include/python3.11/object.h:145:30: error: lvalue required as left operand 
of assignment
  145 | #  define Py_SIZE(ob) Py_SIZE(_PyObject_CAST(ob))
  |   ~~~^~~~
snappy/snappymodule.cc:71:13: note: in expansion of macro ‘Py_SIZE’
   71 | Py_SIZE(str) = actual_size;
  | ^~~
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 
--- End Message ---
--- Begin Message ---
Source: python-snappy
Source-Version: 0.5.3-1.2
Done: Stefano Rivera 

We believe that the bug you reported is fixed in the latest version of
python-snappy, 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.
Stefano Rivera  (supplier of updated python-snappy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Nov 2022 14:40:44 +0200
Source: python-snappy
Architecture: source
Version: 0.5.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: Shell Xu 
Changed-By: Stefano Rivera 
Closes: 1023910
Changes:
 python-snappy (0.5.3-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add support for Python 3.11. (Closes: #1023910)
Checksums-Sha1:
 f0c215e6576d8509f7914b1ac1cff7e761575efc 1249 python-snappy_0.5.3-1.2.dsc
 4a6ea387d35ae4deff5ccfca4f87604aa7795040 5548 
python-snappy_0.5.3-1.2.debian.tar.xz
 81964e6c0702a221f9b0e31e84aada702e2e6b36 6427 
python-snappy_0.5.3-1.2_source.buildinfo
Checksums-Sha256:
 6047a47ccdb2fe82122c7126abe7d1e2d4ccaffd0130475d0143e04dbcf8e134 1249 
python-snappy_0.5.3-1.2.dsc
 870e305127bd2cd30e1919b8e7bb6ea55470a1fcd48d37a7a1a84b5274059df0 5548 
python-snappy_0.5.3-1.2.debian.tar.xz
 f39126a4a45e06338828864c557497e0c1271264882187d056f6030e1edd8bd8 6427 
python-snappy_0.5.3-1.2_source.buildinfo
Files:
 92061070e0cd2c9fbd670df3e481e2f4 1249 python optional 
python-snappy_0.5.3-1.2.dsc
 1a270169c3b022e4724b3e80f0fdd47d 5548 python optional 
python-snappy_0.5.3-1.2.debian.tar.xz
 ef87af614549c14ca7817c38ea3afab0 6427 python optional 
python-snappy_0.5.3-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY2+VXxQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2FTQAQDSk6NZGL7HF/mG9guxtZukEznCtqHF
V2la6qMPw3DndwD/ajzKDb3TGXE/t3p09ilTrwzFU7g/W1cQBSfqs7DkeQI=
=DQkl
-END PGP SIGNATURE End Message ---

Processed: reassign 1023953 to python3-rosgraph, affects 1023953

[Debian Bug Tracking System]

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

> reassign 1023953 python3-rosgraph
Bug #1023953 [src:ros-geometry2] ros-geometry2 FTBFS with Python 3.11 as 
supported version
Bug reassigned from package 'src:ros-geometry2' to 'python3-rosgraph'.
No longer marked as found in versions ros-geometry2/0.7.6-1.
Ignoring request to alter fixed versions of bug #1023953 to the same values 
previously set
> affects 1023953 ros-geometry2
Bug #1023953 [python3-rosgraph] ros-geometry2 FTBFS with Python 3.11 as 
supported version
Added indication that 1023953 affects ros-geometry2
> thanks
Stopping processing here.

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

Bug#1016384: marked as done (pampi: Not all dependencies listed in package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 16:20:23 +
with message-id 
and subject line Bug#1016384: fixed in pampi 1.1+dfsg1-6
has caused the Debian Bug report #1016384,
regarding pampi: Not all dependencies listed in package
to be marked as done.

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

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


-- 
1016384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pampi
Version: 1.1+dfsg1-5
Severity: grave
Tags: ftbfs
Justification: renders package unusable
X-Debbugs-Cc: a...@pasteiner.eu




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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 pampi depends on:
ii  fonts-katex 0.13.11+~cs6.0.0-3
ii  fonts-opendyslexic  20160623-4
ii  fonts-sil-andika6.101-2
ii  hovercraft  2.7-3
ii  jsxgraph1.4.5+dfsg1-1
ii  libjs-bootstrap 3.4.1+dfsg-2
ii  libjs-c30.4.11+dfsg-4
ii  libjs-impress   1.1.0-2
ii  libjs-katex 0.13.11+~cs6.0.0-3
ii  libjs-marked4.0.17+ds+~4.0.3-1
ii  macaulay2-common1.20+ds-7
ii  pandoc  2.9.2.1-3+b2
ii  python3 3.10.5-3

pampi recommends no packages.

pampi suggests no packages.

-- no debconf information

Running the programm Fails with a python Traceback Stating:
Traceback (most recent call last):
  File "/usr/share/pampi/pampi.pyw", line 64, in 
import main
  File "/usr/share/pampi/libs/main.py", line 39, in 
import utils_webengine
  File "/usr/share/pampi/libs/utils_webengine.py", line 53, in 
from PyQt5.QtWebKitWidgets import QWebView as QWebEngineView
ModuleNotFoundError: No module named 'PyQt5.QtWebKitWidgets'

This can possible resolved by installing python3-pyqt5-qtwebengine 
adding this pakages to the dependencylist should solve this problem for 
everyone installing the pakage in the future.
--- End Message ---
--- Begin Message ---
Source: pampi
Source-Version: 1.1+dfsg1-6
Done: Georges Khaznadar 

We believe that the bug you reported is fixed in the latest version of
pampi, 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.
Georges Khaznadar  (supplier of updated pampi 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: Sun, 13 Nov 2022 16:46:26 +0100
Source: pampi
Architecture: source
Version: 1.1+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1016384
Changes:
 pampi (1.1+dfsg1-6) unstable; urgency=medium
 .
   * added a new dependency on python3-pyqt5.qtwebengine. Closes: #1016384
   * removed copyright notices about excluded files
Checksums-Sha1:
 6d2059e94c5c4a1b334f4d32753839024d23d07e 1935 pampi_1.1+dfsg1-6.dsc
 e732e921190ca3ced1d06e40a498959626d0c867 20188 pampi_1.1+dfsg1-6.debian.tar.xz
 148e8ef5bc421ca7261dce1e9de79d7bf6f67ec0 10878 
pampi_1.1+dfsg1-6_source.buildinfo
Checksums-Sha256:
 da22b090cdcb01fafa1303b00b4ffe3a10de585404b01fc919e9adad1dedc6b7 1935 
pampi_1.1+dfsg1-6.dsc
 e10a6c61dc280ac4450281690dfd3a11b15c56dc09ac66464f85b9f631ffcc0a 20188 
pampi_1.1+dfsg1-6.debian.tar.xz
 d4c594920be2b7b333a7f930bf49bf79a2e49c87c5988a0747f9133c5d7cc1c0 10878 
pampi_1.1+dfsg1-6_source.buildinfo
Files:
 a7ed285790cd42f87f1a9d439ed0f315 1935 text optional pampi_1.1+dfsg1-6.dsc
 ad065d0fdaa20dcd759c4d6d3fbf2158 20188 text optional 
pampi_1.1+dfsg1-6.debian.tar.xz
 559fb44995e5f1d4523195f8a37d39c0 10878 text optional 
pampi_1.1+dfsg1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmNxE1kUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmi3A//f3G/HsVdIOD2qKAWORvNXJxT7vpg
vZwO4CI4S+qff2Lsm6CPFOX6ujpWwzVtdizz9pRzQu8BDNXiiuW5XSG4FY8lt25P

Bug#1019629: marked as done (ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 16:11:55 +
with message-id 
and subject line Bug#1019629: fixed in ruby-heapy 0.2.0-2
has caused the Debian Bug report #1019629,
regarding ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:  
RuntimeError:
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.)


-- 
1019629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-heapy
Version: 0.2.0-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 ruby-heapy with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>  RuntimeError:
>Ignoring debug-1.4.0 because its extensions are not built. Try: gem 
> pristine debug --version 1.4.0
>  # ./spec/spec_helper.rb:17:in `block in run'
>  # ./spec/spec_helper.rb:15:in `run'
>  # ./spec/heap_inspect_spec.rb:56:in `block (3 levels) in  (required)>'
> 
> Finished in 7.82 seconds (files took 0.11838 seconds to load)
> 8 examples, 7 failures
> 
> Failed examples:
> 
> rspec ./spec/heap_inspect_spec.rb:30 # Heapy drills down all
> rspec ./spec/heap_inspect_spec.rb:35 # Heapy drills down
> rspec ./spec/heap_inspect_spec.rb:9 # Heapy heap diffs diffs 2 heaps
> rspec ./spec/heap_inspect_spec.rb:14 # Heapy heap diffs diffs 3 heaps
> rspec ./spec/heap_inspect_spec.rb:20 # Heapy heap diffs outputs the diff
> rspec ./spec/heap_inspect_spec.rb:50 # Heapy with no generation specified 
> analyzes
> rspec ./spec/heap_inspect_spec.rb:55 # Heapy with no generation specified 
> summarizes
> 
> /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/ruby-heapy/ruby-heapy_0.2.0-1+rebuild1663007689_amd64-2022-09-12T18:34:51Z.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 ---
Source: ruby-heapy
Source-Version: 0.2.0-2
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-heapy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 16:21:36 +0100
Source: ruby-heapy
Architecture: source
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1019629
Changes:
 ruby-heapy (0.2.0-2) unstable; urgency=medium
 .
   * Team upload
   * Bump Standards-Version to 4.6.1 (no changes needed)
   * Add patch trun_with_correct_ruby_version.patch
 - ensures that scripts run during the tests are called with the tested
   ruby version (Closes:#1019629)
Checksums-Sha1:
 b2431e41c20b1513ea1b4e8735ff65bed2ac5f1c 1422 ruby-heapy_0.2.0-2.dsc
 731405151bccad6b8e6d27bdd6be1e20be0fb36e 6085006 ruby-heapy_0.2.0.orig.tar.gz
 85722fdbfe1357b974ed313aed3be1e875e3b074 4204 

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

[Andreas Metzler]

On 2022-11-12 Andreas Metzler  wrote:
> On 2022-11-11 Vincent Lefevre  wrote:
> [...]
>> file and other configuration options.  The options that need to be added
>> to the compiler invocation at compile time are output by the ‘--cflags’
>> option to ‘gpgme-config’.  The following example shows how it can be
>> used at the command line:

>>  gcc -c foo.c `gpgme-config --cflags`

>>Adding the output of ‘gpgme-config --cflags’ to the compiler command
> [...]

> That is clearly suboptimal. I am also do not fond of the fact that
> documentation for AM_PATH_GPGME requiring an earlier invocation of
> AM_PATH_GPG_ERROR seems to be missing.

I have filed https://dev.gnupg.org/T6273 (AM_PATH_GPG_ERROR
predependency) and https://dev.gnupg.org/T6274 (outdated docs).

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1023965: pandas FTBFS with Python 3.11 as supported version

[Adrian Bunk]

On Sun, Nov 13, 2022 at 02:44:42PM +, Rebecca N. Palmer wrote:
> Control: block 1021984 by -1
> Control: tags -1 fixed-upstream fixed-in-experimental
> 
> There's more than just those 2[0].
> Some are tests that expect an error and check the message (not just the
> type), and fail because the message has been reworded - these should be
> trivial to fix.
> The 2 in test_null_quote_char/test_null_byte_char don't look like this, but
> also don't look like major problems.
> 
> The ones that may need someone else's attention (because DMs can't upload
> arbitrary packages) are that Debian's parso is too old to support 3.11 -
> I've filed a new bug about this.
> 
> I'm in the process of moving to pandas 1.5 (#1017809), which probably fixes
> these[1], but also breaks a few reverse dependencies[2].  Do I take the
> 'serious' tag to mean this is urgent enough to fix in 1.3?

Graham did an upload ignoring test failures,[1] if the problems are only 
in tests this might be good enough as a short-term fix?

> [0] 
> https://launchpadlibrarian.net/631797785/buildlog_ubuntu-lunar-amd64.pandas_1.3.5+dfsg-5build1_BUILDING.txt.gz
> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=pandas=ppc64el=1.5.1%2Bdfsg-3=1668226153=0
> (the lxml-not-found errors are probably because it hadn't been built in 3.11
> yet)
> [2] https://qa.debian.org/excuses.php?experimental=1=pandas and
> maybe more because I haven't done a build test yet

cu
Adrian

[1] 
https://tracker.debian.org/news/1384166/accepted-pandas-135dfsg-6-source-into-unstable/

Bug#1020060: statsmodels sometimes FTBFS

[Rebecca N. Palmer]

It also doesn't fail on the buildds.  (The failed binNMU of statsmodels 
for Python 3.11 is instead the expected result of trying to build 
statsmodels on a Python version without pandas - pandas failed due to 
#1023965.)


Is there anything special about the mass-rebuild environment that might 
explain why it fails there and not elsewhere?  (Possibly the standard 
email should link to a description of that environment?)  Has it failed 
there more than once?

Processed: block 1021984 with 1023039

[Debian Bug Tracking System]

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

> block 1021984 with 1023039
Bug #1021984 [release.debian.org] (some kind of) transition: add python3.11 as 
a supported python3 version
1021984 was blocked by: 1021871 1023965
1021984 was not blocking any bugs.
Added blocking bug(s) of 1021984: 1023039
> thanks
Stopping processing here.

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

Processed: Re: Bug#1023965: pandas FTBFS with Python 3.11 as supported version

[Debian Bug Tracking System]

Processing control commands:

> block 1021984 by -1
Bug #1021984 [release.debian.org] (some kind of) transition: add python3.11 as 
a supported python3 version
1021984 was blocked by: 1021871
1021984 was not blocking any bugs.
Added blocking bug(s) of 1021984: 1023965
> tags -1 fixed-upstream fixed-in-experimental
Bug #1023965 [src:pandas] pandas FTBFS with Python 3.11 as supported version
Added tag(s) fixed-in-experimental and fixed-upstream.

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

Bug#1023965: pandas FTBFS with Python 3.11 as supported version

[Rebecca N. Palmer]

Control: block 1021984 by -1
Control: tags -1 fixed-upstream fixed-in-experimental

There's more than just those 2[0].
Some are tests that expect an error and check the message (not just the 
type), and fail because the message has been reworded - these should be 
trivial to fix.
The 2 in test_null_quote_char/test_null_byte_char don't look like this, 
but also don't look like major problems.


The ones that may need someone else's attention (because DMs can't 
upload arbitrary packages) are that Debian's parso is too old to support 
3.11 - I've filed a new bug about this.


I'm in the process of moving to pandas 1.5 (#1017809), which probably 
fixes these[1], but also breaks a few reverse dependencies[2].  Do I 
take the 'serious' tag to mean this is urgent enough to fix in 1.3?


[0] 
https://launchpadlibrarian.net/631797785/buildlog_ubuntu-lunar-amd64.pandas_1.3.5+dfsg-5build1_BUILDING.txt.gz
[1] 
https://buildd.debian.org/status/fetch.php?pkg=pandas=ppc64el=1.5.1%2Bdfsg-3=1668226153=0 
(the lxml-not-found errors are probably because it hadn't been built in 
3.11 yet)
[2] https://qa.debian.org/excuses.php?experimental=1=pandas and 
maybe more because I haven't done a build test yet

Bug#1019631: marked as done (ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 14:56:43 +
with message-id 
and subject line Bug#1019631: fixed in ruby-httparty 0.20.0-2
has caused the Debian Bug report #1019631,
regarding ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
RuntimeError:
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.)


-- 
1019631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-httparty
Version: 0.20.0-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 ruby-httparty with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> RuntimeError:
>   coverage measurement is already setup
> # 
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
>  `start'
> # 
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
>  `start_coverage_with_criteria'
> # 
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:343:in
>  `start_coverage_measurement'
> # 
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:59:in
>  `start'
> # ./spec/spec_helper.rb:2:in `'
> # ./spec/httparty_spec.rb:1:in `require_relative'
> # ./spec/httparty_spec.rb:1:in `'
> No examples found.
> 
> Finished in 0.4 seconds (files took 0.14035 seconds to load)
> 0 examples, 0 failures, 18 errors occurred outside of examples
> 
> Coverage report generated for RSpec to /<>/coverage. 0 / 0 LOC 
> (100.0%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has 
> been detected
> /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/ruby-httparty/ruby-httparty_0.20.0-1+rebuild1663007717_amd64-2022-09-12T18:35:18Z.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 ---
Source: ruby-httparty
Source-Version: 0.20.0-2
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-httparty 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2022 15:10:17 +0100
Source: ruby-httparty
Architecture: source
Version: 0.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1019631
Changes:
 ruby-httparty (0.20.0-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
 .
   [ Cédric Boutillier ]
   * Rename no_pry_in_specs.patch as clean_spec_helper.patch
 - modify to remove simplecov from spec_helper. SimpleCov didn't like to be
   loaded for two different ruby versions (Closes: #1019631)
   * Remove ruby-simplecov from build-dependencies
Checksums-Sha1:
 be3b4bf234aa7a0f75bfe2e0d2377e4e9e255dce 1554 

Bug#1022516: marked as done (python-preshed: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 14:54:05 +
with message-id 
and subject line Bug#1022516: fixed in python-preshed 3.0.8-1
has caused the Debian Bug report #1022516,
regarding python-preshed: FTBFS: distutils.errors.DistutilsSetupError: each 
element of 'ext_modules' option must be an Extension instance or 2-tuple
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:7: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /<>/bin/cythonize.py:45: DeprecationWarning: The distutils 
> package is deprecated and slated for removal in Python 3.12. Use setuptools 
> or check PEP 632 for potential alternatives
>   from distutils.version import LooseVersion
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: /<>/preshed/maps.pxd
>   tree = Parsing.p_module(s, pxd, full_module_name)
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: /<>/preshed/counter.pxd
>   tree = Parsing.p_module(s, pxd, full_module_name)
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: /<>/preshed/bloom.pxd
>   tree = Parsing.p_module(s, pxd, full_module_name)
> Processing maps.pyx
> Processing counter.pyx
> Processing bloom.pyx
> Cythonizing sources
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:7: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.build_ext import build_ext
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Cythonizing sources
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_preshed/build/preshed
> copying preshed/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_preshed/build/preshed
> copying preshed/about.py -> 
> /<>/.pybuild/cpython3_3.10_preshed/build/preshed
> creating /<>/.pybuild/cpython3_3.10_preshed/build/preshed/tests
> copying preshed/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_preshed/build/preshed/tests
> copying