On 3 October 2011 20:51, Martin Schlander
Mandag den 3. oktober 2011 21:37:32 skrev Cristian Morales Vega:
On 3 October 2011 20:15, Martin Schlander
wrote: Mandag den 3. oktober 2011 18:56:30 skrev Sven Burmeister:
Am Montag, 3. Oktober 2011, 18:47:42 schrieb Martin Schlander:
Even if it was maintained by someone who knew what they were doing, it's very unlikely anyone would test all the packages on all suse versions and archs.
KUA is using a distinct "if it builds, ship it!" policy. Noone reported any problems until now, so I don't think it would have made a difference if someone else maintained it.
Even though it's in the community repos list, it's still an unsupported repo, and some minor risks should be accepted.
It's not about testing but simply not having it broken for weeks. A repo which is basically unmaintained should not be offered on the community repos list.
And how are you supposed to know it's broken without testing it and noone reporting there's a problem?
In this specific case just looking at https://build.opensuse.org/project/monitor?project=KDE%3AUpdatedApps The last successful build of digikam was on 2011-07-22. Let's face it, KUA is unmaintained...
The way it works is that when some new app appears in KDF it's linked to KUA - if it builds it builds - if it fails it shouldn't hurt anyone. You can't expect everything to build on old 11.3.
It also fails in 11.4, the latest stable release.
E.g. digiKam 2.x failing to build on 11.3 is not really a problem. In fact it's expected. This does not serve as a hint to anyone that digiKam 1.9 binaries are broken on 11.3.
If every maintainer of KUA agrees in that this is the level of support that should be expected OK. But then you have my vote to raise the minimum level of support required to be in the community repos list and remove KUA from it. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org