If users want to unpack their password protected archives in Silverblue, they currently have to figure what application they are missing and install it as a Flatpak. That's clearly a regression from Fedora Workstation, when File Roller is preinstalled. We should add the org.gnome.FileRoller Flatpak to the list of Flatpaks that are preinstalled on Silverblue.
Proposed as a Freeze Exception for 32-final by Fedora user tpopela using the blocker tracking app because: If users want to unpack their password protected archives in Silverblue, they currently have to figure what application they are missing and install it as a Flatpak. That's clearly a regression from Fedora Workstation, when File Roller is preinstalled. We should add the org.gnome.FileRoller Flatpak to the list of Flatpaks that are preinstalled on Silverblue.
PRs to add file-roller flatpak: https://pagure.io/pungi-fedora/pull-request/825 (f32) https://pagure.io/pungi-fedora/pull-request/826 (master)
+1 FE
Can this be fixed with an ostree update post-release? Either way, I'm +1 FE in case RC 1.3 does not get sign-off.
(In reply to Stephen Gallagher from comment #5) > Can this be fixed with an ostree update post-release? No, as it's Anaconda (or some other part of the installer) that is preinstalling the Flatpaks - they are not part of the base image.
Discussed during the 2020-04-20 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException" was made as it is a noticeable issue that cannot be fixed with an update. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-04-20/f32-blocker-review.2020-04-20-16.01.txt
we've merged the PR now, next compose should include the change. (only for f32, but i'll get kevin to merge for rawhide shortly).
https://kojipkgs.fedoraproject.org/compose/32/Fedora-32-20200420.0/logs/x86_64/Silverblue/ostree_installer-3/program.log shows quite a lot of evidence of file-roller being pulled in, so I'm gonna figure this worked. Closing the bug.