About 95% of my Debian contributions this month were
sponsored by Freexian.
You can also support my work directly via
Liberapay or
GitHub
Sponsors.
OpenSSH
OpenSSH upstream released
10.1p1 this month, so I
upgraded to that. In the process, I reverted a Debian patch that changed
IP
quality-of-service defaults, which
made sense at the
time but has since been reworked upstream
anyway, so it makes sense to find out whether we still have similar
problems. So far I haven t heard anything bad in this area.
10.1p1 caused a regression in the ssh-agent-filter package s tests, which I
bisected and chased up with
upstream.
10.1p1 also had a few other user-visible regressions
(
#1117574,
#1117594,
#1117638,
#1117720); I upgraded to
10.2p1 which fixed some of
these, and
contributed some upstream debugging
help to clear up the
rest. While I was there, I also fixed
ssh-session-cleanup: fails due to
wrong $ssh_session_pattern in our packaging.
Finally, I got all this into trixie-backports, which I intend to keep up to
date throughout the forky development cycle.
Python packaging
For some time, ansible-core has had occasional autopkgtest failures that
usually go away before anyone has a chance to look into them properly. I
ran into these via openssh recently and decided to track them down. It
turns out that they only happened when the
libpython3.13-stdlib package
had different versions in testing and unstable, because an integration test
setup script made a change that would be reverted if that package was ever
upgraded in the testbed, and one of the integration tests accidentally
failed to disable system apt sources comprehensively enough while testing
the behaviour of the
ansible.builtin.apt module. I
fixed this in
Debian
and
contributed the relevant part
upstream.
We ve started working on enabling Python 3.14 as a supported version in
Debian. I fixed or helped to fix a number of packages for this:
I upgraded these packages to new upstream versions:
I packaged
python-blockbuster and
python-pytokens, needed as new
dependencies of various other packages.
Santiago Vila filed a
batch of
bugs
about packages that fail to build when using the
nocheck build
profile, and I fixed several of
these (generally just a matter of adjusting build-dependencies):
I helped out with the
scikit-learn 1.7
transition:
I fixed or helped to fix several other build/test failures:
I fixed some other bugs:
I investigated a
python-py build failure,
which turned out to have been fixed in Python 3.13.9.
I adopted
zope.hookable and
zope.location for the Python team.
Following an
IRC question, I
ported linux-gpib-user to
pybuild-plugin-pyproject,
and added tests to make sure the resulting binary package layout is correct.
Rust packaging
Another Pydantic upgrade meant I had to upgrade a corresponding stack of
Rust packages to new upstream versions:
- rust-idna
- rust-jiter
- rust-pyo3
- rust-regex
- rust-regex-automata
- rust-speedate
- rust-uuid
I also upgraded rust-archery and rust-rpds.
Other bits and pieces
I fixed a few bugs in other packages I maintain:
I investigated a
malware report against
tini, which I think we can prove to be a
false positive (at least under the reasonable assumption that there isn t
malware hiding in libgcc or glibc). Yay for reproducible builds!
I noticed and fixed a
small UI deficiency in
debbugs,
making the checkboxes under Misc options on package pages easier to hit.
This is merged but we haven t yet deployed it.
I notced and fixed a
typo
in the
Being kind to
porters
section of the Debian Developer s Reference.
Code reviews
