=== teward changed the topic of #lubuntu-devel to: Lubuntu Development | Current dev version: Noble Numbat (24.04) | Schedule: https://ubottu.com/y/mm | Testing: http://iso.qa.ubuntu.com/qatracker | Support: #lubuntu | Offtopic: #lubuntu-offtopic | Telegram: https://telegram.lubuntu.me/development | Discourse offline for maintenance, updates, etc. No ETA on return.
[13:05] <kc2bez> https://github.com/lxqt/lxqt/releases/tag/1.4.0
[13:25] <lubot> [telegram] <tsimonq2> I just received in-person permission from vorlon to immediately start that transition
[13:51] <tsimonq2> Fuuuuuuuuuuuuuuuulllllllllllllllllllll speeeeeeed aheadddddd!
[13:51] <tsimonq2> lxqt-build-tools build running locally. All hands on deck :D
[15:40] <tsimonq2> Okay, so now we're waiting on a member of the Archive Team to accept lxqt-menu-data. It's completely Lintian-clean.
[15:40] <tsimonq2> I'm still in Riga (for my last night), so I'll nag people until someone agrees ;)
[15:41] <lubot> [telegram] <kc2bez> XD
[16:01] <lubot> [telegram] <tsimonq2> I got out of the closing plenary first and waited until I spotted an archive admin XD
[16:02] <lubot> [telegram] <tsimonq2> Colin took care of the source, just wondering if lxmenu-data and lxqt-menu-data have conflicting files
[16:02] <lubot> [telegram] <tsimonq2> If anyone can confirm or deny, cool, if not I'll look in a bit
[16:02] <lubot> [telegram] <tsimonq2> The packaging is in Gitea, fully up to date, just need mirroring to LP and GH
[16:37] <lubot> [telegram] <kc2bez> Seems like they shouldn't conflict if I am reading this correctly. https://github.com/lxqt/lxqt/pull/2423 (re @tsimonq2: Colin took care of the source, just wondering if lxmenu-data and lxqt-menu-data have conflicting files)
[16:37] -ubottu:#lubuntu-devel- Pull 2423 in lxqt/lxqt "Replace lxmenu-data with  lxqt-menu-data" [Merged]
[16:50] <arraybolt3> Grief, I only just woke up :P
[16:50] <tsimonq2> arraybolt3: Hey! Huge issue for you to help with >>D
[16:50] <tsimonq2> arraybolt3: So, here's the thing...
[16:50] <arraybolt3> Nice, wassup?
[16:51] <tsimonq2> arraybolt3: Some packages have LGPL-2.1 longtext, in fact I think all of LXQt does. As far as I'm aware, LGPL-2.1+ is not compatible.
[16:51] <arraybolt3> ? I thought they were, lemme check
[16:52] <tsimonq2> arraybolt3: The longtext license is indentical, I *think*. Which means, anything which doesn't have a copyright header is defauling to LGPL-2.1
[16:52] <tsimonq2> Anyway, that's an issue I have to fix on the next upload of lxqt-menu-data, but in general I think as a team we need to review all the packages and ensure compatibility :)
[16:52] <tsimonq2> Ah, the confusion of a single +
[16:52] <tsimonq2> :P
[16:52] <arraybolt3> kk
[16:53] <tsimonq2> Thanks for your help, if you don't get to it, I will when I'm home :)
[16:53] <arraybolt3> https://www.gnu.org/licenses/gpl-faq.en.html#compat-matrix-footnote-6
[16:53] <arraybolt3> They're ckppompatible 
[16:53] <arraybolt3> Wow, thanks chromeos
[16:53] <arraybolt3> *Compatible
[16:54] <tsimonq2> Also, maybe give me a package or two to sponsor and I can add you back to ~lubuntu-dev if you're interested :)
[16:54] <tsimonq2> hah :D
[16:54] <arraybolt3> K, I'll see what I can make happen
[16:55] <arraybolt3> We're packaging LXQt 1..4.0 wholesale right?
[16:55] <tsimonq2> I generally trust your judgement, this just came up irl and I had a 10 minute convo with Mattia about licensing ;D
[16:55] <tsimonq2> Yeah :)
[16:55] <arraybolt3> Could not erase that extra period for the life of me...
[16:55] <tsimonq2> hahahahahahaha
[16:55]  * arraybolt3 goes to a real computer
[16:55] <tsimonq2> Anyway, I'm headed to the afterparty, but I know it's quite earlier there. :)
[16:56] <arraybolt3> ok how many things have we already packaged?
[16:56] <arraybolt3> anything yet?
[16:56] <tsimonq2> Anything you can do is appreciated / if you can't/there's nothing actionable that's cool too I'll take care of it :)
[16:56] <tsimonq2> Well, lxqt-build-tools and lxqt-themes did not get a version bump.
[16:56] <tsimonq2> libqtxdg is already in Noble and Backports Staging, lxqt-menu-data is kinda the blocker for the next step
[16:57] <tsimonq2> https://github.com/lxqt/lxqt/wiki/Building-from-source
[16:57] <tsimonq2> Also TODO add to scripts
[16:57] <arraybolt3> kk, yeah according to the FSF themselves LGPL2.1 and LGPL2.1+ are compatible, but you can't upgrade the whole combo to LGPL3.0+ thereafter.
[16:57] <arraybolt3> so no big deal for the time being
[16:57] <arraybolt3> alright, lemme pop open some things
[16:59] <arraybolt3> lxqt-menu-data is a brand new package yes?
[16:59] <lubot> [telegram] <kc2bez> Yes
[17:01] <arraybolt3> For some reason I can't make a Noble sbuild env
[17:01] <arraybolt3> E: Failed getting release file http://archive.ubuntu.com/ubuntu/dists/noble/Release
[17:01] <arraybolt3> But I can wget that file or open it in Vivaldi just fine
[17:02] <arraybolt3> I can even curl it so it's not having any redirect weirdness
[17:02] <arraybolt3> I wonder if somehow squid-deb-proxy is in the way...
[17:06] <arraybolt3> nope, archive.ubuntu.com is allowed
[17:06] <arraybolt3> so what on earth?!
[17:18] <arraybolt3> Rogue proxy issue, fixed.
[17:19] <arraybolt3> Still not sure where it was picking up my proxy from but I finally just modded the mk-sbuild script directly and removed the part that handed a proxy to debootstrap XD
[17:19] <arraybolt3> really I ought to figure out what I've misconfigured so I don't have to do that nonsense
[17:23] <arraybolt3> yep, it's squid-deb-proxy after all.
[17:23] <arraybolt3> grrrrrr
[17:23] <arraybolt3> ls
[17:24] <arraybolt3> alright, just going to make the sbuild env proxyless and then wire in the proxy after the fact
[17:52] <arraybolt3> tsimonq2: One complication with adding me back to lubuntu-dev... I expired from lubuntu-members too.
[17:53] <arraybolt3> guiverc tried to warn me about that but I wasn't able to get it corrected in time.
[17:55] <lubot> [matrix] <kc2bez> arraybolt3 @arraybolt3:matrix.org: shoot the council an email for posterity sake.
[17:56] <arraybolt3> +1
[17:58] <arraybolt3> but first packaging
[18:08] <arraybolt3> anyway, yeah tsimonq2: LGPL-2.1 and LGPL-2.1+ can be mixed, it just has to be understood that the combo as a whole is treated as LGPL-2.1 but the individual 2.1+ files can be horked by other things and be used as 2.1+ (assuming I'm reading the compatibility guidelines correctly).
[18:08] <arraybolt3> In the mean time, I guess I'll package liblxqt.
[18:33] <arraybolt3> tsimonq2: Also good news, the AUTHORS files in some of the lxqt packages (at least liblxqt) specifically says the repository-wide license is LGPL-2.1+.
[18:34] <arraybolt3> So we can use that as an escape hatch for probably most of the packages :)
[18:38] <arraybolt3> we still have downstream symbols files yes?
[18:38] <arraybolt3> I mean, obviously we do, so nvm
[18:39] <lubot> [telegram] <teward001> i would be careful assuming repo-wide.  it can still be overridden with files that have specific other licensing - blanket licensing isnt a guarantre
[18:40] <lubot> [telegram] <teward001> guarantee*
[18:40] <arraybolt3> I know, but I mean as far as the default license goes.
[18:40] <arraybolt3> Sure individual files can override, but files with no license header default to LGPL-2.1+ if the AUTHORS file says so.
[18:40] <arraybolt3> (See backlog for why this is important)
[19:06] <arraybolt3> Ah, my old nemesis, RISC-V.
[19:18] <arraybolt3> sigh. libqtxdg-3.12.0-0ubuntu1 is built *and published*, yet my noble schroot can't see it.
[19:18] <arraybolt3> now I have libqtxdg in a PPA waiting to publish, and until one of those finishes I can't test-build liblxqt.
[19:19] <arraybolt3> So I guess then I'm taking an impromptu break :P
[19:51] <arraybolt3> gah, it still doesn't want to work
[19:52] <arraybolt3> It keeps telling me that it either can't find lxqt-build-tools >= 0.13.0 (if I try using my PPA), or that it can't find libqt5xdg-dev >= 3.11.0 if I try without my PPA. What's creepy is that both packages (with sufficient versions) can be seen in my noble schroot.
[19:52] <arraybolt3> And can be installed via apt manually together.
[19:53] <arraybolt3> Maybe my shm settings are messing with things
[19:53] <arraybolt3> huh, actually yep that was it
[19:56] <arraybolt3> I hate these sorts of weird bugs.
[19:56] <arraybolt3> Anyways, guess now I know what to debug next.
[20:02] <arraybolt3> tsimonq2: https://git.lubuntu.me/Lubuntu/liblxqt-packaging ready for your review :)
[20:59] <lubot> [telegram] <teward001> tell me about it.  Discourse Docker kind of lit itself aflame due to an unreproducible bug. (re @lubuntu_bot: (irc) <arraybolt3> I hate these sorts of weird bugs.)
[20:59] <lubot> [telegram] <teward001> one that has happened before and requires a complete clean/reset of Docker to make it work again, including a container rebuild
[20:59] <lubot> [telegram] <teward001> *hisses in annoyed-sysadmin*
[21:10] <arraybolt3> fun
[21:40] <arraybolt3> Found my bug - I had accidentally configured my noble-amd64-shm chroot to point to my jammy-amd64 root. 🤦
[21:41] <arraybolt3> So now that I'm building for the development release instead of the release from one and a half years ago, things are working a bit smoother :D
[21:43] <arraybolt3> tsimonq2: https://git.lubuntu.me/Lubuntu/qtxdg-tools-packaging ready for review also
[21:46] <arraybolt3> also if anyone else wants in on the packaging fun, I threw up a PPA at https://launchpad.net/~arraybolt3/+archive/ubuntu/lxqt-dev-noble
[21:53] <tsimonq2> arraybolt3: thanks for your work, might be a day or two before I sponsor (wxl kc2bez teward feel free) but I *deeply* appreciate it :)
[22:15] <kc2bez> I need to get my noble dev box going. It was on my weekend list but I didn't get to it yet. 
[22:46] <arraybolt3> kc2bez: Email to council sent.
[22:47] <arraybolt3> I see Simon was anxious to move forward a bit quicker than I was moving though :P so there's a slight time discrepancy between when I was added back to ~lubuntu-members and when I sent the reapplication email XD
[22:51] <tsimonq2> "Leadership occasionally requires bold decisions that will not be widely understood, consensual or popular. We value the courage to take such decisions, because they enable the project as a whole to move forward faster than we could if we required complete consensus. Nevertheless, boldness demands considerateness; take bold decisions, but do so mindful of the challenges they present for others, 
[22:51] <tsimonq2> and work to soften the impact of those decisions on them. Communicating changes and their reasoning clearly and early on is as important as the implementation of the change itself."
[22:51] <arraybolt3> +1
[22:51] <tsimonq2> If the LC decides to -1 arraybolt3's Lubuntu Membership, I respect that fully, but for the record, I am +1.
[22:52] <arraybolt3> Thanks :)
[22:52] <arraybolt3> Gotta do some work to make food, then coming back to assault libfm-qt.
[22:53] <tsimonq2> And to be clear, I'm very strict on development rights, I'm less strict on pure membership rights, particularly with the deep impact you have had on this project. Let me make this clear: even if it's emeritus, you are always welcome as a Lubuntu Member.
[22:53] <tsimonq2> arraybolt3: enjoy :)
[23:41] <arraybolt3> hmm... wrap-and-sort wants to do interesting things to the control file for libfm-qt :P
[23:42] <arraybolt3> "Replaces: libfm-qt12, libfm-qt11, libfm-qt9"   -->   "Replaces: libfm-qt11, libfm-qt12, libfm-qt9"
[23:42] <arraybolt3> yeah no
[23:44] <tsimonq2> wtf o_o
[23:44] <arraybolt3> numeric sort vs. alphabetic sort
[23:44] <tsimonq2> Please file a bug against that package if you get the chance
[23:44] <tsimonq2> right
[23:44] <arraybolt3> sure thing
[23:44] <tsimonq2> thanks :)
[23:45] <arraybolt3> also have an upstream bug to file in LXQt (they forgot to mention that lxqt-menu-data is a build dep of libfm-qt now)
[23:46] <arraybolt3> so anywho, bug filing while package builds
[23:46] <tsimonq2> I don't know if I'm going to sleep, since the afterparty ended at 11 and the travel agency decided to give the vast majority of us morning flights, but once I get home around 4 PM Central tomorrow, I am *hard* crashing for maybe a day or two, heh
[23:46] <tsimonq2> arraybolt3: ooooooooh good catch
[23:46] <arraybolt3> oh man
[23:46] <tsimonq2> and thanks :)
[23:47] <tsimonq2> (I guess I should say closing party, since it was official)
[23:50] <tsimonq2> Side note, because I know I'm going to forget... this should be addressed in lxqt-build-tools:
[23:50] <tsimonq2>   Compatibility with CMake < 3.5 will be removed from a future version of
[23:50] <tsimonq2>   CMake.
[23:50] <arraybolt3> ah, good to know
[23:53] <arraybolt3> oooh, soname bump
[23:53] <arraybolt3> this is gonna be fun
[23:54] <lubot> [telegram] <tsimonq2> https://matterbridge.lubuntu.me/071bd31d/noo_god_no.mp4
[23:54] <tsimonq2> jk XD
[23:55] <arraybolt3> like symbols files, but worse? :P
[23:57] <tsimonq2> nah one level worse compared to symbols files is converting runit units to systemd :P
[23:57] <tsimonq2> or copyright... yeah, copyright :P
[23:58] <arraybolt3> oof, systemd transition sounds painful
[23:59] <arraybolt3> here's hoping we're finally using the last of the great init systems
[23:59] <arraybolt3> of course some day it'll probably be replaced by systemd2 and then we'll all go and cry in the corner and then mass-rebuild the world
[23:59] <tsimonq2> many people would argue that systemd is a great init system... I do agree tho ;)
[23:59] <tsimonq2> hahahahahahahahahahahahahaha
[23:59] <tsimonq2> I was joking about X12 today... :P
[23:59] <arraybolt3> rofl