 @tsimonq2 shit SHOULD be coming back up Soon(tm)
 ohhhhhhh yeah? That's good news :D (re @teward001: @tsimonq2 shit SHOULD be coming back up Soon(tm))
 What shit? XD (re @teward001: @tsimonq2 shit SHOULD be coming back up Soon(tm))
 !language XD
 XD
 i'm allowed to use that word right now once.
 because i've been on the phone with OVH for over two hours to get them to process payment and reactivate
 *grumble grumble grumble*
 ended up redirected like 200 times
 before I finally said "Listen, if you don't put me in touch with a supervisor or such, I WILL be happy to call my lawyers next" and they went "whoops"
 and yes occasional use of foul language as part of accident is literally that, accident
 the fact i had to call them out for *lawyers* to get them to take the money was a "WTF" moment
 Okay so things should be coming back now.
 *checks things*
[01:39] <teward> and it looks like the bridge is back
[01:39] <teward>  yay!
[01:40] <arraybolt3> woohoo!
 🎉
[13:03] <guiverc> arraybolt3, just fyi... but i noticed a lubuntu looking logo on panel... clicked & lubuntu-update showed upgrades available... i clicked to uppdate & was asked for password; they installed & looks good.   (I've still yet to logout or reboot; but operation looks great)
 🎉 :)
 Hi. I have a question about the development process. Let's say I want to make a change to the installer-prompt or a daemon. How can I actually test it to make sure it works? I've never really worked on anything other than games, CLIs and desktop apps.
 Great question! Have you ever worked with CMake before? (re @Nani72Noni: Hi. I have a question about the development process. Let's say I want to make a change to the installer-prompt or a daemon. How can I actually test it to make sure it works? I've never really worked on anything other than games, CLIs and desktop apps.)
 Yep :)
 I've memorized this command, but I can also explain it if you find it confusing: mkdir build && cd build && cmake .. && make
 With this one specifically, you'll want to do a sudo make install as well
 Then you can simply run lubuntu-installer-prompt to test
 Make sure to clean up these installed files when you're done :)
 That makes sense. Thanks a lot. 👍
 Of course :) let me know how I can help
 I'm having trouble booting up the Lubuntu on my PC. I use a Ventoy USB and I can boot up any other distro (including Lubuntu 23.10) just fine. It works in a VM. I could use some help... Thanks :0
[15:59] <arraybolt3> Nani72Noni: Try flashing the ISO to a USB drive directly. Usually I use `dd` (carefully - it can overwrite important data if you make a typo) or balenaEtcher.
 Will do. Thanks
[16:01] <arraybolt3> If that doesn't work, take a screenshot of whatever error messages you get (or a picture of your screen since you probably won't have Print Screen working yet), or describe the behavior. "Doesn't boot" can mean a lot of things.
 I added the errors to the message
 Unfortunately our current IRC bot doesn't support edits passing through (re @Nani72Noni: I added the errors to the message)
 I'll do a little trick that'll be present on the IRC side but not here
 Forwarded from Nani72Noni: I'm having trouble booting up today's ISO on my PC. I use a Ventoy USB and I can boot up any other distro (including Lubuntu 23.10) just fine. It works in a VM. I could use some help... Thanks :0
 EDIT: It fails like this:
 error: invalid magic number.
 error: you need to load the kernel first.
 And done :)
 ok. Here's error:
 error: invalid magic number.
 error: you need to load the kernel first.
 
 I'm flashing the ISO to the USB directly to see what happens.
 It worked with etcher! Thanks.
 I subscribed lubuntu-packaging to https://launchpad.net/bugs/1838372 which will be a Wayland blocker next cycle. It's on Foundations' radar so no action needed from us right now
[16:20] -ubottu:#lubuntu-devel- Launchpad bug 1838372 in apport (Ubuntu) "'ubuntu-bug -w' doesn't work under wayland" [Wishlist, Triaged]
[16:45] <arraybolt3> Just packaged a new obconf-qt and am now building in in preparation for uploading it.
[16:45] <arraybolt3> (trying to crunch in some Lubuntu work before my Matrix meeting and day job kick in)
 Nice!!! Thank you :)
[16:56] <arraybolt3> And uploaded to Git and the archive.
[16:57] <arraybolt3> Had a slight panic with losing network connectivity in the VM due to a problematic NetworkManager file, but anyways, got it sorted :)
[17:00] <arraybolt3> (if anyone knows what on earth the real purpose of /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is, please tell me, that file causes Lots of Issues for me in manually-built VMs.)
 I noticed that the Lubuntu logo in the grub menu, installer prompt (everywhere) is a fixed size png and looked pretty pixelated on my screen. (The one with the text and bird). Is there a reason as to why we don’t use an svg, since Qt can render those, right?
 I'm glad you asked, essentially we keep the SVGs semiprivate for Ongoing Reasons. We could certainly use SVGs in the installer prompt (doesn't it use an SVG already? curious) but Plymouth may be a different story
 I wouldn't spend too much time looking into Plymouth this cycle, if I'm being frank. It's on my list for next cycle to make sure that's up to date in the archive, for now we're always dealing with an old copy.
[20:57] <arraybolt3> Well Calamares is being interesting :)
[20:57] <arraybolt3> one of the patches I had to drop wasn't mentioned in the changelog at all :P
[20:58] <arraybolt3> anway, let's see if this builds now
[21:05] <tsimonq2> #BlameSimon XD
[21:12] <arraybolt3> no in the *upstream* changelog silly :P
[21:13] <tsimonq2> teward is tossing around infra, may be intermittent for the next few hours while he gets it situated.
[21:13] <arraybolt3> kk
[21:33] <arraybolt3> new Calamares uploaded.
 fyi infra is likely to blip entirely in the next 24 hours.  Doing some nice high-grade migrations between the OVH nodes to cut us back on costs AND get us faster response times
 and i say *everything* will blip multiple times because it's not just migrating machines, it's migrating the IPs over.  Because it has to be routed to the new machine from the old machine.  So yes things will be asploding over the next couple days
[22:08] <tsimonq2> Working on calamares-settings-ubuntu and updates to match the deb822 specification.
[22:41] <tsimonq2> https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-default/29333/13
[22:42] <tsimonq2> Kay, going to be hectic for the next few hours.
[22:45] <tsimonq2> @Roberalz: https://git.lubuntu.me/Lubuntu/installer-prompt/pulls/4 merged, thank you!!!!
 Galician on the way (re @lubuntu_bot: (irc) <tsimonq2> @Roberalz: https://git.lubuntu.me/Lubuntu/installer-prompt/pulls/4 merged, thank you!!!!)
[22:59] -ubottu:#lubuntu-devel- Pull 4 in Lubuntu/installer-prompt "updated Basque translation" [Merged]
 :)
[23:52] <RikMills> arraybolt3: /me looks at what patches you dropped from calamares
[23:53] <RikMills> ok, mine was in the changelog
[23:55] <RikMills> the one from simon ddi not do a explicit 'add d/p/this-patch' entry, but did give the bug ref
[23:56] <RikMills> *simon did
[23:57] <RikMills> maybe it should have, but when there is a fix like that I always go and look to see if it a packaging change or a patch
[23:58] <RikMills> as clearly you did :D