[00:27] <arraybolt3> tsimonq2: Good news, the cala-settings-ubuntu build failure doesn't appear to be the fault of cala-settings-ubuntu. It's Calamares' fault, due to a CMake file boffo
[00:27] <arraybolt3> so now to find what that boffo is
[00:30] <arraybolt3> found it
[00:32] <arraybolt3> Calamares' CMakeLists.txt includes the module FeatureSummary which includes the command set_package_properties which is used in CalamaresAddTransltions.cmake. But CalamaresConfig.cmake.in (which apparently is called when you do a find_package on Calamares, NOT Calamares' usual CMakeLists.txt) doesn't include that module, and thus the
[00:32] <arraybolt3> set_package_properties call fails in CalamaresAddTranslations.cmake making calamares-settings-ubuntu FTBFS.
[00:33] <arraybolt3> Actually then that may be our fault, perhaps *we* have to include FeatureSummary.
[00:53] <arraybolt3> tsimonq2: around? Could use some debugging help since I'm deep into the weeds with CMake weirdness.
 < 20 mins
 I'm not sure on this one tho since CMake docs don't exactly seem clear
 But I'm happy to be a rubber ducky
[00:54] <arraybolt3> kk
[00:56] <arraybolt3> the thing is that we have libkf5coreaddons-dev as a build dep in debian/control, but CMake is erroring with "The link interface of target "Calamares::calamares" contains: KF5::CoreAddons but the targets was not found."
[00:57] <arraybolt3> I suspect something significant changes in Calamares' CMake config that I don't know about, and that's what's causing this.
[00:57] <arraybolt3> actually I think that's the only thing that makes snse
[00:57] <arraybolt3> *sense
 Something changed. I know a Mantic build of the settings worked when I tried it.
[01:00] <arraybolt3> yeah and it uses alpha2
[01:00] <arraybolt3> so I'mma see what's awry
[01:40] <arraybolt3> well I fixed it sorta
[01:41] <arraybolt3> tsimonq2: I had to hack some pieces of Calamares alpha2's CMakeLists.txt file into our code but it worked. Basically I had to find_package KF5::CoreAddons myself rather than relying on Calamares to do it.
[01:41] <arraybolt3> Which feels a bit hacky...? I mean shouldn't Calamares be finding its own deps?
[01:42] <arraybolt3> I'm unsure because of https://stackoverflow.com/questions/74275590/the-link-interface-of-target-target-contains-dependency-but-the-target-was
[01:42] <arraybolt3> so this may be the right way to do things but I dunno
[01:43] <arraybolt3> `E: calamares-settings-ubuntu-common: shared-library-is-executable 0755 [usr/lib/x86_64-linux-gnu/usr/lib/x86_64-linux-gnu/calamares/modules/pkgselect/libcalamares_viewmodule_pkgselect.so]` new error?
[01:55] <arraybolt3> tsimonq2: pkgselect is your new thing right?
[01:55] <arraybolt3> the thing that allows a minimal installation mode?
[01:56] <arraybolt3> it *is*, ok ok
[01:57] <arraybolt3> tsimonq2: The pkgselect module in its current iteration breaks so many policy rules :P I fear trying to fix them all since I don't know exactly how everything works, so can I get your stamp of approval on uploading this thing Lintian mess and all and let you sort out the things you probably will be better at sorting out?
[01:58] <arraybolt3> this is my Lintian output: https://termbin.com/7ujp
[01:59] <arraybolt3> sigh, who am I kidding, I can figure this out...
[01:59] <arraybolt3> hopefully, with God's help
 LMFAO, I'm so, so sorry XD
 You don't have to make it policy compliant, God already knew it isn't :P
[02:09] <arraybolt3> lol, hey, don't stop me now!
[02:10] <arraybolt3> I already debugged why it was getting installed to /usr/lib/x86_64-linux-gnu/usr/lib/x86_64-linux/gnu/calamares/modules/pkgselect
 https://www.youtube.com/watch?v=cE1FrqheQNI
 jk lmfao
