 Some ubuntu ISOś starting to show up..
 Lubuntu Lunar daily ISO now available to test!
 Perfect!
 Tested Lubuntu Lunar - running Qt 1.2 - new bug reported  Lenovo V14 IIL i3-1005G1,20GB,Intel UHD Graphics,WiFi Realtek 802.11ac, bluetooth 4.2, 256GB M2NVMe SSD
[18:01] <arraybolt3> \o/
[18:24] <arraybolt3> Welp, guess it's ISO-pulling time for me then!
 Nice -I updated the bug report to include all the apps that fail to open.. (re @lubuntu_bot: (irc) <arraybolt3> Welp, guess it's ISO-pulling time for me then!)
 Qterminal is one of them? (re @Leokolb: Nice -I updated the bug report to include all the apps that fail to open..)
 Yes .. (re @Roberalz: Qterminal is one of them?)
[18:34] <arraybolt3[m]> @Roberalz: According to the bug report, yes. https://bugs.launchpad.net/ubuntu/+source/lxqt-runner/+bug/1997584
[18:34] -ubot93:#lubuntu-devel- Launchpad bug 1997584 in lxqt-runner (Ubuntu) "Several apps  do not run when selected from menus" [Undecided, New]
 Ok, I have update from 22.10, but qterminal is not openinng
 Thanks for the info @Leokolb
 Yes - I tried that as well..but better to start now with new ISO for Lunar (re @Roberalz: Ok, I have update from 22.10, but qterminal is not openinng)
 Tested 3 bare metal machines - all same errors..
[18:45] <tsimonq2> Try installing qterminal from the proposed pocket 
[18:46] <tsimonq2> I'd have to check again but I think 3 packages out of the entire stack didn't migrate 
[18:47] <kc2bez[m]> qterminal is still waiting on autopkgtest
[21:02] <Roberalz[m]> Ok 
[21:19] <arraybolt3[m]> OK, while I've been hacking away at Debian, I'm gonna take a break from that today since I have a couple of things pending in that area (one of which being that I'd like Yao to either accept or reject lxqt-themes so that I know if I finally have the idea of what they want right). In the mean time, Lubuntu LXQt 1.2.0 audit, here I come!
[21:20] <tsimonq2> Pay attention to copyright, I was terrible with that :/
[21:21] <arraybolt3[m]> Heh, copyright is misery. I think I'm going to write some tools to help orchestrate licensecheck and Vim together to make it easy to update stuff. One moment, slight mess in a channel I moderate...
[21:24] <arraybolt3[m]> I'm thinking make a Python script that throws licensecheck against a file, displays what it thinks the license and copyright are, allows the user to tweak it in Vim looking at the file's original contents at the same time, then keeps track of it all and spits out a debian/copyright file at the end.
 has on lunar someone reported a bug on the themeing of the calamares installer?
[21:24] <arraybolt3[m]> @lynorian: Not that I've seen. I've not tested the installer yet though.
 Is it back to weird again? (re @lynorian: has on lunar someone reported a bug on the themeing of the calamares installer?)
[21:27] <arraybolt3[m]> It wouldn't surprise me if it was. We had a regression with the lubuntu artwork, so who knows what else regressed.
 https://matterbridge.lubuntu.me/e993df0f/file_8756.jpg
 the sidebar is black and illegable for the different steps
[21:30] <arraybolt3[m]> Yep, it regressed.
[21:31] <arraybolt3[m]> It's no longer windowed either.
[21:31] <kc2bez[m]> That was a Qt bug if I remember correctly. It also impacted the menus as well.
[21:31] <kc2bez[m]> arraybolt3[m]: How did that happen? 
[21:31] <arraybolt3[m]> Dan Simmons: In Kinetic, we fixed it by changing a config file (a couple of parameter names weren't capitalized).
[21:31] <kc2bez[m]> Oh right
[21:31] <arraybolt3[m]> (Also the too-tiny picture we fixed by changing the installer from fullscreen to windowed so it looked right.)
[21:31] <tsimonq2> My fault 
[21:32] <tsimonq2> http://launchpadlibrarian.net/630937390/calamares-settings-ubuntu_1%3A22.10.12_1%3A23.04.1.diff.gz
[21:32] <arraybolt3[m]> Ah, I see the parameters that got changed.
[21:33] <tsimonq2> I accidentally reverted the Kinetic fix in Lunar. Whooooops
[21:33] <kc2bez[m]> Ah gotcha.
[21:33] <kc2bez[m]> No worries 
[21:33] <tsimonq2> Anyone want to salvage? :P
[21:33] <arraybolt3[m]> o/
[21:34] <arraybolt3[m]> I can just push to our Git instance and then yell for someone to sponsor, right?
[21:34] <tsimonq2> Yep :)
[21:34] <kc2bez[m]> Maybe
[21:34] <kc2bez[m]> That is in LP
[21:34] <kc2bez[m]> But happy to sponsor 
[21:34] <tsimonq2> Oh, that's right 
[21:35] <arraybolt3[m]> Hmm, so maybe I need to make an MP too?
[21:35] <kc2bez[m]> Yeah
[21:35] <arraybolt3[m]> (I remember someone with powers (Eickmeyer or Simon I think) was able to Just Do It last time, but maybe they did it with an MP. Anyways, I did an MP once, so hopefully it shouldn't be too hard.)
[21:36] <tsimonq2> They're great for when you're unsure about a change or when you don't have push access yet. In this case, I'm pretty sure what the fix will look like :P
[21:36] <tsimonq2> (No pressure, Aaron ;) )
[21:37] <arraybolt3[m]> :P
[21:37] <kc2bez[m]> I mean patches are cool too
[21:37] <kc2bez[m]> Whatever works best for you 
[21:38]  * arraybolt3[m] spins up a Lunar VM
[21:38] <arraybolt3[m]> (I wish GNOME Boxes was a Qt application.)
[21:38] <arraybolt3[m]> (And that it supported bidirectional drag-n-drop that actually worked.)
[21:39] <arraybolt3[m]> (VBox's drag-n-drop doesn't work.)
[21:50] <arraybolt3[m]> Simon Quigley: Do I need to reference the original bug report again, or make a new bug report and reference it, or do I just make the changes and not worry about bug reports at all here?
[21:51] <tsimonq2> Don't worry about the bug, as long as you restore the original changelog entry :)
[21:59] <arraybolt3[m]> OK, I may be lost here, but I see all of the commits in the LP Git repository say "Imported using git-ubuntu import". So I just installed git-ubuntu, and it's description of the "import" command says "import - Update a launchpad git tree based upon the state of the Ubuntu and Debian archives". That sounds like someone sponsors the package and *then* it ends up in LP Git, not the other way around. Is that right, or am I missing
[21:59] <arraybolt3[m]> something, or am I on the entirely wrong track altogether?
[22:01] <tsimonq2> Wrong track, sec
[22:01] <tsimonq2> https://launchpad.net/~ubuntu-qt-code
[22:02] <tsimonq2> https://code.launchpad.net/~ubuntu-qt-code/+git
[22:02] <arraybolt3[m]> Oh, so that's the LP repo.
[22:02] <arraybolt3[m]> https://code.launchpad.net/~ubuntu-qt-code/+git/calamares-settings-ubuntu/+ref/ubuntu/lunar
[22:02] <tsimonq2> Yeah :)
[22:02] <arraybolt3[m]> (I went to the Ubuntu project first, then found calamares-settings-ubuntu in there :P)
[22:03]  * tsimonq2 handwaves - something something better Launchpad UX
[22:04] <arraybolt3[m]> LP is user-friendly. It's just picky about who it's friends are. Just like UNIX.
[22:04] <kc2bez[m]> Function over form or something like that 
[22:04] <arraybolt3[m]> s/is/_is_/, s/it's/its/
[22:06] <arraybolt3[m]> I think my only real gripe with it is the search feature, which seems to give you random gunk unless you shake it just right.
[22:21] <arraybolt3[m]> If no one else minds, I think now would also be a good time for me to update the calmares-settings-ubuntu packaging - there's some stuff like outdated Lintian overrides and the like that I could clean up while I'm right here.
 Sure, can't really argue with that.
[22:34] <arraybolt3[m]> Simon Quigley: Sanity check my logic here - calamares-settings-lubuntu and calamares-settings-ubuntustudio have both Breaks and Conflicts with each other. Lintian is griping about a "breaks-without-version" (the Breaks lines don't have version numbers). I get why they don't have version numbers... but the Debian Policy Manual makes it sound like Conflicts is just Breaks but stronger (Breaks won't let them both be configured at
[22:34] <arraybolt3[m]> once, Conflicts won't even let them both be unpacked at the same time). If Conflicts does everything Breaks does and more, should I just drop the Breaks lines? (Relevant Policy Manual section: https://www.debian.org/doc/debian-policy/ch-relationships.html, sections 7.3 and 7.4)
[22:36] <arraybolt3[m]> (I described Breaks wrong, actually - it won't let the breaking package to be unpacked if the package that gets broken is still configured.)
[23:01] <arraybolt3[m]> guiverc: For when you see this, remember when you were asking where the Calamares log went? I think I just figured it out looking at calamares-settings-ubuntu. Next time you're looking for that, check for /root/.cache/calamares/session.log.
[23:03] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: I think I did it that way to be overly clear that you should not have these packages co-installed under any conditions. If that's still the case when you keep the Conflicts but not the Breaks, sure, go for it 
[23:04] <arraybolt3[m]> Sounds good. By the time I'm done, the Lintian output from this is going to be sparkling clean, rather than the mess it currently is. :D
[23:14] <arraybolt3[m]> Actually, I am leaving one Lintian message (executable in /usr/lib) - we are putting a Python script in /usr/lib it looks like, and I think it probably belongs in /usr/libexec, but I don't know how to make that happen, so for now I'm just leaving it and we can look into that later.
[23:18] <tsimonq2> arraybolt3[m]: Just an entry in the install file :)
[23:18] <tsimonq2> I really need to sit down and do a full re-read of Debian Policy
[23:19] <tsimonq2> It's been quite a few years and I think I need a refresher 
[23:19] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: so as someone who has just freshly read it, in some ways you hold an advantage ;)
[23:20] <kc2bez[m]> I concur
[23:20] <kc2bez[m]> It is somewhat hard to keep up with the changes sometimes. Some things are forgotten when not used much.
[23:22] <tsimonq2> Ebbinghaus curve may put me at 60-70% with Debian Policy right now and that's recently been slightly concerning to my former sponsors :/
[23:24] <kc2bez[m]> Keep your chin up. You learned it once, you can relearn it again. 😃
 "arraybolt3 @arraybolt3:matrix...." <- Uh... I haven't read it yet. :D
[23:44] <arraybolt3[m]> (That's on the to-do list, though.)
 "Just an entry in the install..." <- Right but how is Calamares going to find the file?
[23:52]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/5097dcd771bc04b1d172eb5a26945e7632fb01a9
[23:57] <arraybolt3[m]> (Also that's an interesting override_dh_missing section - maybe this stuff would go better in the main makefile for the repo? Just me thinking about it, it probably doesn't matter either way except for findability.)
[23:57] <arraybolt3[m]>  * (Also that's an interesting override_dh_missing section - maybe this stuff would go better in the main makefile for the repo? Just me thinking about it, it probably doesn't matter unless we want to make it easier to find the part that does this.)