Obikawa:
I have a suspicion, that there is a whole class of bugs being triggered here, where a deep dependency like the GNU lib C, for example, has silently held back a previous upgrade, and now breaks on the next cycle.
jovirkku:
The warning about incompatible packages when starting an OS update may be a false one, unfortunately. System packages (e.g. qt5, kf5) should not be removed. The warning should be ignored in that case.
This problem is caused by this very bug that Jolla for years has been neglecting to fix.
ssu re is set to the new release version as soon as an OS update starts downloading. If the user then does not apply the downloaded update right away but quits the GUI updater, the device is left with the incorrect release version, which is the source of all those issues. Starting the update at some later time causes this very problem, i.e. request to remove lots of system packages.
See e.g.
When the update is being downloaded, all the repositiories get switched to 4.4.0.58. Interrupting the download of the update leaves the system in such a state…
It happened to me too when I interrupted downloading the 4.4 update. I realized it when I then tried to download the ofono package from 4.3.0.15 (to replace my patched version that the update was complaining about) and it downloaded it from 4.4.0.58 repo instead, which broke telephony.
I fixed it as follows:
devel-su
ssu re 4.3.0.15 …
While @wetab73 correctly denoted …
… this may also happen at any other time, when a new SailfishOS release is available, see:
To avoid any mishaps (by mistyping or mis-guessing the truly installed SailfishOS release) one may use (as described in the bug report) to bring the SailfishOS installation into a consistent state again:
devel-su
ssu re "$(grep -F VERSION_ID /etc/os-release | cut -s -f 2 -d "=")"
rm -f /var/cache/ssu/features.ini
ssu ur
Then either run post_sfos-upgrade (if sfos-up…
1 Like