[00:28] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Not seeing your changes reflected in the PR
[00:28] <arraybolt3[m]> Eh? I can see them, hold on one sec...
[00:28] <arraybolt3[m]> Simon Quigley (Developer): Can you see the "Prepared for merge with Lubuntu" commit underneath the instructions you gave me?
[00:29] <arraybolt3[m]> Simon Quigley (Developer): It's showing up in Falkon for me.
[00:30]  * arraybolt3[m] uploaded an image: (29KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/AGtddMzBOFXOouokQmTGXhIl/image.png >
[00:30] <tsimonq2> Hmmm
[00:30] <arraybolt3[m]> Simon Quigley (Developer): If I click on the words "Prepared for merge with Lubuntu", I get a list of diffs showing the changes.
[00:31] <tsimonq2> Merged.
[00:31] <tsimonq2> Dan Simmons: feel free to upload if you get to it first 
[00:32] <arraybolt3[m]> Simon Quigley (Developer): Thank you! Wow, you guys taught me SO MUCH.
[00:37] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Of course! There's still a lot to come. Just wait until you get to have fun with symbols. ;)
[00:38] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: https://phab.lubuntu.me/w/lubuntu-dev/
 "Dan Simmons: feel free to upload..." <- I don't have any power. 
[00:41] <kc2bez[m]> We had some storms roll through. One of the poles down the street is broken in half. It might be a little while.
[00:43] <arraybolt3[m]> Dan Simmons: Good grief, are you OK? We had a storm come through where we live the other day that spun off tornadoes that destroyed a town states away.
[00:43] <arraybolt3[m]> https://en.wikipedia.org/wiki/2021_Western_Kentucky_tornado
[00:44] <tsimonq2> kc2bez[m]: All good
[00:44] <tsimonq2> Half of Green Bay doesn't have power either 
[00:44] <kc2bez[m]> We are all safe here, there were some tornadoes spotted a couple of towns over but none here that I know of.
[00:44] <tsimonq2> We're still under a state of emergency in Brown Counties 
[00:44] <tsimonq2> s/Counties/County/
[00:45] <arraybolt3[m]> Simon Quigley (Developer): Man. Over where I'm at, we had a lot of rain for a few days and now baking heat, but no disasters. Sorry this is happening to you two!
[00:46] <tsimonq2> At least *our house* didn't lose power :)
[00:46] <tsimonq2> Dan Simmons: I gotchu though, will upload in a bit
[00:47] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: If you still have interest in Backports feel free to work on that in the meantime 
[00:47] <tsimonq2> And of course, ping with any questions :)
[00:47] <arraybolt3[m]> Simon Quigley (Developer): Definitely. I'm wrapping up the Ubuntu Studio PipeWire integration (got the easy 75% done, now about to fight with the hard 25%).
[00:48] <arraybolt3[m]> Once that's done, the backports project is next on my list.
[00:48] <kc2bez[m]> Nice
[00:48] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Sounds good! That Eickmeyer @eickmeyer:matrix.org guy may know just a little bit about Studio, just maybe a little bit. :P
[00:49] <arraybolt3[m]> LOL man, he saved me from a total goof I made during the UEFI patch building.
[02:29] <tsimonq2> arraybolt3: Congratulations on your second upload :)
[02:29] <tsimonq2> https://launchpad.net/ubuntu/+source/calamares/3.3.0~git20220610-0ubuntu2
[03:09] <tsimonq2> Sometimes I have too much fun with changelog entries. ;)
[03:09] <tsimonq2> https://launchpad.net/ubuntu/+source/pcmanfm-qt/1.1.0-0ubuntu3
[03:09] <tsimonq2> lynorian_: ^^^^^
[03:09]  * tsimonq2 does not know Lyn's current nick, checks Telegram
 @lynorian ^^^
[03:10] <arraybolt3[m]> LOL
[03:10] <tsimonq2> I remember when that project was maybe a page or two I wrote in high school... now look at how great it is :D
[03:11] <tsimonq2> Lyn has done an AMAZING job
[03:11] <tsimonq2> Completely knocked it out of the park
[03:11] <arraybolt3[m]> It's always so awesome when everything's working and everyone's working together well.
[03:11] <tsimonq2> Definitely. No matter how active any of us have been, one thing I've come to count on is that Lyn somehow still chugs away at that manual in the background :)
[03:12] <tsimonq2> It's amazing, I appreciate her a lot. She's one of the OGs
[03:15] <tsimonq2> (In fact, she should pop her head out more ;) )
[03:15] <tsimonq2> And, maybe we should start having weekly meetings again...
[03:16] <tsimonq2> hmm did I get the right twitter handle? I hope so...
[03:24] <tsimonq2> https://launchpad.net/ubuntu/+source/lubuntu-default-settings/22.10.3
[03:24] <tsimonq2> That upload compliments pcmanfm-qt.
[03:30] <tsimonq2> https://github.com/lxqt/pcmanfm-qt/issues/1603
 yes that is me on twitter
