lubot[matrix] <arraybolt3> If someone doesn't mind doing a quick checkup, I added instructions for doing SRU verification for https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2002255 on Kinetic. However, since SDDM doesn't trigger the bug on Kinetic, the config-file-conflict feature can't be tested without bringing a PPA into the picture, if that would even work (and I have no good idea on how to make it work). So basically I have the00:07
-ubot93:#lubuntu-devel- Launchpad bug 2002255 in lubuntu-update-notifier (Ubuntu Jammy) "lubuntu-update-notifier provides no good way to resolve a forcibly terminated system update" [Critical, Fix Committed]00:07
lubot[matrix] <arraybolt3> Simon Quigley, Dan Simmons , Eickmeyer: ^00:07
lubot[matrix] <arraybolt3> (Purposefully not pinging te_ward since he doesn't seem to like that much)00:08
lubot[matrix] <arraybolt3> The line in question is:00:10
lubot[matrix] <arraybolt3> ```00:10
lubot[matrix] <arraybolt3> For the configuration conflict prompt handling feature:00:10
lubot[matrix] <arraybolt3> 00:10
lubot[matrix] <arraybolt3> 1. Download a Lubuntu 22.04.1 ISO, and install it into a VM.00:10
lubot[matrix] <arraybolt3> (Note that Lubuntu Kinetic does not yet have an update for it00:10
lubot[matrix] <arraybolt3> that causes lubuntu-update-notifier to hang, which makes it00:10
lubot[matrix] <arraybolt3> difficult to do this test on Kinetic. Testing the conflict prompt00:10
lubot[matrix] <arraybolt3> feature on Kinetic should not be needed if things work properly00:10
lubot[matrix] <arraybolt3> on Jammy.)00:10
lubot[matrix] <arraybolt3> ```00:10
lubot[matrix] <eickmeyer> I'm of two minds. First of all is that it could be **any** config file causing the issue, SDDM is just a good test case. The one in -proposed is just nearly guaranteed to make it happen if SDDM has already been installed.00:12
lubot[matrix] <kc2bez> Some of your testing needs to focus on not introducing a reversion too meaning the functionality you already have isn't lost.00:13
lubot[matrix] <eickmeyer> A recent grub upload I think already caused this issue to be in the wild on Jammy.00:13
lubot[matrix] <arraybolt3> Right? What's weird is that, on Kinetic, it doesn't trigger the prompt. I have no idea why, which is why I'm doubting whether I could even make a proper test case in a PPA. And the file is indeed replaced, but it's done automatically.00:14
lubot[matrix] <arraybolt3> Hmm, that's a good point, though I don't think that can be done unless someone keeps their VMs from previous testing around to do more updates later. I suppose the 7-day verification period will give us plenty of time for that though.00:15
lubot[matrix] <arraybolt3> I'll keep my VMs around just for that.00:15
lubot[matrix] <eickmeyer> That means the file hasn't been modified in any way since it was initially installed.00:15
lubot[matrix] <arraybolt3> Then why does it trigger it on Jammy?00:15
lubot[matrix] <eickmeyer> My assumption would be a bug in apt, but idk.00:16
lubot[matrix] <kc2bez> What happens when you run the same scenario in the terminal?00:16
lubot[matrix] <arraybolt3> On Jammy, I get the prompt. In Kinetic, not sure yet, but I'm installing a new VM right now.00:17
lubot[matrix] <kc2bez> If you don't get the prompt in the terminal you won't get it in the GUI.00:18
lubot[matrix] <arraybolt3> True. Unless something's changed in aptd, I assume the reason the GUI isn't doing anything is because the prompt doesn't show up in the terminal. Even the old, buggy updater can handle the SDDM update just fine in Kinetic.00:18
lubot[matrix] <arraybolt3> But we're about to find out.00:19
lubot[matrix] <arraybolt3> Relevant part of a Kinetic update from -proposed:00:35
lubot[matrix] <arraybolt3> ```00:35
lubot[matrix] <arraybolt3> Setting up sddm (0.19.0-3ubuntu1.1) ...00:35
lubot[matrix] <arraybolt3> Installing new version of config file /usr/share/sddm/scripts/Xsetup ...00:35
lubot[matrix] <arraybolt3> Setting up libgbm1:amd64 (22.2.5-0ubuntu0.1) ...00:35
lubot[matrix] <arraybolt3> ```00:35
lubot[matrix] <arraybolt3> So no, I don't get the prompt in Kinetic.00:35
lubot[matrix] <kc2bez> Weird but I think that is still a good sign for lubuntu-update-notifier00:37
lubot[matrix] <kc2bez> It does indicate we need a different way to test it I guess.00:38
arraybolt3I wonder what happens if I modify the file first and then try it...00:38
lubot[matrix] <eickmeyer> That means there's no issue in Kinetic, meaning I can unblock for Kinetic. \o/00:38
lubot[matrix] <kc2bez> I would think testing that small piece from a PPA should be acceptable.00:39
lubot[matrix] <kc2bez> Agreed @Eickmeyer00:39
lubot[matrix] <arraybolt3> Gah, Launchpad is so frustrating sometimes :P00:44
lubot[matrix] <eickmeyer> You get used to it. I did. And if I can, anybody can.00:45
lubot[matrix] <kc2bez> It is a bit of a Swiss army knife so the blade isn't always the sharpest. It is much better than some of the alternatives though.00:46
arraybolt3Makes sense. I'm sure I will get used to it, and to some degree I have.00:47
lubot[matrix] <arraybolt3> So my thinking right now is to make a PPA that ships a modified version of... something (maybe SDDM?) that changes a config file again. The idea is the user can modify the config file first, then run the update, and that should trigger the prompt. Sound good?00:50
lubot[matrix] <kc2bez> Makes sense to me.00:59
arraybolt3K, will do that.00:59
lubot_[matrix] <arraybolt3> Well, I just thoroughly embarrassed myself. There's no need for a PPA package or anything to verify the SRU in Kinetic. Just open up /usr/share/sddm/scripts/Xsetup in Vim, type some random junk into one of the comments, save it, and then do the upgrade.18:21
lubot_[matrix] <arraybolt3> Reproduces the prompt like a charm.18:21
lubot_[matrix] <arraybolt3> I did it immediately before running the full upgrade.18:21
lubot_[matrix] <arraybolt3> So I'm now doing verification on Kinetic.18:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!