Processed sync requests, after verifying that the Ubuntu delta can actually be dropped:
Other sponsored uploads:
Syncs:
Merges:
SRUs:
Unsubscribed:
rls-jj-incoming tag to Bug #530252 “os-prober fails to recognize linux installations wi...” : Bugs : os-prober package : Ubuntu so that Foundations can discuss.Apologies for my late report from Monday.
cpu-checker switch from egrep to grep -E: unsuitable for Ubuntu; rejected with an explanation
os-prober LP: #530252: this looks like a good high quality contribution. Asked the contributor about the use case (this blocks me from reviewing it further), but also asked internally if we can prioritise review of it.
glusterfs fix for difficult-to-reproduce crash. No upstream release yet. Needs more detailed review and involvement of affected user in Test Plan for SRU QA. But already assigned to @bryce by server team triage, so I was going to coordinate with him but I didn’t manage to back to it (see below) and I see that he’s addressed it now. Thanks Bryce!
It turns out that when I enabled support for git-ubuntu MPs I missed MPs targetted to the applied branches. This needs fixing, but the sponsorship queue takes forever to run which hurts development iteration, so I wrote some tests for the already quite testable function that needed amending and verified that the fix made the tests pass. I still need to adjust the codebase to run the tests on “package build”, etc.
I fixed up my previous MP for ubuntu-sponsors-reporter which is another case where items are known to get lost from the sponsorship queue. But fixing it unveiled a rabbithole of a 1 vs. n problem. I’m halfway through resolving this.
I had to move on from the rabbit holes but I think they are important since otherwise we will leave contributors waiting without them realising that their contributions are missing from the queue. I expect I’ll look at them in lieu of my next shift.
LP: #2040483: AppArmor denies crun sending signals to containers (stop, kill). SPent a long time on this one, which packages need rebuilding, and also tested the fix. Turns out it’s a bad upgrade experience, thinking about an SRU, because just updating the package doesn’t reload the apparmor profile, which is embedded in the podman binary. One has to either reboot, or manually unload the containers-default-0.57.4 profile. If unloading, of course that will make all running containers suddenly unconfined, without a way to confine them again because there is no text file for the apparmor profile that could be given to the apparmor_parser tool. I left some suggestions in the bug on how we could perhaps handle an SRU, and sponsored the oracular package. On another note, for some reason I cannot nominate the golang-github-containers-common task for noble, even though it’s published in noble. No idea what is going on, but it’s definitely needed in noble.
Well, that was an interesting shift. I ended up working on sosreport only.
I started looking at the first bug in the queue, which had lots of history and led me to the last bug in the queue 
After working my way through the long history of that, I sponsored it for Oracular, Noble, Mantic, Jammy & Focal, after some tiny fixes.
That finally allowed me to sponsor that tiny sosreport fix for Bionic from the first item, too:
Both sosreport items are now handled and Sponsors unsubscribed.
So long, and thanks to @arif-ali for the IRC assistance!
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.
I continued where @schopin stopped going from old to newer. I reached 2024-06-17. So leaving the green and white entries to the next one.
I continued from where @bdrung stopped, and I was able to do the following: