Patch Pilot Hand-off 26.10

Notes from my sponsoring shift done this week. It was also the opportunity to experiment with a bot I’m working on to help doing a first automated review of sponsoring requests (in case you saw some activity from ubuntu-sponsoring-bot account, I plan to do a discourse post next week about it)

libinput fix + R/N SRU

Security update for stable serie but no fix proposed for stonking, requested for that to be addressed first

launchpad git failed to produce a diff but also seems to target the wrong branch, asked to fix that

SRU for jammy but doesn’t state if it’s fixed in newer series and the description isn’t SRU compliant, asked for those points to be addressed

sponsored

https://code.launchpad.net/~blkerby/ubuntu/+source/ipmiutil/+git/ipmiutil/+merge/508280
asked to fix the changelog version used for the update
got fixed, sponsored

sponsored

asked for the SRU to be rebased on the recent security update

uploaded

https://code.launchpad.net/~karljs/ubuntu/+source/abseil/+git/abseil/+merge/508288
uploaded

https://code.launchpad.net/~zineb/ubuntu/+source/speech-dispatcher/+git/speech-dispatcher/+merge/507552
uploaded

closed, the change was sponsored but the sponsor edited the debian/changelog description before upload while not updating the Vcs so git-ubuntu didn’t autoclose the MP

https://code.launchpad.net/~ravi-sharma/ubuntu/+source/wvstreams/+git/wvstreams/+merge/506345
uploaded

fixed in stonking, targetting resolute but no MP/patch so unsubscribed sponsors asked to subscribe them again once their is something to review

https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2150285
uploaded (stonking and resolute

https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2152688
was already uploaded, unsubscribed sponsors

was already uploaded, unsubscribed sponsors

https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2154708
unsubscribed, there is nothing left to sponsor and the changes have been reviewed in attached MPs already

marking as merged, those were uploaded but with other changes and such the commits didn’t match what was proposed and such launchpad didn’t mark them as merged

https://code.launchpad.net/~simpoir/ubuntu/+source/tiff/+git/tiff/+merge/505408
uploaded

https://bugs.launchpad.net/ubuntu/+bug/2154549
uploaded

1 Like

Sponsored and reviewed specific requests on the ubuntu-devel matrix today, including

Sponsor:

Review:

Unsubscribe sponsors:

Although the sponsoring report is a week old or so, I could help here and there with:

Sponsored

Provided feedback

2026-08-18:

2026-08-19:

2026-08-20:

August 28th 2026:

reviewed + sponsored

reviewed + provided feedback

  • LP: #2151177 (renesas-iot-defaults): Needs packaging, interesting, not looked at as I could see. I asked for some more info in the bug itself, and warned about FF and the need for some AA pinging if this should still go to Stonking (as stated in the bug).

  • LP: #2161172 (flrig): has two MPs open linked:

    • MP 508661 (stonking)
      The fix is released upstream, and Debian is several versions behind, but not affected by the bug (gcc15 magic, LTO). I asked about the possibility to work on pushing the new version to Debian instead, to avoid delta on a previously untouched universe package.
    • MP 508661 (resolute SRU)
      For a SRU, we would need a better test plan in the bug and/or some justification on why the (minimal) change should have little impact or regression potential.
  • LP: #2160023 (base-files): Fixed in devel, being SRUed to Resolute. As the bad behavior was introduced in Kinetic, I asked why the SRU points only to Resolute. The bug states it’s intended for the point release, which at this point (heh) is pretty much closed.

reviewed + commented

  • MP 509081 (landscape-client): MP for an SRU to Noble, but the patch, accepted upstream, is not even in Stonking yet. Suggested pinging Lanscape people for planning the backport properly.

queue cleanup

Reviewed and added notes:

Approved/Sponsored:

Review:

Sponsor:

Pinged author: