In preparation to publish the next major Sailfish OS release, 5.1, to early access users, we have published the repositories and added them to the community OBS.
This is done so that the software in Chum and other projects in OBS can be rebuilt against the new release, and any build issues fixed before the release is published to the wider early access user base. Many of the build tools and lower level libraries have received version updates of varying degrees, so incompatibilities and other issues are to be expected.
Some notable changes:
Tools and languages
cmake - 3.27.1 => 3.31.8
gcc - 10.3.1 => 13.4.0
gdb - 12.1.0 => 16.3.0
make - 4.2.1 => 4.4.1
meson - 1.4.1 => 1.9.1
perl - 5.16.3 => 5.40.3
python3 - 3.8.18 => 3.11.15
Libraries and components
curl - 8.9.1 => 8.19.0
cython - 0.29.14 => 3.0.11
glib2 - 2.78.4 => 2.86.4
glibc - 2.30 => 2.41
glslang - 14.1.0 => 15.3.0
gobject-introspection - 1.72.1 => 1.86.0
gstreamer1.0 - 1.24.6 => 1.26.11
libphonenumber - 8.13.27 => 9.0.5
linux-glibc-devel - 3.18.136 => 4.4.302
lxc - 5.0.2 => 6.0.3
ncurses - 6.5 => 6.6
net-tools - 1.60 => 2.10
openssh - 9.8p1 => 10.3p1
openssl - 1.1.1v => 3.5.6
* openssl1.1 kept available for compatibility
poppler - 24.08.0 => 25.12.0
pulseaudio - 14.2 => 17.0
python-pip - 19.3.1 => 23.3.2
python3-fuse3 - 2.0.0 => 3.4.0
python3-lxml - 4.6.5 => 5.3.0
python3-setuptools - 46.1.3 => 70.3.0
python3-twisted - 20.3.0 => 22.10.0
sqlite - 3.46.1 => 3.50.4
taglib - 1.12 => 2.0.2
This is not a comprehensive list, and some things listed here may or may not be as significant as some that were not included Full changelog will be provided later.
Updating your development devices
The developers who want to test things on device can update their devices from command line, you know how to do it, if you don’t, then this is not for you
The currently published version is: 5.1.0.5
Make sure you have enough free disk space, at least 1.5G on the rootfs, preferably more. Update installation on running system may take significantly more space during the installation than is actually needed afterwards.
“Make sure you have enough free disk space, at least 1.5G on the rootfs, preferably more. Update installation on running system may take significantly more space during the installation than is actually needed afterwards.”
I think this is going to be a big problem for those wishing to upgrade. I have an XA2, XA2 Plus, Sony Xperia 10 Mk iii, iv and v. NONE of those phones have in excess of 1.5 Gb free on the root file system.
The 10iii, which has been upgraded over the years from 4.x versions, has 492 Mb free (nowhere near enough) whilst my 10 iv, freshly flashed with 5.0.0.77, has 809 Mb free.
Of course I can delete all my apps, but is that really going to free up nearly 1Gb?
So, at the moment 5.1 is a non starter for ALL of my five SFOS phones without starting again from scratch on every one.
Usually cache of browser, angelfish, Quickddit (if links are opened in webview), thumbnails of pictures takes hundreds of MB or even more depends on usage.
[ 151s] + /usr/bin/python3 -B /usr/lib/rpm/meego/pathfix.py -pni /usr/bin/python3 -kasP libevdev/make-event-names.py
[ 152s] /usr/bin/python3: can't open file '/usr/lib/rpm/meego/pathfix.py': [Errno 2] No such file or directory
[ 152s] error: Bad exit status from /var/tmp/rpm-tmp.Mn0LwF (%prep)
Is that supposed to work?
(That particular .spec has a bug where this macro is evaluated despite it being commented out (single %), but this did not fail in earlier releases.)
[EDIT]: definitely not specific to one package. Is python-rpm-macros broken perhaps?
I’m not a dev but happened to have a 10 II with a 10 GB rootfs…, after update 3,6 GB in use, 6,5 free.
The XA2 is still my main phone. I use Kuri, Pure Maps and OSM Scout Server so no update yet. I’ll do it with zypper dup and move big files out of the way as needed - no uninstalls.
The update initially went well, but I don’t have internet access in any of the Sailfish apps. However, everything works perfectly in my Android apps. I have a C2.
Full changelog will be provided later.
