[02:20] ^#GR&6fg7^gr36go*#RG*3tt89zzzzzzzzzzzZZZZZZZZZZZZZ OK, tachyon beam aligned, anyone here? [02:20] sup? [02:21] đŸ‘‹ Just finished up a bunch of Reddit stuff. I'm doing OK, how about you? [02:21] I'm all good. [02:21] * arraybolt3[m] checks for anything new in the Lubuntu sprint [03:00] Hey Aaron! [03:00] Sup Dan and queuebot :P [03:01] arraybolt3 @arraybolt3:matrix.org: My PM is a book, don't feel like you have to read it all tonight :P [03:05] "^#GR&6fg7^gr36go*#RG*3tt89zzzzzz..." <- * keyboard mashing intensifies * [03:18] "* keyboard mashing intensifies *" <- LOL [06:00] 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:00] Launchpad bug 1981898 in libfm-qt (Ubuntu) "package libfm-qt11 1.1.0-0ubuntu7 failed to install/upgrade: trying to overwrite '/usr/share/libfm-qt/archivers.list', which is also in package libfm-qt-common 1.1.0-0ubuntu7" [Undecided, New] [06:07] Hmm, I put libfm-qt9 as a Breaks/Replaces, maybe I had Simon call syncpackage a bit too early? [06:09] 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] thanks arraybolt3[m] ! (`libfm-qt-dev : Depends: libfm-qt11 (= 1.1.0-1) but 1.1.0-0ubuntu7 is installed` on discourse) [11:23] :) Thank you (tsimonq2, arraybolt3[m]), I see lxqt 1.1 on debian (experimental) [11:32] 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 [13:31] "Hmm, I put libfm-qt9 as a Breaks..." <- I don't think your package was done building for s390 [13:34] "likely already known, but in..." <- It will be covered in the beginning of tomorrow's Linux User Space too. https://linuxuserspace.show [14:07] "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 [14:14] "thanks arraybolt3 ! (`libfm-qt..." <- 6 hours ahead of you, it's why I manually synced -2. Needs an automatic sync now too [14:49] 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] (And in Ubuntu, why do we wait until the LTS?) [20:13] [telegram] Small bug Lubuntu Kinetic - https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1981938 [20:13] Launchpad bug 1981938 in lubuntu-default-settings (Ubuntu) "Selecting Install Lubuntu 22.10 from desktop results in error" [Undecided, New] [20:15] I know exactly where that bug lives, should be pcmanfm-qt. [20:15] arraybolt3: Sound familiar to you? Trusted executable? ^^^^^^^^^^^^^^6 [20:16] casper handles setting the flag and casper didn't change in that part of the code right? [20:44] "I know exactly where that bug..." <- Did the debian sync wipe out the patch? That is libfm-qt no? [20:44] One of the two, and maybe. [20:45] I remember adding a patch to one of them from trusted executables. [20:56] Looks like libfm-qt https://github.com/lubuntu-team/libfm-qt-packaging/blob/ubuntu/kinetic/debian/patches/fix-metadata-for-trusting-executables.patch [22:08] "arraybolt3: Sound familiar to..." <- I added that patch back into Debian, though. [22:09] so, tsimonq2, i *really* need the moderation password for lubuntu-devel [22:10] 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] JFDI [22:11] Simon Quigley (Developer): https://salsa.debian.org/ArrayBolt3/libfm-qt/-/tree/debian/experimental/debian/patches The patch is in there. [22:11] And the series file is set to apply it. [22:12] And it's also in the main LXQt repo in Salsa. [22:12] I am not sure that is the version on the iso though [22:12] Yeah, but I don't see where the patch could have ever gotten dropped in the first place. [22:15] 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] grr..... [22:16] Once that migrates we are all set [22:16] And I'm not seeing a patches directory if I download the packaging from packages.ubuntu.com. [22:16] I see it in the diff file linked above [22:17] I wonder how it got dropped. At least it will eventually carry over, but that's odd. [22:18] A. Lee dropped it in -1 and it got added back in -2 [22:18] Oh. I forget that we're dealing with multiple teams. [22:19] Right, autosync takes time too [22:19] s390 was slow last night too [22:19] It sat in proposed for a while [22:20] Britney won't sweep it through until it builds on all arches [22:22] "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. [22:27] [telegram] https://github.com/lxqt/lxqt-themes/pull/75 [22:27] Pull 75 in lxqt/lxqt-themes "Adding styling for Wing Menu in all themes" [Open] [22:28] Simon Quigley (Developer): OK, I can't find the docs, so I'm gonna go for it. [22:29] 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] 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. [22:30] [telegram] It seems to be something cosmetic. (re @lubuntu_bot: (irc) Rober: If you think the fix looks important enough we can include it, asking for input first.) [22:33] 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] 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] Simon Quigley (Developer): Did I get all that right? [22:37] [telegram] New menĂº? [22:37] [telegram] https://matterbridge.lubuntu.me/649e7c52/file_5503.jpg [22:46] [telegram] https://t.me/ldevel2019/133911 (re @Roberalz: New menĂº?) [22:51] @Roberalz: OK wait what? That looks SO COOL. [22:57] [telegram] Perfect (re @kc2bez: https://t.me/ldevel2019/133911) [22:57] [telegram] Thanks