Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "mariano.lopez@intel.com" <mariano.lopez@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: do_populate_cve_db: Error in executing cve-check-update
Date: Tue, 7 Feb 2017 09:07:46 -0600	[thread overview]
Message-ID: <8ab28120-012b-4f16-e812-a06ad8b351b9@linux.intel.com> (raw)
In-Reply-To: <CAHiDW_GXHZ4Yk_pbEZXLgvzsnohZFjHGcDdfMUFz2bmCcSbJ=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]



On 06/02/17 09:17, Jussi Kukkonen wrote:
>
>
> On 6 February 2017 at 16:56, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
>
>     On 6 February 2017 at 14:43, Sona Sarmadi <sona.sarmadi@enea.com
>     <mailto:sona.sarmadi@enea.com>> wrote:
>
>             bbdebug 2 "Updating cve-check-tool database located in
>         $cve_dir"
>             if cve-check-update -d "$cve_dir" ; then
>                 printf "CVE database was updated on %s UTC\n\n"
>         "$(LANG=C date --utc +'%F %T')" > "$cve_file"
>             else
>                 bbwarn "Error in executing cve-check-update" 
>         <<<<<<<<<<<<<<<<<<<<<<<<<
>
>
>     This definitely needs to be rewritten so you can see the output if
>     it fails.  Just run cve-check-update -d <dir> yourself and see
>     what it says.  Last time I had this failing it was because the
>     mitre servers were offline.
>
>
> Agreed about the error output.

Also you need to patch the tool, most of the time there is no output
from it; I think Ikey would integrate those patches without hesitation.

>
> I think recipe specific sysroots broke the setup somehow (so the tools
> are not actually in sysroot when they're needed). I'm taking a look at
> this tomorrow.

I tried today, but I'm having a hard time with the proxies (like always)
so I can't really verify this. Were you able to check?

Mariano

[-- Attachment #2: Type: text/html, Size: 3937 bytes --]

  reply	other threads:[~2017-02-07 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 14:43 do_populate_cve_db: Error in executing cve-check-update Sona Sarmadi
2017-02-06 14:56 ` Burton, Ross
2017-02-06 15:17   ` Jussi Kukkonen
2017-02-07 15:07     ` Mariano Lopez [this message]
2017-02-07 16:49       ` Jussi Kukkonen

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=8ab28120-012b-4f16-e812-a06ad8b351b9@linux.intel.com \
    --to=mariano.lopez@linux.intel.com \
    --cc=jussi.kukkonen@intel.com \
    --cc=mariano.lopez@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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