Patch Pilot Hand-off 24.04

  • LP: #1508290 - uploaded with block-proposed-jammy
  • LP: #2043494 - processed sync request
  • LP: #1097467 - uploaded, thanks @waveform80 for the attention on bugs that have been open for a very long time. (this also cleans up LP: #589496 !)
  • LP: #2036873 - reviewed, nearly convinced, start discussion on plan for the test suite

Nothing to report from IRC

1 Like
  • alacarte LP: #2037326 fix was auto-sync’d from Debian, asked in the bug about SRUs, unsubscribed Ubuntu Sponsors
  • evince LP: #1794064 reviewed and sponsored SRU for Jammy
  • gdb LP: #2040113 reviewed and sponsored SRU for Lunar

The request for the gdb SRU came from irc. There was another request just after I ended my shift for an openssl SRU, but it needs more than just a quick look.

1 Like

Notable achievements

  • MP #455564 and MP #455517: apache2 MPs for @mdzurick. Left comments asking for improvements.

  • Bug #1991909: the user addressed the comments made by @paride, so I uploaded the package and staged the SRU as per @ahasenack’s instructions.

  • MP #455006: curl merge from @danilogondolfo. Left minor comments asking for improvements. He addressed them, and I uploaded the package.

  • MP #454972: netcat-openbsd merge from @danilogondolfo. Left a question. Also explained more about how dpkg-buildpackage scans changelog entries to automatically close bugs.

  • Bug #2008594: getmail6 fix. Uploaded after doing a small adjustment to the provided debdiff.

  • Bug #2038834: fix for mesa. The Noble upload was done, but there’s no debdiff for Mantic. I left a comment asking for it.

General comments

  • I think we should unsubscribe ~ubuntu-sponsors from bugs whose debdiffs/packages have been uploaded. If there are any subsequent problems with the upload, the reporter can always flag us again. I had a brief conversation with @tsimonq2 and @ahasenack on IRC about it.
1 Like
  • #2026589: left a comment asking how this is supposed to be tested, with a suggestion.
  • #2039280: no update since my last shift on Oct 27th, unsubscribing sponsors.
  • #2039429: stuck in noble migration, due to armhf dep8 infrastructure problems. Since I sponsored this upload, I’ll keep an eye on it. For now, unsubscribing sponsors from the bug, as there is nothing else to sponsor here.
  • #1973084: got confirmation the ppa fixes the problem for some user(s). I prepared the SRU template and sponsored the uploads.
  • #2042059, #2042094: unsubscribed sponsors, as it was uploaded already
  • #2042394: marked as incomplete, added other ubuntu release tasks. Patch is just for jammy, others needed.
  • #2029930: wget crash when calculated download speeds are in the Tb/s range. Prepared a ppa, asked for confirmation on the fix for noble at least, and help with coming up with a test scenario for a possible SRU.
1 Like

I’ve been casually taking care of one or two a day. I haven’t been posting here because I don’t want to fill up the thread with my one or two each time, but feel free to mention me. :slight_smile:

Today I did these two:

