"update fail prevention" since 1.1.6.x?

asked 2015-06-09 20:36:01 +0300

mosen gravatar image

updated 2015-06-09 21:15:38 +0300

A question or observation i'd like to have confirmed regarding a new(?) feature arose from update 1.1.6. I did not find any mention in the release notes so i am looking for confirmation.

Is there sort of a new "update fail prevention" in place that checks for potential problems during the update and stops update process with "... try again later" message"?

I witnessed it myself during testing what happens if i update with phonehook still installed. The update started, did some progress and stopped showing the message, then rebooting safely.

This question seems to be caused by clamAV beeing installed, stopping the update process, then showing the same message.

I was prepared greeting the recovery-menu again (i love it) but there seems to be a build in fail protection now. Could someone elaborate on that if existant?

edit retag flag offensive close delete

Comments

1

I noticed similar (openvpn) So. Thanks :) I have now openvpn and clamav review of my builds coming up for perfection ;)

Nieldk ( 2015-06-09 20:44:23 +0300 )edit

Nice Nieldk! love your work

mosen ( 2015-06-09 21:17:48 +0300 )edit
1

the 'try again later' is not new, already occured in 1.1.2.16 - with clamav as reason ;-)
https://together.jolla.com/question/84385/11216-sailfish-os-couldnt-be-updated-try-again-later/

rudi ( 2015-06-10 01:00:56 +0300 )edit
1

At least Fedup and similar distribution upgrade tools are usually transaction based - they create a big RPM "transaction" that contains all packages to be updated. This transaction can then be used to verify if all the package can actually updated with all dependencies satisfied and without other breakage (file ownership collisions, not enough space, etc.) - all before the transaction is actually started.

This makes it possible to detect some (but not all) possible upgrade issues before the OS is actually modified, preventing stuff like a halp-applied upgrade breaking it.

So maybe the Sailfish OS upgrade tool is using something similar ?

MartinK ( 2015-06-10 01:27:30 +0300 )edit
1

I witnessed it too. OK -> Reboot and update it again make it work.

Makeclick ( 2015-06-10 07:34:22 +0300 )edit