[00:06] <arraybolt3[m]> Si
[00:06] <arraybolt3[m]> Wow, hit Enter instead of Tab...
[00:06] <arraybolt3[m]> Simon Quigley (Developer): Any progress on pushing the Calamares packaging repo?
[16:30] <arraybolt3[m]> Good evening (or whatever it is in your part of the world)!
[16:46] <LeoK[m]> <arraybolt3[m]> "Good evening (or whatever it..." <- Good evening to you as well.
[16:47] <arraybolt3[m]> Leo K: I'm still not quite able to get the UEFI patch merged in, so would you like me to pastebin it and send it? It should be applied to /lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py (I believe, double-check me on that).
[16:53] <LeoK[m]> <arraybolt3[m]> "Leo K: I'm still not quite..." <- Yes you can send me - good to have basic instructions as I am not a developer
[17:02] <tsimonq2> Good morning :)
[17:02] <tsimonq2> Yes I can import that stuff in today
[17:04] <LeoK[m]> tsimonq2: Good morning and once again - great idea!
[17:05] <arraybolt3[m]> Leo K: https://termbin.com/jc0c
[17:05] <arraybolt3[m]> Copy the contents into a file names uefi.patch.
[17:05] <LeoK[m]> arraybolt3[m]: got it
[17:05] <arraybolt3[m]> Then apply it to a live system with "sudo patch /lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py uefi.patch"
[17:05] <arraybolt3[m]> Then try to install, and it should work on a UEFI system.
[17:07] <LeoK[m]> arraybolt3[m]: hang on a few
[17:09] <arraybolt3[m]> (Also, whoever invented termbin.com was a genius - piping to netcat is so much easier than copypasting into a website. URLs are short and easy to type, too, and they delete data after a month so you don't feel bad about eternally eating a chunk of space on someone else's server. Woot!)
[17:18] <LeoK[m]> install with ppatch running on barebone uefi+secure system
[17:20] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Do you have a diff that includes packaging?
[17:21] <tsimonq2> Or would you prefer a Git workflow?
[17:22] <LeoK[m]> restart - holding breath..
[17:23] <LeoK[m]> I owe arraybolt3 one beer or maybe coffee..booted np
[17:25] <arraybolt3[m]> Simon Quigley (Developer): I think I just need to uscan the packaging repo, finagle Quilt and then send the finished patch. I think that's a diff? And then I can git push and send a PR, so that would be Git? Which one works for you?
[17:25] <arraybolt3[m]> Leo K: LOL I actually don't drink either coffee or beer...
[17:25] <arraybolt3[m]> Le
[17:25] <arraybolt3[m]> Bah, Enter instead of Tab again...
[17:25] <arraybolt3[m]> Leo K: Glad it worked!
[17:26] <LeoK[m]> arraybolt3[m]: Icelandic water is cool 
[17:26] <arraybolt3[m]> Pun detected!
[17:27] <LeoK[m]> the test was with yesterdays (15-6) ISO
[17:27] <arraybolt3[m]> Simon Quigley (Developer): I think by "diff" you mean "arc diff". I couldn't get Arcanist working on my system, so I guess Git it is.
[17:45] <tsimonq2> <arraybolt3[m]> "Simon Quigley (Developer): I..." <- pull-lp-source then make your changes then debuild -S -d and use debdiff between the two dsc files 
[17:46] <arraybolt3[m]> And then I frobnicate the dsc files, right? Sorry, I have no idea what you just said...
[17:47] <tsimonq2> 1. Get existing package using pull-lp-source
[17:47] <tsimonq2> 2. cd into the packaging and make changes 
[17:47] <tsimonq2> 3. Run debuild -S -d
[17:48] <tsimonq2> 4. cd .. and run debdiff ORIG.dsc NEW.dsc
[17:48] <arraybolt3[m]> Ah, OK. That makes sense. Thanks!
[17:49] <tsimonq2> No problem, lmk how I can help 
[17:49] <arraybolt3[m]> Is pull-lp-source still right in Kinetic? The Ubuntu manpages website makes it look like it got changed to pull-pkg.
[17:49] <tsimonq2> Maybe, still works for me on Kinetic
[17:49] <arraybolt3[m]> 👍️
[17:52] <kc2bez[m]> arraybolt3[m]: I hadn't realized there was a change there either and I have used pull-lp-source this cycle so I can confirm it to work.
[17:53] <arraybolt3[m]> kc2bez[m]: Makes sense. It looks like it's been pull-pkg since 20.04, I'm guessing that pull-lp-source was just made part of it.
[17:53] <arraybolt3[m]> Yep, confirmed.
[18:22] <tsimonq2> arraybolt3: Packaging pushed, all clear.
[18:22] <tsimonq2> (Keep up work like this and you may just earn yourself commit access ;) )
[18:23] <arraybolt3[m]> tsimonq2: Let's wait until I really know what I'm doing. Last thing I need is to shatter all of creation with one poorly placed typo.
[18:23] <tsimonq2> Just as something to look forward to, I didn't say now
[18:23] <tsimonq2> :)
[18:23] <arraybolt3[m]> I knew that. Just making a joke.
[18:24] <tsimonq2> I mean, what could go wrong? :P
[18:24] <kc2bez[m]> You are doing great arraybolt3 !
[18:24] <arraybolt3[m]> Thanks!
[18:24] <tsimonq2> arraybolt3: Let me know when you have a PR using one of the several options and I'll get it merged + uploaded. :)
[18:24] <kc2bez[m]> tsimonq2: We only have root access 🤷
[18:25] <tsimonq2> kc2bez[m]: haha commit go brr
[18:25] <tsimonq2> (Gen Z joke, carry on)
[18:25] <arraybolt3[m]> kc2bez[m]: Just keep your fingers off the the r, the m, the -, the f, and the /, and you should be good.
[18:25] <tsimonq2> arraybolt3[m]: Now you need --no-preserve-root to actually make that command hurt :P
[18:25] <kc2bez[m]> tsimonq2: I got it even though I am old.
[18:25] <arraybolt3[m]> s/the the/the
[18:26] <tsimonq2> Also...
[18:26] <tsimonq2> In case you're looking for an easy way to really get going arraybolt3 ...
[18:26] <arraybolt3[m]> tsimonq2: Thank goodness. You can actually brick some MSI motherboards with that one.
[18:26] <tsimonq2> I can let you hack away at some of the backports packaging
[18:26] <tsimonq2> arraybolt3[m]: yeah exactly
[18:27] <tsimonq2> arraybolt3: All you need to do is follow this order: https://github.com/lxqt/lxqt/wiki/Building-from-source#Compiling
[18:27] <tsimonq2> arraybolt3: The PPA is here: https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging/+packages
[18:27] <tsimonq2> arraybolt3: I have sbuild set up as per here: https://wiki.ubuntu.com/SimpleSbuild and http://wiki.debian.org/sbuild is also good reading, but whatever works
[18:28] <tsimonq2> Basically, checkout ubuntu/kinetic, create a new backports/jammy branch based on top of that, add a new changelog entry as I've previously done (using the same scheme pretty please), run a test build with that PPA as a build repo, and verify no further packaging changes are required.
[18:29] <tsimonq2> This is exactly how I got my first packaging experience. It makes you really well-rounded.
[18:29] <tsimonq2> I would 100% suggest at least attempting to dig into some of that while I'm AFK today and someone can answer questions (or I can, when I get back).
[18:29] <tsimonq2> The vast majority of the packaging changes have already been made.
[18:30] <arraybolt3[m]> Wow, that looks fun! And it's in backports-staging, so if something blows up no one gets hurt, right? Or should I try it in my own PPA just for safety's sake?
[18:30] <tsimonq2> You don't have upload access to that PPA yet, but you can do one of two things...
[18:31] <tsimonq2> A) Create a PPA that depends on backports-staging and test your builds there.
[18:31] <tsimonq2> B) Create a local "PPA" to house packages in the meantime.
[18:31] <tsimonq2> (The latter of which is documented in wiki.u.c./SimpleSbuild linked above.)
[18:31] <tsimonq2> I usually do the latter if I'm rapidly updating a stack in an overlay PPA.
[18:32] <tsimonq2> I do the former if I'm dealing directly with the Ubuntu archive.
[18:32] <tsimonq2> There's benefits (more arches) and downsides (publishing time) to PPAs.
[18:32] <arraybolt3[m]> I like it. Then if everything works someone can check it and make sure it's good, then copy it into the official PPA if it's all good?
[18:33] <arraybolt3[m]> OK, sounds like a plan. I do need to finish the UEFI stuff, and then I have a project in Ubuntu Studio (PipeWire integration) to fight with, then I should be ready to try battling LXQt.
[18:35] <tsimonq2> Yes, you can either propose the changes via Git and I can GPG sign it locally, or you can upload to your PPA and I can use local tooling to copy the source over via the Launchpad API.
[18:35] <tsimonq2> Either or works, I personally prefer the former if you're newer but as things progress the latter is more scalable.
[18:35] <arraybolt3[m]> 👍️
[18:36] <tsimonq2> arraybolt3[m]: Sounds good.
[18:37] <arraybolt3[m]> Hey, while I'm right here, there's a bug somewhere in LXQt that's causing the "Open in terminal" button in PCManFM-Qt to throw an error related to a missing "xterm".
[18:37] <Eickmeyer[m]> It's Simon's Fault.
[18:38] <arraybolt3[m]> Eickmeyer: Ey!
[18:40] <lubot> [telegram] <teward001> *hands Simon the "Use git workflows!" edict
[18:40] <lubot> [telegram] <teward001> :P
[18:41] <lubot> [telegram] <teward001> *yawns* anyways hello
[18:41] <tsimonq2> He's new, he needs to be well-rounded. :P
[18:41] <tsimonq2> arraybolt3[m]: ooh, fun
[18:41] <arraybolt3[m]> OK, so what do I do if uscan decided to tell me "uscan warn: In debian/watch no matching hrefs for version 3.3.0~git20220610 in watch line https://github.com/calamares/calamares/tags (?:.*/)?v?(\d[\d.]*)\.tar\.gz"?
[18:42] <arraybolt3[m]> (Matrix slaughtered my hand-typed regex.)
[18:42] <lubot> [telegram] <teward001> here simon you have work.  https://askubuntu.com/questions/1414369/how-to-disable-lubuntus-graphical-grub-theme   i am giving this to you to help users with their issues.  or to whomever wants to help.
[18:43] <lubot> [telegram] <teward001> but you first Simon :P
[18:43]  * arraybolt3[m] snatches the task from teward, turns it into a paper airplane, then bombards teward with it
[18:46] <tsimonq2> arraybolt3[m]: You have to manually craft that tarball when you make a new one, however, in this case just grab the one from the archivre
[18:46] <tsimonq2> s/archivre/archive/
[18:46] <arraybolt3[m]> Oh OK. With pull-lp-source, right?
[18:46] <tsimonq2> !upkg calamares -> link to that repo -> tars right there
[18:46] <tsimonq2> You can do that, or here:
[18:46] <tsimonq2> https://launchpad.net/ubuntu/+source/calamares/3.3.0~git20220610-0ubuntu1
[18:46] <tsimonq2> https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/calamares/3.3.0~git20220610-0ubuntu1/calamares_3.3.0~git20220610.orig.tar.gz
[18:47] <tsimonq2> (You only really need the orig file in this case, the other files don't particularly matter if you're working off of a Git repository...)
[18:48]  * tsimonq2 -> AFK, ping and I can answer at an async pace with questions
[18:48] <arraybolt3[m]> Oh, by the way, as far as Falkon's viability as a default web browser, I'm actually really liking it so far.
[18:49] <tsimonq2> Yeah?
[18:49] <arraybolt3[m]> Using it in my development VM as my sole browser.
[19:19] <arraybolt3[m]> Whew, finally finished the debuild! Looks like it worked!
[19:20] <arraybolt3[m]> After the "git add -A" step, do I then do a "git commit"? I don't see that in the packaging tutorial.
[19:21] <arraybolt3[m]> I think I'm supposed to git commit, then git push, then pull request.
[19:22] <arraybolt3[m]> (Also, when filling out the Quilt DEP-3 header, I wasn't sure what to put in the Last-Update field, but it was autofilled with a date, so I left it as-is.)
[19:22] <arraybolt3[m]> (After removing the documentation message in the template, that is.)
[19:23] <tsimonq2> You're on the right track, keep going :)
[19:24] <arraybolt3[m]> Holy cow, that can't be right. It looks like the Debian folder got loaded with twenty tons of junk from the debuild step.
[19:25] <arraybolt3[m]> This is literally going to upload a built Calamares binary. What did I miss?
[19:25] <Eickmeyer[m]> Try executing dh_clean real quick.
[19:26] <arraybolt3[m]> Eickmeyer: Thank goodness. That wasn't in the tutorial. Thank you!
[19:26] <Eickmeyer[m]> np
[19:26] <arraybolt3[m]> Also, how do i undo "git add -A" so I can try it again with the now cleaned repo?
[19:27] <Eickmeyer[m]> Well, if you have git-cola installed, you can open the folder with git-cola . and it'll help you clean it up.
[19:29] <arraybolt3[m]> Eickmeyer: You just saved my day. Thank you! Unstaged everything and that appears to have fixed it.
[19:29] <Eickmeyer[m]> Yep, that would do the trick.
[19:29] <Eickmeyer[m]> git-cola has saved my bacon so many times it's not funny.
[19:30] <arraybolt3[m]> LOL
[19:31] <arraybolt3[m]> Wow, I like git-cola a lot. I may use it instead of the Git command line from now on.
[19:31] <Eickmeyer[m]> Honestly, git-cola taught me git in many ways since it's basically a graphical front-end. It can also create patches.
[19:32] <Eickmeyer[m]> git on easy mode.
[19:33] <arraybolt3[m]> Wow, it even did the git push for me. That's awesome. Thanks again!
[19:38] <arraybolt3[m]> Simon Quigley (Developer): Whew! UEFI patch created, pull request made. Look it over carefully, some of the stuff that it looks like is going to get changed is things I wouldn't expect, and I suspect that the debuild step left some junk behind, even after the dh_clean.
[20:08] <tsimonq2> <arraybolt3[m]> "Simon Quigley (Developer): Whew!..." <- Link?
[20:08]  * tsimonq2 tries to find
[20:14] <tsimonq2> Requested changes 
[20:18] <kc2bez[m]> <arraybolt3[m]> "This is literally going to..." <- Maybe this `rm -rf !(debian) .pc/ # requires bash and `shopt -s extglob``
[20:53] <arraybolt3[m]> Dan Simmons: Nope, ran that.
[20:54] <arraybolt3[m]> And then I ran "shopt -s extglob" and then ran the rm command again.
[20:54] <arraybolt3[m]> Simon Quigley (Developer): It's a PR on GitHub.
[20:55] <arraybolt3[m]> Dan Simmons: Did I need to have the shopt -s extglob in my bashrc before running the rm command the first time?
[20:56] <arraybolt3[m]> Simon Quigley (Developer): Changes noted, will do.
[21:12] <arraybolt3[m]> Uh... I made the changes, committed, then pushed, but I seem to think I shouldn't need to make a second pull request. What do I do?
[21:13] <arraybolt3[m]> Oh wait, the PR picked up my changes. Nevermind.
[21:15] <arraybolt3[m]> Dan Simmons: Oh, I'm realizing what you replied to. Eickmeyer came in and saved me with a "dh_clean".
[21:19] <kc2bez[m]> `rm -rf !(debian) .pc/` cleans up your source files too. everything after the # is a comment. You need to have bash and shopt-s extglob
[21:19] <kc2bez[m]> As long as you got it.
[21:19] <arraybolt3[m]> Dan Simmons: But I even ran shopt -s extglob, and then ran the rm command (though I did run the rm command once, then ran the shopt, then ran rm again).
[21:20] <arraybolt3[m]> Dan Simmons: Did my first rm mess it up?
[21:20] <arraybolt3[m]> (I'm guessing that's probably what happened.)
[21:21] <arraybolt3[m]> (And I'm using Bash. I don't use anything but Bash.)