you dont trust package built from sources in public obs? go and build latest bash with security patches yourself. oh, you dont believe patches from internet and dont want to apply it to sources, still sitting and waiting for OS maintainers to deliver you these modifications?

I actually thought they would integrate younited with Jolla for automatic photo uploads etc. but yeh... not installing the android app.

How do I know that is where it is built from?

i'm using my brain to know what i need. is there any alternative to brains in our universe?

Well, you can always just fetch the package directly from OBS.

BTW, there was a talk about an OBS bridge for OpenRepos - any status updates Basil ?

How do I know that regarding Jolla's updates?
The keyword here is 'trust'. I trust Jolla and I trust OpenRepos.net Everything you do and use with your Jolla is a matter of trust, bro.

OK, good for you. I don't trust OpenRepos.net.

Quick reply...

What is the part that you do not trust: the compiler or the code? If compiler, then compile it yourself, like Gentoo, or feed it to a trusted builder. If code, then read it, or wait for the developers whom you trust to read it.

Best wishes.

You have no idea how amused I am that "smart watch" got presumably hit by the forum swear filter.

QA is the easiest, most obvious missing part. I can't even count the number of times I've upgraded a desktop linux distro and ended up with a nonbooting system, or a system that won't boot to UI, or broken audio, or, or, or ... you get the idea.

Seeing the number of distros that ship complex things like Qt virtually unpatched at the .0 minor release, after knowing the amount of effort we had to put into 5.1.x and now 5.2.x to get them to a remotely product-capable level, makes me realise that the people testing them aren't really testing them at all. Either that or they're testing with a "hello world".

Same with virtually every other piece of software in the world, unfortunately, although most aren't quite as large/complex (in terms of LOC).

A consumer product has to try much, much harder to avoid problems like those. And as it gets older, the compatibility matrix gets a lot bigger. And when it's open/hackable, the testing matrix is even bigger still, because you don't know what jerk decided to do some absolutely crazy thing to their system six months ago that they long since forgot about.

It's a pretty hard problem. A solvable one, with enough hands, but those aren't infinite.