[00:03] <tsimonq2> guiverc: Hey, so for bug 1922342 I saw your note in the QA tracker. Have you tested with this machine before? (Is this a recent bug/does it show on Jammy?)
[00:03] -ubottu:#lubuntu-devel- Bug 1922342 in casper (Ubuntu Kinetic) "Impish live session takes ages to boot on BIOS systems" [High, Fix Released] https://launchpad.net/bugs/1922342
[00:04] <tsimonq2> !standuo
[00:04] <tsimonq2> !standup
[00:04] <tsimonq2> This is my one hour "last call" for any RC bugs or *anything* someone has noticed that's off. I'm all ears.
[00:04] <tsimonq2> At 1:00 UTC I'm marking us as ready.
[00:05] <guiverc> I have no concerns about us being ready; so ack to ready
[00:06] <guiverc> the 1922342 has occurred since mid-groovy cycle on a unmodified ISO; its expected... 
[00:06] <guiverc> it's not Lubuntu ISOs specific; but all flavor & Ubuntu Desktop too
[01:45] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Mantic Final] has been marked as ready
 That's just a running joke at this point
[08:16] -queuebot:#lubuntu-devel- Builds: Upgrade Lubuntu amd64 [Mantic Final] has been marked as ready
[08:17] -queuebot:#lubuntu-devel- Builds: Upgrade Lubuntu amd64 [Mantic Final] has been updated (20231009)
[08:41] <guiverc> it's getting dark outside, not much day left (for me anyway) :)
[08:45] <guiverc> most days anyway yeah ; overcast & loads of rain today locally (& I got drenched)
 Welcome Michael !
 @utkarsh2102 Hey! I'm on the road today, if you have anything for me feel free to relay it here :)
 
 Also, when we have a codename, let me know immediately please (here or PM if still embargoed) so I can do my usual debootstrap / lintian / vim / devscripts / cala uploads immediately :)
 Hello! Yes, absolutely, will do! (re @tsimonq2: @utkarsh2102 Hey! I'm on the road today, if you have anything for me feel free to relay it here :)
 
 Also, when we have a codename, let me know immediately please (here or PM if still embargoed) so I can do my usual debootstrap / lintian / vim / devscripts / cala uploads immediately :))
 Thanks! Happy Release Day!! (re @utkarsh2102: Hello! Yes, absolutely, will do!)
 You, too! ^.^ (re @tsimonq2: Thanks! Happy Release Day!!)
