Hello fellow Patch Pilots and Ubuntu community members,
This post serves as the official hand-off for the Patch Pilot Program for the 25.04 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)
MP for #2073552: previous review comments unanswered, while oracular was in freeze. I suggested to change the upload to plucky now, and added oracular and plucky tasks to the bug which were missing, but it’s up to the author to state intentions in the MP now.
LP: #2076084: software-properties. Created an oracular branch off of 0.102, pushed that branch to upstream. Then I committed a d/changelog change to change oracular into plucky, tagged that as 0.103, and pushed to ubuntu/master. Sponsored 0.103 for plucky, left instructions on what’s left to proceed with an oracular SRU if wanted.
MP for #2069953: pinged asking if the submitter had a chance to examine the feedback provided so far.
MP for #2083458: add apparmor for linuxptp (a requirement for the filed MIR). This is a plucky MP now
LP: #2078638: coredumps with Xymon on 24.04: has a report that the fix is good. I also checked upstream looking for movement there, but there is nothing recent in the SVN repository. Debian has applied the fix in salsa already, so Plucky should get it as soon as it opens, and debian does an upload. I added a comment explaining the sru process and what we would need for that, and also asked the debian maintainer if he is going to do an upload soon. We can sponsor this for plucky, but if there will be a debian upload soon, then we would just be adding a delta for nothing. There is a timing point here: it’s a crash in noble, and we should fix that quickly, and not wait for a fix in plucky.
LP: #2083051: nose, git-buildpackage FTBFS: nose is fixed, and git-buildpackage now builds fine, with the nose fix, but will fail to build if a version suffix like “ubuntuN” is added to it. The patch added in the bug copes with that, but not if the suffix is different, like “buildN”, so I think it needs improving. I left a comment there as such, and marked the bug incomplete, pending a better patch.
sponsored shotwell for LP: #2084777. This was actually the newest request in the sponsorship queue, but it had by far the longest bug title making the sponsorship report table not fit in my browser, annoying me enough to take it first so that a regenerated report would be more readable.
libseccomp: requested changes to the SRU patch on LP: #2059734 and unsubscribed sponsors for now.
linuxptp and ntpsec PRs back to work in progress, pending internal team discussion. These won’t show up in the sponsoring report from now on, until they are ready again.
LP: #1980991: veeery long bug to go through, over 40 comments. I think there is a non-trivial amount of risk to get this wrong in stable releases. I left a question whether we shouldn’t switch to systemd-ac-power instead, which at least is an active upstream.
LP: #2084405: was sponsored already, so I unsubscribed sponsors.
LP: #2084059: similarly, unsubscribed sponsors because the package was uploaded already
A rather unproductive shift as half of it was filled with meetings. Still:
LP: #2040027 – openblas – Reviewed status; already sponsored so unsub’d ubuntu-sponsors and added advice about SRU template
LP: #2084776 – pwl-pc-services – Reviewed status; @vpa1977 provided review, points raised were addressed, provided second review, but one point still needs addressing
libgrokj2k merge – Reviewed status; left query about right way forward
libgrokj2k MP: rejected, in favor of a new upload from Debian if it ever happens.
LP: #2086110: console-setup setupcon logic error. Good patch, real code problem, sponsored. Left a comment with hints on how to continue with the SRU process, if so desired.
LP: #1047018: has an MP up for review, naming JulianK specifically. I pinged him on IRC.
LP: #2062118: fixed in plucky via a sync from debian. I marked the linked MP as merged, and closed the bug (it wasn’t autoclosed by the sync).
LP: #2089933maven-plugin-tools ftbfs. I left syntax comments in the MP, asking for DEP3 headers to be added and perhaps suggesting this to debian (even if the bug states that debian is unaffected), but am abstaining from reviewing the actual fix because I’m not familiar with the java ecosystem.
ntpsec armhf FTBFS MP: checked upstream, debian, and left a comment in the launchpad MP.
needrestart merge: since this was filed, debian uploaded a new version, so this MP needs rebasing.
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.
