On 3/31/22 14:38, Neal Gompa wrote:
Additionally, we're not really sure what the scope of things should be
provided in said recovery environment and what kind of things people
would expect to be able to fix in there.
The ticket mentions Boot Repair, which is the first thing that comes to
mind: https://help.ubuntu.com/community/Boot-Repair
Additionally, I think a one-click option to do some of these could be
useful repair options:
* Fix owner, permission, and capabilities: rpm --restore *
* SELinux relabel, or schedule it for the next boot (if that's the best
option available)
* Until Fedora has something like snapper to roll back the filesystem in
the event of an interrupted rpm upgrade, it'd be very nice to have a
tool that can attempt a fix. In the past I've used this:
|#!/bin/bash exec > /var/log/fix_updates 2>&1 # Remove the "new" package
so that the old package can be upgraded again. package-cleanup
--cleandupes --removenewestdupes -y # Upgrade everything that can be
safely upgraded yum update --skip-broken -y # Collect the remaining
duplicate packages for later reinstallation broken=$(package-cleanup
--dupes | xargs rpm -q --qf '%{NAME}\n' | uniq) # Remove the "old"
package, so that the new package can be reinstalled package-cleanup
--cleandupes -y test -n "$broken" && yum reinstall -y $broken # cleanup
leftover transaction yum-complete-transaction --cleanup-only|
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
