[02:20] <arraybolt3[m]> ^#GR&6fg7^gr36go*#RG*3tt89zzzzzzzzzzzZZZZZZZZZZZZZ<modulate on> OK, tachyon beam aligned, anyone here?
[02:20] <kc2bez[m]> sup?
[02:21] <arraybolt3[m]> 👋 Just finished up a bunch of Reddit stuff. I'm doing OK, how about you?
[02:21] <kc2bez[m]> I'm all good. 
[02:21]  * arraybolt3[m] checks for anything new in the Lubuntu sprint
[03:00] <tsimonq2> Hey Aaron!
[03:00] <tsimonq2> Sup Dan and queuebot :P
[03:01] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: My PM is a book, don't feel like you have to read it all tonight :P
 "^#GR&6fg7^gr36go*#RG*3tt89zzzzzz..." <- * keyboard mashing intensifies *
 "* keyboard mashing intensifies *" <- LOL
[06:00] <arraybolt3[m]> Looks like something went awry in the world of LXQt updates. https://bugs.launchpad.net/ubuntu/+source/libfm-qt/+bug/1981898 I'm guessing this is probably my fault, we probably need a Breaks/Replaces section in the libfm-qt11 Control file I would guess.
[06:07] <arraybolt3[m]> Hmm, I put libfm-qt9 as a Breaks/Replaces, maybe I had Simon call syncpackage a bit too early?
[06:09] <arraybolt3[m]> Simon Quigley (Developer): Whenever you get the time, can you syncpackage libfm-qt again? I think I must have had you do it before it was actually fully built, since the package in Ubuntu doesn't conflict with libfm-qt9, even though the new code does.
[06:12]  * arraybolt3[m] adds "Make sure the package is actually built before asking for syncpackage" to the list of things to do in the future
[06:27] <guiverc> thanks arraybolt3[m] !  (`libfm-qt-dev : Depends: libfm-qt11 (= 1.1.0-1) but 1.1.0-0ubuntu7 is installed` on discourse)
[11:23] <guiverc> :)   Thank you (tsimonq2, arraybolt3[m]), I see lxqt 1.1 on debian (experimental)
[11:32] <guiverc> likely already known, but in case..  "Lubuntu's  New Backports PPA" was covered in this week in linux (206); https://www.youtube.com/watch?v=S19PhKupl4M  tsimonq2 
 "Hmm, I put libfm-qt9 as a Breaks..." <- I don't think your package was done building for s390 
 "likely already known, but in..." <- It will be covered in the beginning of tomorrow's Linux User Space too. https://linuxuserspace.show 
 "I don't think your package was..." <- It is built for all arches now but is still in proposed. https://launchpad.net/ubuntu/+source/libfm-qt/1.1.0-2~1
 "thanks arraybolt3 !  (`libfm-qt..." <- 6 hours ahead of you, it's why I manually synced -2. Needs an automatic sync now too
[14:49] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: That package Breaks/Replaces needs to be updated to include libfm-qt8 in there, to be dropped on the next Debian release. Fun thing for you to explore, why is it suddenly good after a release?
[14:50] <tsimonq2> (And in Ubuntu, why do we wait until the LTS?)
 Small bug Lubuntu Kinetic - https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1981938
[20:15] <tsimonq2> I know exactly where that bug lives, should be pcmanfm-qt.
[20:15] <tsimonq2> arraybolt3: Sound familiar to you? Trusted executable? ^^^^^^^^^^^^^^6
[20:16] <tsimonq2> casper handles setting the flag and casper didn't change in that part of the code right? 
 "I know exactly where that bug..." <- Did the debian sync wipe out the patch? That is libfm-qt no? 
[20:44] <tsimonq2> One of the two, and maybe.
[20:45] <kc2bez[m]> I remember adding a patch to one of them from trusted executables.
[20:56] <kc2bez[m]> Looks like libfm-qt https://github.com/lubuntu-team/libfm-qt-packaging/blob/ubuntu/kinetic/debian/patches/fix-metadata-for-trusting-executables.patch
 "arraybolt3: Sound familiar to..." <- I added that patch back into Debian, though.
