--- /dev/null
+Title: Free software activity in August 2025
+Slug: activity-2025-08
+Date: 2025-09-03 11:56:59 +01:00
+Category: columbiform
+Tags: activity, columbiform, freexian, planet-debian, planet-ubuntu
+Summary: Lots of Python package upgrades, and planning for `setup.py install` being removed.
+Mastodon-ID: 115140004439269694
+
+About 95% of my Debian contributions this month were
+[sponsored](https://www.freexian.com/about/debian-contributions/) by
+Freexian.
+
+You can also support my work directly via
+[Liberapay](https://liberapay.com/cjwatson) or [GitHub
+Sponsors](https://github.com/sponsors/cjwatson).
+
+## Python team
+
+forky is
+[open](https://lists.debian.org/debian-devel-announce/2025/08/msg00002.html)!
+As a result I'm starting to think about the [upcoming Python
+3.14](https://peps.python.org/pep-0745/). At some point we'll doubtless do
+a full test rebuild, but in advance of that I concluded that one of the most
+useful things I could do would be to work on our [very long list of packages
+with new upstream
+versions](https://udd.debian.org/dmd/?email1=team%2Bpython%40tracker.debian.org).
+Of course there's no real chance of this ever becoming empty since upstream
+maintainers aren't going to stop work for that long, but there are a lot of
+packages there where we're quite a long way out of date, and many of those
+include fixes that we'll need for 3.14, either directly or by fixing
+interactions with new versions of other packages that in turn will need to
+be fixed. We can backport changes when we need to, but more often than not
+the most efficient way to do things is just to keep up to date.
+
+So, I upgraded these packages to new upstream versions (deep breath):
+
+* aioftp
+* aiosignal (building on [work by
+ IanLucca](https://salsa.debian.org/python-team/packages/aiosignal/-/merge_requests/1))
+* audioop-lts
+* celery
+* djangorestframework
+* djoser
+* fpylll
+* frozenlist
+* git-repo-updater
+* ipykernel
+* klepto
+* kombu
+* multipart
+* netmiko (sponsoring [work by Eduardo
+ Silva](https://salsa.debian.org/python-team/packages/netmiko/-/merge_requests/1);
+ [contributed supporting fix
+ upstream](https://github.com/ktbyers/netmiko/pull/3722))
+* pathos
+* ppft
+* pydantic
+* pydantic-core
+* pydantic-settings
+* pylsqpack
+* pymssql
+* pytest-mock
+* pytest-pretty
+* pytest-repeat
+* pytest-rerunfailures
+* python-a2wsgi
+* python-apptools (sponsoring [work by Kathlyn Lara
+ Murussi](https://salsa.debian.org/python-team/packages/python-apptools/-/merge_requests/6))
+* python-asgiref
+* python-asyncssh
+* python-bitarray
+* python-bitstring
+* python-bytecode
+* python-channels-redis
+* python-charset-normalizer
+* python-daphne
+* python-django-analytical
+* python-django-guid
+* python-django-health-check
+* python-django-pgbulk
+* python-django-pgtrigger
+* python-django-postgres-extra
+* python-django-storages
+* python-holidays
+* python-httpx-sse
+* python-icalendar
+* python-lazy-model
+* python-line-profiler
+* python-lz4
+* python-marshmallow-dataclass
+* python-mastodon
+* python-model-bakery
+* python-oauthlib
+* python-parse-type
+* python-pathvalidate
+* python-pgspecial
+* python-processview
+* python-pytest-subtests
+* python-roman
+* python-semantic-release
+* python-testfixtures
+* python-time-machine
+* python-tokenize-rt
+* python-typeguard
+* python-typing-extensions
+* python-urllib3
+* pyupgrade
+* requests (fixing [CVE-2024-47081](http://bugs.debian.org/1107368))
+* responses
+* zope.deferredimport
+* zope.schema
+* zope.testrunner
+
+That's only about 10% of the backlog, but of course others are working on
+this too. If we can keep this up for a while then it should help.
+
+I packaged [pytest-run-parallel](https://bugs.debian.org/1111640),
+[pytest-unmagic](https://bugs.debian.org/1110995) (still in `NEW`), and
+[python-forbiddenfruit](https://bugs.debian.org/1111569) (still in `NEW`),
+all needed as new dependencies of various other packages.
+
+setuptools upstream will be [removing the `setup.py install`
+command](https://setuptools.pypa.io/en/stable/history.html#v80-1-0) on 31
+October. While this may not trickle down immediately into Debian, it does
+mean that in the near future nearly all Python packages will have to use
+`pybuild-plugin-pyproject` (note that this does _not_ mean that they
+necessarily have to use `pyproject.toml`; this is just a question of how the
+packaging runs the build system). We talked about this a bit at DebConf,
+and I said that I'd noticed a number of packages where this isn't
+straightforward and promised to write up some notes. I wrote the
+[Python/PybuildPluginPyproject](https://wiki.debian.org/Python/PybuildPluginPyproject)
+wiki page for this; I expect to add more bits and pieces to it as I find
+them.
+
+On that note, I converted several packages to `pybuild-plugin-pyproject`:
+
+* billiard
+* lazr.config
+* python-timeline
+* zope.sqlalchemy
+* zope.testing
+
+I fixed several build/test failures:
+
+* [aiosmtplib](https://bugs.debian.org/1111057)
+* [blinker](https://bugs.debian.org/1111058)
+* [ipykernel](https://bugs.debian.org/1111059)
+* [ipyparallel](https://bugs.debian.org/1111060)
+* [quart](https://salsa.debian.org/python-team/packages/quart/-/commit/481c11c4fc33a18b17f8b223dff584342adc84af)
+
+I fixed some other bugs:
+
+* [austin: binutils now has a libsframe-dev package, please add an explicit
+ build dependency](https://bugs.debian.org/1110821)
+* [python-django-pgbulk: Missing dependency on
+ python3-typing-extensions](https://salsa.debian.org/python-team/packages/python-django-pgbulk/-/commit/96a17113f634d3c401c21a113579273ec49ccc2b)
+ ([contributed
+ upstream](https://github.com/AmbitionEng/django-pgbulk/pull/54))
+* [python-maturin: Upcoming rust-which
+ update](https://bugs.debian.org/1110139)
+
+I reviewed [Debian defaults: nftables as banaction and systemd as
+backend](https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/18),
+but it looked as though nothing actually needed to be changed so we closed
+this with no action.
+
+## Rust team
+
+Upgrading Pydantic was complicated, and required a rust-pyo3 transition
+(which Jelmer Vernooij started and Peter Michael Green has mostly been
+driving, thankfully), packaging rust-malloc-size-of (including an [upstream
+portability fix](https://github.com/servo/malloc_size_of/pull/12)), and
+upgrading several packages to new upstream versions:
+
+* rust-serde
+* rust-serde-derive
+* rust-serde-json
+* rust-smallvec
+* rust-speedate
+* rust-time
+* rust-time-core
+* rust-time-macros
+
+## bugs.debian.org
+
+I fixed [bugs.debian.org: misspelled checkbox id
+"uselessmesages"](https://bugs.debian.org/1078575), as well as a [bug that
+caused incoming emails with certain header contents to go
+missing](https://salsa.debian.org/debbugs-team/debbugs/-/commit/fff0db4e57a2781f5c82827e42f395a3325270f3).
+
+## OpenSSH
+
+I fixed [openssh-server: refuses further connections after having handled
+PerSourceMaxStartups connections](https://bugs.debian.org/1080350) with a
+cherry-pick from upstream.
+
+## Other bits and pieces
+
+I upgraded libfido2 to a new upstream version.
+
+I fixed [mimalloc: FTBFS on armhf: cc1: error: ‘-mfloat-abi=hard’: selected
+architecture lacks an FPU](https://bugs.debian.org/1103589), which was
+blocking changes to pendulum in the Python team. I also spent some time
+helping to investigate [libmimalloc3: Illegal instruction Running mtxrun
+--generate](https://bugs.debian.org/1106879), though that bug is still open.
+
+I fixed [various autopkgtest bugs in
+gssproxy](https://salsa.debian.org/debian/gssproxy/-/compare/debian%2F0.9.2-3...debian%2F0.9.2-4?from_project_id=45135),
+prompted by
+[#1007](https://salsa.debian.org/freexian-team/debusine/-/issues/1007) in
+Debusine.
+
+Since my old team is [decommissioning Bazaar/Breezy code hosting in
+Launchpad](https://blog.launchpad.net/general/phasing-out-bazaar-code-hosting)
+(the end of an era, which I have distinctly mixed feelings about), I
+converted [Storm](https://git.launchpad.net/storm) to git.
~cjwatson / blog.git / commitdiff