At least my OpenRepos repository hosting sfos-upgrade
says so, so I assume I am really me.
I consider altering the limits to notice@1G, warn@800M and exit@600M.
But I still wonder a bit why 750M free was not sufficient for you.
If understand correctly, that was because you had the update downloaded by Jolla’s graphical updater, cancelled it and then immediately started sfos-upgrade
without rebooting in between, right?
Or maybe for people like me who apparently ignores it use CAPITAL letters
No, I will not shout at people for no wrongdoing.
Well funny thing is: I didn’t reboot the phone but later I checked and Settings/About product reported that 4.4.0.64 was installed.
See SFOS version 4.4.0.58 without upgrade - #22 by olf
I then rebooted and everything still works fine even though the error message during install really looked like something was missing? But there’s 600MB free system space now so it cleaned up on reboot
Run sfos-upgrade --verify
to ensure that an upgrade is completely installed.
I’m not used to pkcon or zypper, but is there a command to run to apply any updates that got interrupted without downloading new updates?
I do not know: If you want to know, read Jolla’s version
script and trace back further, IIRC to ssu
, which is Free Software hosted at GitHub, so you can read its code to see what it does.