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