It seems #Flatpak can get stuck with a corrupt installation if it's interrrupted in the middle of an update:
https://github.com/flatpak/flatpak/issues/4116#issuecomment-974883345
😩
It seems #Flatpak can get stuck with a corrupt installation if it's interrrupted in the middle of an update:
https://github.com/flatpak/flatpak/issues/4116#issuecomment-974883345
😩
This makes me wonder if #Fedora Silverblue and containers based on ostree can also get corrupted after a failed update. Wasn't ostree invented to solve this?
Perhaps #flatpak can be repaired if you know how, but so could the Windows 95 registry... and so today regular users are still forced to reinstall the OS like it's Windows 95.
@codewiz I think, even after a corrupted upgrade on Fedora Silverblue, we can boot back into the older last successful boot of Fedora over GRUB menu. Each deployment (ostree version) has their own GRUB entries, so I think we can quickly open up the previous system, and rebase the changes.
@srevinsaju Next time you update your #Fedora Silverblue install, could you please disconnect from the Internet in the middle?
I want to know if it will recover WITHOUT USER ACTION. And if it does, why couldn't #Flatpak do the same thing?
@codewiz people REALLY shouldn't be pushing Flatpak right now. the fact that the GNOME developers refuse to distribute any other way makes me scared, i'm going to stick with native repos for the forseeable future...
@smoldesu I agree, it's interesting emerging technology, but it's irresponsible to push it onto end-users when it's so fragile and incomplete.
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.