From: Yoann CONGAL <yoann.congal@smile.fr>
To: Stephen Jolley <sjolley.yp.pm@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
",openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status 12 March 2024 (WW11)
Date: Wed, 13 Mar 2024 21:04:38 +0100 [thread overview]
Message-ID: <CAMSfU+5fTNCyTSRMkN=L4UQ83eOSBtfBXHUUhmMtUd9KEgjJYA@mail.gmail.com> (raw)
In-Reply-To: <CAK5yBb-rUZzdqbXD4yoHiF5V-L2sOg1DVWMEsDGXWk36F2cexQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
Hi,
Le mar. 12 mars 2024 à 15:45, Stephen Jolley <sjolley.yp.pm@gmail.com> a
écrit :
>
> -
>
> The previously reported CVE database update issue on the autobuilder
> has not been addressed yet. This is causing higher numbers of CVEs to be
> reported on the autobuilder generated charts.
>
> Here's my proposal to fix this :
- [PATCH 2/2] cve-update-nvd2-native: Add an age threshold for
incremental update
https://lists.openembedded.org/g/openembedded-core/message/197046
- [yocto-autobuilder2][PATCH] schedulers: metrics: Start with master for
the daily full download
https://lists.yoctoproject.org/g/yocto/message/62754
- [yocto-autobuilder-helper][PATCH] config.json: metrics: Switch to
daily CVE DB full-download
https://lists.yoctoproject.org/g/yocto/message/62753
Those 3 patches work together to (hopefully) do a daily full download of
the NVD CVE database. That should fix the metrics on master and any branch
sharing the CVE database with it.
Best regards,
--
Yoann Congal
Smile ECS - Tech expert
[-- Attachment #2: Type: text/html, Size: 2567 bytes --]
prev parent reply other threads:[~2024-03-13 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 14:45 Yocto Project Status 12 March 2024 (WW11) Stephen K Jolley
2024-03-12 16:03 ` [OE-core] " Alexander Kanavin
2024-03-12 17:29 ` Richard Purdie
2024-03-12 17:42 ` Alexander Kanavin
2024-03-13 20:04 ` Yoann CONGAL [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='CAMSfU+5fTNCyTSRMkN=L4UQ83eOSBtfBXHUUhmMtUd9KEgjJYA@mail.gmail.com' \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=sjolley.yp.pm@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).