Releases: Olf0/sfos-upgrade
v3.8.2
Changes
- Omit "-o posix", because busybox-ash does not support it.
- License change from MIT to LPGPL-2.1-only
v3.8.1
Changes
- Update list of known "stop releases" with
4.0.1.48. See also issue #48. - Change "\n" to "," in list of known "stop releases", to increase its readability and to make editing it more fail-safe.
v3.8.0
Changes
- Changed option
-hto-?(which stays equivalent to--help) - Minor enhancement of grammar in a warning, which is likely never displayed
- Issue #48 is really annoying, because Jolla has increased the frequency of SailfishOS' "stop releases" (due to their massive updates and changes of the BaseOS packages), lately (i.e., in 2019 to 2021).
Thus help / know-how is still direly needed (as already mentioned in the release notes for v3.7.8)! - Hence, add
3.4.0.24to sfos-upgrade's internal list of known "stop releases", this time.
v3.7.8
Help / know-how needed!
Unfortunately downloading the list of recent stop releases from jolla.zendesk.com is not working anymore.
For details, see issue #48 (comment) ff.
(Please contribute with your knowledge, if you can.)
Change: Thus disabling this safety measure for now!
Note, that sfos-upgrade's internal list of stop releases always has been up-to-date (and still is), hence additionally downloading and merging the recent list from jolla.zendek.com (now disabled) just constituted a fail safety measure (against the internal list becoming outdated).
v3.7.7
Changes:
- Deleting comment at (formerly) line #719, as Jolla retracted the statement which was referred to, here.
- Reestablish old free space limits, while retaining the new, three level structure (notify, warn, abort).
Rationale for the second change:
As the largest SailfishOS upgrades (Jolla's estimates: the sum of the sizes of all updated RPMs (which are installed by default), when directly upgrading from the predecessor release) have been over 600 MiB (e.g., SFOS 3.3.0 -> 3.4.0), a 1 GiB limit to notify the user, a ¾ GiB limit to warn explicitly and a ½ GiB limit to abort seem to be reasonable.
Note that the download sizes Jolla mentions in their release notes are only valid for upgrading from the direct predecessor release, but one may upgrade from one stop release to another, comprising the RPMs of multiple releases. Furthermore these estimates from Jolla only cover their own default components (RPMs), individually installed RPMs (e.g., from the Jolla Store, OpenRepos or even Jolla's SailfishOS repositories) are not and cannot be accounted for.
v3.7.6
Changes:
- Enhancing the rectified change from v3.7.4 (by v3.7.5) by a single, fail-safer formatting, to avoid such testing mishap (resulting in a "false positive") in the future.
- Better documenting what is really going on by enhancing the principal "icon comment".
No change in functionality since v3.7.3.
v3.7.5
Change:
Rectifying and enhancing incorrect comment WRT the "Icon:" tag, introduced with v3.7.4.
(No icon path, just a pure basename makes sense in the SOURCE directory, because the dirname of an icon path is always stripped by rpmbuild.)
Still no change in functionality compared to v3.7.3.
v3.7.4
v3.7.3
Changes:
- Adjust free space limits for the root file-system on non-BTRFS devices to accommodate the ever growing size of SailfishOS upgrades, "one-third reverting" commit #3c771c4
- Restructure the free space checks for non-BTRFS devices to notify earlier but provide more leeway (by a lower hard limit)