Yes, most probably it could be that. As I also noticed (maybe not related) that Seaprint depending on curl does not want to play with my printer(s) anymore…
So… what’s the point of providing conflicting libraries to what SFOS normally ships?
Seems like it is a sure way to break a system…
With a bit of work, it should not break anything.
The point? Updated apps to latest versions, to have better security and better compatibility with newer standards.
4 Likes
When core things depend on them, how can it not?
Sure, Jolla doesn’t release very often - but things tend to be fairly up top date once they do.
Because libraries have different extensions for versions
For example libcrypto.so.3 as to libcrypto.so.1
So, things can mostly live side by side
3 Likes
Now that makes me laugh and let me answer.
Version of libcurl on Jolla repo: 8.9.1+git1-1.1+.2.jolla, dating back to 2024-07-30T22:00:00Z
Current libcurl version as of 2026-01-06T23:00:00Z: 8.18.0
Maybe see that link as well?
What about sqlite3, as another e.g.?
Jolla: 3.46.1, 2024-08-12T22:00:00Z
Current: 3.51.2, 2026-01-08T23:00:00Z
And more …
–
Do someone remember the for years available vpnc-0.5.3.patch for being able to connect to a FRITZ box?
3 Likes
Curl is good at keeping backwards compatibility, so my package almost definitely will not break anything for libcurl (major version is same)
And yes, this is one reason I am working on updates 
Hopefully it does not break things. This I’ll test more when I do have a device (i586 build servers still dead, so can’t use the emulator atm)
1 Like
Which is also what they have in their github repos.
I’m still puzzled as to what the point is here. Why not contribute to the Jolla packaging if they are so much after in your favorite packages?
3.50 in their github repos.
Nobody outside .de presumably cares; but solution is the same - why not help upstreaming or packaging?
@attah as for packaging, well, this is what iam doing. Care to link their GitHub? I’ll happily push.
As for “nobody cares” - that’s kinda rude. I care, many of my supporters (and kind ppl who helps in other ways) are from DE.
3 Likes
maybe you can add to your repo?
dav1d for av1 (ffmpeg/ffplay) (GitHub - videolan/dav1d: A read-only mirror of dav1d source code repository. The origin is at https://code.videolan.org/videolan/dav1d/ builds without issues)
maybe libao for frotz (for ancient text adventure games)
4 Likes
done and on my repository (both packages)
2 Likes
Thank you! (20 -explicitly not written- chars)
1 Like
I have build two rpm’s for ChameleonUltra, for the app ChameleonUltraGUI which can control the device. I would like if someone with physical devices can test 
http://sec1.dk/chameleon.chameleonultragui-1.3.0-1.armv7hl.rpm
http://sec1.dk/chameleon.chameleonultragui-1.3.0-1.x86_64.rpm
http://sec1.dk/chameleon.chameleonultragui-1.3.0-1.aarch64.rpm
Don’t forget the glibc! Version 2.30, released in 2019.
Tor, Tor-hs-example (hidden service), harbour-tor-button (app to start/stop Tor daemon) and apache2 all up so that you can actually use tor, and run a webserver as a hidden service (this gave me a tshirt, long before I made the packages ready, from tor project. I still needs to write a blog about that)
3 Likes
@nieldk is it ok to voice wishes/requests here? Feel free to ignore.
I wanted to install wireshark through Openrepos yesterday but apparently it’s not available for my Xperia X10 II. I’m guessing 32 bit only, it’s also really old (2014).
CLI would suffice.
There aren’t any proper continuous deep monitoring network tools available for SFOS. I had to faff around with netstat and ss and was wishing I could install something better.
Did you try Nethogs from Chum?
Perfectly OK to have wishes.
There is tcpdump on my build.sailfishos.org repository, once that build engine is up again I promise I will work on wireshark (or at least tahsin which is CLI version)
2 Likes