[02:10] <arraybolt3> lol
[02:11] <arraybolt3> if you really want me to not touch it I'm fine with not doing it
[02:11] <arraybolt3> but I think I have some ideas
 Knock yourself out, but once you start untangling the rules file, don't say I didn't warn you :P
 Some of those aren't too bad to fix and some of them are false positives (the noble stuff)
[02:12] <arraybolt3> already there and partially untangled :)
[02:12] <arraybolt3> kc2bez: true
[02:18]  * Eickmeyer yeets @tsimonq2 into #ubuntu-devel for a ping
 not at my IRC client so either wait 40 mins for the IRC logs to update or Telegram me the logs :P
[02:19] <Eickmeyer> Dunno if urgent or not, but it's been waiting there a while, not my ping.
 oiccc
 bandali's right?
[02:20] <Eickmeyer> Yup.
 I'll respond $later, nonurgent, thanks for the heads up
[02:21] <Eickmeyer> np
[02:24] <arraybolt3> tsimonq2: debian/rules untangled \o/
[02:25] <arraybolt3> gonna push this to the archive and to Git, I think it's in good shape. Got it Lintian-clean.
[02:25] <arraybolt3> almost
[02:25] <arraybolt3> there's a no-manual-page warning in there that I think we don't care about
[02:25] <arraybolt3> in fact I'm sure of it, so lemme add a lintian override
 Seems like an override
 Yeah
