[00:11] <tsimonq2> https://twitter.com/DavidL_Greene/status/1549556448950194177
[00:11] <tsimonq2> What do we need to improve in nm-tray?
[00:34]  * Eickmeyer[m] might have to fork the lubuntu grub theme to replace the now-outdated ubuntustudio grub theme
[02:32] <lubot> [telegram] <teward001> a lot.  :P (re @lubuntu_bot: (irc) <tsimonq2> What do we need to improve in nm-tray?)
=== guiverc2 is now known as guiverc
[09:31] <arraybolt3[m]> OK, doing the last little bit of preliminary testing and prepping the SRU paperwork for Calamares. I'll be running it by y'all before applying it to the bug report. Si
[09:31] <arraybolt3[m]> Simon Quigley (Developer) Eickmeyer ^
[10:15] <arraybolt3[m]> Simon Quigley (Developer): Is there any way to make an SRU that fixes two bugs in one blow? Once I'm done with Calamares, I want to tackle calamares-settings-ubuntu since it's harboring two Jammy bugs - one with LibreOffice localization and one with BTRFS installation. It would be awfully convenient to SRU it too so that our Calamares testing can also simultaneously test those two fixes, and then we can get everything fixed in
[10:15] <arraybolt3[m]> 22.04.1, but I don't see where the SRU process makes room for fixing two bugs with one update.
[11:19] <arraybolt3[m]> Simon Quigley (Developer) Eickmeyer https://paste.ubuntu.com/p/3GzN2wGkFv/ SRU paperwork draft, lmk what you think
[11:36] <arraybolt3[m]>  * OK, doing the last little bit of preliminary testing and prepping the SRU paperwork for Calamares. I'll be running it by y'all before applying it to the bug report.
[13:04] -queuebot:#lubuntu-devel- New source: lubuntu-installer-prompt (kinetic-proposed/primary) [0.2.0-0ubuntu1]
[14:55] <Eickmeyer[m]> arraybolt3: So, the other bug report regarding the LibreOffice localization would have to be converted into an SRU per the procedure and then the changelog in the cala upload would have to reference it as well.
[17:49] <arraybolt3[m]> Eickmeyer: Well, true, but I'm talking about both the BTRFS install bug and the LibreOffice localization bug - they both affect calamares-settings-ubuntu but are different bugs - how would one get both of them SRU'd at the same time?
[17:49] <arraybolt3[m]> (So we'd be talking about three SRUs at once.)
[17:52] <Eickmeyer[m]> The changelog for calamares-settings-ubuntu could point to the different SRU bugs. Example:
[17:52] <Eickmeyer[m]> * Fix for btrfs installation bug (LP: #123456)
[17:52] <Eickmeyer[m]> * Fix for Libreoffice localization bug  (LP: #789123)
[17:52] <ubot93> Launchpad bug 123456 in xine-lib (Ubuntu) "podcast crashes amarok" [Undecided, Fix Released] https://launchpad.net/bugs/123456
[17:52] <ubot93> Launchpad bug 789123 in overlay-scrollbar (Ubuntu) "Eclipse crashes/quits without any error messages" [Medium, Confirmed] https://launchpad.net/bugs/789123
[17:52] <Eickmeyer[m]> shuddup ubot93
[17:52] <arraybolt3[m]> LOL
[17:52] <arraybolt3[m]> OK, that makes sense.
[17:53] <arraybolt3[m]> (Of course, having that many SRUs at once might be a danger - if any one failed all of them would potentially be toast.)
[17:54] <arraybolt3[m]> (So we might need to just let LibreOffice slide - if there's any one of the three that would be likely to cause problems, that's the one I would think would have the highest likelyhood of blowing up.)
[19:04] <Eickmeyer[m]> I'd say that one might be a little late for 22.04.1. Right now, Cala is the absolute highest priority.
[19:17] <arraybolt3[m]> Eickmeyer: True. I think we should get in the BTRFS installation bug fix, though - that bug went in the release notes.
[19:20] <Eickmeyer[m]> I don't have a problem with that one per se, but I have watched BTRFS literally destroy an SSD, so I don't care about that one as much.
[19:20] <arraybolt3[m]> Yikes, destroy, like physically?
[19:21]  * arraybolt3[m] was thinking of switching to BTRFS :(
[21:25] <Eickmeyer[m]> Yeah, the darn thing fried.
[21:26] <arraybolt3[m]> Good grief. How...??? Everything I know of computers would make me think that would be impossible unless it resulted in constant write access to the drive, but weird things happen I guess.
[21:29] <arraybolt3[m]> Eickmeyer: So, here's a question for you. Where on earth does the SRU'd package end up when it's up for review? The Wiki doesn't make it obvious (or I'm missing something). Is it just the debdiff, but people with archive upload privileges also use dput and not just the debdiff?
[21:29] <Eickmeyer[m]> arraybolt3: It goes into the Unapproved queue.
[21:30] <arraybolt3[m]> Right, but I mean, the instructions in the paperwork I'm writing say "Install the package from this SRU" as part of the Test Plan section, and I'm thinking, "But wait... how do they get the package in the first place?"
[21:30] <arraybolt3[m]> Like, if it's a debdiff, do they put it in the unapproved queue?
[21:30] <Eickmeyer[m]> It's a dput, and launchpad automatically generates the debdiff. However, creating a debdiff is a little more complicated.
[21:30] <Eickmeyer[m]> I mean, manually.
[21:31] <arraybolt3[m]> Thus why I provide the packaging to someone else who can do the dput, I guess.
[21:31] <arraybolt3[m]> At any rate, the Calamares SRU and paperwork is finished and up for review, and the calamares-settings-ubuntu SRU and paperwork is finished, but I've not yet put it up for review.
[21:31] <Eickmeyer[m]> One of my predecessors had this nice writeup that might give you a clue: https://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioPackageMaintenance#Making_Changes_to_a_Package
[21:31] <arraybolt3[m]> (I only just fixed the BTRFS install bug in the second SRU.)
[21:32] <Eickmeyer[m]> <arraybolt3[m]> "Good grief. How...??? Everything..." <- But yes. Because of CoW, it writes more frequently, and some SSDs just don't like that.
[21:33] <arraybolt3[m]> Oh great.
[21:33] <arraybolt3[m]> My SSD should hopefully be OK since it has 800 TBW of life on it, but I'll keep that in mind for weaker SSDs.
[21:33] <arraybolt3[m]> (Er, it had 800 TBW when I bought it, it's been used pretty heavily and has less than that now.)