 arraybolt3: now start uploading XD
[00:36] <arraybolt3> heh, got my equivalent of $dayjob on the other line right now :P so give me a bit
 No worries ;)
[05:24] <arraybolt3> Has anyone already uploaded libfm-qt? And also where can I see the NEW queue so I can answer these questions for myself later?
[05:26] <arraybolt3> nvm, found it for myself, libfm-qt still needs uploaded
[05:31] -queuebot:#lubuntu-devel- New binary: libfm-qt [amd64] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[05:32] -queuebot:#lubuntu-devel- New binary: libfm-qt [s390x] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[05:32] -queuebot:#lubuntu-devel- New binary: libfm-qt [armhf] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[05:32] -queuebot:#lubuntu-devel- New binary: libfm-qt [ppc64el] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[05:34] <arraybolt3> Is there any special process involved in getting new binaries into the development release? I don't think https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages has any relevant information on that.
[05:34] <arraybolt3> (new binaries from existing source packages I mean)
[05:35] -queuebot:#lubuntu-devel- New binary: libfm-qt [arm64] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[06:08] -queuebot:#lubuntu-devel- New binary: libfm-qt [riscv64] (noble-proposed/universe) [1.4.0-0ubuntu1] (lubuntu)
[06:21] <guiverc> just noting this, but I've received a report that Lubuntu noble 'hung' during install  (~30 mins to install to ssd system; 5-10 for ubuntu desktop).. another reported lubuntu took far longer than xubuntu ; neither person (#ubuntu-next) reported bugs.. 
[06:27] <arraybolt3> We've had a bunch of install problems recently right? I'll take a look tomorrow and see if there's something to be sorted out.
[06:28] <arraybolt3> Maybe also tackle some other items on The List other than just the LXQt upgrade and the network and Bluetooth managers.
[06:29] <guiverc> i was just noting it... we can 'monitor' at this stage.. I did an install earlier today & all was good (7 mins, but I have no comparison for the time)... repeated install with encryption & failure-to-install...   install issues maybe need attention (with slow boot we can wait until bug report filed)
[06:29] <guiverc> we're very early in the cycle
[06:30] <arraybolt3> Yeah. Still, no install is no bueno
 arraybolt3: You have upload access to do binary NEW for packages you already have upload access to. You'll have access for source NEW once you're a MOTU