[02:32] <arraybolt3> alright fixed
[02:36] <arraybolt3> woot, perfectly lintian-clean now after a couple of overrides
[02:40] <arraybolt3> whew! Finally done.
[02:41] <arraybolt3> If this FTBFS all over the place I'm going to be a bit upset :P
[02:44] <arraybolt3> sigh, so far four out of six arches are dead
[02:44] <arraybolt3> amd64 seems to have emerged alive and riscv64 is still grinding
[02:48] <Eickmeyer> You can probably sleep on that one.
[02:48] <arraybolt3> Simon had tried to fix it and it appeared to cause amd64 to fail too but then we found out the total failure was unrelated
[02:49] <arraybolt3> cp -v common/modules/pkgselect/pkgselect.qml debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml
[02:49] <arraybolt3> 'common/modules/pkgselect/pkgselect.qml' -> 'debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml'
[02:49] <arraybolt3> cp: cannot create regular file 'debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml': No such file or directory
[02:49] <arraybolt3> is how it dies on all but amd64
[02:49] <arraybolt3> so for some reason that directory... doesn't exist? Except on amd64?
[02:50] <Eickmeyer> That points to odd build rules usually.
[02:50] <Eickmeyer> Or botched localizations.
[02:51] <arraybolt3> I can't find any arch-specific build rules
[02:53] <arraybolt3> oh wait, I think I know what's going on!
[02:54] <arraybolt3> The module is in calamares-settings-ubuntu-common but the lubuntu/branding directory is in calamares-settings-lubuntu
[02:54] <arraybolt3> ooooooookay...
[02:54] <Eickmeyer> Logs, my friend. Loooooogs.
[02:54] <arraybolt3> https://launchpadlibrarian.net/697995409/buildlog_ubuntu-noble-s390x.calamares-settings-ubuntu_1%3A24.04.4_BUILDING.txt.gz
[02:55] <Eickmeyer> Yeah, when you see that, always check your .install files.
[02:56] <Eickmeyer> override_dh_missing was the clue.
[02:56] <arraybolt3> bUt iT WOrkS on aMd64!!!!!!111
[02:56] <Eickmeyer> Yeah, because arch=all on common.
[02:56] <arraybolt3> wah
[02:57] <arraybolt3> oh
[02:57] <arraybolt3> wait, I get what you mean
[02:57] <arraybolt3> the lubuntu and ubuntustudio packages are arch: all, but the common is arch:any
[02:57] <Eickmeyer> Yeah, I had it backwards, but yes, you're right.
[02:58] <arraybolt3> so basically on all but amd64, that directory doesn't exist because... ba-dum-tiss, that package wasn't build this time
[02:58] <arraybolt3> *built
[02:58] <Eickmeyer> Yep.
[02:58] <arraybolt3> sigh.
[02:59] <arraybolt3> the file in question probably has to be under common for things to work, but common should NOT be fiddling with lubuntu's stuff even if this is lubuntu-specific for now
[02:59] <Eickmeyer> Correct.
[02:59] <Eickmeyer> Means you need to move a file between binary packages. Fun times.
[03:00] <arraybolt3> well that's not too hard, except for common probably needs that file in order to build at all
[03:00] <arraybolt3> lemme find out
[03:00] <arraybolt3> what I need is to say "if on amd64, copy this file"
[03:00] <arraybolt3> unless I can move it without setting off Sbuild War III
[03:01] <Eickmeyer> But remember, common is arch:any.
[03:01] <arraybolt3> even then that would mean having one project split across two packages
[03:01] <arraybolt3> Eickmeyer: Right, so when building on amd64, copy the file. Otherwise, don't copy the file, amd64 did that for you already.
[03:01] <Eickmeyer> So anything that *doesn't have to be compiled* can be in either package.
[03:02] <Eickmeyer> i.e. anything that isn't localized.
[03:02] <arraybolt3> ok so Simon wrote the pkgselect module as its own little mini-project and has it, all of it, under common.
[03:02] <arraybolt3> but then he copies the qml file from common to lubuntu so that Calamares can find it, as part of debian/rules.
[03:03] <Eickmeyer> I see.
[03:03] <arraybolt3> so if I move that qml file, the compiler may scream, but even if it doesn't, now the pkgselect module has bits and pieces in two different packages.
[03:03] <arraybolt3> thus, copy it but only on amd64, thus satisfying all arches
[03:03] <Eickmeyer> Except now we have an open can of worms that only Simon can sort.
[03:04] <arraybolt3> perhaps we need some way to install the QML to a distro-independent location...?
[03:04] <arraybolt3> if Cala even has such a notion
[03:05] <arraybolt3> which it may not
[03:05] <Eickmeyer> I thought common was supposed to take care of the files that were shared between the two flavors, not be complicated spaghetti.
[03:06] <arraybolt3> correct, and this QML file may be shared between multiple flavors if any new flavors pick up Calamares.
[03:06] <arraybolt3> But it has to be in a flavor-specific spot for Calamares' sake IIUC.
[03:06] <arraybolt3> (if any new flavors pick up Calamares - i.e., if you switch back to it, or if I ever make Ubuntu Trinity using TDE, which if I do, I intend on using Cala as the installer)
[03:06] <Eickmeyer> Correct, but -lubuntu should be able to just pick it up via .install and put it where it needs to be.
[03:07] <arraybolt3> the .install file copies, not moves, right?
[03:07] <Eickmeyer> Correct.
[03:07]  * arraybolt3 's brain just uncramped
[03:07] <Eickmeyer> It copies at .deb creation time.
[03:07] <arraybolt3> I thought it moved things and never thought about doing that
[03:07] <arraybolt3> And this is why I'm not a MOTU yet :P
[03:08] <Eickmeyer> It's why -lubuntu and -ubuntustudio just needed breaks/replaces against each other since they'd be installing files to the same location, essentially.
[03:09] <arraybolt3> that makes perfect sense
[03:17] <arraybolt3> alright, if this doesn't fix it, I don't know what will :)
[03:19] <arraybolt3> both arm variants have passed, so I think we're good
[03:19] <arraybolt3> Eickmeyer: Thank you for your help, I probably would not have figured out how to do this properly without you.
[03:34] <teward> wxl: arraybolt3: it's Simon's fault
[03:34] <teward> we can stop the mirror and rename it, then do a reverse mirror
[03:34] <teward> it's not trivial but can be done
[03:35] <teward> but it'll have to be a 'new repo' locally
[03:35] <teward> i know i'm hours late but i've been busy so.  *pushes Simon off the ledge again*
[04:07] <arraybolt3> teward: we unraveled that mess like an hour ago
[04:07] <teward> as i said i'm late
[04:07] <teward> i only just got time to rest so :p
[04:07] <teward> *drops a small flashbang in the chat*
[04:08] <arraybolt3> np, actually more like four hours ago :p just giving you a hard time
[04:08] <arraybolt3> I haven't even gotten to the wallpaper yet, the pkgselect module was HARD to get working right
[04:09] <arraybolt3> Out of curiosity, do I still have the needed access to kick off image builds?
[04:09] <teward> no idea
[04:10] <arraybolt3> I think I need to be part of... /me finds it
[04:10] <arraybolt3> Lubuntu Product Managers, that's it
[04:11] <arraybolt3> Not part of that team anymore though.
[04:12] <arraybolt3> I may never have been part and only gained access during my brief stint on the Council that I had to resign from.
[04:12] <arraybolt3> Can't remember now
[04:12] <teward> yeah Council kind of has god rights to everything Lubuntu
[04:13] <teward> we can talk to the other Council members and see if we want to add you to that.  i think kc2bez is the current lead (tsimonq2 is part of the Ubuntu Release Team now so I have to make sure he can properly split hats xD)
[04:13] <teward> (he knows i'm just raising heck on him for no reason xD
[04:15] <arraybolt3> It would possibly be handy, and I was trained pretty well on how to use that access before.
[13:17] <dacash> Hi. It seems i can't just add ppa:lubuntu-dev/backports in Mantic? apt complains about missing Release file and indeed there is none i can see for mantic. Is it only for LTS?
[13:27] <dacash>  https://pastebin.com/kWMxaMAG , apt-get update with allow-insecure-repos also fails at 404 not found
 /names
 dacash: (Assuming you're still on IRC) we only support 22.04 for Backports :)
 I'm really, really considering whether we should just, yk, do 23.10 Backports as well
 Eickmeyer: Thank you very much for your help :)
 arraybolt3: Very nice, great success :D
 Kay, I re-spun our ISO. This new batch of Calamares settings WILL eat your kittens, and probably your lunch, too. Proceed with caution.
[13:53] <dacash> tsimonq2 that's what i assumed. Tho it's vaguely written "supporting stable versions", Well, i am not using any nightlies )
 That being said, it's the start of all of our new installer functionality, and I tested it, it works, so ;)
 dacash: No worries. I thought I was clear in the announcement but then again, I too am human :)
 @kc2bez arraybolt3 @teward001 wxl this is about a 3-4 hour notice that I'm probably going to be publishing an announcement regarding some preliminary Backports for 23.10. I'll paste the draft link here when I have it. Let's talk about it after I get back from lunch ;)
