[00:01] <arraybolt3> sbuilding away
[00:03] <arraybolt3> ok so that'll depwait, what package are you on?
[00:03] <arraybolt3> tsimonq2: ^
[00:03] <tsimonq2> lxqt-admin is done, I was just about to hop on a new one
[00:04] <arraybolt3> lxqt-config or lxqt-archiver?
[00:04] <tsimonq2> archiver since I think I packaged that one myself ;)
[00:04] <arraybolt3> +1
[00:04] <arraybolt3> one sec, didn't backport yet
[00:07] <tsimonq2> no worries
[00:08] <tsimonq2> also don't forget to tag - it's been a struggle for me lol
[00:09] <arraybolt3> just finished tagging and pushing the tags :)
[00:09] <arraybolt3> moving onto lxqt-config
[00:11] <tsimonq2> Sweet, moving onto lxqt-globalkeys.
[00:11] <arraybolt3> Grief, already? :P
[00:12] <tsimonq2> Yep :D
[00:17] <tsimonq2> Moving onto lxqt-notificationd.
[00:19] <arraybolt3> dh_install: warning: Cannot find (any matches for) "etc/xdg/menus/lxqt-config.menu" (tried in ., debian/tmp)
[00:19] <arraybolt3> this means that the install file is missing the file right?
[00:19] <arraybolt3> just double-checking
[00:20] <tsimonq2> Other way around, the install file thinks it's there when it isn't.
[00:20] <arraybolt3> ahhh
[00:20] <arraybolt3> and now I see where the install file has wonky things
[00:20] <tsimonq2> If I were you, I'd compare the files in lxqt-menu-data versus what you have in your install file - and perhaps even compare the tarball size from last release, I think those files just simply got moved. That's just a theory, again, leaving the judgement call to you.
[00:21] <arraybolt3> I think it's very likely moved files since it's menu stuff.
[00:21] <arraybolt3> but yeah, I'll check while this rebuilds
[00:21] <tsimonq2> Sweet, I'll have to do another Backports-only patch for lxqt-notificationd reverting this: https://github.com/lxqt/lxqt-notificationd/commit/63fdeb192b8e7bf0a131278393903de0b014e0cd
[00:21] -ubottu:#lubuntu-devel- Commit 63fdeb1 in lxqt/lxqt-notificationd "Port deprecated KWindowSystem"
[00:22] <arraybolt3> yeah looks like menu move stuff is all
[00:22] <tsimonq2> Makes sense. Do what you know is right :)
[00:32] <arraybolt3> whew, this has been a sticky package. Lintian-overrides syntax needed fixing, obsolete linker flag, build failures, the works. Oh, and a crazy copyright file.
[00:32] <arraybolt3> I may be fighting with this one for a while :P
[00:33] <tsimonq2> Kay, lxqt-notificationd is now churning. On to lxqt-openssh-askpass.
[00:33] <tsimonq2> Why do I keep getting the easy ones? XD
[00:33] <tsimonq2> Hey, like I said before, it makes you stronger, eh? :)
[00:33] <arraybolt3> idk :P
[00:33] <tsimonq2> If you need help, I'm here.
[00:33] <arraybolt3> definitely makes me stronger 💪
[00:33] <arraybolt3> :P
[00:33] <arraybolt3> you're helping right now! :D
[00:33] <tsimonq2> hah good :)
[00:39] <tsimonq2> lxqt-openssh-askpass is done, I'll take lxqt-policykit next (but taking a quick break first.)
[00:40] <tsimonq2> Also, generally beware that RikMills decided to upload a new Frameworks release. I doubt we'll have to do much, *might* need an NCR for Cala.
[00:41] <tsimonq2> Anyway, tonight I'm more focused on ramming 1.4 through, so we frontload a lot of testing this cycle.
[00:42] <arraybolt3> I think I'm going to just upload lxqt-config as-is and file another bug report about licensing. I just ran into a file that says it is both GPL-2 OR GPL-3, and GPL-2-only, in the same copyright header.
[00:43] <tsimonq2> HAH. Nice one.
[00:43] <arraybolt3> I think all open-source devs need to have like a one-day course on "how licensing actually works" before being allowed to publish anything :P
 I often joked over the course of the Ubuntu Summit that a Debian Developer certificate should come with an Associate's in Law, on the other end of that :P
[00:47] <arraybolt3> lol, ikr?
[00:47] <arraybolt3> IANAL but at this point I could probably teach a lawyer how to do their job better in some ways >_<
[00:48] <arraybolt3> (not actually but you get the joke)
[00:50] <arraybolt3> ok lxqt-config "finished" for the most part, but I'm going to be stuck on it for a while longer compiling a bug report.
[00:50] <tsimonq2> hah :D
[00:51] <tsimonq2> No worries, I'm just now getting started on lxqt-policykit.
[00:56] <tsimonq2> And, done.
[00:56] <tsimonq2> Looks like I'm on to lxqt-session.
[00:57] <arraybolt3> nice
[01:09] <tsimonq2> lxqt-session is done, moving to lxqt-sudo.
[01:15] <arraybolt3> hit a hard one this time?
[01:16] <arraybolt3> meh, probably not
[01:16] <tsimonq2> Kinda sorta. I had to import the SRU we did for lxqt-sudo (hint, hint: we still need to verify that :P)
[01:16] <tsimonq2> Anyway, all set on that one. How's it coming on your end?
[01:16] <arraybolt3> still have three sub-programs to audit
[01:17] <arraybolt3> lxqt-config is like seven or so programs in one repo
[01:17] <tsimonq2> niiiiiiiiiiiiiiice
[01:17] <arraybolt3> yeah :D :-/
[01:17] <tsimonq2> I'll pump the brakes for a few minutes in case I can help you with anything
[01:17] <arraybolt3> And it's a motly mess of licensing. LGPL-2.0, GPL-2+, LGPL-2.1+, GPL-2, LGPL-2.1+, GPL-2 OR GPL-3, WTFPL-2, and the infamous GPL-2 and LGPL-2.1+ weirdness, all in one repo.
[01:18] <tsimonq2> (I feel like I'm just chugging away and you're standing back in awe. In reality, by chance I'm just getting the easy ones. :P)
[01:18] <tsimonq2> Woahhhhhhh. Nice. :/
[01:18] <tsimonq2> (Also, you're doing hard work too, so it's about even, I guess.)
[01:19] <arraybolt3> true :)
[01:19] <tsimonq2> https://www.youtube.com/watch?v=cE1FrqheQNI
[01:19] <arraybolt3> <one line to give the library's name and an idea of what it does.>
[01:19] <arraybolt3>  Copyright (C) 2014  <copyright holder> <email>
[01:20]  * arraybolt3 decides to name my next project "<one line to give the library's name and an idea of what it does.>" just so that the next time I see that at least it's a valid name
[01:20] <tsimonq2> Is that like... actually in the LXQt source code? :P
[01:20] <arraybolt3> Yes.
[01:20] <tsimonq2> LMFAOOOOOOOOOOOOO
[01:20] <arraybolt3> lxqt-config-input/keyboardlayoutconfig.cpp
[01:21] <tsimonq2> 🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍🤦‍
[01:21] <tsimonq2> arraybolt3: Also, you saw that lxqt-config FTBFS in Backports Staging, right?
[01:21] <arraybolt3> missed that
 I feel like I've met that guy. (re @lubuntu_bot: (irc) <arraybolt3>  Copyright (C) 2014  <copyright holder> <email>)
