[00:53] Oh hi. [00:53] arraybolt3: Looks like that stage is all good. [00:59] arraybolt3: So, with this changelog entry...... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/e624fb4a707bba6008c14dfa34b657b4d004ba5d) [01:02] In lxqt-config you missed a dash, fixing:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/75d57d9826f9e2bb7e08e37ea4425fe6727ef1f4) [01:15] All of the packages in that list are uploading now. Please let me know if I missed one. [01:46] Closed all of the PRs, should be solid for now [01:46] Let me know once you have another list, Aaron [01:46] For now I go back to being afk :) [17:28] Testers - Please verify https://bugs.launchpad.net/bugs/1980687 [17:28] Thanks [17:31] Good afternoon! [17:32] > <@tsimonq2:linuxdelta.com> arraybolt3: So, with this changelog entry...... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/46f4ece738bb05a95fbb416d8da0c61c3debe667) [17:32] > <@tsimonq2:linuxdelta.com> In lxqt-config you missed a dash, fixing:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/c490c387d2277cb754ae5b989ca842c082686245) [17:33] kc2bez[m]: Fresh VM? [17:34] arraybolt3[m]: A jammy VM, probably doesn't need to be fresh but it does need the version of Quassel in -proposed. [17:34] OK (was about to spin up Kinetic...) [17:34] Kinetic should be released already so that should work too. [17:35] Well making a Jammy system is trivial. [17:35] Just install, update, reboot, open Quassel, right? [17:35] The jammy -proposed one needs the verification. [17:35] (Oh, an enabled -proposed. Got it.) [17:35] yup [17:36] [telegram] Testing Jammy Quassel proposed right now [17:36] Me too. [17:36] Let me know how it goes..... [17:36] cool, a couple can't hurt [17:37] I mean, it should be stupid simple. [17:37] Very true [17:38] [telegram] OK - Network name : DebianIRC but server is irc.libera.chat:6696 and join channel #ubuntu [17:39] Uh.... did I miss... the.... network... .name..... [17:39] ? [17:39] * Eickmeyer[m] facepalms hard [17:39] Guess we're about to find out. [17:39] [telegram] yes (re @lubuntu_bot: (irc) Uh.... did I miss... the.... network... .name.....) [17:40] sigh A one-line change, not hard to fix, but back to the drawing board a little. [17:40] iterative changes, progress all the way. [17:48] Yeah, but the SRU team tends to get annoyed with this stuff. [17:50] [telegram] Should I hold off with bug comments? (re @lubuntu_bot: (irc) Yeah, but the SRU team tends to get annoyed with this stuff.) [17:51] @Leokolb Yeah, probably. I'm already on it. [17:51] https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687/comments/5 [17:51] [telegram] ok fine - give a shout when it needs re-testing (re @lubuntu_bot: (irc) @Leokolb Yeah, probably. I'm already on it.) [17:51] Launchpad bug 1980687 in quassel (Ubuntu Kinetic) "[SRU] Quassel should not have #debian as default channel in Ubuntu" [High, Fix Committed] [18:01] @Leokolb Feel free to comment if you wish, but I don't know how much more you can add. I'll also alert Robie. [18:33] Ok, @Leokolb, arraybolt3 Dan Simmons , the fix for the quassel name has been accepted, we're good to go. [18:33] Rather, the network name. [18:34] Excellent, thanks for the update. [18:34] No prob. [18:40] [telegram] tks ..running test (re @lubuntu_bot: (irc) Ok, @Leokolb, arraybolt3 Dan Simmons , the fix for the quassel name has been accepted, we're good to go.) [18:40] @Leokolb it's not even in proposed yet. [18:41] [telegram] ohhhh...ok np (re @lubuntu_bot: (irc) @Leokolb it's not even in proposed yet.) [18:41] Still building. [18:42] [telegram] Saw the comment from Robie.. [18:43] Yeah, that's a hybrid-automated comment when they accept an SRU. [18:44] You can watch the build process here https://launchpad.net/ubuntu/+source/quassel/1:0.14.0-1ubuntu0.22.04.3 [18:59] Simon Quigley (Developer): There's still a couple of Stage IV LXQt backports that haven't been merged yet (I think I did them late last night): https://github.com/lubuntu-team/qterminal-packaging/pull/1 and https://github.com/lubuntu-team/xdg-desktop-portal-lxqt-packaging/pull/1 [18:59] Pull 1 in lubuntu-team/qterminal-packaging "Backports/jammy" [Open] [18:59] Pull 1 in lubuntu-team/xdg-desktop-portal-lxqt-packaging "Backports/jammy" [Open] [20:16] [telegram] Quassel after 22.04.3 upgrade - https://imgur.com/a/XLDHpYD (re @lubuntu_bot: (irc) Yeah, that's a hybrid-automated comment when they accept an SRU.) [20:17] \o/ [20:17] Take a look for UbuntuIRC. [20:17] (should be default) [20:24] [telegram] NP connecting to #ubuntu (re @lubuntu_bot: (irc) (should be default)) [20:24] Awesome. [20:25] [telegram] yes ..have to run but good to get another confirm on this (re @lubuntu_bot: (irc) Awesome.) [20:25] arraybolt3: ^ [20:25] Eickmeyer: Will test shortly. [21:40] [telegram] https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1974231 I can't update the manual on xscreensaver becasue I keep running into this bug I filed [21:40] Launchpad bug 1974231 in xscreensaver (Ubuntu) "xscreensaver has a segmentation fault at startup" [Undecided, New] [22:11] * tsimonq2 uploaded an image: (205KiB) < https://libera.ems.host/_matrix/media/r0/download/linuxdelta.com/lghTXhzMHhwgxbjUrdeqNFdY/Screenshot_20220706-171127_Outlook.jpg > [22:12] Hey, did you see the two last Stage IV PR's I linked to? Simon Quigley (Developer) [22:13] arraybolt3[m]: Yes I did [22:13] I will review them in a bit [22:13] Feel free to start on others as well :) [22:14] Nice. I'll be done with Stage V by tonight most likely. Then we can sprint tomorrow. [23:18] [telegram] okay, so i've got drone partially set up [23:18] [telegram] it's set up with the docker runner. not sure if we can create a template 'build' env that allows us to launch the relevant docker image builds and produce build runs, but if not i can always create an ssh/exec runner on a relevant LXD container for a given release and set stuff up. or create an exec runner that has access to sbuild etc. calls [23:19] [telegram] @kc2bez see above [23:26] [telegram] right now it only has the docker runner on it, but at least i'm making progress. it's running on a RamNode VPS at the moment, because it suggested NOT running the drone stuff on the same system as other resources so [23:26] [telegram] (max of 2 concurrent builds at the moment though, might up it to 4 but we'll see) [23:27] [telegram] at least i'm STARTING to make progress [23:27] Wow, that's exciting! You're having to run it on a VPS? Would it potentially be cheaper to run it on cheap physical hardware (say intel i3 Alder Lake)? [23:28] Recent Intel i3s have gotten insanely fast just recently. [23:28] I put together a sample build in PCPartPicker for ~$600 that should have been able to take on 8 concurrent builds.