[01:21] <mmikowski> arraybolt3: Got your mention on the bug. Yes, we already use a file in /etc/initramfs-tools/conf.d/kfocus.conf to set xz compression which fixes the issue with NX. Although we played with modules=dep, we avoided it because it can break some peripherals support (as you mention in your bug).
[01:24] <arraybolt3> K, good to know. Thank you!
[11:33] <GunnarHj> sil2100: Thanks for the langpacks in the making. :)
[12:30] <sil2100> GunnarHj: yw! But there's a problem: we don't have the potemplate-stats updated
[12:30] <sil2100> GunnarHj: I need to poke IS or someone to see why we don't see lunar stats updated here https://people.canonical.com/~people-l10n/data/ubuntu-l10n/
[12:33] <GunnarHj> sil2100: Ok. That's something I didn't even know it exists. :/
[12:35] <sil2100> GunnarHj: it's very vague, recently it was migrated to another place that does the auto-updates, but uh, it doesn't seem to work. I need to investigate who's actually maintaining it (I assume IS)
[13:37] <seb128> sil2100, could you note down what you figure out, we should drop that down in some maintainance notes for futur cycles?
[13:38] <sil2100> seb128: +1
[13:38] <seb128> sil2100, thanks!
[13:38] <LocutusOfBorg> zhsj, hello, thanks for the dpkg work! I was doing exactly the very same with Guillem (the Debian maintainer) and after doing it he pointed me to your branch
[13:38] <LocutusOfBorg> so I just did upload
[13:39] <LocutusOfBorg> with your name on it, of course :D
[13:39] <sil2100> I looked for documentation just now and found nothing about this, sadly :| Besides one RT that I'm trying to read through
[13:44] <zhsj> LocutusOfBorg: thanks for sponsoring as well as other places that i've missed.
[15:38] <sergiodj> LocutusOfBorg: hi, when you merged dpkg you dropped the changes I made on https://launchpad.net/ubuntu/+source/dpkg/1.21.12ubuntu2
[15:39] <LocutusOfBorg> sorry!
[15:39] <LocutusOfBorg> will fix soon!
[15:39] <sergiodj> LocutusOfBorg: thanks
[15:39] <LocutusOfBorg> bad when stuff doesn't migrate and MoM fails to detect it :/
[15:40] <sergiodj> yeah
[15:40] <LocutusOfBorg> damn it doesn't apply anymore
[15:40] <LocutusOfBorg> will have a look later
[15:40] <sergiodj> LocutusOfBorg: nevermind, I will work on adding them again
[15:42] <LocutusOfBorg> let me know if you have issues, otherwise I can work on it in 1h or so
[15:42] <LocutusOfBorg> I'm afk now for some time
[15:42]  * LocutusOfBorg goes grab child to kindengarden
[15:43] <sergiodj> LocutusOfBorg: will do, thank
[16:05] <seb128> !dmb-ping
[16:13] <mariogrip> Can anyone request a rebuild for lunar here? https://launchpad.net/ubuntu/+source/lomiri-url-dispatcher it tests fine on debian, but seems to be a bit flaky on ubuntu infra, i cannot reproduce it locally.
[16:15] <mariogrip> Also, i am a DM on debian, is there a way i can also get upl access on ubuntu? how does that work?
[16:16] <teward> mariogrip: amd64, ppc64el requeued.
[16:16] <mariogrip> teward: Thank you :)
[16:20] <teward> mariogrip: regarding "upload access" - https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess#Debian_Developers_applying_for_Per-Package_upload_rights see this.  note that Ubuntu and Debian processes differ greatly on old releases, etc. (Stable Release UPdates, etc.) so you might want to review all the Ubuntu developer processes first before you consider whether you need upload in Ubuntu
[16:21] <mariogrip> Thanks, will read it
[16:21] <teward> so in your case if you have no Ubuntu rights currently you should apply for Per Package Uploader (see the same page) for your package with justification
[16:22] <mariogrip> also can we try https://launchpad.net/ubuntu/+source/u1db-qt and https://launchpad.net/ubuntu/+source/lomiri-ui-extras armhf rebuild?
[16:23] <RikMills> mariogrip: I have retried those 3 on the architectures they failed on
[16:24] <mariogrip> tnx :)
[16:27] <RikMills> u1db-qt succeeded at least
[16:27] <RikMills> ah and lomiri-ui-extras
[16:27] <mariogrip> lomiri-url-dispatcher also worked :D so all good now
[16:28] <RikMills> the ppc64el fail on lomiri-url-dispatcher looks stubborn though :/
[16:28] <mariogrip> i have patched all my packages to work with LTO so, so all builds on ubuntu now
[16:28] <mariogrip> those dbus tests are tricky and racy
[16:30] <RikMills> giving it another go
[16:30] <teward> yeah i was gonna say ppc64el was still failing
[16:30] <mariogrip> I need to look more into those tests should not be like this, we have not seen those upstream,, but i need to find a way to trigger the bug
[16:33] <RikMills> mariogrip: teward looks like 3 go was the charm
[16:33] <teward> looks like that one built this time
[16:33] <RikMills> *3rd go
[16:33] <teward> RikMills: racy tests are racy :P
[16:34] <mariogrip> yay :D
[16:34] <teward> *returns to the warmth of blankets and hot coffee*
[16:35] <mariogrip> yeah, i need to look into it more, maybe i  need to try it in qemu
[17:55] <LocutusOfBorg> sergiodj, I did upload and it failed
[17:55] <LocutusOfBorg> I hate perl
[17:59] <arraybolt3> Slight version number problem I need help with if anyone's around. I'm working with a package that is native to Ubuntu, lubuntu-update-notifier. We recently made some changes and uploaded version 0.5.1 into Lunar, and I'm now about to prepare an SRU for Kinetic and Jammy that is a backport of the entire version, as all of the changes are bugfixes for high- or critical-severity problems. What
[17:59] <arraybolt3> version numbers should I make the Kinetic and Lunar packages?
[18:00] <arraybolt3> The Security Team docs tell me that Kinetic should be 0.5.1-0ubuntu0.22.10.1, BUT, dpkg --compare-versions tells me that this version number is *higher* than 0.5.1, which doesn't work well with upgrades.
[18:00] <arraybolt3> I suspect I should actually use 0.5.1~22.10.1, but I wanted to check first.
[18:01] <arraybolt3> For those who are interested in the SRU details, the bug report is https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2002255
[18:01] -ubottu:#ubuntu-devel- Launchpad bug 2002255 in lubuntu-update-notifier (Ubuntu Jammy) "lubuntu-update-notifier provides no good way to resolve a forcibly terminated system update" [Critical, Confirmed]
[18:01] <arraybolt3> I have not yet uploaded the Kinetic and Jammy fixes for that bug, however, since I'm stuck on version numbering.
[18:04] <sergiodj> LocutusOfBorg: are you taking a look or do you want me to handle this?
[18:31] <LocutusOfBorg> feel free if you understand the issue, I didn't yet
[18:31] <LocutusOfBorg> and ENOTIME for tonight
[18:35] <sergiodj> LocutusOfBorg: ACK, I'll work on it
[18:50] <sergiodj> LocutusOfBorg: FTBFS should be fixed now
[19:16] <jbicha> arraybolt3: using a ~ version number like you suggested for an SRU is fine
[19:17] <arraybolt3> Nice, thank you!