Bug#1020137: marked as done (celery: FTBFS: KeyError: 4)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 06:49:09 +
with message-id 
and subject line Bug#1020137: fixed in celery 5.2.6-3
has caused the Debian Bug report #1020137,
regarding celery: FTBFS: KeyError: 4
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /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 config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /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 build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/canvas.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/platforms.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/__main__.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/states.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/exceptions.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/_state.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/bootsteps.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/schedules.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/signals.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/beat.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/result.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> copying celery/local.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery
> creating /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/components.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/worker.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/pidbox.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/autoscale.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/control.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/heartbeat.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/state.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/strategy.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/loops.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> copying celery/worker/request.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/worker
> creating /<>/.pybuild/cpython3_3.10_celery/build/celery/loaders
> copying celery/loaders/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/loaders
> copying celery/loaders/default.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/loaders
> copying celery/loaders/app.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/loaders
> copying celery/loaders/base.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/loaders
> creating /<>/.pybuild/cpython3_3.10_celery/build/celery/utils
> copying celery/utils/graph.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/utils
> copying celery/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/utils
> copying celery/utils/imports.py -> 
> /<>/.pybuild/cpython3_3.10_celery/build/celery/utils
> copying celery/utils/threads.py -> 
> 

Bug#1021078: marked as done (billiard breaks celery autopkgtest: 48 failed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 06:49:09 +
with message-id 
and subject line Bug#1020137: fixed in celery 5.2.6-3
has caused the Debian Bug report #1020137,
regarding billiard breaks celery autopkgtest: 48 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.)


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

Source: billiard, celery
Control: found -1 billiard/4.0.2-1
Control: found -1 celery/5.2.6-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
billiard   from testing4.0.2-1
celery from testing5.2.6-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of billiard to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/celery/26573246/log.gz

=== FAILURES 
===
__ test_EagerResult.test_wait_raises 
___


self = 

def test_wait_raises(self):
res = self.raising.apply(args=[3, 3])
with pytest.raises(KeyError):

  res.wait()


t/unit/tasks/test_result.py:946: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , timeout = None
propagate = True, disable_sync_subtasks = True, kwargs = {}

def get(self, timeout=None, propagate=True,
disable_sync_subtasks=True, **kwargs):
if disable_sync_subtasks:
assert_will_not_block()
if self.successful():
return self.result
elif self.state in states.PROPAGATE_STATES:
if propagate:

  raise self.result if isinstance(

self.result, Exception) else Exception(self.result)
E   billiard.einfo.ExceptionWithTraceback: E   """
E   Traceback (most recent call last):
E File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

E   R = retval = fun(*args, **kwargs)
E File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

E   raise KeyError(x, y)
E   KeyError: (3, 3)
E   """

celery/result.py:1005: ExceptionWithTraceback
-- Captured log call 
---
ERRORcelery.app.trace:trace.py:265 Task 
t.unit.tasks.test_result.raising[09b01603-8e3c-4417-8c1c-0c906d383510] 
raised unexpected: ExceptionWithTraceback()

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

R = retval = fun(*args, **kwargs)
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

raise KeyError(x, y)
billiard.einfo.ExceptionWithTraceback: """
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

R = retval = fun(*args, **kwargs)
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

raise KeyError(x, y)
KeyError: (3, 3)
"""
_ test_task_retries.test_retry 
_


self = 

def test_retry(self):
self.retry_task.max_retries = 3
self.retry_task.iterations = 0
self.retry_task.apply([0xFF, 0x])

  assert self.retry_task.iterations == 4

E   assert 1 == 4
E+  where 1 = <@task: t.unit.tasks.test_tasks.retry_task of 
celery.tests at 0x7fbc36762350>.iterations
E+where <@task: 

Processed: Bug#1023317 marked as pending in zsh

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023317 [zsh,zsh-static] zsh: re-adds /bin/zsh to /etc/shells on upgrade
Ignoring request to alter tags of bug #1023317 to the same tags previously set

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

Bug#1023317: marked as pending in zsh

[Axel Beckert]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/zsh/-/commit/8dff29f4cd9663746b51ffad9317e68a2cd00a55


Update /etc/shells using dpkg triggers

Closes: #1023317


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023317

Processed: tagging 1023317

[Debian Bug Tracking System]

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

> tags 1023317 + pending
Bug #1023317 [zsh,zsh-static] zsh: re-adds /bin/zsh to /etc/shells on upgrade
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1023318: marked as done (screen: re-adds /usr/bin/screen to /etc/shells on upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 05:05:25 +
with message-id 
and subject line Bug#1023318: fixed in screen 4.9.0-3
has caused the Debian Bug report #1023318,
regarding screen: re-adds /usr/bin/screen 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.)


-- 
1023318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screen
Version: 4.9.0-2
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

