Post AETIr39O4ydgtaFu0u by gabek@mastodon.social
(DIR) More posts by gabek@mastodon.social
(DIR) Post #AETIr39O4ydgtaFu0u by gabek@mastodon.social
2021-12-16T18:50:53Z
0 likes, 0 repeats
Wasn't able to complete the Pop_OS update. When I searched the web for the error I got to an issue @aral filed over a year ago. This is my sign to deal with it some other day.
(DIR) Post #AETIr3YYZOlw9e20FE by aral@mastodon.ar.al
2021-12-16T18:53:28Z
0 likes, 0 repeats
@gabek Oh, crap, that’s not a good bug to hit. Can’t believe it’s still an issue… if I remember correctly it’s because of upstream renaming their repo URLs or something.
(DIR) Post #AETIr43khPj3iOcurw by captain_morgan@mastodon.social
2021-12-16T19:01:13Z
0 likes, 0 repeats
@aral @gabek got a URL? Not super thrilled with PopOS of late anyhow, a major bug might push me to finally ditch it on my laptop (assuming I can still get System76 firmware updates without)
(DIR) Post #AETIr4WoxKyhAYE8B6 by gabek@mastodon.social
2021-12-16T19:10:22Z
0 likes, 0 repeats
@captain_morgan @aral I searched for "pop-upgrade: calling ReleaseUpgradeFinalize method failed" and found https://github.com/pop-os/upgrade/issues/81
(DIR) Post #AETIr4uZX1ycMDL6CO by captain_morgan@mastodon.social
2021-12-16T19:12:50Z
0 likes, 0 repeats
@gabek @aral uuuuugh, yeah I've hit similar to that an old Ubuntu server. Pain.ful. I think I'm just over Ubuntu based distros.
(DIR) Post #AETIr5J245Xha4mdKC by aral@mastodon.ar.al
2021-12-16T19:15:12Z
0 likes, 0 repeats
@captain_morgan @gabek Yeah, I have no idea how they still haven’t handled that. It basically means that if you miss the deadline to upgrade, you’re majorly screwed.
(DIR) Post #AETIr5iCYVfwq8YjYW by captain_morgan@mastodon.social
2021-12-16T19:17:29Z
0 likes, 0 repeats
@aral @gabek or spend a week or two manually upgrading, downgrading, install, purge, reinstall to the magic combo that gets you there.
(DIR) Post #AETIr65x8Cfs1nfhZo by aral@mastodon.ar.al
2021-12-16T19:18:41Z
0 likes, 0 repeats
@captain_morgan @gabek Sounds like my experience entirely.
(DIR) Post #AETIr6VTbJ5hIxc5MO by captain_morgan@mastodon.social
2021-12-16T19:20:31Z
0 likes, 0 repeats
@aral @gabek My condolences for the lost time you'll never get back.
(DIR) Post #AETIr6vM35n6bDikhE by aral@mastodon.ar.al
2021-12-16T19:35:46Z
0 likes, 0 repeats
@captain_morgan @gabek I believe this is one of the reasons why the Pop!_OS folks are considering moving to rolling releases: https://twitter.com/jeremy_soller/status/1417464682164547586
(DIR) Post #AETIr7HKjNN7hO0IxE by captain_morgan@mastodon.social
2021-12-16T19:36:47Z
0 likes, 0 repeats
@aral @gabek Would support! Also love the idea they're building a Rust based Window Manager/Desktop
(DIR) Post #AETIrXEOEwSyBmpJya by inference@pleroma.inferencium.net
2021-12-16T19:50:00.020336Z
0 likes, 0 repeats
@captain_morgan @aral @gabek Not sure if related, but rolling releases are the only way to do security properly, because backporting security fixes is very difficult when stable/LTS releases rely on old, incompatible software which cannot easily be fixed. Newer software, code, libraries, and even just the fact that fixes are implemented into the newer versions by default, make rolling releases best for security.
(DIR) Post #AETIxpUVGN5QYhMhEm by inference@pleroma.inferencium.net
2021-12-16T19:51:16.834143Z
0 likes, 0 repeats
@captain_morgan @aral @gabek Security maintenance is infeasible when it comes to distros such as Debian stable, and this is admitted by the Debian team; they simply cannot keep up with security backports.
(DIR) Post #AETJC2JIOkb2N3tga8 by inference@pleroma.inferencium.net
2021-12-16T19:53:50.621928Z
0 likes, 0 repeats
@aral @captain_morgan @gabek An example of this in action is the recent Chromium issue on Debian. The version of Chromium was extremely vulnerable to MANY severe security issues, which were even being exploited in the wild, and Debian couldn't keep up. Even the newest version of Chromium on Debian (93) is very out-of-date; the newest version is 96, with 97 coming soon.