I think, intuitively I take the LIFO approach to the queue, but in reality it should be FIFO. Would be nice to see some of those older items gone. :slight_smile:

  • LP: #2026589; left a comment requesting the updated test case first referenced by @ahasenack and unsubscribed ubuntu-sponsors until this is addressed
  • Reviewed the status of nemos-dev-key, optee-os-s32, u-boot-s32, and arm-trusted-firmware-s32
  • With nemos-dev-key now sponsored thanks to @tsimonq2 (LP: #2043448), optee-os-s32 was ready to go (LP: #2034648) so I sponsored that with minor changes
  • Reviewed u-boot-s32 (LP: #2034650) but I need to compare it to a fresh build of u-boot under noble and I’m now getting yet-another FTBFS due to cross-build compiler flags on that. I’ll dig into it again tomorrow, but ultimately I’m aiming to deal with this and the remaining -s32 packages.

I did more than my usual “one or two” packages today, so here’s a post.

According to the KPI metrics, the sponsorship queue was at 33, 24 hours ago. Right now, it sits at 24. Here are the uploads I personally did today:

  • Looks like kernelshark was accepted. Thanks for your help, @tjaalton!
  • Sponsored redshift-qt to both Debian and Ubuntu NEW queues for @arraybolt3. With my Lubuntu hat on, it’s a feature goal for 24.04 LTS and has a straightforward license, so it should be a pretty simple review.
  • Sponsored cryptsetup for @mkukri. We’re both going to keep a close eye on Britney, so we can address any potential issues with autopkgtests.
  • Some NemOS packages (I think all of these are?), which are:
  • openjdk was sponsored as well, I expressed concerns with the nearly 50 Lintian warnings, @vpa19771 promised me he’d look into them before the release. Not very happy about sponsoring a package that looks like that, but I’ll give them the benefit of the doubt on this one.

Other extremely important notes:

  • [19:28] (@eeickmeyer) kernelshark do do do do do do :shark:
  • Re: [Merge] ~mkukri/ubuntu/+source/cryptsetup:merge into ubuntu/+source/cryptsetup:debian/sid
    • Review: Approve
           / .--. \
          / /    \ \
          | |    | |
          | |.-""-.|
        ||| ::/  \:: ;
        ||; ::\__/:: ;
         \\\ '::::' /

Remember, community members can patch pilot too. If you’re in ~ubuntu-dev, take a seat in the cockpit! :airplane:

I’d also like to highlight @bdrung’s starter work on an ubuntu-sponsoring package, with some additional refinements to the code. I think the original package looks promising, but if anyone (~ubuntu-dev or not) is looking for some low-hanging fruit, I’m sure he’d appreciate the help with test cases, splitting data collection and rendering, etc.



I will say my singing was on-point.

1 Like
  • LP: #2007702: asked the reporter to fix the version numbers for the SRU candidates and pointed to the SRU policy.

  • LP: #2041171: removed ubuntu-sponsors, patch already uploaded.

  • LP: #2042902: asked the reporter to fix the version number for the mantic SRU candidates, pointed to the SRU policy, and asked them to adjust the trackers for each series.

  • LP: #2042902:

    • Continuation of the work of @paride 10 days ago and @athos-ribeiro 1 day ago.
    • I got an IRC ping as well even before finding it in the queue
    • Playing this as “please do X” ping pong would not complete anytime soon, but sadly the requester was not available for direct discussion. So as fallback I provided a case study and reasoning/material to study how it should be done to learn from.
    • uploaded to noble, once good there and updates to the SRU uploads have been made it can be sponsored there
  • Ping about zlib sponsoring: I didn’t have time to do all of it, but at least was able to spot and suggest some organizational details in the changelog that should help to not be in the way when the next sponsor comes by


I had the opportunity to do a little piloting today. Here are a few notes…


Workflow Notes

  • Protip for sponsors: if you find yourself manually specifying -k, just set DEBSIGN_KEYID=<YOUR_KEYID_HERE> in ~/.devscripts - this will pick up your key every time.
  • Differences in quilt configuration usually are not blockers for sponsorship (in my opinion,) unless those differences result in incompatible patches. When sponsoring khmer for @ogayot, I noticed some differences. Given some further followup, I use some sane defaults from a guide, which removes that Index header. /etc/quilt.quiltrc has the default quiltrc, which enables the header and differences in the config. We should consider whether changing the defaults, or noting in the packaging guide, might be a good idea. Less diff lines are Usually better.
  • Canonical employees should note that sometimes, when using their email address, it creates a ghost Launchpad account. That karma belongs to you! Here’s an example that I discussed with @adrien today.

General Notes

  • Remember, community members can patch pilot too! If you’re in ~ubuntu-dev, take a seat in the cockpit! :airplane:
  • I’m seeing a lot of kernel-related and security-related sponsorship queue items. For example, four of the oldest items in the queue are security updates, and many of the newer items are kernel-related patches. Like some others, I tend to not mess with anything tangential to the kernel, and I don’t have the permissions to upload to the security pocket (despite being a proud member of MOTU SWAT.) If we could get representatives from both teams to knock out these items before the holidays, I’d greatly appreciate it. Past people I’ve pinged include @xnox and @alexmurray - perhaps either of you would be able to point us in the right direction.

“Extremely Important” Notes

1 Like

The sponsor queue report that the Patch Pilot team uses is the general report that excludes security and kernel uploads.


Makes sense, I didn’t notice that. Thanks.

That being said, KPI shows all items, and IMO the point still stands: red items should get appropriate attention.

1 Like

Well, we can fix the KPI to track the thing we’re actually trying to drive to zero!

The other items should get attention, yes. But kernel patches in particular are not really an Ubuntu community thing.


Let’s do it! :smile:

A quick point of clarification: there’s a difference, in this case, between kernel packages and kernel-adjacent packages. The former, yeah, not touching with a 10-foot pole, let Canonical Kernel take care of that. The latter gets more fuzzy, because that covers e.g. DKMS-related packages that I’d rather not touch, but don’t fall into the direct “jurisdiction” of Canonical Kernel.

Those packages will still show up, and are still on the general report, but are not something most sponsors feel comfortable touching. We should think about either asking someone from Canonical Kernel to rotate and take care of these, and/or ask skilled/willing individuals from Foundations/another team to do the same.

1 Like

My shift today was affected by multiple conflicting meetings and interruptions. So I couldn’t get lots of stuff done.

1 Like

Notable Achievements:

  • LP: 2045000 - sponsored
  • LP: 2044852 - Gave some recommendations and created a PPA to confirm the patch works

Important Context

Excited to be able to help a bit more with patch pilot now that I’m a core dev :smiley:

1 Like

In between meetings, I did some archaeology for the zeitgeist merge, and looked at the libgcrypt20 SRU.

Since the current queue is mostly made out of Canonical contributions, I’d like future shifts to prioritize the zeitgeist merge if possible as it is a pure community contribution.

1 Like

This shift was my first patch pilot shift were I got pinged on #ubuntu-devel. It look like the patch pilot program takes off!

IRC discussions