Bug#1070658: FTBFS: error: expected ‘)’ before ‘maxLength’

2024-05-06 Thread Stefano Rivera
Source: clickhouse
Version: 18.16.1+ds-7.4
Severity: serious
Tags: ftbfs
Justification: ftbfs

clickhouse FTBFS in unstable:

[ 87%] Building CXX object 
dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o
cd /<>/obj-x86_64-linux-gnu/dbms && /usr/bin/c++ 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -Ddbms_EXPORTS 
-I/<>/contrib/cityhash102/include 
-I/<>/libs/libpocoext/include 
-I/<>/libs/libmysqlxx/include 
-I/<>/contrib/libbtrie/include -isystem 
/<>/contrib/libdivide -isystem /<>/dbms/src -isystem 
/<>/obj-x86_64-linux-gnu/dbms/src -isystem 
/<>/contrib/libpcg-random/include -isystem 
/<>/libs/libcommon/include -isystem 
/<>/obj-x86_64-linux-gnu/libs/libcommon/include -isystem 
/usr/include/metrohash -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -pipe  
-fno-omit-frame-pointer  -Wall  -Wnon-virtual-dtor -Wextra -O2 -g -DNDEBUG -O3  
-std=c++17 -flto=auto -fno-fat-lto-objects -fPIC   
-fno-tree-loop-distribute-patterns -MD -MT 
dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -MF 
CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o.d -o 
CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -c 
/<>/dbms/src/Storages/MergeTree/LevelMergeSelector.cpp
In file included from 
/<>/dbms/src/Interpreters/InterserverIOHandler.h:8,
 from 
/<>/dbms/src/Storages/MergeTree/DataPartsExchange.h:3,
 from 
/<>/dbms/src/Storages/MergeTree/DataPartsExchange.cpp:1:
/usr/include/Poco/BinaryWriter.h:137:14: error: expected ‘)’ before ‘maxLength’
  137 | void writeCString(const char* cString, std::streamsize 
maxLength = DEFAULT_MAX_CSTR_LENGTH);
  |  ^~~~
