From: "akuster" <akuster808@gmail.com>
To: Ross Burton <ross@burtonini.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [[PATCH] cve-check.bbclass: don't skip scanning if file not found
Date: Thu, 18 Feb 2021 12:19:29 -0800 [thread overview]
Message-ID: <a90e22e6-2dbc-945b-7c35-a0dc2f4c336d@gmail.com> (raw)
In-Reply-To: <CAAnfSTsYM9QwW6qyLAfC+OnKES0K0nfvH9eoTCZu1zH9-HuObA@mail.gmail.com>
On 2/18/21 8:50 AM, Ross Burton wrote:
> Why is the file not found though?
its downloaded there for not in the WORKDIR
-armin
>
> Ross
>
> On Mon, 15 Feb 2021 at 22:41, akuster <akuster808@gmail.com> wrote:
>> This helps avoid these errors:
>> ERROR: lockdev-1_1.0.3-r0 do_cve_check: File Not found: /home/build/builds/master/tmp/work/core2-64-poky-linux/lockdev/1_1.0.3-r0/lockdev_1.0.3-1.6.diff
>>
>> We should continuing to scan other applied patches for CVE info.
>>
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>> meta/classes/cve-check.bbclass | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
>> index 1bed815d8e4..e56366579d1 100644
>> --- a/meta/classes/cve-check.bbclass
>> +++ b/meta/classes/cve-check.bbclass
>> @@ -186,8 +186,8 @@ def get_patches_cves(d):
>> patch_file = bb.fetch.decodeurl(url)[2]
>>
>> if not os.path.isfile(patch_file):
>> - bb.error("File Not found: %s" % patch_file)
>> - raise FileNotFoundError
>> + bb.warn("File Not found: %s" % patch_file)
>> + continue
>>
>> # Check patch file name for CVE ID
>> fname_match = cve_file_name_match.search(patch_file)
>> --
>> 2.25.1
>>
>>
>>
>>
prev parent reply other threads:[~2021-02-18 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 22:41 [[PATCH] cve-check.bbclass: don't skip scanning if file not found akuster
2021-02-18 16:50 ` [OE-core] " Ross Burton
2021-02-18 20:19 ` akuster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a90e22e6-2dbc-945b-7c35-a0dc2f4c336d@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox