7 Mar
2016
7 Mar
'16
11:20
Olaf Hering
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. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org