[09:47] <ogayot> hello, may I kindly ask somebody to trigger this autopkgtest for me? https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=amd64&package=dbus&ppa=ogayot%2Fmantic-proposed&trigger=dbus%2F1.14.6-1ubuntu1~ppa1  - thanks!
[09:50] <schopin> ogayot: .
[09:51] <ogayot> schopin: thanks!
[11:00] <rbasak> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: rbasak
[11:06] <rbasak> I was using the fact that ~ubuntu-sponsors is requested for review in a git-ubuntu MP to make it appear in the sponsorship queue.
[11:07] <rbasak> But if somebody in ~ubuntu-sponsors reviews (let's say with Needs Fixing) then they "grab" that review slot, and ~ubuntu-sponsors no longer has one. I think this might cause the entry to disappear from the sponsorship queue - for example after the contributor has fixed the issue.
[11:07] <rbasak> Any suggestions on what I should do instead?
[11:08] <rbasak> On the Server Team, we use a review slot for ~canonical-server-reporter that nobody is a member of in order to avoid this happening. That way the "marker" remains. But to do this for ~ubuntu-sponsors would mean we have to use a separate team name.
[11:08] <rbasak> Separately, there's a bot that actually adds ~ubuntu-sponsors as a reviewer if there is nobody else. Maybe that could subscribe ~ubuntu-sponsors-reporter or similar?
[11:22] <rbasak> juliank: I'm patch piloting today but I can't progress https://code.launchpad.net/~macg3/ubuntu/+source/gdebi/+git/gdebi/+merge/414211 because I'm not in ~gdebi-developers - surely this should go upstream rather than in an Ubuntu delta? What's the plan there please?
[11:23] <juliank> rbasak: it's been dead and unmaintained for 8 years?
[11:25] <rbasak> That wasn't my question :)
[11:26] <juliank> Well there's no upstream, you can find a DD to NMU it and sync it
[11:27] <juliank> There's no version control any of the 6 NMUs are imported in and I'm on a long weekend so I'm not doing anything today
[11:42] <rbasak> mapreri or utkarsh2102: I think https://code.launchpad.net/~macg3/ubuntu/+source/gdebi/+git/gdebi/+merge/414211 is good to land but I'm not sure where. As recent NMUers to gdebi, could you help me with an NMU to Debian please if that's appropriate?
[11:42] <rbasak> The previous NMUs don't look like they were done with a BTS bug or the delayed queue. What's the etiquette here?
[11:44] <utkarsh2102> rbasak: I can look at it this weekend or early next week. If that’s okay, please have it assigned to me and I’ll get back.
[11:48] <rbasak> utkarsh2102: sure. Thanks!
=== JanC_ is now known as JanC
[12:25] <rbasak> coreycb: bug 1996010 is in the general sponsorship queue, but it was added automatically and it's not clear to me if this is ready/wanted by the openstack team. Please could you take a look?
[12:25] -ubottu:#ubuntu-devel- Bug 1996010 in ceph (Ubuntu Lunar) "[SRU] the leak in bluestore_cache_other mempool" [Undecided, Confirmed] https://launchpad.net/bugs/1996010
[14:30] <rbasak> xnox: are you planning on merging tpm2-pkcs11? https://code.launchpad.net/~danfuhry/ubuntu/+source/tpm2-pkcs11/+git/tpm2-pkcs11/+merge/437163 is affected and it looks like the merge has been outstanding for over a year.
[16:01] <bdmurray> rbasak: How much longer are you piloting for?
[16:42] <rbasak> Oh
[16:42] <rbasak> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[16:42] <rbasak> Sorry
[16:42] <rbasak> I'm done, just writing up.
[18:02] <bdmurray> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: bdmurray
[22:04] <bdmurray> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[22:27] <bdmurray> sarnold: Do you know about adding bug watches? bug 2020826
[22:27] -ubottu:#ubuntu-devel- Bug 2020826 in needrestart (Ubuntu Lunar) "VM detection is broken, leading to prompt to restart for microcode updates" [Medium, In Progress] https://launchpad.net/bugs/2020826
[22:29] <bdmurray> https://wiki.ubuntu.com/Bugs/Watches
[22:42] <sarnold> bdmurray: I think "vaguely" is the right answer -- I know about them, and I thought putting the debian bug url in the description would just automatically hook it up
[22:47] <bdmurray> sarnold: It shows up in the "Remote bug watches" info box but that isn't nearly as useful
[22:50] <sarnold> bdmurray: hah then I guess I need to amend my previous answer and spend more time onthe wiki page..
[22:53] <sarnold> bdmurray: so.. I thought there was (a) tracking the status in the info box thing (b) importing comments from the remote bug tracker; re-reading this bug, I see that (a) you added the bug watch very recently (b) no comments imported from debian -- does launchpad only import comments made after the bug watch was installed? or do we need to wait for midnight to import them?
[22:54] <vorlon> rbasak: so I've routinely found that I have to explicitly claim MP reviews on behalf of e.g. ~ubuntu-archive, else it doesn't show as the team review happening
[22:54] <vorlon> rbasak: and AFAIK this is not a launchpad per-team configuration issue?
[22:58] <rbasak> vorlon: I don't know. It was a long standing issue on the server team until we started using a team we deliberately don't belong to instead
[22:58] <rbasak> I'm fairly sure that this was happening without anyone clicking on the Claim Review button
[22:59] <vorlon> interesting
[22:59] <rbasak> In our case we actually belonged to two or three separate teams that had review slots
[22:59] <bdmurray> sarnold: I don't think debian comments get imported but the status of the Debian bug task would change some time when the sync runs
[22:59] <rbasak> One would get randomly "claimed", and if it was the one we didn't intend, then that messed up our process.
[23:00] <vorlon> wow definitely not my experience
[23:00] <rbasak> I think I need to set some time aside to experiment.
[23:02] <sarnold> " 1 → 75 of 4771 trackers "  https://launchpad.net/bugs/bugtrackers/  *wow*. I thought we had something like 20, which felt very impressive until now :)