On Montag, 7. März 2016, 12:24:48 wrote Stephan Kulow:
On 07.03.2016 12:20, Andreas Schwab wrote:
Olaf Hering
writes: build-compare compares rpmlint.log and triggers a republish if the old and new rpmlint.log differs. What could be the reason to republish a pkg if the rpmlint.log changes? The scm log contains no hints for the reasoning for this appearently useless check.
If rpmlint checks have been updated you don't want to lose the result of them.
Right. Unfortunately the way the OBS implements unchanged, it's all or nothing. We can't cherry-pick build results.
we can change this, once we store QA results different from build results ... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org