Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yoann Congal <yoann.congal@smile.fr>
To: openembedded-core@lists.openembedded.org
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [OE-core][kirkstone 0/1] Pull request
Date: Fri, 31 Jul 2026 01:17:43 +0200	[thread overview]
Message-ID: <cover.1785453214.git.yoann.congal@smile.fr> (raw)

Fixes to improve the local CVE database reliability. Even if the branch
is EOL, the CVE metrics is the only part we maintain.
Should fix 15660 – [kirkstone, scarthgap] AB-INT: cve-update-nvd2-native-1.0-r0 do_fetch: CVE database update failed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15660

The following changes since commit 51259c7e933a2ac8ebc01604d6e65607b76b7b56:

  build-appliance-image: Update to kirkstone head revision (2026-04-10 14:14:10 +0100)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
  https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next

for you to fetch changes up to 9687b9409d3a1e121f0f04de856055764d0a392e:

  cve-update: Avoid NFS caching issues (2026-07-31 01:06:35 +0200)

----------------------------------------------------------------

Paul Barker (1):
  cve-update: Avoid NFS caching issues

 meta/recipes-core/meta/cve-update-db-native.bb   | 9 +++++++--
 meta/recipes-core/meta/cve-update-nvd2-native.bb | 9 +++++++--
 2 files changed, 14 insertions(+), 4 deletions(-)



             reply	other threads:[~2026-07-30 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 23:17 Yoann Congal [this message]
2026-07-30 23:17 ` [OE-core][kirkstone 1/1] cve-update: Avoid NFS caching issues Yoann Congal
  -- strict thread matches above, loose matches on Subject: below --
2026-04-10 12:26 [OE-core][kirkstone 0/1] Pull request Yoann Congal

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=cover.1785453214.git.yoann.congal@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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