On Mon, 2017-03-13 at 17:45 +0100, Olaf Hering wrote:
Am Mon, 13 Mar 2017 17:23:19 +0100 schrieb Dimstar / Dominique Leuenberger <dimstar@opensuse.org>:
Any ideas are welcome on how to avoid this in the future - the more automatic it is, the higher the chance of it not failing again.
How much longer is the turnaround if build-compare takes care of it, instead of doing the pkg selection manually? Are there any numbers? Even if the tree is not 100% clean today it would be nice to know what the cost is when doing full rebuilds unconditionally, compared what is done right now. I think ABI breakage happened often enough in the past to consider a change.
Just as a comparison: when we switch on rebuildstrategy 'direct' (which is still more optimized than OBS' default): TW churns around usually for 3 - 5 days - definitively too much for Tumbleweed snapshots to be building. It's not even clear if the issue would not have appeared, as libffi4 was part of the distro and was readily available to be used - and now it's not any longer Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>