While adding || : or || true to every shell statement outside of if, elif, while and other conditional statements prevents a shell invoked with the option -e to stop executing a shell-script when a statement has an exit status not equal to 0, the scriptlets (i.e. %pre*, %post*, %trigger* and %file*) scripts in an RPM spec-file are not executed in a shell invoked with the option -e (in contrast to the scripts in the “body” of an RPM spec-file, i.e. %prep, %build and %install).
The only condition the scriptlets must fulfil in order to not accidentally abort an RPM file’s installation, update or removal, is to exit with a status of 0. Consequently concluding RPM spec-file scriptlets with an exit 0 statement (or any other statement which is guaranteed to return 0) is fully sufficient.
What about Sailfish OS updates for the Turing Phone? I know that it never really went into at-scale, but there are still a couple of phones around. Would it still receive a OS 4.6 update or it’s stuck at whichever version it is?
Guess I´m lucky.
I have a XA2 Sauna with Android App Support.
GPS works fine with (Jolla)SFOS/OSM Scout (with offline maps).
But also with Android/GPS-test (download via F-droid).
I just had a similar experience. Tried an OTA update of 4.6.0.13 , chickened out after “call recorder” incompatibility massage. Later, against better judgment, I started updating, and after some time, the status bar slowly came to an end and got a message saying how updater was unable to update and offered me a restart. After restart I got the standard boot manager GUI to enter a pin, but after it successfully passed it twice fleshed the white screen with the message “No apps running”, Now after every power up it acts the same. Does anyone have some solution to not destroy all of the data on it.
I tried to update my Intex Aquafish (transformed to JollaC) and got a huge list of packages that should be uninstalled, similar to those screenshots. It does not look good. Anyone updated a jollified Aquafish successfully?