[22:09] <teward> so, tsimonq2, i *really* need the moderation password for lubuntu-devel
[22:10] <teward> if you don't know it and wxl is unreachable, then I may have to go stab Mark to get him to assert "I own everything" power for lists.u.c and give me power
[22:10] <tsimonq2> JFDI
[22:11] <arraybolt3[m]> Simon Quigley (Developer): https://salsa.debian.org/ArrayBolt3/libfm-qt/-/tree/debian/experimental/debian/patches The patch is in there.
[22:11] <arraybolt3[m]> And the series file is set to apply it.
[22:12] <arraybolt3[m]> And it's also in the main LXQt repo in Salsa.
[22:12] <kc2bez[m]> I am not sure that is the version on the iso though 
[22:12] <arraybolt3[m]> Yeah, but I don't see where the patch could have ever gotten dropped in the first place.
[22:15] <kc2bez[m]> It was dropped and you added it back http://launchpadlibrarian.net/613311606/libfm-qt_1.1.0-1_1.1.0-2~1.diff.gz
[22:15] <arraybolt3[m]> grr.....
[22:16] <kc2bez[m]> Once that migrates we are all set
[22:16] <arraybolt3[m]> And I'm not seeing a patches directory if I download the packaging from packages.ubuntu.com.
[22:16] <kc2bez[m]> I see it in the diff file linked above
[22:17] <arraybolt3[m]> I wonder how it got dropped. At least it will eventually carry over, but that's odd.
[22:18] <kc2bez[m]> A. Lee dropped it in -1 and it got added back in -2
[22:18] <arraybolt3[m]> Oh. I forget that we're dealing with multiple teams.
[22:19] <kc2bez[m]> Right, autosync takes time too
[22:19] <kc2bez[m]> s390 was slow last night too
[22:19] <kc2bez[m]> It sat in proposed for a while 
[22:20] <kc2bez[m]> Britney won't sweep it through until it builds on all arches 
 "arraybolt3 @arraybolt3:matrix...." <- Simon Quigley (Developer): Is there a place in the documentation for me to look that up, or should I just use logic? Because I think I can see the logic exactly already.
 https://github.com/lxqt/lxqt-themes/pull/75
[22:28] <arraybolt3[m]> Simon Quigley (Developer): OK, I can't find the docs, so I'm gonna go for it.
[22:29] <arraybolt3[m]> libfm-qt8 exists in Debian.. If libfm-qt11 does not break/replace libfm-qt8, it will cause update problems if a package (like pcmanfm-qt) depends on libfm-qt11 and is upgraded.
[22:30] <arraybolt3[m]> Once a new Debian release is made that no longer contains libfm-qt8 in its archive, then we can drop the package breaks/replaces for libfm-qt8 because there's no need to break/replace a package that doesn't exist anymore.
 It seems to be something cosmetic. (re @lubuntu_bot: (irc) <tsimonq2> Rober: If you think the fix looks important enough we can include it, asking for input first.)
[22:33] <arraybolt3[m]> In Ubuntu, users can upgrade either straight from one LTS to another, or from LTS to standard release, meaning we need to be prepared for a user to be coming from one of two different upgrade paths, so for maximum safety, we need to have breaks/replaces against everything in between two LTS releases.
[22:34] <arraybolt3[m]> That way, no matter what package versions or sonames are involved once upgrade time rolls around, there won't be a random conflict somewhere deep in the guts of the system.
[22:35] <arraybolt3[m]> Simon Quigley (Developer): Did I get all that right?
 New menú?
 https://matterbridge.lubuntu.me/649e7c52/file_5503.jpg
 https://t.me/ldevel2019/133911 (re @Roberalz: New menú?)
[22:51] <arraybolt3[m]> @Roberalz: OK wait what? That looks SO COOL.
 Perfect (re @kc2bez: https://t.me/ldevel2019/133911)
 Thanks