Tirsdag den 4. oktober 2011 10:52:23 skrev Sven Burmeister:
Am Dienstag, 4. Oktober 2011, 08:24:38 schrieb Martin Schlander:
Well. If one broken published binary on an old distro version, ever, is enough to remove a repo from the community repos list, then you can remove all of them, including packman and mozilla.
The mozilla repo seems pretty green, 100% for 11.4 and one package failing for 11.3 and that's a branding package. I have not tested every package in KUA and you might be right that all the ~20 packages failing might not be published – nevertheless they fail.
And the issue is not that there is one broken binary but simply that there is nobody checking whether it builds within KUA and to fix it within hours/days (reverting to a version that builds within KUA)
This is the last time I repeat myself. Users are not affected by build failures. Noone is. The amount of "red" and build failures couldn't be less significant - especially not in a repo for leaf packages only. It's a complete non-issue. What does matter is the binaries that actually get published for users. If the build fails, the package isn't published. And the "old" binary remains in the repo. That is why users still see digikam 1.9 in KUA, when digikam 2.0 fails to build. The brokenness of digikam 1.9 on 11.3 has absolutely NOTHING to do with digikam 2.0 or any other package in KUA failing to build. And digikam 2.0 or any other package in KUA failing to build does not hurt ANY user. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org