After problems with the previous release where third-party packages were causing upgrades to fail, we’ve added a check into the upgrade download sequence to try to ensure that no packages are going to be involved in the upgrade that can’t be verified as coming from the previous release. For a package to be involved, it must be either intended to be upgraded or uninstalled as part of the upgrade, so ordinary apps from the store should not be affected. The involved package name and version is checked against the previous release, and if it’s not found or differs in version then it will be listed in that warning.
As it’ll show packages that exist in the system but aren’t the same versions, the text might be better understood as ‘Uninstall or revert to system versions’. Even this can be misleading, as if the current SSU sailfish version has been changed and the repositories refreshed manually then installed packages will no longer correspond to the repository version and so will be flagged.
Later on we may be able to add additional metadata to verify package origins more accurately, at which point it may even be reliable enough to block the upgrade until the package state is sorted out. For now though it’ll stay as only a warning, which will hopefully help casual openrepos users avoid failing upgrades and non-booting devices.
Note: you can find the list of package reported in ~/.cache/sailfish-osupdateservice/osinfo if you want to copy/paste it