All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"mariano.lopez@intel.com" <mariano.lopez@intel.com>
Subject: Re: do_populate_cve_db: Error in executing cve-check-update
Date: Mon, 6 Feb 2017 17:17:04 +0200	[thread overview]
Message-ID: <CAHiDW_GXHZ4Yk_pbEZXLgvzsnohZFjHGcDdfMUFz2bmCcSbJ=g@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LZ+khtB9f==4KQr_iaVJhHmTGfFj-2toAnN=GFPiyUVDQ@mail.gmail.com>

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

On 6 February 2017 at 16:56, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 6 February 2017 at 14:43, Sona Sarmadi <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.

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.

Jussi

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

  reply	other threads:[~2017-02-06 15:17 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 [this message]
2017-02-07 15:07     ` Mariano Lopez
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='CAHiDW_GXHZ4Yk_pbEZXLgvzsnohZFjHGcDdfMUFz2bmCcSbJ=g@mail.gmail.com' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.