[00:49] <arraybolt3[m]> Dan Simmons: That sounds like exactly what I want! Though it should be noted that the configuration changes make our config work with Calamares 3.3.0, but break compatibility with 3.2.x.
[00:49] <arraybolt3[m]> (At least, that's the intended result.)
[00:50] <kc2bez[m]> arraybolt3[m]: We can take care of that in the packaging. 
[00:52] <kc2bez[m]> https://github.com/lubuntu-team/calamares-settings-ubuntu/blob/ubuntu/kinetic/debian/control#L26
[00:55] <arraybolt3[m]> Thanks! This is my first time using Git (I do program, but I used to do it without any version control or stuff like that), so you might have to help me figure out some of what I'm doing, but hopefully I'll figure it out. I'm thinking, fork that repository, replace the necessary files, and then can I use Pull Request to ask to merge my changes back into your repository?
[00:56] <kc2bez[m]> Yes, that is a good way to summarize.
[00:57] <kc2bez[m]> For good hygiene each thing you change should be a commit.
[00:58] <arraybolt3[m]> OK. Uh... crud. I'm doing that in my custom Git repo containing the /etc/calamares/modules directory, but I'm gonna lose all of that when I move it over to GitHub...
[00:58] <kc2bez[m]> Keep doing what you are doing and testing.
[00:59] <arraybolt3[m]> OK. Worst case scenario, I'll stick it in another GitHub repo all of its own and all the commit history will be there, and then everything can just be glommed into one massive "Update config for Calamares 3.3.0" commit for putting it in the main repo. (I think that's right?)
[01:02] <kc2bez[m]> Once you get it where you want you can create a new fork and just edit the files one at a time. I guess that is what I should have said, each file you edit should be a commit. You should have a changelog entry for each thing too.
[01:03] <arraybolt3[m]> Oh, I get it. That makes sense. So, one commit per file, not per logical change? I ask because at least one of my changes was moving config from fstab.conf to mount.conf, since that's where Calamares expects to find some of the config data now. So that changed two files in one logical change.
[01:04] <kc2bez[m]> Yeah, that makes sense to be one commit.
[01:04] <kc2bez[m]> @teward001 it looks like the cert on phab expired.
[01:06] <kc2bez[m]> arraybolt3 @arraybolt3:matrix.org:  when phab comes back around you will want to look at this https://phab.lubuntu.me/w/packaging/packaging-requirements/
[01:07] <arraybolt3[m]> Dan Simmons: OK. I can just force my way into Phab despite the invalid certificate, right? Or is that dangerous from a security perspective?
[01:07] <kc2bez[m]> You likely have some of that done already 
[01:08] <arraybolt3[m]> Actually, I've never made a package before...
[01:08] <arraybolt3[m]> But I should learn how to do that.
[01:08] <kc2bez[m]> arraybolt3[m]: It is just an expired let's encrypt so your call. 
[01:09] <kc2bez[m]> arraybolt3[m]: Hopefully we are guiding you through that ;) 
[01:09] <arraybolt3[m]> OK. As long as it won't risk leaking account data, I'm fine with clicking scary buttons to make things work.
[01:09] <arraybolt3[m]> kc2bez[m]: Thanks! This is really fun, and hopefully it will work by the end of it. I'm just going through all the files, looking to see what's changed and how, then rewriting the files to do the same thing with the new syntax and option placement.
[01:11] <kc2bez[m]> arraybolt3[m]: Sounds good. With a little local testing before we upload we should know if it works, at least generally. 
[01:11] <arraybolt3[m]> True. I'm not going to upload something untested. If it won't at least give me a good full disk install and a good manually partitioned install, it's no good.
[01:29] <arraybolt3[m]> OK, so, I hit a problem. Even with the updated config, I'm getting the exact same error. It told me that "name ssd_extra_mount_options" is not defined in /usr/lib/x86_64-linux-gnu/calamares/modules/fstab/main.py, line 417. So I went there, and I can see the code that's throwing a fit... but I don't know Python and am not sure what to do from here. My fstab.conf has nothing about "ssdExtraMountOptions" - I moved that into
[01:29] <arraybolt3[m]> mount.conf and formatted it as needed.
[01:33] <arraybolt3[m]> OK, I just tried modding the Python code to remove "ssd_extra_mount_options" entirely since it looked unused. Let's see how this blows up.
[01:33] <kc2bez[m]> arraybolt3[m]: It might be time for that upstream bug with logs and settings attached. 
[01:34] <arraybolt3[m]> That makes sense. I'm always a bit scared of filing upstream bugs since the first time I did that it got closed instantly because I made a boffo...
[01:34] <arraybolt3[m]> But I guess I'll do that if needed. Seems odd, though, if this isn't our fault, this should have been easily caught in testing, I would have thought.
[01:35] <arraybolt3[m]> (Wow, my mod made it pass the fstab bit?!? Weird. Wonder how malformed fstab is going to be now.)
[01:36] <kc2bez[m]> arraybolt3[m]: Nobody else is running this version. It hasn't been released yet. 
[01:36] <arraybolt3[m]> Ah. That makes sense. I didn't realize that.
[01:37] <kc2bez[m]> Bleeding edge ;) 
[01:37] <kc2bez[m]> Keep the band-aids handy :D
 "Nobody else is running this..." <- The only other human is ade lol
[02:52] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Are you planning on sticking around enough to become a Lubuntu Member?
[02:52] <tsimonq2> Definitely wouldn't be a bad thing ;)
[02:53] <kc2bez[m]> I hope you do ;) 
[02:53] <tsimonq2> ^^^^^
[03:03] <arraybolt3[m]> Simon Quigley, Dan Simmons: I'm hoping to!
[03:05] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Keep track of when you first popped in the channel and date it out minimum 3 months 
[03:05] <tsimonq2> Now, you'll hear from people that oh, 6 months is the minimum, 6 months is recommended, whatever 
[03:05] <tsimonq2> I would absolutely be a hypocrite if I enforced that 
[03:06] <tsimonq2> When I first started contributing with all that 13 year old crackhead energy I did it in three months flat, usually takes people six :)
[03:06] <tsimonq2> As long as you can justify your contributions as significant and sustained and we can trust you to represent the project, you're eligible 
[03:07] <tsimonq2> And I definitely think you're on your way 
[03:07] <arraybolt3[m]> OK. I have a document where I'm tracking everything so I can survive the interview. I'm kinda scared LOL
[03:08] <tsimonq2> Nah you're good. Unless you go for Lubuntu Developer, in that case prepare for the two hour roasting session with myself, teward, and Dan ;]
[03:08] <tsimonq2> s/]/)/
[03:09] <tsimonq2> Lubuntu Member is a breeze as long as you show your face enough times 
[03:09] <arraybolt3[m]> I might do that, but that's probably WAY far off.
[03:09] <tsimonq2> Yeah go for member first 
[03:10] <tsimonq2> Anyway, one last thing, and that's, don't be afraid to speak up if you're not getting something. My DMs are open too if it's long-form
[03:10] <tsimonq2> We all started right where you are 
[03:11] <arraybolt3[m]> OK, sounds good. So far things are going "smoothly" (well, except for the fact that Calamares is crashing for goodness-knows-why with a very obscure error message), but I definitely am thankful for help. I'll probably need some assistance with packaging.
[03:12] <tsimonq2> Sounds good. If it makes you feel any better I picked it up after basically a year or two with no packaging experience and it came right back to me after the first upload or two 
[03:12] <tsimonq2> So please, reach out 
[03:12] <tsimonq2> Myself, Thomas, Dan, etc.
[03:13] <tsimonq2> Well of course Cala will crash, it's early alpha you know ;) welcome to the team that gets to fix it! Yay!
[03:13] <tsimonq2> Do you have a longer error message that you can paste?
[03:18] <arraybolt3[m]> tsimonq2: Yeah, but it's all but useless. My config file is good, I think, and the code that's going wonky is a SO file, if I'm not mistaken (not a python script), so... But, I'll paste it just in case it helps. You'll also want the Calamares log if you want to make heads or tails of it.
[03:18] <arraybolt3[m]> ERROR: Installation failed: "Could not run command."
[03:18] <arraybolt3[m]>  - message: "Could not run command."
[03:18] <arraybolt3[m]>  - details: The commands use variables that are not defined. Missing variables are: i.
[03:19] <arraybolt3[m]> (And in case you're wondering, "What command?", the answer is: Yeah, right? Who knows?!?)
[03:19] <tsimonq2> Fun. Have your config anywhere yet?
[03:20] <arraybolt3[m]> Not anywhere public - I was waiting to upload it until I got one good install, but that looks hopeless, so I'll upload what I've got and we'll see what happens.
[03:20] <tsimonq2> I'll grab it then - I have a few tricks up my sleeve
[03:21] <tsimonq2> If nothing else I'll just git bisect it 
[03:21] <tsimonq2> No sweat off my brow :)
[03:22] <arraybolt3[m]> OK. I'll fight with GitHub and see if I can make it happen.
[03:22] <arraybolt3[m]> (Git bisect is a good idea.)
[03:24] <tsimonq2> git clone existing-repo... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/14a80ed54e28f08231347fac6b3be6f9fc571891)
[03:24] <tsimonq2> That's just off the top of my head, take it with a grain of salt
[03:25] <arraybolt3[m]> Nice.
[03:25] <tsimonq2> Hope it helps 
[03:26] <arraybolt3[m]> I have yet to connect git to GitHub though, I'll probably need to do that, right?
[03:27] <tsimonq2> Nope, you don't have to connect anything like a service 
[03:27] <tsimonq2> Git is distributed and scalable 
[03:27] <arraybolt3[m]> OK. But I do need some method of authentication - I'm looking into a GitHub Personal Access Token ATM.
[03:27] <arraybolt3[m]> (ATM = at the moment - there's no Personal Access Token Automated Teller Machine...)
[03:28] <tsimonq2> SSH keys > auth keys unless it's a server 
[03:28] <tsimonq2> arraybolt3[m]: Oh I'm Gen Z, I'll lyk if I don't get ya ;)
[03:29] <tsimonq2> tsimonq2: If you have the money, a Yubikey is a great investment. They're standard issue at Altispeed (my employer, shameless plug for asknoahshow.com)
[03:29] <arraybolt3[m]> I'm looking into one of those, but for now it's kinda expensive. But that seems like a good idea for tin the future.
[03:30] <arraybolt3[m]> SSH keys > auth keys - meaning better than?
[03:30] <tsimonq2> We'll pay for one if you become a Lubuntu Member :)
[03:30] <tsimonq2> arraybolt3[m]: Yes
[03:31] <arraybolt3[m]> You can delete an SSH key from GitHub if you lose it, right?
[03:31] <kc2bez[m]> Yes
[03:31] <arraybolt3[m]> OK, then I'll do that then.
[03:32] <kc2bez[m]> Here are the add instructions https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
[03:32] <arraybolt3[m]> I'm there, but I didn't see anything about being able to remove the key, and I hate when there's stuff hanging around that I can't delete that I'll never use again.
[03:32] <kc2bez[m]> Basically generate your key and add your pub key to Github 
[03:33] <tsimonq2> arraybolt3[m]: I've done it before, you'll see once you add it 
[03:33] <kc2bez[m]> There is a big red X for delete after you add them 
[03:33] <arraybolt3[m]> OK, nice.
[03:39] <arraybolt3[m]> Alright, SSH key done.
[03:41] <arraybolt3[m]> OK, it looks like it's working!
[03:42] <tsimonq2> I'm going to go AFK for the night, thanks for everything guys :)
[03:42] <tsimonq2> Tomorrow my goals are to get the images building and to at least start the backport staging process
[03:42] <guiverc> thanks & have a good night tsimonq2 
[03:43] <arraybolt3[m]> Simon Quigley: Thank you! Good night!
[03:43] <kc2bez[m]> Sounds awesome! I going to spend some time horizontal too. I too shall return tomorrow.
[03:44] <tsimonq2> Thanks guys :) take care 
[03:45] <arraybolt3[m]> And I'll see if I can figure out this crazy Git thing and get something useful uploaded.
[04:08] <arraybolt3[m]> I DID IT! https://github.com/ArrayBolt3/calamares-settings-ubuntu Wow, that was hard, but there it is.
[04:10] <guiverc> well done arraybolt3[m]
[04:10] <arraybolt3[m]> guiverc: Thanks!
 i'll fix it in a bit - i blame letsencrypt xD (re @lubuntu_bot: (irc) <kc2bez[m]> @teward001 it looks like the cert on phab expired.)
 *yawns loudly*
