On Thu, Nov 04, 2021 at 06:51:23PM +0100, Florian Weimer wrote:
* 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
On Thu, Nov 04, 2021 at 06:51:23PM +0100, Florian Weimer wrote:
* 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
* 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
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
I've got an rpminspect failure I don't understand. Looking at
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/54461/testReport/(root)/tests/_patches/
the relevant result seems to be this:
|25) glibc-upstream-2.34-18.patch touches 26 files and as
