lint: Workaround rhcheckpatch returning non-zero on errors
When the second lint stage is enabled, rhcheckpatch also needs to change its return code to non-zero to properly trigger the pipeline warning.
If the second lint stage creates problems and needs to be reverted, then insted of reverting that patch and rhcheckpatch, just revert the second lint stage creation patch.
This patch just makes it easier to revert if things go bad, otherwise it is very useless.
The patch dependency only fails with return code 255, hence the logic.
Signed-off-by: Don Zickus dzickus@redhat.com
NOTE: This allows me to modify the return code for rhcheckpatch before enabling the second lint stage.