On Tue, Oct 4, 2011 at 12:12 PM, Sven Burmeister
Am Dienstag, 4. Oktober 2011, 11:46:52 schrieb Martin Schlander:
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 repeat myself again. There is no maintainer for KUA! QA is not given. That's all that matters.
How do I know? Simply because there would not be a broken 1.9 package in there months after it built correctly (if ever) last time if somebody cared. And that's exactly the problem which I think you ignore. Unless there is an active maintainer it does not belong on the community repos list.
And another thing you ignore is that all those supposedly not hurting build failures hide feedback regarding the published packages. The repo monitor and the repo content are not in sync and thus this makes it even more difficult to know which packages are ok in the repo but failing to build or failing to build and broken in the repo as well.
So what you do when seeing a build failure in KUA is to assume that it's ok since there are the last working binaries still in the repo. You don't know and that's simply not enough for a repo to be recommended, i.e. part of the community repos list.
Sven
The build status tells you absolutely nothing about whether the package works when installed. Packages can be, and are, green across the board and still fail to install or fail when running (in fact I am currently fixing a problem with wine where it builds but refuses to install in Factory). OBS does not check whether packages work when installed. So even if it built successfuly that would still not be enough to assume the binaries work. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org