In November I spent 0 hours on Debian LTS, and 5.5 on ELTS.

I reviewed updates by Bastien Roucariès for Python 2.7, 3.5, and 3.7. This mostly involved backporting the same set of patches to older releases, where things worked a little differently.

In October I spent 1 hours on Debian LTS, and 2.5 on ELTS.

Updating the distro-info-data database. A straightforward data update, but I ran into a bug in sbuild+autopkgtest that made my sbuild unable to build on old ELTS releases. Once understood, it was trivial to fix.

I also re-investigated the current state of the PEP-440 issue that affects Python virtulenvs on older releases, that have system site package exposed to the virtualenv. Newer Python tooling (likely to be installed in a virtualenv) does not accept that Python packages can have versions that don't parse under PEP-440's rules. Some Debian packages include nonsense Python package versions, because it didn't matter at the time. For supported packages, we have corrected this.

In June I spent 0.5 hours on Debian LTS, and none on ELTS.

Updating the distro-info-data database, which turned out to be no update at all. In preparing to announce the end-of-life of Debian 10 LTS, the date shifted a couple of times before ending back where it started.

In April I spent 1.5 hours on Debian LTS and 1.5 hours on Debian ELTS:

Updating the distro-info-data database. This update included the new columns that had previously been stripped out of distro-info-data updates to older releases. That required groundwork in October 2023, updating the older distro-info versions to handle unexpected columns.

In October I spent 10 hours on Debian LTS:

• Investigating the number of packages with invalid PEP-440 versions. These are problematic when using newer setuptools or pip on an older system.

• Updating the distro-info-data database. This was more complex than usual, because the update changed a number of historical dates, breaking the distro-info test-suite.

• Updating distro-info to account for the date changes above, and while we were at it:

  • Generate valid PEP-440 versions for the python module in stable updates.
  • Handle unknown extra columns in the CSV data, allowing us to more easily backport distro-info-data updates in the future.

In October I spent 3 hours on Debian ELTS, on the same distro-info-data and distro-info update tasks.

In April I spent 1 hour on Debian LTS, and 1.5 hours on Debian ELTS, for the same task:

• Updating the distro-info-data database.

My Freexian-sponsored Debian work is now reported on in the Freexian blog:

• January & February
• March

In January I spent 4.5 hours on Debian LTS, resulting in no uploads:

• Work on backporting security fixes to ceph, which I still haven't tested yet, so it hasn't been uploaded.

In January I spent 0 hours on Debian ELTS. I'm cutting my LTS & ELTS hours down to 0, for the next couple of months, as I'm sailing and have more limited time.

During the month, Freexian sponsored 8 hours of 37 I spent on Debian:

• debian.socal infrastructure administration:
  • Handling an outage on matrix.debian.social due to a full disk. This happens somewhat frequently, the database grows fast, we need to implement proper monitoring...
  • Upgraded pleroma on pleroma.debian.social. And then investigated constant performance issues.
  • Escalated a host machine outage to people who had the rights to file issues with the hosting company.
  • Some general cleanup.
  • Upgraded element on element.debian.social.
• debian.net VM creation: botfleet.debian.net, meetbot2.debian.net
• DebConf administration:
  • Helped some minidebconfs to set up websites.
  • Set up an email alias for the treasurer team.
  • Requested write access to debconf.org domains DNS for terceiro.
  • Reviewed and gave feedback on the proposed venue contract for DebConf 23.
• python-team package maintenance: beets, hatch-vcs, hatchling, python-pip, pystemmer, configobj.
• python-team sponsorship: bidict, foolscap, scikit-build, Reviewed twisted security patches for CVE-2022-39348.
• General package maintenance: re2 (which missed the transition window for bookworm), dh-python: 1 + 2, distro-info-data.
• Python 3.11 transition: adonthell, cadabra2 (investigation only), python-cryptography, python-rstr, gavodachs, pytorch (investigation only), setuptools-scm, python3-defaults: 1 + 2, foolscap.
• Implementing PEP-668: python3.11, python-pip, upstream-coordination,
• Bug Triage: reviewed some future design questions about distro-info-data, did a big cleanup of python3-defaults and python3.10 bugs.

A Freexian customer also sponsored some work on Debian packages:

• Python 3.11-transition related uploads: pyobjcryst: 1 + 2, cctbx.
• Unsticking autopkgtests: libobjcryst: 1 + 2, freesas, silx.

In December I spent 2.5 hours on Debian LTS, resulting in no uploads:

• Work on backporting security fixes to ceph, will be uploaded in January.

In December I spent 0 hours on Debian ELTS.

During the month, Freexian sponsored 7.5 hours of 36 I spent on Debian:

• General package maintenance:
  • New releases of pypy3: 7.3.10 and 7.3.11.
  • New releases of hatch-vcs: 0.2.1 and 0.3.0.
  • New release of hatchling: 1.11.1.
  • New release of platformdirs: 2.6.0.
  • New release of pystemmer: 2.2.0.
  • New release of python-authlib: 1.2.0.
  • New release of twine: 4.0.2.
  • New release of python-installer: 0.6.0.
  • New upstream snapshot of configobj: 5.0.6+git20201014.3e2f4cc-1.
  • New upstream release of python-pip: 22.3.1.
  • Land John David Anglin's patch to support hppa (again) in python-cffi.
