The queue was unusually empty, so I spent my time moving the needle on the only actionable item there, a dracut bug, doing some digging in kernel doc and code to leave a review on the patch itself.
I didn’t upload the patch, preferring to ping @bdrung as our resident dracut expert.
LP git and some other Ubuntu sites are experiencing an outage at the moment.
LP: #2099668: cockpit backport request. It’s the first time I look at a backport, so I spent some time reading UbuntuBackports from the Ubuntu wiki, and added a comment to the bug with a suggestion on how to proceed.
LP: #2083908: another backport request: pymodbus. Since it was removed from noble due to autopkgtest failures (a debian bug was linked in the removal comment: #1061817), I asked for evidence that the backported version works in noble.
This dkms build failure was a bit harder to reproduce/verify than your common FTBFS. Reviewed and sponsored ipu6-drivers and ipu7-drivers into plucky-proposed.
LP: #2099785: mariadb CVE fixes. Otto is working on them, and Eduardo B. from security is reviewing.
rsyslog plucky MP: I asked for pointers to when the bug was introduced, and what it actually changes in the log messages, because we are now in feature freeze. I also asked to rebase the PR because it was branched off of something that is not rsyslog in our git.
LP: #2083481: nothing left to sponsor, unsubscribed ubuntu-sponsors.
landscape-client PR: fixing LP: #2031036 and LP: #2099283. I asked for a simple d/changelog fix, but had a bigger question about one of the patches. Also, bug LP: #2099283 is incomplete wrt ubuntu tasks, left a question there.
LP: #2083908: pymodbus backport to noble request. All seems fine now, and I left a comment to that note. Frank H. offered to sponsor. But now I’m also wondering if we wouldn’t be better off to actually SRU that package back into noble.