This seems to be the case with my 10 II, too.
This IS the case with EVERY updated device until CHUM is updated as well.
Symbolic links have been added for the Chum repositories for the .25 release, so they should now work without any modifications.
I cannot install. Updater says âno connectionâ although there is a connection.
I had same issue, found an old post where problem fixed by delete cashe files from /etc/zypp/repos.d/* and after a few reboots managed to install using manual method.
Thank you.
@Jolla:
Since my most pressing issue with 4.5 is the now dysfunctional weather service and I have no trust in the new business owners yet, I decided not to risk the good state on my devices by installing updates that donât do anything for me. I wish you good luck and will wait and see what people say about 4.6.
I got a message that i need to remove or revert ca-certificates before upgrading.
How do i revert ca-certificates to the stock version?
As a wise man once said
Only fools rush in. +++
Thanks, the first time it didnât work and i got that it wasnât able to upgrade.
The second time the upgrade worked as expected without doing anything about ca-certificates.
We have switched the rpm compression from xz to zstd on 4.5.0.
Malicious commits found in xz.
XZ-utils in sailfish is 4 years old, so this is irrelevant as far as sfos is concernedâŚ
Not really:
(still kinda unrelated as x86 machines running sfos are like⌠Handful, so doubt someone spent 2 years to target them)
Still much older than the (known) affected versions.
Look at the crossed title in screenshot: 5.6.1the exact backdoored version, luckily our openssh is not the patched one from rhel/debian
I noticed the CVE for xz while updating (CVE was created just hours before) so I reverted to older version just in case. There are several factors which would have made the backdoor not work in Sailfish (based on current information): we donât use patched openssh, the architectures affected are rare or non-existent for Sailfish, and most importantly we build xz from git and since one of the critical parts for enabling the backdoor is only in the release tarball it wouldnât have been enabled.
" I have no trust in the new business owners yet" ---- I follow your position
Meanwhile, did you review 4.6 and do you find it interesting (new EULA, bug fixes, especially on Xperia 10 III ?)
I updated my Xperia XA2, everything seemed to work, but I didnât use it for long and only without SIM. On my main device Xperia 10 III, I still didnât do the update. I donât notice the small bugs that may have been fixed.