Am Montag, 3. Oktober 2011, 21:51:05 schrieb Martin Schlander:
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.
Nobody expects that. But what I thought that one could expect is that all packages in it build, i.e. are not broken. So if digikam 1.9 is the last version that builds fine for KUA it should be in there and not updated to 2.0.
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.
See above. If a version does not compile for distro x.y it should not be included in KUA. Everything that is in the repo and installable via YaST should work. Of course there can be issues if a new version is introduced but then it should be fixed ASAP after it was noticed. If the latter does not work within days or a week max then the repo should not be on the community repo list, IMHO. I'm not saying that one can demand anything from anyone, just that whatever repo is put on the community repo list must have a certain QA standard and be maintained. If those standards cannot be met then the repo has to be removed. In case of digikam there is a tarball which contains all necessary libs, so it should be buildable, but I might be wrong about that. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org