[17:57] <arraybolt3> tsimonq2: Personally I'm -1 on a Backports for interim releases. That's a lot of extra work, plus if an LTS were only going to live for another nine months we probably wouldn't bother backporting to it.
[17:59] <arraybolt3> Interims are stable snapshots to get newer stuff before the next LTS. They're not rolling releases. The appeal of Backports for LTS is there because otherwise you use an old version of LXQt for long. But for interim, idk, I'm just not seeing a sufficient return on investment there.
[17:59] <arraybolt3> Perhaps I'm wrong though :p
 I've had no less than three media outlets and a half a dozen users ask/complain about it
 I'll highlight that in the announcement
 Usually I'm -1 as well... this one it really feels like we kinda have to
[18:10] <arraybolt3> *shrug* I mean that makes sense, I guess.
[18:13] <arraybolt3> One thing we should keep in mind though is, backporting LXQt means there's less incentive to move to the next release when it comes out.
[18:14] <arraybolt3> I.e., we're encouraging people to use their existing installs of interim releases when people need to upgrade to newer releases to stay secure.
[18:15] <arraybolt3> Not sure if we want to do that, we might see an increase in "hey why won't my system upgrade" support requests stemming from "your OS is EOL, you need to upgrade ASAP".
[18:16] <arraybolt3> For LTS we stop backporting once the new LTS is out, so there's a whole year (or three depending on how you look at it) to get tired of your LXQt and upgrade. Interim doesn't provide that advantage.
 Hi —sorry late reply —was away in Berlin past 7days just got home and yes will resume testing Lubuntu and all the other flavours.. (re @tsimonq2: @guiverc @Leokolb @Roberalz etc. I'd appreciate some testing help with Backports Staging/Backports (if you see this later) :) ^^^^)
 Thank you very much Leó! I hope all is well with you. (re @Leokolb: Hi —sorry late reply —was away in Berlin past 7days just got home and yes will resume testing Lubuntu and all the other flavours..)
 All is well ..thanks for asking! (re @tsimonq2: Thank you very much Leó! I hope all is well with you.)
 @tsimonq2 sorry missed out on some messages - what was it you needed help testing? Might be able to run a few tests tomorrow..
[20:07] <tsimonq2> https://notes.lubuntu.me/JfofmArESxmV8XwcLxV5UQ#
[20:13] <arraybolt3> tsimonq2: left a note, also I like how you got around the issue of EOL release problems.
[20:17] <tsimonq2> arraybolt3: Right, exactly. Strong message saying "upgrade or you shall perish." :P
[20:18] <arraybolt3> I have no further objections to the interim backports, and all the ones I had are dealt with, so I'm happy with it.
[20:20] <tsimonq2> Thank you.
[20:22] <arraybolt3> (I mean, it's not like I exactly get a vote since I'm not on the Council :P Thanks for taking into consideration what I was thinking too.)
[20:27] <tsimonq2> Of course :)
[20:34] <tsimonq2> https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/433283
[20:35] <tsimonq2> https://answers.launchpad.net/launchpad/+question/708471
[20:36] <tsimonq2> https://answers.launchpad.net/launchpad/+question/708471
[20:36] <tsimonq2> whoops
[20:40] <arraybolt3> Can't say no to free cloud storage :D
[20:44] <arraybolt3> Alright, so *today* I'mma try wallpaper stuff.
[20:45] <arraybolt3> tsimonq2: I know you were trolling with the retro wallpaper idea... but what if I used one of them for the placeholder SDDM screen?
[20:46] <arraybolt3> I could add a watermark like "Lubuntu Noble - DEVELOPMENT EDITION" somewhere to make it obvious it's a placeholder and also to act as a warning for those brave souls that choose to use Noble now other than our testers.
[20:54] <tsimonq2> Sure, heh. As long as it looks pretty under a variety of resolutions, lol.
[20:56] <arraybolt3> https://i.imgur.com/D4W366u.png
[20:56] <arraybolt3> that might even look good as a wallpaper
[20:56] <arraybolt3> aspect ratio wasn't as much as a problem as I expected
[20:57] <arraybolt3> also the numbat picture: https://i.imgur.com/oCQlcSp.jpg
[21:28]  * arraybolt3 really wishes QEMU supported drag-n-drop files without needing SPICE
[21:42] <tsimonq2> https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-mantic-staging/+packages
[21:42] <tsimonq2> Just playing a game of chicken with the publisher.
[21:42] <tsimonq2> Don't worry, I have a local, hacky retry script. :P
[21:43] <tsimonq2> I would imagine it'll be another couple long publish runs before we fully release this thing.
[21:43] <tsimonq2> I'll just do a smoke test... but that's about it, lol.
[21:43] <tsimonq2> Also, I just uploaded some extra themes to both the PPAs that will be installed (but not enabled) by default. Like 300 kb. I think that's doable. :P
[21:56] <arraybolt3> tsimonq2: any idea what the copyright info is on that old wallpaper I linked earlier?
[21:56] <tsimonq2> arraybolt3: *shrug*
[21:57]  * arraybolt3 rummages through Phab to find it
[21:58] <arraybolt3> oh wow, we have a data loss situation in Phab
[21:58] <arraybolt3> something awry with AWS looks like
[21:58] <arraybolt3> teward: !needhelp
[21:59] <tsimonq2> arraybolt3: Email him for an instant response, at his personal email :P
[21:59] <arraybolt3> not that urgent, just something's Not Right
[21:59] <tsimonq2> arraybolt3: With big bold letters "THE NUKES HAVE BEEN UNLEASHED"
[21:59] <tsimonq2> XD
[21:59] <arraybolt3> tsimonq2: where did you pull that wallpaper from at first?
[21:59] <teward> #InvalidSummons
[21:59] <arraybolt3> teward: ohai
[21:59] <arraybolt3> DM incoming
[22:00] <teward> you owe me coffee if yer gonna be summoning meout of the blue :P
[22:01] <arraybolt3> don't we always ping you when infra throws a fit? :P
[22:02]  * tsimonq2 throws rocks at teward 
[22:04] <tsimonq2> teward, Eickmeyer, RikMills: also FYI in case you fail to read logs, default PPA size is now 8 GB
[22:04] <arraybolt3> anyway, PSA: All file access within repos on Phab is entirely b0rked. Every repo, every file, that I try to access, gives an esoteric AWS-related error.
[22:04] <tsimonq2> \o\ /o/ \o/
[22:05] <arraybolt3> So for now, I have no clue what license or copyright one of these files is under :P gonna have to dig through oldreleases to find it and hope the copyright file is valid
[22:05] <tsimonq2> I'm 75% sure it's Rafael Laguna but wxl would know.
[22:12] <tsimonq2> https://9to5linux.com/lxqt-1-4-desktop-arrives-for-lubuntu-23-10-users-heres-how-to-install-it
[22:12] <tsimonq2> This current build cycle has the vast majority of packages, which also means the longest publisher run.
[22:13] <tsimonq2> As soon as it's all published in Backports Staging, I'll be smoke testing it, then shipping it right out the door.
[22:14] <arraybolt3> tsimonq2: see Matrix DM when you get a chance
[22:30] <arraybolt3> welp, I found the 10.04 package for lubuntu-artwork, and it has the (almost) right wallpaper... BUT... the copyright file is malformed so I'm not sure who owns that wallpaper's copyright still :P Looks like Rafael Laguna is most likely though.
[22:35]  * arraybolt3 has the joy of importing a CC-BY-3.0 license into a package :-/
[22:39] <arraybolt3> Aaaaaand... I imported BY-SA-3.0 rather than BY-3.0 XD
 Nice job XD
 Use sed/awk/regex
 :P