[01:21] <tsimonq2> Not meaning to nag, just making sure you're aware.
[01:21] <arraybolt3> fun
[01:22] <tsimonq2> XD
[01:22] <arraybolt3> kc2bez: roflol
[01:22] <tsimonq2> arraybolt3: It's just a missing include, no biggie. Also, we're almost done, just the final stretch :D
[01:23] <arraybolt3> nice
[01:23] <tsimonq2> Well, there's the Launchpad build queue again. Fun stuff. At least we have passing amd64 builds for Backports Staging...
 I've been packing to head out to a conference for work this week watching the scroll go by.
[01:24] <tsimonq2> Nice nice :D
[01:24] <tsimonq2> Save travels!
[01:25] <arraybolt3> kc2bezL o/ Hope everything goes well!
[01:25] <arraybolt3> s/L/:/
 Should be good, it is a shortish drive of a couple of hours.
[01:27] <tsimonq2> Nice, nice.
[01:27] <tsimonq2> I'm going to get started with pcmanfm-qt (which could honestly be a mean one).
[01:29] <arraybolt3> good luck :)
[01:29] <arraybolt3> (funny enough, I expected lxqt-archiver to be harder than lxqt-config, so you may find this one is the easiest one you've done yet)
[01:30] <arraybolt3> whoa hi IRC reconnect
[01:42] <arraybolt3> this just keeps getting better
[01:42] <arraybolt3>   2     Copyright (C) 2014  P.L. Lucas <selairi@gmail.com>
[01:42] <arraybolt3>   3     Copyright (C) 2013  <copyright holder> <email>
[01:43] <arraybolt3> A valid copyright line above an invalid one.
[01:43] <arraybolt3> in lxqt-config-monitor now
[01:45] <tsimonq2> hahahahahahahahaha
[01:46] <tsimonq2> Looks like pcmanfm-qt has been a lot to chew on.
[01:46] <arraybolt3> oh man
[01:46] <tsimonq2> We'll need to double-check how this GUI looks when it's all good.
[01:46] <arraybolt3> kk, sounds a bit scary :P
[01:46] <tsimonq2> I just had to edit a UI file by hand, merging a three-way diff. :P
[01:46] <arraybolt3> oh grief
[01:47] <arraybolt3> I haven't had the privilege of doing that yet
[01:47] <tsimonq2> So, I'm crossing my fingers, hoping I didn't completely b0rk it. :P
[01:47] <tsimonq2> hahahahahahahaha
[01:47] <arraybolt3> open it in Qt Designer to double-check?
[01:47] <arraybolt3> you probably did that already
[01:47] <tsimonq2> Nah, not yet, prob should :P
[01:47] <tsimonq2> Oh bah, it FTBFS.
[01:47] <arraybolt3> welp
[01:48] <arraybolt3>   2  * <one line to give the library's name and an idea of what it does.>
[01:48] <arraybolt3>   3  * Copyright (C) 2014  PCMan <email>
[01:48] <arraybolt3> Well he got closer this time 🤣
[01:48] <tsimonq2> XD
[01:48] <arraybolt3> Bet it's Hong Jen Yee who owns all of the placeholders.
[01:49] <tsimonq2> Right.
[01:49] <tsimonq2> Well, I'm going to go grab a nice, frosty mug and think about this FTBFS. :P
[01:50] <tsimonq2> Or at the very least, what my plans are for adapting this menu further.
[01:50] <tsimonq2> Anyway, I'll be back before about 9ish.
[01:50] <arraybolt3> kk, see you later!
[01:50] <arraybolt3> I'll keep adding onto this quite beefy bug report in the mean time.
[01:51] <tsimonq2> Sounds good, don't feel like my absence should stop you, keep on chugging. ;)
[01:52] <arraybolt3> I may have to take a break after this.
[01:52] <tsimonq2> No worries.
[01:52] <tsimonq2> I think we've both reached the hard part, so breaks are probably well deserved. :P
[01:52] <tsimonq2> (At least on your end, I don't know about me. XD)
[02:01] <arraybolt3> https://github.com/lxqt/lxqt-config/issues/966
[02:01] -ubottu:#lubuntu-devel- Issue 966 in lxqt/lxqt-config "Confusing and contradictory licensing information" [Open]
[02:02] <arraybolt3> And with that, my audit is complete.
[02:03]  * arraybolt3 feels like I have a coffee withdrawal headache now even though I've not drank coffee in a long, long time
 Niceee XD
 The LXQt stack just half-migrated, which means potential instability for testers. Beware, system updates might eat kittens.
 Either way, we're in early Alpha; I hope we can get to Calamares stuff tonight but that all depends. Might be (less than) a week before that gets fully settled, all the nested errors
 I'm willing to bet the reports we've seen so far are only the first set
 arraybolt3: Are you still around, or did you hit the hay for the night?
[02:45] <arraybolt3> Around-ish.
 By the way, getting back into things, The Headache is to be expected the first difficult upload or two. Take your time, I'm here to help :)
[02:46] <arraybolt3> (I'll be up for a good long while most likely, especially since the Ubuntu support room on Matrix is under attack by a spammer :-/)
[02:46] <arraybolt3> (I have mod privileges there so I'm currently "standing guard")
 Ouch.
 Remember, it's open source, I'm extremely grateful for your help, but if you need to crash, just do it man :)
 If you're still energetic though, let's get it :D
[02:47] <arraybolt3> heh, I woke up at around 11, probably will be up until past midnight if history is any indicator.
[02:47] <arraybolt3> I'm still recovering and working on tending the fire, but I'll be ready to help out more soon most likely.
 Sounds about right :) with jetlag, it feels much later than it actually is. I'm on the tail end of that, but daylight savings doesn't exactly help.
[02:50] <arraybolt3> ugh, I hate Daylight Wastings Time.
[02:56] <arraybolt3> tsimonq2: Did you do everything up to and including pcmanfm-qt that comes after lxqt-config?
[02:57] <arraybolt3> and where are you at now?
[03:01]  * arraybolt3 tackles xdg-desktop-portal-lxqt
[03:05] <tsimonq2> arraybolt3: Okay, so I'm currently at pcmanfm-qt.
[03:05] <tsimonq2> arraybolt3: I just need to evaluate the UI changes made, and determine the best steps for the patch going forward.
[03:11] <arraybolt3> sounds good
[03:11] <arraybolt3> almost have xdg-desktop-portal-lxqt knocked out
[03:11] <arraybolt3> fie upon me, I forgot to tag my lxqt-config uploads
[03:12] <tsimonq2> cool cool, and oof :/
[03:12] <tsimonq2> *shrug* it happens XD
[03:12] <tsimonq2> Ever get Backports sorted for lxqt-config?
[03:13] <arraybolt3> not yet, need to do that
[03:13] <arraybolt3> btw any clue how to fix this? W: xdg-desktop-portal-lxqt: wrong-name-for-upstream-changelog [usr/share/doc/xdg-desktop-portal-lxqt/CHANGELOG]
[03:14] <arraybolt3> I know why it's happening but I don't recall finding a way to get that file to be compressed when it doesn't happen automatically
[03:15] <Eickmeyer> override_dh_autoinstall: 😈
[03:15] <arraybolt3> ugh, I guess that might work
[03:17] <tsimonq2> XD
[03:17] <tsimonq2> Eickmeyer: ohai
[03:17] <Eickmeyer> hello
[03:18] <arraybolt3> so like what, dh_auto_install; gzip -9 usr/share/doc/xdg-desktop-portal-lxqt/CHANGELOG
[03:19] <arraybolt3> or something like that?
[03:19] <tsimonq2> Awful. I hate it. Ship it.
[03:19] <Eickmeyer> No no no no no
[03:19] <tsimonq2> ;)
[03:19] <Eickmeyer> BAD
[03:19] <Eickmeyer> EVIL
[03:19] <arraybolt3> You mean -EvIL +pedantic :P
[03:19] <Eickmeyer> Actually, yes. Do it.
[03:19] <tsimonq2> XD
[03:26] <arraybolt3> actually I override dh_installchangelogs X(
[03:30] <tsimonq2> Okay, so pcmanfm-qt has been uploaded.
[03:30] <tsimonq2> It's about that time, that I EOD.
[03:30] <tsimonq2> arraybolt3: Thanks again for all your help today.
[03:30] <arraybolt3> HAHA it worked!
[03:30] <arraybolt3> tsimonq2: Congratulations :)
[03:31] <arraybolt3> (on getting pcmanfm-qt done)
[03:31] <tsimonq2> Feel free to continue, don't let my EOD stop you :)
[03:31] <tsimonq2> Thanks :D
[03:31] <Eickmeyer> Imagine I actually had a good idea with that override....
[03:31] <tsimonq2> I'll check in later/in the morning to see how far you've gotten.
[03:31] <tsimonq2> Eickmeyer: <3
[03:31] <tsimonq2> Anyway, good night all o/ :D
[03:31] <arraybolt3> Eickmeyer: That was an awesome idea, and one I wouldn't have thought of.
[03:39] <arraybolt3> Aaaaand... xdg-desktop-portal-lxqt conquered.
[03:40] <arraybolt3> I'm tired, hungry, and should spend some time with my family, so I think I'm calling it a night. Please keep in mind that qterminal needs packaged still (assuming it got a version bump).
[03:43] <arraybolt3> also I still haven't fixed lxqt-config, need to do that
 Gooooooood morning :D
[15:55] <tsimonq2> @kc2bez, @teward001: Did we need to seek *re*-qualification for LTS last time around, or were we just grandfathered in?
[15:59] <tsimonq2> arraybolt3: Okay, so I have limited time this morning before I must get back to $dayjob. The binary NEW queue *does* seem a little backed up, which is typical for this part of the cycle.
[15:59] <tsimonq2> Eickmeyer: (cc, for your general musings ^^^)
[15:59] <tsimonq2> arraybolt3: That being said, I'll crank out as much as I can. In an ideal world, we'd get to testing on Jammy systems today.
 KF5 is really only bugfixes at this point (re @lubuntu_bot: (irc) <tsimonq2> Also, generally beware that RikMills decided to upload a new Frameworks release. I doubt we'll have to do much, *might* need an NCR for Cala.)
[16:07]  * Eickmeyer wonders how much more NEW to throw into the queue for kicks/giggles....
 KF6 to new?
 /me hides
[16:17] <arraybolt3> tsimonq2: there's only four packages left that need fully done, and one that needs fixed in Jammy, so I suspect this will be easily doable. I could Jusg Do It today if needed.
[16:17] <arraybolt3> Also I can make early Noble testing possible if we're itching to try
[16:29] <tsimonq2> arraybolt3: Sweet, let's continue to coordinate, I'll let you know when I pick my next subject.
[16:30] <tsimonq2> arraybolt3: And remember, waiting on binary NEW ;) so unless you have a clean-ish PPA, it's probably Just Easier to test Jammy first, then release that into Backports.)
[16:30] <arraybolt3> True, I would have to build a whole PPA, so yeah, Jammy first sounds good.
[16:33] <tsimonq2> Sweet.
[16:34] <tsimonq2> I'll be on in about 5-10 minutes to get started. Shouldn't take us too long.
[16:39] <arraybolt3> I may be a bit slower :p
[16:51] <arraybolt3> Working on fixing lxqt-config.
[16:54] <tsimonq2> Sounds good!
[17:02] <arraybolt3> Gah, it's fighting me, the upstream patch can't just be imported in and work as-is.
[17:03] <arraybolt3> That's because I'm not using a revert commit like I should XD
[17:03] <arraybolt3> ok, figuring this out
[17:04] <tsimonq2> mv lxqt-config-packaging lxqt-config-1.4.0 && tar xvf the_orig.tar.uhh.plasma-distro-update-up...no..gz && cd lxqt-config-1.4.0 && quilt pop -af && quilt new ohai-newpatch.patch && quilt add the-files-touched && patch -R -p1 < patch-you-want-to-reverse.patch
[17:04]  * tsimonq2 shots fired at Eickmeyer XD
[17:05] <arraybolt3> lol, there's too many easter eggs in that one to read and get much info out of it XD
[17:05] <tsimonq2> LMFAO
[17:06] <tsimonq2> "Quilt pop, af." is one of my favorites
[17:06] <Eickmeyer> Huh... that reminds me... 
[17:07]  * Eickmeyer looks
[17:07] <Eickmeyer> Oh... no new patch. Huh.
[17:07] <Eickmeyer>  ¯\_(ツ)_/¯
 Whoops XD
[17:11] <arraybolt3> Fired off an sbuild. Gonna take a bit, haven't build a Jammy package in a while so lots of downloads to be done.
[17:14] <tsimonq2> Sweet. :)
[17:18] <arraybolt3> So, you have to add Backrport *and* Backports Staging for all packages to be available. Noted.
[17:18] <arraybolt3> (forgot we had a PPA dependency there)
[17:18] <tsimonq2> I mean, technically, yeah.
[17:18] <tsimonq2> That being said, all the packages for the *new* stack *should* be in Backports Staging, thus superseding the ones in Backports.
[17:19] <arraybolt3> Backrport. Because that's the real spelling of Backports. Not sure how the s turned into an r and migrated into the middle of the word :P
[17:19] <tsimonq2> XD
[17:19] <arraybolt3> Well lxqt-build-tools didn't get a bump.
[17:19] <arraybolt3> So it's not in Backports Staging.
[17:19] <arraybolt3> And thus my local build attempt initially failed miserably.
[17:19] <tsimonq2> Ah, okay, that makes a lot of sense.
[17:21] <tsimonq2> I'll grab qterminal.
[17:25] <arraybolt3> https://git.lubuntu.me/Lubuntu/lxqt-config-packaging/commit/2610884257c100ef22046257a98ca9ca43b117dc
[17:25] -ubottu:#lubuntu-devel- Commit 2610884 in Lubuntu/lxqt-config-packaging "ah kscreen, thine version art insufficient for our purposes. Downgrade thyself."
[17:25] <arraybolt3> Soooo... I forgot to do some git pushes last night apparently.
[17:26] <arraybolt3> I'll need to audit and make sure I actually uploaded all of my changes to Git and not just to the archive.
[17:26] <arraybolt3> And make sure they're all tagged. Grief.
[17:26] <arraybolt3> Anyway, fixed lxqt-config now in Backports Staging and hopefully building away.
[17:31] <arraybolt3> tsimonq2: qterminal working OK for you?
[17:32] <tsimonq2> arraybolt3: Yup! Just pinged in #launchpad about ssh-ppa not working but ppa working.
[17:32] <arraybolt3> oh weird, and nice
[17:32] <arraybolt3> can I snag -panel?
[17:32] <arraybolt3> or would you prefer I do -powermanagement
[17:33] <tsimonq2> Pick one, they're both equally as hard (muahahahahaha).
[17:33] <tsimonq2> Aaaaaaaaaaaactually, let me do powermanagement please.
[17:33] <arraybolt3> sure
[17:33] <tsimonq2> I have a patch I'd like to throw in there :)
[17:47] <arraybolt3> hrm, sooooo this may bomb out if the debs for lxqt-panel are depwaiting
[17:47] <arraybolt3> if yours bombs out too I'll throw some builds into my PPA and we can use it as a bootstrap in the mean time.
[17:47] <arraybolt3> (I don't know if mine will fail yet or not)
[17:47] <arraybolt3> (I think it's working actually)
[17:48] <tsimonq2> copy-package --from ubuntu -s noble-proposed --to ppa:lubuntu-dev/ubuntu/backports-staging --to-suite jammy -y vim
[17:48] <tsimonq2> That's a past command I've used for jammy
[17:48] <tsimonq2> ubuntu-archive-tools should have it, probably a simple git clone lp:ubuntu-archive-tools
[17:48] <arraybolt3> wait that actually is a thing?
[17:48] <arraybolt3> TIL
[17:49] <tsimonq2> That's actually the command Britney uses to do its package migration.
[17:50]  * arraybolt3 starts up https://www.youtube.com/watch?v=_DTANlTnpeo to play in the background while I'm building stuff
[17:51] <tsimonq2> :D
[17:51] <tsimonq2> Kay, lxqt-powermanagement is good.
[17:51] <arraybolt3> This brings back good memories of backporting the whole mountain of LXQt stuff back in the Kinetic cycle.
[17:51] <tsimonq2> hahahahahah :D
[17:51] <arraybolt3> Glad to be back to it :)
[17:51] <tsimonq2> Glad this one was a team effort, too :D
[17:51] <tsimonq2> (i.e. not just me, or not just you, lol)
[17:52] <arraybolt3> 👍
[17:52] <tsimonq2> Do you want the last package, or want me to take care of it?
[17:53] <arraybolt3> I'm happy to tackle it.
[17:53] <arraybolt3> You're in a time crunch and I'm not :)
[17:53] <tsimonq2> Sounds good :)
[17:53] <tsimonq2> Thanks.
[17:54] <arraybolt3> Glad to help :) thanks for letting me come back.
[17:55] <tsimonq2> Of course.
[17:55] <tsimonq2> Le sigh, looks like Backports has another special commit to revert.
[17:55] <tsimonq2> https://github.com/lxqt/lxqt-powermanagement/commit/aca58172f611e2545c3cfcb8310725b3cf5fa715
[17:55] -ubottu:#lubuntu-devel- Commit aca5817 in lxqt/lxqt-powermanagement "Port deprecated KWindowSystem"
[17:58] <tsimonq2> Kay, done.
[17:59] <tsimonq2> I see lxqt-config also passed, congrats \o/
[18:00] <arraybolt3> woohoo!
[18:00] <arraybolt3> uh, while you're here...
[18:00] <arraybolt3> I: lxqt-panel: package-contains-documentation-outside-usr-share-doc [usr/share/lxqt/panel/qeyes-types/README]
[18:00] <arraybolt3> This isn't really a documentation file, but it isn't really not a documentation file either
[18:00] <arraybolt3> thoughts?
[18:01] <tsimonq2> Where are other READMEs shipped, again?
[18:01] <tsimonq2> Like, in this source package.
[18:01] <tsimonq2> I mean, options include moving it there, under like a README.qeyes-types, or creating its own subdirectory, or just overriding the Lintian warning.
[18:01] <tsimonq2> *info tag
[18:01] <arraybolt3>  /usr/share/doc/lxqt-panel
[18:01] <arraybolt3> is where things are
[18:01] <tsimonq2> I mean, if it was upstream, you know they'd say your tooling is broken just ship it anyway :P
[18:01] <tsimonq2> So, I think that's your answer :)
[18:01] <arraybolt3> I like README.qeyes-types
[18:02] <arraybolt3> oh ok
[18:02] <arraybolt3> heh, then I'll just override it and call it a day.
[18:02] <tsimonq2> Let me be clear, those are two separate messages, lol
[18:02] <tsimonq2> Sorry, I was unclear
[18:02] <arraybolt3> oh.
[18:02] <arraybolt3> so, what am I doing?
[18:02] <tsimonq2> I do think *we* should move it but I doubt *upstream* will care 
[18:02] <arraybolt3> ahhh, ok then
[18:02] <tsimonq2> so if it involves patching the CMake file, if you don't just do it in the packaging, don't bother with upstream they won't care XD
[18:03] <arraybolt3> "Go! Stop! Walk. No, run! OK, turn around! No, stop!"
[18:03] <tsimonq2> LMFAO
[18:03] <tsimonq2> sorry
[18:03] <arraybolt3> np, just thought it was funny :P
[18:03] <arraybolt3> I'll just do it with another override, that's easier than patching and probably more reliable in the long run.
[18:05] <tsimonq2> Sweet.
 🤷‍♂ (re @lubuntu_bot: (irc) <tsimonq2> @kc2bez, @teward001: Did we need to seek *re*-qualification for LTS last time around, or were we just grandfathered in?)