[03:31] <tsimonq2> arraybolt3: You gonna be up fairly late to test this respin or nah?
[03:31] <tsimonq2> lynorian: Good, thanks. :)
[03:31] <arraybolt3[m]> Definitely able to test the respin.
[03:32] <arraybolt3[m]> I stay up until 3 to 5 AM almost every night.
[03:32] <tsimonq2> Alright, let's give everything an hour or two to settle down.
[03:32] <tsimonq2> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[03:32] <tsimonq2> We're looking for calamares, libfm-qt, and lubuntu-default-settings to show up.
[03:33] <tsimonq2> (They'll show up once even if they just migrate right away.)
[03:33] <tsimonq2> I don't think any of those packages have autopkgtests, could be wrong.
[03:33] <tsimonq2> Anyway, once that's done, waiting for it to be published for at least 15-30 minutes before the respin.
[03:33] <tsimonq2> That takes another 30-45 minutes. Then the download time (I would suggest zsync.)
[03:34] <arraybolt3[m]> Do I need to be constantly checking it to see if it pops up, 'cause it will disappear at some point? Or will it appear and then stay there?
[03:34] <tsimonq2> update_excuses.html will only update once every hour.
[03:34]  * tsimonq2 wishes it was faster but oh well...
[03:34] <arraybolt3[m]> (I always zsync, makes my 300 KBps - 1 MBps connection way happier to deal with.)
[03:34] <arraybolt3[m]> (Those being kiloBytes and megaBytes per second, not bits.)
[03:35] <tsimonq2> $ date -u
[03:35] <tsimonq2> Fri Jun 17 03:34:45 AM UTC 2022
[03:35] <tsimonq2> Generated: 2022.06.17 02:29:47 +0000
[03:35] <tsimonq2> So the next Britney run should be happening nowish. Unfortunately that means another hour before everything migrates. I'd check back at about 12:30-12:45 central
[03:36] <tsimonq2> oh wait perhaps I forgot to change the tz back on my computer oops
[03:36] <tsimonq2> I was gonna say, that doesn't add up lol...
[03:36] <tsimonq2> Okay you get the point 😆
[03:37] <arraybolt3[m]> 👍️
[03:38] <tsimonq2> arraybolt3: Also, another thing to add to your list if you're interested...
[03:38] <tsimonq2> featherpad needs an update to the newest release, see this discussion for issues I came across: https://github.com/tsujan/FeatherPad/discussions/657
[03:39] <tsimonq2> Not to give you a whole list right away, if there's something you'd rather me JFD, just say the word :)
[03:40] <arraybolt3[m]> Nah, I love doing tons of Linux stuff. I will need tons of help figuring out what I'm doing if we want it done in anything like a timely fashion, since some of this stuff is insanely complicated, but once I get it, I should be able to get faster. Thank you for this!
[03:42] <tsimonq2> Of course, I've done it so many times that I'd rather sponsor :) for the big stuff I'll definitely pitch in but for stuff like updating the lightweight text editor and backporting some packages I'm going to deep test before releasing anyway, meh, it's fairly low-risk high-reward :)
[03:43] <arraybolt3[m]> Simon Quigley (Developer): Which one should I do first? The text editor, since it's probably easier and quicker, or the LXQt stack?
[03:43] <tsimonq2> Yeah, I think you have the right idea, try featherpad first :)
[03:44] <tsimonq2> Although that work will be more intensive, it will a) teach you more and b) make the backporting feel like a breeze
[03:44] <arraybolt3[m]> Alright, sounds like a plan. I'm reading the discussion right now.
[03:44] <tsimonq2> All finished with Ubuntu Studio? Don't mean to distract you if you were actively working on that.
[03:45] <arraybolt3[m]> For the most part. I finished 75% of the job, then ran into a probable bug on one side and a highly confusing glitch on the other, reported my results and am waiting for a response, so for now I'm free.
[03:45] <tsimonq2> https://phab.lubuntu.me/w/packaging/packaging_for_new_upstream_releases/
[03:45] <tsimonq2> arraybolt3[m]: Nice, sounds good. :)
[03:46] <tsimonq2> tsimonq2: This link has a ton of resources
[03:46] <tsimonq2> I would also remind you of this link from earlier: https://phab.lubuntu.me/w/lubuntu-dev/
[03:48] <tsimonq2> Between those two links and your requisite knowledge, I would think you could do that no problem. Just make sure to create an ubuntu/kinetic branch, sync it with the archive (literally copy the debian/ directory from the package you get from pull-lp-source and commit that by itself), and work off of that.
[03:48] <tsimonq2> Any questions please ask. I'll be around.
[03:48] <arraybolt3[m]> Nice.
[03:55]  * tsimonq2 will retar cala probably this weekend early next week
[03:55] <arraybolt3[m]> Holy cow, that's a lot. OK, looks like I have my work cut out for me. This should be exciting!
[03:56] <tsimonq2> Yeah, if you're looking at it all and trying to absorb it I'd get yourself a <your equivalent to a cup of coffee> and prepare for 2 hours or so :)
[03:56] <arraybolt3[m]> Quick question - I only followed part of the packaging requirements guide - Arcanist wasn't working right, I don't have a GPG key, and I don't have bzr set up. Is that OK?
[03:57] <tsimonq2> Don't worry about bzr or Arc*.
[03:57] <arraybolt3[m]> And I don't have the ssh agent with keychain.
[03:57] <tsimonq2> GPG key I would get set up though. Remember, think open source social security card.
[03:57] <arraybolt3[m]> OK.
[03:57] <tsimonq2> SSH agent may be fine. I wouldn't worry too hard about that unless you come across it.
[03:58] <tsimonq2> I may be distracted by two adorable kittens trying to get my attention. :)
[03:58] <arraybolt3[m]> I'm guessing that I should take very high precautions to ensure that I never lose the GPG key? I'm thinking back it up to my external drive and plop it in a private repo on GitHub (not sure about the safety of that last part).
[03:58] <arraybolt3[m]> Maybe Google Drive it, too.
[03:59] <tsimonq2> Just be very careful with it. Try not to store it on anyone else's computer, ever.
[03:59] <tsimonq2> I have two flash drives in very secure locations that involve multiple keys.
[03:59] <arraybolt3[m]> OK. I may take advantage of LUKS for this. That ought to throw a doozy of a problem at anyone who manages to steal a flash drive.
[03:59] <arraybolt3[m]> (Which probably won't happen, but can't be too careful.)
[04:01] <arraybolt3[m]> Also, what are the risks of losing the key? Can the old one be revoked and a new one made? If it's important that it never die, I'm thinking of only having one flash drive that contains it, protected by LUKS and with a passphrase set on the key, but if the drive dies/is lost/i forget one of the two passwords, is it possible to recover?
[04:01] <arraybolt3[m]> (I like to have a bunch of contingency plans laid out for maximum safety.)
[04:02] <arraybolt3[m]> s/it never die/it never be used by anyone else
[04:03] <arraybolt3[m]> Simon Quigley (Developer): Pinging.
[04:03] <arraybolt3[m]> 'Cause I'm about to generate it right now.
[04:03] <tsimonq2> Yes, the old one can be revoked.
[04:04] <tsimonq2> Not possible to recover I don't think. Be careful.
[04:04] <arraybolt3[m]> By recover, I meant throw away the old one and make a new one. Of course if the drive dies/is lost/passphrase(s) are forgotten, it should NEVER be recoverable, or else something is dreadfully wrong.
[04:05] <arraybolt3[m]> I'll start with the paranoid security level I described above, and if it's needed, I'll make a backup protected with equally high security.
[04:12] <arraybolt3[m]> Simon Quigley (Developer): Should I do anything with key expiration, or should the key be valid forever?
[04:12] <tsimonq2> My key is valid forever.
[04:13]  * guiverc wishes I'd made mine forever..
[04:14] <kc2bez[m]> Mine expires but you can extend it.
[04:14] <kc2bez[m]> I have done that a couple of times now.
[04:15] <arraybolt3[m]> Simon Quigley (Developer): Possibly silly question, but is there any algorithm better than RSA? I'm hoping that GPG can support a quantum-resistant one, and RSA is easy for a quantum computer to crack IIRC.
[04:16] <arraybolt3[m]> (If they can get the things to work reliably, that is.)
[04:16] <guiverc> Yeah.. I extended mine; some sites/commands accept it; others state it's expired .. meaning I likely missed something & haven't return to attempting to upload to ppa; or salsa.deb..  (spending time elsewhere)
[04:16] <tsimonq2> arraybolt3[m]: Couldn't tell you off the top of my head, doubt it matters too much. :)
[04:16] <tsimonq2> At that point your key is bitrot enough that you'd probably be working off of a new one anyway.
[04:17] <arraybolt3[m]> 👍️ OK, will report back once I've got it generated.
[04:17] <tsimonq2> Sounds good.
[04:21] <arraybolt3[m]> Agh, I hate that GPG keeps cancelling the key generation when it takes too long for me to think up a doozy of a password...
[04:23] <arraybolt3[m]> Bah, it went ahead and stored the key on the computer itself, not on the flash drive...
[04:26] <arraybolt3[m]> Wow, I had to confirm not one, not three, but FIVE OR SIX TIMES that I really wanted to delete the misplaced key.
[04:27] <arraybolt3[m]> Simon Quigley (Developer): How on earth do I tell GPG to plop my key directly on my encrypted flash drive? I don't want it to ever touch any other drive, since that entirely removes one powerful layer of security.
[04:27] <tsimonq2> arraybolt3[m]: I don't quite know how to answer that, apologies.
[04:27] <tsimonq2> My drive is completely LUKS-encrypted.
[04:28] <arraybolt3[m]> Sigh. My computer needs to be able to record music and is only just baaarely good enough for that, so I didn't enable LUKS for the sake of better performance. I just LUKS'd the tar out of my flash drive, but now gpg is being stubborn...
[04:29] <arraybolt3[m]> Ah, looks like --homedir will do it.
[04:29] <tsimonq2> Cool.
[04:48] <arraybolt3[m]> Simon Quigley (Developer): I'm looking at the guide and am a bit lost. Where exactly do I move all of the changes from upstream into the package? Is it in the sbuild step 16?
[04:50] <arraybolt3[m]> Simon Quigley (Developer): Also, Featherpad is not in the lubuntu-team GitHub.
[04:52] <arraybolt3[m]> Wow, that was fast, I'm watching the featherpad-packaging repository materialize before my eyes!
[04:54] <tsimonq2> https://github.com/lubuntu-team/featherpad-packaging
[04:54] <tsimonq2> Have fun
[04:54] <arraybolt3[m]> Thank you!
 "Simon Quigley (Developer): I'm..." <- How do you mean move the changes?
