SFOS 4.5.0 switches RPM compression. What does that mean for existing RPMs?

@jolladiho :

  1. which version of SFOS do you use? (SFOS 4 does not need libcrypto.so.10)
    if you are on SFOS 3.4 you will need https://openrepos.net/sites/default/files/packages/8272/openssl-libs10-1.0.2o-5.armv7hl.rpm (but then it’s not rpm that needs it but the other system components)
  2. you do not seem to have installed rpm (legacy SFOS 3.4 - 4.2) | OpenRepos.net — Community Repository System because these versions depend on libcrypto.so.1.1 and not on libcrypto.so.10
  3. do not use pkcon as this stupid tool installs multiple packages not in one step but calls rpm multiple times (which doesn’t work: rpm fails right after libcrypto.so.10 is removed)

first thing to do to get your device working again seems to extract libcrypto.so.1.0.2o and the symlink libcrypto.so.10 out of openssl-libs10-1.0.2o-5.armv7hl.rpm with an xz-archive-app and put it in /lib/ at your device via jolla-recovery-mode-shell (over telnet) https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode (depending on your phone type)

@lpr sorry for being to short on my question.

  1. I’m using sfos 3.4 on the “First One” and get “bad magic” errors. I will try the “openssl-libs10…” next to solve some problems. I know it’s to old and not supported any more.

  2. Ok I have an eye on this. There was an error, but I cannot remember. After that try, the device was dead.

  3. I could install nothing, because there was an update of “harbour-file-browser” at Jollastore. And every pkcon install(-local) “name-of-a-single-package” ended in an abortion because it always tried to install “harbour-file-browser” together with the “name-of-a-single-package”. Hmm, and why does the Jollastore URL have the sfos version included if it does not take note of it? :frowning:

I restored an old backup (rootfs.tar) via recovery and telnet - it’s alive again and I wll try it once more next days (after making a fresh backup this time).

Thank u a lot.