[15:38] <R> When I try to install Lubuntu on new modern machines without a CD, it crashes because it is searching CD. I tried to correct the source file - comment the rows with cd. Refresh and try again. But the problem persists. Is there a solution to this problem? I want Lubuntu on my machines!
[15:41] <kc2bez> It isn't really looking for a physical CD. This question belongs in the support channel though. 
[15:42] <kc2bez> !support | R 
[15:59] <R> Sorry for the second asking, but i am lost your answer! when trying to install lubuntu on new modern machines (without tcd)- it faults, because it is searching for CD! I trying to edit source file - I comments rows with cd and only web is available! But it is stil crashed - the problem persist! Is there a solution to this issue?
[16:00] <kc2bez> Let's move this to the support channel please. 
[16:01] <R> Ok, Thank you!
[19:13] <tsimonq2> arraybolt3: Yo, so do we have some testing yet as to whether we'll need runtime deps too? https://git.lubuntu.me/Lubuntu/libfm-qt-packaging/commit/d5ecfb6681f6624ee64a78d435b15b03e2ce8955
[19:13] -ubottu:#lubuntu-devel- Commit d5ecfb6 in Lubuntu/libfm-qt-packaging "Add lxqt-menu-data as a build dep"
[19:13] <tsimonq2> arraybolt3: I'll upload as-is (assuming I don't find anything else) simply to move the needle forward, but we should keep an eye on it.
[19:13] <arraybolt3> I already uploaded that :)
[19:14] <tsimonq2> I didn't even check yet ;)
[19:14] <arraybolt3> I thought adding a build dep also pulled in a runtime dep if needed?
[19:14] <tsimonq2> I *think* there's some automagic there?
[19:14] <arraybolt3> ${misc:Depends}
[19:14] <tsimonq2> Would be worth double checking, though. Just something to keep an eye on.
[19:14] <arraybolt3> kk
[19:15] <arraybolt3> once the NEW binary gets through I can start uploading Stage III stuff
[19:15] <arraybolt3> I'm using a PPA in the mean time to accelerate things and am up to pavucontrol-qt
[19:18]  * Eickmeyer triages bug report.... bug 2043310
[19:18] -ubottu:#lubuntu-devel- Bug 2043310 in calamares (Ubuntu) "Calamares installs rather slow" [Undecided, New] https://launchpad.net/bugs/2043310
[19:19] <tsimonq2> XD
[19:19] <Eickmeyer> "feels rather slowly (around 30min) and then finishes well."
[19:19] <Eickmeyer> 💀
[19:19] <tsimonq2> ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[19:19] <tsimonq2> I know exactly what that is
[19:20] <Eickmeyer> I was about to chalk it up to "opinion" based on hardware performance. 💀
[19:22] <tsimonq2> Responded.
[19:24] <Eickmeyer> 🤌
[19:24] <Eickmeyer> (for lack of snapping fingers)
[20:02] <tsimonq2> arraybolt3: https://lists.ubuntu.com/archives/lubuntu-devel/2023-November/002003.html <3
[20:03] <tsimonq2> arraybolt3: https://twitter.com/LubuntuOfficial/status/1723793721328582912 <3
[20:27] <arraybolt3> tsimonq2: thanks for the vote of confidence :)
[20:27] <tsimonq2> Of course, Aaron :)
[21:02] <kc2bez> I concur with tsimonq2 
[21:07] <tsimonq2> git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/commit/?id=a598d2b00869f80c0ac1229f1958485751c78883
[21:07] -ubottu:#lubuntu-devel- Commit a598d2b in ~lubuntu-dev/ubuntu-seeds/+git/lubuntu "Demote quite a bit of packages to recommends."
[21:07] <tsimonq2> https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/commit/?id=c22a02182e96f682bf04f971c464e9b1ee90ee3c
[21:07] -ubottu:#lubuntu-devel- Commit c22a021 in ~lubuntu-dev/ubuntu-seeds/+git/lubuntu "Add lxqt-menu-data as a depends, in case it doesn't get pulled in by another package HEAD noble"
[21:13] <kc2bez> Quite a bit of packages. Much packages. :P
[21:27] <tsimonq2> All of the packages. :P
[21:27] <tsimonq2> https://launchpad.net/ubuntu/+source/lubuntu-meta/24.04.1
[21:28] <kc2bez> That should setup minimal nicely. 
[21:29] <tsimonq2> I think so, too.
[22:00] <guiverc> it'll make many end-users happy too (comments on 'bloat' etc)
[22:01] <tsimonq2> If anyone has further feedback on demotion/promotion between depends/recommends, as well as options for the minimal install and pkgselect, let me know.
[22:01] <tsimonq2> Also, I will be updating the wording to match the new Ubuntu Desktop Installer (default install vs full install)
[22:01] <tsimonq2> Maybe have three options, default, minimal, full
[22:01] <tsimonq2> *shrug*
[22:02] <tsimonq2> I'll play with it, any opinions in either direction would be cool
[22:11] <tsimonq2> arraybolt3: I sent you a Matrix PM for you to look at, at your convenience, with more details/next steps.
[22:12] <tsimonq2> arraybolt3: In the meantime, I'm going to go through what you've already prepared for packaging, and continue the LXQt 1.4 transition.
[22:12] <tsimonq2> arraybolt3: If you're going to be on tonight, just let me know so we can coordinate. Same with wxl, teward, or kc2bez if you'd like to assist.
[22:17] <tsimonq2> A little promo for the manual :D https://twitter.com/LubuntuOfficial/status/1723827150548000985
[22:19] <tsimonq2> Reviewing lxqt-qtplugin.
[22:19] <tsimonq2> I'm literally just skimming a git diff to make sure I don't see anything crazy, and then uploading. ;)
[22:19] <tsimonq2> You know better now. :P
[22:22] <tsimonq2> https://launchpad.net/ubuntu/+source/lxqt-qtplugin/1.4.0-0ubuntu1 will FTBFS due to depwait
[22:24] <tsimonq2> This one *shouldn't* FTBFS due to depwait: https://launchpad.net/ubuntu/+source/obconf-qt/0.16.3-0ubuntu1
[22:25] <tsimonq2> Oh shoot, I almost forgot to concurrently upload to Backports.
[22:31] <tsimonq2> This one should also be good: https://launchpad.net/ubuntu/+source/pavucontrol-qt/1.4.0-0ubuntu1
[22:33] <tsimonq2> libfm-qt FTBFS on all Jammy arches. Very nice, very cool, great success.
[22:35] <tsimonq2> Just waiting for armhf to finish building in Backports Staging, so I can update symbols.
[22:36] <tsimonq2> (Note for other packagers: this is something that's prone to happen when Backporting. Jammy uses a completely different GCC version, Qt version, and KDE Frameworks version than Noble, so some symbols are bound to change.)
[22:36] <arraybolt3> depwait - meaning dependncies aren't there yet, right?
[22:37] <tsimonq2> Correct. ;)
[22:37] <arraybolt3> kk cool
[22:37] <arraybolt3> yeah that's why I haven't uploaded the Stage III things yet
[22:37] <tsimonq2> Right, no I get it :)
[22:37] <tsimonq2> If nothing else, we can get some testing for Backports.
[22:40] <tsimonq2> As an example of the aforementioned symbols diff:
[22:40] <tsimonq2> - (arch=!armel !riscv64)_ZTSSt23_Sp_counted_ptr_inplaceIKN2Fm12BookmarkItemESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.1.0
[22:41] <tsimonq2> +#MISSING: 1.4.0# (arch=!armel !riscv64)_ZTSSt23_Sp_counted_ptr_inplaceIKN2Fm12BookmarkItemESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.1.0
[22:41] <tsimonq2> > typeinfo name for std::_Sp_counted_ptr_inplace<Fm::BookmarkItem const, std::allocator<void>, (__gnu_cxx::_Lock_policy)2>
[22:41] <tsimonq2> + (arch=!riscv64)_ZTSSt23_Sp_counted_ptr_inplaceIN2Fm11PlacesModelESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.0
[22:41] <tsimonq2> > typeinfo name for std::_Sp_counted_ptr_inplace<Fm::PlacesModel, std::allocator<Fm::PlacesModel>, (__gnu_cxx::_Lock_policy)2>
[22:42] <tsimonq2> Let's see if this upload fares any better: https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging/+sourcepub/15378536/+listing-archive-extra
[22:42] <tsimonq2> oh wait hurr durr
[22:42] <tsimonq2> I need to remove all those MISSING lines XD
[22:42] <tsimonq2> sec, fixing in a ~ppa3
[22:42] <arraybolt3> If you'd like, pavucontrol-qt probably also won't die in depwait
[22:43] <arraybolt3> I can snag that myself in a sec though
[22:43] <tsimonq2> Already done, I think
[22:44] <tsimonq2> Kay, this one should be it: https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging/+sourcepub/15378537/+listing-archive-extra
[22:45] <tsimonq2> arraybolt3: You're more than welcome to upload anything; the archive is special compared to PPAs in that depwait packages are automatically retried when they become resolvable.
[22:45] <tsimonq2> arraybolt3: As long as you can verify with a local build that Lintian's clean and it doesn't FTBFS, I'm cool with you uploading straight to the archive + to Backports Staging.
[22:45] <arraybolt3> Oh, I didn't know that depwaits were automatically rebuilt.
[22:45] <arraybolt3> That's why I was holding off :P
[22:46] <arraybolt3> kay, I guess I'll get to explo...ER...packaging then.
[22:46] <tsimonq2> arraybolt3: Literally, all I'm doing for Backports Staging is taking the exact source I uploaded, checking out a brand new backports/jammy branch, creating a new changelog entry appending ~ppa1 to the end of the existing (NOT greater!) version number with Jammy as the codename, then uploading that and force-overriding the Backports branch.
[22:46] <tsimonq2> Hah, cool :D
[22:46] <arraybolt3> oh nice I somehow deleted libfm-qt out of my PPA 🤦
[22:47] <tsimonq2> Well, you have access to ~lubuntu-dev's PPAs now too ;)
[22:47] <arraybolt3> handy, thanks!
[22:48] <tsimonq2> As a general rule of thumb, unless we're talking emergency-level fixes, upload to Backports Staging, wait for it all to build and publish, copy it over to Backports, then *once you verify the copy is successful* you can nuke it from Backports Staging (without waiting for the publisher on Backports to finish).
[22:48] <tsimonq2> I just did that with Vim, actually :)
[22:49] <tsimonq2> With the LXQt 1.4 stack, in lieu of Britney not being set up for us org-wide, let's wait for a round of manual QA testing, and copy it over all at once.
[22:50] <arraybolt3> sounds good
[22:50] <arraybolt3> alright, got libfm-qt back where it goes in my PPA so I can continue working through the stack
[22:50] <tsimonq2> Sweet!
[22:51] <arraybolt3> And our next victim is...
[22:51] <arraybolt3> qps
[22:51] <arraybolt3> here we go
[22:51] <tsimonq2> I'll take a lap + some fresh air, so go ahead and tackle whatever you'd like. I'll sync up with you in a sec, just post status updates :)
[22:51] <tsimonq2> If both of us are on this, we should be able to crank it out fairly quickly.
[22:52] <arraybolt3> sounds good
[22:54] <arraybolt3> qps needs added to our list of "packages to make a new branch for when we start developing a new release"
[22:54] <arraybolt3> it's still on a Mantic branch
[22:54] <arraybolt3> anyways, fixing
[23:03] <arraybolt3> Days since I had to put a full copy of the CC-BY-4.0 license in a package: 0
[23:03] <arraybolt3> Seriously, this needs to be a default license in Debian.
[23:03] <arraybolt3> er, a common one I mean
[23:05] <tsimonq2> Hah yeah, I can agree with that one. I really appreciate your attention to detail when it comes to copyright.
[23:05] <tsimonq2> Let's see... I'll grab...
[23:05] <tsimonq2> qtermwidget
[23:05] <arraybolt3> also, can we add bumping build dep versions to https://phab.lubuntu.me/w/packaging/packaging_for_new_upstream_releases/?
[23:06] <arraybolt3> I don't think I can do that myself
[23:07] <tsimonq2> .
[23:08] <arraybolt3> thanks :)
[23:08] <tsimonq2> Of course :)
[23:09] <arraybolt3> oh boy, arm(64|hf) and s390x builders must be slammed
[23:09] <tsimonq2> If you upload to Noble, that gets priority over all those PPA uploads you see queued. Those will build faster.
[23:10] <tsimonq2> As for Backports, yeah it might go towards the back of the line, but I'd imagine there's some prioritization in there.
[23:10] <arraybolt3> anything that won't depwait on libfm-qt will get that advantage :)
[23:10] <tsimonq2> Right ;)
[23:10] <arraybolt3> I think qps probably will survive though
[23:10] <tsimonq2> I mean, most of them should, to be honest. At least, the leafier packages.
[23:19] <arraybolt3> qps go brrr
[23:20] <arraybolt3> hopefully should be building soon
[23:21] <tsimonq2> Good timing, qtermwidget was just uploaded as well.
[23:21] <tsimonq2> I can take screengrab?
[23:21] <arraybolt3> sure
[23:26] <tsimonq2> Packages to add on that list> screengrab too.
[23:26] <tsimonq2> arraybolt3: Do you have another one quite yet, or still chewing on what you have? :)
[23:26] <arraybolt3> Just finished the Jammy backport
[23:26] <arraybolt3> got to get the dog in and fed, brb
[23:26] <tsimonq2> I forget that I'm faster than you XD
[23:26] <tsimonq2> No worries
[23:27] <arraybolt3> I've broken things going too fast, so I try to err on the side of thoroughness :P
[23:27] <tsimonq2> No worries :P
[23:28] <arraybolt3> also I had an entire license to insert into the last package :P
[23:30] <tsimonq2> true, true
[23:34] <arraybolt3> *snatches lximage-qt
[23:34] <arraybolt3> *
[23:34] <tsimonq2> screengrab done, grabbing lxqt-about
[23:37] <arraybolt3> what in the world
[23:37] <arraybolt3> lximage-qt's copyright file has some issues :P
[23:37] <tsimonq2> ...oh?
[23:37] <arraybolt3>   8 License: GPL-2+ and LGPL-2.1+
[23:37] <arraybolt3> don't think that's a valid line :P
[23:37] <arraybolt3> or if it is it's certainly not one I've ever seen
[23:38] <tsimonq2> git blame that... is that #SimonsFault :P
[23:38] <arraybolt3> huh, though actually
[23:38] <arraybolt3> https://github.com/lxqt/lximage-qt/blob/master/AUTHORS
[23:38] <arraybolt3> so... it is accurate... but is it valid...
[23:38] <arraybolt3> idk what to even think of that, I'm guessing they were trying to summarize and didn't realize that was going to dual-license instead.
[23:39] <arraybolt3> also this gem:
[23:39] <arraybolt3> Copyright: 2013-2016 Hong Jen Yee (PCMan) <pcman.tw@gmail.com>  ?
[23:39] <tsimonq2> Lmfao, I have no idea what LXQt upstream was thinking (as usual) XD
[23:39] <arraybolt3> that question mark is probably my fault
[23:40] <arraybolt3> but... I think I'm going to rebuild this from scratch. There's too much weird here.
[23:40] <tsimonq2> I don't think the builders are really hindering us, by the way. That's cool.
[23:40] <tsimonq2> Alright. :)
[23:40] <tsimonq2> I'm sure I'll get to a big hurdle eventually, right now I'm just breezing through the last bits for lxqt-about.
[23:41] <arraybolt3> Stamp of approval or disapproval please:
[23:41] <arraybolt3>   8 Comment: Yes, that's actually what upstream chose as the license. I don't get it
[23:41] <arraybolt3>   9  either.
[23:42] <tsimonq2> If it was me, I'd just keep the first sentence XD
[23:42] <tsimonq2> Also, looks like screengrab needs patching too:   Could not find a configuration file for package "KF5WindowSystem" that is   compatible with requested version "5.101.0".
[23:42] <tsimonq2> looking
[23:43] <arraybolt3> +1 on wording
[23:43] <arraybolt3> oh are you kidding me

