+1 maintenance report - Week 27, 2025

Pre-Release Discussion +1 Maintenance
1

+1 Maintenance report from 2025-06-30 to 2025-07-04 (2025 week 27)

This week was another +1 shift for me. @ginggs provided me with some topics to work on and that took all my time. Most of the topics I worked on were rabbit holes. The report is short and that makes me feel unproductive (the imposter syndrome kicks in).

Work-needed items

None unless you want to investigate why wp2latex 4.15~ds-1 fails to build on armhf.

Lessons learned

The positive takeaway from this week: Several of the issues that I reported upstream got fixed within hours. So I highly recommend to document the failures and forward them upstream.

Autopkgtest can have artifacts. Look at those when the log output does not give a clue! See my text about the crun package for details.

Full logs

  • python-psutil: Fixed FTBFS on s390x and forwarded this fix upstream. Then noticed it started to fail on ppc64el, because lscpu (from util-linux) is broken on ppc64el. I opened LP: #2115636 and forwarded it to upstream. This got fixed by upstream and I backported the fix.
  • pyopengl: I opened LP :#2115791 for it and decided to skip the failing test in case of the permission error. I forwarded the patch to upstream. Then took my Debian Python team hat to release that patch in 3.1.9+dfsg-2 in Debian (and let this new version autosync).
  • tools-build-clojure: I opened LP: #2115740 for it and forwarded it upstream, because the test did not use the configured proxy (ignored the http_proxy environment variable). Upstream pointed to Maven and told me to configure Maven in a settings.xml config. I tried different alternatives (setting some Maven environment variables), but none of the alternatives worked. So I wrote some shell code for the test to convert http_proxy to $home/.m2/settings.xml. In addition the autopkgtest failed in my schroot environment, because the home directory does not exist there. So I configured a temporary directory as home directory for the test. I forwarded both changes to Debian.
  • crun: I opened LP #2115813 for it. One of the tests failed without logs. I tried to reproduce it locally and failed. Then I looked at the test and saw one return 1 without logs. I added a print command and tried again in a PPA. It failed again without logs. Then I saw that the test stores the log output of the tests in an autopkgtest artifact. That artifact revealed the culprit: Calling crun --version failed. I reported that upstream and it got fixed. So I uploaded the fix to Ubuntu.
  • wp2latex: I reported that 4.15~ds-1 fails to build on armhf. I tried to run the build on my Raspberry Pi Zero 2, but it failed. The board rebooted itself (reproducible). I haven’t looked into the details why (maybe it’s a power supply issue, maybe I should ask @waveform how to troubleshoot that). I forwarded this wp2latex bug to the upstream maintainer via email.