I bluntly went through the queue in chronological order to avoid getting things too stale, only skipping items that were last commented by a potential uploader.
gdb SRU → Approved but not uploaded, I want to check in with our GDB maintainer first.
python3.10 SRU: I felt we still need some test cases in the proposed patch before we move on. Added a comment stating so.
python-oslo.messaging SRU: The proposed changes look good but the version string seems weird to me. Asked the rationale behind that and also proposed a new version string which seems more sensible to me.
jsxgraph FTBFS fix: Disapproved this MP since the bug was fixed by the Debian maintainer and the fixed version was already sync’ed into Ubuntu.
Today I’ve spent my time making the sponsorship report better.
Unfortunately just running the script takes about an hour, so working on it is burdensome. I have multiple branches that are mostly ready but testing and iterating on minor polishing issues is extremely slow. While waiting, I started a performance branch that approximately doubles the report generation speed. But I’m still waiting for it to run to finish testing it!
wsdd: LP: 2071692: the package is currently a sync, and @aleasto has contributions on the Debian packaging side. I asked for more info on the plans with the delta.
LP: #1854588 gdebi-gtk calls pkexec inappropriately: having a hard time reproducing this. Trying out MATE 24.04 to check what the process tree looks like there when gdebi is launched from the browser. Problem reproduced in Mate 24.04 with “setsid gdebi-gtk ”. Built PPA packages for noble and oracular.
Previous comments were addressed. For some reason, despite the user pushing to the correct (AFAICT) remote branch, the MP was not updated. I sponsored using their remote.
On my shift today I continued working on the sponsorship report itself.
It had stopped updating due to an escaping problem. I fixed that as part of the next MP, and @bdrung cherry-picked it so I think that means it should be live already. It’s probably worth the next pilot checking the timestamp on the report though!
I finished a branch and submitted an MP that makes the code more testable, adds tests for a bug that is easy to test for, and fixes the bug. The issue was that git-ubuntu MPs against applied branches weren’t appearing in the report. Thanks again @bdrung for the initial review.
I have one branch remaining, which is the swap to ubuntu-sponsors-reporter to stop MPs from accidentally disappearing from the queue. Unfortunately it requires a one-to-many change that turned into a bit of a rabbithole. I’ll continue on that on my next shift.
https://bugs.launchpad.net/bugs/1980991 - powermgmt-base - link LP bug to debbug, I think this patch is correct but I did have one outstanding question that I wanted resolved due to a mismatch in comments vs logic
