Updating tablet 4.4.0.68->4.4.0.72 fails

[attah]

So i tried to do the last little update on my tablet and see if i could understand anything about the positioning issues. Basic stuff like checking versions etc…

But the update would not show up in the GUI, so i went to the terminal…
The regular song and dance ensued, but it keeps failing half way through:

Error: Subprocess failed. Error: RPM failed: warning: /var/cache/pk-zypp-cache/packages/adaptation0/i486/droid-bin-tbj-0.0.18-1.2.5.jolla.i486.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY

I have tried clearing the cache and force installing that specific package as well… but nothing seems to let the update complete.
I’m afraid to turn it off now…

Any ideas?

[attah]

Hmm, perhaps it is a bit of a false error message.
These seemingly unrelated issues have it:

Cpio fails to install in SDK

REPRODUCIBILITY (% or how often): hard to say, quite frequent BUILD ID = OS VERSION (Settings > About product): 4.0.1 Tested on Platform SDK DESCRIPTION: When trying to install cpio (gnu version) to be able to package boot image, I frequently (but not always, as far as I remember from earlier times), get sb2 -t SailfishOS-4.0.1.48-aarch64.h8324 -R zypper in --force-resolution -y --allow-vendor-change --allow-unsigned-rpm cpio Loading repository data... Reading installed packages... Resolving…

Not enough space using sfos-upgrade. Where are packages stored?

I started upgrade to 4.4.0.64 by downloading via the Settings app, but decided to continue using sfos-upgrade to be able to follow it. I tried to updating using sfos-upgrade 4.4.0.64 which started fine but ended up in need of just 60MB more space. It seems the Settings app and sfos-upgrade uses different download paths? As Settings app stores the download somewhere(?) and the script stores it somewhere else(?) both are filing up space and I’m now left with just 287.5M free space on the root p…

I guess i could be out of space somehow…

[nephros]

There is a chance that the actual error message is in /var/log/zypp/history.

Does that file say anything useful?

[Seven.of.nine]

@attah

Any ideas?

Typo…? Does 4.4.0.75 exist (for devs)?

[poetaster]

@attah

I guess i could be out of space somehow…

Uhm, really stupid question but what did

du -hsc

tell you? the last time I had the cpio errors it really was a user partition full problem …

[attah]

Yes, a typo. Well spotted.
(Not one i repeated in the process itself fortunately)

[attah]

Hmm, that says 281MB… but the gui says 682MB. Weird.

[olf]

BTW, the log file created by Jolla’s GUI updater’s last run is at: /var/log/systemupdate.log

[olf]

@attah

Hmm, that says 281MB… but the gui says 682MB. Weird.

I wonder if it is worth reiterating that I did not write sfos-upgrade out of altruism, but because years ago I frequently ran into issues (too little space on root-volume → upgrade fails half-way, low battery → hectically searching for a charger while an upgrade was running, etc.) when manually upgrading SailfishOS at the command line. Ultimately sfos-upgrade does the same (ssu re <release> && version --dup), but with tons of safety checks prepended and typos at the command line having no practical impact.

[johanh]

So I didn’t dare the update directly to 4.5.x, but tried 4.4.0.68 → 4.4.0.72 first.

Exactly the same issue here (RPM failed etc.). When I tried to install the failing rpm manually, it said that disk space was too low and it required at least 78 MB of disk space. Now, there were some 300 MB free in / from what I could see. But the root partition is way too small, so I booted the tablet into rescue mode and after some LVM resizing there is now a root disk with a size of 4.7 GB.

Now I’ll try the update to 4.5.0.19.