Skip to content

Commit

Permalink
Update sfos-upgrade
Browse files Browse the repository at this point in the history
  • Loading branch information
Olf0 authored Jun 15, 2019
1 parent 2d3fefc commit c4fef7b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions usr/bin/sfos-upgrade
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,7 @@ then
;;
g4)
echo "Warning: About to DOWNGRADE SailfishOS from $installed_release to ${upgrade_release}, which downgrades to a \"point release\" \"below\" the stop release $stop_release." >&2
echo "While downgrading between \"point releases\" seems to be generally feasible, doing so \"below\" a stop release bears the little extra danger of the changes making it a stop release not all being introduced with SailfishOS $(echo "$stop_release" | cut -f -3 -d '.').0 (e.g. with ${stop_release}, and thus potentially downgrading \"across\" these changes, which would break this SailfishOS installation)." >&2
echo "While downgrading between \"point releases\" seems to be generally feasible, doing so \"below\" a stop release implies the danger of the changes making it a stop release not all being introduced with SailfishOS $(echo "$stop_release" | cut -f -3 -d '.').0 (e.g. with ${stop_release}, and thus potentially downgrading \"across\" these changes, which would break this SailfishOS installation)." >&2
echo "The only absolutely safe way to achieve this is to execute a \"factory reset\", followed by UPgrading to the intended version. Although one may try downgrading and if it fails or breaks some functionality, perform a \"factory reset\" then (in the worst case at the recovery console)." >&2
echo >&2
break
Expand Down Expand Up @@ -294,7 +294,7 @@ then
;;
g4)
echo "Warning: About to DOWNGRADE SailfishOS from $installed_release to ${upgrade_release}, which downgrades to a \"point release\" \"within\" the stop release range $(echo "$stop_release" | cut -f -3 -d '.').x!" >&2
echo "While downgrading between \"point releases\" seems to be generally feasible, doing so \"below\" a stop release bears the little extra danger of the changes making it a stop release not all being introduced with SailfishOS $(echo "$stop_release" | cut -f -3 -d '.').0 (e.g. with ${installed_release}, and hence potentially downgrading \"across\" these changes, which would break this SailfishOS installation)." >&2
echo "While downgrading between \"point releases\" seems to be generally feasible, doing so \"below\" a stop release implies the danger of the changes making it a stop release not all being introduced with SailfishOS $(echo "$stop_release" | cut -f -3 -d '.').0 (e.g. with ${installed_release}, and hence potentially downgrading \"across\" these changes, which would break this SailfishOS installation)." >&2
echo "The only absolutely safe way to achieve this is to execute a \"factory reset\", followed by UPgrading to the intended version. Although one may try downgrading and if it fails or breaks some functionality, perform a \"factory reset\" then (in the worst case at the recovery console)." >&2
echo >&2
break
Expand Down

0 comments on commit c4fef7b

Please sign in to comment.