When upgrading or reinstalling screen, it adds /usr/bin/screen 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 screen-4.9.0/debian/changelog screen-4.9.0/debian/changelog
--- screen-4.9.0/debian/changelog   2022-08-24 03:45:18.0 +0200
+++ screen-4.9.0/debian/changelog   2022-11-02 10:03:05.0 +0100
@@ -1,3 +1,10 @@
+screen (4.9.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update /etc/shells using dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 10:03:05 +0100
+
 screen (4.9.0-2) unstable; urgency=medium
 
   * Add patch to fix bash example in man page. (LP: #1986839) Thanks to
diff --minimal -Nru screen-4.9.0/debian/control screen-4.9.0/debian/control
--- screen-4.9.0/debian/control 2022-08-23 19:15:25.0 +0200
+++ screen-4.9.0/debian/control 2022-11-02 10:03:05.0 +0100
@@ -18,7 +18,8 @@
 Package: screen
 Architecture: any
 Depends: ${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ debianutils (>= 5.3-1~)
 Suggests: byobu | screenie | iselect (>= 1.4.0-1),
   ncurses-term
 Description: terminal multiplexer with VT100/ANSI terminal emulation
diff --minimal -Nru screen-4.9.0/debian/rules screen-4.9.0/debian/rules
--- screen-4.9.0/debian/rules   2021-08-05 15:30:52.0 +0200
+++ screen-4.9.0/debian/rules   2022-11-02 10:03:02.0 +0100
@@ -63,6 +63,7 @@
rm -f $(ROOT)/usr/share/info/dir*
# Remove documentation from udeb
rm -rf $(ROOT_UDEB)/usr/share/info $(ROOT_UDEB)/usr/share/man
+   install -D -m644 debian/shells 
$(ROOT)/usr/share/debianutils/shells.d/screen
 
 override_dh_installinit:
dh_installinit --no-start --init-script=screen-cleanup
diff --minimal -Nru screen-4.9.0/debian/screen.postinst 
screen-4.9.0/debian/screen.postinst
--- screen-4.9.0/debian/screen.postinst 2021-02-23 11:18:41.0 +0100
+++ screen-4.9.0/debian/screen.postinst 2022-11-02 10:00:59.0 +0100
@@ -30,8 +30,6 @@
   if [ ! -e $servicefile ]; then
   ln -s /dev/null $servicefile
   fi
-
-  add-shell /usr/bin/screen || true
 fi
 
 #DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/screen.postrm 
screen-4.9.0/debian/screen.postrm
--- screen-4.9.0/debian/screen.postrm   2021-02-18 09:51:15.0 +0100
+++ screen-4.9.0/debian/screen.postrm   2022-11-02 10:01:12.0 +0100
@@ -13,8 +13,4 @@
   rmdir -p --ignore-fail-on-non-empty /lib/systemd/system
 fi
 
-if [ "$1" = disappear ]; then
-  remove-shell /usr/bin/screen || true
-fi
-
 #DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/screen.prerm 
screen-4.9.0/debian/screen.prerm
--- screen-4.9.0/debian/screen.prerm2021-02-18 09:51:15.0 +0100
+++ screen-4.9.0/debian/screen.prerm1970-01-01 01:00:00.0 +0100
@@ -1,8 +0,0 @@
-#!/bin/sh
-set -e
-
-if [ "$1" = remove ] || [ "$1" = deconfigure ]; then
-  remove-shell /usr/bin/screen || true
-fi 
-
-#DEBHELPER#
diff --minimal -Nru screen-4.9.0/debian/shells screen-4.9.0/debian/shells
--- screen-4.9.0/debian/shells  1970-01-01 01:00:00.0 +0100
+++ screen-4.9.0/debian/shells  2022-11-02 10:02:02.0 +0100
@@ -0,0 +1 @@
+/usr/bin/screen
--- End Message ---
--- Begin Message ---
Source: screen
Source-Version: 4.9.0-3
Done: Axel Beckert 

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

(This message was generated automatically at their request; if you
believe that 

Bug#1023953: ros-geometry2 FTBFS with Python 3.11 as supported version

[Adrian Bunk]

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

Bug#1023940: marked as done (Doesn't work: blank editor and shell panes)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 02:01:24 +
with message-id 
and subject line Bug#1023940: fixed in pyzo 4.12.3-1
has caused the Debian Bug report #1023940,
regarding Doesn't work: blank editor and shell panes
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.)


-- 
1023940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pyzo
Version: 4.11.2-1
Severity: grave

Launching pyzo displays the normal window, but the shell never comes up
and the editor pane never gets a prompt ; starting from a terminal
makes the following messages fly by continuously:

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?


Cheers,

J.Puydt
--- End Message ---
--- Begin Message ---
Source: pyzo
Source-Version: 4.12.3-1
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
pyzo, 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.
Julien Puydt  (supplier of updated pyzo 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 00:42:17 +0100
Source: pyzo
Architecture: source
Version: 4.12.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julien Puydt 
Closes: 1023940
Changes:
 pyzo (4.12.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (Closes: #1023940).
   * Bump Standards-Version to 4.6.1.
   * Drop NEWS.Debian.gz - it's obsolete.
   * Add a patch fixing some typos.
   * Add a patch fixing the 

Bug#1023422: marked as done (minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 01:56:35 +
with message-id 
and subject line Bug#1023422: fixed in minilla 3.1.20-1
has caused the Debian Bug report #1023422,
regarding minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' 
not allowed
to be marked as done.

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

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


-- 
1023422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minilla
Version: 3.1.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


As also seen on ci.debian.net, minilla recently started to fail its
test suite, which also makes it FTBFS:

#   Failed test 'No tests run for subtest "FileGatherer"'
#   at t/filegatherer.t line 46.
Minilla::Error::CommandExit at /build/minilla-3.1.19/blib/lib/Minilla/Logger.pm 
line 56.
Minilla::Logger::errorf("Giving up.\x{a}") called at 
/build/minilla-3.1.19/blib/lib/Minilla/Util.pm line 150
Minilla::Util::cmd("git", "submodule", "add", "file:///tmp/cNMz9BGy3K", 
"libfoo") called at /build/minilla-3.1.19/blib/lib/Minilla/Git.pm line 43
Minilla::Git::git_submodule_add("file:///tmp/cNMz9BGy3K", "libfoo") 
called at t/filegatherer.t line 70
main::init() called at t/filegatherer.t line 17
main::__ANON__() called at /usr/share/perl/5.36/Test/Builder.pm line 374
eval {...} called at /usr/share/perl/5.36/Test/Builder.pm line 374
Test::Builder::subtest(Test::Builder=HASH(0x55b66779e4c0), 
"FileGatherer", CODE(0x55b667d4a8a0)) called at 
/usr/share/perl/5.36/Test/More.pm line 809
Test::More::subtest("FileGatherer", CODE(0x55b667d4a8a0)) called at 
t/filegatherer.t line 46
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 2.
t/filegatherer.t .
ok 1 - Minilla::FileGatherer->can('new')
# Subtest: FileGatherer
[cNMz9BGy3K] $ git init
Initialized empty Git repository in /tmp/cNMz9BGy3K/.git/
[cNMz9BGy3K] $ git add .
[cNMz9BGy3K] $ git commit -m submodule
[main (root-commit) 928d506] submodule
 1 file changed, 1 insertion(+)
 create mode 100644 foo.c
[1X4gcCt02H] $ git init
Initialized empty Git repository in /tmp/1X4gcCt02H/.git/
[1X4gcCt02H] $ git add .
[1X4gcCt02H] $ git commit -m submodule
[main (root-commit) fcf8e7d] submodule
 1 file changed, 1 insertion(+)
 create mode 100644 bar.c
[75BXf3LiVD] $ git init
Initialized empty Git repository in /tmp/75BXf3LiVD/.git/
[75BXf3LiVD] $ git add .
[75BXf3LiVD] $ git submodule add file:///tmp/cNMz9BGy3K libfoo
1..0
not ok 2 - No tests run for subtest "FileGatherer"
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/2 subtests
Cloning into '/tmp/t_vUmqA512/libbar'...
fatal: transport 'file' not allowed
fatal: clone of 'file:///tmp/VnuWv09juk' into submodule path 
'/tmp/t_vUmqA512/libbar' failed
Giving up.
# No tests run!

#   Failed test 'No tests run for subtest "FileGatherer"'
#   at t/filegatherer/submodules-recursive.t line 46.
Minilla::Error::CommandExit at /build/minilla-3.1.19/blib/lib/Minilla/Logger.pm 
line 56.
Minilla::Logger::errorf("Giving up.\x{a}") called at 
/build/minilla-3.1.19/blib/lib/Minilla/Util.pm line 150
Minilla::Util::cmd("git", "submodule", "add", "file:///tmp/VnuWv09juk", 
"libbar") called at /build/minilla-3.1.19/blib/lib/Minilla/Git.pm line 43
Minilla::Git::git_submodule_add("file:///tmp/VnuWv09juk", "libbar") 
called at t/filegatherer/submodules-recursive.t line 86
main::create_deep_submodule_repo("foo") called at 
t/filegatherer/submodules-recursive.t line 52
main::init() called at t/filegatherer/submodules-recursive.t line 17
main::__ANON__() called at /usr/share/perl/5.36/Test/Builder.pm line 374
eval {...} called at /usr/share/perl/5.36/Test/Builder.pm line 374
Test::Builder::subtest(Test::Builder=HASH(0x55c165f41840), 
"FileGatherer", CODE(0x55c166599dd0)) called at 
/usr/share/perl/5.36/Test/More.pm line 809
Test::More::subtest("FileGatherer", CODE(0x55c166599dd0)) called at 
t/filegatherer/submodules-recursive.t line 46
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 2.
t/filegatherer/submodules-recursive.t 
ok 1 - Minilla::FileGatherer->can('new')
# Subtest: FileGatherer
[t_vUmqA512] $ git init
Initialized empty Git repository in /tmp/t_vUmqA512/.git/
[t_vUmqA512] $ git add .
[t_vUmqA512] $ git commit -m submodule

Bug#1023689: marked as done (minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2022 01:56:35 +
with message-id 
and subject line Bug#1023422: fixed in minilla 3.1.20-1
has caused the Debian Bug report #1023422,
regarding minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' 
not allowed
to be marked as done.

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

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


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

This package fails to build from source on current sid.

   Test Summary Report
   ---
   t/filegatherer.t   (Wstat: 65280 (exited 255) Tests: 
2 Failed: 1)
 Failed test:  2
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   t/filegatherer/submodules-recursive.t  (Wstat: 65280 (exited 255) Tests: 
2 Failed: 1)
 Failed test:  2
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   t/project/in_submodule.t   (Wstat: 65280 (exited 255) Tests: 
1 Failed: 1)
 Failed test:  1
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   Files=62, Tests=170, 105 wallclock secs ( 0.42 usr  0.08 sys + 44.82 cusr 
11.18 csys = 56.50 CPU)
   Result: FAIL
 
The build log is rather hard to read as there are intentional test
failures sprayed all over, but I think the main thing that is new is
messages like this:

  Cloning into '/tmp/uGVjCBrSr3/libfoo'...
  fatal: transport 'file' not allowed
  fatal: clone of 'file:///tmp/hhqN4NFWJc' into submodule path 
'/tmp/uGVjCBrSr3/libfoo' failed

I've tested that building in bookworm succeeds, but injecting
git_1%3a2.38.1-1_amd64.deb (and git-man_1%3a2.38.1-1_all.deb) makes it
fail. I assume this is about

  https://security-tracker.debian.org/tracker/CVE-2022-39253

which was fixed in git 1:2.38.1-1.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: minilla
Source-Version: 3.1.20-1
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
minilla, 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.
gregor herrmann  (supplier of updated minilla 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 01:25:25 +0100
Source: minilla
Architecture: source
Version: 3.1.20-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1023422
Changes:
 minilla (3.1.20-1) unstable; urgency=medium
 .
   * Import upstream version 3.1.19.
   * Add test dependency on libdevel-checkbin-perl for additional tests.
   * Import upstream version 3.1.20.
 Closes: #1023422
Checksums-Sha1:
 09db1d0bc49ec0d977ca7dafc27891b6adc08fd4 3121 minilla_3.1.20-1.dsc
 5efc6a4e27fd834dccf07f76217220ee9aa1e54d 94793 minilla_3.1.20.orig.tar.gz
 df4c527e1eb8efe765a9a806911ae9821775b5bd 3104 minilla_3.1.20-1.debian.tar.xz
Checksums-Sha256:
 a459a859985d01925801e6a724dbd1df884e8dba9e8ddd6f6002fc273b1d9394 3121 
minilla_3.1.20-1.dsc
 d4394b11e83466e1f7394f903ca20b137222c35544358218dd1265dedcb89cf6 94793 
minilla_3.1.20.orig.tar.gz
 73488ce93bac18fee9d98217797f9e65359515fc273e157b81022c10e3febecf 3104 
minilla_3.1.20-1.debian.tar.xz
Files:
 7f19138833e9a171cb1d9b669e971604 3121 perl optional minilla_3.1.20-1.dsc
 4f8d950ff43f333ee0b6d1f4cf11d399 94793 perl optional minilla_3.1.20.orig.tar.gz
 7555e99c39e4ad0fac76a1a15a693ca4 3104 perl optional 
minilla_3.1.20-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNwOtBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbWjw/+Pl7cmkwoJj4a7nAUhFYMTKcy30nI5awWEkRd5QAgZKwJ7d6pBUSrE5pg
WuGsn/1Ow4AwS0nDA7yCzIB47Ul2C1CcL4+mTbQOKsyxVYduOT6O/Lj5CwvjfB7X
TgmOfmcqIacwYJct5EVBxijtc8RLq6KZMiTIpbmlelGquVgvrW+BIAu6eGCHifqu
QUz0T5ZeDJ+pOoCLtNwhtI0XlfpKZ4Q8YiPDjlLVKdyduW5xVSKIEoDZV7iBzZre

Bug#1023898: qtlocation-opensource-src: FTBFS on mipsel: test timeout

[Adrian Bunk]

On Sat, Nov 12, 2022 at 09:33:22AM +0100, Sebastian Ramacher wrote:
> Source: qtlocation-opensource-src
> Version: 5.15.6+dfsg-2
> 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=qtlocation-opensource-src=mipsel=5.15.6%2Bdfsg-2%2Bb1=1668119800=0
> 
> * Finished testing of DefaultSourceTest *
> make[3]: Leaving directory 
> '/<>/tests/auto/qgeopositioninfosource'
> PASS   : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateAfterStartUpdates_SmallInterval()
> QDEBUG : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
>  listening on QHostAddress("127.0.0.1") 43715
> QWARN  : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
>  Received pending connection: QTcpSocket(0x5755d1b8) true
> PASS   : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
> QDEBUG : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
>  listening on QHostAddress("127.0.0.1") 43715
> QWARN  : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
>  Received pending connection: QTcpSocket(0x5765ea48) true
> PASS   : 
> tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateAfterStartUpdates_SmallInterval()
> PASS   : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
> QDEBUG : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout() 
> listening on QHostAddress("127.0.0.1") 43715
> QWARN  : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout() 
> Received pending connection: QTcpSocket(0x57559130) true
> PASS   : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout()
> QDEBUG : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated() 
> listening on QHostAddress("127.0.0.1") 43715
> QWARN  : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated() 
> Received pending connection: QTcpSocket(0x5765f088) true
> PASS   : 
> tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated()
> PASS   : tst_QNmeaPositionInfoSource_RealTime_Generic::cleanupTestCase()
> Totals: 47 passed, 0 failed, 0 skipped, 0 blacklisted, 187926ms
> * Finished testing of tst_QNmeaPositionInfoSource_RealTime_Generic 
> *
> make[4]: Leaving directory 
> '/<>/tests/auto/qnmeapositioninfosource/qnmeapositioninfosource_realtime_generic'
> PASS   : 
> tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
> PASS   : 
> tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
> PASS   : 
> tst_QNmeaPositionInfoSource_Simulation_Generic::removeSlotForRequestTimeout()
> PASS   : 
> tst_QNmeaPositionInfoSource_Simulation_Generic::removeSlotForPositionUpdated()
> PASS   : tst_QNmeaPositionInfoSource_Simulation_Generic::cleanupTestCase()
> Totals: 47 passed, 0 failed, 0 skipped, 0 blacklisted, 189495ms
> * Finished testing of tst_QNmeaPositionInfoSource_Simulation_Generic 
> *
> make[4]: Leaving directory 
> '/<>/tests/auto/qnmeapositioninfosource/qnmeapositioninfosource_simulation_generic'
> make[3]: Leaving directory 
> '/<>/tests/auto/qnmeapositioninfosource'
> E: Build killed with signal TERM after 150 minutes of inactivity

It did build nowon one of the fastest buildds.

> Cheers

cu
Adrian

Bug#1023951: python-pyscss FTBFS with Python 3.11 as supported version

[Adrian Bunk]

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

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

...
= test session starts ==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /<>/scss
collected 249 items / 1 skipped

../../../scss/tests/test_cli.py .[  0%]
../../../scss/tests/test_expression.py F [  2%]
../../../scss/tests/test_interactive.py ..   [  3%]
../../../scss/tests/test_misc.py FFF...  [  5%]
../../../scss/tests/test_types.py ...[  8%]
../../../scss/tests/extension/test_core.py F [ 20%]
F[ 33%]
../../../scss/tests/extension/test_extra.py  [ 34%]
../../../scss/tests/extension/compass/test_gradients.py .x   [ 35%]
../../../scss/tests/extension/compass/test_helpers.py    [ 42%]
../../../scss/tests/extension/compass/test_images.py FFF [ 43%]
../../../scss/tests/files/bugs/append.scss F [ 43%]
../../../scss/tests/files/bugs/argspec-named-arguments.scss F[ 44%]
../../../scss/tests/files/bugs/argspec-slurpy-arguments.scss F   [ 44%]
../../../scss/tests/files/bugs/at-rules-1.scss F [ 44%]
../../../scss/tests/files/bugs/at-rules-2.scss . [ 45%]
../../../scss/tests/files/bugs/at-rules-compressed-semicolon.scss F  [ 45%]
../../../scss/tests/files/bugs/at-rules-duplicate-media-queries.scss .   [ 46%]
../../../scss/tests/files/bugs/at-rules-interpolation.scss F [ 46%]
../../../scss/tests/files/bugs/base64url.scss F  [ 46%]
../../../scss/tests/files/bugs/colors-preserve-names.scss F  [ 47%]
../../../scss/tests/files/bugs/division-in-assignment.scss . [ 47%]
../../../scss/tests/files/bugs/division-vs-literal-slash.scss .  [ 48%]
../../../scss/tests/files/bugs/extend-child-selector.scss F  [ 48%]
../../../scss/tests/files/bugs/extend-common-prefix-complex.scss F   [ 48%]
../../../scss/tests/files/bugs/extend-common-prefix.scss .   [ 49%]
../../../scss/tests/files/bugs/extend-selector-order.scss F  [ 49%]
../../../scss/tests/files/bugs/for-to-vs-through.scss .  [ 50%]
../../../scss/tests/files/bugs/if-with-parentheses.scss F[ 50%]
../../../scss/tests/files/bugs/interpolation-timing.scss F   [ 51%]
../../../scss/tests/files/bugs/names-equivalence.scss F  [ 51%]
../../../scss/tests/files/bugs/selectors-adjacent-is-not-include.scss .  [ 51%]
../../../scss/tests/files/bugs/trailing-combinators.scss F   [ 52%]
../../../scss/tests/files/bugs/unit-float-precision.scss F   [ 52%]
../../../scss/tests/files/bugs/variables-font-face-default.scss F[ 53%]
../../../scss/tests/files/compass/current-color.scss F   [ 53%]
../../../scss/tests/files/compass/gradients.scss F   [ 53%]
../../../scss/tests/files/general/000-smoketest.scss F   [ 54%]
../../../scss/tests/files/general/css-calc.scss .[ 54%]
../../../scss/tests/files/general/each-destructuring-2.scss F[ 55%]
../../../scss/tests/files/general/each-destructuring-3.scss F[ 55%]
../../../scss/tests/files/general/each-destructuring.scss F  [ 55%]
../../../scss/tests/files/general/empty-list-included.scss F [ 56%]
../../../scss/tests/files/general/global-variable-exists.scss F  [ 56%]
../../../scss/tests/files/general/if-lazy.scss F [ 57%]
../../../scss/tests/files/general/interpolation-acid.scss F  [ 57%]
../../../scss/tests/files/general/interpolation-mixin-name.scss F[ 57%]
../../../scss/tests/files/general/maps-complex-keys.scss F   [ 58%]
../../../scss/tests/files/general/maps-example-lists.scss F  [ 58%]
../../../scss/tests/files/general/maps-example.scss F[ 59%]
../../../scss/tests/files/general/names-loop-variable.scss F [ 59%]
../../../scss/tests/files/general/null-values.scss F [ 59%]
../../../scss/tests/files/general/scoping-mixin-2.scss F [ 60%]
../../../scss/tests/files/general/scoping-mixin.scss F   [ 60%]
../../../scss/tests/files/general/scoping-nested-2.scss F[ 61%]
../../../scss/tests/files/general/scoping-nested.scss F  [ 61%]
../../../scss/tests/files/general/slurpy-keyword-args.scss F [ 61%]
../../../scss/tests/files/kronuz/args.scss F [ 62%]

Bug#1023529: marked as done (subversion: FTBFS: segfault in Python tests with SWIG 4.1.0)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 22:12:34 +
with message-id 
and subject line Bug#1023529: fixed in subversion 1.14.2-4
has caused the Debian Bug report #1023529,
regarding subversion: FTBFS: segfault in Python tests with SWIG 4.1.0
to be marked as done.

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

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


-- 
1023529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion
Version: 1.14.2-3
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: https://github.com/swig/swig/issues/2373 
https://github.com/apache/subversion/commit/8ff4cfd06ce554e9df31a088c9d09f45278c6de4
 https://svn.apache.org/repos/asf/subversion/trunk@1904167

subversion FTBFS in sid (on all arches, but detected below on amd64 and
by the buildds on riscv64) due to a segfault in the Python tests when
building with SWIG 4.1.0. The issue has been fixed upstream in the
subversion git/svn repos, see the URLs above.

   pabs@barriere:~$ dd-schroot-cmd -y -c $sessionid apt-get build-dep subversion
   ...
   Get:286 https://deb.debian.org/debian sid/main amd64 swig4.0 amd64 4.1.0-0.1 
[1387 kB]
   Get:287 https://deb.debian.org/debian sid/main amd64 swig all 4.1.0-0.1 [321 
kB]
   ...
   Selecting previously unselected package swig4.0.
   Preparing to unpack .../285-swig4.0_4.1.0-0.1_amd64.deb ...
   Unpacking swig4.0 (4.1.0-0.1) ...
   Selecting previously unselected package swig.
   Preparing to unpack .../286-swig_4.1.0-0.1_all.deb ...
   Unpacking swig (4.1.0-0.1) ...
   ...
   Setting up swig4.0 (4.1.0-0.1) ...
   ...
   Setting up swig (4.1.0-0.1) ...
   ...
   pabs@barriere:~$ schroot -r -c $sessionid
   (sid_amd64-dchroot)pabs@barriere:~$ apt source subversion
   ...
   (sid_amd64-dchroot)pabs@barriere:~$ cd subversion-*/
   (sid_amd64-dchroot)pabs@barriere:~/subversion-1.14.2$ debuild -J10
   ...
   finished...
   make[2]: Leaving directory '/home/pabs/subversion-1.14.2/BUILD'
   make[1]: Leaving directory '/home/pabs/subversion-1.14.2'
  debian/rules override_dh_auto_test-arch
   make[1]: Entering directory '/home/pabs/subversion-1.14.2'
   /usr/bin/make -f debian/rules check-swig-py check-swig-pl check-swig-rb 
check-javahl check
   make[2]: Entering directory '/home/pabs/subversion-1.14.2'
   make[2]: warning: -j10 forced in makefile: resetting jobserver mode.
   set -e; for v in 3.10; do rm -f 
/home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; ln -sfT 
python$v /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; 
pyinc=$(python$v-config --includes); pylib=$(python$v -c 'from distutils import 
sysconfig; print(sysconfig.get_python_lib())');  /usr/bin/make -C 
/home/pabs/subversion-1.14.2/BUILD LTFLAGS="--tag=CC --verbose" 
LTCXXFLAGS="--tag=CXX --verbose" check-swig-py PYTHON=python$v PYVER=$v 
CLEANUP=1 LC_ALL=C; ln -sfT python3.10 
/home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; done
   :1: DeprecationWarning: The distutils package is deprecated and 
slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
   :1: DeprecationWarning: The distutils.sysconfig module is 
deprecated, use sysconfig instead
   make[3]: Entering directory '/home/pabs/subversion-1.14.2'
   make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
   mkdir 
/home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/libsvn
   if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in 
/home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/libsvn_swig_py
 
/home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/../../../libsvn_*;
 do if [ -n "$DYLD_LIBRARY_PATH" ]; then 
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else LD_LIBRARY_PATH="$d/.libs"; 
fi; done; export LD_LIBRARY_PATH; fi; \
   cd /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; \
 python3.10 
/home/pabs/subversion-1.14.2/BUILD/../subversion/bindings/swig/python/tests/run_all.py
   make[3]: *** [Makefile:944: check-swig-py] Segmentation fault
   make[3]: Leaving directory '/home/pabs/subversion-1.14.2/BUILD'
   make[2]: *** [debian/rules:252: check-swig-py] Error 2
   make[2]: Leaving directory '/home/pabs/subversion-1.14.2'
   make[1]: *** [debian/rules:232: override_dh_auto_test-arch] Error 2
   make[1]: Leaving directory '/home/pabs/subversion-1.14.2'
   make: *** [debian/rules:197: binary] Error 2
   dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2
   debuild: fatal error at line 1182:
   dpkg-buildpackage -us -uc 

Bug#1022577: llvm-toolchain-15 fails with LLVM ERROR when using mesa

[Adrian Bunk]

Control: close 1022576 22.2.3-1

On Sat, Nov 05, 2022 at 10:22:18AM +, Simon McVittie wrote:
> Control: retitle -1 llvm-toolchain-15: Mesa on armel,armhf fails with LLVM 
> ERROR: Cannot select
> Control: tags -1 + patch fixed-upstream
> 
> On Mon, 24 Oct 2022 at 12:45:01 +0300, Adrian Bunk wrote:
> > https://buildd.debian.org/status/fetch.php?pkg=mutter=armhf=43.0-3=1666029584=0
> > 
> > ...
> > # Start of pipeline tests
> > LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, 
> > Constant:i32<2>
> >   0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 
> > 0xdf9afc, 0x131c538:1, Constant:i32<4>
> > 0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> > > 0xdf9afc, 0x12fb7e0, Constant:i32<64>
> >   0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23
> > 0x12e99c0: i32 = Register %23
> >   0x131a9a8: i32 = Constant<64>
> > 0x1319fd0: i32 = Constant<4>
> >   0x131a2e8: i32 = Constant<2>
> > In function: fs_variant_partial
> > ...
> > 
> > 
> > Some discussion is in
> > https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800
> 
> According to upstream bug 
> this is fixed by commit
> .

The reason why mesa hit this issue often has been fixed in mesa in [1],
and I am closing the bug in mesa.

With current mesa all visible issues are gone,
except perhaps mutter FTBFS.

mutter on armhf/armel went from 62 test failures to 1-2 test failures,
I have not investigated whether they are due to this issue or unrelated.

> smcv

cu
Adrian

[1] 
https://gitlab.freedesktop.org/mesa/mesa/-/commit/b6c47ce3651127fe87d96543b9b4b2b38438c10e

Processed: Re: Bug#1022577: llvm-toolchain-15 fails with LLVM ERROR when using mesa

[Debian Bug Tracking System]

Processing control commands:

> close 1022576 22.2.3-1
Bug #1022576 [src:mesa] mesa causes FTBFS and autopkgtest regressions on 32bit 
ARM due to LLVM ERROR
Marked as fixed in versions mesa/22.2.3-1.
Bug #1022576 [src:mesa] mesa causes FTBFS and autopkgtest regressions on 32bit 
ARM due to LLVM ERROR
Marked Bug as done

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

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

[Kevin J. McCarthy]

I've just released mutt 2.2.9, which I believe should fix this problem.

-Kevin


signature.asc
Description: PGP signature

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1022299 silver-platter
Bug #1022299 [src:silver-platter] silver-platter: FTBFS: AttributeError: module 
'breezy.errors' has no attribute 'NoColocatedBranchSupport'
Bug reassigned from package 'src:silver-platter' to 'silver-platter'.
No longer marked as found in versions silver-platter/0.4.5-1.
Ignoring request to alter fixed versions of bug #1022299 to the same values 
previously set
> forcemerge 1021796 1022299
Bug #1021796 {Done: Jelmer Vernooij } [silver-platter] 
silver-platter: workspace.py: ImportError: cannot import name 
'NoColocatedBranchSupport' from 'breezy.errors'
Bug #1021796 {Done: Jelmer Vernooij } [silver-platter] 
silver-platter: workspace.py: ImportError: cannot import name 
'NoColocatedBranchSupport' from 'breezy.errors'
Added tag(s) sid, ftbfs, and bookworm.
Bug #1022299 [silver-platter] silver-platter: FTBFS: AttributeError: module 
'breezy.errors' has no attribute 'NoColocatedBranchSupport'
Marked Bug as done
Added indication that 1022299 affects src:janitor
Marked as fixed in versions silver-platter/0.5.0-1.
Marked as found in versions silver-platter/0.4.5-1.
Merged 1021796 1022299
> affects 1021796 src:silver-platter
Bug #1021796 {Done: Jelmer Vernooij } [silver-platter] 
silver-platter: workspace.py: ImportError: cannot import name 
'NoColocatedBranchSupport' from 'breezy.errors'
Bug #1022299 {Done: Jelmer Vernooij } [silver-platter] 
silver-platter: FTBFS: AttributeError: module 'breezy.errors' has no attribute 
'NoColocatedBranchSupport'
Added indication that 1021796 affects src:silver-platter
Added indication that 1022299 affects src:silver-platter
> thanks
Stopping processing here.

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

Processed: block 1021798 with 1011665

[Debian Bug Tracking System]

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

> block 1021798 with 1011665
Bug #1021798 [src:crowdsec] crowdsec: FTBFS: FAIL: 
TestCreateMachineWithForwardedFor
1021798 was not blocked by any bugs.
1021798 was not blocking any bugs.
Added blocking bug(s) of 1021798: 1011665
> thanks
Stopping processing here.

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

Bug#1022504: xrstools: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Stefano Rivera]

I tried the obvious patch of moving setuptools imports above distutils,
but setuptools still wasn't having it:

> I: pybuild base:240: python3.11 setup.py clean 
> INFO:xrstools.setup:Use setuptools
> INFO:xrstools.setup:Use setuptools.setup
> error: Multiple top-level packages discovered in a flat-layout: ['fitcc', 
> 'superr', 'debian',
> 'OFFDIAG', 'sandbox', 'XRStools', 'nonregressions', 'useful_scripts'].
>
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
>
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
>
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
>
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 

Given the complexity of setup.py, clearly more work is needed, and I've spent
all the time that I'm going to, on it.

It doesn't help that upstream's bugtracker is on a GitLab without public
registration... :(

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1022516: marked as pending in python-preshed

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-preshed/-/commit/c034dae732748e01c4df605dc0f9cc6a2d7aab21


Adds support for setuptools >= 60 (Closes: #1022516)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022516

Processed: Bug#1022516 marked as pending in python-preshed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022516 [src:python-preshed] python-preshed: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) pending.

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

Processed: bug 1022504 is forwarded to https://github.com/PyAr/fades/pull/417

[Debian Bug Tracking System]

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

> forwarded 1022504 https://github.com/PyAr/fades/pull/417
Bug #1022504 [src:xrstools] xrstools: FTBFS: 
distutils.errors.DistutilsClassError: command class  must subclass Command
Set Bug forwarded-to-address to 'https://github.com/PyAr/fades/pull/417'.
> thanks
Stopping processing here.

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

Bug#1022491: deluge: diff for NMU version 2.0.3-3.2

[Stefano Rivera]

Control: tags 1022491 + patch
Control: tags 1022491 + pending

Dear maintainer,

I've prepared an NMU for deluge (versioned as 2.0.3-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru deluge-2.0.3/debian/changelog deluge-2.0.3/debian/changelog
--- deluge-2.0.3/debian/changelog	2021-07-15 13:57:18.0 +0200
+++ deluge-2.0.3/debian/changelog	2022-11-12 22:37:10.0 +0200
@@ -1,3 +1,10 @@
+deluge (2.0.3-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Support setuptools >= 60. (Closes: #1022491)
+
+ -- Stefano Rivera   Sat, 12 Nov 2022 22:37:10 +0200
+
 deluge (2.0.3-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru deluge-2.0.3/debian/patches/series deluge-2.0.3/debian/patches/series
--- deluge-2.0.3/debian/patches/series	2021-07-15 13:45:42.0 +0200
+++ deluge-2.0.3/debian/patches/series	2022-11-12 22:37:10.0 +0200
@@ -1,2 +1,3 @@
 new_release_check.patch
 0001-Fix-warning-related-to-gettext.patch
+setuptools-60.patch
diff -Nru deluge-2.0.3/debian/patches/setuptools-60.patch deluge-2.0.3/debian/patches/setuptools-60.patch
--- deluge-2.0.3/debian/patches/setuptools-60.patch	1970-01-01 02:00:00.0 +0200
+++ deluge-2.0.3/debian/patches/setuptools-60.patch	2022-11-12 22:37:10.0 +0200
@@ -0,0 +1,43 @@
+From: Stefano Rivera 
+Date: Sat, 12 Nov 2022 22:34:04 +0200
+Subject: Import setuptools before distutils
+
+setuptools 60 uses its own bundled version of distutils, by default. It
+injects this into sys.modules, at import time. So we need to make sure
+that it is imported, before anything else imports distutils, to ensure
+everything is using the same distutils version.
+
+This change in setuptools is to prepare for Python 3.12, which will drop
+distutils.
+
+Bug-Debian: https://bugs.debian.org/1022491
+Forwarded: https://github.com/deluge-torrent/deluge/pull/400
+---
+ setup.py | 9 +
+ 1 file changed, 5 insertions(+), 4 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 5cae466..fb49f10 100755
+--- a/setup.py
 b/setup.py
+@@ -15,15 +15,16 @@ import glob
+ import os
+ import platform
+ import sys
++from shutil import rmtree
++
++from setuptools import find_packages, setup
++from setuptools.command.test import test as _test
++
+ from distutils import cmd
+ from distutils.command.build import build as _build
+ from distutils.command.clean import clean as _clean
+ from distutils.command.install_data import install_data as _install_data
+ from distutils.spawn import find_executable
+-from shutil import rmtree
+-
+-from setuptools import find_packages, setup
+-from setuptools.command.test import test as _test
+ 
+ import msgfmt
+ from version import get_version

Processed: deluge: diff for NMU version 2.0.3-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1022491 + patch
Bug #1022491 [src:deluge] deluge: FTBFS: distutils.errors.DistutilsClassError: 
command class  must subclass Command
Added tag(s) patch.
> tags 1022491 + pending
Bug #1022491 [src:deluge] deluge: FTBFS: distutils.errors.DistutilsClassError: 
command class  must subclass Command
Added tag(s) pending.

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

Bug#1022483: marked as done (python-requirements-detector: FTBFS: TypeError: dist must be a Distribution instance)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 20:46:47 +
with message-id 
and subject line Bug#1022483: fixed in python-requirements-detector 0.6-4
has caused the Debian Bug report #1022483,
regarding python-requirements-detector: FTBFS: TypeError: dist must be a 
Distribution instance
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.)


-- 
1022483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-requirements-detector
Version: 0.6-3
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):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:2: 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 setup
> /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.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 38, in 
> setup(
>   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
>   File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in 
> __init__
> super().__init__(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:11: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-requirements-detector_0.6-3_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-requirements-detector
Source-Version: 0.6-4
Done: Stefano Rivera 

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

Bug#1022482: marked as done (python-mbed-host-tests: FTBFS: TypeError: dist must be a Distribution instance)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 20:46:20 +
with message-id 
and subject line Bug#1022482: fixed in python-mbed-host-tests 1.4.4-8
has caused the Debian Bug report #1022482,
regarding python-mbed-host-tests: FTBFS: TypeError: dist must be a Distribution 
instance
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.)


-- 
1022482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mbed-host-tests
Version: 1.4.4-6
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_clean
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.10
> D: pybuild pybuild:587: version: 5.20221008
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--clean', '-i', 
> 'python{version}', '-p', '3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=True, configure_only=False, 
> build_only=False, install_only=False, test_only=False, list_systems=False, 
> print_args=None, before_clean=None, clean_args=None, after_clean=None, 
> before_configure=None, configure_args=None, after_configure=None, 
> before_build=None, build_args=None, after_build=None, before_install=None, 
> install_args=None, after_install=None, before_test=None, test_args=None, 
> after_test=None, test_nose=False, test_nose2=False, test_pytest=False, 
> test_tox=False, test_custom=False, dir='/<>', 
> destdir='debian/tmp', ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', 
> ext_sub_pattern=None, ext_sub_repl=None, install_dir=None, 
> name='mbed-host-tests', system=None, versions=['3.10'], 
> interpreter=['python{version}'], disable=None, custom_tests=False)
> D: pybuild __init__:37: cannot initialize 'cmake' plugin: Missing command 
> 'cmake'
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild debhelper:141: skipping package: python-mbed-host-tests-doc
> D: pybuild debhelper:172: source=python-mbed-host-tests, binary 
> packages=['python3-mbed-host-tests']
> D: pybuild pybuild:122: Plugin custom: certainty 0
> D: pybuild pybuild:122: Plugin distutils: certainty 50
> D: pybuild pybuild:122: Plugin flit: certainty 0
> D: pybuild pybuild:122: Plugin pyproject: certainty 0
> D: pybuild pybuild:148: detected build system: distutils (certainty: 50%)
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.10_mbed-host-tests/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.10/dist-packages
> prefix=/usr
> 
> I: pybuild base:240: python3.10 setup.py clean 
> D: pybuild tools:232: invoking: python3.10 setup.py clean 
> /<>/setup.py:26: 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 setup
> /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.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'long_description_content_type'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_suite'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'entry_points'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 39, in 
> setup(name='mbed-host-tests',
>   File "/usr/lib/python3.10/distutils/core.py", line 

Bug#1012081: marked as done (jboss-classfilewriter: FTBFS with OpenJDK 17 due to test failures)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 20:39:49 +
with message-id 
and subject line Bug#1012081: fixed in jboss-classfilewriter 1.3.0-1
has caused the Debian Bug report #1012081,
regarding jboss-classfilewriter: FTBFS with OpenJDK 17 due to 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.)


-- 
1012081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jboss-classfilewriter
Version: 1.2.5-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17


jboss-classfilewriter fails to build with OpenJDK 17, almost all the tests fail:

  
  [INFO] ---
  [INFO]  T E S T S
  [INFO] ---
  [INFO] Running org.jboss.classfilewriter.test.simple.FieldTest
  [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.033 
s <<< FAILURE! - in org.jboss.classfilewriter.test.simple.FieldTest
  [ERROR] testCreatingField(org.jboss.classfilewriter.test.simple.FieldTest)  
Time elapsed: 0.008 s  <<< ERROR!
  java.lang.Error: java.lang.NoSuchFieldException: override
  at 
org.jboss.classfilewriter.test.simple.FieldTest.testCreatingField(FieldTest.java:45)
  Caused by: java.lang.NoSuchFieldException: override
  at 
org.jboss.classfilewriter.test.simple.FieldTest.testCreatingField(FieldTest.java:45)
  
  [INFO] Running org.jboss.classfilewriter.test.simple.MethodTest
  [ERROR] Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0 s 
<<< FAILURE! - in org.jboss.classfilewriter.test.simple.MethodTest
  [ERROR] testCreatingMethod(org.jboss.classfilewriter.test.simple.MethodTest)  
Time elapsed: 0 s  <<< ERROR!
  java.lang.NoClassDefFoundError: Could not initialize class 
org.jboss.classfilewriter.DefaultClassFactory
  at 
org.jboss.classfilewriter.test.simple.MethodTest.testCreatingMethod(MethodTest.java:53)
  
  [ERROR] testExceptionTypes(org.jboss.classfilewriter.test.simple.MethodTest)  
Time elapsed: 0 s  <<< ERROR!
  java.lang.NoClassDefFoundError: Could not initialize class 
org.jboss.classfilewriter.DefaultClassFactory
  at 
org.jboss.classfilewriter.test.simple.MethodTest.testExceptionTypes(MethodTest.java:79)
  
  [INFO] Running org.jboss.classfilewriter.test.simple.SimpleTest
  [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0 s 
<<< FAILURE! - in org.jboss.classfilewriter.test.simple.SimpleTest
  [ERROR] simpleTest(org.jboss.classfilewriter.test.simple.SimpleTest)  Time 
elapsed: 0 s  <<< ERROR!
  java.lang.NoClassDefFoundError: Could not initialize class 
org.jboss.classfilewriter.DefaultClassFactory
  at 
org.jboss.classfilewriter.test.simple.SimpleTest.simpleTest(SimpleTest.java:32)
  
  [ERROR] 
testAddingInterfaces(org.jboss.classfilewriter.test.simple.SimpleTest)  Time 
elapsed: 0 s  <<< ERROR!
  java.lang.NoClassDefFoundError: Could not initialize class 
org.jboss.classfilewriter.DefaultClassFactory
  at 
org.jboss.classfilewriter.test.simple.SimpleTest.testAddingInterfaces(SimpleTest.java:46)
  
  [ERROR] 
testDefaultInterface(org.jboss.classfilewriter.test.simple.SimpleTest)  Time 
elapsed: 0 s  <<< ERROR!
  java.lang.NoClassDefFoundError: Could not initialize class 
org.jboss.classfilewriter.DefaultClassFactory
  at 
org.jboss.classfilewriter.test.simple.SimpleTest.testDefaultInterface(SimpleTest.java:39)
  
  ...

  [INFO]
  [ERROR] Tests run: 177, Failures: 0, Errors: 171, Skipped: 0
  [INFO]
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

--- End Message ---
--- Begin Message ---
Source: jboss-classfilewriter
Source-Version: 1.3.0-1
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated jboss-classfilewriter 
package)

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

Bug#1023946: rdiff-backup FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: rdiff-backup
Version: 2.0.5-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rdiff-backup=2.0.5-3%2Bb3

...
src/_librsyncmodule.c: In function ‘PyInit__librsync’:
src/_librsyncmodule.c:543:36: error: lvalue required as left operand of 
assignment
  543 |   Py_TYPE(&_librsync_SigMakerType) = _Type;
  |^
src/_librsyncmodule.c:544:38: error: lvalue required as left operand of 
assignment
  544 |   Py_TYPE(&_librsync_DeltaMakerType) = _Type;
  |  ^
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

Processed: Bug#1022483 marked as pending in python-requirements-detector

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022483 [src:python-requirements-detector] python-requirements-detector: 
FTBFS: TypeError: dist must be a Distribution instance
Added tag(s) pending.

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

Bug#1022483: marked as pending in python-requirements-detector

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-requirements-detector/-/commit/982e81f1323e115b3facf20e0590ef13329da98d


Patch: Support setuptools >= 60. (Closes: #1022483)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022483

Processed: Bug#1022482 marked as pending in python-mbed-host-tests

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022482 [src:python-mbed-host-tests] python-mbed-host-tests: FTBFS: 
TypeError: dist must be a Distribution instance
Added tag(s) pending.

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

Bug#1022482: marked as pending in python-mbed-host-tests

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-mbed-host-tests/-/commit/8cf1205a2119eed6a720a01a13100a48112d875d


Patch: Support setuptools 60. (Closes: #1022482)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022482

Bug#1023940: Doesn't work: blank editor and shell panes

[julien . puydt]

Package: pyzo
Version: 4.11.2-1
Severity: grave

Launching pyzo displays the normal window, but the shell never comes up
and the editor pane never gets a prompt ; starting from a terminal
makes the following messages fly by continuously:

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?
Uncaught Python exception: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(int, int, int, int): argument 1 has unexpected type 'float'
  QRect(QPoint, QPoint): argument 1 has unexpected type 'float'
  QRect(QPoint, QSize): argument 1 has unexpected type 'float'
  QRect(QRect): argument 1 has unexpected type 'float'
  File "/usr/share/pyzo/pyzo/codeeditor/extensions/appearance.py", line
485, in paintEvent
QtCore.QRect(margin, top, self.viewport().width() - 2 * margin,
height),

QBackingStore::endPaint() called with active painter; did you forget to
destroy it or call QPainter::end() on it?


Cheers,

J.Puydt

Bug#1023803: marked as done (git-evtag: autopkgtest needs update for new version of git: transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 18:04:05 +
with message-id 
and subject line Bug#1023803: fixed in git-evtag 2016.1+git20221112-1
has caused the Debian Bug report #1023803,
regarding git-evtag: autopkgtest needs update for new version of git: transport 
'file' not allowed
to be marked as done.

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

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


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

Source: git-evtag
Version: 2016.1-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
git-evtag  from testing2016.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

Currently this regression is blocking the migration of git to testing 
[1]. Of course, git shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in git 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 git 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=git

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-evtag/28079227/log.gz

Running test: git-evtag/test-basic.test
+ set -o pipefail
+ echo 1..6
1..6
++ dirname /usr/libexec/git-evtag/installed-tests/test-basic.sh
+ . /usr/libexec/git-evtag/installed-tests/libtest.sh
+++ dirname /usr/libexec/git-evtag/installed-tests/test-basic.sh
++ SRCDIR=/usr/libexec/git-evtag/installed-tests
+++ pwd
++ test_tmpdir=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
++ export G_DEBUG=fatal-warnings
++ G_DEBUG=fatal-warnings
++ export TEST_GPG_KEYID_1=472CDAFA
++ TEST_GPG_KEYID_1=472CDAFA
++ export TEST_GPG_KEYID_2=CA950D41
++ TEST_GPG_KEYID_2=CA950D41
++ export TEST_GPG_KEYID_3=DF444D67
++ TEST_GPG_KEYID_3=DF444D67
++ export 'GIT_AUTHOR_NAME=Colin Walters'
++ GIT_AUTHOR_NAME='Colin Walters'
++ export GIT_AUTHOR_EMAIL=walt...@verbum.org
++ GIT_AUTHOR_EMAIL=walt...@verbum.org
++ export 'GIT_COMMITTER_NAME=Colin Walters'
++ GIT_COMMITTER_NAME='Colin Walters'
++ export GIT_COMMITTER_EMAIL=walt...@verbum.org
++ GIT_COMMITTER_EMAIL=walt...@verbum.org
++ cp -a /usr/libexec/git-evtag/installed-tests/gpghome 
/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1

++ chmod 0700 /tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ export GNUPGHOME=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ GNUPGHOME=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/gpghome
++ test -n ''
+ setup_test_repository
++ pwd
+ oldpwd=/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
+ cd /tmp/test-tmp-git-evtag_test-basic.test-2FD4U1
+ mkdir coolproject
+ cd coolproject
+ git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/test-tmp-git-evtag_test-basic.test-2FD4U1/coolproject/.git/

+ gitcommit_reset_time
+ 

Bug#1022481: marked as done (pylint-celery: FTBFS: TypeError: dist must be a Distribution instance)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 17:06:12 +
with message-id 
and subject line Bug#1022481: fixed in pylint-celery 0.3-7
has caused the Debian Bug report #1022481,
regarding pylint-celery: FTBFS: TypeError: dist must be a Distribution instance
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.)


-- 
1022481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint-celery
Version: 0.3-6
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 clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:2: 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 setup
> /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.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'zip_safe'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 12, in 
> setup( name='pylint-celery',
>   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
>   File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in 
> __init__
> super().__init__(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/pylint-celery_0.3-6_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: pylint-celery
Source-Version: 0.3-7
Done: Stefano Rivera 

We believe that the bug you reported is fixed in the latest version of
pylint-celery, 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.
Stefano Rivera  (supplier 

Processed: Bug#1022481 marked as pending in pylint-celery

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022481 [src:pylint-celery] pylint-celery: FTBFS: TypeError: dist must be 
a Distribution instance
Added tag(s) pending.

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

Bug#1022481: marked as pending in pylint-celery

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1022481 in pylint-celery 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/pylint-celery/-/commit/bddfc76d2b55084d1dbbcf69553967592720340c


Patch: Support setuptools >= 60. (Closes: #1022481)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022481

Bug#1022466: marked as done (kytos-utils: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 16:36:49 +
with message-id 
and subject line Bug#1022466: fixed in kytos-utils 2019.2-4
has caused the Debian Bug report #1022466,
regarding kytos-utils: FTBFS: distutils.errors.DistutilsClassError: command 
class  must subclass Command
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.)


-- 
1022466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kytos-utils
Version: 2019.2-3
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 clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:12: 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.clean import clean  # pylint: disable=E0401,E0611
> /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.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 173, in 
> setup(name='kytos-utils',
>   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  '__main__.Cleaner'> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:5: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/kytos-utils_2019.2-3_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: kytos-utils
Source-Version: 2019.2-4
Done: Stefano Rivera 

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

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

Bug#1023316: marked as done (9base: re-adds /bin/rc to /etc/shells on upgrade)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 16:34:07 +
with message-id 
and subject line Bug#1023316: fixed in 9base 1:6-13
has caused the Debian Bug report #1023316,
regarding 9base: re-adds /bin/rc 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.)


-- 
1023316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 9base
Version: 1:6-12
Tags: patch
Severity: serious
Justification: Debian policy 10.7.3

If I remove /bin/rc from /etc/shells and then upgrade or reinstall
9base, it will re-add itself to /etc/shells. Such behaviour violates
Debian policy section 10.7.3. I propose moving to dpkg triggers and
update-shells to fix this issue and attach a patch for your convenience.

Helmut
diff --minimal -Nru 9base-6/debian/changelog 9base-6/debian/changelog
--- 9base-6/debian/changelog2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/changelog2022-11-02 09:45:01.0 +0100
@@ -1,3 +1,9 @@
+9base (1:6-13) UNRELEASED; urgency=medium
+
+  * Update /etc/shells via dpkg triggers. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 09:45:01 +0100
+
 9base (1:6-12) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru 9base-6/debian/control 9base-6/debian/control
--- 9base-6/debian/control  2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/control  2022-11-02 09:45:01.0 +0100
@@ -11,7 +11,7 @@
 
 Package: 9base
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, debianutils (>= 5.3-1~)
 Description: Plan 9 userland tools
  9base is a port of following original Plan 9 userland tools to Unix:
  ascii, awk, basename, bc, cal, cat, cleanname, cmp, date, dc, dd, diff, du,
diff --minimal -Nru 9base-6/debian/postinst 9base-6/debian/postinst
--- 9base-6/debian/postinst 2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/postinst 2022-11-02 09:45:01.0 +0100
@@ -5,10 +5,6 @@
 # and so we can maintain compatibility with rc scripts expecting /bin/rc
 update-alternatives --install /bin/rc rc /usr/lib/plan9/bin/rc 20
 
-# allow use of 9base' rc as a login shell:
-add-shell /bin/rc
-add-shell /usr/lib/plan9/bin/rc
-
 #DEBHELPER#
 
 exit 0
diff --minimal -Nru 9base-6/debian/postrm 9base-6/debian/postrm
--- 9base-6/debian/postrm   2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/postrm   1970-01-01 01:00:00.0 +0100
@@ -1,9 +0,0 @@
-#!/bin/sh
-set -e
-
-if [ "$1" = "remove" ]; then
-remove-shell /bin/rc
-remove-shell /usr/lib/plan9/bin/rc
-fi
-
-#DEBHELPER#
diff --minimal -Nru 9base-6/debian/rules 9base-6/debian/rules
--- 9base-6/debian/rules2022-03-17 21:15:01.0 +0100
+++ 9base-6/debian/rules2022-11-02 09:45:01.0 +0100
@@ -52,6 +52,8 @@
mv $$MANPAGE $${MANPAGE}$(MANEXT); \
done
 
+   install -D -m644 debian/shells 
$(PKGDIR)$(DATADIR)/debianutils/shells.d/plan9
+
 override_dh_fixperms:
dh_fixperms
 
diff --minimal -Nru 9base-6/debian/shells 9base-6/debian/shells
--- 9base-6/debian/shells   1970-01-01 01:00:00.0 +0100
+++ 9base-6/debian/shells   2022-11-02 09:45:01.0 +0100
@@ -0,0 +1,2 @@
+/bin/rc
+/usr/lib/plan9/bin/rc
--- End Message ---
--- Begin Message ---
Source: 9base
Source-Version: 1:6-13
Done: Bo YU 

We believe that the bug you reported is fixed in the latest version of
9base, 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.
Bo YU  (supplier of updated 9base 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 21:48:16 +0800
Source: 9base
Architecture: source
Version: 1:6-13
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bo YU 
Closes: 1023316
Changes:
 9base (1:6-13) unstable; urgency=medium
 .
   * QA upload.
   * Update /etc/shells via dpkg triggers. Thanks Helmut Grohne
 (closes: #1023316)
Checksums-Sha1:
 3507e141513ca8900b657ec1e15ff6b79cf9afb3 1802 9base_6-13.dsc
 

Processed: tagging 1018446, tagging 1022464

[Debian Bug Tracking System]

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

> tags 1018446 + pending
Bug #1018446 [src:pykafka] pykafka: build-depends on python3-nose or uses it 
for autopkgtest
Added tag(s) pending.
> tags 1022464 + pending
Bug #1022464 [src:pykafka] pykafka: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 1022470, tagging 1018561

[Debian Bug Tracking System]

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

> tags 1022470 + pending
Bug #1022470 [src:python-pyeclib] python-pyeclib: FTBFS: 
distutils.errors.DistutilsClassError: command class  
must subclass Command
Added tag(s) pending.
> tags 1018561 + pending
Bug #1018561 [src:python-pyeclib] python-pyeclib: build-depends on python3-nose 
or uses it for autopkgtest
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: python-av: diff for NMU version 9.2.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1022472 + patch
Bug #1022472 [src:python-av] python-av: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) patch.
> tags 1022472 + pending
Bug #1022472 [src:python-av] python-av: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) pending.

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

Bug#1022472: python-av: diff for NMU version 9.2.0-3.1

[Stefano Rivera]

Control: tags 1022472 + patch
Control: tags 1022472 + pending

Dear maintainer,

I've prepared an NMU for python-av (versioned as 9.2.0-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Also pushed to Salsa as the "nmu" branch:
https://salsa.debian.org/debian/python-av/-/compare/debian%2Fmaster...nmu

Regards,

SR
diff -Nru python-av-9.2.0/debian/changelog python-av-9.2.0/debian/changelog
--- python-av-9.2.0/debian/changelog	2022-08-16 16:13:13.0 +0200
+++ python-av-9.2.0/debian/changelog	2022-11-12 18:11:54.0 +0200
@@ -1,3 +1,10 @@
+python-av (9.2.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Support setuptools >= 60. (Closes: #1022472)
+
+ -- Stefano Rivera   Sat, 12 Nov 2022 18:11:54 +0200
+
 python-av (9.2.0-3) unstable; urgency=medium
 
   * add patch cherry-picked upstream
diff -Nru python-av-9.2.0/debian/patches/series python-av-9.2.0/debian/patches/series
--- python-av-9.2.0/debian/patches/series	2022-08-16 16:10:55.0 +0200
+++ python-av-9.2.0/debian/patches/series	2022-11-12 18:11:54.0 +0200
@@ -1,2 +1,3 @@
 020220311~1870465.patch
 020220621~972f3ca.patch
+setuptools-60.patch
diff -Nru python-av-9.2.0/debian/patches/setuptools-60.patch python-av-9.2.0/debian/patches/setuptools-60.patch
--- python-av-9.2.0/debian/patches/setuptools-60.patch	1970-01-01 02:00:00.0 +0200
+++ python-av-9.2.0/debian/patches/setuptools-60.patch	2022-11-12 18:11:54.0 +0200
@@ -0,0 +1,34 @@
+From: Stefano Rivera 
+Date: Sat, 12 Nov 2022 18:01:50 +0200
+Subject: Import setuptools before distutils
+
+setuptools 60 uses its own bundled version of distutils, by default. It
+injects this into sys.modules, at import time. So we need to make sure
+that it is imported, before anything else imports distutils, to ensure
+everything is using the same distutils version.
+
+This change in setuptools is to prepare for Python 3.12, which will drop
+distutils.
+
+Forwarded: https://github.com/PyAV-Org/PyAV/pull/1049
+Bug-Debian: https://bugs.debian.org/1022472
+---
+ setup.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index ec234f4..2d9da42 100644
+--- a/setup.py
 b/setup.py
+@@ -7,9 +7,10 @@ import shlex
+ import subprocess
+ import sys
+ 
++from setuptools import Extension, find_packages, setup
++
+ from Cython.Build import cythonize
+ from Cython.Compiler.AutoDocTransforms import EmbedSignature
+-from setuptools import Extension, find_packages, setup
+ 
+ 
+ FFMPEG_LIBRARIES = [

Bug#1012636: isync: license conflict with libsasl2

[Bastian Germann]

I see that in git there is now LicenseRef-isync-GPL-exception applied to mbsync.

Processed: raise severity (Policy violation)

[Debian Bug Tracking System]

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

> severity 1012636 serious
Bug #1012636 [isync] isync: license conflict with libsasl2
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#1013223: marked as done (bird2: FTBFS on arm64: make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 10:25:55 -0500
with message-id <3a2e843a-7b52-4610-c418-bb6f23120...@nic.cz>
and subject line Re: bird2: FTBFS on arm64
has caused the Debian Bug report #1013223,
regarding bird2: FTBFS on arm64: make[1]: *** [Makefile:180: 
obj/lib/bitmap_test.ok] Error 1
to be marked as done.

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

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


-- 
1013223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bird2
Version: 2.0.9-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/fetch.php?pkg=bird2=arm64=2.0.9-3=1649868353=0


obj/lib/bitmap_test: t_hmap_set_clear_fill 5.023173111s  [FAIL] 
obj/lib/bitmap_test 6.241085926s [FAIL] 
make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1
make[1]: *** Waiting for unfinished jobs
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ 

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

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 14:55:50 +
with message-id 
and subject line Bug#1023900: fixed in python-keyutils 0.6-3
has caused the Debian Bug report #1023900,
regarding python-keyutils 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.)


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

https://buildd.debian.org/status/logs.php?pkg=python-keyutils=0.6-2%2Bb7

...
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 keyutils/_keyutils.c -o 
build/temp.linux-x86_64-cpython-311/keyutils/_keyutils.o
keyutils/_keyutils.c: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 
--- End Message ---
--- Begin Message ---
Source: python-keyutils
Source-Version: 0.6-3
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
python-keyutils, 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.
Gianfranco Costamagna  (supplier of updated 
python-keyutils 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: Sat, 12 Nov 2022 14:39:02 +0100
Source: python-keyutils
Built-For-Profiles: noudeb
Architecture: source
Version: 0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Gianfranco Costamagna 
Changed-By: Gianfranco Costamagna 
Closes: 1023900
Changes:
 python-keyutils (0.6-3) unstable; urgency=medium
 .
   * Bump std-version to 4.6.0
   * Bump compat level to 13
   * Run cython3 during build, fixing FTBFS with Python3.11 (Closes: #1023900)
   * Make sure c files are regenerated by deleting _keyutils.c during clean.
Checksums-Sha1:
 66bf2e00d2d747e2af47e05f2a6de17987d42cb8 1900 python-keyutils_0.6-3.dsc
 d6b6fb8447be7740fde8f90bdafc2b512fa38196 2268 
python-keyutils_0.6-3.debian.tar.xz
 ee37b163826ae6e82d43c5d7602896bb9eb3dbc6 8884 
python-keyutils_0.6-3_source.buildinfo
Checksums-Sha256:
 b50d94e801870d345816596e6e4c2f1d2a06b7e31156850c668f596909d74ebf 1900 
python-keyutils_0.6-3.dsc
 338cee1cdeedd5716393e7c8f260e2c0d9ffb2ebe802618a997d345298f77759 2268 
python-keyutils_0.6-3.debian.tar.xz
 6a3a840828a00cfbc87e9aa5ae332e9f6e0242f7aeee29b7833437cb19f96565 8884 
python-keyutils_0.6-3_source.buildinfo
Files:
 ac46ee5bc7bbdfb0a31b696b96313364 1900 python optional python-keyutils_0.6-3.dsc
 0f072b138f3a6c60aa892b1732e10b16 2268 python optional 
python-keyutils_0.6-3.debian.tar.xz
 6494670739b4e0bd74ede3823fef03c6 8884 python optional 
python-keyutils_0.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmNvpDUACgkQ808JdE6f
XdnmNQ//RqTnlIDPmHP/ts2+qzZX8Kxo1lfrYW4EtXneSVmUBcunCAHZijwo2U4E
eUXHmJcknDdGAgchMbrO00/B+Wp0REasYMLZ3riUuyF2lsLqmWjjJ9JwOvEcb0B7
dz37PtLIbKS3UW0pm0ETm+yzLIAnJuqVA5RqnYTn+zhIn+B0ZmYEBxYx92cDRxgg
X4WdKx3hK6G/11cXoszFz+X2yyzPEMS+z7SLo+7cVfBWo37Pqfc3IkKfwtYYP6y5
tAOfE1t5zPEFsIHScDbrShxG0RfXMWnd2OTc43mG+qv7tDrIkTkQcrEKPDgA20px
OTf8WP8cKCDkFxJpABVb5SjsUQtmxmpffTSExvjTCJTjChY1Wiikt83VMq5mTuKP
LzhwE5NnsYeF7XIZJFaf+J5NLM1jhlO4cvgm1N3d2/AYtCC84r+i9fWdqZJv5OLg
k9gQnERYO0Jif+mGTk6F35Z0l7FRh3WJz5okefnKswr/dKyep41H7JsbL+dCPSoI
h8nzKs+dU4Oe6qBGPiy3nxck/T4Ta2/D56x7dKs38Y9e9QPn3TCp85gYu2uHcpJe
IFhRlfV1vmokSQoJSPQcbWVU3QIolGKgZTV8141W1nqYGRyUFVd33Mg2m/ZTZBVH
F68tAqRspC/44dNVTHPi+JiLGq4NgylydABoco6h4MtndBNMEk4=
=OT3u
-END PGP SIGNATURE End Message ---

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

[Andreas Metzler]

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.

Since upstream BTS is offline for the weekend I cannot check whether
this is a known issue.

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#1022468: marked as done (python-http-parser: 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 Sat, 12 Nov 2022 13:54:03 +
with message-id 
and subject line Bug#1022468: fixed in python-http-parser 0.9.0-3
has caused the Debian Bug report #1022468,
regarding python-http-parser: 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.)


-- 
1022468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-http-parser
Version: 0.9.0-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.errors import CCompilerError, DistutilsExecError, \
> /<>/setup.py:12: 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
>   from imp import load_source
> /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.")
> 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.errors import CCompilerError, DistutilsExecError, \
> /<>/setup.py:12: 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
>   from imp import load_source
> /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.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/util.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/_socketio.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/pyparser.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/http.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> copying http_parser/reader.py -> 
> /<>/.pybuild/cpython3_3.10_http-parser/build/http_parser
> running build_ext
> Traceback (most recent call last):
>   File "/<>/setup.py", line 172, in 
> run_setup(not IS_PYPY)
>   File "/<>/setup.py", line 155, in run_setup
> setup(
>   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 
> 185, in setup
> return run_commands(dist)

Bug#1022468: marked as pending in python-http-parser

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-http-parser/-/commit/4daabe09613e8b0b25f2aaf02118e7f113df


Patch: Support building with setuptools 60. (Closes: #1022468)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022468

Processed: Bug#1022468 marked as pending in python-http-parser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022468 [src:python-http-parser] python-http-parser: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) pending.

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

Bug#1023923: veyon-plugins: license conflict with libsasl2

[Bastian Germann]

Package: veyon-plugins
Version: 4.7.4+repack1-1
Severity: serious

Hi,

libkldap-light.so depends on libsasl2-2, which is licensed under CMU's BSD-4-clause license and covered by the RSA-MD 
and OpenSSL licenses. All of them have an advertisement clause in place, which is known to be incompatible with the GPL. 
There are several possible solutions to this problem:


1) Build without the plugin.

2) Support my request at #996892.

3) Ask upstream to change this plugin's license or add a license exception for libsasl2-2, similar to the one that was 
required by Debian for OpenSSL for a long time.


Thanks for your consideration,
Bastian

Processed: block 1023921 with 1023910

[Debian Bug Tracking System]

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

> block 1023921 with 1023910
Bug #1023921 [pykafka] pykafka: diff for NMU version 2.7.0-2.1
1023921 was not blocked by any bugs.
1023921 was not blocking any bugs.
Added blocking bug(s) of 1023921: 1023910
> thanks
Stopping processing here.

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

Processed: python-snappy: diff for NMU version 0.5.3-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1023910 + patch
Bug #1023910 [src:python-snappy] python-snappy FTBFS with Python 3.11 as 
supported version
Added tag(s) patch.
> tags 1023910 + pending
Bug #1023910 [src:python-snappy] python-snappy FTBFS with Python 3.11 as 
supported version
Added tag(s) pending.

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

Bug#1023910: python-snappy: diff for NMU version 0.5.3-1.2

[Stefano Rivera]

Control: tags 1023910 + patch
Control: tags 1023910 + pending

Dear maintainer,

I've prepared an NMU for python-snappy (versioned as 0.5.3-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru python-snappy-0.5.3/debian/changelog python-snappy-0.5.3/debian/changelog
--- python-snappy-0.5.3/debian/changelog	2019-12-20 21:36:43.0 +0200
+++ python-snappy-0.5.3/debian/changelog	2022-11-12 14:40:44.0 +0200
@@ -1,3 +1,10 @@
+python-snappy (0.5.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for Python 3.11. (Closes: #1023910)
+
+ -- Stefano Rivera   Sat, 12 Nov 2022 14:40:44 +0200
+
 python-snappy (0.5.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-snappy-0.5.3/debian/patches/python3.11 python-snappy-0.5.3/debian/patches/python3.11
--- python-snappy-0.5.3/debian/patches/python3.11	1970-01-01 02:00:00.0 +0200
+++ python-snappy-0.5.3/debian/patches/python3.11	2022-11-12 14:40:39.0 +0200
@@ -0,0 +1,429 @@
+Description: Port to Python 3.11: use Py_SET_SIZE()
+ .
+ On Python 3.11, "Py_SIZE(str) = actual_size;" fails with a compiler
+ error. Since Python 3.9, Py_SET_SIZE() must be used instead:
+ .
+ * https://docs.python.org/dev/whatsnew/3.11.html#c-api-changes
+ * https://docs.python.org/dev/c-api/structures.html#c.Py_SIZE
+ .
+ Add a copy of the pythoncapi_compat.h header file to get
+ Py_SET_SIZE() on Python 3.8 and older:
+ https://github.com/pythoncapi/pythoncapi_compat
+Author: Victor Stinner 
+Origin: upstream: https://github.com/andrix/python-snappy/commit/5575c80fbbbf3c8b257dfe1c9b9bb3e69ac909a8
+Bug-Debian: https://bugs.debian.org/1023910
+--- /dev/null
 b/snappy/pythoncapi_compat.h
+@@ -0,0 +1,393 @@
++// Header file providing new functions of the Python C API to old Python
++// versions.
++//
++// File distributed under the MIT license.
++// Copyright Contributors to the pythoncapi_compat project.
++//
++// Homepage:
++// https://github.com/pythoncapi/pythoncapi_compat
++//
++// Latest version:
++// https://raw.githubusercontent.com/pythoncapi/pythoncapi_compat/master/pythoncapi_compat.h
++//
++// SPDX-License-Identifier: MIT
++
++#ifndef PYTHONCAPI_COMPAT
++#define PYTHONCAPI_COMPAT
++
++#ifdef __cplusplus
++extern "C" {
++#endif
++
++#include 
++#include "frameobject.h"  // PyFrameObject, PyFrame_GetBack()
++
++
++// Compatibility with Visual Studio 2013 and older which don't support
++// the inline keyword in C (only in C++): use __inline instead.
++#if (defined(_MSC_VER) && _MSC_VER < 1900 \
++ && !defined(__cplusplus) && !defined(inline))
++#  define inline __inline
++#  define PYTHONCAPI_COMPAT_MSC_INLINE
++   // These two macros are undefined at the end of this file
++#endif
++
++
++// Cast argument to PyObject* type.
++#ifndef _PyObject_CAST
++#  define _PyObject_CAST(op) ((PyObject*)(op))
++#endif
++#ifndef _PyObject_CAST_CONST
++#  define _PyObject_CAST_CONST(op) ((const PyObject*)(op))
++#endif
++
++
++// bpo-42262 added Py_NewRef() to Python 3.10.0a3
++#if PY_VERSION_HEX < 0x030A00A3 && !defined(Py_NewRef)
++static inline PyObject* _Py_NewRef(PyObject *obj)
++{
++Py_INCREF(obj);
++return obj;
++}
++#define Py_NewRef(obj) _Py_NewRef(_PyObject_CAST(obj))
++#endif
++
++
++// bpo-42262 added Py_XNewRef() to Python 3.10.0a3
++#if PY_VERSION_HEX < 0x030A00A3 && !defined(Py_XNewRef)
++static inline PyObject* _Py_XNewRef(PyObject *obj)
++{
++Py_XINCREF(obj);
++return obj;
++}
++#define Py_XNewRef(obj) _Py_XNewRef(_PyObject_CAST(obj))
++#endif
++
++
++// See https://bugs.python.org/issue42522
++#if !defined(_Py_StealRef)
++static inline PyObject* __Py_StealRef(PyObject *obj)
++{
++Py_DECREF(obj);
++return obj;
++}
++#define _Py_StealRef(obj) __Py_StealRef(_PyObject_CAST(obj))
++#endif
++
++
++// See https://bugs.python.org/issue42522
++#if !defined(_Py_XStealRef)
++static inline PyObject* __Py_XStealRef(PyObject *obj)
++{
++Py_XDECREF(obj);
++return obj;
++}
++#define _Py_XStealRef(obj) __Py_XStealRef(_PyObject_CAST(obj))
++#endif
++
++
++// bpo-39573 added Py_SET_REFCNT() to Python 3.9.0a4
++#if PY_VERSION_HEX < 0x030900A4 && !defined(Py_SET_REFCNT)
++static inline void _Py_SET_REFCNT(PyObject *ob, Py_ssize_t refcnt)
++{
++ob->ob_refcnt = refcnt;
++}
++#define Py_SET_REFCNT(ob, refcnt) _Py_SET_REFCNT(_PyObject_CAST(ob), refcnt)
++#endif
++
++
++// Py_SETREF() and Py_XSETREF() were added to Python 3.5.2.
++// It is excluded from the limited C API.
++#if (PY_VERSION_HEX < 0x03050200 && !defined(Py_SETREF)) && !defined(Py_LIMITED_API)
++#define Py_SETREF(op, op2)  \
++do {\
++PyObject *_py_tmp = _PyObject_CAST(op); \
++(op) = (op2);   \
++Py_DECREF(_py_tmp); \
++} while (0)
++
++#define Py_XSETREF(op, op2) \
++do {   

Bug#1023918: ziproxy: license conflict with libsasl2

[Bastian Germann]

Package: ziproxy
Version: 3.3.2-5
Severity: serious

Hi,

ziproxy depends on libsasl2-2, which is licensed under CMU's BSD-4-clause 
license and covered by the RSA-MD and OpenSSL
licenses. All of them have an advertisement clause in place, which is known to 
be incompatible with ziproxy's GPL.
There are several possible solutions to this problem:

1) Build without SASL support.

2) Support my request at #996892.

3) Ask upstream to add a license exception for libsasl2-2, similar to the one 
that was required by Debian for OpenSSL
for a long time.

Thanks for your consideration,
Bastian

Processed: bug 1023910 is forwarded to https://github.com/andrix/python-snappy/pull/114

[Debian Bug Tracking System]

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

> forwarded 1023910 https://github.com/andrix/python-snappy/pull/114
Bug #1023910 [src:python-snappy] python-snappy FTBFS with Python 3.11 as 
supported version
Set Bug forwarded-to-address to 
'https://github.com/andrix/python-snappy/pull/114'.
> thanks
Stopping processing here.

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

Bug#1023917: cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no]

[Andreas Metzler]

Package: cpm
Version: 0.32-1.4
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

cpm FTBFS against libgpgme-dev without gpgme-config. Find attached a
minimal patch using gnupg standard autoconf macros. You could also
simply use pkgconf.

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'
Description: Use standard macro to detect gpgme
Author: Andreas Metzler 
Origin: vendor
Forwarded: no
Last-Update: 2022-11-12

--- a/configure.in
+++ b/configure.in
@@ -351,10 +351,16 @@
 PKG_CHECK_MODULES([LIBXML], [libxml-2.0])
 
 LIBXML_XMLLINT="$exec_prefix/bin/xmllint"
 AC_SUBST(LIBXML_XMLLINT)
 
+dnl AM_PATH_GPGME requires AM_PATH_GPG_ERROR for fallback to gpgrt-config
+AM_PATH_GPG_ERROR()
+AM_PATH_GPGME([1.0.0],
+	  AC_MSG_RESULT([found GPGME]),
+	  AC_MSG_ERROR([GPGME must be version 1.0 or higher.]))
+
 AC_PATH_PROG([GPGME_CONFIG], [gpgme-config])
 if test -z "$ac_cv_path_GPGME_CONFIG"; then
   AC_MSG_ERROR([Could not find gpgme anywhere.])
 fi
 

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

[программист некто]

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.

Bug#1022151: marked as done (python3-pip: Trying to install a package gave me some errors I believe are from pip.)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 13:58:18 +0200
with message-id <20221112115818.wc7yfhqrxhhcj...@haydn.kardiogramm.net>
and subject line Re: Bug#1022151: python3-pip: Trying to install a package gave 
me some errors I believe are from pip.
has caused the Debian Bug report #1022151,
regarding python3-pip: Trying to install a package gave me some errors I 
believe are from pip.
to be marked as done.

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

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


-- 
1022151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pip
Version: 20.3.4-4+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: fabquennevi...@gmail.com

Dear Maintainer,

I was trying to install spotipy with:

pip3 install spotipy

and I got a wall of errors:

--- Logging error ---
Traceback (most recent call last):
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 177, in emit
self.console.print(renderable, overflow="ignore", crop=False, style=style)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1673, in print
extend(render(renderable, render_options))
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1305, in render
for render_output in iter_render:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 134, in __rich_console__
for line in lines:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/segment.py", 
line 249, in split_lines
for segment in segments:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1283, in render
renderable = rich_cast(renderable)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/protocol.py",
 line 36, in rich_cast
renderable = cast_method()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 130, in __rich__
pip_cmd = get_best_invocation_for_this_pip()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/entrypoints.py",
 line 58, in get_best_invocation_for_this_pip
if found_executable and os.path.samefile(
  File "/usr/lib/python3.9/genericpath.py", line 101, in samefile
s2 = os.stat(f2)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/pip3.9'
Call stack:
  File "/home/fabrice/.local/bin/pip3", line 8, in 
sys.exit(main())
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/main.py", 
line 70, in main
return command.main(cmd_args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 101, in main
return self._main(args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 223, in _main
self.handle_pip_version_check(options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/req_command.py",
 line 190, in handle_pip_version_check
pip_self_version_check(session, options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 236, in pip_self_version_check
logger.warning("[present-rich] %s", upgrade_prompt)
  File "/usr/lib/python3.9/logging/__init__.py", line 1454, in warning
self._log(WARNING, msg, args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log
self.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle
self.callHandlers(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1657, in callHandlers
hdlr.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 948, in handle
self.emit(record)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 179, in emit
self.handleError(record)
Message: '[present-rich] %s'
Arguments: (UpgradePrompt(old='22.2.2', new='22.3'),)

This seamed like a pip error so I tryed 

pip3 install pip-install-test

And got a similar wall of errors:

Defaulting to user installation because normal site-packages is not writeable
Collecting pip-install-test
  Downloading pip_install_test-0.5-py3-none-any.whl (1.7 kB)
Installing collected packages: pip-install-test
Successfully installed pip-install-test-0.5
--- Logging error ---
Traceback (most recent call last):
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 

Processed: Re: Bug#995477: cppman: error: no such table: cppreference.com_keywords

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #995477 [cppman] cppman: error: no such table: cppreference.com_keywords
Severity set to 'grave' from 'important'

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

Bug#1023303: marked as done (jhead 1:3.06.0.1-3 deletes EXIF data)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 11:34:17 +
with message-id 
and subject line Bug#1023303: fixed in jhead 1:3.06.0.1-4
has caused the Debian Bug report #1023303,
regarding jhead 1:3.06.0.1-3 deletes EXIF data
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.)


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

Package: jhead
Version: 1:3.06.0.1-3
Severity: grave


jhead version 1:3.06.0.1-3 deletes EXIF data when rotating images:

$ exiftool IMG_20221102_000230.jpg | wc -l

77



$ jhead -autorot IMG_20221102_000230.jpg



Nonfatal Error : 'IMG_20221102_000230.jpg' Command has invalid characters.



$ exiftool IMG_20221102_000230.jpg | wc -l

23





jhead 1:3.06.0.1-2 is not affected.
--- End Message ---
--- Begin Message ---
Source: jhead
Source-Version: 1:3.06.0.1-4
Done: Joachim Reichel 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Oct 2022 20:48:16 +0200
Source: jhead
Architecture: source
Version: 1:3.06.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Joachim Reichel 
Changed-By: Joachim Reichel 
Closes: 1023303
Changes:
 jhead (1:3.06.0.1-4) unstable; urgency=medium
 .
   * Update patch fix_cve_2022_41751 to handle images where the thumbnail
 needs autorotation, too (Closes: 1023303).
   * Add graphicsmagick-imagemagick-compat (mogrify) and (re-)add
 libjpeg-turbo-progs (jpegran) to Depends: to avoid information loss in
 case of errors due to missing executables. Remove Suggests: imagemagick.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
Checksums-Sha1:
 5cbfd7010c07cfbae89ded6f9a40c398b3b08e35 1827 jhead_3.06.0.1-4.dsc
 7972aeae1684e4e18c7ba950fdd799ebb7ab5784 8312 jhead_3.06.0.1-4.debian.tar.xz
 8872292a12e11811595b29cbdea544be303e462b 6190 jhead_3.06.0.1-4_amd64.buildinfo
Checksums-Sha256:
 21c53b869f2b29cefdb54bf727cbb37e986cb19294dd51d656f29aa1c05d922d 1827 
jhead_3.06.0.1-4.dsc
 744ca309af6acebe160b8c31ca99934fa69a33c98cd0b2aa6f15531e75d182c7 8312 
jhead_3.06.0.1-4.debian.tar.xz
 dcc019e7d2010cb7c873f68f53f69b82fb84e1505fc969c3e2f2c6cbfedf20e7 6190 
jhead_3.06.0.1-4_amd64.buildinfo
Files:
 242c4c82be6f36762333e1c01f56e250 1827 graphics optional jhead_3.06.0.1-4.dsc
 9c9542e1ea2d110be26480f6b4608ee4 8312 graphics optional 
jhead_3.06.0.1-4.debian.tar.xz
 2858ed9a36b06e3da4111955e10670f4 6190 graphics optional 
jhead_3.06.0.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmNvfz4ACgkQuPr/HEOI
Z3H63RAAyDHziczxqRXuFGJKiOpI6lRac3qAz6KSemK5u/QBVeIbztFZKvcypU7K
0+0MQ8No+c9HruRHdQZDk8RWJgP43XagsOyp1mtJ936HbOOAp9pruLPbHEpsixqo
8WxW4l7WsiZ1iKKUqzviKVEmhqTHLFIgQ3x+fPYfCWs6APzDz9I8CDtVYWvK+aO6
0ujSwCTnWwC1g2qQi4WsAjtlsV8xNw+49SNRTImifw011iBS2lNi/+i2BxDlDPp/
L+isSqeckZ+U5UEIs3CCLvaBSJqoU6IDKwhab+4AvbnRUaGJ99rZFY5ZKe7UwLNL
BJyc7Tzxeo10ybwIHoijht35V4Sl/jc4iO1wNUw6HdiGr+I/doTQxk6G0Q0Zy3GM
RRO+YPwzsPcUAHpUQmtReblBA1YLHwn+rv5NUyCahwH/wIT98yrd5veQlZWUUOIe
7cPetSaEK+lftKjONt0xA79mqw1Rp6NZcgvibNYr2UjRT6vTZQGoZ5s3zIgKy/+J
p9I21FqYRFa3GBdPHJy4in5uKNcigFM2su5v43caEn1rTsLGEL+gDs/rAXuEL3sN
O40xHrV+BCxn4NeBblA5FdZowwEVuFbRsQ+lFMhCe1J1lSbNU0mbnCXOJt8arYyN
1pucsj+JpveteyS59H78+r2ZTicogVqOqROdbY2TYb6h5JnRnE4=
=4wsx
-END PGP SIGNATURE End Message ---

Processed: found 1023899 in 1.5.2-4

[Debian Bug Tracking System]

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

> found 1023899 1.5.2-4
Bug #1023899 [src:pylibmc] pylibmc FTBFS with Python 3.11 as supported version
Marked as found in versions pylibmc/1.5.2-4.
> thanks
Stopping processing here.

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

Processed: bug 1023904 is forwarded to https://github.com/eerimoq/bitstruct/pull/26

[Debian Bug Tracking System]

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

> forwarded 1023904 https://github.com/eerimoq/bitstruct/pull/26
Bug #1023904 [src:bitstruct] bitstruct FTBFS with Python 3.11 as supported 
version
Set Bug forwarded-to-address to 'https://github.com/eerimoq/bitstruct/pull/26'.
> thanks
Stopping processing here.

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

Processed: tagging 989166, tagging 925274, tagging 940229, fixed 991309 in 0.9.9-1~exp1, tagging 1023899

[Debian Bug Tracking System]

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

> tags 989166 + bullseye sid
Bug #989166 [r-cran-gtools] Error: package or namespace load failed for ‘gtools’
Added tag(s) sid and bullseye.
> tags 925274 + bullseye sid
Bug #925274 {Done: Nicolas Braud-Santoni } [libu2f-udev] 
libu2f-udev: Please add support for solokey
Added tag(s) bullseye and sid.
> tags 940229 + bullseye sid
Bug #940229 {Done: ro...@atchoo.org (Roger A. Light)} [mosquitto] uses killall 
in logrotate snippet
Added tag(s) bullseye and sid.
> fixed 991309 0.9.9-1~exp1
Bug #991309 {Done: Christian Ehrhardt } 
[nftables] nftables 0.9.8 regresses icmp rule deletion
Marked as fixed in versions nftables/0.9.9-1~exp1.
> tags 1023899 + sid bookworm
Bug #1023899 [src:pylibmc] pylibmc FTBFS with Python 3.11 as supported version
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1023915: zodbpickle FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: zodbpickle
Version: 2.2.0-1
Severity: serious
Tags: ftbfs

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

...
src/zodbpickle/_pickle_33.c: In function ‘Pdata_New’:
src/zodbpickle/_pickle_33.c:201:19: error: lvalue required as left operand of 
assignment
  201 | Py_SIZE(self) = 0;
  |   ^
src/zodbpickle/_pickle_33.c: In function ‘Pdata_clear’:
src/zodbpickle/_pickle_33.c:227:19: error: lvalue required as left operand of 
assignment
  227 | Py_SIZE(self) = clearto;
  |   ^
src/zodbpickle/_pickle_33.c: In function ‘Pdata_pop’:
src/zodbpickle/_pickle_33.c:269:23: error: lvalue required as decrement operand
  269 | return self->data[--Py_SIZE(self)];
  |   ^~
src/zodbpickle/_pickle_33.c: In function ‘Pdata_push’:
src/zodbpickle/_pickle_33.c:279:29: error: lvalue required as increment operand
  279 | self->data[Py_SIZE(self)++] = obj;
  | ^~
src/zodbpickle/_pickle_33.c: In function ‘Pdata_poptuple’:
src/zodbpickle/_pickle_33.c:305:19: error: lvalue required as left operand of 
assignment
  305 | Py_SIZE(self) = start;
  |   ^
src/zodbpickle/_pickle_33.c: In function ‘Pdata_poplist’:
src/zodbpickle/_pickle_33.c:322:19: error: lvalue required as left operand of 
assignment
  322 | Py_SIZE(self) = start;
  |   ^
src/zodbpickle/_pickle_33.c: In function ‘save_float’:
src/zodbpickle/_pickle_33.c:1695:13: warning: implicit declaration of function 
‘_PyFloat_Pack8’; did you mean ‘PyFloat_Pack8’? 
[-Wimplicit-function-declaration]
 1695 | if (_PyFloat_Pack8(x, (unsigned char *)[1], 0) < 0)
  | ^~
  | PyFloat_Pack8
src/zodbpickle/_pickle_33.c: In function ‘load_binfloat’:
src/zodbpickle/_pickle_33.c:4247:9: warning: implicit declaration of function 
‘_PyFloat_Unpack8’; did you mean ‘PyFloat_Unpack8’? 
[-Wimplicit-function-declaration]
 4247 | x = _PyFloat_Unpack8((unsigned char *)s, 0);
  | ^~~~
  | PyFloat_Unpack8
src/zodbpickle/_pickle_33.c: In function ‘load_pop’:
src/zodbpickle/_pickle_33.c:4862:30: error: lvalue required as left operand of 
assignment
 4862 | Py_SIZE(self->stack) = len;
  |  ^
src/zodbpickle/_pickle_33.c: In function ‘do_append’:
src/zodbpickle/_pickle_33.c:5167:38: error: lvalue required as left operand of 
assignment
 5167 | Py_SIZE(self->stack) = x;
  |  ^
src/zodbpickle/_pickle_33.c:5173:30: error: lvalue required as left operand of 
assignment
 5173 | Py_SIZE(self->stack) = x;
  |  ^
src/zodbpickle/_pickle_33.c: In function ‘Pdata_pop’:
src/zodbpickle/_pickle_33.c:270:1: warning: control reaches end of non-void 
function [-Wreturn-type]
  270 | }
  | ^
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#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

[Joachim Reichel]

Hi Stefan,

thanks for the image. I just uploaded -4 which fixes the problem.

Best regards,
  Joachim

Bug#1023914: urwid FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: urwid
Version: 2.1.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=urwid=2.1.2-2%2Bb3

...
==
ERROR: test_coroutine_error 
(urwid.tests.test_event_loops.AsyncioEventLoopTest.test_coroutine_error)
--
Traceback (most recent call last):
  File "/<>/urwid/tests/test_event_loops.py", line 207, in 
test_coroutine_error
@asyncio.coroutine
 ^
AttributeError: module 'asyncio' has no attribute 'coroutine'

--
Ran 278 tests in 1.503s

FAILED (errors=1)
Test failed: 
(, ZeroDivisionError('division by zero'), )
error: Test failed: 
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: 
python3.11 setup.py test 

Bug#1023913: sip4 FTBFS with Python 3.11 as supported version

[Adrian Bunk]

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;
  |  ^~
...

Bug#1023912: python-uinput FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-uinput
Version: 0.11.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-uinput=0.11.2-3%2Bb3

...
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
python3.11 -m unittest discover -v 
uinput (unittest.loader._FailedTest.uinput) ... ERROR

==
ERROR: uinput (unittest.loader._FailedTest.uinput)
--
ImportError: Failed to import test module: uinput
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
_get_module_from_name
__import__(name)
  File "/<>/.pybuild/cpython3_3.11/build/uinput/__init__.py", line 
86, in 
_libsuinput_path = os.path.abspath(os.path.join(os.path.dirname(__file__), 
"..", "_libsuinput" + sysconfig.get_config_var("SO")))

 ~~^~~~
TypeError: can only concatenate str (not "NoneType") to str


--
Ran 1 test in 0.001s

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 
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10/build; 
python3.10 -m unittest discover -v 

--
Ran 0 tests in 0.000s

OK
dh_auto_test: error: pybuild --test -i python{version} -p "3.11 3.10" returned 
exit code 13

Bug#1023911: xdmf FTBFS with SWIG 4.1.0

[Adrian Bunk]

Source: xdmf
Version: 3.0+git20190531-11
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xdmf=3.0%2Bgit20190531-11%2Bb1

...
[ 81%] Building CXX object CMakeFiles/XdmfPython.dir/XdmfPYTHON_wrap.cxx.o
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5606:248: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5606 | SWIGINTERN std::vector< boost::shared_ptr< XdmfAttribute 
>,std::allocator< boost::shared_ptr< XdmfAttribute > > > 
*std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SggetitemSWIG_0(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT *slice){
  | 


   ^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘std::vector >* 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SggetitemSWIG_0(std::vector
 >*, int*)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5612:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5612 |   PySlice_GetIndices(slice, (Py_ssize_t)self->size(), , , 
);
  |  ^
  |  |
  |  int*
In file included from /usr/include/python3.10/Python.h:106,
 from 
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:168:
/usr/include/python3.10/sliceobject.h:41:46: note:   initializing argument 1 of 
‘int PySlice_GetIndices(PyObject*, Py_ssize_t, Py_ssize_t*, Py_ssize_t*, 
Py_ssize_t*)’
   41 | PyAPI_FUNC(int) PySlice_GetIndices(PyObject *r, Py_ssize_t length,
  |~~^
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: At global 
scope:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5617:149: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5617 | SWIGINTERN void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_0(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT 
*slice,std::vector< boost::shared_ptr< XdmfAttribute >,std::allocator< 
boost::shared_ptr< XdmfAttribute > > > const ){
  | 

^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_0(std::vector
 >*, int*, const std::vector >&)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5623:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5623 |   PySlice_GetIndices(slice, (Py_ssize_t)self->size(), , , 
);
  |  ^
  |  |
  |  int*
/usr/include/python3.10/sliceobject.h:41:46: note:   initializing argument 1 of 
‘int PySlice_GetIndices(PyObject*, Py_ssize_t, Py_ssize_t*, Py_ssize_t*, 
Py_ssize_t*)’
   41 | PyAPI_FUNC(int) PySlice_GetIndices(PyObject *r, Py_ssize_t length,
  |~~^
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: At global 
scope:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5628:149: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5628 | SWIGINTERN void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_1(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT *slice){
  | 

^~
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: In function 
‘void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgsetitemSWIG_1(std::vector
 >*, int*)’:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5634:26: 
error: cannot convert ‘int*’ to ‘PyObject*’ {aka ‘_object*’}
 5634 |   PySlice_GetIndices(slice, (Py_ssize_t)self->size(), , , 
);
  |  ^
  |  |
  |  int*
/usr/include/python3.10/sliceobject.h:41:46: note:   initializing argument 1 of 
‘int PySlice_GetIndices(PyObject*, Py_ssize_t, Py_ssize_t*, Py_ssize_t*, 
Py_ssize_t*)’
   41 | PyAPI_FUNC(int) PySlice_GetIndices(PyObject *r, Py_ssize_t length,
  |~~^
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx: At global 
scope:
/<>/debian/build-mpi-python3.11/XdmfPYTHON_wrap.cxx:5639:149: 
error: ‘SWIGPY_SLICEOBJECT’ has not been declared
 5639 | SWIGINTERN void 
std_vector_Sl_boost_shared_ptr_Sl_XdmfAttribute_Sg__SgdelitemSWIG_1(std::vector<
 boost::shared_ptr< XdmfAttribute > > *self,SWIGPY_SLICEOBJECT *slice){

Bug#1023910: python-snappy FTBFS with Python 3.11 as supported version

[Adrian Bunk]

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 

Bug#1023909: python-pgmagick FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-pgmagick
Version: 0.7.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-pgmagick=amd64=0.7.6-1%2Bb4=1668243187=0

...
==
ERROR: pgmagick (unittest.loader._FailedTest.pgmagick)
--
ImportError: Failed to import test module: pgmagick
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
_get_module_from_name
__import__(name)
  File 
"/<>/.pybuild/cpython3_3.11_pgmagick/build/pgmagick/__init__.py", 
line 1, in 
from pgmagick import _pgmagick
SystemError: initialization of _pgmagick raised unreported exception


--
Ran 1 test in 0.000s

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

Bug#1023908: pyfltk FTBFS with SWIG 4.1.0

[Adrian Bunk]

Source: pyfltk
Version: 1.3.8+repack-2
Severity: serious
Tags: ftbfs
Forwarded: https://sourceforge.net/p/pyfltk/code/597/

https://buildd.debian.org/status/logs.php?pkg=pyfltk=1.3.8%2Brepack-2%2Bb1

...
Running command: ['swig', '-w302', '-w312', '-w325', '-w362', '-w389', '-w401', 
'-w473', '-w509', '-I./swig', '-I/usr/include/libpng16', 
'-I/usr/include/freetype2', '-I/usr/include/uuid', '-I/usr/include/pixman-1', 
'-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/glib-2.0', 
'-I/usr/include/cairo', '-I/usr/include/libpng16', '-I/usr/include/freetype2', 
'-I/usr/include/uuid', '-I/usr/include/libpng16', '-I/usr/include/freetype2', 
'-I/usr/include/uuid', '-I/usr/include/pixman-1', 
'-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/glib-2.0', 
'-I/usr/include/cairo', '-I/usr/include', '-DFL_EXPORT', '-DPYTHON', 
'-DPYTHON3', '-py3', '-c++', '-python', '-shadow', '-fastdispatch', '-outdir', 
'fltk', '-o', 'fltk/fltk_wrap.cpp', './swig/fltk.i']
Deprecated command line option: -py3. Ignored, this option is no longer 
supported.
/usr/include/FL/Fl_Export.H:35: Error: Macro 'FL_EXPORT' redefined,
:1: Error: previous definition of 'FL_EXPORT'.
...

Bug#1023907: pybluez FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pybluez
Version: 0.23-5
Severity: serious
Tags: ftbfs

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

...
bluez/btmodule.c: In function ‘PyInit__bluetooth’:
bluez/btmodule.c:2984:25: error: lvalue required as left operand of assignment
 2984 | Py_TYPE(_type) = _Type;
  | ^
bluez/btmodule.c:2985:32: error: lvalue required as left operand of assignment
 2985 | Py_TYPE(_session_type) = _Type;
  |^
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#1023906: jcc FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: jcc
Version: 3.12-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=jcc=amd64=3.12-1%2Bb3=1668234417=0

...
In file included from /usr/include/python3.11/Python.h:44,
 from _jcc3/java/lang/Object.h:18,
 from jcc3/sources/functions.cpp:23:
jcc3/sources/functions.cpp: In function ‘void installType(PyTypeObject**, 
PyType_Def*, PyObject*, char*, int)’:
/usr/include/python3.11/object.h:136:30: error: lvalue required as left operand 
of assignment
  136 | #  define Py_TYPE(ob) Py_TYPE(_PyObject_CAST(ob))
  |   ~~~^~~~
jcc3/sources/functions.cpp:1742:13: note: in expansion of macro ‘Py_TYPE’
 1742 | Py_TYPE(*type) = PY_TYPE(FinalizerClass);
  | ^~~
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#1022459: marked as done (python-openflow: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 10:01:56 +
with message-id 
and subject line Bug#1022459: fixed in python-openflow 2019.2-3
has caused the Debian Bug report #1022459,
regarding python-openflow: FTBFS: distutils.errors.DistutilsClassError: command 
class  must subclass Command
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.)


-- 
1022459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-openflow
Version: 2019.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 clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:9: 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.clean import clean
> /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.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 112, in 
> setup(name='python-openflow',
>   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  '__main__.Cleaner'> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-openflow_2019.2-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: python-openflow
Source-Version: 2019.2-3
Done: Stefano Rivera 

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

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

Bug#1023905: blist FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: blist
Version: 1.3.6-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=blist=1.3.6-8%2Bb2

...
blist/_blist.c: In function ‘py_blist_sort’:
blist/_blist.c:6597:25: error: lvalue required as left operand of assignment
 6597 | Py_TYPE() = _Type;
  | ^
blist/_blist.c: In function ‘init_blist_types1’:
blist/_blist.c:7384:32: error: lvalue required as left operand of assignment
 7384 | Py_TYPE(_Type) = _Type;
  |^
blist/_blist.c:7385:36: error: lvalue required as left operand of assignment
 7385 | Py_TYPE(_Type) = _Type;
  |^
blist/_blist.c:7386:36: error: lvalue required as left operand of assignment
 7386 | Py_TYPE(_Type) = _Type;
  |^
blist/_blist.c:7387:43: error: lvalue required as left operand of assignment
 7387 | Py_TYPE(_Type) = _Type;
  |   ^
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#1022456: marked as done (django-js-reverse: FTBFS: TypeError: dist must be a Distribution instance)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 09:52:05 +
with message-id 
and subject line Bug#1022456: fixed in django-js-reverse 0.7.3-3
has caused the Debian Bug report #1022456,
regarding django-js-reverse: FTBFS: TypeError: dist must be a Distribution 
instance
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.)


-- 
1022456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-js-reverse
Version: 0.7.3-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):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:5: 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 setup
> /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.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 18, in 
> setup(
>   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
>   File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in 
> __init__
> super().__init__(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/django-js-reverse_0.7.3-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: django-js-reverse
Source-Version: 0.7.3-3
Done: Stefano Rivera 

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

(This message was generated automatically at their request; if 

Bug#1023904: bitstruct FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: bitstruct
Version: 8.9.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=bitstruct=8.9.0-3%2Bb2

...
ImportError: /<>/bitstruct/c.cpython-311-x86_64-linux-gnu.so: 
undefined symbol: _PyFloat_Pack2


--
Ran 27 tests in 0.014s

FAILED (errors=1)
Test failed: 
error: Test failed: 

Bug#1023903: python-clickhouse-driver FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-clickhouse-driver
Version: 0.2.3-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-clickhouse-driver=0.2.3-1.1%2Bb2

...
clickhouse_driver/bufferedreader.c:209:12: fatal error: longintrepr.h: No such 
file or directory
  209 |   #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#1023902: python-pam FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-pam
Version: 0.4.2-14
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-pam=0.4.2-14%2Bb1

...
PAMmodule.c: In function ‘PyPAM_pam’:
PAMmodule.c:110:32: error: lvalue required as left operand of assignment
  110 | Py_TYPE(_Type) = _Type;
  |^
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#1022449: marked as done (python-maxminddb: 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 Sat, 12 Nov 2022 09:26:26 +
with message-id 
and subject line Bug#1022449: fixed in python-maxminddb 2.2.0-0.1
has caused the Debian Bug report #1022449,
regarding python-maxminddb: 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.)


-- 
1022449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-maxminddb
Version: 2.0.3-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 '/<>'
> PYTHONPATH=.:$PYTHONPATH sphinx-build -b html -d .build/.doctrees -N docs 
> .build/html
> Running Sphinx v4.5.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> intersphinx inventory has moved: http://docs.python.org/objects.inv -> 
> https://docs.python.org/3/objects.inv
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
> 
> The HTML pages are in .build/html.
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:8: 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.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/errors.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/reader.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/file.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/const.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/types.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> copying maxminddb/decoder.py -> 
> /<>/.pybuild/cpython3_3.10_maxminddb/build/maxminddb
> running egg_info
> creating maxminddb.egg-info
> writing maxminddb.egg-info/PKG-INFO
> writing dependency_links to maxminddb.egg-info/dependency_links.txt
> writing top-level names to maxminddb.egg-info/top_level.txt
> writing manifest file 'maxminddb.egg-info/SOURCES.txt'
> Traceback (most recent call last):
>   File "/<>/setup.py", line 145, in 
> run_setup(True)
>   File "/<>/setup.py", line 101, in run_setup
> setup(
>   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 
> 185, in setup
> return run_commands(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 201, in run_commands
> dist.run_commands()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 968, in run_commands
> 

Processed: Bug#1022456 marked as pending in django-js-reverse

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022456 [src:django-js-reverse] django-js-reverse: FTBFS: TypeError: dist 
must be a Distribution instance
Added tag(s) pending.

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

Bug#1022456: marked as pending in django-js-reverse

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1022456 in django-js-reverse 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/django-js-reverse/-/commit/b9b3bc72d39eca09b4c7d7a4409529369d9e87a1


Patch: Setuptools 60 support. (Closes: #1022456)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022456

Bug#1023901: python-libtrace FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-libtrace
Version: 1.6+git20180219-1
Severity: serious
Tags: ftbfs bookworm sid
X-Debbugs-Cc: ac...@debian.org

https://buildd.debian.org/status/logs.php?pkg=python-libtrace=1.6%2Bgit20180219-1%2Bb9

...
creating build/temp.linux-x86_64-3.11
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../include 
-I/usr/include/python3.11 -c ippmodule.c -o 
build/temp.linux-x86_64-3.11/ippmodule.o
ippmodule.c: In function ‘PyInit_ipp’:
ippmodule.c:934:27: error: lvalue required as left operand of assignment
  934 |Py_TYPE() = _Type;
  |   ^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

Bug#1023900: python-keyutils FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: python-keyutils
Version: 0.6-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=python-keyutils=0.6-2%2Bb7

...
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 keyutils/_keyutils.c -o 
build/temp.linux-x86_64-cpython-311/keyutils/_keyutils.o
keyutils/_keyutils.c: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 

Processed: unarchiving 983815

[Debian Bug Tracking System]

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

> unarchive 983815
Bug #983815 {Done: Adrian Bunk } [src:python-crc32c] 
python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on armhf if 
built on 64bit hardware
Unarchived Bug 983815
> thanks
Stopping processing here.

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

Bug#1023444: marked as done (llvm-toolchain-14: FTBFS with swig 4.1: interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 09:08:17 +
with message-id 
and subject line Bug#1023444: fixed in llvm-toolchain-14 1:14.0.6-8
has caused the Debian Bug report #1023444,
regarding llvm-toolchain-14: FTBFS with swig 4.1: interfaces.swig:5: Error: 
Macro '__STDC_LIMIT_MACROS' redefined
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.)


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

Hi,

llvm-toolchain-14 FTBFS on i386 on the buildds, but I can reproduce that
locally on amd64 now, too.
Comparing the build logs shows swig 4.0.2-2 being used on the successful
amd64 buildd build and 4.1.0-0.1 on the failing i386 one.
(Please check the other llvm versions, too.)

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-14=i386=1%3A14.0.6-7=1667248227=0

...
[2858/7462] cd 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
&& /usr/bin/swig4.0 -c++ -features autodoc -I/<>/lldb/include 
-I/<>/lldb/bindings -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-I/<>/lldb/bindings/python -c++ -shadow -python -py3 -threads 
-outdir 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
-o 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 /<>/lldb/bindings/python/python.swig
FAILED: tools/lldb/bindings/python/LLDBWrapPython.cpp 
tools/lldb/bindings/python/lldb.py 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/lldb.py
cd 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
&& /usr/bin/swig4.0 -c++ -features autodoc -I/<>/lldb/include 
-I/<>/lldb/bindings -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-I/<>/lldb/bindings/python -c++ -shadow -python -py3 -threads 
-outdir 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
-o 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 /<>/lldb/bindings/python/python.swig
Deprecated command line option: -py3. Ignored, this option is no longer 
supported.
/<>/lldb/bindings/interfaces.swig:5: Error: Macro 
'__STDC_LIMIT_MACROS' redefined,
:1: Error: previous definition of '__STDC_LIMIT_MACROS'.
[2859/7462] /<>/build-llvm/./bin/clang++ -D_FILE_OFFSET_BITS=64 
-D_GNU_SOURCE -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen
 -I/<>/clang/utils/TableGen -I/<>/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/include 
-I/<>/llvm/include -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition 
-fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O3 -DNDEBUG  -fno-exceptions 
-std=c++14 -MD -MT 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o -MF 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o.d -o 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o -c 
/<>/clang/utils/TableGen/RISCVVEmitter.cpp
[2860/7462] /<>/build-llvm/./bin/clang++ -DHAVE_ROUND 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/utils/TableGen 
-I/<>/lldb/utils/TableGen -I/<>/lldb/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/include 
-I/<>/build-llvm/tools/clang/stage2-bins/include 
-I/<>/llvm/include -I/usr/include/python3.10 
-I/<>/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/../clang/include
 -I/usr/include/libxml2 

Processed: bug 1023789 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1782988

[Debian Bug Tracking System]

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

> forwarded 1023789 https://bugzilla.mozilla.org/show_bug.cgi?id=1782988
Bug #1023789 [src:thunderbird] thunderbird: FTBFS: error: no matching function 
for call to 'arc4random_buf'
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1782988'.
> thanks
Stopping processing here.

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

Bug#1023899: pylibmc FTBFS with Python 3.11 as supported version

[Adrian Bunk]

Source: pylibmc
Version: 1.5.2-4+b2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pylibmc=1.5.2-4%2Bb2

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean 
/<>/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.core import setup, Extension
Traceback (most recent call last):
  File "/<>/setup.py", line 98, in 
with open("README.rst", "U", encoding="utf-8") as r:
 ^
ValueError: invalid mode: 'U'
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:10: clean] Error 25

Processed: severity of 1022176 is serious

[Debian Bug Tracking System]

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

> severity 1022176 serious
Bug #1022176 [src:jpy] jpy: FTBFS with Python 3.11 as a supported version
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1023898: qtlocation-opensource-src: FTBFS on mipsel: test timeout

[Sebastian Ramacher]

Source: qtlocation-opensource-src
Version: 5.15.6+dfsg-2
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=qtlocation-opensource-src=mipsel=5.15.6%2Bdfsg-2%2Bb1=1668119800=0

* Finished testing of DefaultSourceTest *
make[3]: Leaving directory '/<>/tests/auto/qgeopositioninfosource'
PASS   : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateAfterStartUpdates_SmallInterval()
QDEBUG : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
 listening on QHostAddress("127.0.0.1") 43715
QWARN  : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
 Received pending connection: QTcpSocket(0x5755d1b8) true
PASS   : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
QDEBUG : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
 listening on QHostAddress("127.0.0.1") 43715
QWARN  : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
 Received pending connection: QTcpSocket(0x5765ea48) true
PASS   : 
tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateAfterStartUpdates_SmallInterval()
PASS   : 
tst_QNmeaPositionInfoSource_RealTime_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
QDEBUG : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout() 
listening on QHostAddress("127.0.0.1") 43715
QWARN  : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout() 
Received pending connection: QTcpSocket(0x57559130) true
PASS   : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForRequestTimeout()
QDEBUG : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated() 
listening on QHostAddress("127.0.0.1") 43715
QWARN  : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated() 
Received pending connection: QTcpSocket(0x5765f088) true
PASS   : 
tst_QNmeaPositionInfoSource_RealTime_Generic::removeSlotForPositionUpdated()
PASS   : tst_QNmeaPositionInfoSource_RealTime_Generic::cleanupTestCase()
Totals: 47 passed, 0 failed, 0 skipped, 0 blacklisted, 187926ms
* Finished testing of tst_QNmeaPositionInfoSource_RealTime_Generic 
*
make[4]: Leaving directory 
'/<>/tests/auto/qnmeapositioninfosource/qnmeapositioninfosource_realtime_generic'
PASS   : 
tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateBeforeStartUpdates_ZeroInterval()
PASS   : 
tst_QNmeaPositionInfoSource_Simulation_Generic::requestUpdateBeforeStartUpdates_SmallInterval()
PASS   : 
tst_QNmeaPositionInfoSource_Simulation_Generic::removeSlotForRequestTimeout()
PASS   : 
tst_QNmeaPositionInfoSource_Simulation_Generic::removeSlotForPositionUpdated()
PASS   : tst_QNmeaPositionInfoSource_Simulation_Generic::cleanupTestCase()
Totals: 47 passed, 0 failed, 0 skipped, 0 blacklisted, 189495ms
* Finished testing of tst_QNmeaPositionInfoSource_Simulation_Generic 
*
make[4]: Leaving directory 
'/<>/tests/auto/qnmeapositioninfosource/qnmeapositioninfosource_simulation_generic'
make[3]: Leaving directory '/<>/tests/auto/qnmeapositioninfosource'
E: Build killed with signal TERM after 150 minutes of inactivity


Cheers
-- 
Sebastian Ramacher

Bug#1022449: python-maxminddb: diff for NMU version 2.0.3-1.1

[Faidon Liambotis]

On Sat, Nov 12, 2022 at 08:06:56AM +, stefa...@debian.org wrote:
> Hi Faidon (2022.11.11_22:25:52_+)
> > I don't mind having an NMU, though, whether targeted or for the new
> > upstream version itself.
> 
> Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that.
>
> [...]
>
> > I have one small request, which would be to push the changes to the
> > git repo if you can (it's under the "debian" salsa project).
> 
> Done!
> 
\o/ That's amazing, thank you so much!

Best,
Faidon

Bug#1022449: python-maxminddb: diff for NMU version 2.0.3-1.1

[stefanor]

Hi Faidon (2022.11.11_22:25:52_+)
> I don't mind having an NMU, though, whether targeted or for the new
> upstream version itself.

Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that.

I'm afraid this specific bug isn't fixed there, yet, so we still need to
carry a patch. But it'll be in the next release.

I've been working through this class of FTBFS bugs, and this is a rare
case where the upstream has already dealt with the issue... But, not
released yet.

> I have one small request, which would be to push the changes to the
> git repo if you can (it's under the "debian" salsa project).

Done!

Upstream now has a main branch, so you probably want to delete your
master branch.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272