[18:18] <arraybolt3> Victory!
[18:20] <tsimonq2> "Great success, very nice" -Borat, probably
[18:20] <tsimonq2> Let's keep an eye on the GitHub clone for https://github.com/lubuntu-team/manual - something is overwriting it, I think.
[18:21] <tsimonq2> It should be an exact copy of the Phab manual.
[18:21] <tsimonq2> Er, Gitea manual.
[18:21] <tsimonq2> cc @lynorian ^^^^^^^^^^
[18:22] <tsimonq2> Okay, so I'm preparing two announcements...
[18:23] <tsimonq2>  1) Announce the availability of LXQt 1.4 for Backports: https://notes.lubuntu.me/gr2Tv9iRSpe9uHvEYOmCtw#
[18:24] <tsimonq2>  2) Announce installer changes: https://notes.lubuntu.me/T-oS14rdS2G-m-r3FDILdw#
[18:24] <arraybolt3> ooo fun
[18:24] <tsimonq2> I'd like to publish #1 as soon as we get done testing Backports upgrades, both 0.17 -> 1.4 and 0.17 -> 1.3 -> 1.4.
[18:25] <arraybolt3> @teward001: you still haven't changed my notes.lubuntu.me password after the Vivaldi mess :P
[18:25] <tsimonq2> The second one, while ideally it would be done by EOD today, would mean a working installer on tomorrow's daily, and I know we have *several* issues surrounding that.
[18:25]  * arraybolt3 refills teward's Keurig in the hopes of not making him really mad
[18:26] <tsimonq2> Notably, I need to polish the QML frontend and add some more options for pkgselect, confirm nothing weird is going on with the onboard cdrom mini-archive, and do some further smoke testing to confirm e.g. version numbers have also been properly updated.
[18:26] <arraybolt3> and I need to fix encrypted installations
[18:27] <tsimonq2> That being said, all of that comes *after* the LXQt 1.4 work is done. From here, once those packages are uploaded and build in Backports Staging, assuming they're basically identical copies of what's in the archive for Noble, I have no problem testing then blasting it out.
[18:27] <tsimonq2> arraybolt3: What's wrong with them right now?
[18:27] <arraybolt3> No clue.
[18:27] <arraybolt3> But our testers have been reporting them failing lately
[18:28] <arraybolt3> I haven't looked into it at all, too busy with Other Stuff.
[18:28] <tsimonq2> No worries. Again, it's a team effort. I might want to rope wxl, teward, and/or kc2bez in anyway for some of that extra testing and polish.
[18:28] <tsimonq2> "Oh hi! How much coffee/beer do you need? :P"
[18:30] <tsimonq2> arraybolt3: Anyway, so I see you have lxqt-panel taken care of in the archive, just not in Backports yet. lxqt-runner should be the remaining one, and I really don't imagine that will present too much of a challenge for you.
[18:30] <arraybolt3> I'm managing the backport now.
[18:30] <tsimonq2> Let me know if you need help, otherwise I'm going to start drafting that announcement.
[18:30] <arraybolt3> I did a local sbuild so the build failure happened on my machine :)
[18:30] <tsimonq2> Thanks!
[18:30] <arraybolt3> Announcement drafting sounds good. I think I got this.
[18:30] <tsimonq2> Perfect, I appreciate it.
[18:31] <tsimonq2> I'm going to *try* getting some screenshots from a VM. Try. :P
[18:32] <arraybolt3> Heh, *might* be a bit early for that, lxqt-panel has some significant changes it looks like
[18:33] <arraybolt3> Patch prepared, rebuilding.
[18:33] <tsimonq2> Cool.
[18:34] <tsimonq2> https://paste.ubuntu.com/p/ZWy6xtzxx9/ <--- we might need to add appropriate Conflicts/Replaces (or some such relationships).
[18:34] <tsimonq2> I mean, Colin's intuition was right when he reviewed it in person.
[18:34] <tsimonq2> And I *know* you just removed that file from somewhere too, so. :P
[18:36] <arraybolt3> pretty sure I removed it, yeah
[18:36] <arraybolt3> ooof, my patch FTBFS
[18:37] <teward> arraybolt3: i been busy sue me
[18:37] <teward> paying job comes first :P
[18:37] <teward> had to do a weekend of work
[18:38] <arraybolt3>  /<<PKGBUILDDIR>>/plugin-taskbar/lxqttaskbutton.cpp:448:1: error: version control conflict marker in file
[18:38] <arraybolt3> So GCC can detect really silly goofs.
[18:38] <arraybolt3> Now we know.
[18:38]  * arraybolt3 sighs deeply
[18:38] <tsimonq2> Nice one. :)
[18:40] <arraybolt3> oh, and I forgot to add DEP headers to my last patch *facepalm*
[18:40] <arraybolt3> ok, so I may be finding my footing again here
[18:46] <arraybolt3> try #2 :P
[18:51] <arraybolt3> And now I removed an include that I was supposed to leave. Nice.
[18:52] <tsimonq2> Package: lxqt-qtplugin
[18:52] <tsimonq2> Depends: libfm-qt13, ${misc:Depends}, ${shlibs:Depends}
[18:52] <arraybolt3> ooops
[18:52] <tsimonq2> I got it.
[18:52] <arraybolt3> sorry about that
[18:53] <tsimonq2> No worries.
[18:53] <tsimonq2> Also, remember, you have @ubuntu.com and @lubuntu.me emails now :P
[18:53] <arraybolt3> yeah... I have to figure out how to get my email changed on my new GPG key (or duplicate the key and apply the other email to it also, or something)
[18:53] <arraybolt3> dunno how to do that
[18:54] <arraybolt3> but right now my GPG stuff is Just Working while using my gmail address so I'm hesitant to switch back until I know how on earth to do it.
[18:54] <tsimonq2> GPG keys are fun stuff. teward is definitey the expert. :P
[18:54] <arraybolt3> Hey, build worked this time!
[18:55] <tsimonq2> 🎉🎉
[18:56] <tsimonq2> Also, oooooh someone forgot to backport lxqt-qtplugin :P
[18:56] <arraybolt3> Probably did that before I realized we were backporting things...
[18:56] <tsimonq2> All good.
[18:57] <tsimonq2> I just like giving you a hard time XD
[18:57] <arraybolt3> well it is good to let me know so I can gradually get sharper :)
[18:57] <arraybolt3> FINALLY finished backporting lxqt-panel
[18:58] <arraybolt3> that package gave me a hard time, though not as hard as lxqt-config :P
[18:58] <tsimonq2> Niceeeeeeeeeeeeeeeeeee!
[18:58] <tsimonq2> hah :D
[18:59] <arraybolt3> now let's just really hope some esoteric architecture doesn't bomb out just to mock me :P
[19:01] <arraybolt3> Alright, food, then lxqt-runner, in that order :)
[19:04] <arraybolt3> Be prepared for lxqt-panel to be a glitchy mess, the backporting was rather complicated.
[19:04] <arraybolt3> (in jammy I mean)
[19:04] <tsimonq2> Same with pcmanfm-qt, heh.
[19:04] <arraybolt3> so the main two desktop components may be a disaster XD
[19:05] <tsimonq2> yes this is perfect, such Alpha very cool XD
 https://matterbridge.lubuntu.me/488a2b0f/doge_dogeintensifies.mp4
