 well
 Dell told me the partwould arrive in 7 days - next week
 i have the new keyboard today installed in the laptop yay!
 so nice to have a working enter key again xD
[01:54] <arraybolt3[m]> @teward001 I love ridiculously early deliveries.
 i know right
 Dell's regular shipping is usually 2 day turnaround for parts only
 but in this case it waslike 1 day xD
 in any case check your DMs i sent you codimd creds for notes.lubuntu.me
 *goes and obtainsfood*
[02:37] <arraybolt3[m]> I got a successful GBP build! \o/
[02:37] <arraybolt3[m]> I've still got to get it uploaded to Salsa, but I'm finally getting there!
[03:25] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: What time will you be around tomorrow morning you think?
[03:26] <arraybolt3[m]> You said early tomorrow morning, what time is that for you?
[03:26] <tsimonq2> I'm probably going to just pick up where you left off and work at it until I'm waiting on Debian publishing 
[03:26] <arraybolt3[m]> (I know we both have a tendency to be night owls.)
[03:26] <arraybolt3[m]> I got all of LXQt done, just those last PRs need merged.
[03:26] <arraybolt3[m]> I can pull up the list if that's helpful.
[03:26] <tsimonq2> arraybolt3[m]: With Backports, Kinetic, or for Debian?
[03:27] <tsimonq2> We need a list for all three.
[03:27] <arraybolt3[m]> Backports.
[03:27] <arraybolt3[m]> Kinetic, not even touched hardly. Debian, just got started.
[03:27] <arraybolt3[m]> (I finished whatever's before qtxdg-tools on Debian, and am just finishing qtxdg-tools now.)
[03:27] <tsimonq2> Cool, keep cranking it out, if you come to a stopping point in the middle of the package please give me your WIP packaging somewhere 
[03:28] <arraybolt3[m]> OK. I'm gonna get two pushes done, probably make MRs for them, CodiMD, then send them... somehow, since I've never used CodiMD before :-D
[03:28] <tsimonq2> Here's what I'd do... I'd look at the upstream Compiling wiki page and get a machine-readable list for the LXQt stack
[03:29] <tsimonq2> I would make a table with four columns... Package Name, Debian, Kinetic, Backports (in order of upstream/downstream relationships, top to bottom)
[03:29] <arraybolt3[m]> List of URLs?
[03:30] <tsimonq2> One package per row, just do a checkbox / link to PR / name to say you're working on it 
[03:30] <tsimonq2> arraybolt3[m]: List of package names 
[03:30] <arraybolt3[m]> And what format is the table best in? Google Sheets? reST?
[03:30] <tsimonq2> Markdown :)
[03:30] <arraybolt3[m]> tsimonq2: Got it.
[03:30] <tsimonq2> Bonus points if you use sed 
[03:30] <arraybolt3[m]> Ah, I know Markdown tables!
[03:30] <tsimonq2> And awk
[03:30] <arraybolt3[m]> tsimonq2: :-(
[03:30]  * arraybolt3[m] already had to burst my brain with GBP
[03:31] <arraybolt3[m]> tsimonq2: 🤯
[03:31]  * tsimonq2 would personally make a machine-readable newline-separated list with all the packages and use bash
[03:32] <arraybolt3[m]> > * <@tsimonq2:linuxdelta.com> would personally make a machine-readable newline-separated list with all the packages and use bash
[03:32] <arraybolt3[m]> Bash 👍️ That I know!
[03:34] <tsimonq2> It would look something like this (I may even get the syntax first try on mobile, look at me being a baller):... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/af8743343ca2d6c12a2b31ac4a9314b2e36988cd)
[03:34] <tsimonq2> Let me know if you need help understanding what that does 
[03:35] <arraybolt3[m]> Eh, I think I get the jist of it.
[03:35] <arraybolt3[m]> Takes a list of package names and turns it into a Markdown table ready to be filled in.
 "OK. I'm gonna get two pushes..." <- You don't send docs with Codi, it's saved automatically, you just send the link. We can both work on the same doc simultaneously 
