About 90% of my Debian contributions this month were
sponsored by Freexian.
You can also support my work directly via
Liberapay or
GitHub
Sponsors.
Some months I feel like I m pedalling furiously just to keep everything in a
roughly working state. This was one of those months.
Python team
I upgraded these packages to new upstream versions:
- aiosmtplib
- billiard
- dbus-fast
- django-modeltranslation
- django-sass-processor
- feedparser
- flask-security
- jaraco.itertools
- mariadb-connector-python
- mistune
- more-itertools
- pydantic-settings
- pyina
- pytest-mock
- python-asyncssh
- python-bytecode
- python-ciso8601
- python-django-pgbulk
- python-ewokscore
- python-ewoksdask
- python-ewoksutils
- python-expandvars
- python-git
- python-gssapi
- python-holidays
- python-jira
- python-jpype
- python-mastodon
- python-orjson (fixing a build failure)
- python-pyftpdlib
- python-pytest-asyncio (fixing a build
failure)
- python-pytest-run-parallel
- python-recurring-ical-events
- python-redis
- python-watchfiles (fixing a build
failure)
- python-x-wr-timezone
- python-zipp
- pyzmq
- readability
- scalene (fixing test failures with pydantic 2.12.0~a1)
- sen (contributed supporting fix
upstream)
- sqlfluff
- trove-classifiers
- ttconv
- vdirsyncer
- zope.component
- zope.configuration
- zope.deferredimport
- zope.deprecation
- zope.exceptions
- zope.i18nmessageid
- zope.interface
- zope.proxy
- zope.schema
- zope.security (contributed supporting fix
upstream)
- zope.testing
- zope.testrunner
I had to spend a fair bit of time this month chasing down build/test
regressions in various packages due to some other upgrades, particularly to
pydantic, python-pytest-asyncio, and rust-pyo3:
After some upstream discussion I
requested removal of
pydantic-compat, since it was more trouble
than it was worth to keep it working with the latest pydantic version.
I filed
dh-python: pybuild-plugin-pyproject doesn t know about
headers and added it to
Python/PybuildPluginPyproject,
and converted some packages to
pybuild-plugin-pyproject:
I updated dh-python to
suppress generated dependencies that would be
satisfied by python3 >=
3.11.
pkg_resources is
deprecated. In most cases
replacing it is a relatively simple matter of
porting to
importlib.resources,
but packages that used its old namespace package support need more
complicated work to port them to
implicit namespace
packages. We had quite a few bugs about
this on
zope.* packages, but fortunately upstream did the
hard part of
this recently. I went
round and cleaned up most of the remaining loose ends, with some help from
Alexandre Detiste. Some of these aren t completely done yet as they re
awaiting new upstream releases:
- zope.component (Debian bug, upstream
PR)
- zope.configuration (Debian bug,
upstream
PR)
- zope.deferredimport (Debian bug,
upstream
PR)
- zope.deprecation (Debian bug, upstream
PR)
- zope.exceptions (Debian bug, upstream
PR)
- zope.i18nmessageid (Debian bug,
upstream
PR)
- zope.interface (Debian bug, upstream
PR)
- zope.location (Debian bug, upstream
PR)
- zope.security (Debian bug, upstream
PR)
- zope.testing (Debian bug, upstream
PR)
- zope.testrunner (Debian bug, upstream
PR)
This work also caused a couple of build regressions, which I fixed:
I fixed
jupyter-client
so that its autopkgtests would work in Debusine.
I fixed
waitress to build with the
nocheck profile.
I fixed several other build/test failures:
I fixed some other bugs:
Code reviews
Other bits and pieces
I fixed several CMake 4 build failures:
I got
CI for debbugs passing
(
!22,
!23).
I fixed a
build failure with GCC 15 in
trn4.
I filed a
release-notes bug about the
tzdata reorganization in the trixie cycle.
I filed and fixed a
git-dpm regression with bash
5.3.
I upgraded libfilter-perl to a new upstream version.
I
optimized some code in
ubuntu-dev-tools
that made O(1)
HTTP requests when it could instead make O(n).
The following contributors got their Debian Developer accounts in the last two
months: