UbuntuIRC / 2022 /07 /06 /#lubuntu-devel.txt
niansa
Initial commit
4aa5fce
[00:53] <tsimonq2> Oh hi.
[00:53] <tsimonq2> arraybolt3: Looks like that stage is all good.
[00:59] <tsimonq2> arraybolt3: So, with this changelog entry...... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/e624fb4a707bba6008c14dfa34b657b4d004ba5d)
[01:02] <tsimonq2> In lxqt-config you missed a dash, fixing:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/75d57d9826f9e2bb7e08e37ea4425fe6727ef1f4)
[01:15] <tsimonq2> All of the packages in that list are uploading now. Please let me know if I missed one.
[01:46] <tsimonq2> Closed all of the PRs, should be solid for now
[01:46] <tsimonq2> Let me know once you have another list, Aaron
[01:46] <tsimonq2> For now I go back to being afk :)
[17:28] <kc2bez[m]> Testers - Please verify https://bugs.launchpad.net/bugs/1980687
[17:28] <kc2bez[m]> Thanks
[17:31] <arraybolt3[m]> Good afternoon!
[17:32] <arraybolt3[m]> > <@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] <arraybolt3[m]> > <@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] <arraybolt3[m]> kc2bez[m]: Fresh VM?
[17:34] <kc2bez[m]> arraybolt3[m]: A jammy VM, probably doesn't need to be fresh but it does need the version of Quassel in -proposed.
[17:34] <arraybolt3[m]> OK (was about to spin up Kinetic...)
[17:34] <kc2bez[m]> Kinetic should be released already so that should work too.
[17:35] <arraybolt3[m]> Well making a Jammy system is trivial.
[17:35] <arraybolt3[m]> Just install, update, reboot, open Quassel, right?
[17:35] <kc2bez[m]> The jammy -proposed one needs the verification.
[17:35] <arraybolt3[m]> (Oh, an enabled -proposed. Got it.)
[17:35] <kc2bez[m]> yup
[17:36] <lubot> [telegram] <Leokolb> Testing Jammy Quassel proposed right now
[17:36] <arraybolt3[m]> Me too.
[17:36] <Eickmeyer[m]> Let me know how it goes.....
[17:36] <kc2bez[m]> cool, a couple can't hurt
[17:37] <Eickmeyer[m]> I mean, it should be stupid simple.
[17:37] <kc2bez[m]> Very true
[17:38] <lubot> [telegram] <Leokolb> OK - Network name : DebianIRC but server is irc.libera.chat:6696 and join channel #ubuntu
[17:39] <Eickmeyer[m]> Uh.... did I miss... the.... network... .name.....
[17:39] <Eickmeyer[m]> ?
[17:39] * Eickmeyer[m] facepalms hard
[17:39] <arraybolt3[m]> Guess we're about to find out.
[17:39] <lubot> [telegram] <Leokolb> yes (re @lubuntu_bot: (irc) <Eickmeyer[m]> Uh.... did I miss... the.... network... .name.....)
[17:40] <Eickmeyer[m]> sigh A one-line change, not hard to fix, but back to the drawing board a little.
[17:40] <kc2bez[m]> iterative changes, progress all the way.
[17:48] <Eickmeyer[m]> Yeah, but the SRU team tends to get annoyed with this stuff.
[17:50] <lubot> [telegram] <Leokolb> Should I hold off with bug comments? (re @lubuntu_bot: (irc) <Eickmeyer[m]> Yeah, but the SRU team tends to get annoyed with this stuff.)
[17:51] <Eickmeyer[m]> @Leokolb Yeah, probably. I'm already on it.
[17:51] <Eickmeyer[m]> https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687/comments/5
[17:51] <lubot> [telegram] <Leokolb> ok fine - give a shout when it needs re-testing (re @lubuntu_bot: (irc) <Eickmeyer[m]> @Leokolb Yeah, probably. I'm already on it.)
[17:51] <ubot93> Launchpad bug 1980687 in quassel (Ubuntu Kinetic) "[SRU] Quassel should not have #debian as default channel in Ubuntu" [High, Fix Committed]
[18:01] <Eickmeyer[m]> @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] <Eickmeyer[m]> Ok, @Leokolb, arraybolt3 Dan Simmons , the fix for the quassel name has been accepted, we're good to go.
[18:33] <Eickmeyer[m]> Rather, the network name.
[18:34] <kc2bez[m]> Excellent, thanks for the update.
[18:34] <Eickmeyer[m]> No prob.
[18:40] <lubot> [telegram] <Leokolb> tks ..running test (re @lubuntu_bot: (irc) <Eickmeyer[m]> Ok, @Leokolb, arraybolt3 Dan Simmons , the fix for the quassel name has been accepted, we're good to go.)
[18:40] <Eickmeyer[m]> @Leokolb it's not even in proposed yet.
[18:41] <lubot> [telegram] <Leokolb> ohhhh...ok np (re @lubuntu_bot: (irc) <Eickmeyer[m]> @Leokolb it's not even in proposed yet.)
[18:41] <Eickmeyer[m]> Still building.
[18:42] <lubot> [telegram] <Leokolb> Saw the comment from Robie..
[18:43] <Eickmeyer[m]> Yeah, that's a hybrid-automated comment when they accept an SRU.
[18:44] <kc2bez[m]> You can watch the build process here https://launchpad.net/ubuntu/+source/quassel/1:0.14.0-1ubuntu0.22.04.3
[18:59] <arraybolt3[m]> 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] <ubot93> Pull 1 in lubuntu-team/qterminal-packaging "Backports/jammy" [Open]
[18:59] <ubot93> Pull 1 in lubuntu-team/xdg-desktop-portal-lxqt-packaging "Backports/jammy" [Open]
[20:16] <lubot> [telegram] <Leokolb> Quassel after 22.04.3 upgrade - https://imgur.com/a/XLDHpYD (re @lubuntu_bot: (irc) <Eickmeyer[m]> Yeah, that's a hybrid-automated comment when they accept an SRU.)
[20:17] <arraybolt3[m]> \o/
[20:17] <Eickmeyer[m]> Take a look for UbuntuIRC.
[20:17] <Eickmeyer[m]> (should be default)
[20:24] <lubot> [telegram] <Leokolb> NP connecting to #ubuntu (re @lubuntu_bot: (irc) <Eickmeyer[m]> (should be default))
[20:24] <Eickmeyer[m]> Awesome.
[20:25] <lubot> [telegram] <Leokolb> yes ..have to run but good to get another confirm on this (re @lubuntu_bot: (irc) <Eickmeyer[m]> Awesome.)
[20:25] <Eickmeyer[m]> arraybolt3: ^
[20:25] <arraybolt3[m]> Eickmeyer: Will test shortly.
[21:40] <lubot> [telegram] <lynorian> 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] <ubot93> 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] <arraybolt3[m]> Hey, did you see the two last Stage IV PR's I linked to? Simon Quigley (Developer)
[22:13] <tsimonq2> arraybolt3[m]: Yes I did
[22:13] <tsimonq2> I will review them in a bit
[22:13] <tsimonq2> Feel free to start on others as well :)
[22:14] <arraybolt3[m]> Nice. I'll be done with Stage V by tonight most likely. Then we can sprint tomorrow.
[23:18] <lubot> [telegram] <teward001> okay, so i've got drone partially set up
[23:18] <lubot> [telegram] <teward001> 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] <lubot> [telegram] <teward001> @kc2bez see above
[23:26] <lubot> [telegram] <teward001> 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] <lubot> [telegram] <teward001> (max of 2 concurrent builds at the moment though, might up it to 4 but we'll see)
[23:27] <lubot> [telegram] <teward001> at least i'm STARTING to make progress
[23:27] <arraybolt3[m]> 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] <arraybolt3[m]> Recent Intel i3s have gotten insanely fast just recently.
[23:28] <arraybolt3[m]> I put together a sample build in PCPartPicker for ~$600 that should have been able to take on 8 concurrent builds.