Free software activity in August 2026
My Debian contributions this month were all sponsored by Freexian.
You can also support my work directly via Liberapay or GitHub Sponsors.
Personal note
This month, my Dad unexpectedly passed away after a short illness. As a result I obviously got less work done than usual, and I still have a lot to take care of (since I’m the executor of his will, as well as helping with funeral arrangements) while grieving and generally having less focus and energy. Having routine work to do is one of the ways I cope with this sort of thing, but all the same, I hope people will bear with me and maybe remind me if I seem to be dropping the ball on something you especially need.
LLM vote
[Content note: strong opinions.]
I voted in General Resolution: LLM usage in Debian. My vote was pretty much the opposite of what ended up winning, so I’m quite disappointed. My personal opinion is that LLMs are cognitive hazards to their users that impose ecological costs far out of proportion to their utility at a time when the world absolutely cannot afford them. When the impossible economics of the large commercial models are finally allowed to catch up with reality, I expect there to be significant macroeconomic consequences, and that people who have become dependent on them will have problems; and who knows what the copyright situation on their output really is. I’m not convinced that local models are better enough on these axes to be worth the costs.
Debian’s direct contribution to all that will be negligible on a global scale, and even the most radical proposals in the GR didn’t expect that we could do much about upstreams that have gone all-in on LLMs. Even so, I’d hoped that my fellow developers might be more willing to lean on our position in the free software ecosystem to make at least a moderately radical statement. Instead, we’ve at best presented an undistinguished fence-sitting position to the world, and further entrenched the idea that humans can reliably do a good job of reviewing the output of tools that are designed to produce output plausible to humans. I certainly don’t trust my own code review skills that far.
Since I’ve never voluntarily used an LLM (not counting LLMs being foisted on me by things like search results, support chatbots, or incoming pull requests, regardless of whether I asked for them), and don’t intend to for the foreseeable future, I doubt this will change much for me in terms of the way I work. The winning option is a very weak one that imposes no new requirements on developers, which means that it also does nothing to stop me continuing to reject LLM-generated material from Debian bug reports and merge requests in my areas of responsibility. I know this probably won’t do much to satisfy people who have decided that Debian is slop now, but it’s the best I can do.
OpenSSH
I finally landed the GSS-API key exchange package split in our OpenSSH packaging. Here’s the NEWS entry:
openssh (1:10.4p1-5) unstable; urgency=medium
The openssh-client and openssh-server packages no longer include GSS-API
authentication and key exchange support; this adds pre-authentication
attack surface and generally increases complexity, and should only be used
where specifically needed. Users who need these features should install
openssh-client-gssapi or openssh-server-gssapi instead.
-- Colin Watson <cjwatson@debian.org> Sun, 23 Aug 2026 17:39:55 +0100
I upgraded from 10.4p1 to 10.5p1, which was a good test of keeping openssh and the new openssh-gssapi source package in sync.
PuTTY
I upgraded from 0.84 to 0.85.
Python packaging
New upstream versions:
- anorack
- djangorestframework (fixing a build failure)
- isort
- lazr.delegates (dropping pkg_resources)
- lazr.restfulclient (dropping pkg_resources)
- lazr.uri (dropping pkg_resources)
- nbclient (fixing a build failure)
- pydantic-settings
- python-argcomplete
- python-blockbuster
- python-makefun (fixing a build failure)
- python-persistent
- python-pytest-run-parallel
- python-time-machine
- python-typing-inspection
- wcwidth
- zope.hookable
- zope.i18nmessageid
- zope.interface
- zope.proxy
- zope.security
- zope.testrunner
The version treadmill continues: we’ve just finished dropping Python 3.13 as a supported version, so now we’ve started working on enabling Python 3.15 as a supported version. Maximiliano Curia has been very helpfully driving this. I didn’t get as much done here as I’d have liked (see the top of this post), but I fixed a couple of packages:
Other build/test failures:
- anorack
- buildbot
- codespell
- django-prometheus
- pendulum
- pydantic-core
- python-argcomplete
- python-ast-serialize
- python-bcrypt
- python-cross-web
- python-datamodel-code-generator
- python-djangorestframework-flex-fields
- python-openapi-core
- python-treq
- scikit-build-core
I fixed some other bugs:
- python-librosa: Hardcoded Python 3.13 in rules file
- python-makefun: Fails to build source after successful build
bugs.debian.org
I deployed the fix for Invalid link rel=”canonical” on bugs.debian.org. In the process I found a few bugs in recent undeployed code and fixed them.
Comments
With an account on the Fediverse or Mastodon, you can respond to this post. Since Mastodon is decentralized, you can use your existing account hosted by another Mastodon server or compatible platform if you don't have an account on this one. Known non-private replies are displayed below.
Learn how this is implemented here.