[15:55] <arraybolt3[m]> Hey, am I the only one who Discourse is throwing a small fit with?
[15:56] <arraybolt3[m]> It keeps glitching in weird and unexpected ways (likes that I know are applied aren't showing up, notifications I've already read are popping up, pages are sometimes just not loading right, topics appearing and disappearing)
[15:57] <kc2bez[m]> I haven't noticed those issues.
[15:57] <LeoK[m]> I cannot even sign in...no error just twirling
[15:58] <arraybolt3[m]> Hmm, maybe we all need to clear our cookies and cached site data from Discourse to see if that straightens it out.
[15:59] <kc2bez[m]> Clearing cache is always a good start.
[15:59] <LeoK[m]> no luck but now the certificate warning 
[15:59] <arraybolt3[m]> And now the SSL cert on Discourse is dead too.
[16:00] <kc2bez[m]> Ah, that makes sense why it was acting weird.
[16:01] <kc2bez[m]> Thomas indicated he would get them renewed when he could.
[16:33] <tsimonq2> Good morning :)
[16:44] <LeoK[m]> Daily ISO build failed
[16:45] <tsimonq2> Alright, give me some Matrix thumbs up/down... too early to roll up a new tar? Here are the new changes that would be pulled: https://github.com/calamares/calamares/compare/821a62ffbb24955287d10205f62ff62301c76eb7...calamares
[16:46] <tsimonq2> (thumbs up means yes go for it)
[16:50] <kc2bez[m]> I see some fixes there but I expect a couple of key ones are still to come. Namely the undefined variable in the fstab module and a fix to the welcome module.
[17:24] <arraybolt3[m]> I'd say build it. If I get asked to use the absolute latest version in the bug report I'm writing, that will come in handy.
[17:29] <arraybolt3[m]> Bug report on ssd_extra_mount_options bug: https://github.com/calamares/calamares/issues/1980
[17:30] <arraybolt3[m]> And I had to typo the title. Lovely.
[17:30] <arraybolt3[m]> OK fixed the title.
[18:21] <kc2bez[m]> Thanks for filing the bug arraybolt3 @arraybolt3:matrix.org: 
[21:08] <tsimonq2> LXQt just migrated 
[21:08] <tsimonq2> I'll kick the ISO within the hour 
[22:02] <kgiii> Hmm... Discourse appears down. Let me do some additional testing.
[22:02] <kc2bez[m]> It is already mentioned here, the certificate has expired. :(
[22:04] <kgiii> I see it mentioned now. I can kinda load it (trusting the cert) in PaleMoon. Chromium doesn't even give me that option.
 HSTS is a bitch isnt it
[22:51] <kc2bez[m]> Yes
 the issue lies in Certbot getting an unknown response from their servers
 i'm sort of waiting for a reply from one of their admins who can stab the backend
[22:51] <kc2bez[m]> Gotcha.
 i also have the <sarcasm>luxury</sarcasm> of having to majorly un-[CENSORED] one teams data feed offering at FT job.  and itd MAJORLY fubar so what FUN.  >.>
[22:54] <kc2bez[m]> Sounds swell.
[22:56] <kgiii> Yeah, I use HSTS on my sites as well. On the other hand, I also use a control panel - like cPanel - which happily deals with LetsEncrypt for me.
 kgiii: which only is as good as LE not giving an invalid response from their backends to the client
 OTHERWISE LE is set on our side with autorenew and NGINX reload hooks sooooo
 *blames LE for this one*
[22:58] <kgiii> Yeah, but if that happens it's someone else's job to fix it. ;-) 
[22:59] <kgiii> Hmm... Lemme check something...
[23:19] <kgiii> FWIW, I can add and renew LE certificates via cPanel. I didn't check anything else. 
[23:20] <kgiii> IE In other words, they may only be partially broken.