[04:54] <arraybolt3[m]> I mean, there's got to be some step in which the commits that were made upstream get merged into the thing that uscan downloads, but I don't see where that happens.
[04:55] <tsimonq2> Nope, not really a thing :)
[04:55] <tsimonq2> When updating it you don't do anything with the upstream commits
[04:55] <tsimonq2> Remember, we don't use GBP :P
[04:56] <arraybolt3[m]> Oh, because I'm just updating the packaging stuff and then later when someone build the package, they download the packaging, uscan, then build?
[04:56] <tsimonq2> Yeah
[05:06] <arraybolt3[m]> Simon Quigley (Developer): Just to make sure I don't botch the copyright step, do I download the version of Featherpad in the archives with apt-get source, or pull-lp-source, or something else?
[05:09] <arraybolt3[m]> Also, is it normal for pull-lp-source to be shockingly slow?
[05:09] <tsimonq2> I'm not sure what you mean
[05:09] <tsimonq2> Yeah, it is
[05:09] <arraybolt3[m]> This involves manually scanning the diff between the version the package previously in the archive and this new version, keeping track of any and all copyright notice changes and updating debian/copyright. This is tedious, and you have to do it manually.
[05:10] <arraybolt3[m]> Don't I need the source code to do the copyright notice checking?
[05:10]  * tsimonq2 cracks his knuckles
[05:10] <tsimonq2> get ready for me to blow your mind
[05:11] <tsimonq2> https://github.com/tsujan/FeatherPad/compare/V1.0.1...V1.3.0
[05:12] <tsimonq2> add .diff at the end
[05:12] <arraybolt3[m]> Oh, well that's convenient!
[05:12] <tsimonq2> yep :)
[05:12] <tsimonq2> and then use your standard text editor to grep
[05:12] <tsimonq2> GitHub is the single source of truth for upstream anyway
[05:13] <tsimonq2> Many bonus points if you can get it switched to the Qt 6 version and nail the dependencies on the first try. (Get the rest done first.)
[05:13] <arraybolt3[m]> Then any time I see a copyright notice, I just check it and update if needed?
[05:13] <tsimonq2> Yeah
[05:13] <tsimonq2>  * Copyright (C) Pedram Pourang (aka Tsu Jan) 2014-2019 <tsujan2000@gmail.com>
[05:13] <tsimonq2>  * Copyright (C) Pedram Pourang (aka Tsu Jan) 2014-2021 <tsujan2000@gmail.com>
[05:13] <tsimonq2> Seeing that already
[05:14] <arraybolt3[m]> I don't know what "use your standard text editor to grep" means. I know what text editor is, and I know what grep is, but I'm missing where the two go together.
[05:16] <tsimonq2> Okay, I've figured out how you'd modify d/copyright, let's see you give it a shot :)
[05:17] <arraybolt3[m]> Good grief, are copyright notices always placed at the top of a file? I don't want to scroll through 2386 lines of XML looking for a buried copyright notice, but I will if I have to.
[05:28] <tsimonq2> Yeah.
[05:28] <tsimonq2> Or Ctrl + F
[05:28] <arraybolt3[m]> LOL ok, that's a good idea (just search for "copyright", yeah?) Simon Quigley (Developer)
[05:28] <tsimonq2> yeah
[05:29] <arraybolt3[m]> Wow, you just saved my scroll wheel approximately seven thousand revolutions. Thank you!
[05:29] <tsimonq2> lmao of course :)
[05:43] <arraybolt3[m]> Man, still doing the copyright check, and I just have to say, I respect Tsu Jan. The amount of work this guy puts into ONE TEXT EDITOR is insane and amazing.
[05:47] <tsimonq2> That's the beauty of open source :)
[05:48] <arraybolt3[m]> Another question - do I need to check for potential varying licenses in the different files, even though the whole repo appears to be GPL v3-or-later'd? Or do I just check copyright dates?
[05:50] <tsimonq2> Nah, just dates
[05:50] <tsimonq2> Bigger projects, yes
[05:53] <arraybolt3[m]> LOL I forgot to look at when the search wrapped in Firefox, so I was like, "Man, I already cataloged this file. And this one, too. And this one, too! And... wait a minute, did I wrap? 🤦‍♂️
[05:55] <arraybolt3[m]> Oh no. I though I finished the job... and then discovered the "Load more commits" button.
[05:58] <tsimonq2> :)
[06:10] <arraybolt3[m]> Simon Quigley (Developer): I'm doing this in the browser, and I'm starting to get worried that I may have missed some of the files, since there's an epic number of diffs so large that GitHub hides them, and trying to click all of them is resulting in some possibly missed. Can I somehow download the history or something like that, then use a bash command to find "Copyright" for me so that I can make sure I catch everything?
[06:11] <tsimonq2> .diff at the end of the url
[06:11] <tsimonq2> use grep
[06:11] <tsimonq2> man grep can even give you line numbers and context :)
[06:14] <arraybolt3[m]> YAY!
[06:14] <arraybolt3[m]> Whew, that will make this ten times easier and way more accurate.
[06:17] <arraybolt3[m]> Man, I was wondering how on earth you managed to do the job yourself so fast when it was taking me so long...
[06:18] <tsimonq2> :)
[06:18] <LeoK[m]> Good morning - do we expect a respin this am?
[06:18] <tsimonq2> Everyone learns the hard way
[06:18] <arraybolt3[m]> Leo K: I believe so.
[06:18] <tsimonq2> LeoK[m]: Yes, within the next hour or so
[06:18] <arraybolt3[m]> Leo K: UEFI patch merged, plus Simon Quigley (Developer) made an exciting change related to the Lubuntu manual in PCManFM.
[06:18] <LeoK[m]> Great will run tests as soon as it appears
[06:19] <tsimonq2> https://launchpad.net/ubuntu/+source/calamares/3.3.0~git20220610-0ubuntu2
[06:19] <tsimonq2> https://launchpad.net/ubuntu/+source/pcmanfm-qt/1.1.0-0ubuntu3
[06:19] <tsimonq2> https://launchpad.net/ubuntu/+source/lubuntu-default-settings/22.10.3
[06:20] <LeoK[m]> arraybolt3[m]: Nice one Simon Quigley (Developer) 
[06:20] <tsimonq2> Thanks :)
[06:20] <tsimonq2> Also, good morning
[06:20] <arraybolt3[m]> 👋
[06:20] <LeoK[m]> tsimonq2: and good evening to you sir!
[06:21] <tsimonq2> To be fair also morning, 1:21 AM, close enough I guess :)
[06:24] <tsimonq2> My eyes are starting to get droopy. May call it a night here soon.
[06:25] <tsimonq2> arraybolt3: Feel free to leave me questions for the morning, or if you rack your brain against the docs hard enough you'll probably get it, you've proven yourself to be adaptable so far ;)
[06:25] <tsimonq2> Leo K: Unless LP actually migrates these darn things in the next 10 minutes or so, wait for the usual cronjob daily respin. Unless Dan sees this first.
[06:26] <LeoK[m]> tsimonq2: ok thanks - eyes wide open - 
[06:47] <tsimonq2> Probably better to respin once lubuntu-default-settings lands and that won't be until the next Britney run
[06:49] <tsimonq2> Leo K: I would suggest that once all three of those packages are in "Release" for at least 30 minutes, install them on a live ISO, log out, log back in (no password), and you should see both the new desktop icon (if you don't, log out, remove .config from a tty and you're golden) and the Calamares install should work
[06:49] <tsimonq2> anyway
[06:49]  * tsimonq2 -> bed
[06:49] <tsimonq2> Thanks for everything today guys. Really glad to see how it's all coming together.
[06:50] <LeoK[m]> ok Thanks Simon Quigley (Developer) - hit the sack and rest
[08:03] <arraybolt3[m]> Simon Quigley (Developer): Well, crud. I'm stuck at the sbuild step. I'm not sure what "making sure you have the -EvIL +pedantic flags set in your sbuildrc file" means. The best I can figure is that they're Lintian options (since Lintian has -E, -I, -L, and --pedantic flags... but no -v oddly, despite man sbuild.conf mentioning a -v flag for Lintian), but I'm not entirely sure since the -v flag is missing.  It's also 3 AM here, so
[08:03] <arraybolt3[m]> I've decided to do the ISO test if it's ready, and then spend the rest of the night taking a break. I'll see you in the morning, and thank you for all your help!
[08:48] <LeoK[m]> Ran tests looking for the UEFI patch and manual on Desktop - looks good - had to select to show manual in "desktop preference" advanced - the icon for the manual is a question mark. But initial test again look good.
[12:43] <kc2bez[m]> Simon Quigley (Developer): slow tests are slow. lubuntu-default-settings is still doing package tests so I didn't respin an iso. A new one should spin in ~4 hours. 
 "Ran tests looking for the UEFI..." <- I used the help-browser built-in icon, we should really get a Lubuntu Manual icon
