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. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On 07.03.2016 12:33, Adrian Schröter wrote:

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 ...

As I just learned recently: the spanish say 'cuando los sapos bailan flamenco' - which is much more poetic than your version. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org