[22:42] <arraybolt3> just finished using Vim
[22:43] <arraybolt3> Those CC licenses are LOGN
[22:43] <arraybolt3> *LONG
[22:50] <arraybolt3> sigh, looking through Lubuntu's Wikipedia I miss LXDE.
[22:51] <wxl> why????
 ^^^^^^
 XD
[22:51] <arraybolt3> wxl: Fancy 3d-looking buttons :P
[22:51] <arraybolt3> and a less "flat" UI
 (phab is down while i shove it in a sandbox)
 (and will stay down even in the sandbox env)
[22:52] <arraybolt3> I get that flat user interfaces are the present and probably the future but I miss the 3d Everything world we had for a bit there.
[22:52] <wxl> arraybolt3: that's no reason to miss lxde. 
[22:52] <wxl> but
[22:52] <wxl> if you really want 3d looking buttons, make yourself a theme
[22:53] <arraybolt3> I guess I could make one that looks suspiciously LXDE-like :P
[22:53] <arraybolt3> I loved its overall look and feel too
[22:53] <wxl> sounds like you care enough about looks that maybe you should be our new art lead XD
[22:53] <arraybolt3> lol, I thought that was you right now
 I already threatened wxl with it, he threatened me with making Fritz the QA lead so I backed down XD
[22:55] <arraybolt3> oh yikes :P
[22:55] <wxl> my problem is i don't care enough to be the art lead
 *reassigns tsimonq2 to the salt mines for reasons*