[19:06] <tsimonq2> Nah, in all seriousness though, let's take a hammer to any bugs we see, on sight.
[19:06] <arraybolt3> sounds good
[19:06] <tsimonq2> NO BUGS ALLOWED OMGWTFBBQ!!!!1111111 -Every developer, ever
[19:08] <tsimonq2> arraybolt3: libfm-qt has been *accepted* from binary NEW.
[19:08] <tsimonq2> arraybolt3: 19:07 < vorlon> tsimonq2: I: libfm-qt14: hardening-no-fortify-functions [usr/lib/x86_64-linux-gnu/libfm-qt.so.14.0.0]
[19:08] <arraybolt3> the hardening flag is set so I just ignored that.
[19:09] <arraybolt3> Either a lintian bug or something wrong with the build system, either way Not Our Problem(TM) (though perhaps worth some investigation in upstream).
[19:09] <tsimonq2> Sounds good.
[19:10] <tsimonq2> I say, sometime within the next hour we should have movement on libfm-qt reverse dependencies.
[19:10] <tsimonq2> The publisher cycle, then the retry cycle.
[19:11] <tsimonq2> If you can upgrade to the new libfm-qt from noble-proposed on an actual system, I'd say the publisher round is done and you can manually retry anything that hasn't been done yet.
[19:12] <tsimonq2> Either way, I'm going to focus more energy on some lunch (be back in a little bit) and the announcement + screenshots + verbosity for the normally terse LXQt release announcements (help here is welcome), otherwise I'll leave the rest of the packaging bits to you, and we can meet somewhere in the middle with testing/announcement #2
[19:12] <arraybolt3> I'll finish lxqt-runner first, then maybe start experimenting in that regard.
[19:12] <arraybolt3> tsimonq2: Sounds like a plan!
[19:12] <tsimonq2> Thanks!
[19:13] <tsimonq2> arraybolt3: Don't forget to add the missing Breaks/Replaces :)
[19:13] <tsimonq2> See -release and vorlon's comment on the image building
[19:14]  * tsimonq2 lunch
[19:16] <arraybolt3> to be clear, adding Breaks/Replaces to lxqt-menu-data, specifying that it breaks any LXQt components <= 1.3.0 that used to contain menu data?
[19:16] <arraybolt3> lxqt-panel and lxqt-config are the two I know of, not sure which others but I'll find out
[19:18] <arraybolt3> ah, and also pcmanfm-qt
[19:20] <arraybolt3> or are you referring to lxqt-qtplugin?
[19:20] <arraybolt3> nah you did that one already
 did I tho?
 yes :) (re @lubuntu_bot: (irc) <arraybolt3> to be clear, adding Breaks/Replaces to lxqt-menu-data, specifying that it breaks any LXQt components <= 1.3.0 that used to contain menu data?)
 actually I'd do any version less than upstream 1.4, if it were me
 but Trust The Policy