[16:58] <LeoK[m]> tsimonq2: downloading todays ISO - running uefi þ secure test
[16:58] <tsimonq2> Sounds good- icon should appear 
[16:59] <LeoK[m]> hang on 5
[17:02] <LeoK[m]> While waiting --thinking -would also be nice to have manual in Live session 
[17:05] <tsimonq2> https://launchpad.net/ubuntu/+source/lubuntu-default-settings/22.10.3
[17:05] <tsimonq2> I don't know why that didn't land yet
[17:06] <kc2bez[m]> tsimonq2: Excuses sez autopkgtest earlier 
[17:07] <tsimonq2> Yeah, apparently that autopkgtest queue is backed up 24+ hours for amd64. Yikes.
[17:08] <tsimonq2> Thankfully once this ubiquity change migrates, future updates to lubuntu-default-settings will need no autopkgtest
[17:11] <LeoK[m]>  - one install in VM - manual  on desktop after selecting desktop icons
[17:13] <tsimonq2> I will respin later once tests are done 
[17:15] <LeoK[m]> UEFI+secure boot - good - no errors
[17:21] <LeoK[m]> Intend to test more later this evening or early AM - several file systems etc
[17:22] <tsimonq2> Thank you very much Leo! I'll ping once we have a respin done.
[17:22] <LeoK[m]> tsimonq2: Great - thanks
[17:36] <arraybolt3[m]> Hey guys!
[17:37] <arraybolt3[m]> Simon Quigley (Developer): Do you know where exactly in sbuildrc I'm supposed to put the -EvIL +pedantic flags?
 "Simon Quigley (Developer): Do..." <- Last I checked I had to consult the Debian wiki page for sbuild
