| Summary: | [Flatpak SDK][GLIB] Try ostree fsck command when the flatpak update fails | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Lauro Moura <lmoura> |
| Component: | Tools / Tests | Assignee: | Philippe Normand <philn> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply, pgriffis, philn, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Lauro Moura
2021-01-26 05:54:14 PST
Maybe `flatpak repair` would be better. I dunno what is the difference. Yes `flatpak repair` does `ostree fsck` plus a bit of extra work on top: According to the code: * Try to repair a flatpak directory: * + Delete any mirror refs which may be leaking disk space * (https://github.com/flatpak/flatpak/issues/3222) * + Scan all locally available refs * + remove ref that don't correspond to a deployed ref * + Verify the commits they point to and all object they reference: * + Remove any invalid objects * + Note any missing objects * + Any refs that had invalid object, or non-partial refs that had missing objects are removed * + prune (depth=0) all object not references by a ref, which gets rid of any possibly invalid non-scanned objects * * Remove leftover .removed contents * + Enumerate all deployed refs: * + if they are not in the repo (or is partial for a non-subdir deploy), re-install them (pull + deploy) Pull request: https://github.com/WebKit/WebKit/pull/4987 Committed 255142@main (7e710036103c): <https://commits.webkit.org/255142@main> Reviewed commits have been landed. Closing PR #4987 and removing active labels. |