[22:56] <wxl> that and i have zero graphic design skills
[22:56] <wxl> which is more than the negative skills simon has but you get the idea
[22:56] <arraybolt3> 🤣
[22:57] <teward> i have 2.56% artistic skills xD
[22:57] <teward> so i mean i'm not a good fit either
[22:57] <teward> but mleh
[22:57] <teward> *sips coffee*
[22:57] <wxl> 2.56 > 0, sooooooo
[22:57] <teward> 2.56 < 50% competency which is bare minimum so
 How far in the negative am I? XD
[22:58] <arraybolt3> I'm decent with some things (especially Gimp fractals and basic Inkscape stuff), but my mom is breathtakingly good with a lot of stuff.
[22:58] <teward> tsimonq2: -500000000000%
[22:58] <teward> which is why i sent you to the salt mines
[22:58] <teward> go fix the autodrills
[22:58] <arraybolt3> She made the Kinetic and Lunar wallpapers, I'm probably going to talk her into making the Noble one too
[22:58] <teward> they run on Ubuntu 8.04 and COBOL
 XD : https://matterbridge.lubuntu.me/9bab9806/file_10122.jpg
[22:58] <arraybolt3> (I got to make the Lunar SDDM screen though :D)
 file image.png too big to download (2373886 > allowed size: 1000000)
 Can't see it pastebin it