[19:26] <arraybolt3> https://launchpad.net/ubuntu/+source/lxqt-qtplugin/1.4.0-0ubuntu2 sure looks like you did
[19:34] <arraybolt3> tsimonq2: https://termbin.com/lirv (need confirmation that this is right before I upload to the archive and shatter all of everything on accident)
 Go for it.
 That's different, actually. (I'm sure you know that.) (re @lubuntu_bot: (irc) <arraybolt3> https://launchpad.net/ubuntu/+source/lxqt-qtplugin/1.4.0-0ubuntu2 sure looks like you did)
[19:43] <arraybolt3> right, I was asking which one of two things needed done and realized you had done #2 so it must be #1.
 Ah, right :) same page
[19:45] <arraybolt3> Uh-oh.
 ...oh?
[19:45] <arraybolt3> tsimonq2: you may have forgotten to push your last changes to lxqt-build-tools :)
[19:45] <arraybolt3> Got this attempting to upload: "lxqt-menu-data_1.4.0-0ubuntu2.dsc: Version older than that in the archive. 1.4.0-0ubuntu2 <= 1.4.1-0ubuntu1"
 Ah, drat.
 Feel free to manually import my changes/separate it out, I'll be an hour or two.
[19:46] <arraybolt3> kk, sounds good
 Otherwise, if you want good, consistent history, wait to do anything on the Git side and just manually grab my package from the archive, and iterate on it
 I mean, it's easier to import a change like that later than to import this massive changeset now, don't you think?
 I know, running in circles again, but I'm allowed to change my mind :P