[03:35] <arraybolt3[m]> Oh that's cool!
[03:35] <tsimonq2> arraybolt3[m]: I guess what I'm asking is if you understand the `awk` part
[03:36] <arraybolt3[m]> No, only sorta looked into awk, but I recognize the pipe characters as being from Markdown... I hope.
[03:36] <arraybolt3[m]> (I mean, it sure looks like a table.)
[03:36] <arraybolt3[m]> Is Awk something I should learn?
[03:37] <arraybolt3[m]> (I mean, like, something essential to learn. I'd like to learn the essentials first and then get the tips and optimizations later so I can keep up. Unless that's a bad idea.)
[03:37] <tsimonq2> arraybolt3[m]: It's one of the many tools that you'll find on virtually every distro by default, and down the road when you do much more complex things you'll thank me later 
[03:38] <arraybolt3[m]> OK. I never could make heads or tails of the man page, but I have Internet now, so I should be able to find an actually good tutorial.
[03:38] <arraybolt3[m]> (I guess if I stared at it long enough it might have worked, but...)
[03:39] <tsimonq2> Don't spend an awful amount of time on it since we're sprinting not walking ;) but I'd say learn the basics of the syntax and the functions you're going to use the most. This is a great opportunity to get some practice
[03:39] <arraybolt3[m]> OK. Sounds like a plan.
[03:40] <arraybolt3[m]> I'd rather tune my schedule to when you want to start the sprint, and my sleep schedule has been so wildly out of whack I can pretty much choose to go to bed whenever (or not go to bed at all), so whatever time is best for you, I'll do that.
[03:41] <tsimonq2> I'm thinking I'll be back anywhere between 1 and 3. Do you plan on being up that late?
[03:41] <arraybolt3[m]> Easily.
[03:41] <tsimonq2> Sounds good. If you get tired soon just remember to attempt a smooth handoff so I can make progress while you sleep (and vice versa :))
[03:41] <arraybolt3[m]> I'll probably be down for the count by 6... but I might push past even that if things get going rapidly enough.
[03:42] <arraybolt3[m]> tsimonq2: Very good plan.
[03:42] <arraybolt3[m]> Really, though, of all of the time I've been doing this so far, I feel like, this is it. If I'm going to prove myself, now's my chance. I do have to be done by sunset tomorrow due to other appointments I have, but I'll be back on Sunday night and be ready to go full throttle again.
[03:43] <tsimonq2> I'm not sure how much energy I have but I planned a few backup fallout days after this to just chill (probably will be running on 3h of sleep tomorrow, it is what it is, I've accepted it)
[03:43] <arraybolt3[m]> Sounds like a good idea - this is going to be extreme. We need extreme here.
[03:43] <tsimonq2> arraybolt3[m]: Remember to document all your changes, I will say nothing more *wink* *wink*
[03:43] <arraybolt3[m]> You got it.
[03:44] <tsimonq2> Debian, Ubuntu, and Backports. They all count
[03:44] <arraybolt3[m]> Nice. Should I document the last five packages in backports, or are they merged in?
[03:45] <arraybolt3[m]> (By document I mean, record that they still need merged in.)
[03:45] <arraybolt3[m]> (I made detailed changelogs and git commits.)
[03:46] <arraybolt3[m]> OK, I'll record them. (Dawns on me, that was probably already part of the plan.)
[04:49] <arraybolt3[m]> I made a CodiMD sheet for keeping track of our progress, I didn't realize hitting Publish was going to, erm, publish it instantly, and I can't find a Delete button now 🫠, so if that needs cleaned up, sorry. I'm not sure if the sheet should be publically shared or DM'd to everyone, so let me know when and where you want it so I can send it.
 "I made a CodiMD sheet for..." <- Can you just go back to the edit page or does it strip that?
