Hi, this is a cross-post from: https://discourse.ubuntu.com/t/1-maintenance-report-week-27-2025/63944 You can read it there or here. The report is written in Markdown. I just added some newlines to make it a bit easier to read in plain text.
# +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](https://bugs.launchpad.net/ubuntu/+source/wp2latex/+bug/2115809). ## 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](https://github.com/giampaolo/psutil/pull/2595). Then noticed it started to fail on ppc64el, because lscpu (from **util-linux**) is broken on ppc64el. I opened [LP: #2115636](https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2115636 ) and forwarded it to upstream. This got fixed by upstream and I backported the fix. * **pyopengl**: I opened [LP :#2115791](https://bugs.launchpad.net/ubuntu/+source/pyopengl/+bug/2115791 ) for it and decided to skip the failing test in case of the permission error. I [forwarded the patch to upstream](https://github.com/mcfletch/pyopengl/pull/153). 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] (https://bugs.launchpad.net/ubuntu/+source/tools-build-clojure/+bug/2115740) for it and [forwarded it upstream] (https://ask.clojure.org/index.php/14602/tools-build-fails-with-httpproxy-httpsproxy-set), 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] (https://salsa.debian.org/clojure-team/tools-build-clojure/-/merge_requests/1). * **crun**: I opened [LP #2115813](https://bugs.launchpad.net/ubuntu/+source/crun/+bug/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](https://github.com/containers/crun/issues/1816) and it got fixed. So I uploaded the fix to Ubuntu. * **wp2latex**: I reported that [4.15~ds-1 fails to build on armhf](https://bugs.launchpad.net/ubuntu/+source/wp2latex/+bug/2115809). 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. -- Benjamin Drung Debian & Ubuntu Developer -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
