[00:04] <mapreri> teward: it's *one* spam email?  No need to be so triggered :)
[00:05] <mapreri> the only criteria mailman uses to identify poster is the From address, which as you surely know is easily forged…
[00:05] <teward> mapreri: masquerading as the list itself to bypass the moderation
[00:05] <teward> so ye a little concerned
[00:06] <mapreri> and since before my time as list admin there is a whitelist for '^(.*)ubuntu.com' ; I'll add a @ so that particular address is not allowed anymore
[00:06] <mapreri> normally the list address itself is not special cased in any way for mailman, it's an address like any other
[00:07] <teward> ah.  well i am gonna go take a nap - my "too awakeness" has worn off and i need a nap
[00:07] <mapreri> what annoys me the most is that removing mails from the mailman archive is a PITA, I don't know if IS wants to do that…
[00:10] <arraybolt3> bdmurray: I noticed that the Ubuntu Studio Kinetic broadcom driver bug got marked Fix Committed (back from Fix Released), and that the version of the package where the bug was fixed is somehow in -proposed. I thought certainly it had migrated to -release. Did something happen that somehow kicked it out of -release and back into -proposed?
[00:10] <arraybolt3> https://launchpad.net/ubuntu/+source/software-properties/0.99.27.1
[00:10] <arraybolt3> Er... no, wrong link
[00:10] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370
[00:10] <arraybolt3> ^ right link
[00:10] -ubottu:#ubuntu-devel- Launchpad bug 1993370 in software-properties (Ubuntu) "Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic" [High, Fix Committed]
[00:12] <bdmurray> The bug bot marked it as Fix Released although it really made it into Lunar around the time of archive opening
[00:12] <arraybolt3> Oh, I get it. OK, I guess I'll verify it.
[00:31] <vpa1977> Hi, would it be possible to retry a couple of regressions for java-common, it is failing on old version of pgpainless and we have a newer version in lunar that does not fail: https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=pgpainless&trigger=java-common%2F0.74
[00:31] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=pgpainless&trigger=java-common%2F0.74
[00:32] <vpa1977> Thanks!!!!
[00:42] <MacSlow> bbl
[02:55] <MarkPruett91> Do you need sponsorship for a SRU? Or do I simply open a bug report with the diff file on the package I'm patching?
[11:05] <nteodosio> tsimonq2, added the diff for Lunar for bug 1993191 if you would like to sponsor it. (:
[11:05] -ubottu:#ubuntu-devel- Bug 1993191 in chromium-browser (Ubuntu Kinetic) "apport hook that collects snap's information is outdated" [Medium, In Progress] https://launchpad.net/bugs/1993191
[15:02] <tsimonq2> nteodosio: Hey! Sure, I'd be happy to sponsor a Lunar diff for you :) I'm also seeing diffs for a couple of stable releases, if you fill out the bug description to match the SRU guidelines I can review/sponsor those as well!
[15:04] <mdeslaur> Skuggen: good morning! Any news on a fix for the issue? There are more details in the bug
[15:04] <tsimonq2> In other news, the sponsorship queue is now back down to August 2022 levels. Should be slightly less daunting for other patch pilots ;)
[15:05] <nteodosio> tsimonq2, thank you! I've already updated the description to the SRU shape.
[15:05] <tsimonq2> rbasak: OOC, does the sponsorship report still run on a 12.04 server? Are there any plans to upgrade that any time soon?
[15:06] <tsimonq2> nteodosio: Sweet, I'll look in a few, thanks!
[15:22] <rbasak> tsimonq2: I'm not sure, but someone has to test ESM :-)
[15:27] <tsimonq2> Fair enough, I guess :)
[15:54] <Skuggen> mdeslaur: No, sorry. The initial fix was quick because it was easy to identify with the error message. I didn't see the added comments, though, so that might help
[16:01] <mdeslaur> Skuggen: ok, this is a pretty serious regression for users, could you please let me know if there is any progress?
[16:18] <Skuggen> Yeah, will do
[16:26] <mdeslaur> Skuggen: thanks!
[18:49] <ogayot> Can somebody trigger this autopkgtest for me please? I'd appreciate it!
[18:49] <ogayot> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=ubiquity&ppa=ogayot/lunar-proposed&trigger=ubiquity/23.04.3%7Eppa1
[19:13] <MacSlow> Greetings everybody!
[19:16] <sarnold> wb
[19:17] <MacSlow> hey sarnold
[19:18] <dbungert> ogayot: clicked
[19:18] <ogayot> dbungert: thank you!
[19:33] <MacSlow> anyone present who has an all-amd laptop with working amd-sfh-hid (gyro/accelerometer)?
[20:05] <blackboxsw> seb128: it looks like update-manager SRU upload got accepted into -proposed a few minutes ago related https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1990450.  I heard this may be priority but it loooks like sil-2100 already let into -proposed. Was there anything else critical expected on this SRU review today? It looks like it needs SRU verification performed etc.
[20:05] -ubottu:#ubuntu-devel- Launchpad bug 1990450 in update-manager (Ubuntu Xenial) "Show potential Ubuntu Pro updates" [Medium, New]
[20:05] <blackboxsw> wrong channel
[20:14] <coreycb> Skuggen: I added the strace requested by Jan to the mysql bug
[20:16] <Skuggen> coreycb: I saw, thanks! Since he's struggling a bit to reproduce, do you have any references we could use to reproduce the setup, config, etc?
[20:19] <coreycb> Skuggen: would config files be useful?
[20:20] <Skuggen> Yeah
[20:21] <coreycb> Skuggen: ok I'll attach them to the bug
[20:27] <Skuggen> Great, thanks.
[20:31] <coreycb> Skuggen: I added some. please let me know if anything else would be useful.
[20:33] <Skuggen> Will do. If we can reproduce from that, I guess we'll need to try to more fully recreate the setup
[20:34] <Skuggen> can't*
[20:37] <MacSlow> ok, bbl folks
[21:01] <liushuyu> Hi there, I am having trouble issuing the retry command for the autopkgtest for the package tryton-modules-account-payment-clearing. The system said I don't have the permission to use the service
[21:06] <jawn-smith> liushuyu: You need to have upload rights for the package that you are testing in order to start the tests
[21:06] <jawn-smith> By that logic any core dev can trigger any test for you
[21:06] <jawn-smith> If you link the test here I can restart it for you
[21:09] <liushuyu> jawn-smith: https://autopkgtest.ubuntu.com/packages/tryton-modules-account-payment-clearing
[21:11] <jawn-smith> liushuyu: hmm this appears to only be failing on i386, right?
[21:11] <jawn-smith> What's the reason you want the test restarted? I don't see it blocking anything in the excuses report
[21:12] <liushuyu> jawn-smith: That's my assigned proposed-migration last week. And yes, it was only failing on i386.
[21:13] <jawn-smith> Well it looks like that's resolved itself then, likely due to a migration-reference/0 test
[21:14] <jawn-smith> If you look at the excuses report for foundations:
[21:14] <jawn-smith> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[21:14] <jawn-smith> You'll see that setuptools is no longer blocked on that package
[21:14] <liushuyu> jawn-smith: That's why I was asking that question today morning in the meeting because I did not find it on the update_excuses page
[21:15] <jawn-smith> For further information, a migration-reference/0 test determines if the package's tests are failing regardless of any new packages. If it's regressed as a baseline, it won't block other packages from migrating
[21:15] <jawn-smith> I must have misunderstood your question in the meeting this morning, sorry about that!
[21:16] <liushuyu> jawn-smith: No worries! I probably did not phrase the question clear enough. I will try to word the questions better in the future
[22:00] <coreycb> Skuggen: I've added some recreate steps to the bug