• Python Team Package sponsorship during the Python Team sprint: python-amply, python-gssapi, python-parameterized, python-schema, python-pkginfo, python-statsd, python-peakutils, python-pyotp, python-exceptiongroup, ×2, python-ssdeep, python-setoptconf. Also reviewed: pygubu, python-freesasa, and python-phonenumbers.
• Python Team Package sponsorship: transmissionrpc, scalene, xdoctest. Also reviewed: kivey.
• Python Team administration, including catching up on a lot of membership requests.
• Python 3.11 support: python-cffi, ponyorm, pytango, boost1.74, i3pystatus, python-boltons, python-limits, python-omegaconf, python-pyramid, cypari2.
• Support Debian's Python package scheme in: pyobjcryst.
• Support setuptools 60 in cctbx.
• Work on dh-python: Supporting --remaining-packages, multiple libraries in a source package, and removing Python 2.7 / PyPy 2.7 support. Landing Antonio Terceiro's changes to add an automatic test runner, pybuild-autopkgtest, and some follow-up patches to it. Supporting data installation in PEP517 builds.

In November I spent 2.5 hours on Debian LTS, resulting in no uploads:

• Investigating erlang (which we eventually decided to backport)
• Investigating fwupd (which turned out to not have the affected code)

In November I spent 0 hours on Debian ELTS.

During the month, Freexian sponsored 16 hours of 80 hours I spent on Debian:

• General package maintenance: wheel, platformdirs, wheel.
• Supporting setuptools >= 60: I went down the rabbit-hole of applying a lot of patches to work-around bug #1025216 - a missing .pth file, before realizing that Debian was missing the .pth file that setuptools used to avoid the problem: python-feather-format, genshi, osc, ofxstatement-plugins, python-pyhcl, rapid-photo-downloader, python-easygui, python-ldap3, python-maxminddb (and migrated nose→pytest), django-js-reverse, python-openflow, pykafka (and migrated nose→pytest), kytos-utils, python-http-parser, python-pyeclib (and migrated nose→pytest), python-av, pylint-celery, python-mbed-host-tests, python-requirements-detector (and migrated nose→pytest), m2crypto (and fixed CVE-2020-25657), deluge, python-preshed, xrstools (investigated but not fixed), python-cbor, python-ssdeep (investigated but not fixed), ddupdate, yaramod, python-grpc-tools, python-mbed-ls, python-peachpy.
• Attending the debconf-video sprint at Jonathan's house. Migrated our YouTube uploader tool to use the loopback OAuth 2 flow. Migrated sreview to bootstrap4 and spent most of the weekend implementing a Vue.js-driven frontend. Including some followup.
• Starting the Python 3.11 transition in python3-defaults: python3-defaults, and some follow-up patches.
• Filing Python 3.11 transition bugs.
• Fixing Python 3.11 related build failures (FTBFS): virt-manager, python-whisper bug #2, temporarily build numpy without inskscape, 2 matplotlib uploads, python-snappy, python-http-parser, sponsored jpy, blist, pybluez, pylibmc, python-coverage, opengv, python-clickhouse-driver, python-libtrace, python3-typed-ast, pythonmagick (investigated but not building yet), python-pyscss (migrated to PCRE2 too), beancount, pycxx, pyliblo, python-cassandra-driver, cython to fix a problem showing up in python-cassandra-driver, python-clevercsv, python-jpype, python-line-profiler (investigated but not building yet), python-cffi (investigated and forwarded, but not fixed yet), objgraph.
• Debugged a regression in sbuild on LXD.
• Uploaded a new PyPy RC to experimental, and reorganized the packaging of headers a bit.
• Work on dh-python: Applied a patch to fix flit buildswith multiple supported python versions. Deprecated the flit plugin in favour of pyproject. Clean up more license files from dist-info directories. Write to debhelper.log files, in overrides, to support --remaining-packages. Rebased the pybuild-autopkgtest branch to prepare to land it. Tested it on several of my packages.
• Attended debconf-team meetings.
• Raising our request for unittest to exit non-zero when there are no tests upstream.

In October I spent 5.5 hours on Debian LTS:

• Issuing a security updates for CVE-2022-37454, a buffer overflow in the reference SHA-3 implementation, XKCP in: pysha3 and python3.7.
• Updating distro-info-data in Debian LTS, to include Ubuntu 23.04, and make other corrections.

In October I spent 2 hours on Debian ELTS:

• Updating distro-info-data in Debian ELTS, which hadn't been updated in a long time.

During the month Freexian sponsored 20 hours of Debian time, which I spent on:

• Winding up DebConf 22 Accounting.
• Helping the DebConf 23 team to get set up their budget.
• Maintenance of dh-python: fixing a bug I introduced in handling dh_python3 -X, handling a wider range of PEP-440 version constraints in environment markers.
• Python Team package maintenance: unidecode, beets, python-discogs-client, git-filter-repo, hatchling, python-distro, lazr.restfulclient, python-launchpadlib.
• Debian Python team sponsorship: pmbootstrap
• Supporting the nodoc and nocheck build profiles in my key packages, to help the release team to reduce the size of the key package set: beautifulsoup4, configobj, dh-python, distro-info, distro-info-data, hatch-vcs, platformidrs, python-cachecontrol, python-cffi, python-flexmock, python-installer, python-launchpadlib, python-mitogen, python-pip, python-virtualenv, python-wadllib, python-webencodings, snowball, wheel.
• Supporting Python 3.11 in key packages where we had noticed problems: python-cffi, python-py, toolz, python-greenlet.
• Updating distro-info-data for the release of Ubuntu 22.10. Including an update for the next Debian stable point release.
• Dealing with CVE-2022-37454 in unstable, by patching pypy3. Patched python-opentimestamps to migrate off pysha3, so it could be removed from the archive, as it's no longer maintained upstream.
• Dealing with CVE-2022-37454 in stable, by patching pypy3 and pysha3.