Hello fellow Patch Pilots and Ubuntu community members,
This post serves as the official hand-off for the Patch Pilot Program for the 25.10 cycle. The purpose of this thread is to ensure continuity in our program, keeping operations smooth and contributors supported. Whether you’ve just wrapped up a piloting session or are gearing up for your session, this space ensures that no detail gets lost in the shuffle. If you are interested in what is going on, you can subscribe to this post.
Please reserve responses in this thread ONLY to hand-off reports. If you have a question as a contributor please check with the current patch pilot. If you need a clarification from the last pilot please reach out to them separately. If you have a more general question please create a new topic in this category.
To the incoming pilot: please take a moment to review the updates from the previous session. It provides the context you’ll need to pick up where they left off. When writing your own report, please include the following headlines:
- Notable Achievements
- Important Context
- Notable Contributors (tag them if you know their discourse username)
- Program Improvements (anything that you think needs documenting or otherwise improving)
Links: Latest hand-off post | Previous cycle hand-off
1 Like
Review:
Added comment:
Unsubscribed sponsors:
Submitter needs to raise the SRU:
Should be reviewed by the maintainer:
Sponsored:
I’m skipping sponsorships or reviews of the SRU type, since that would mean I should abstain from doing the SRU review later on.
I started with 57 items and went down to 40 minus I think 3 or so pending so we should come out at 37. Given the sheer number of items I was unable to effectively take notes. The important bits are:
- I disapproved all outstanding landscape-client SRU merges as they were conflicting and the current SRU is in disarray
- I incompleted basically all SRUs that claimed to be HWE:
- Sponsored opensnitch, wasmedge, and plocate
To maintain efficiency I skipped over non-merges of new upstream versions as trying to find the tarball and validating those can be time consuming.
LP: #2110421 - Reviewed and sponsored
MP: #487210 - Reviewed and sponsored
LP: #2112053 - Ran PPA autopkgtests and started looking over it. As far as I’ve seen it looks good but I ran out of time to review manpage and other diff updates
Many of the items in the sponsorship queue are related to SRUs. I skip those, because otherwise I won’t be able to do the SRU processing (conflict of interest). The remaining ones are:
- resource agents merge: preemptively approved, pending autopkgtests results
- azure-proxy-agent PR: marked as merged, as it was sponsored already, and is even in the archive by now.
- LP: #2112632: efibootmgr: looks like a valid bug, based on my testing. I marked the affected ubuntu releases, found an upstream patch, asked if the user would like to prepare a PR with the upstream patch instead and that I would guide them if needed. I subscribed to the bug so I can get notified of a response.
- PAM merge from debian: I just started looking when I noticed that there was a reviewer assigned already. In any case, just left a comment saying that it needs to be rebased on top of a security update.
- LP: #2114945: interesting discussion about automounting different types of filesystems and the security implications. I learned that we already don’t automount certain filesystems via a set of udev rules. Left a command there asking for next steps, since the original diff (for kmod) is probably being abandoned.
- LP: #2115041: hard to understand SRU template. I left a question, and also commented that the status of the bug for oracular, plucky, and questing, needs to be clear and set before the SRU for noble can continue.
- LP: #2114778: I have no idea what “Patched AdwSpinner to Match yaru.dart’s YaruCircularProgressIndicator Design and Animation” means, sorry. So I just did a syntax-based review, and added a review slot for ubuntu-desktop.
- LP: #2109673: sssd and apparmor profile. I did some tests, and I’m wondering if we shouldn’t take the opportunity to create a better profile for sssd overall, one that uses child profiles as well. This is a complex piece of software, and won’t be easy, but could be a good goal for the next LTS, and we have one interim release to stabilize it. Also, given that this profile is not installed in enforce mode by default, I question the need to SRU this. I think we should first get it right in questing and later, so that it can be used in enforce mode.
- debmirror merge from debian: reviewed, left a comment and a +1.