[23:43] <arraybolt3> someone please make up my mind
[23:43]  * arraybolt3 goes and files an upstream bug
[23:48] <tsimonq2> omfg, lol
[23:48] <tsimonq2> That's terrible.
[23:48] <tsimonq2> I commend you again for your copyright analysis skills. :P
[23:49] <tsimonq2> Kay, this should fix screengrab: https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-staging/+sourcepub/15378626/+listing-archive-extra
[23:49] <arraybolt3> woot
[23:49] <tsimonq2> I'll grab lxqt-admin next
[23:51] <arraybolt3> https://github.com/lxqt/lximage-qt/issues/645
[23:51] -ubottu:#lubuntu-devel- Issue 645 in lxqt/lximage-qt "Confusing and contradictory licensing information" [Open]
[23:53] <arraybolt3> I think I'm going to leave lximage-qt on the back burner and return to it once I get a reply, since I can't make a very useful copyright file until I know what on earth is happening here. GPL-2+ and LGPL-2.1+ is (I think?) equivalent to just GPL-2+, so until I know what's LGPL, I'm just going to add to the confusion if I finish it now.
[23:54] <tsimonq2> arraybolt3: This is kind of bad, if I was, say, an Archive Admin... but does the copyright really *change* between releases?
[23:54] <tsimonq2> arraybolt3: If it was a *regression* in copyright notices, I would say yeah, definitely hold off.
[23:54] <tsimonq2> arraybolt3: That being said, if it's shipped in a few releases, it's unfortunate, sure, but it shouldn't be a blocker for a new release.
[23:55] <tsimonq2> arraybolt3: Also, lximage-qt is a fairly small part of the LXQt stack, so if you *really* want to wait, we can. I'm going to leave the final judgement call up to you, fellow Lubuntu Developer :)
[23:56] <arraybolt3> I mean, I can probably do something with it in its current state, but assuming upstream is responsive (which they usually are), it'll be added work to regenerate the file now and then regen or tweak it again later.
[23:57] <tsimonq2> Fair enough, you could always leave it as-is for now, only doing year bumps.
[23:57] <arraybolt3> If we finish the rest of the stack and this is still left, I'll do it as-is, sound goo?
[23:57] <tsimonq2> Sounds good :)
[23:57] <arraybolt3> That's a good idea actually
[23:57] <arraybolt3> I'll just do your thing and we'll revamp later.
[23:57] <tsimonq2> Sounds good, no worries either way.
[23:58] <tsimonq2> Just don't forget to let me know what you tackle next so we don't dup work :D