[13:28] <tsimonq2> Updated the release announcement.
[13:29] <tsimonq2> I see ISOs, so pushing to social media.
[14:48] <Eickmeyer> tsimonq2: You don't wait for the OK from the release team?
[14:48] <Eickmeyer> (consisting of the official release email)
[14:51] <Eickmeyer> Reason being: just because the isos are there, doesn't mean the mirrors have all synced yet.
 FYI: email server that is handling our Discourse mail and other stuff is being fubar right now for Microsoft-destined recipients (tsimonq2 and myself included) because MIcrosoft has blocked the VPS provider's networks.  I opened a high priority ticket with the provider to get them in touch with Microsoft.
 This explains our discourse email crap we've observed in the past year
 I also have the same problem :( (re @teward001: FYI: email server that is handling our Discourse mail and other stuff is being fubar right now for Microsoft-destined recipients (tsimonq2 and myself included) because MIcrosoft has blocked the VPS provider's networks.  I opened a high priority ticket with the provider to get them in touch with Microsoft.)
 remind me what your address is again (re @Roberalz: I also have the same problem :()
 because if it's yahoo or a free mail provider i can't do shit about it
 and yeah apologies about swears
 i'm grumpy
 Is a Outlook address
 that's a Microsoft destined recipient
 hotmail, msn, outlook, etc. are included in the same notice
 I know :)
 Thanks @teward001
 so are the other complainers.  However, Microsoft until *recently* just silently dropped without errors
 so that's been changed in the recent timeframe so
 I just hate email, does that count for complaining. :P
 VPS provider indicated they have zero luck getting their entire range unblocked, but have had luck with specific IPs so.
 welcome to IT Security 101 - Email Sucks (re @kc2bez: I just hate email, does that count for complaining. :P)
 Indeed.
 i'm going to be yoinking data out anyways, and replacing some mail server stuffs.
 I usually get the discourse stuff though.
 ye unless you're on a Microsoft provider (MS365 tenant, etc.) it breaks
 because blocklists.  Which hopefully we'll be able to get *these* systems i use for the SMTP off that chaos
[17:45] <tomreyn> hey, just a quick note - you probably got this on your list, though: https://manual.lubuntu.me/stable/1/1.1/retrieving_the_image.html currently points to 23.04
 tomreyn yes I am working on updating that for 23.10 right now release annoucment came kinda early in the morning for me as I am on the west coast of usa
[17:47] <tomreyn> great (the first part) :)
 @kc2bez and others: https://discourse.lubuntu.me/t/notice-known-issue-with-emails-used-for-account-sign-ups-on-this-discourse - globally pinned for now until this email issue is resolved
 Also should be done now. The checksum part means I need to know what the final version is with all changes and usually means I have to add that on release day
[21:11] <tsimonq2> Eickmeyer: I mean, yeah, you're 100% right.
[21:11] <tsimonq2> Eickmeyer: My "release day" checklist from memory is obviously outdated. :P
[21:12] <tsimonq2> Eickmeyer: Also, nice, if Ubuntu Studio gets to outline Calamares' flaws in its release announcement, I accept it as a personal challenge to respond in our next release announcement with "we did all that, and better" ;)
[21:13] <Eickmeyer> tsimonq2: Those were literal bug reports we got.
[21:13] <tsimonq2> Eickmeyer: I know, I know. Doesn't mean I won't take the bait XD
[21:14] <tsimonq2> (To be clear to any backlog readers, I consider Eickmeyer a friend and 100% know it's not a dig, I just enjoy giving him crap. ;) )
[21:14] <Eickmeyer> ^ A little too much. :P
[21:15] <Eickmeyer> XD
[21:15] <tsimonq2> I know it's going to come up again at the summit. I don't plan on budging unless the TB forces my hand.
[21:15] <tsimonq2> (Or some large event happens.)
[21:17] <Eickmeyer> BTW, utkarsh still hasn't sent out the release announcement email due to issues with the emailer, and official release "go-ahead" was given via #ubuntu-release at 9:38am my time (11:38 CDT).
[21:18] <tsimonq2> My IRC client is still set to UTC XD
[21:18] <Eickmeyer> ...
[21:18] <Eickmeyer> you get the idea.
[21:18] <tsimonq2> That's why I was oddly specific yesterday ;)
[21:18] <tsimonq2> But yeah, I get it
[21:18] <Eickmeyer> HAHAHAA (oddly specific)
[21:20] <Eickmeyer> RE: Large event: last flavor sync we were discussing moving as many away from ubiquity as possible due to the amount of technical debt in ubiquity. Nobody wants to have ubiquity in their LTS as then they'd be beholden to maintain it for that amount of time.
[21:20] <tsimonq2> I agree, and to be honest, when it comes to timing, I don't... blame you?
[21:21] <Eickmeyer> I shudder at the thought. I had to fix *two* bugs in Ubiquity and it took me hours to hunt down how and where.
[21:21] <Eickmeyer> And each one was a single line.
[21:21] <Eickmeyer> It shouldn't take hours to fix a single line.
[21:22] <tsimonq2> I mean, we have a related issue. Take a peek at our (meaning, the Qt/KDE frontend) for release upgrading. It still has KDE *4* conditionals in it.
[21:22] <Eickmeyer> Oh, you mean in ubuntu-release-upgrader?
[21:22] <tsimonq2> yeah :)
[21:23] <Eickmeyer> Well, that one isn't going away and is still supported by Foundations, so I think we can all work together there.
[21:23] <tsimonq2> So, I think Riddell originally wrote that. We just never got around to doing more than bugfixes.
[21:23] <tsimonq2> I agree.
[21:23] <tsimonq2> I don't plan on rewriting that in Lubuntu, to be clear :)
[21:23] <Eickmeyer> As we shouldn't. That's a can of worms nobody should be opening.
[21:24] <tsimonq2> (In fact, I'd like to be *more* dependent on update-notifier/release-upgrader, just its libraries, if possible.)
[21:24] <Eickmeyer> Kubuntu and Ubuntu Studio are using a version of KDE Neon's update notifier that I forked.
[21:25] <tsimonq2> Is that a standalone package? Why was I under the impression Discover handled this?
[21:25] <Eickmeyer> Discover never handled the upgrade notification, just update notifications.
[21:25] <Eickmeyer> (I should've been clear)
[21:25] <tsimonq2> Cool, so it no longer does that, at least in the Ubuntu flavors?
[21:26] <tsimonq2> (I'd be curious to see what you're working with.)
[21:26] <Eickmeyer> So, Discover handles the package update notifications, but plasma-disto-release-notifier handles the upgrade notifications for distro upgrades.
[21:28] <tsimonq2> Got it, that makes sense.
[21:28]  * tsimonq2 wonders about the UX on Lubuntu, but meh...
[21:29] <tsimonq2> Eickmeyer: So, it's just a notifier that calls the existing program, much like lubuntu-update-notifier now does, right?
[21:29] <Eickmeyer> tsimonq2: well, it's a KDE Plasmoid that calls the update-manager common backend.
[21:31] <Eickmeyer> https://launchpad.net/plasma-distro-release-notifier
[21:31] <tsimonq2> <3
[21:33] <Eickmeyer> tsimonq2: It has to get the EOL date frm the raw git output of the .json in the eol branch.
[21:33] <tsimonq2> I mean, kinda makes sense.
[21:34] <tsimonq2> Could use distro-info-tools or whatever it's called?
[21:34] <Eickmeyer> Doesn't have the EOL date.
[21:34] <tsimonq2> orly?
[21:34] <tsimonq2> base-files doesn't either?
[21:34] <Eickmeyer> Nope. 
[21:34] <tsimonq2> That seems... unintended? Or at least, not what it could be.
[21:35] <Eickmeyer> Well, I think because EOL is simply announced, and then everything is moved to old.u.c months later.
[21:35] <Eickmeyer> er, oldreleases.u.c
[21:35] <tsimonq2> Oh, well, that's another thing.
[21:36] <Eickmeyer> But yes, it would be nice if there was an exact date instead of arbitrary "9 months/3 years/5 years" from release.
[21:36] <tsimonq2> I really think *something* should be smarter to say "hey bud, looks like what 'yer running here is EOL, can we just sed sources.list, or do you want to upgrade?"
[21:36] <tsimonq2> Instead of the Many errors
[21:37] <Eickmeyer> plasma-disto-release-notifier actually says, "Your release goes EOL in x days/weeks/etc.".
[21:37] <tsimonq2> Hey dude, ubuntu.csv has EOL dates :)
[21:37] <tsimonq2> e.g. http://launchpadlibrarian.net/631684138/distro-info-data_0.54_0.56.diff.gz
[21:37] <tsimonq2> 23.04,Lunar Lobster,lunar,2022-10-20,2023-04-20,2024-01-25
[21:37] <tsimonq2> That last CSV key is it, no?
[21:38]  * Eickmeyer doesn't dare translate that into the required .json format the neon team made
[21:38] <tsimonq2> That sounds like a bet XD
[21:39] <Eickmeyer> I mean, one could curl the hell out of it.
[21:43] <tsimonq2> Eickmeyer: This would be sooooooooooooooooooooooooooooooo easy.
[21:43]  * tsimonq2 starts on patches
[21:43] <Eickmeyer> HAHAHAHAHAHA
[21:44] <Eickmeyer> Would be nice to have something where I wasn't having to actively maintain a git branch every 6 months. :)
[21:44] <tsimonq2> ;)
[21:47]  * tsimonq2 grabs a fresh ISO
[21:48] <tsimonq2> Eickmeyer: How is this called? (As in, what's the *best* way to manually call it?)
[21:48] <Eickmeyer> `/usr/share/distro-info/ubuntu.csv` :eyes: 
[21:48] <Eickmeyer> plasma-distro-release-notifier
[21:49] <tsimonq2> Cool. I'll run a quick baseline while my patch compiles.
[21:49]  * tsimonq2 is the machine 😎
[21:49] <Eickmeyer> 😂
[21:50] <Eickmeyer> Mantic EOLs on slurpee day.
[21:52] <Eickmeyer> tsimonq2: Flaw in your plan: the LTS dates don't use the 3-year date in the csv.
[21:54] <tsimonq2> Eickmeyer: Nah, that's not a flaw, that's a conditional. XD
[21:54] <Eickmeyer> Heh
[22:23] <tsimonq2> QDate("2025-06-01")
[22:23] <tsimonq2> That looks right.
[22:25] <tsimonq2> Eickmeyer: I hate this patch: 0004-set-ubuntu-version.patch ;)
[22:26] <tsimonq2> BOOOOOOOOOO uscan doesn't work :P
[22:35] <kc2bez> Time for some regex-watch-file-fu
[23:01] <tsimonq2> kc2bez: I don't envy anyone who has to modify watch files by hand without docs.
[23:01] <kc2bez> Nor do I. 
[23:37] <Eickmeyer> Yeah, there's a reason why I just said, "screw it" to the watch file with that one.
[23:38] <Eickmeyer> I mean, it's not truly forked in the sense of a fork, but if I have to I will.
[23:39] <Eickmeyer> (native packages don't need watch files, if you know what I mean)
[23:43] <Eickmeyer> tsimonq2: I hate that you hate it, but can't wait to see it so I can see it and barf at it. 🤮 😂
[23:47] <tsimonq2> Eickmeyer: How do you want your patch? :)
[23:47] <tsimonq2> Some people hate Launchpad MPs, I don't blame them.
[23:47] <tsimonq2> And to be fair, the patch will be pretty unreadable. It's better to use a non-unified diff on this one to review, I'd say.
[23:48] <tsimonq2> Anyway, I'm testing now, but it builds. Have I mentioned I hate string quoting?
[23:48] <tsimonq2> XD
[23:48] <tsimonq2> "On a platter"
[23:48] <kc2bez> Email or it doesn't count.
[23:48] <tsimonq2> ^^^^^^^^
[23:48] <Eickmeyer> Damnit, arraybolt3 took the words out of my fingers. Though, pancakes sound amazing.
[23:48] <tsimonq2> kc2bez: has the only real answer XD
[23:48] <Eickmeyer> tsimonq2: You know my email.
[23:48] <tsimonq2> Or, fax machine. No printer.
[23:48] <tsimonq2> Eickmeyer: Sweet.
[23:49]  * tsimonq2 slides Aaron and Erich some pancakes
[23:49] <kc2bez> It is the greybeard coming out. XD
[23:49] <kc2bez> \o/
[23:49] <tsimonq2> \o/
[23:50] <kc2bez> jinx
[23:50] <tsimonq2> XD
[23:50] <kc2bez> :D
[23:51] <kc2bez> Take the time you need, contribute where you can.
[23:51] <tsimonq2> Do you remember what happened recently with wxl's status? :)
[23:51] <kc2bez> Yeah, we can fast track some of that given past history I'd say.
[23:52] <tsimonq2> Prove you don't have bad amnesia, and I think we'd be happy to restore your status. ;)
[23:52] <guiverc> We'd love to have you around @arraybolt3, you've been available on request (when needed) anyway! so you'll sure not be starting again..
[23:52]  * Eickmeyer rubberstamps arraybolt3 cuz reasonz
[23:52] <tsimonq2> Yeah @arraybolt3, your work with the XDG desktop portals really saved our bacon :)
[23:52] <tsimonq2> (Ha. Ha. Ha.)
[23:53] <Eickmeyer> 🤦
[23:53] <kc2bez> Maybe prove you had temporary amnesia could work... 
[23:54] <tsimonq2> XD
[23:54] <tsimonq2> I mean, I don't judge. Everyone has something going on. My point is, if you remember how to package as well as you did, you'll be green stamped pretty easily.
[23:55] <kc2bez> +1
[23:55] <Eickmeyer> Having a hand in that mentoring, I can +1 that.
[23:56] <tsimonq2> We all do ;)
[23:56] <kc2bez> That is never ending
[23:56] <Eickmeyer> I even forgot stuff that bit me this past cycle.
[23:57] <kc2bez> Everything is iterative, just do better than last time every time and you are all set.
[23:57] <tsimonq2> It's one of those "read once, remember where to find stuff, bookmark it, use Lintian" type things
[23:57] <tsimonq2> +1
[23:58] <tsimonq2> 1% improvement is improvement ;)
[23:58] <Eickmeyer> Lintian is your friend except when it considers x.x-xubuntux.23.10 a debian nmu update and vorlon himself tells lintan to "go home, you're bitrotted."
[23:59] <tsimonq2> HAHAHAHA I was just thinking about that
[23:59] <kc2bez> On the Wayland front upstream had some comments today, let me dig it up.
[23:59] <tsimonq2> @arraybolt3: I told someone on Twitter today "whenever I'm ready for the mountain of bug reports" XD
[23:59] <tsimonq2> kc2bez: oh? :)
[23:59] <tsimonq2> Ref: https://twitter.com/GhigoTrieste/status/1712465673107243188