--- /dev/null
+Title: Free software activity in June 2025
+Slug: activity-2025-06
+Date: 2025-07-01 00:30:51 +01:00
+Category: columbiform
+Tags: activity, columbiform, freexian, planet-debian, planet-ubuntu
+Summary: pterm on Wayland, a groff PDF bug, and a few other odds and ends.
+Mastodon-ID: 114774931332338525
+
+My Debian contributions this month were all
+[sponsored](https://www.freexian.com/about/debian-contributions/) by
+Freexian. This was a very light month; I did a few things that were easy or
+that seemed urgent for the upcoming trixie release, but otherwise most of my
+energy went into
+[Debusine](https://salsa.debian.org/freexian-team/debusine). I'll be giving
+a talk about that at DebConf in a couple of weeks; this is the first DebConf
+I'll have managed to make it to in over a decade, so I'm pretty excited.
+
+You can also support my work directly via
+[Liberapay](https://liberapay.com/cjwatson) or [GitHub
+Sponsors](https://github.com/sponsors/cjwatson).
+
+## PuTTY
+
+After reading a bunch of recent discourse about X11 and Wayland, I decided
+to try switching my laptop (a Framework 13 AMD running Debian trixie with
+GNOME) over to Wayland. I don't remember why it was running X; I think I
+must have either inherited some configuration from my previous laptop (in
+which case it could have been due to anything up to ten years ago or so), or
+else I had some initial problem while setting up my new laptop and failed to
+make a note of it. Anyway, the switch was hardly noticeable, which was
+great.
+
+One problem I did notice is that my preferred terminal emulator, `pterm`,
+crashed after the upgrade. I run a slightly-modified version from git to
+make some small terminal emulation changes that I really must either get
+upstream or work out how to live without one of these days, so it took me a
+while to notice that it only crashed when running from the packaged version,
+because the crash was in code that only runs when `pterm` has a set-id bit.
+I reported this upstream, they [quickly fixed
+it](https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=26a8ef376daf5f50c441a65691b84f87df49db9b),
+and I
+[backported](https://salsa.debian.org/ssh-team/putty/-/commit/14d65a6b00f559295e3174f09e233888da4b125c)
+it to the Debian package.
+
+## groff
+
+[Upstream bug #67169](https://savannah.gnu.org/bugs/index.php?67169)
+reported URLs being dropped from PDF output in some cases. I [investigated
+the history](https://bugs.debian.org/1107068) both upstream and in Debian,
+identified the [correct upstream patch to
+backport](https://cgit.git.savannah.gnu.org/cgit/groff.git/commit/?id=d9e90209725a716dff23807ffffda403c58020c9),
+and uploaded a fix.
+
+## libfido2
+
+I upgraded libfido2 to 1.16.0 in experimental.
+
+## Python team
+
+I upgraded pydantic-extra-types to a new upstream version, and [fixed some
+resulting fallout in
+pendulum](https://salsa.debian.org/python-team/packages/pendulum/-/commit/76ddf2d9a665a57f28867179cad43818545496aa).
+
+I updated python-typing-extensions in bookworm-backports, to help fix
+[python3-tango: python3-pytango from bookworm-backports does not work
+(10.0.2-1~bpo12+1)](https://bugs.debian.org/1107980). I upgraded twisted to
+a new upstream version in experimental.
+
+I fixed or helped to fix a few release-critical bugs:
+
+* [pdfarranger: Fails to start: RuntimeError: context has already been
+ set](https://bugs.debian.org/1107304)
+* [python-covdefaults: FTBFS: E AttributeError: type object 'Plugins' has no
+ attribute 'load\_plugins'](https://bugs.debian.org/1107410)
+* [python-jq: FTBFS: E ValueError: jq: error: syntax error, unexpected
+ INVALID\_CHARACTER](https://bugs.debian.org/1107782)
+* [python-returns: FTBFS: FAILED
+ returns/future.py::returns.future.Future.do](https://bugs.debian.org/1106442)
+ (fixed in python3.13, closed with no action)
~cjwatson / blog.git / commitdiff