[Suggestion] Consider removing SSU's caches before / after upgrading

[Olf0]

DESCRIPTION

Consider performing
rm -r /var/cache/ssu/
ssu ur

But when? Likely both, before and after updating (on SFOS < 4.4.0), because users may start on any affected release and end on one, but never use sfos-upgrade before or after that, again.

ADDITIONAL INFORMATION

• Original issue & resolution: https://forum.sailfishos.org/t/4-3-0-12-jolla-camera-also-torch-does-not-start-at-all-as-well-as-videos-do-not-play/9000/36
• Permanent solution: sailfishos/ssu@5bd8a09 which should be released with SFOS 4.4.0.
  Edit: Yes, it did, see lines 2532 to 2540 of Changelog_from_4.3.0.15_to_4.4.0.58.md:
  • Updated : 1.0.14.1-1.6.1.jolla -- 1.0.19-1.8.1.jolla
  • [...]
  • [ssu] Make sure the ssu cache is up-to-date.

[Olf0]

See also https://docs.sailfishos.org/Support/Help_Articles/Updating_Sailfish_OS/#if-it-keeps-failing

pkill  store-client
rm -rf /home/.pk-zypp-dist-upgrade-cache/*
rm ~/.cache/sailfish-osupdateservice/os-info

Better, also applicable to SailfishOS < 2.2.1 and suitable for root:

pkill -x store-client
rm -rf /home/.pk-zypp-dist-upgrade-cache/*
primuser="$(loginctl list-sessions | fgrep seat0 | tr -s ' ' | cut -d ' ' -f 4)"
rm -f "/home/${primuser}/.cache/sailfish-osupdateservice/os-info" "/home/${primuser}/.cache/store-client/os-info"

For references, see post_sfos-upgrade.

[Olf0]

The original idea should rather be implemented as (see ssu commit 5bd8a09):

killall -q ssud 2> /dev/null || { sleep 1; killall -KILL -q ssud 2> /dev/null; } || true
# or `pkill -x ssud 2> /dev/null || { sleep 1; pkill -KILL -x ssud 2> /dev/null; } || true`

rm -rf /var/cache/ssu/*
ssu updaterepos

One may make this dependent on installed_version >= 4.4.0, but this does nor rally make a difference.