[19:50] <arraybolt3> Ummm...
[19:50] <arraybolt3> the changeset wasn't very big :P and I sort of already did everything
[19:50] <arraybolt3> If nothing else, our combined version are now in the archive
[19:50] <arraybolt3> I'll hold off on git pushing for now
[19:51] <arraybolt3> gah! "The signer of this package is lacking the upload rights for the source package, component or package set in question."
[19:51]  * arraybolt3 kicks the archive
[19:52] <arraybolt3> tsimonq2: sponsor this for me when you get back: https://drive.google.com/file/d/1PwwR4phy6oMFSLBWAwgH_vMiKB9ciA05/view?usp=sharing
 Bruh, Google Drive XD
[20:58] <arraybolt3> Just uploaded lxqt-menu-data_1.4.1-0ubuntu2~ppa1 to Backports Staging.
[20:58] <arraybolt3> So now lxqt-runner is all we have left :D
 Sweeeeeeeet!
 @guiverc @Leokolb @Roberalz etc. I'd appreciate some testing help with Backports Staging/Backports (if you see this later) :) ^^^^
[21:01] <guiverc> ack.
[21:01] <arraybolt3> sigh, this is another package that will need some fixing to work in backports
[21:12] <arraybolt3> lxqt-runner uploaded to Noble, once the latest lxqt-menu-data is uploaded the Noble LXQt stack will be complete. Working on the backport now.
 Thanks. I'll be around again at about 4. Feel free to start smoke testing, specifically comparing the GUI for adding the Lubuntu Manual, and the panel functionality you talked about :)
