| === scoobydoob is now known as scoobydoo | ||
| lotuspsychje | you guys got some cases/tricks where you can LTS upgrade to the next release but only on the last point release, like 20.04==>22.04.5 for example? | 12:28 |
|---|---|---|
| ahasenack | that should be the case, the point release is just a tag for the iso image | 12:30 |
| ahasenack | the archive is always moving | 12:30 |
| ahasenack | and the do-release-upgrade tool will always update to the latest available packages in the archive for that release | 12:31 |
| lotuspsychje | ahasenack: im asking because i had some customer call doing an early 20.04==>22.04.1 and resulted in some bad bugs | 12:32 |
| lotuspsychje | so a last point release so it doesnt get eol would be nice | 12:33 |
| sdeziel | lotuspsychje: 22.04.1 is the latest point release currently available for 22.04 | 12:34 |
| lotuspsychje | oh | 12:34 |
| sdeziel | 22.04.2 is planned for Feb 2023 | 12:35 |
| lotuspsychje | yeah but i mean what if i only want an LTS upgrade on 22.04.2? | 12:35 |
| sdeziel | lotuspsychje: the way it works is that LTS users get proposed about LTS+1 when LTS+1 gets its first point release (.1). Users are free to wait for the second point release to be available before doing the jump | 12:37 |
| ahasenack | I don't think you can configure do-release-upgrade to filter on point releases of the target | 12:37 |
| ahasenack | it's what sdeziel said, but after .1 is released, then do-release-upgrade will do the upgrade if asked | 12:37 |
| lotuspsychje | ok tnx | 12:38 |
| lotuspsychje | i also dont wanna disable lts upgrades on my customers | 12:38 |
| lotuspsychje | so i was wondering if some trick existed | 12:39 |
| sdeziel | lotuspsychje: which bugs have they hit? | 12:43 |
| frickler | the usual "trick" would be to have a local mirror of upstream repos, then you can snapshot 22.04.1 when it is released and have consistent upgrades. aptly ftw. | 12:49 |
| lotuspsychje | sdeziel: the customer in question, was a desktop (laptop) resulted in an intel flickering bug on 5.15 and fixed from 5.17, FF snap update does not yet support belgian EID card reader, so i had to install chrome temporary and cheese is still borked on 22.04 aswell | 13:13 |
| lotuspsychje | sdeziel: so in a bit more time (point releases) those might be fixed | 13:13 |
| sdeziel | lotuspsychje: that's unfortunate.. As for alternatives for Firefox, I quite like chromium which is one `snap install chromium` away ;) | 13:17 |
| lotuspsychje | i think chromium was also a part of that bug sdeziel | 13:17 |
| sdeziel | dunno if Chromium's snap support the belgian EID card reader ... maybe it's a snap limitation/issue? | 13:17 |
| lotuspsychje | bug #1741074 | 13:17 |
| ubottu | Bug 1741074 in firefox (Ubuntu) "[snap] chrome-gnome-shell extension fails to detect native host connector" [High, In Progress] https://launchpad.net/bugs/1741074 | 13:17 |
| lotuspsychje | yeah it is | 13:18 |
| lotuspsychje | they working on it for sure | 13:18 |
| sdeziel | good, at least there is something to track | 13:18 |
| lotuspsychje | yeah its all known bugs, but not so good for my customers | 13:19 |
| lotuspsychje | bug #1958191 for the flickering | 13:20 |
| ubottu | Bug 1958191 in linux (Ubuntu) "[i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)" [High, Triaged] https://launchpad.net/bugs/1958191 | 13:20 |
| lotuspsychje | and bug #1949183 +upstream for cheese | 13:21 |
| ubottu | Bug 1949183 in cheese (Ubuntu) "Cheese screenshot white screen and video freezes" [Undecided, Confirmed] https://launchpad.net/bugs/1949183 | 13:21 |
| sdeziel | I subscribed to those likely to affect me, thanks! | 13:25 |
| lotuspsychje | np sdeziel | 13:25 |
| lotuspsychje | would be nice to have an LTS upgrade feature for extreme paranoia admins lol | 13:26 |
| kanashiro[m] | ahasenack: I have an initial version of the pcs MIR bug, could you take a look? LP #1953341 | 14:35 |
| ubottu | Launchpad bug 1953341 in pcs (Ubuntu) "[MIR] make pcs the default management tool for Corosync/Pacemaker clusters" [Undecided, New] https://launchpad.net/bugs/1953341 | 14:35 |
| ahasenack | kanashiro[m]: will do (after lunch) | 15:01 |
| kanashiro[m] | ahasenack: FWIW I am already starting to work on the MIR template for the ruby dependencies needed | 18:17 |
| ahasenack | ok | 18:17 |
| kanashiro[m] | ahasenack: ruby-open4 which is one of the dependencies seems dead upstream (no activity since 2013): https://github.com/ahoward/open4 | 19:17 |
| ahasenack | not a good mir candidate :/ | 19:18 |
| kanashiro[m] | meh, this is a good start.. | 19:19 |
| kanashiro[m] | ahasenack: do you think it is worth to write a patch to depend on something else instead of ruby-open4? | 19:58 |
| ahasenack | otp | 20:09 |
| === justache is now known as justDeez | ||
| ahasenack | kanashiro[m]: would that be simple? | 22:14 |
| ahasenack | assuming there is another popen-like ruby module out there | 22:15 |
| ahasenack | maybe file a bug with upstream, see what they think. But just "nothing new since 2014" might not be enough of a reason | 22:15 |
| sarnold | "oh good that means it's perfect" :) | 22:17 |
| sarnold | I thought ruby had popen baked into the kernel's open() function: https://apidock.com/ruby/Kernel/open | 22:18 |
| kanashiro[m] | ahasenack: I could try to move to posix-spawn or childprocess gems, and of course this would be submitted upstream | 22:18 |
| ahasenack | kanashiro[m]: maybe keep that as an option, but don't work on it yet | 22:19 |
| kanashiro[m] | I will start filling a bug as you mentioned to see what they think | 22:19 |
| ahasenack | is it used in a lot of places? | 22:19 |
| ahasenack | the code from that module, I mean | 22:19 |
| ahasenack | (just looking for a quick grep, not a deep analysis) | 22:20 |
| kanashiro[m] | Not in many places | 22:51 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!