[05:23] <arraybolt3[m]> I can go back to Edit just fine, but now there's some random link pointing to a different view of the page, not sure how to undo that. I can still edit just fine.
[05:36] <tsimonq2> Perhaps it just saves a snapshot of the document
[05:36] <arraybolt3[m]> I don't think it did any harm except for eat a bit of disk space, but if someone wonders, "Hey, what is this?", that's what it is.
[06:35] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: 15 min heads up
[06:35] <arraybolt3[m]> Got it..
[06:36] <tsimonq2> We can also definitely work side-by-side if we're both online
[06:36] <arraybolt3[m]> Simon Quigley (Developer): Ready whenever you are.
[06:36] <arraybolt3[m]> Simon Quigley (Developer): CodiMD sheet?
[06:36] <tsimonq2> Do you have some kind of docs ready for the current status of everything?
[06:36] <arraybolt3[m]> (I can paste it here or DM)
[06:36] <tsimonq2> Please
[06:36] <arraybolt3[m]> Yep, it's mostly complete.
[06:36] <arraybolt3[m]> Paste here is good?
[06:36] <tsimonq2> Yeah just pays the link it's OK
[06:36] <arraybolt3[m]> https://notes.lubuntu.me/m4VP6HXnSI-e10z1MfsuAw?edit
[06:37] <tsimonq2> Please excuse my talk to texting
[06:37] <arraybolt3[m]> No problem.
[06:37] <tsimonq2> That's funny, that time I actually did say Texan as in Texas
[06:37] <arraybolt3[m]> LOL auto-in-correct-but-got-it-right-this-time
[06:38] <arraybolt3[m]> OK, I'd better get off my Chromebook and onto my desktop.
[06:43] <arraybolt3[m]> Simon Quigley (Developer): OK, I think I'm fully armed. Both monitors on, Element on desktop, VM primed, CodiMD open.
[06:44] <arraybolt3[m]> (Am I the only one who seems to have a bunch of junk terminals all over the place from previous work? I sometimes have to close 5 or 7 terminal windows all at once LOL)
[06:48] <guiverc> (You won't be arraybolt3[m])
[06:50] <arraybolt3[m]> guiverc: I suppose you're right, we're probably going to end up with terminals on our screen like pepper on our food during this. Hey, good to see you!
[06:53] <guiverc> My (second) screen fills up with browser windows mostly... when I finish the task the window gets closed..  but yeah I have numerous terms open too  (I'm waiting on an ISO download so I can write & test that..)  :) & thanks
[06:54] <arraybolt3[m]> Man, sounds a bit more orderly than mine. I usually have Element full-screen on the second monitor, the primary one looks like an angry squirrel tore through my app menu.
[06:54] <arraybolt3[m]> *quite a bit more orderly than mine
[06:56] <guiverc> It's not orderly... I do also use the workspace/desktops for specific tasks.. but most of Ubuntu sits on 1st as that's where hexchat (my IRC client) is
[06:57] <arraybolt3[m]> I really should learn to use workspaces - as a previous long-time Windows user, I'm still not used to the idea of workspaces even being a thing.
[06:57] <guiverc> I do have element full size on a thinkpad x201 elsewhere; but not on this box with larger screen
 I find workspaces less useful if you do have multiple monitors and more useful if you only have 1
[06:59] <guiverc> they are cool (unlike in XP which did have them.. but they were near useless) .. but it depends on how/what you use them for... I like how GNOME has the second display unchanged for some tasks (here on LXQt I just make those windows appear all workspaces)
[06:59] <arraybolt3[m]> @lynorian: That makes sense, but when you decide to consume one whole monitor with one application and then try to juggle five or seven others on the other monitor... (That being said, I'd probably be able to make better use of the space if my monitors were arranged sanely, but desk real estate is precious in my setup, so one monitor is caddy-corner to the other and is a pain to use for much other than Element.)
[07:00] <arraybolt3[m]> guiverc: Wait, Windows XP had workspaces? This is news to me.
[07:00] <arraybolt3[m]> ls
[07:00] <arraybolt3[m]> (Great, now I'm gonna use Element as my terminal, I guess...)
[07:01] <guiverc> a form of them yes.. (xp & workspaces).. linux (GNOME & KDE, XFCE etc) had them for a few years by then so msft gave it a try.. they were to inefficient to be useful on XP & boxes used to run xp at the time how it was done
[07:02]  * guiverc thinks they came out with xp sp2; so not early xp - but a later service pack introduced them
[07:02] <arraybolt3[m]> Hmm. I never stumbled across them even once, and I was one of those kids who liked to dig through the guts of the system (found the hidden chat program somewhere deep inside System32 at one point). I think I was using sp2 and sp3.
[07:04] <arraybolt3[m]> Simon Quigley (Developer): For whenever you see this, there's one small problem I'm having with making good progress on the Debian stuff, and that's that, I don't know what code is in the finished product after our work on Backports. I have my code, obviously, but I know you made some tweaks and fixes, and I
[07:04] <arraybolt3[m]> I'd hate to plop a bad bit of code into Debian.
[07:04] <arraybolt3[m]> So we will need to get everything Git-ified (or at least I'll need to find out where everything's at) before I can proceed efficiently.
[07:04] <arraybolt3[m]> (And safely.)
[07:05]  * guiverc whispers take take of my debian; don't upset it !   or my Ubuntu boxes either !!
[07:06] <arraybolt3[m]> 👍️
[07:08] <tsimonq2> Online time tbd
[07:08] <arraybolt3[m]> ?
[07:08] <arraybolt3[m]> (Sorry, I'm missing something.)
[07:12] <arraybolt3[m]> Ah, I think I get it now. Nevermind. I'll be here.
[07:13] <arraybolt3[m]> ls
[07:13] <arraybolt3[m]>  * (trying to ls in Element rather than QTerminal again)
 "So we will need to get everythin..." <- Actually, it dawns on me I can pull the source packages for the backports-staging PPA most likely, and get the exact code. OK, problem solved.)
[08:39] <arraybolt3[m]> Wow, can I just say that Git done GBP style is fragile? Yikes.
[08:39] <arraybolt3[m]> I guess the fact that I'm learning it isn't helping...
[08:40] <tsimonq2> I need to get some rest, I simply can't focus and am not in the correct headspace right now
[08:40] <tsimonq2> I apologize 
[08:40] <tsimonq2> When I wake up with a fresh mind I'm hoping it'll be better
[08:41] <arraybolt3[m]> Sounds good. I'll hack away at it tonight, and hopefully leave a good base to build on.
[08:41] <tsimonq2> Thank you Aaron. Somewhat (oddly) comforting that something is actually going right in some part of my life right now...
[08:42] <tsimonq2> Being a young adult rocks and sucks at the same time. Infinite energy and hormones, limited money and decision making skills
[08:42] <tsimonq2> :P
[08:43] <arraybolt3[m]> Right?
[08:43] <arraybolt3[m]> As someone who's about the same age, I get you.
[08:43] <tsimonq2> Anyway, I'm going to visit Mr. Sandman for a bit
[08:44] <tsimonq2> watch as he compiles qtwebengine 
[08:44] <arraybolt3[m]> OK. (lol I don't think I can do that yet)
[08:44] <tsimonq2> tsimonq2: (Inside joke, qtwebengine legit takes 24h+ to build on a medium grade machine)
[08:44] <arraybolt3[m]> Oh great. And my machine is sub-low grade at this point...
[08:45] <tsimonq2> It is the redheaded step child of Qt modules imo
[08:45] <tsimonq2> ...morbidly obese redheaded stepchild :P
[08:46] <tsimonq2> Imagine Chromium, with Qt APIs... yeah you could probably build Chrome faster :P
[08:46] <arraybolt3[m]> Yeah but do you need 64GB RAM for QtWebEngine?
[08:46] <tsimonq2> I mean basically lol...
[08:47] <tsimonq2> Imagine you're 15 hours in and it throws you an OOM 
[08:47] <tsimonq2> (Out Of Memory Exception) :P
[08:47] <arraybolt3[m]> Oh no.
[08:47] <tsimonq2> I know you were joking 
[08:47] <tsimonq2> I wish it was a joke :P
[08:47]  * tsimonq2 likes to poke fun at it, ❤️ the authors
[08:48] <arraybolt3[m]> Moral of the story - HAVE LOTS OF SWAP.
[08:48] <tsimonq2> Anyway
[08:48] <tsimonq2> Good night 
[08:48] <tsimonq2> Talk later
[08:48] <arraybolt3[m]> Good night. Thanks again.
 "https://notes.lubuntu.me/..." <- Putting this at the tail end of our convo for my own reference...
[08:48] <tsimonq2> arraybolt3[m]: Of course :)
[08:51] <tsimonq2> IMO just add another column in LXQt checklist for links and use them `[Like this](https://example.com)`
[08:51] <tsimonq2> So like Debian | Ubuntu | Backports
[08:51] <arraybolt3[m]> That makes my screen explode in editor mode, and I can't turn word wrap off.
[08:52] <arraybolt3[m]> Thus why I did it this other way, so I could actually see what I was typing.
[08:52] <tsimonq2> Fair enough gn fr 👍
[10:07] <arraybolt3[m]> I done pooped out. I got libfm-qt into Debian, put a question for you on CodiMD, and need some sleep - my eyes literally feel sticky (which is weird). Let's both take another swing at it tomorrow. On the bright side, that's three less packages to handle, and we're on to Stage III in Debian if I'm understanding correctly!
[10:08] <arraybolt3[m]> (I've not yet submitted any merge requests since there's a problem I don't know the answer to - details are on CodiMD.
[10:08] <arraybolt3[m]> * on CodiMD.)
[18:07] <arraybolt3[m]> Hey guys!
 "Hey guys!" <- Hey!
[18:20] <kc2bez[m]> 👋
 "https://notes.lubuntu.me/..." <- Refresh of notes link for sprinters
[18:58] <tsimonq2> Hey!
[18:58] <arraybolt3[m]> Currently on lxqt-themes
[18:58] <tsimonq2> If anyone else is looking to dig into some packaging, now is the time 
[18:58] <tsimonq2> arraybolt3[m]: Very nice 
[18:58] <arraybolt3[m]> ls
[18:59] <arraybolt3[m]> (Wow, I'm gonna do that a lot I guess...)
 Ouch, I don't have the notes.lubuntu.me pass, @teward001 can you generate one for me when you can without hating me too much?
[19:00] <kc2bez[m]> I've been working on GiTea as I can fit it into my workday.
[19:01] <arraybolt3[m]> I also don't have GiTea, so I'm still working off of GitHub (and now Salsa), so @teward001 GiTea access would be appreciated while you're managing CodiMD for Roberalz.
[19:01] <kc2bez[m]> I can shoot you GiTea access
[19:02] <kc2bez[m]> I need to figure out an appropriate team
[19:02] <arraybolt3[m]> OK, that will come in handy once Debian's finished up with and we're on to finishing Kinetic's LXQt.
 You can do it for me too, I'm a little jealous xD (re @lubuntu_bot: (irc) <kc2bez[m]> I can shoot you GiTea access)
[19:04] <kc2bez[m]> sure
[19:04] <kc2bez[m]> I will send you both a DM here on Matrix so that it is encrypted.
 Thanks (re @lubuntu_bot: (irc) <kc2bez[m]> sure)
[19:59] <arraybolt3[m]> Simon Quigley (Developer): When we're done with upstreaming stuff to Debian, the next step is to sync from Debian into Kinetic, right? Or are we just re-forward-porting the Jammy work back into Kinetic?
 "Simon Quigley (Developer..." <- Debian -> Kinetic -> Backports
[20:11] <tsimonq2> If either one of the three hits a freeze, take the changes into consideration carefully before doing the merge in that direction 
[20:12] <tsimonq2> Debian does freeze and we need formal transition slots at all times, Ubuntu has freeze dates but no formal transition slotting, and Backports is well, whatever we decide :)
[20:13] <arraybolt3[m]> OK, good to know.
[20:13] <arraybolt3[m]> Also, whenever you review my work on Debian's packaging, look very carefully, since GBP is throwing me in circles like sbuild never could, so I keep having to go back and fix things.
[20:15] <arraybolt3[m]> Also, Simon Quigley (Developer) In Lubuntu, we copyright everything under Lubuntu Developers. That doesn't appear to be what Debian does, so I've left out any hint of Lubuntu Developers in the copyright file. However, I'm not sure who or what to put in it's place, which is a bit of a problem since qtxdg-tools *was packaged by Lubuntu specifically, and has no other copyright owners for debian/\*.* How exactly is this supposed to be
[20:15] <arraybolt3[m]> done?
[21:16] <arraybolt3[m]> Well, I hate to say it, but I've accidentally been doing GBP all wrong, and am going to have to restart all my work on that end from scratch. Sorry for the delay, but I think I've almost got a good handle on this and things will hopefully start going faster from here.
[21:18] <Eickmeyer[m]> Hey everyone, the quassel SRU for Jammy is getting ghosted. Not much more I can do.
[21:18] <arraybolt3[m]> That's fine. We got it better than it was before!
[22:09] <arraybolt3[m]> Simon Quigley (Developer): Redoing libsysstat, it looks like the last change we made in Ubuntu was to sync it with Debian? If so, do I need to do anything to debian/experimental at all with libsysstat?
[22:15] <tsimonq2> Nope
 "Also, Simon Quigley (Developer..." <- Lubuntu Developers 
[22:15] <arraybolt3[m]> Nice.
[22:15] <arraybolt3[m]> (OK, will use that as the copyright.)
[22:23] <arraybolt3[m]> Simon Quigley (Developer): I've discovered there's three methods of importing upstream code with GBP - there's the tarball method, the git method, and the hybrid method (with --upstream-vcs-tag). Last time I tried to use the Git method and things went very poorly, presumably since that wasn't the method we used originally. So which method should I use, tarball or hybrid?
[22:24] <tsimonq2> I think the other packages use tarball
[22:24] <tsimonq2> I'd double check that for sure though 
[22:24] <arraybolt3[m]> That explains a LOT. Trying to use Git merges just kept erroring out and corrupting stuff. How do I double check?
[22:24] <tsimonq2> gbp.conf mostly :)
[22:25] <arraybolt3[m]> Oh... OK, thank you!
[22:25] <tsimonq2> Of course 
[22:31] <arraybolt3[m]> Simon Quigley (Developer): I'm not sure what I'm looking for that would tell me whether or not Git is being used at the upstream source in gbp.conf, and the manpages are being very unhelpful in this particular instance. What would tell me, "Ah! This is using tarballs" or "Ah! This is using Git"?
[22:34] <arraybolt3[m]> I don't see any mention of a tag or branch from out of LXQt's upstream, so I think it's tarball, also. And gitk output and merge warnings lead me to believe this, too. So I'm gonna try it.
 "Hey everyone, the quassel SRU..." <- Thanks for trying. We can get back to it next week. 
 "Simon Quigley (Developer): I'm..." <- The git history 
[23:03] <tsimonq2> Run `git log upstream`
[23:18] <arraybolt3[m]> Simon Quigley (Developer): Oh, smart! Thank you!
[23:33] <tsimonq2> Of course :)
[23:37] <arraybolt3[m]> Alright! One package done right! WOOT! Now I'm not sprinting in circles anymore!
[23:37] <arraybolt3[m]> OK, on to the next one. (I'm finally getting a hang of this, I think.)
[23:37] <arraybolt3[m]> s/a/the/
[23:38] <arraybolt3[m]> (Is it a hang? the hang? I don't actually know, but you know what I'm trying to say.)
[23:41] <kc2bez[m]> Not sprinting, just hanging around.
[23:42] <kc2bez[m]> 😂