[17:49] <tsimonq2> I can check in a min but I need to be on paid time rn :)
[17:49]  * tsimonq2 brb
[18:01] <arraybolt3[m]> OK. Thank you!
[18:02]  * arraybolt3[m] only used the Ubuntu instructions
[18:26] <tsimonq2> arraybolt3: Okay, hi.
[18:26] <tsimonq2> Figure it all out?
[18:51] <arraybolt3[m]> No LOL, I've been afk this whole time getting my day started.
[18:53] <kc2bez[m]> Lintian opts is the in your sbuildrc is what you are looking for 
[18:54] <kc2bez[m]> s/is the//
[18:54] <arraybolt3[m]> That's what I thought! But then what does the missing "-i" flag do?
[18:54] <kc2bez[m]> I is informational I think 
[18:55] <arraybolt3[m]> OK, then I guess I'll try it and see what happens.
[18:56] <kc2bez[m]> It spews all sorts of stuff in your stdout :D
[18:57] <arraybolt3[m]> Actually it wasn't -i that was missing, it was -v. I can't find anything about -v in Lintian's man page.
[18:58] <kc2bez[m]> Pretty sure that is verbose
[18:58] <kc2bez[m]> Might be wrong about that but I don't think so.
[19:04] <arraybolt3[m]> So basically the options mean "make Lintian as grumpy and loud as possible."
[19:06] <kc2bez[m]> Yes! 
[19:06] <kc2bez[m]> Just like your sponsors XD
[19:06] <tsimonq2> XD
[19:07] <arraybolt3[m]> OK. I went ahead and went with the Debian manual rather than Ubuntu since it looked closer to right. Also, do I tell Lintian "+pedantic", or "--pedantic"? The latter is in the man page, the former in the packaging guide for upstream.
[19:08] <tsimonq2> May have changed over the years, used to just be +pedantic
[19:16] <arraybolt3[m]> OK, anyone mind if I pastebin my new sbuildrc so everyone can look it over and make sure I didn't make any boffos?
[19:20] <arraybolt3[m]> (Also, figured out why I couldn't find options in man - I was forgetting to hit the Home key after each search to return to the top of the page. All the options actually were there.)
[19:28] <kc2bez[m]> Paste away
[19:29] <arraybolt3[m]> https://termbin.com/w819
[19:30] <arraybolt3[m]> OK, I just hit the sbuild button, let's see what happens...
[19:31] <arraybolt3[m]> Shoot, I'm doing this in Qt5 looks like. I'm supposed to try with Qt6...
[19:31] <kc2bez[m]> Sounds good 
[19:32] <kc2bez[m]> I would let it rip you can rebuild later/again 
[19:32] <kc2bez[m]> This way you know sbuild is the way you want.
[19:33] <arraybolt3[m]> 👍️
[19:35] <arraybolt3[m]> Simon Quigley (Developer): This may be cheating, since I'm supposed to try to nail the Qt6 dependencies the first try, but... what exactly am I supposed to be doing here? Do I edit debian/control to point to different dependencies, and then try and get sbuild to pull everything that's needed?
[19:39] <tsimonq2> arraybolt3[m]: Edit debian/control for the Qt 6 equivalent and then go by what cmake says
[19:39] <arraybolt3[m]> tsimonq2: As in, try to make debian/control right, and then deal with whatever fits cmake throws?
[19:40] <kc2bez[m]> Skim through the cmake and see what dependencies you might need.
[19:41] <kc2bez[m]> That is upstream 
[19:41] <tsimonq2> arraybolt3[m]: Yes 
[19:42] <arraybolt3[m]> First build failed! Missed libhunspell-dev.
[19:42] <tsimonq2> Wait for it... :)
[19:44] <arraybolt3[m]> And now adding it didn't work (hmm, seems familiar?)
[19:45] <arraybolt3[m]> OK, so I'm guessing that installing the package Tsujan mentioned in that GitHub discussion you linked to needs to be in the chroot, not on the main system.
[19:49] <arraybolt3[m]> alRIGHT! Got it to actually start building! \o/
[19:49] <kc2bez[m]> Nice
[19:53] <arraybolt3[m]> Simon Quigley (Developer) Dan Simmons Build failure, but I can't make heads or tails of the error message. Missing files... what missing files? https://termbin.com/nqiu
[19:56] <kc2bez[m]> That message is saying it expected to have files installed at that path but the  packaging didn't do that.
[19:56] <kc2bez[m]> Look at your  .install files.
[19:58] <arraybolt3[m]> Oh, so I need to add that path to featherpad-l10n.install. Thanks!
[20:03] <arraybolt3[m]> Well, everything but the build failed, probably because I botched sbuild's config, but the build succeeded this time.
[20:04] <kc2bez[m]> Paste your log
[20:04] <arraybolt3[m]> OK, but it's ridiculous, I can already see where it went wrong (trying to access unstable-amd64-sbuild chroot when it's named kinetic-amd64, or trying to get to kinetic-amd64-amd64 chroot (?!))...
[20:05] <kc2bez[m]> Hmm ok
[20:05] <arraybolt3[m]> https://termbin.com/3gyg
[20:06] <tsimonq2> Did you do the shm setup?
[20:06] <arraybolt3[m]> No, directly to disk. I gave the VM 16 GB RAM (I only have 32 GB in my system), so I didn't think that the shm setup would work on my system.
[20:06] <tsimonq2> Hmmm
[20:07] <kc2bez[m]> `schroot -l` might help you 
[20:07] <tsimonq2> Is your configuration b0rked?
[20:07] <arraybolt3[m]> Pretty sure it was just a bad sbuildrc file, I found where the thing was most likely getting its crazy values, so I changed them.
[20:07] <arraybolt3[m]> tsimonq2: Pretty sure. Guess I should've expected that when copypasting from Debian's manual and then following Ubuntu's.
[20:08] <kc2bez[m]> Also from your paste it should be +pedantic 
[20:08] <arraybolt3[m]> Bah, thanks "man lintian" for the bad info.
[20:08] <arraybolt3[m]> (Or at least the misunderstood info.)
[20:08] <arraybolt3[m]> OK, fixed, let's try it again.
[20:15] <arraybolt3[m]> Much better results this time, but there was so much output to stdout that all the Lintian results decided to vanish. Where does Lintian hide its logs at?
[20:19] <arraybolt3[m]> Also, piuparts got mad because of a bunch of broken symlinks related to coreutils, and some leftovers related to fonts. Is that normal?
[20:36] <LeoK[m]> Calamares update looks good - ran tests BIOS,UEFI,UEFI+secure,encryption,BTRFS and XFS installs - all good
[20:37] <arraybolt3[m]> OK, I hit a lot of stuff in Lintian, pasted the errors and relevant data, and wrote some questions, can you check this over? https://termbin.com/zals4 Dan Simmons Simon Quigley (Developer) 
[20:37] <arraybolt3[m]> Leo K: Wow, sounds like a lot's been happening on the testing front while I've been tied up. Nice going, and thank you!
[20:54] <arraybolt3[m]> Attempting Qt6 build...
[21:13] <arraybolt3[m]> Simon Quigley (Developer): Need some help. I'm trying to switch to building with Qt6, but changing the dependencies didn't automatically make everything work. So then I dug into the rules file and saw that Qt5 was selected, but changing "export QT_SELECT = 5" to "export QT_SELECT = 6" is now resulting in a "qmake: could not find a Qt installation of '6'" error. My google-fu is failing me. What am I supposed to do here?
 "Simon Quigley (Developer..." <- Check the cmake file
