Update to 2.2.1.18 on Jolla J 1 Failed

Question

1

Update to 2.2.1.18 on Jolla J 1 Failed

asked 2018-09-10 18:31:17 +0200

simc
71 ●3 ●7 ●9

updated 2018-09-11 10:35:54 +0200

jiit

2678 ●32 ●58 ●59

admin

I've tried to update my J1 to Sailfish 2.2.1.18 but, the first time I've tried, something failed. Blackscreen on reboot fixe by btrfs check, after version --dup work one time but not completly done the upgrade. Now when i try version --dup it's not working :

Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Finished transaction (status=2, runtime=0ms)
UPGRADE NOT COMPLETE - Retry 4 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES

Error: Failed to activate service 'org.freedesktop.PackageKit': timed out
Finished transaction (status=2, runtime=0ms)
UPGRADE NOT COMPLETE - Retry 5 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES

and when i try to restart packagekitd, journalctl indicate that issue:

Sailfish packagekitd[xxpidxx]: Failed to load the backend: opening module zypp failed : librpm.so.8: cannot open shared object file: No such file or directory

Is it possible to download and install rpm/zypp package manualy ?

Thanks in advance,

edit retag flag offensive close delete

Comments

Did you try 'ssu re 2.2.1.18', then 'version --dup'?

Levone1 ( 2018-09-11 02:46:41 +0200 )edit

yes, my device is already in release mode. I think some package are broken librpm...

but i don't know, if it's possible to dowload and extract packages manualy to fix it.

simc ( 2018-09-11 12:19:42 +0200 )edit

not sure. I saw this - https://together.jolla.com/question/92209/blank-screen-after-updating-to-11429-glibc-broken/ - which might be similar.. (or restore in recovery)

Levone1 ( 2018-09-11 13:21:22 +0200 )edit

Did you try 'ssu re 2.2.1.18', then 'version --dup'?
Levone1 ( 2018-09-11 02:46:41 +0200 )edit
yes, my device is already in release mode. I think some package are broken librpm...
but i don't know, if it's possible to dowload and extract packages manualy to fix it.
simc ( 2018-09-11 12:19:42 +0200 )edit
not sure. I saw this - https://together.jolla.com/question/92209/blank-screen-after-updating-to-11429-glibc-broken/ - which might be similar.. (or restore in recovery)
Levone1 ( 2018-09-11 13:21:22 +0200 )edit

Answer 1

1

answered 2018-09-17 19:17:45 +0200

simc
71 ●3 ●7 ●9

Yes, I think it' that librpm.so.8 is missing but i don't know how to download this RPM manualy from the repository :

rpm-libs-4.9.1.2-1.4.1.armv7hl.rpm

https://releases.jolla.com/releases/2.2.1.18/jolla/armv7hl/core/armv7hl/rpm-libs-4.9.1.2-1.4.1.armv7hl.rpm return : not found.

I'm familiar with debian repository not good with RPM :-(, How it's works ?

edit flag offensive delete publish link

Comments

Try devel-su pkcon refresh then attempt update again.

If that doesn't work, try devel-su pkcon search name rpm-libs and see what you get offered, when I tried it, I got this;

    [nemo@Sailfish ~]$ devel-su pkcon search name rpm-libs
    Password:
    Searching by name
    Starting
    Refreshing software list
    Querying
    Finished
    Installed       rpm-libs-4.14.1+git3-1.3.2.jolla.armv7hl (installed)

Regarding RPM usage, rpm --help

Spam Hunter ( 2018-09-17 21:57:31 +0200 )edit

'pkcon download . rpm-libs' if you want to save it, or 'pkcon install...' Also, I found this in sailfish documentation for rebuilding corrupt database, (run as root) - 'rm -rf /var/lib/rpm/__db* ; rpm --rebuilddb' - maybe applicable...

Levone1 ( 2018-09-17 22:15:00 +0200 )edit

Update to 2.2.1.18 on Jolla J 1 Failed

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Update to 2.2.1.18 on Jolla J 1 Failed

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions