I was on my seventh +1 maintenance shift last week (starting 24 March, 2025). This week was the beta release week. My shift was not as productive as I would have wanted it to be.
I posted a version of this report on discourse [0] last Friday. Sincere apologies for the delay posting it here, on the ubuntu-devel mailing list.
I spent some time on the cluster of documentation-related Python packages which fail to build from source. Initially, things seemed like a build-dependency rabbit hole. Thanks to a suggestion from ginggs, I eventually focused on getting this cluster built in a PPA [1]. We can have these nine packages migrated iff:
1. The mkdocs-get-deps package which is currently in the NEW queue is accepted into the archive
2. A build-dep cycle between mkdocstring and mkdocstring-python-handler is broken by temporarily disabling and re-enabling build-time tests (I used nocheck).
3. A build-dep cycle between mkdocstring + mkdocstring-python-handler and python-mkdocs is broken by temporarily removing doc-related build-deps from the latter.
(Update: schopin just replied on the discourse post that mkdocs-get-deps is accepted)
I also picked up the maven-plugin-tools related FTBFSs [2], I investigated from the point I had left during a previous +1 shift. A new package - munge-maven-plugin [3] - is the latest one to get affected. After a short discussion with vpa1977, I decided to go with the currently proposed solution. I addressed old review comments on the MP [4] and cleaned it up. I also created a Debian bug report [5] and proposed the same patch in Debian [6].
Apart from the two clusters above, I looked into a few minor FTBFS issues.
- linuxcnc [7] - thanks liushuyu-011 for sponsoring
- uvtool [8] - thanks liushuyu-011 for sponsoring
- grubzfs-tests - thanks to ginngs for the heads-up about the removal of this package while I was ignorantly investigating its FTBFS
Regards,
Pushkar
[0] https://discourse.ubuntu.com/t/1-maintenance-report-week-12-2025/58071
[1] https://launchpad.net/~pushkarnk/+archive/ubuntu/python-test-ppa-2
[2] https://bugs.launchpad.net/ubuntu/+source/antlr-maven-plugin/+bug/2089933
[3] https://launchpadlibrarian.net/783356930/buildlog_ubuntu-plucky-amd64.munge-maven-plugin_1.0-3_BUILDING.txt.gz
[4] https://code.launchpad.net/~pushkarnk/ubuntu/+source/maven-plugin-tools/+git/maven-plugin-tools/+merge/477551
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101824
[6] https://salsa.debian.org/java-team/maven-plugin-tools/-/merge_requests/1
[7] https://bugs.launchpad.net/ubuntu/+source/linuxcnc/+bug/2104012
[8] https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2104381
I spent some time on the cluster of documentation-related Python packages which fail to build from source. Initially, things seemed like a build-dependency rabbit hole. Thanks to a suggestion from ginggs, I eventually focused on getting this cluster built in a PPA [1]. We can have these nine packages migrated iff:
1. The mkdocs-get-deps package which is currently in the NEW queue is accepted into the archive
2. A build-dep cycle between mkdocstring and mkdocstring-python-handler is broken by temporarily disabling and re-enabling build-time tests (I used nocheck).
3. A build-dep cycle between mkdocstring + mkdocstring-python-handler and python-mkdocs is broken by temporarily removing doc-related build-deps from the latter.
(Update: schopin just replied on the discourse post that mkdocs-get-deps is accepted)
I also picked up the maven-plugin-tools related FTBFSs [2], I investigated from the point I had left during a previous +1 shift. A new package - munge-maven-plugin [3] - is the latest one to get affected. After a short discussion with vpa1977, I decided to go with the currently proposed solution. I addressed old review comments on the MP [4] and cleaned it up. I also created a Debian bug report [5] and proposed the same patch in Debian [6].
Apart from the two clusters above, I looked into a few minor FTBFS issues.
- linuxcnc [7] - thanks liushuyu-011 for sponsoring
- uvtool [8] - thanks liushuyu-011 for sponsoring
- grubzfs-tests - thanks to ginngs for the heads-up about the removal of this package while I was ignorantly investigating its FTBFS
Regards,
Pushkar
[0] https://discourse.ubuntu.com/t/1-maintenance-report-week-12-2025/58071
[1] https://launchpad.net/~pushkarnk/+archive/ubuntu/python-test-ppa-2
[2] https://bugs.launchpad.net/ubuntu/+source/antlr-maven-plugin/+bug/2089933
[3] https://launchpadlibrarian.net/783356930/buildlog_ubuntu-plucky-amd64.munge-maven-plugin_1.0-3_BUILDING.txt.gz
[4] https://code.launchpad.net/~pushkarnk/ubuntu/+source/maven-plugin-tools/+git/maven-plugin-tools/+merge/477551
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101824
[6] https://salsa.debian.org/java-team/maven-plugin-tools/-/merge_requests/1
[7] https://bugs.launchpad.net/ubuntu/+source/linuxcnc/+bug/2104012
[8] https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2104381
