[09:43] <justdan96___> what is the process for getting sponsorship for an SRU? It isn't clear to me what to do next with this: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1995967
[09:43] -ubottu:#ubuntu-devel- Launchpad bug 1995967 in qt6-base (Ubuntu) "[SRU] qt6-base/6.2.4+dfsg-10 to jammy" [Undecided, New]
[10:27] <rbasak> justdan96___: thank you for contributing this.
[10:28] <rbasak> Looks like you've taken the right steps for review - it's in the sponsorship queue.
[10:28] <rbasak> That queue has been languishing but there's a new effort to regularly review that queue that will be starting soon.
[10:28] <rbasak> In the meantime, asking in here is the right thing to do - thanks.
[10:29] <rbasak> On the patch itself, for an SRU the fix needs to be minimal. Could you narrow down the debdiff to change only the bug being fixed please?
[10:30] <rbasak> Please also use the bug that tracks the bug you're fixing, rather than having a separate one.
[10:58] <justdan96___> on narrowing the debdiff - there is one already shared on the original bug report, I can attach that
[10:58] <justdan96___> on the bug report I thought SRUs had to be requested as a separate ticket?
[11:16] <cpaelzer> hi jbicha I'm looking for a component mismatch libsoup3->sysprof
[11:16] <cpaelzer> jbicha: AFAICS you have done all that is needed back in https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=b8f710e7d283a3b9d02641230ee8daf5cf9224ef
[11:16] -ubottu:#ubuntu-devel- Commit b8f710e in ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu "Extra-Exclude: add a bunch more libsoup-3.0-dev rdepends"
[11:16] <cpaelzer> jbicha: but still it is listed in germinate output to be pulled into main this way and thereby shows up in https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[11:17] <cpaelzer> jbicha: do you have any insight from the libsoup3 POV to why this might happen now?
[11:18] <cpaelzer> the only trace I can find is libsoup3 -> auto-promote libsoup-3.0-dev -> depending on libsysprof-4-dev; but since  libsoup-3.0-dev  is listed as extra-exclude I'm puzzled
[11:20] <cpaelzer> germinate lists libedataserver1.2-dev to be the one pulling in libsoup-3.0-dev, but you have added that in extra exclude as well
[11:27] <jbicha> cpaelzer: https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html lists what's pulling in libsoup-3.0-dev, we just have to add that to the excludes too
[11:29] <cpaelzer> jbicha: ack, do you want to or should I?
[11:30] <jbicha> cpaelzer: I can work on it. I need to add gupnp and rygel to the excludes too
[11:30] <cpaelzer> yeah then one commit from you including all of them is better
[11:30] <cpaelzer> thanks jbicha!
[12:41] <rbasak> justdan96___: no - see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure "Do not create a meta-bug"
[12:41] <rbasak> We use one bug to track each root cause, with separate bug tasks within that bug to track the status in different places (eg. different Ubuntu releases).
[12:47] <justdan96___> rbasak: okay - so I should copy everything to the existing bug report? There is already an SRU in the comments of that report
[12:51] <rbasak> justdan96___: I don't want to require busywork for the sake of it. Maybe just mark the dupe, make sure the SRU information is present in the existing bug, and add a comment to clarify anything as needed?
[14:13] <ahasenack> +1 maintenance: I'm working on the libuhd4.2.0 NBS
[14:24] <rbasak> Is kinetic-proposed not cleaned out yet post-release?
[14:32] <enr0n> Can a core dev please retry these autopkgtests? retry-autopkgtest-regressions --blocks openssh -s lunar | grep -v xen-tools
[14:44] <ahasenack> +1 maintenance: now working on the librcutils0d NBS
[20:06] <mwhudson> vorlon: thanks for merging https://code.launchpad.net/~mwhudson/ubuntu-cdimage/reuse-livefs/+merge/423321, a change i have absolutely no recollection of submitting!
[20:06] <vorlon> mwhudson: you're welcome ;)
[20:06] <mwhudson> also ubuntu-cdimage in git sounds like a very good thing
[21:23] <tsimonq2> 🎉🎉🎉🎉