[21:28] <arraybolt3> lxqt-runner uploaded to backports-staging
[21:29] <arraybolt3> Once that finishes building, the new stack is ready to test :D
 \o/ (re @lubuntu_bot: (irc) <arraybolt3> https://launchpad.net/ubuntu/+source/lxqt-qtplugin/1.4.0-0ubuntu2 sure looks like you did)
[21:50] <tsimonq2> arraybolt3: btw I did it too :/ https://git.lubuntu.me/Lubuntu/pcmanfm-qt-packaging/src/branch/ubuntu/noble/debian/control
[21:50] <tsimonq2> Waiting on another iteration of pcmanfm-qt.
[21:51] <arraybolt3> welp :)
[21:53] <tsimonq2> Should be taken care of, I think.
[21:54] <tsimonq2> arraybolt3: lxqt-menu-data is now in the packageset, by the way.
[21:54] <arraybolt3> Yay, will upload soon.
[21:54] <tsimonq2> I already did XD
[21:55] <arraybolt3> Ah
[21:55] <tsimonq2> Anyway, I think I'll wait for this publisher run to finish, to get the results of a "clean" upgrade.
[21:55] <tsimonq2> Right now I've been doing the unpublished stuff piecemeal.
[21:55] <tsimonq2> Meh, well, I might as well just throw it in my local archive to try it...
[21:58] <tsimonq2> I love that xscreensaver randomly triggers on the live session >_<
[21:59] <tsimonq2> I'm not about to SRU casper, noooooooooo way.
[22:04] <tsimonq2> Kay, a couple of issues I'm seeing to start, that I'd consider blockers...
[22:05] <tsimonq2>  1) LXQt power management continuously crashes, I'm going to revert my preliminary patch for the time being in Backports only, until it's mature.
[22:05] <tsimonq2>  2) The Lubuntu Manual icon isn't set as the default anymore, so something definitely changed.
[22:06] <tsimonq2>  3) X-Leave is super weird as a menu title. Before I ship this out to Backports users, I want to be sure that translations *and* existing menu items stay where they belong.
[22:06] <tsimonq2> Looking for any additional feedback on LXQt 1.4. Throw it my way. :)
[22:07] <tsimonq2> In the meantime, I'll be hard at work on these issues.
[22:09] -queuebot:#lubuntu-devel- Packageset: Added lxqt-menu-data to lubuntu in noble
[22:10] <tsimonq2> <3 arraybolt3 kc2bez ^^^
[22:21] <tsimonq2> Yeah, something is definitely wacked out with this pcmanfm-qt update.
[22:22] <tsimonq2> Essentially, the background shows up black and there's nothing checked in here:
 https://matterbridge.lubuntu.me/7816e09e/file_10108.jpg
