=== diddledani is now known as lucyllewy
=== sem2peie- is now known as sem2peie
[17:34] <renanrodrigo> rbasak: sorry me here
[17:35] <rbasak> renanrodrigo: o/
[17:35] <rbasak> Is the eol-esm fix in Salsa? I don't see it there, or an MR to add it.
[17:35] <rbasak> I think we have time, right? Can we do that first?
[17:36] <renanrodrigo> I don't think so. I got questions from the maintainers in the LP bug I opened, but that's all
[17:36] <renanrodrigo> sure, that first makes sense
[17:36] <rbasak> Then it's more straightforward for everything to pull from there. We can sync into Lunar, and the the SRUs would be straight backports.
[17:36] <rbasak> Could you submit an MR to Salsa please?
[17:36] <renanrodrigo> sure. Is there any kind of special process for that?
[17:37] <renanrodrigo> sorry again but I am new to this world, will need to create an account :|
[17:37] <rbasak> Nothing special - just the same as submitting a change to any typical FLOSS project.
[17:37] <rbasak> Yes you'll need a Salsa account. It should be straightforward to register for one.
[17:38] <rbasak> Then see https://salsa.debian.org/debian/distro-info-data
[17:38] <rbasak> Note also https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2003949
[17:38] -ubottu:#ubuntu-devel- Launchpad bug 2003949 in distro-info-data (Ubuntu Bionic) "Document ESM overlap period" [High, Incomplete]
[17:38] <rbasak> Steve wanted a public source for the change to support periods. I guess that request still stands.
[17:39] <rbasak> Your bug is for esm-esm, and Dimitri's is for eol and eol-server, so they are distinct. But it's probably be easier to merge them together as they're really all the same thing.
[17:42] <renanrodrigo> sure it is
[17:42] <renanrodrigo> for Bionic, we have public blog posts about the new date
[17:43] <renanrodrigo> as people asked, this will probably be reflected for F/J, and I'll ask Lech for evidence once this is decided
[17:47] <renanrodrigo> Your account is pending approval from your GitLab administrator and hence blocked. - /me waits
[17:51] <rbasak> "Your account will be locked until a gitlab administrator enables it. As of July 2021 you will now receive an email confirming your account validation, please be patient. (Ping the above Support after 4 days patience)"
[17:51] <rbasak> From https://wiki.debian.org/Salsa/Doc
[17:52] <renanrodrigo> yep found it
[17:52] <renanrodrigo> thanks for all the guidance
[18:06] <arraybolt3> Asking for review for the latest patch for this bug: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751 Somewhat anxious to get it in soon, since Beta Freeze is looming and this is a serious bug that I would rather not see be in the beta.
[18:06] -ubottu:#ubuntu-devel- Launchpad bug 2011751 in openbox (Ubuntu) "openbox crashed with SIGABRT" [Critical, Confirmed]
[19:25] <arraybolt3> Hey, it looks like a recent change in aptdaemon may have broken some of the functionality of lubuntu-update-notifier - in particular, we used to have download progress indicators that have silently vanished - no errors in the terminal, no indication why they're gone, they're just gone.
[19:26] <arraybolt3> I'm unable to build an older version of aptdaemon for Kinetic in order to tell for sure since it looks like a change was needed to get it to build on Lunar.
[19:26] <arraybolt3> But I'm wondering if this might have affected things? https://launchpad.net/ubuntu/+source/aptdaemon/1.1.1+bzr982-0ubuntu40
[19:27] <arraybolt3> In particular, it looks like the "progress-download-changed" signal is no longer being triggered.
[19:31] <arraybolt3> Anyway, filing a bug report.
[19:31] <arraybolt3> And doing some further testing.
[19:32] <arraybolt3> Yeah, the signal is no longer being triggered.
[19:33] <arraybolt3> Sorta surprising, the whole entire diff is http://launchpadlibrarian.net/645079610/aptdaemon_1.1.1+bzr982-0ubuntu39_1.1.1+bzr982-0ubuntu42.diff.gz
[19:33] <arraybolt3> From Kinetic (which I believe works) to Lunar (which is now broken).
[19:40] <arraybolt3> Oh, wait, it is getting called?
[19:40] <arraybolt3> grr... might be Python being Python again
[19:53] <arraybolt3> OK nevermind, it's a bug in our code apparently, probably Qt related.
[19:53] <arraybolt3> Figuring it out now.
[21:40] <danilogondolfo> I need a sponsor for https://code.launchpad.net/~danilogondolfo/ubuntu/+source/tgt/+git/tgt/+merge/439580 anybody available? Should be a quick one...
[21:56] <mwhudson> danilogondolfo: have you sent the patch to debian?
[21:57] <danilogondolfo> mwhudson, not yet, but I will
[22:30] <mwhudson> danilogondolfo: uploading
[22:30] <mwhudson> danilogondolfo: please do follow up on getting the patch into debian :-)
=== arraybolt3_ is now known as arraybolt3