2014-07-03 18:06:41 UTC
kernel-xen. If someone could fix that, it'd be appreciated ...
Of greater interest is fixing a 'problem' that keeps allowing it (and
other repos) to be regularly broken; spefically, as posted @:
"REQUEST: don't push Project updates to repos until all pkg builds are
'succeeded'; don't allow push if pkgs are in 'failed' state #702"
Yes, I know the mantra -- "it's development".
Packages can be built -- and some can be broken -- without breaking
highly useful/used repos in the process. Whether that's by fixing push
rules for existing repos, or creating a ":tested" class for
some/selected repos -- I don't know what's 'best'.
But, I'd argue, in a situation where those such repos are *widely used*
as fixes for broken release pkgs, or access to modern/needed feautres --
as is very much the case for KernelStable -- there's real value in
having consistent access to a working, dependency-consistent repo, even
for 'development' builds.
I'm not sure what the final answer should be. I'm hoping it's not
sticking our heads in the sand, and that there are at least a reasonable
handful of folks that'd appreciate a stable alternative.