[22:22] <tsimonq2> Even though the icons actually do exist on the desktop.
[22:22] <tsimonq2> This will be a fun one. :)
[22:23] <tsimonq2> *Something* got mucked up here.
[22:24] <tsimonq2> Quite possibly. Hm.
[22:24] <tsimonq2> I guess for now, we'll have to wait and see when it comes to Noble.
[22:24] <tsimonq2> Might have some fun with git bisect, who knows?
[22:25] <tsimonq2> Anyway, I'm being pulled away for an impromptu brainstorming meeting at work. I have the draft announcement done, but I want to pad it with some screenshots and a feature list, for the press to go wild over.
[22:25] <tsimonq2> I should be back sometime before 6.
[23:04] <tsimonq2> Nah, I don't think it's related to env vars at *all*.
[23:04] <tsimonq2> Let me see if it's just stupidly clobbering the config.
[23:10] <tsimonq2> Greeeeeeeeat. I can't reproduce it. Just wonderful.
[23:19] <tsimonq2> Kay, so none of the menu items are different. Time to check with translations...
[23:20] <tsimonq2> Spanish gets the first test :D
 For your musings... : https://matterbridge.lubuntu.me/e4b126e7/simplescreenrecorder.mkv
 https://matterbridge.lubuntu.me/a257f839/new.mkv
[23:23] <tsimonq2> Does anyone have a clue on why X-Leave is a thing, instead of Leave?
[23:24] <tsimonq2> I'm probably going to just completely replace that new stuff with the old icon and text.
[23:24] <tsimonq2> Well, that might affect translations... this sucks :/
 I don't know anything about xleave
[23:26] <tsimonq2> Kay, guess I'm patching it. XD
 I also have qterminal now crashing every time I start it up on noble
[23:34] <tsimonq2> That's probably going to happen for the next day or two, unfortunately.
[23:34] <tsimonq2> The stack is migrating in parts, so it'll be a little bit before it all migrates.
[23:34] <tsimonq2> I hope we're on the tail end of all that, but I keep watching the Britney runs optimisically, so. :)
[23:34] <tsimonq2> *optimistically
[23:36] <tsimonq2> Spanish install is running, let's see how badly this regresses. :P
[23:40] <tsimonq2> arraybolt3: Oh Aaaaaaron :P
[23:40] <tsimonq2> Package: xdg-desktop-portal-lxqt
[23:40] <tsimonq2> Depends: libfm-qt-dev (>= 1.3.0),
[23:40] <tsimonq2> Fixing...
[23:41] <arraybolt3> Re xleave, I saw something like that in GNOME once.
[23:41] <arraybolt3> Gah, thanks for catching my boffo
[23:41] <tsimonq2> I didn't catch it, Britney did. :P
[23:42] <arraybolt3> (And now you know why I wanted that added to the checklist.)
[23:42] <tsimonq2> Right right :D
[23:42] <arraybolt3> Oh lovely >_<
[23:43] <tsimonq2> Fixed, pushed, and uploaded.
[23:46] <arraybolt3> I should make an "abbreviated checklist" for packaging - I kept skimming through the guide because of all the redundant steps (like specifying to add a changelog entry and commit for each change). It was quite helpful as a newbie, but having gotten more experience it gets slightly in my way.
[23:48] <tsimonq2> I agree, like a "cheat sheet."
[23:48] <tsimonq2> So, looks like 22.04 in Spanish doesn't have my nice menu translation enhancements. Looks like we didn't SRU that.
[23:49] <tsimonq2> (We *could*... if we wanted to, but it's in Backports.)
[23:49] <tsimonq2> I'm going to double-check everything is still properly translated in 1.3 and then upgrade to 1.4, which will test your lxqt-panel patch skills. :P
[23:49] <arraybolt3> Good luck >:-)
[23:50] <tsimonq2> Heh, thanks :P
[23:50] <tsimonq2> Looks like a few packages just migrated to Noble, from the emails I'm receiving.
[23:50] <tsimonq2> Let's see what excuses thinks now...
[23:50] <arraybolt3> very hopeful
[23:51] <tsimonq2> Hasn't updated yet, prob gotta give it a min :)
[23:51] <arraybolt3> Anyways, methinks I shall get to encrypted installation failure debugging.
[23:51] <tsimonq2> Sweeeet.
[23:51] <arraybolt3> Yeah, I've held off updating my Noble VM after the warning that it may eat kittens
[23:52] <arraybolt3> (I labeled my PPA with a warning "may convert your HVAC unit into a fire-breathing dragon" :P)
[23:52] <tsimonq2> I saw that XD
[23:52]  * arraybolt3 wonders if my quick downloader script still works
[23:52] <tsimonq2> Gah, something might *already* be b0rked, let me check...
[23:53] <arraybolt3> Oh hey, iso.qa.ubuntu.com just loaded with https and looks right \o/
[23:53] <arraybolt3> when did that happen?
[23:55] <arraybolt3> Wow, getting 3 MiB/s down, rare for my connection
[23:57] <tsimonq2> Ahh mmkay, so with my change to the panel, I also added some packages to the installer which actually give us additional translations.
[23:57] <tsimonq2> There does not seem to be a reliable way to actually deliver those new packages to existing users... so we release note it.
[23:57] <tsimonq2> Anyway, I'm seeing that this works.