[21:33] <tsimonq2> option(ENABLE_QT5 "Building Qt5 plugin." ON)
[21:33] <tsimonq2> So set that to OFF in your rules file
[22:06] <arraybolt3[m]> Simon Quigley (Developer): Thanks, wondered how on earth to set that thing.
[22:07] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: all good now?
[22:08] <arraybolt3[m]> Sadly, no. I'm still getting the exact same error. I'll paste the whole thing.
[22:08] <arraybolt3[m]> https://pastebin.com/P4edWFW3
[22:09] <arraybolt3[m]> (This time I tried getting rid of the QT_SELECT variable entirely, but having it set to 6 also fails.)
[22:09] <tsimonq2> Did you install the Qt 6 version of qmake?
[22:09] <arraybolt3[m]> (Should it be set to 5 despite the fact that I'm building with 6?)
[22:09] <arraybolt3[m]> Simon Quigley (Developer): Yes.
[22:10] <tsimonq2> Hmm. I remember I had to do something locally to get this far
[22:10] <tsimonq2> What's in debian/rules?
[22:10] <arraybolt3[m]> qmake6, qt6-base-dev, etc.
[22:10] <arraybolt3[m]> https://pastebin.com/DCYtwJF3
[22:10] <arraybolt3[m]> (Again, results of experiment with removing QT_SELECT, but having it set to 6 results in a very similar error.)
[22:11] <arraybolt3[m]> Ack, somehow I missed the top two lines of the file...
[22:11] <arraybolt3[m]> Simon Quigley (Developer): https://pastebin.com/uzvmmkGU
[22:11] <arraybolt3[m]> (Contents of debian/rules)
[22:14] <arraybolt3[m]> Setting "QT_SELECT = 5" results in "qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory"
[22:59] <tsimonq2> Okay that's your issue 
[22:59] <tsimonq2> You need to pass it directly as cmake arguments not as env vars in the rules file 
[22:59]  * tsimonq2 thinks at least...
[23:03] <arraybolt3[m]> OK, I'm awfully tired. I think I'll have to take a break for a day and pick up Sunday morning. Thanks for everything!
[23:05] <tsimonq2> All good :)
[23:05] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Any chance you could push your commits?
[23:15] <tsimonq2> https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/commit/?id=1e997e760fa5901d14318edd9b1d02da3a4a9cfb
[23:18] <arraybolt3[m]> Simon Quigley (Developer): Sure. It's kinda messy, I'll probably need to redo the whole thing once I figure out what I'm doing, but I'll get it pushed in about 15 minutes or so.
[23:22] <tsimonq2> arraybolt3[m]: I'm going to come up with a fix tonight myself to be able to give you a useful hint. All good.
[23:22] <arraybolt3[m]> Thanks.
[23:27] <tsimonq2> Of course. Just let me know where your packaging hides.
[23:27] <arraybolt3[m]> Got it pushed. https://github.com/ArrayBolt3/featherpad-packaging
[23:27] <arraybolt3[m]> Fun fact - Forgot to fork and then clone, but forking, then changing Git's remote to the forked repo worked just fine.