/usr/include/Poco/BinaryWriter.h:137:14: note: to match this ‘(’
  137 | void writeCString(const char* cString, std::streamsize 
maxLength = DEFAULT_MAX_CSTR_LENGTH);
  |  ^~~~

Full build log:
https://debusine.debian.net/artifact/66597/clickhouse_18.16.1+ds-7.4_amd64-2024-05-06T16:48:46Z.build

Stefano



Bug#1068255: marked as pending in dh-python

2024-04-22 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1068255 in dh-python 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/tools/dh-python/-/commit/5406e503c4428ae3b019f2078146a1ea2dfc2fa5


dh_python3: Don't rename _module to module. (Closes: #1068255)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068255



Bug#1063989: marked as pending in xonsh

2024-03-31 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1063989 in xonsh 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/xonsh/-/commit/a6106cfef2c398408365d976bfde9efb1895b53f


New upstream release.

* New upstream release.
  - Supports pytest 8. (Closes: #1063989)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063989



Bug#1066764: marked as pending in python-authlib

2024-03-25 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1066764 in python-authlib 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-authlib/-/commit/1f6db06f30d70ef0cc3df5dbb4d669da7ce7a38d


Unset http_proxy and https_proxy for client test. (Closes: #1066764)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066764



Bug#1058132: marked as pending in python-mitogen

2024-03-08 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1058132 in python-mitogen 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-mitogen/-/commit/d017ecfea882adde47ddc3a7b3a58355babb6a28


Patch: Python 3.12 support. (Closes: #1058132, 1061755)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058132



Bug#1064689: marked as pending in objgraph

2024-02-28 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1064689 in objgraph 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/objgraph/-/commit/a229c89ca98f31735686636bb6ec40f10bf1f735


Run tests using upstream's test.py, not pytest. (Closes: #1064689)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064689



Bug#1064213: incus-agent: Incus Agent never starts due to ConditionPathExists

2024-02-18 Thread Stefano Rivera
Package: incus-agent
Version: 0.5.1-3
Severity: serious

...
Feb 18 14:31:55 debian systemd[1]: incus-agent.service - Incus - agent was 
skipped because of an unmet condition check 
(ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.incus).
...
Feb 18 14:31:55 debian systemd[1]: Starting systemd-udevd.service - Rule-based 
Manager for Device Events and Files...
Feb 18 14:31:55 debian systemd[1]: Started systemd-udevd.service - Rule-based 
Manager for Device Events and Files.
...

Because the systemd unit declares DefaultDependencies=no, it attempts to
start incus-agent before systemd-udevd has started, and so the path
doesn't exist yet.

I can't see any obvious way to delay the condition check, I think it's
best to just remove it, and allow the unit to quietly fail.

Stefano



Bug#1058198: marked as pending in autopep8

2024-01-22 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1058198 in autopep8 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/autopep8/-/commit/4872f13d07c9dff7ae5b3d1ab5a82c7e244a8a47


Patch: Python 3.12 support. (Closes: #1058198)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058198



Bug#1058172: unattended-upgrades: diff for NMU version 2.9.1+nmu4

2024-01-22 Thread Stefano Rivera
Control: tags 1058172 + patch
Control: tags 1058172 + pending

Dear maintainer,

I've prepared an NMU for unattended-upgrades (versioned as 2.9.1+nmu4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

Stefano
diff -Nru unattended-upgrades-2.9.1+nmu3/debian/changelog unattended-upgrades-2.9.1+nmu4/debian/changelog
--- unattended-upgrades-2.9.1+nmu3/debian/changelog	2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/debian/changelog	2024-01-22 16:11:59.0 -0400
@@ -1,3 +1,11 @@
+unattended-upgrades (2.9.1+nmu4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't run pyflakes, it dropped support for type comments.
+(Closes: #1058172)
+
+ -- Stefano Rivera   Mon, 22 Jan 2024 16:11:59 -0400
+
 unattended-upgrades (2.9.1+nmu3) unstable; urgency=medium
 
   * test: don't confuse -dbg and -unsigned with current running kernel
diff -Nru unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py
--- unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py	2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py	2024-01-22 16:11:59.0 -0400
@@ -7,6 +7,8 @@
 """ ensure that the tree is pyflakes clean """
 
 def test_pyflakes_clean(self):
+# https://github.com/PyCQA/pyflakes/issues/683
+self.skipTest("not clean, pyflakes no longer supports type comments")
 top_src_dir = os.path.join(os.path.dirname(__file__), "..")
 targets = [
 top_src_dir,


Bug#1058089: multiprocess: FTBFS: KeyError: '/psm_00befb89'

2024-01-21 Thread Stefano Rivera
Hi 1058089 (2024.01.21_17:19:38_-0400)
> This package ships a separate version of the source for each python 3.X
> version. So, this requires a new upstream release, git snapshot, or
> a patch with the 3.12 tree.

Oh, no, it does have the py3.12 dir. Never mind.

Stefano

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



Bug#1058089: multiprocess: FTBFS: KeyError: '/psm_00befb89'

2024-01-21 Thread Stefano Rivera
This package ships a separate version of the source for each python 3.X
version. So, this requires a new upstream release, git snapshot, or
a patch with the 3.12 tree.

https://github.com/uqfoundation/multiprocess/commits/master/py3.12

Stefano

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



Bug#1056505: marked as pending in python-stack-data

2024-01-21 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056505 in python-stack-data 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-stack-data/-/commit/9666fea069e975f1df166e37b1a4146e237ab88b


Write an autopkgtest that calls pybuild. We can't use autopkgtest-pkg-pybuild, 
as version.py isn't built yet. In combination with work in cython, this Closes: 
#1056505.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056505



Bug#1056511: marked as pending in python-urllib3

2024-01-21 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056511 in python-urllib3 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-urllib3/-/commit/5c1f30f127d360c60adfcce917f740275a51ca7b


Patch: Fix tests under Python 3.12. (Closes: #1056511)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056511



Bug#1056872: marked as pending in cython

2024-01-21 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056872 in cython 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/cython/-/commit/a8803eb6c512dbca7eb10fc6d652c24630760145


Patch: pyximport: Avoid chdir() and relative paths. (Closes: #1056872)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056872



Bug#1056483: python-memory-profiler's autopkg tests fail with Python 3.12

2024-01-20 Thread Stefano Rivera
Note: This package is no longer maintained upstream:
https://github.com/pythonprofilers/memory_profiler/issues/383

Stefano

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



Bug#1056414: marked as pending in ipython4

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056414 in ipython4 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/ipython/-/commit/461ff4ff6c2bfb35567884ea240bab29019cf25f


New upstream release.

* New upstream release.
  - Adds support for Python 3.12. (Closes: #1056414)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056414



Bug#1055570: marked as pending in lazy-object-proxy

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1055570 in lazy-object-proxy 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/lazy-object-proxy/-/commit/3e78c4e1840467d470cc282a79e9262c5e11b670


New upstream release.

* New upstream release.
  - Supports Python 3.12 (Closes: #1055570, 1058384)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1055570



Bug#1055568: marked as pending in m2crypto

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1055568 in m2crypto 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/m2crypto/-/commit/f00ff93bd40edb1647441943f0223b91e2cd8900


New upstream release.

* New upstream release.
  - Supports Python 3.12. (Closes: #1055568, 1040103)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1055568



Bug#1052849: marked as pending in python-pkginfo

2024-01-11 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1052849 in python-pkginfo 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-pkginfo/-/commit/84978dbed4417cd40d3fc3eb04ee0385bdb5fe33


Run the build-time tests with tox, so that the package is installed. Closes: 
#1052849


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052849



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

2024-01-11 Thread Stefano Rivera
Hi Andreas (2024.01.11_17:48:43_+)
> I've fixed the two other bugs in python-pkginfo and upgraded to latest
> upstream.  Unfortunately I have no clue about this issue.

The test is expecting the module to be installed in the test
environment. Either we could try harder to emulate that, or skip the
tests.

I committed a patch to run the test inside tox, which will install it in
a virtualenv before running the test.

Stefano

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



Bug#1059913: marked as pending in setuptools-scm

2024-01-03 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1059913 in setuptools-scm 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/setuptools-scm/-/commit/5dd92fba07814c9fd6c41f911e0bd1ba23828c8e


Explicitly depend on python3-setuptools (Closes: #1059913)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1059913



Bug#1052856: marked as pending in httpbin

2023-12-21 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1052856 in httpbin 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/httpbin/-/commit/5cb1ee47ba39aab5815289108a9b54c042dc8441


Patch: Support Flask >= 2.3.0, and avoid deprecation warnings in >= 2.2.0. 
(Closes: #1052856)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052856



Bug#1058096: marked as pending in xonsh

2023-12-17 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1058096 in xonsh 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/xonsh/-/commit/5b83ef4462292c31069c63514d4d7f86ebe85283


Patch: Support Sphinx >= 5. (Closes: #1058096)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058096



Bug#1056627: marked as pending in cython

2023-11-24 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056627 in cython 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/cython/-/commit/05b85b1c9c465cf3e0c88d96a4cdafeaf31631f1


cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056627



Bug#1056627: marked as pending in cython

2023-11-24 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1056627 in cython 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/cython/-/commit/075c1237c5112a873fd93c12e28981b1b5f44398


cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056627



Bug#1054946: marked as pending in distro-info

2023-10-29 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1054946 in distro-info 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/distro-info/-/commit/64aecef3f187152cdf13c8d9d982c25de9502882


Update tests for distro-info-data 0.59, which adjusted Debian 7's EoL (Closes: 
#1054946)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054946



Bug#1054591: python3-pyflow: ${VERSION} not expanded in package metadata, causing PEP-440 validation failures

2023-10-26 Thread Stefano Rivera
Package: python3-pyflow
Version: 1.1.20-4
Severity: serious

Filing this as serious severity, because it has the risk of breaking
unrelated software.

The background here is that setuptools since 66 has required PEP-440
valid versions for all packages installed on a system. Pip makes a noise
about this since 23.3 in preparation for completely rejecting them in
pip 24.
https://github.com/pypa/setuptools/issues/3772#issuecomment-1384342813
https://github.com/pypa/pip/issues/12063

It looks like ${VERSION} is never expanded in setup.py. I suspect this
is because you are grabbing source from GitHub, and not using tarballs
from "scratch/make_release_tarball.bash"

Please provide a valid version in the package metadata.

$ python3 -c 'import pkg_resources; pkg_resources.require("pyFlow")'

This affects bookworm too, if a virtualenv has --system-site-packages
(less common) and upgraded setuptools (very common).

Stefano



Bug#1054581: asdf: Missing dependency on asdf-unit-schemas (breaks pkg_resources)

2023-10-26 Thread Stefano Rivera
Package: asdf
Version: 2.14.3-1
Severity: serious

asdf's upstream requirements declare a dependency on asdf-unit-schemas,
but this doesn't exist in Debian, and isn't a dependency.

The relevant upstream change is https://github.com/asdf-format/asdf/pull/1210
It seems this used to be part of asdf-standard, but got moved into its
own module.

I see the relevant schemas still exist in asdf-standard in Debian.
However, missing this dependency this breaks Python pkg_resources, that
attempts to validate Python requirements.

Filing this as serious, because it breaks unrelated software when asdf
is installed.

In bookworm:
$ python3 -c 'import pkg_resources; pkg_resources.require("asdf")'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 956, in 
require
needed = self.resolve(parse_requirements(requirements))
 ^^
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 815, in 
resolve
dist = self._resolve_dist(
   ^^^
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 856, in 
_resolve_dist
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'asdf-unit-schemas>=0.1.0' distribution 
was not found and is required by asdf

The same thing happens in unstable.

If you are certain that you don't need a (non-optional) Python
dependency, the best thing to do is to patch it out of the requirements
in pyproject.toml.

Stefano



Bug#1052854: python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/vulndb/db'

2023-10-14 Thread Stefano Rivera
Hi Gianfranco (2023.09.26_16:55:49_+0200)
> hello, I see a TON of FTBFS bugs for python failures
> I suspect the reason for them to fail is
> * Remove *.egg-info directories in clean step, as part of Debian's wider
>   effort to improve clean targets. Thanks Stuart Prescott for the patch.

I haven't seen that many of these. A few, yes, maybe 3?

On balance, it still seems like the right change to have made.
There is the risk of silent breakage from missing files, but I haven't
heard of any of those, yet.

I'm coming around to making cleaning .egg-info configurable.
Right now you have to skip pybuild cleaning entirely, which is not
complex. But it's more than the one line instruction to skip egg-info
cleaning. I think configuration makes sense.

Stefano

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


signature.asc
Description: PGP signature


Bug#1050363: marked as pending in flit

2023-08-24 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1050363 in flit 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/flit/-/commit/c1e043d301493c47fe58ff579e80f5889f68d19e


Make README.rst and LICENSE available to build-time tests. (Closes: #1050363)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050363



Bug#1050163: dh-python is confused about the name for wheels on armel and armhf

2023-08-21 Thread Stefano Rivera
Control: forwarded -1 https://github.com/tox-dev/tox/issues/3100
Control: reassign -1 tox
Control: found -1 tox/4.9.0-1
Control: close -1 4.9.0-2
Control: affects -1 dh-python

This should already be fixed in tox.

This should be fixed by tox 4.9.0-2.

Stefano

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



Bug#1035694: python-bottle: diff for NMU version 0.12.23-1.2

2023-08-11 Thread Stefano Rivera
Control: tags 1035694 + patch
Control: tags 1035694 + pending

Dear maintainer,

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

Regards.

Stefano
diff -Nru python-bottle-0.12.23/debian/changelog python-bottle-0.12.23/debian/changelog
--- python-bottle-0.12.23/debian/changelog	2023-02-26 22:59:44.0 +0200
+++ python-bottle-0.12.23/debian/changelog	2023-08-11 17:42:13.0 +0200
@@ -1,3 +1,10 @@
+python-bottle (0.12.23-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depend on python3-wheel, for tox 4 support. (Closes: #1035694)
+
+ -- Stefano Rivera   Fri, 11 Aug 2023 17:42:13 +0200
+
 python-bottle (0.12.23-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-bottle-0.12.23/debian/control python-bottle-0.12.23/debian/control
--- python-bottle-0.12.23/debian/control	2023-02-26 22:48:33.0 +0200
+++ python-bottle-0.12.23/debian/control	2023-08-11 17:42:13.0 +0200
@@ -13,6 +13,7 @@
  python3-paste,
  python3-tornado,
  python3-werkzeug,
+ python3-wheel,
  tox
 Standards-Version: 4.6.1
 Homepage: https://bottlepy.org


Bug#1042918: reprotest: FTBFS with tox 4

2023-08-02 Thread Stefano Rivera
Source: reprotest
Version: 0.7.25
Severity: serious
Justification: ftbfs

I thought we'd managed to avoid this, in #1035645, but we just did the
transition, and I see reprotest is FTBFS:

I: pybuild base:275: cd 
/<>/.pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_reprote
st/reprotest-0.7.25-py3-none-any.whl -e py311 
py311: install_deps .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install coverage 
diffoscope pytest
py311: install_package_deps .pybuild/cpython3_3.11_reprotest/build> python -I 
-m pip install d
istro rstr
py311: install_package .pybuild/cpython3_3.11_reprotest/build> python -I -m pip 
install --forc
e-reinstall --no-deps 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-n
one-any.whl
py311: commands[0] .pybuild/cpython3_3.11_reprotest/build> 
.tox/py311/bin/python -m coverage r
un --omit '.tox/*' --parallel -m py.test tests/
__path__ attribute not found on 'py' while trying to find 'py.test'
py311: exit 1 (0.09 seconds) /<>> .tox/py311/bin/python -m 
coverage run --omit '.
tox/*' --parallel -m py.test tests/ pid=7370
  py311: FAIL code 1 (2.31=setup[2.22]+cmd[0.09] seconds)
  evaluation failed :( (2.36 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.
pybuild/cpython3_3.11_reprotest/build; tox -c /<>/tox.ini 
--sitepackages --instal
lpkg 
/<>/.pybuild/cpython3_3.11_reprotest/reprotest-0.7.25-py3-none-any.whl
 -e py311 
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
--test-tox returned exit code 13


I'm guessing you want to replace py.test there with pytest.

Stefano

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

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



Bug#1042917: rdflib-sqlalchemy: FTBFS with tox 4

2023-08-02 Thread Stefano Rivera
Source: rdflib-sqlalchemy
Version: 0.5.4-1
Severity: serious
Tags: upstream
Justification: ftbfs

With tox 4, rdflib-sqlalchemy FTBFS with:
   dh_auto_test -O--buildsystem=pybuild
E: pybuild pybuild:388: test: plugin distutils failed with: wheel is required 
to build wheels for distutils/setuptools packages. Build-Depend on 
python3-wheel.
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
returned exit code 13

I committed the fix for that to git, but the next issue is:

I: pybuild base:275: cd 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build; tox -c 
/<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
 -e py311 
py311: install_deps .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> python -I 
-m pip install mysqlclient psycopg2 'pytest-cov>=2.5.1' 'pytest>=3.4.0'
py311: install_package_deps .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> 
python -I -m pip install 'SQLAlchemy<2.0.0,>=1.1.4' 'alembic>=0.8.8' 
'rdflib>=4.0' 'six>=1.10.0'
py311: install_package .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> python 
-I -m pip install --force-reinstall --no-deps 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
py311: commands[0] .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> 
.tox/py311/bin/python setup.py clean --all
running clean
removing '/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build' (and 
everything under it)
removing 'build/bdist.linux-x86_64' (and everything under it)
'build/scripts-3.11' does not exist -- can't clean it
removing 'build'
py311: commands[1] .pybuild/cpython3_3.11_rdflib_sqlalchemy/build> pytest 
--cov=rdflib_sqlalchemy
py311: failed with pytest is not allowed, use allowlist_externals to allow it
  py311: FAIL code 1 (3.06 seconds)
  evaluation failed :( (3.12 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/build; tox -c 
/<>/tox.ini --sitepackages --installpkg 
/<>/.pybuild/cpython3_3.11_rdflib_sqlalchemy/rdflib_sqlalchemy-0.5.4-py3-none-any.whl
 -e py311 
dh_auto_test: error: pybuild --test --test-tox -i python{version} -p 3.11 
returned exit code 13

The fix here should be as simple as replacing "pytest" with "{envpython} -m 
pytest" in tox.ini

Stefano

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

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



Bug#932501: BTS housekeeping and severity adjustments

2023-07-21 Thread Stefano Rivera
Hi Adrian (2021.05.30_21:44:58_+0200)
> severity 932501 serious
I'm wondering if this bug should really be serious. Squid's apparmor
config is shipped disabled, so one has to manually enable it to trigger
this bug.

I would have gone for normal/important.

I don't know what the correct solution to this bug is. Presumably one
has to get the squid profile to include the abstraction that
squid-deb-proxy provides. I don't know how this is usually done in a
Debian package. Maybe one of the apparmor team can comment.

Stefano

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



Bug#1036943: marked as pending in dh-python

2023-06-03 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1036943 in dh-python 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/tools/dh-python/-/commit/f5e867022a03df5f76259a89d914650269158a2d


Reintroduce Breaks+Replaces on python2 needed to help apt in some upgrade 
scenarios. (Closes: #1036943)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1036943



Bug#1034079: marked as pending in wheel

2023-04-11 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1034079 in wheel 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/wheel/-/commit/91490bb17bac824668a6124a924baa1a15bcd28d


Correctly clean. (Closes: #1034079)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034079



Bug#1034079: marked as pending in wheel

2023-04-11 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1034079 in wheel 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/wheel/-/commit/06a0a4f1fa38f91a535104aac08e6f5f7b366414


Correctly clean. (Closes: #1034079)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034079



Bug#1031716: Generating stricter dependencies on python3-protobuf rdeps

2023-03-07 Thread Stefano Rivera
Hi Adrian (2023.03.07_10:09:35_+)
> Creating an own debhelper addon similar to dh_numpy3 would work for 
> automatically creating such dependencies, but is there any way for
> python3-protobuf to inject such versioned runtime dependencies into
> python3:Depends that does not require every rdep to manually add
> addon usage?

Yes, via pydist files, see /usr/share/doc/dh-python/README.PyDist
They are consulted when translating Python .dist-info/.egg-info requires
into Debian dependencies.

You can see a (more complex) example in cffi:
https://salsa.debian.org/python-team/packages/python-cffi/-/blob/master/debian/gen-backend-versions.py

SR

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



Bug#1031757: marked as pending in python-formencode

2023-02-24 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1031757 in python-formencode 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-formencode/-/commit/f365324c8211e80167c05014b3e7a0883e61bec1


Use virtualenvs in testfe-setuptools autopgktest, fixing a regression now that 
pip refuses --user installs. (Closes: #1031757)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031757



Bug#1031436: ubuntu-dev-tools: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

2023-02-19 Thread Stefano Rivera
err, and Mattia, of course:
> Benjamin: Launchpad doesn't have any modern CI, yet. How about moving
> ubuntu-dev-tools to Salsa (maybe create an ubuntu-developers-team?) and
> running linting under CI, there?

SR

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



Bug#1031436: ubuntu-dev-tools: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

2023-02-19 Thread Stefano Rivera
Hi Andreas (2023.02.19_05:10:13_-0400)
> Running linters during build seems like an equally bad idea as using
> -Werror in release builds! When ever a linter changes opinion of
> something the package will start to FTBFS (just like when gcc gains a
> new warning and code with -Werror starts to FTBFS).

Yeah, I agree with that.

These days, linters are something that one expects to run in CI on merge
requests, not at build time.

Benjamin: Launchpad doesn't have any modern CI, yet. How about moving
ubuntu-dev-tools to Salsa (maybe create an ubuntu-developers-team?) and
running linting under CI, there?

SR

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



Bug#1030806: pypy3: autopkgtest failure

2023-02-07 Thread Stefano Rivera
Hi Adrian (2023.02.07_16:10:23_+)

Ah, I forgot to bump the test dependency version requirement for pip.
It'll pass with the new pip in unstable (which will migrate soon).

SR

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



Bug#1030530: Python 3.10 in bookworm

2023-02-07 Thread Stefano Rivera
Hi Joost (2023.02.07_11:31:23_+)
> Op Tue, Feb 07, 2023 at 05:52:21AM + schreef Danial Behzadi دانیال بهزادی:
> > Does it worth trying to package pyenv for Debian? Ain't it against any 
> > rules?
> 
> See "ITP pyenv" @ http://bugs.debian.org/978149 .

I think the Python development community would be very happy to see
this. Debian's selected Python releases don't meet all the needs of
Python developers, who typically want access to all supported Python 3
versions (and possibly the next alpha), at all times.

I'd be happy to review and sponsor uploads.

Stefano

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



Bug#1030530: Python 3.10 in bookworm

2023-02-05 Thread Stefano Rivera
Hi Julian (2023.02.05_10:38:23_+)

> Why is the current intention not to ship the python3.10 package in
> bookworm?

Because we aim to have a single Python release supported in every stable
release.

> I was trying to run some experiments in a virtual environment a few
> days ago, and it turns out that several of the Python packages I
> needed do not yet run on Python 3.11.  I was saved by being able to
> run in a Python 3.10 venv and download all the required packages from
> PyPI.  If bookworm shipped without python3.10, I would not have been
> able to do my work.  Removing python3.10 from bookworm will seriously
> affect many of our users in a similar situation to me.

By the time bookworm releases, that probably won't be the case any more.
But anything that gets removed from Debian, because it isn't ready yet
obviously gets hurt in the process...

SR

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



Bug#1030220: xrayutilities: missing dependency on python3-h5py breaks armel tests

2023-02-01 Thread Stefano Rivera
Control: clone -1 -2
Control: reassign -2 src:python-h5py 3.7.0-3
Control: retitle -2 Provide PyDist overrides for h5py?

Hi Drew (2023.01.31_18:48:32_-0400)
> xrayutilities does have Build-Depends: python3-h5py. Evidentally
> dh-python3 isn't able to determine the correct dependency for h5py
> (likely it gets confused by python3-h5py-serial).  Until that's fixed,
> python3-xrayutilities should declare 
> Depends: python3-h5py
> explicitly.

This sounds like an issue in the way the python3-h5py package is
structured.

python3-h5py-serial has the .egg-info, so that's the dependency that's
being generated.

You can customize this with a PyDist override file, see:
/usr/share/doc/dh-python/README.PyDist

Maybe it would make sense to have a pydist like so:
h5py python3-h5py; PEP386

That way any package declaring a Python requires on h5py will get a
binary dependency on python3-h5py.

Thanks,

Stefano

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



Bug#1025183: silx: (autopkgtest) needs update for python3.11: Segmentation fault

2023-01-27 Thread Stefano Rivera
Hi Simon (2023.01.26_19:30:35_-0400)
> While I can't confirm the original error in the bug report, I can confirm
> that the autopkgtests fail with Python 3.11, and require some fixes.
> 
> I have uploaded a fix for this to Ubuntu, the delta is attached. I also
> uploaded this to DELAYED/2 (the fix is non-intrusive and only affects the
> test suite, so it should be safe). Please let me know if you would like this
> delayed further, cancelled, or expedited.

Thanks, I'll team-upload that now.

I had looked at the next upstream version, and got a whole slew of other
test failures. This looks like a much simpler solution...

SR

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



Bug#1026603: marked as pending in foolscap

2023-01-19 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1026603 in foolscap 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/foolscap/-/commit/f6175eefdec6ef8583054b016a9f21f9a32112c5


Patch: Python 3.11 support. (Closes: #1026603)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026603



Bug#1028704: distro-info: FTBFS: ModuleNotFoundError: No module named 'tomli'

2023-01-14 Thread Stefano Rivera
Control: reassign -1 pylint
Control: affects -1 src:distro-info

This is the same class of issue as #1027947. As long as Python 3.10 is a
supported release, please provide an explicit dependency on
python3-tomli.

The same thing could apply to any other dependencies that are generated
as "foo | python3 (>> 3.11)".

Thanks,

Stefano

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



Bug#1027947: marked as pending in setuptools-scm

2023-01-14 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1027947 in setuptools-scm 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/setuptools-scm/-/commit/6c175812f2a16e51e93ae8bf91e68c1371f24b33


Add an explicit Depends on python3-tomli, required while Python 3.10 is a 
supported version. (Closes: #1027947)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027947



Bug#1026569: marked as pending in python-rstr

2023-01-10 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1026569 in python-rstr 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-rstr/-/commit/91c31f055098729d174c3aee829ca494ff60e791


New upstream release.

* New upstream release.
  - Supports Python 3.11 (Closes: #1026569)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026569



Bug#1026622: python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends'

2023-01-10 Thread Stefano Rivera
I see that python-omemo 1.0.0 is a complete rewrite:
https://github.com/Syndace/python-omemo/blob/main/CHANGELOG.md#100---1st-of-november-2022

This removed the omemo.backends module.

I also see that the upstream has archived python-omemo-backend-signal
repo, around the same time:
https://github.com/Syndace/python-omemo-backend-signal

So, probably time to remove this from the archive, clearly they don't
intend to support the new API.

SR

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



Bug#1026537: marked as pending in python-cryptography

2023-01-08 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1026537 in python-cryptography 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-cryptography/-/commit/a740b22e2968a7539678a7aad41d5899241245f9


Patch: Remove the runtime dependency on cffi from .dist-info. (Closes: #1026537)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026537



Bug#1027398: gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install

2023-01-08 Thread Stefano Rivera
Control: reassign -1 src:gavodachs
Control: tag -1 + patch

> On Fri, Dec 30, 2022 at 10:13:45PM +0100, Paul Gevers wrote:
> > *** Error: Oops.  Unhandled exception AttributeError.
> > 
> > Exception payload: module 'lib' has no attribute
> > 'SSL_CTX_set_ecdh_auto'
> 
> While DaCHS doesn't do a good job of communicating this, the
> regression is actually within python3-openssl and python3-twisted.
> There's a test case in python3-twisted that looks like it is
> exercising the failing code.  I have tried to locate a corresponding
> bug against twisted, but I have not been able to locate it.  Is there
> any action I should take to alert the maintainers of the two packages?

I think that was a misdiagnosis. I found that too, when looking for the
source. But, of course, those test cases aren't being run at import
time.

The real issue was in pyopenssl, which was also updated around the same
time, to include this patch:
https://github.com/pyca/pyopenssl/commit/c8fe4dd5e91b00a5817db283c6198ef7031da825

However, there is also a Python 3.11 incompatibility breaking the
autopkgtests. Patch attached.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272
From: Stefano Rivera 
Date: Sun, 8 Jan 2023 15:18:21 -0400
Subject: Don't repeat global inline flags in the middle of a regex

[bpo-47066]: As of Python 3.11, global inline flags (e.g. (?i)) can now
only be used at the start of regular expressions. Using them elsewhere
has been deprecated since Python 3.6.

Bug-Debian: https://bugs.debian.org/1027398
---
 gavo/stc/tapstc.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gavo/stc/tapstc.py b/gavo/stc/tapstc.py
index 0e3c206..e744508 100644
--- a/gavo/stc/tapstc.py
+++ b/gavo/stc/tapstc.py
@@ -225,7 +225,7 @@ def getSimpleSTCSParser():
 		frameRE = _makeRE(TAP_SYSTEMS)
 		refposRE = _makeRE(TAP_REFPOS)
 		flavorRE = _makeRE(TAP_FLAVORS)
-		systemRE = (r"(?i)\s*"
+		systemRE = (r"\s*"
 			r"(?P%s)?\s*"
 			r"(?P%s)?\s*"
 			r"(?P%s)?\s*")%(
@@ -238,7 +238,7 @@ def getSimpleSTCSParser():
 			+coordsRE)
 		simpleStatement.setName("STC-S geometry")
 		simpleStatement.addParseAction(lambda s,p,t: _makePgSphereInstance(t))
-		system = Regex(systemRE)
+		system = Regex("(?i)" + systemRE)
 		system.setName("STC-S system spec")
 		region = Forward()
 		notExpr = CaselessKeyword("NOT") + Suppress('(') + region + Suppress(')')


Bug#1027815: adonthell: diff for NMU version 0.3.8-2.1

2023-01-03 Thread Stefano Rivera
Control: tags 1027815 + patch
Control: tags 1027815 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru adonthell-0.3.8/debian/changelog adonthell-0.3.8/debian/changelog
--- adonthell-0.3.8/debian/changelog	2022-03-28 13:31:59.0 -0400
+++ adonthell-0.3.8/debian/changelog	2023-01-03 13:39:42.0 -0400
@@ -1,3 +1,10 @@
+adonthell (0.3.8-2.1) unreleased; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support. (Closes: #1027815)
+
+ -- Stefano Rivera   Tue, 03 Jan 2023 13:39:42 -0400
+
 adonthell (0.3.8-2) unstable; urgency=high
 
   * Team upload.
diff -Nru adonthell-0.3.8/debian/patches/python3.11.patch adonthell-0.3.8/debian/patches/python3.11.patch
--- adonthell-0.3.8/debian/patches/python3.11.patch	1969-12-31 20:00:00.0 -0400
+++ adonthell-0.3.8/debian/patches/python3.11.patch	2023-01-03 13:39:42.0 -0400
@@ -0,0 +1,16 @@
+Remove  include. This was indirectly included via Python.h, and Python
+3.11 removed the header entirely.
+
+Author: Stefano Rivera 
+Bug-Debian: https://bugs.debian.org/1027815
+Forwarded: not-needed
+--- a/src/python_class.h
 b/src/python_class.h
+@@ -35,7 +35,6 @@
+ #include 
+ #include "Python.h"
+ #include "compile.h"
+-#include "eval.h"
+ #include "fileops.h"
+ 
+ #ifndef SWIG
diff -Nru adonthell-0.3.8/debian/patches/series adonthell-0.3.8/debian/patches/series
--- adonthell-0.3.8/debian/patches/series	2022-03-28 13:29:19.0 -0400
+++ adonthell-0.3.8/debian/patches/series	2023-01-03 13:37:51.0 -0400
@@ -1 +1,2 @@
 python3.10.patch
+python3.11.patch


Bug#1026599: cadabra2: FTBFS: type_caster_base.h:482:26: error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}

2023-01-03 Thread Stefano Rivera
Control: tag -1 + fixed-upstream

Looks like upstream has updated the embedded pybind11 for Python 3.11
support in 
https://github.com/kpeeters/cadabra2/commit/217bc21f9fff3de8eeb9ed651b2143a4f9c8a4b6
available from 2.4.2.2.

Of course it's worth asking if the Debian package should be using these
bundled libraries at all

SR

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



Bug#1027623: marked as pending in hatch-vcs

2023-01-01 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1027623 in hatch-vcs 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/hatch-vcs/-/commit/02cd4417ba053dd18c322e6e021f9c88f3e8cc35


Patch: Support setuptools_scm 7.1 in tests. (Closes: #1027623)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027623



Bug#1027461: marked as pending in beets

2023-01-01 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1027461 in beets 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/beets/-/commit/3061f007222b4f780b740ee212c65a855926be37


Patch: Support mediafile 0.11. (Closes: #1027461, 1027519)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027461



Bug#1026537: python-certbot: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

2022-12-30 Thread Stefano Rivera
Hi Harlan (2022.12.20_14:24:23_-0400)
> This error stems from the .egg-info file being shipped as part of
> python3-cffi, but the python3-cryptography lib only having Depends on the
> cffi backend lib.

I suspect the best thing to do here is to patch out that dependency. It
doesn't need python3-cffi at runtime (I assume). This is just
pkg_resources being annoying.

SR

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



Bug#1026312: meson: diff for NMU version 1.0.0-1.1

2022-12-27 Thread Stefano Rivera
Hi Eli (2022.12.24_21:46:13_-0400)
> This patch is non-upstreamable.

For context, this patch is along the same lines as changes you are
making in your refactor, upstream in
https://github.com/mesonbuild/meson/pull/11133

Your refactor goes further and removes distutils use entirely, where
possible. It's still required on older Debian systems, because the
deb_system scheme was patched into distutils but not sysconfig at the
time.

So, I still think we should be landing this patch in Debian, until your
refactor is released, and I haven't cancelled the NMU.

> I must confess however that I am surprised that setuptools is installed
> in your buildd at all -- Meson doesn't use it, and projects using Meson
> most likely don't also need setuptools at the same time. So this should
> be a moot point.
> 
> If setuptools is not installed, it cannot overwrite the stdlib
> distutils. And there's a viable approach to not using distutils by the
> time distutils is removed from the stdlib.

To expand on what Eli is saying here, if meson Conflicted with
python3-setuptools, or exported SETUPTOOLS_USE_DISTUTILS=stdlib, then
this patch would not be required.

However, such a conflict wouldn't be ideal for user systems. And
virtualenvs still come with setuptools by default, so meson probably
needs to be able to coexist with it.

For the export option, I wouldn't want to patch something like that into
our meson, unless we had to. That should be an upstream decision.

I think coexisting with setuptools and setuptools-distutils is the best
way forward.

SR

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



Bug#1025181: qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'

2022-12-25 Thread Stefano Rivera
I see this is fixed upstream in around 0.11, by
https://github.com/Qiskit/qiskit-ibmq-provider/pull/779

Given #1008627 and the deprecation upstream, should we just drop the
package, entirely?

SR

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



Bug#1025117: marked as pending in python-pyramid

2022-12-25 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1025117 in python-pyramid 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-pyramid/-/commit/198c2961b51f17d7768b675cd072ac319310d906


Patch: Add support for Python 3.11 (Closes: #1025117)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025117



Bug#1025111: python-omegaconf: diff for NMU version 2.2.2-2.1

2022-12-25 Thread Stefano Rivera
Control: tags 1025111 + patch

Dear maintainer,

I've prepared an NMU for python-omegaconf (versioned as 2.2.2-2.1). The diff
is attached to this message.

Regards.

SR
diff -Nru python-omegaconf-2.2.2/debian/changelog python-omegaconf-2.2.2/debian/changelog
--- python-omegaconf-2.2.2/debian/changelog	2022-10-26 06:24:04.0 -0400
+++ python-omegaconf-2.2.2/debian/changelog	2022-12-25 12:42:17.0 -0400
@@ -1,3 +1,10 @@
+python-omegaconf (2.2.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Support Python 3.11. (Closes: #1025111)
+
+ -- Stefano Rivera   Sun, 25 Dec 2022 12:42:17 -0400
+
 python-omegaconf (2.2.2-2) unstable; urgency=medium
 
   * Fixed VCS URLs (Closes: #1016890).
diff -Nru python-omegaconf-2.2.2/debian/patches/python-3.11.patch python-omegaconf-2.2.2/debian/patches/python-3.11.patch
--- python-omegaconf-2.2.2/debian/patches/python-3.11.patch	1969-12-31 20:00:00.0 -0400
+++ python-omegaconf-2.2.2/debian/patches/python-3.11.patch	2022-12-25 12:41:57.0 -0400
@@ -0,0 +1,1184 @@
+Description:
+ This PR updates OmegaConf's tests and metadata for compatibility with python3.11.
+ .
+ There are no changes to the omegaconf source code.
+ .
+ The changes to the test are motivated by python3.11 dataclasses dropping
+ support for mutable default arguments. This means dataclasses with mutable
+ default arguments must use default_factory.
+ .
+ I've updated the dataclasses in the test suite to use default_factory, and
+ I've added a file tests/structured_conf/dataclasses_pre_311.py that contains
+ old-style dataclasses that do not use default_factory for mutable dataclass
+ defaults. This pre_311 file is run only when python version < 3.10.
+ .
+ Commits:
+   tests/structured_config module fixture: use pytest.param
+   test dataclass with mutable default: skip if python>=3.11
+   tests/structured_conf: default_factory for mutable dataclass args
+   python3.11: add news fragment & update metadata
+   python3.11: update docs
+
+Author: Jasha <8935917+jash...@users.noreply.github.com>
+Origin: upstream, https://github.com/omry/omegaconf/pull/1032
+Bug-Debian: https://bugs.debian.org/1025111
+
+--- a/tests/structured_conf/test_structured_basic.py
 b/tests/structured_conf/test_structured_basic.py
+@@ -1,8 +1,9 @@
+ import re
++import sys
+ from importlib import import_module
+ from typing import Any, Optional
+ 
+-from pytest import fixture, mark, raises
++from pytest import fixture, mark, param, raises
+ 
+ from omegaconf import (
+ DictConfig,
+@@ -20,10 +21,17 @@
+ 
+ @fixture(
+ params=[
+-"tests.structured_conf.data.dataclasses",
+-"tests.structured_conf.data.attr_classes",
++param("tests.structured_conf.data.dataclasses", id="dataclasses"),
++param(
++"tests.structured_conf.data.dataclasses_pre_311",
++id="dataclasses_pre_311",
++marks=mark.skipif(
++sys.version_info >= (3, 11),
++reason="python >= 3.11 does not support mutable default dataclass arguments",
++),
++),
++param("tests.structured_conf.data.attr_classes", id="attr_classes"),
+ ],
+-ids=["dataclasses", "attr_classes"],
+ )
+ def module(request: Any) -> Any:
+ return import_module(request.param)
+--- a/tests/structured_conf/test_structured_config.py
 b/tests/structured_conf/test_structured_config.py
+@@ -29,10 +29,17 @@
+ 
+ @fixture(
+ params=[
+-"tests.structured_conf.data.dataclasses",
+-"tests.structured_conf.data.attr_classes",
++param("tests.structured_conf.data.dataclasses", id="dataclasses"),
++param(
++"tests.structured_conf.data.dataclasses_pre_311",
++id="dataclasses_pre_311",
++marks=mark.skipif(
++sys.version_info >= (3, 11),
++reason="python >= 3.11 does not support mutable default dataclass arguments",
++),
++),
++param("tests.structured_conf.data.attr_classes", id="attr_classes"),
+ ],
+-ids=["dataclasses", "attr_classes"],
+ )
+ def module(request: Any) -> Any:
+ return import_module(request.param)
+--- /dev/null
 b/tests/structured_conf/data/dataclasses_pre_311.py
+@@ -0,0 +1,879 @@
++import dataclasses
++import sys
++from dataclasses import dataclass, field
++from pathlib import Path
++from typing import Any, Dict, List, Optional, Tuple, Union
++
++from pytest import importorskip
++
++from omegaconf import II, MISSING, SI
++from tests import Color, Enum1
++
++if sys.version_info >= (3, 8):  # pragma: no cover
++from typing import TypedDict
++
++# skip test if dataclasses are not available
++importorskip("dataclas

Bug#1025107: marked as pending in python-limits

2022-12-25 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1025107 in python-limits 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-limits/-/commit/45af8aedb841c17c638942f9fff0e0c9e052b37a


Flush memcached storage between Python versions in python3-tests. (Closes: 
#1025107)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025107



Bug#1025023: marked as pending in python-boltons

2022-12-25 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1025023 in python-boltons 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-boltons/-/commit/118228847c8175b4392c6a7a2f42e5ee51c7f02e


Patch: Python 3.11 support. Closes: #1025023


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025023



Bug#1025016: onedrivesdk: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'

2022-12-25 Thread Stefano Rivera
The upstream has declared the project deprecated, and there are no
reverse-depends.

Time to remove it from Debian?

SR

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



Bug#1024915: i3pystatus: diff for NMU version 3.35+git20191126.5a8eaf4-2.1

2022-12-25 Thread Stefano Rivera
Control: tags 1024915 + patch

Dear maintainer,

I've prepared an NMU for i3pystatus (versioned as 
3.35+git20191126.5a8eaf4-2.1). The diff
is attached to this message.

Regards.

SR
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog	2019-11-27 12:39:56.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/changelog	2022-12-25 09:33:18.0 -0400
@@ -1,3 +1,10 @@
+i3pystatus (3.35+git20191126.5a8eaf4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for Python 3.11. (Closes: #1024915)
+
+ -- Stefano Rivera   Sun, 25 Dec 2022 09:33:18 -0400
+
 i3pystatus (3.35+git20191126.5a8eaf4-2) unstable; urgency=medium
 
   [ EstebanB ]
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch	1969-12-31 20:00:00.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/0001-Migrate-to-inspect.getfullargspec.patch	2022-12-25 09:33:09.0 -0400
@@ -0,0 +1,33 @@
+From 1a54a8332e9398f18c6c4f8258f4853f2cc53013 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Sun, 25 Dec 2022 09:26:31 -0400
+Subject: [PATCH] Migrate to inspect.getfullargspec()
+
+getargspec() was deprecated in 3.0 and removed in 3.11.
+
+Forwarded: https://github.com/enkore/i3pystatus/pull/844
+Bug-Debian: https://bugs.debian.org/1024915
+---
+ i3pystatus/core/modules.py | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+--- a/i3pystatus/core/modules.py
 b/i3pystatus/core/modules.py
+@@ -121,13 +121,14 @@
+ tmp_cb = cb
+ 
+ try:
+-args_spec = inspect.getargspec(tmp_cb)
++args_spec = inspect.getfullargspec(tmp_cb)
+ except Exception:
+-args_spec = inspect.ArgSpec([], None, None, None)
++args_spec = inspect.FullArgSpec(
++[], None, None, None, None, None, {})
+ 
+ # Remove all variables present in kwargs that are not used in the
+ # callback, except if there is a keyword argument.
+-if not args_spec.keywords:
++if not args_spec.varkw:
+ kwargs = {k: v for k, v in kwargs.items()
+   if k in args_spec.args}
+ cb(*args, **kwargs)
diff -Nru i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series
--- i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series	1969-12-31 20:00:00.0 -0400
+++ i3pystatus-3.35+git20191126.5a8eaf4/debian/patches/series	2022-12-25 09:32:32.0 -0400
@@ -0,0 +1 @@
+0001-Migrate-to-inspect.getfullargspec.patch


Bug#1024252: boost1.74: diff for NMU version 1.74.0-18.1

2022-12-24 Thread Stefano Rivera
Control: tags 1024252 + patch


Dear maintainer,

I've prepared an NMU for boost1.74 (versioned as 1.74.0-18.1). The diff
is attached to this message.

Regards.

SR
diff -Nru boost1.74-1.74.0/debian/changelog boost1.74-1.74.0/debian/changelog
--- boost1.74-1.74.0/debian/changelog	2022-12-17 16:19:02.0 -0400
+++ boost1.74-1.74.0/debian/changelog	2022-12-24 21:06:20.0 -0400
@@ -1,3 +1,11 @@
+boost1.74 (1.74.0-18.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update PEP-3149 patch to add support for Python 3.11 (which dropped the SO
+sysconfig variable). (Closes: #1024252)
+
+ -- Stefano Rivera   Sat, 24 Dec 2022 21:06:20 -0400
+
 boost1.74 (1.74.0-18) unstable; urgency=medium
 
   * [754888a] Disable blhc-check in gitlab-ci.
diff -Nru boost1.74-1.74.0/debian/patches/0001-Add-PEP-3149-compliant-extension-suffix-discovery.patch boost1.74-1.74.0/debian/patches/0001-Add-PEP-3149-compliant-extension-suffix-discovery.patch
--- boost1.74-1.74.0/debian/patches/0001-Add-PEP-3149-compliant-extension-suffix-discovery.patch	2022-12-17 16:09:48.0 -0400
+++ boost1.74-1.74.0/debian/patches/0001-Add-PEP-3149-compliant-extension-suffix-discovery.patch	2022-12-24 18:36:21.0 -0400
@@ -32,7 +32,7 @@
 +# Discover and set extension suffix
 +#
 +debug-message "Checking for extension suffix..." ;
-+local full-cmd = "from __future__ import print_function; import sysconfig; print(sysconfig.get_config_var('SO'))" ;
++local full-cmd = "from __future__ import print_function; import sysconfig; print(sysconfig.get_config_var('EXT_SUFFIX'))" ;
 +local full-cmd = $(interpreter-cmd)" -c \"$(full-cmd)\"" ;
 +debug-message "running command '$(full-cmd)'" ;
 +local result = [ SHELL $(full-cmd) : strip-eol : exit-status ] ;


Bug#1026312: meson: diff for NMU version 1.0.0-1.1

2022-12-24 Thread Stefano Rivera
Control: tags 1026312 + patch
Control: tags 1026312 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru meson-1.0.0/debian/changelog meson-1.0.0/debian/changelog
--- meson-1.0.0/debian/changelog	2022-12-23 12:24:54.0 -0400
+++ meson-1.0.0/debian/changelog	2022-12-24 11:22:03.0 -0400
@@ -1,3 +1,11 @@
+meson (1.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Correctly select the Debian python scheme with modern distutils.
+Closes: #1026312.
+
+ -- Stefano Rivera   Sat, 24 Dec 2022 11:22:03 -0400
+
 meson (1.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru meson-1.0.0/debian/patches/3-debian-sysconfig-layout.patch meson-1.0.0/debian/patches/3-debian-sysconfig-layout.patch
--- meson-1.0.0/debian/patches/3-debian-sysconfig-layout.patch	1969-12-31 20:00:00.0 -0400
+++ meson-1.0.0/debian/patches/3-debian-sysconfig-layout.patch	2022-12-24 11:22:03.0 -0400
@@ -0,0 +1,60 @@
+From 9cea9e351d20d58f447b06baa7bb9a3f5cc40ea4 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Mon, 19 Dec 2022 19:56:32 -0400
+Subject: [PATCH] Update the Debian Python path detection for setuptools >= 60
+
+Debian now (since Python 3.10.2-6) adds the deb_system scheme to
+sysconfig. Newer distutils (such as bundled with setuptools >= 60) adds
+fetch schemes from sysconfig, rather than duplicating the sysconfig
+schemes statically in distutils.command.install.
+
+This change broke meson's deb_system check.
+
+This patch replaces that mechanism (for newer Debian releases) with
+explicit scheme selection, which is far simpler.
+But it also retains the old mechanism, for older Debian releases that
+require it (Debian <= 11).
+
+Fixes: #8739 (for python module, and makes similar minimal changes to the python3 module)
+
+Fixes: https://bugs.debian.org/1026312
+
+Forwarded: https://github.com/mesonbuild/meson/pull/11211
+---
+ mesonbuild/modules/python.py | 14 +++---
+ 1 file changed, 11 insertions(+), 3 deletions(-)
+
+diff --git a/mesonbuild/modules/python.py b/mesonbuild/modules/python.py
+index f74d10e4c..68632af2d 100644
+--- a/mesonbuild/modules/python.py
 b/mesonbuild/modules/python.py
+@@ -363,15 +363,23 @@ def get_distutils_paths(scheme=None, prefix=None):
+ # default scheme to a custom one pointing to /usr/local and replacing
+ # site-packages with dist-packages.
+ # See https://github.com/mesonbuild/meson/issues/8739.
+-# XXX: We should be using sysconfig, but Debian only patches distutils.
++# Until version 3.10.2-6, Debian only patched distutils, not sysconfig.
+ 
+ if 'deb_system' in distutils.command.install.INSTALL_SCHEMES:
++# Debian systems before setuptools-bundled distutils was used by default
+ paths = get_distutils_paths(scheme='deb_system')
+ install_paths = get_distutils_paths(scheme='deb_system', prefix='')
+ else:
+-paths = sysconfig.get_paths()
++if 'deb_system' in sysconfig.get_scheme_names():
++# Use Debian's custom deb_system scheme (with our prefix)
++scheme = 'deb_system'
++elif sys.version_info >= (3, 10):
++scheme = sysconfig.get_default_scheme()
++else:
++scheme = sysconfig._get_default_scheme()
++paths = sysconfig.get_paths(scheme=scheme)
+ empty_vars = {'base': '', 'platbase': '', 'installed_base': ''}
+-install_paths = sysconfig.get_paths(vars=empty_vars)
++install_paths = sysconfig.get_paths(vars=empty_vars, scheme=scheme)
+ 
+ def links_against_libpython():
+ from distutils.core import Distribution, Extension
+-- 
+2.35.1
+
diff -Nru meson-1.0.0/debian/patches/series meson-1.0.0/debian/patches/series
--- meson-1.0.0/debian/patches/series	2021-02-14 08:58:40.0 -0400
+++ meson-1.0.0/debian/patches/series	2022-12-24 11:22:03.0 -0400
@@ -1,2 +1,3 @@
 1-disable-openmpi.patch
 2-disable-rootdir-test.patch
+3-debian-sysconfig-layout.patch


Bug#1025027: marked as pending in python-cffi

2022-12-04 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1025027 in python-cffi 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-cffi/-/commit/06dee85317a78dad380bd514c313d32adfec4b59


Patch: Untrack some objects that triggered assertion failures in 3.11. (Closes: 
#1024767, #1025027)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025027



Bug#1025015: marked as pending in objgraph

2022-11-28 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1025015 in objgraph 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/objgraph/-/commit/099164ac877e8b50e1b0548cb209addb4e0a285f


Patch: Python 3.11 support. (Closes: #1025015)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025015



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

2022-11-23 Thread Stefano Rivera
Control: tag -1 + fixed-upstream

Upstream claims that version 4.0.0 supports Python 3.11.

I tried backporting a minimal patch to bring 3.11 support back, but
tests fail. So... time to stop kicking this can down the road and update
to the latest upstream version.

SR



Bug#1024042: marked as pending in python-jpype

2022-11-23 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1024042 in python-jpype 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-jpype/-/commit/503262a6d9c673ba616c32c73e8a8286c7d4e5b0


New upstream release.

* New upstream release.
  - Supports Python 3.11. (Closes: #1024042)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024042



Bug#1024049: marked as pending in python-clevercsv

2022-11-23 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1024049 in python-clevercsv 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-clevercsv/-/commit/0c2f62b8b60949d0c4ce3e8f63d9fc1956e5384c


Patch: Python 3.11 support. (Closes: #1024049)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024049



Bug#1024043: marked as pending in python-cassandra-driver

2022-11-18 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1024043 in python-cassandra-driver 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-cassandra-driver/-/commit/a2cc8a12f8c090fbca8d281557f9a70b078c75c0


Patch: Python 3.11 support. (Closes: #1024043)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024043



Bug#1024048: pyliblo: diff for NMU version 0.10.0-5.1

2022-11-18 Thread Stefano Rivera
Control: tags 1024048 + patch
Control: tags 1024048 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru pyliblo-0.10.0/debian/changelog pyliblo-0.10.0/debian/changelog
--- pyliblo-0.10.0/debian/changelog	2021-11-21 17:07:07.0 +0200
+++ pyliblo-0.10.0/debian/changelog	2022-11-18 20:04:17.0 +0200
@@ -1,3 +1,10 @@
+pyliblo (0.10.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support (Closes: #1024048)
+
+ -- Stefano Rivera   Fri, 18 Nov 2022 20:04:17 +0200
+
 pyliblo (0.10.0-5) unstable; urgency=medium
 
   * Team upload
diff -Nru pyliblo-0.10.0/debian/patches/python3.11.patch pyliblo-0.10.0/debian/patches/python3.11.patch
--- pyliblo-0.10.0/debian/patches/python3.11.patch	1970-01-01 02:00:00.0 +0200
+++ pyliblo-0.10.0/debian/patches/python3.11.patch	2022-11-18 20:03:57.0 +0200
@@ -0,0 +1,164 @@
+Merge branch 'callable-callback'
+
+Includes migrating to inspect.getfullargspec() in Python 3.
+
+Origin: https://github.com/dsacre/pyliblo/commit/33999ca8178a01c720e99856df769f1986c7e912
+--- a/src/liblo.pyx
 b/src/liblo.pyx
+@@ -23,6 +23,7 @@
+ from liblo cimport *
+ 
+ import inspect as _inspect
++import functools as _functools
+ import weakref as _weakref
+ 
+ 
+@@ -249,7 +250,6 @@
+ free(url)
+ 
+ cb = cb_data
+-func = cb.func.func
+ 
+ func_args = (_decode(path),
+  args,
+@@ -257,20 +257,42 @@
+  src,
+  cb.user_data)
+ 
+-# call function
+-if _inspect.getargspec(func)[1] == None:
+-# determine number of arguments to call the function with
+-n = len(_inspect.getargspec(func)[0])
+-if _inspect.ismethod(func):
+-n -= 1  # self doesn't count
+-r = cb.func(*func_args[0:n])
+-else:
+-# function has argument list, pass all arguments
+-r = cb.func(*func_args)
++# call the function
++r = cb.func(*func_args[:cb.nargs])
+ 
+ return r if r != None else 0
+ 
+ 
++cdef int _callback_num_args(func):
++"""
++Return the number of arguments that should be passed to callback *func*.
++"""
++getargspec = (_inspect.getargspec if PY_VERSION_HEX < 0x0300
++ else _inspect.getfullargspec)
++
++if isinstance(func, _functools.partial):
++# before Python 3.4, getargspec() did't work for functools.partial,
++# so it needs to be handled separately
++argspec = getargspec(func.func)
++nargs = len(argspec.args) - len(func.args)
++if func.keywords is not None:
++nargs -= len(func.keywords)
++else:
++if (hasattr(func, '__call__') and
++not (_inspect.ismethod(func) or _inspect.isfunction(func))):
++func = func.__call__
++
++argspec = getargspec(func)
++nargs = len(argspec.args)
++
++if _inspect.ismethod(func):
++nargs -= 1  # self doesn't count
++
++# use all 5 arguments (path, args, types, src, user_data) if the
++# function has a variable argument list
++return nargs if argspec.varargs is None else 5
++
++
+ cdef int _bundle_start_callback(lo_timetag t, void *cb_data) with gil:
+ cb = cb_data
+ r = cb.start_func(_timetag_to_double(t), cb.user_data)
+@@ -446,11 +468,16 @@
+ 
+ self._check()
+ 
++# determine the number of arguments to call the function with
++nargs = _callback_num_args(func)
++
+ # use a weak reference if func is a method, to avoid circular
+ # references in cases where func is a method of an object that also
+ # has a reference to the server (e.g. when deriving from the Server
+ # class)
+-cb = struct(func=_weakref_method(func), user_data=user_data)
++cb = struct(func=_weakref_method(func),
++user_data=user_data,
++nargs=nargs)
+ # keep a reference to the callback data around
+ self._keep_refs.append(cb)
+ 
+--- a/test/test_liblo.py
 b/test/test_liblo.py
+@@ -15,6 +15,7 @@
+ import re
+ import time
+ import sys
++import functools
+ import liblo
+ 
+ 
+@@ -24,7 +25,7 @@
+ 
+ 
+ class Arguments:
+-def __init__(self, path, args, types, src, data):
++def __init__(self, path, args, types=None, src=None, data=None):
+ self.path = path
+ self.args = args
+ self.types = types
+@@ -178,6 +179,50 @@
+ with self.assertRaises(RuntimeError):
+ self.server.recv()
+ 
++def testCallbackVarargs(self):
++def foo(path, args, *varargs):
++self.cb = Arguments(path, args)
++self.cb_varargs = varargs
++self.server.add_method('/foo', 'f', foo, user_data='spam')
++self.server.send(1234, '/foo', 123.456)
++self.assertTrue(self.server.r

Bug#1023951: marked as pending in python-pyscss

2022-11-18 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1023951 in python-pyscss 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-pyscss/-/commit/0f15c67fa0592569d6d8aa397dd4c9e1828ca953


Patch: Python 3.11 support. (Closes: #1023951)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023951



Bug#1024088: marked as pending in pycxx

2022-11-18 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1024088 in pycxx 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/pycxx/-/commit/841e3484a9386a1b9c453bd197ee91b3a0175d33


Team upload.

* Team upload.
* Source-only upload to add Python 3.11 support. (Closes: #1024088)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024088



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

2022-11-18 Thread Stefano Rivera
Control: retitle -1 pythonmagick: only default python3 version extension is 
published in deb

Hi Graham (2022.11.17_11:40:02_+0200)
> This package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions.

It was trying to, but they were stomping on each other.

That's an easy fix. However... the resulting binary fails to import
under Python 3.11. That needs more debugging.

SR

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



Bug#1024299: marked as pending in pythonmagick

2022-11-18 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1024299 in pythonmagick 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/pythonmagick/-/commit/cc51c680cb6cd8a0520bbf8a7e83893de2e5f725


Install the C extensions into versioned directories, so they don't stop on each 
other. dh_python3 will tidy up. (Closes: #1024299)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024299



Bug#1023969: marked as pending in python3-typed-ast

2022-11-18 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1023969 in python3-typed-ast 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/python3-typed-ast/-/commit/cbb67339da432e172e22c122fcfb9178b33b8917


New upstream release.

* New upstream release.
  - Adds support for Python 3.11 (Closes: #1023969)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023969



Bug#1023901: python-libtrace: diff for NMU version 1.6+git20180219-1.1

2022-11-18 Thread Stefano Rivera
Control: tags 1023901 + patch
Control: tags 1023901 + pending
Control: forwarded 1023901 
https://github.com/nevil-brownlee/python-libtrace/pull/13

Dear maintainer,

I've prepared an NMU for python-libtrace (versioned as 1.6+git20180219-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru python-libtrace-1.6+git20180219/debian/changelog python-libtrace-1.6+git20180219/debian/changelog
--- python-libtrace-1.6+git20180219/debian/changelog	2018-06-03 15:54:48.0 +0200
+++ python-libtrace-1.6+git20180219/debian/changelog	2022-11-18 12:08:57.0 +0200
@@ -1,3 +1,10 @@
+python-libtrace (1.6+git20180219-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support. (Closes: #1023901)
+
+ -- Stefano Rivera   Fri, 18 Nov 2022 12:08:57 +0200
+
 python-libtrace (1.6+git20180219-1) unstable; urgency=medium
 
   * New upstream version from git snapshot.
diff -Nru python-libtrace-1.6+git20180219/debian/patches/python3.11.patch python-libtrace-1.6+git20180219/debian/patches/python3.11.patch
--- python-libtrace-1.6+git20180219/debian/patches/python3.11.patch	1970-01-01 02:00:00.0 +0200
+++ python-libtrace-1.6+git20180219/debian/patches/python3.11.patch	2022-11-18 12:08:57.0 +0200
@@ -0,0 +1,286 @@
+From 308a0158332677be4e5d74073e1c1929a5497618 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Fri, 18 Nov 2022 11:57:46 +0200
+Subject: [PATCH] Python 3.11 support
+
+Py_TYPE() changed to a inline static function, replace it with
+Py_SET_TYPE(). Include a backwards compatibility macro.
+
+See: bpo-39573
+Forwarded: https://github.com/nevil-brownlee/python-libtrace/pull/13
+Bug-Debian: https://bugs.debian.org/1023901
+---
+ lib/include/pv.h  |  6 ++
+ lib/ipp/ippmodule.c   |  2 +-
+ lib/natkit/natkit.c   |  4 ++--
+ lib/plt/icmp.c|  6 +++---
+ lib/plt/icmp6.c   | 10 +-
+ lib/plt/internet.c|  2 +-
+ lib/plt/ip.c  |  2 +-
+ lib/plt/ip6.c |  2 +-
+ lib/plt/ipflow.c  |  2 +-
+ lib/plt/layers.c  |  6 +++---
+ lib/plt/outputtrace.c |  4 ++--
+ lib/plt/packet.c  |  2 +-
+ lib/plt/pltmodule.c   |  2 +-
+ lib/plt/sctp.c|  4 ++--
+ lib/plt/tcp.c |  2 +-
+ lib/plt/trace.c   |  2 +-
+ lib/plt/udp.c |  2 +-
+ 17 files changed, 33 insertions(+), 27 deletions(-)
+
+diff --git a/lib/include/pv.h b/lib/include/pv.h
+index f85b172..4e758a2 100644
+--- a/lib/include/pv.h
 b/lib/include/pv.h
+@@ -58,4 +58,10 @@
+ #endif
+ #endif
+ 
++#if PY_VERSION_HEX < 0x030900A4 && !defined(Py_SET_TYPE)
++static inline void _Py_SET_TYPE(PyObject *ob, PyTypeObject *type)
++{ ob->ob_type = type; }
++#define Py_SET_TYPE(ob, type) _Py_SET_TYPE((PyObject*)(ob), type)
++#endif
++
+ #endif
+diff --git a/lib/ipp/ippmodule.c b/lib/ipp/ippmodule.c
+index c30b9b6..6e1d237 100644
+--- a/lib/ipp/ippmodule.c
 b/lib/ipp/ippmodule.c
+@@ -931,7 +931,7 @@ PyMODINIT_FUNC initipp(void)  {
+ 
+if (PyType_Ready() < 0)
+   RETURN;
+-   Py_TYPE() = _Type;
++   Py_SET_TYPE(, _Type);
+ 
+ #if PYTHON3
+m = PyModule_Create(_module);
+diff --git a/lib/natkit/natkit.c b/lib/natkit/natkit.c
+index 354757a..6fd4bea 100644
+--- a/lib/natkit/natkit.c
 b/lib/natkit/natkit.c
+@@ -722,10 +722,10 @@ PyObject *m=NULL;
+if (m == NULL) RETURN;
+ 
+if (PyType_Ready() < 0) RETURN;
+-   Py_TYPE() = _Type;
++   Py_SET_TYPE(, _Type);
+ 
+if (PyType_Ready() < 0) RETURN;
+-   Py_TYPE() = _Type;
++   Py_SET_TYPE(, _Type);
+ 
+Py_INCREF();
+PyModule_AddObject(m, "IPflow", (PyObject *));
+diff --git a/lib/plt/icmp.c b/lib/plt/icmp.c
+index db6b2ae..6da97d9 100644
+--- a/lib/plt/icmp.c
 b/lib/plt/icmp.c
+@@ -483,9 +483,9 @@ void initicmp(void) {
+if (PyType_Ready() < 0) return;
+if (PyType_Ready() < 0) return;
+ 
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
+ 
+Py_INCREF();
+PyModule_AddObject(plt_module, "icmp", (PyObject *));
+diff --git a/lib/plt/icmp6.c b/lib/plt/icmp6.c
+index 98ad09e..79a7c04 100644
+--- a/lib/plt/icmp6.c
 b/lib/plt/icmp6.c
+@@ -690,11 +690,11 @@ void initicmp6(void) {
+if (PyType_Ready() < 0) return;
+if (PyType_Ready() < 0) return;
+ 
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
+-   Py_TYPE() = _Type;
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
++   Py_SET_TYPE(, _Type);
+ 
+Py_INCREF();
+PyModule_AddObject(plt_module, "icmp6", (PyObject *));
+diff --git a/lib/plt/internet.c b/lib/plt/internet.c
+index 5fb04e1..7666389 100644
+--- a/lib/plt/internet.c
 b/lib/plt/internet.c
+@@ -423,7 +423,7 @@ PyTypeObject InternetType = {
+ void initinternet(void) {
+if (PyType_Ready() < 0) return;
+ 

Bug#1024265: opengv: diff for NMU version 1.0+1git91f4b1-6.1

2022-11-18 Thread Stefano Rivera
Control: tags 1024265 + pending

Dear maintainer,

I've prepared an NMU for opengv (versioned as 1.0+1git91f4b1-6.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

The patch (thanks Tyler!) may not be ideal, it's building the whole of the big
package, twice. There may be a more efficient way to only rebuild the
python bits. But I can't see that.

Also filed as: https://salsa.debian.org/science-team/opengv/-/merge_requests/2

Regards.

SR
diff -Nru opengv-1.0+1git91f4b1/debian/changelog opengv-1.0+1git91f4b1/debian/changelog
--- opengv-1.0+1git91f4b1/debian/changelog	2022-11-02 19:34:56.0 +0200
+++ opengv-1.0+1git91f4b1/debian/changelog	2022-11-18 11:43:32.0 +0200
@@ -1,3 +1,11 @@
+opengv (1.0+1git91f4b1-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use pybuild to build for multiple Python versions. Thanks Tyler Weaver.
+(Closes: #1024265)
+
+ -- Stefano Rivera   Fri, 18 Nov 2022 11:43:32 +0200
+
 opengv (1.0+1git91f4b1-6) unstable; urgency=medium
 
   * Arch:all builds work (Closes: #1020995)
diff -Nru opengv-1.0+1git91f4b1/debian/rules opengv-1.0+1git91f4b1/debian/rules
--- opengv-1.0+1git91f4b1/debian/rules	2022-11-02 19:34:56.0 +0200
+++ opengv-1.0+1git91f4b1/debian/rules	2022-11-18 11:43:32.0 +0200
@@ -4,14 +4,11 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-%:
-	dh $@ --with python3
+export PYBUILD_CONFIGURE_ARGS=-DBUILD_TESTS=ON -DBUILD_PYTHON=ON -DBUILD_SHARED_LIBS=ON
+export PYBUILD_SYSTEM=cmake
 
-override_dh_auto_configure:
-	dh_auto_configure -- \
-		-DBUILD_TESTS=ON \
-		-DBUILD_PYTHON=ON \
-		-DBUILD_SHARED_LIBS=ON
+%:
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_build-arch:
 	dh_auto_build -a
@@ -32,5 +29,3 @@
 override_dh_auto_clean:
 	dh_auto_clean
 	rm -rf doc/html doc/latex
-
-


Bug#1023903: python-clickhouse-driver: diff for NMU version 0.2.3-2

2022-11-18 Thread Stefano Rivera
Control: tags 1023903 + patch
Control: tags 1023903 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru python-clickhouse-driver-0.2.3/debian/changelog python-clickhouse-driver-0.2.3/debian/changelog
--- python-clickhouse-driver-0.2.3/debian/changelog	2022-04-01 04:07:11.0 +0200
+++ python-clickhouse-driver-0.2.3/debian/changelog	2022-11-18 11:50:06.0 +0200
@@ -1,3 +1,9 @@
+python-clickhouse-driver (0.2.3-2) unstable; urgency=medium
+
+  * Re-cythonize for Python 3.11 support (Closes: #1023903)
+
+ -- Stefano Rivera   Fri, 18 Nov 2022 11:50:06 +0200
+
 python-clickhouse-driver (0.2.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-clickhouse-driver-0.2.3/debian/control python-clickhouse-driver-0.2.3/debian/control
--- python-clickhouse-driver-0.2.3/debian/control	2022-03-23 01:49:28.0 +0200
+++ python-clickhouse-driver-0.2.3/debian/control	2022-11-18 11:49:31.0 +0200
@@ -4,6 +4,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
   dh-python,
+  cython3,
   python3-all-dev,
   python3-setuptools,
   python3-sphinx,


Bug#1024148: python-coverage: diff for NMU version 6.2+dfsg1-2.1

2022-11-16 Thread Stefano Rivera
Control: tags 1024148 + patch
Control: tags 1024148 + pending

Dear maintainer,

I've prepared an NMU for python-coverage (versioned as 6.2+dfsg1-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

BTW, it looks like 3.11 support is fully available from 6.4.2 onwards.

Regards.

SR
diff -Nru python-coverage-6.2+dfsg1/debian/changelog python-coverage-6.2+dfsg1/debian/changelog
--- python-coverage-6.2+dfsg1/debian/changelog	2022-01-14 01:43:38.0 +0200
+++ python-coverage-6.2+dfsg1/debian/changelog	2022-11-16 22:20:27.0 +0200
@@ -1,3 +1,10 @@
+python-coverage (6.2+dfsg1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support. Closes: #1024148.
+
+ -- Stefano Rivera   Wed, 16 Nov 2022 22:20:27 +0200
+
 python-coverage (6.2+dfsg1-2) unstable; urgency=medium
 
   * Correct autopkgtest control, for removal of ‘pypy-coverage’.
diff -Nru python-coverage-6.2+dfsg1/debian/patches/04.python3.11.patch python-coverage-6.2+dfsg1/debian/patches/04.python3.11.patch
--- python-coverage-6.2+dfsg1/debian/patches/04.python3.11.patch	1970-01-01 02:00:00.0 +0200
+++ python-coverage-6.2+dfsg1/debian/patches/04.python3.11.patch	2022-11-16 22:11:13.0 +0200
@@ -0,0 +1,145 @@
+From d723b46460dc7ffb4abf54806087ffd614b81331 Mon Sep 17 00:00:00 2001
+From: Ned Batchelder 
+Date: Sun, 9 Jan 2022 11:37:29 -0500
+Subject: [PATCH] fix: 3.11 now traces decorator lines as the decorators
+ execute
+
+See: https://bugs.python.org/issue46234
+---
+ coverage/env.py  |  4 
+ coverage/parser.py   | 10 --
+ tests/test_arcs.py   | 30 ++
+ tests/test_parser.py |  4 
+ 4 files changed, 38 insertions(+), 10 deletions(-)
+
+--- a/coverage/env.py
 b/coverage/env.py
+@@ -112,6 +112,10 @@
+ # Some words are keywords in some places, identifiers in other places.
+ soft_keywords = (PYVERSION >= (3, 10))
+ 
++# CPython 3.11 now jumps to the decorator line again while executing
++# the decorator.
++trace_decorator_line_again = (PYVERSION > (3, 11, 0, 'alpha', 3, 0))
++
+ 
+ # Coverage.py specifics.
+ 
+--- a/coverage/parser.py
 b/coverage/parser.py
+@@ -944,10 +944,11 @@
+ def _handle_decorated(self, node):
+ """Add arcs for things that can be decorated (classes and functions)."""
+ main_line = last = node.lineno
+-if node.decorator_list:
++decs = node.decorator_list
++if decs:
+ if env.PYBEHAVIOR.trace_decorated_def:
+ last = None
+-for dec_node in node.decorator_list:
++for dec_node in decs:
+ dec_start = self.line_for_node(dec_node)
+ if last is not None and dec_start != last:
+ self.add_arc(last, dec_start)
+@@ -955,6 +956,11 @@
+ if env.PYBEHAVIOR.trace_decorated_def:
+ self.add_arc(last, main_line)
+ last = main_line
++if env.PYBEHAVIOR.trace_decorator_line_again:
++for top, bot in zip(decs, decs[1:]):
++self.add_arc(self.line_for_node(bot), self.line_for_node(top))
++self.add_arc(self.line_for_node(decs[0]), main_line)
++self.add_arc(main_line, self.line_for_node(decs[-1]))
+ # The definition line may have been missed, but we should have it
+ # in `self.statements`.  For some constructs, `line_for_node` is
+ # not what we'd think of as the first line in the statement, so map
+--- a/tests/test_arcs.py
 b/tests/test_arcs.py
+@@ -1667,6 +1667,13 @@
+ """Tests of arcs with decorators."""
+ 
+ def test_function_decorator(self):
++arcz = (
++".1 16 67 7A AE EF F. " # main line
++".2 24 4.   -23 3-2 "   # decorators
++"-6D D-6 "  # my_function
++)
++if env.PYBEHAVIOR.trace_decorator_line_again:
++arcz += "A7 76 6A "
+ self.check_coverage("""\
+ def decorator(arg):
+ def _dec(f):
+@@ -1684,13 +1691,17 @@
+ a = 14
+ my_function()
+ """,
+-arcz=
+-".1 16 67 7A AE EF F. " # main line
+-".2 24 4.   -23 3-2 "   # decorators
+-"-6D D-6 ", # my_function
++arcz=arcz,
+ )
+ 
+ def test_class_decorator(self):
++arcz = (
++".1 16 67 6D 7A AE E. " # main line
++".2 24 4.   -23 3-2 "   # decorators
++"-66 D-6 "  # MyObject
++)
++if env.PYBEHAVIOR.trace_decorator_line_again:
++arcz += "A7 76 6A "
+

Bug#1023899: marked as pending in pylibmc

2022-11-16 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1023899 in pylibmc 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/pylibmc/-/commit/de8cf7f8a090b9bcbe80fd75e59a6ac512dd2d11


Adds support for Python 3.11. (Closes: #1023899)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023899



Bug#1023907: pybluez: diff for NMU version 0.23-5.1

2022-11-16 Thread Stefano Rivera
Control: tags 1023907 + patch
Control: tags 1023907 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru pybluez-0.23/debian/changelog pybluez-0.23/debian/changelog
--- pybluez-0.23/debian/changelog	2022-05-28 07:01:31.0 +0200
+++ pybluez-0.23/debian/changelog	2022-11-16 19:19:13.0 +0200
@@ -1,3 +1,10 @@
+pybluez (0.23-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Python 3.11 support. (Closes: #1023907)
+
+ -- Stefano Rivera   Wed, 16 Nov 2022 19:19:13 +0200
+
 pybluez (0.23-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru pybluez-0.23/debian/patches/python3.11.patch pybluez-0.23/debian/patches/python3.11.patch
--- pybluez-0.23/debian/patches/python3.11.patch	1970-01-01 02:00:00.0 +0200
+++ pybluez-0.23/debian/patches/python3.11.patch	2022-11-16 19:19:13.0 +0200
@@ -0,0 +1,450 @@
+From: Victor Stinner 
+Date: Wed, 8 Sep 2021 14:04:11 +0200
+Subject: Port to Python 3.11
+
+* Replace "arg == Py_None" with Py_IsNone(arg)
+* Replace arg->ob_type with Py_TYPE(arg)
+* Replace "Py_TYPE(obj) = type" with Py_SET_TYPE(obj, type).
+* Copy pythoncapi_compat.h from:
+  https://github.com/pythoncapi/pythoncapi_compat
+* pythoncapi_compat.h provides Py_SET_TYPE() and Py_IsNone() to old
+  Python versions.
+
+Origin: upstream, https://github.com/pybluez/pybluez/commit/5096047f90a1f6a74ceb250aef6243e144170f92
+Bug-Debian: https://bugs.debian.org/1023907
+---
+ bluez/btmodule.c  |  14 +-
+ bluez/pythoncapi_compat.h | 364 ++
+ 2 files changed, 372 insertions(+), 6 deletions(-)
+ create mode 100644 bluez/pythoncapi_compat.h
+
+diff --git a/bluez/btmodule.c b/bluez/btmodule.c
+index c870258..64481c7 100644
+--- a/bluez/btmodule.c
 b/bluez/btmodule.c
+@@ -22,6 +22,8 @@ Local naming conventions:
+ #include "btmodule.h"
+ #include "structmember.h"
+ 
++#include "pythoncapi_compat.h"
++
+ #include 
+ #include 
+ #include 
+@@ -679,7 +681,7 @@ sock_settimeout(PySocketSockObject *s, PyObject *arg)
+ {
+ 	double timeout;
+ 
+-	if (arg == Py_None)
++	if (Py_IsNone(arg))
+ 		timeout = -1.0;
+ 	else {
+ 		timeout = PyFloat_AsDouble(arg);
+@@ -1753,7 +1755,7 @@ bt_btohl(PyObject *self, PyObject *args)
+ 	else
+ 		return PyErr_Format(PyExc_TypeError,
+ "expected int/long, %s found",
+-arg->ob_type->tp_name);
++Py_TYPE(arg)->tp_name);
+ 	if (x == (unsigned long) -1 && PyErr_Occurred())
+ 		return NULL;
+ 	return PyInt_FromLong(btohl(x));
+@@ -1817,7 +1819,7 @@ bt_htobl(PyObject *self, PyObject *args)
+ 	else
+ 		return PyErr_Format(PyExc_TypeError,
+ "expected int/long, %s found",
+-arg->ob_type->tp_name);
++Py_TYPE(arg)->tp_name);
+ 	return PyInt_FromLong(htobl(x));
+ }
+ 
+@@ -1890,7 +1892,7 @@ bt_setdefaulttimeout(PyObject *self, PyObject *arg)
+ {
+ 	double timeout;
+ 
+-	if (arg == Py_None)
++	if (Py_IsNone(arg))
+ 		timeout = -1.0;
+ 	else {
+ 		timeout = PyFloat_AsDouble(arg);
+@@ -2981,8 +2983,8 @@ PyMODINIT_FUNC
+ init_bluetooth(void)
+ #endif
+ {
+-Py_TYPE(_type) = _Type;
+-Py_TYPE(_session_type) = _Type;
++Py_SET_TYPE(_type, _Type);
++Py_SET_TYPE(_session_type, _Type);
+ #if PY_MAJOR_VERSION >= 3
+ PyObject *m = PyModule_Create();
+ #else
+diff --git a/bluez/pythoncapi_compat.h b/bluez/pythoncapi_compat.h
+new file mode 100644
+index 000..e660b61
+--- /dev/null
 b/bluez/pythoncapi_compat.h
+@@ -0,0 +1,364 @@
++// 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-4

Bug#1023905: marked as pending in blist

2022-11-15 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1023905 in blist 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/blist/-/commit/3b2ef89642e7daa02ea7c35d398d76a6e791409d


Patch: Python 3.11 support (Closes: #1023905).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023905



Bug#1022480: python-peachpy: diff for NMU version 0.0~git20211013.257881e-1.1

2022-11-13 Thread Stefano Rivera
Control: tags 1022480 + patch
Control: tags 1022480 + pending

Dear maintainer,

I've prepared an NMU for python-peachpy (versioned as 
0.0~git20211013.257881e-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

SR
diff -Nru python-peachpy-0.0~git20211013.257881e/debian/changelog python-peachpy-0.0~git20211013.257881e/debian/changelog
--- python-peachpy-0.0~git20211013.257881e/debian/changelog	2022-01-10 07:28:35.0 +0200
+++ python-peachpy-0.0~git20211013.257881e/debian/changelog	2022-11-13 11:31:03.0 +0200
@@ -1,3 +1,10 @@
+python-peachpy (0.0~git20211013.257881e-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Support setuptools >= 60 (Closes: #1022480)
+
+ -- Stefano Rivera   Sun, 13 Nov 2022 11:31:03 +0200
+
 python-peachpy (0.0~git20211013.257881e-1) unstable; urgency=medium
 
   * New upstream version 0.0~git20211013.257881e (Closes: #966250)
diff -Nru python-peachpy-0.0~git20211013.257881e/debian/patches/empty-package-dir.patch python-peachpy-0.0~git20211013.257881e/debian/patches/empty-package-dir.patch
--- python-peachpy-0.0~git20211013.257881e/debian/patches/empty-package-dir.patch	1970-01-01 02:00:00.0 +0200
+++ python-peachpy-0.0~git20211013.257881e/debian/patches/empty-package-dir.patch	2022-11-13 11:31:03.0 +0200
@@ -0,0 +1,27 @@
+From eaa2eaef5e4f00bc61d0bc9dafbfda13518c7c57 Mon Sep 17 00:00:00 2001
+From: Alfredo Tupone 
+Date: Sun, 15 May 2022 20:03:39 +0200
+Subject: [PATCH] Update setup.py
+
+Consider the case where self.distribution.package_dir is an empty dictionary
+Origin: upstream, https://github.com/Maratyszcza/PeachPy/commit/eaa2eaef5e4f00bc61d0bc9dafbfda13518c7c57
+---
+ setup.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index bd80bd6..337b310 100755
+--- a/setup.py
 b/setup.py
+@@ -35,7 +35,7 @@ class GenerateInstructions(Command):
+ def run(self):
+ # package_dir may be None, in that case use the current directory.
+ import os
+-if self.distribution.package_dir is None:
++if not self.distribution.package_dir:
+ src_dir = os.getcwd()
+ else:
+ src_dir = os.path.abspath(self.distribution.package_dir[""])
+-- 
+2.35.1
+
diff -Nru python-peachpy-0.0~git20211013.257881e/debian/patches/series python-peachpy-0.0~git20211013.257881e/debian/patches/series
--- python-peachpy-0.0~git20211013.257881e/debian/patches/series	2022-01-10 07:24:58.0 +0200
+++ python-peachpy-0.0~git20211013.257881e/debian/patches/series	2022-11-13 11:31:03.0 +0200
@@ -1 +1,3 @@
 reproducible-build.patch
+empty-package-dir.patch
+setuptools-60.patch
diff -Nru python-peachpy-0.0~git20211013.257881e/debian/patches/setuptools-60.patch python-peachpy-0.0~git20211013.257881e/debian/patches/setuptools-60.patch
--- python-peachpy-0.0~git20211013.257881e/debian/patches/setuptools-60.patch	1970-01-01 02:00:00.0 +0200
+++ python-peachpy-0.0~git20211013.257881e/debian/patches/setuptools-60.patch	2022-11-13 11:31:03.0 +0200
@@ -0,0 +1,34 @@
+From a1a3b0b88ea2802d2b0c48c43c73f95897ed914f Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Sun, 13 Nov 2022 11:28:59 +0200
+Subject: [PATCH] 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/1022480
+Forwarded: https://github.com/Maratyszcza/PeachPy/pull/133
+---
+ setup.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/setup.py
 b/setup.py
+@@ -1,10 +1,10 @@
+ #!/usr/bin/env python
+ 
++from setuptools import setup
++from setuptools.command.develop import develop
+ import distutils.log
+ from distutils.command.build import build
+-from setuptools.command.develop import develop
+ from distutils.cmd import Command
+-from setuptools import setup
+ 
+ def read_text_file(path):
+ import os


Bug#1022538: marked as pending in python-grpc-tools

2022-11-13 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1022538 in python-grpc-tools 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-grpc-tools/-/commit/218f8384655239256211878d1d97b807247380d6


Patch: Support setuptools >= 60 (Closes: #1022538)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022538



Bug#1022538: marked as pending in python-mbed-ls

2022-11-13 Thread Stefano Rivera
Control: tag -1 pending

Hello,

Bug #1022538 in python-mbed-ls 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-ls/-/commit/d4ad8c4635f2f95bc02565be15fa679336beebac


Patch: Support setuptools >= 60 (Closes: #1022538)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022538



Bug#1022534: yaramod: diff for NMU version 3.6.0-1.1

2022-11-13 Thread Stefano Rivera
Control: tags 1022534 + patch
Control: tags 1022534 + pending

Dear maintainer,

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

Also filed as: https://salsa.debian.org/yangfl-guest/yaramod/-/merge_requests/1

Regards.

SR
diff -Nru yaramod-3.6.0/debian/changelog yaramod-3.6.0/debian/changelog
--- yaramod-3.6.0/debian/changelog	2020-07-18 10:32:07.0 +0200
+++ yaramod-3.6.0/debian/changelog	2022-11-13 10:21:29.0 +0200
@@ -1,3 +1,10 @@
+yaramod (3.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Support setuptools >= 60 (Closes: #1022534)
+
+ -- Stefano Rivera   Sun, 13 Nov 2022 10:21:29 +0200
+
 yaramod (3.6.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru yaramod-3.6.0/debian/patches/0004-Import-setuptools-before-distutils.patch yaramod-3.6.0/debian/patches/0004-Import-setuptools-before-distutils.patch
--- yaramod-3.6.0/debian/patches/0004-Import-setuptools-before-distutils.patch	1970-01-01 02:00:00.0 +0200
+++ yaramod-3.6.0/debian/patches/0004-Import-setuptools-before-distutils.patch	2022-11-13 10:21:29.0 +0200
@@ -0,0 +1,33 @@
+From: Stefano Rivera 
+Date: Sun, 13 Nov 2022 10:19:19 +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/1022534
+Forwarded: https://github.com/avast/yaramod/pull/224
+---
+ setup.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index df3cfc3..3ad5594 100644
+--- a/setup.py
 b/setup.py
+@@ -3,9 +3,9 @@ import re
+ import subprocess
+ import sys
+ 
+-from distutils.command.build import build
+ from setuptools import setup, Extension
+ from setuptools.command.build_ext import build_ext
++from distutils.command.build import build
+ 
+ 
+ script_dir = os.path.dirname(os.path.realpath(sys.argv[0]))
diff -Nru yaramod-3.6.0/debian/patches/series yaramod-3.6.0/debian/patches/series
--- yaramod-3.6.0/debian/patches/series	2020-07-18 10:32:07.0 +0200
+++ yaramod-3.6.0/debian/patches/series	2022-11-13 10:21:29.0 +0200
@@ -1,3 +1,4 @@
 0001-Build-Python-module-together.patch
 0002-Build-shared-library.patch
 0003-Use-system-packages.patch
+0004-Import-setuptools-before-distutils.patch


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

2022-11-13 Thread Stefano Rivera
Control: tags 1022527 + patch
Control: tags 1022527 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru ddupdate-0.6.6/debian/changelog ddupdate-0.6.6/debian/changelog
--- ddupdate-0.6.6/debian/changelog	2022-10-15 11:03:45.0 +0200
+++ ddupdate-0.6.6/debian/changelog	2022-11-13 10:16:41.0 +0200
@@ -1,3 +1,10 @@
+ddupdate (0.6.6-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for setuptools >= 60 (Closes: #1022527)
+
+ -- Stefano Rivera   Sun, 13 Nov 2022 10:16:41 +0200
+
 ddupdate (0.6.6-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ddupdate-0.6.6/debian/patches/series ddupdate-0.6.6/debian/patches/series
--- ddupdate-0.6.6/debian/patches/series	2022-01-20 16:12:35.0 +0200
+++ ddupdate-0.6.6/debian/patches/series	2022-11-13 10:13:03.0 +0200
@@ -1 +1,2 @@
 0001-fix-systemd-service
+setuptools-60
diff -Nru ddupdate-0.6.6/debian/patches/setuptools-60 ddupdate-0.6.6/debian/patches/setuptools-60
--- ddupdate-0.6.6/debian/patches/setuptools-60	1970-01-01 02:00:00.0 +0200
+++ ddupdate-0.6.6/debian/patches/setuptools-60	2022-11-13 10:14:07.0 +0200
@@ -0,0 +1,37 @@
+From b01dc01a3f4194043fae579416f5cab5c0b0 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Sun, 13 Nov 2022 10:07:43 +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/1022527
+Forwarded: https://github.com/leamas/ddupdate/pull/76
+---
+ setup.py | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+--- a/setup.py
 b/setup.py
+@@ -3,13 +3,12 @@
+ import shutil
+ import os
+ import subprocess
++from glob import glob
+ 
++from setuptools import setup
+ from distutils.command.clean import clean
+ from distutils.command.install import install
+ 
+-from glob import glob
+-from setuptools import setup
+-
+ # pylint: disable=bad-continuation
+ ROOT = os.path.dirname(__file__)
+ ROOT = ROOT if ROOT else '.'


Bug#1022525: python-cbor: diff for NMU version 1.0.0-1.2

2022-11-13 Thread Stefano Rivera
Control: tags 1022525 + patch
Control: tags 1022525 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru python-cbor-1.0.0/debian/changelog python-cbor-1.0.0/debian/changelog
--- python-cbor-1.0.0/debian/changelog	2019-10-15 02:56:11.0 +0200
+++ python-cbor-1.0.0/debian/changelog	2022-11-13 10:04:41.0 +0200
@@ -1,3 +1,11 @@
+python-cbor (1.0.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update homepage to point to the replacement GitHub repo.
+  * Patch: Support setuptools >= 60 (Closes: #1022525)
+
+ -- Stefano Rivera   Sun, 13 Nov 2022 10:04:41 +0200
+
 python-cbor (1.0.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-cbor-1.0.0/debian/control python-cbor-1.0.0/debian/control
--- python-cbor-1.0.0/debian/control	2019-10-15 02:56:01.0 +0200
+++ python-cbor-1.0.0/debian/control	2022-11-13 09:54:47.0 +0200
@@ -10,7 +10,7 @@
 Standards-Version: 4.0.0
 X-Python-Version: >= 2.7
 X-Python3-Version: >= 3.3
-Homepage: https://bitbucket.org/bodhisnarkva/cbor
+Homepage: https://github.com/brianolson/cbor_py
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/python-cbor.git
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/python-cbor.git
 
diff -Nru python-cbor-1.0.0/debian/copyright python-cbor-1.0.0/debian/copyright
--- python-cbor-1.0.0/debian/copyright	2015-09-03 20:50:51.0 +0200
+++ python-cbor-1.0.0/debian/copyright	2022-11-13 09:55:13.0 +0200
@@ -1,7 +1,7 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: python-cbor
-Upstream-Contact: https://bitbucket.org/bodhisnarkva/cbor
-Source: https://bitbucket.org/bodhisnarkva/cbor
+Upstream-Contact: https://github.com/brianolson/cbor_py
+Source: https://github.com/brianolson/cbor_py
 
 Files: *
 Copyright: 2014-2015 Brian Olson
diff -Nru python-cbor-1.0.0/debian/patches/series python-cbor-1.0.0/debian/patches/series
--- python-cbor-1.0.0/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ python-cbor-1.0.0/debian/patches/series	2022-11-13 09:58:00.0 +0200
@@ -0,0 +1 @@
+setuptools-60
diff -Nru python-cbor-1.0.0/debian/patches/setuptools-60 python-cbor-1.0.0/debian/patches/setuptools-60
--- python-cbor-1.0.0/debian/patches/setuptools-60	1970-01-01 02:00:00.0 +0200
+++ python-cbor-1.0.0/debian/patches/setuptools-60	2022-11-13 09:58:27.0 +0200
@@ -0,0 +1,42 @@
+From 36507492af9e51a95fe2514e07d283b30b812dd6 Mon Sep 17 00:00:00 2001
+From: Stefano Rivera 
+Date: Sun, 13 Nov 2022 09:56:25 +0200
+Subject: [PATCH] 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/1022525
+Forwarded: https://github.com/brianolson/cbor_py/pull/21
+---
+ setup.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 93fc7ee..0032a93 100644
+--- a/setup.py
 b/setup.py
+@@ -16,13 +16,13 @@
+ # Thanks!
+ # to Mic Bowman for a bunch of work and impetus on dumps(,sort_keys=)
+ 
++from setuptools import setup, Extension
++
+ from distutils.command.build_ext import build_ext
+ from distutils.errors import (CCompilerError, DistutilsExecError,
+ DistutilsPlatformError)
+ import sys
+ 
+-from setuptools import setup, Extension
+-
+ 
+ build_errors = (CCompilerError, DistutilsExecError, DistutilsPlatformError)
+ if sys.platform == 'win32' and sys.version_info > (2, 6):
+-- 
+2.35.1
+


Bug#1022526: python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

2022-11-13 Thread Stefano Rivera
Hi Helmut (2022.11.04_11:36:41_+0200)
> And no, updating it to 3.4 does not fix the ftbfs.

Updating it to 3.4.1 might. It includes this commit:
https://github.com/DinoTools/python-ssdeep/commit/fce02106c07ff56a84097dec0df02fb00ef69dc7
which moves the setuptools import above the first distutils import,
which should resolve this issue.

SR

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



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

2022-11-12 Thread 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

2022-11-12 Thread 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



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

2022-11-12 Thread 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


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

2022-11-12 Thread 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



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

2022-11-12 Thread 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



  1   2   3   4   5   >