[1.1.2.16] Sailfish OS couldn't be updated. Try again later

Question

4

[1.1.2.16] Sailfish OS couldn't be updated. Try again later

asked 2015-03-02 18:15:42 +0300

objectifnul

9370 ●150 ●203 ●224

updated 2015-03-02 20:58:20 +0300

(My English translation from French).

Trying to update from Vaarainjärvi to Yliaavanlampi. Update downloaded apparently successfully, then while installing update, an error message appears: "Sailfish OS couldn't be updated, try again later. Device will now reboot".

Battery full, charger connected. Available phone memory > 5 Gb. Nightly browser uninstalled before OS update, stock browser reinstalled instead (pkcon install sailfish-browser). Tried with patches activated or inactivated (but not uninstalled; perhaps I should but not sure it's worth the candle).

EDIT:

Deleted /home/nemo/.cache/store-client/os-info.
killed store-client.

Issue not solved.

Any explanation? Why am I asked to try again later? Is it likely to work better tomorrow?

Comments

I guess that the phone that something was wrong. I think it is necessary to make data storage and make a full reset.

Victorious ( 2015-03-02 19:34:33 +0300 )

Try again tomorrow and check if you still have this error.

ced117 ( 2015-03-02 19:41:56 +0300 )

If you are running developer mode on the device. Check your journal. You'll probably find that some package can't be installed (most likely due to some dependency installed from openrepos?)

xfade ( 2015-03-02 19:43:56 +0300 )

@xfade Do you mean system.journal in /run/log/journal/<my folder> ? To me it's completely cryptic.

Are there some apps that are likely to have compatibility issues with 1.1.2.16 but not with Vaarainjärvi ?

objectifnul ( 2015-03-02 20:20:07 +0300 )

add a comment

I guess that the phone that something was wrong. I think it is necessary to make data storage and make a full reset.
Victorious ( 2015-03-02 19:34:33 +0300 )
Try again tomorrow and check if you still have this error.
ced117 ( 2015-03-02 19:41:56 +0300 )
If you are running developer mode on the device. Check your journal. You'll probably find that some package can't be installed (most likely due to some dependency installed from openrepos?)
xfade ( 2015-03-02 19:43:56 +0300 )
@xfade Do you mean system.journal in /run/log/journal/<my folder> ? To me it's completely cryptic.
Are there some apps that are likely to have compatibility issues with 1.1.2.16 but not with Vaarainjärvi ?
objectifnul ( 2015-03-02 20:20:07 +0300 )

Answer 1

2

answered 2015-03-03 02:30:27 +0300

Dromi
151 ●2 ●3 ●7

I had the same issue '/var/log/zypp/history' gave me

# 2015-03-02 20:15:08 droid-system-sbj-0.4.3-10.24.1.jolla.armv7hl.rpm install failed
# rpm output:
# error: unpacking of archive failed on file /system/lib/libandroidfw.so: cpio: rename failed - No space left on device
# error: droid-system-sbj-0.4.3-10.24.1.jolla.armv7hl: install failed

I tried (in su-devel)

pkcon update droid-system-sbj

Update was successful, so I continued with every other packages, starting with connman related packages to get the network back

pkcon get-updates  # gives the list of packages we can update, even offline
pkcon update <package[s]> # without package name, packagekit tried to connect to the network...

At some point, pkcon started to fail, I had to reboot the phone. Once rebooted, network was back (wifi AND cellular). I unfortunately couldn't update the last packages with an automatic method (pkcon update/store/sailfish update) so I had to update all of them by hand. Trick: once the network is back, you can connect on ssh, copy/paste on a computer is a bit more comfortable than the terminal on the phone !

I hope this will work also for you !

link

Comments

1

There was some kind of miracle, I don't know how to explain it:

I noticed clamav was corrupted (update or uninstall both failed).
I performed pkcon update without package name. It took about 20 minutes but eventually succeeded (thank you Dromi).
I rebooted.
I performed rpm -e --noscripts clamav to get rid of it (don't know if I succeeded or failed: no confirmation, no error).

After reboot, the device is now running Yliaavanlampi without having installed it again. Maybe previous attempts were partially successful.

Will now review the configuration carefully.

objectifnul ( 2015-03-03 09:57:19 +0300 )

add a comment

Answer 2

1

answered 2015-03-02 21:25:00 +0300

rudi
1483 ●10 ●24 ●41

updated 2015-03-02 22:32:24 +0300

like
https://together.jolla.com/question/82037/release-notes-upgrade-112-yliaavanlampi/?answer=82157#post-id-82157 ?
maybe it's another app, causing rpm-problems (but in my case, it was clamav)

link

Comments

I guess indeed that 'some' app or apps might be the source of the problem. As I don't really want to uninstall 100+ apps one by one just to check, I'm looking for primary suspects first :)

objectifnul ( 2015-03-02 21:37:54 +0300 )

so, you don't have clamav installed?

rudi ( 2015-03-02 21:39:01 +0300 )

No I don't. Currently uninstalling all patches, just to check. Stay tuned.

objectifnul ( 2015-03-02 22:40:14 +0300 )

All patches plus patchmanager uninstalled, then rebooted. Re-deleted /home/nemo/.cache/store-client/os-info, re-killed store-client. Same problem.

objectifnul ( 2015-03-02 23:29:48 +0300 )

maybe you'll find some errors in '/var/log/zypp/history', that will give you a hint

rudi ( 2015-03-03 00:25:01 +0300 )

see more comments

[1.1.2.16] Sailfish OS couldn't be updated. Try again later

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

[1.1.2.16] Sailfish OS couldn't be updated. Try again later

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions