http://bugzilla.suse.com/show_bug.cgi?id=1142975
http://bugzilla.suse.com/show_bug.cgi?id=1142975#c2
--- Comment #2 from Dominique Leuenberger
This is not a machinery issue.
I think it is not good that updates of packages can be released to Tumbleweed which break already existing packages. This happened a couple of times in the past for Ruby gems.
It is the nature of a rolling distro to receive frequent updates - and it's a balancing act to allow breakage vs getting releases at all. In a perfect world, I'd agree, all packages would work at any moment. In reality, we are far away from that - there are currently > 250 failing packages in openSUSE:Factory. The only 'guarantee' for non-breaking packages are the ones in the rings. We could increase the priority of machinery into the rings - But that requires buy-in from all the maintainers in the stack below machinery, as all build-deps and runtime-deps need to be raised to rings as well. Depending on the number of packages and the build time of said packages, this can in plus have negative impact on the TW release throughput in general. In any case: once the issue is fixed, we can discuss these options together -- You are receiving this mail because: You are on the CC list for the bug.