[22:58] <teward> #TooLarge
[22:59] <wxl> oh whatever
 No I wanna see it pastebin it XD
[22:59] <wxl> it's on matrix go look there
[22:59] <arraybolt3> wxl: what is it, MacNCheeseBook?
[22:59] <arraybolt3> (I can see it and have no idea what to even name that)
[22:59] <wxl> https://i5.walmartimages.com/asr/4342f3f0-5f24-432a-8e41-9b7ebc51fe96_1.9596121f40a561f932002ba9554fc001.jpeg
 HAHAHAHAHAHA
 OMGGG
[23:00] <arraybolt3> (in reply to Simon's squiggly bird)
[23:01] <wxl> note he didn't say anything like "no i wouldn't be that bad"
 No I think I'd be worse tbh XD
[23:02] <wxl> hahahahaha
[23:02] <arraybolt3> Uploading new wallpaper and SDDM screen packaging to the archive
 Do ittt
[23:03] <arraybolt3> also lubuntu-artwork packaging is a hot mess right now, BUT I didn't leave it in any worse shape than it started, I think.
[23:03] <arraybolt3> I'll do a packaging cleanup on it hopefully soon.
[23:04] <arraybolt3> PSA: if you upgrade and your SDDM screen and wallpaper are solid black, I botched a symlink, feel free to force me to brew your virtual coffee for the remainder of next week.
[23:04] <arraybolt3> (I think I got the symlinks right though.)
[23:04] <arraybolt3> (I looked at the existing ones with ls -l and remade them the same way.)
[23:04]  * genii twitches
 LGTM, ship it. (re @tsimonq2: XD)
 TBF it is better than mine. At least you can make out that it is a bird. XD
 LMFAO
[23:16] <teward> genii: go get me a coffee
[23:17] <teward> :P
[23:17]  * genii breaks out the Aeropress and Death Wish coffee for teward
[23:17] <teward> thank you kindly *takes the caffeine*
[23:20] <arraybolt3> I actually wanted to do a UI refresh with the Lunar cycle, and I want to get Breeze out of Lubuntu *this* cycle because it's caused us issues before.
[23:20] <arraybolt3> So I might try some theming overhauls and see what y'all think.
[23:21] <arraybolt3> For now though, tell https://launchpad.net/ubuntu/+source/lubuntu-artwork/24.04.1 to hurry up and build so you can install it and tell me what you think :P
[23:21] <tsimonq2> Let us know what you find!
[23:25] <arraybolt3> I'm brave, so I just did an encrypted XFS installation of Lubuntu XD
[23:35] <arraybolt3> QTerminal is still broken :(
[23:36] <arraybolt3> sigh, I have unfortunate word placement
[23:36] <arraybolt3> https://i.imgur.com/BJaN7VK.png
[23:36] <arraybolt3> shoulda put it at the upper-right
[23:37] <arraybolt3> oh well, version numbers are cheap, yadda yadda
[23:37] <arraybolt3> I really should have tested before uploading it though
[23:39] <tsimonq2> Just manually install the package from proposed... :P
[23:39]  * tsimonq2 dinner