* Aleksei Bavshin:
On 11/4/21 09:17, Florian Weimer wrote:
> Why is this VERIFY? The patch was generated as if by “git show”, and I
> do not see anything wrong with it.
rpminspect thinks that the patch is suspiciously large and asks you to
confirm that it is intentional.
There's a test description in the beginning of the log:
Inspects all patches defined in the spec file and reports changes
between builds. At the INFO level, rpminspect reports diffstat(1) and
patch size changes. If thresholds are reached regarding a change in
the patch size or the number of files the patch touches, rpminspect
reports the change at the VERIFY level unless the comparison is for a
rebase. The configuration file can also list patch names that
rpminspect should ignore during the inspection.
Is this a new check? It was flagged as a regression in Jenkins.
Thanks,
Florian