From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: deeratho@cisco.com,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Yoann Congal <yoann.congal@smile.fr>
Cc: "Viral Chavda (vchavda)" <vchavda@cisco.com>
Subject: Re: [OE-core] Inquiry Regarding Package Upgrade Approach vs. Manual CVE Fixes in LTS Releases
Date: Mon, 16 Mar 2026 10:00:30 +0000 [thread overview]
Message-ID: <eb249cdc0bfb57d3e0ef4cb20dafffe7896c408b.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM4PR11MB61899D3F758D2B3C7BAA9361C444A@DM4PR11MB6189.namprd11.prod.outlook.com>
On Thu, 2026-03-12 at 08:45 +0000, Deepak Rathore via lists.openembedded.org wrote:
> I am currently working for Cisco where our team focuses primarily on:
> * CVE fixing for OSS packages
> * Package upgrades
> * LTP execution and validation
I would note that we're going to have to drop support for LTP in the
next week before feature freeze.
Upstream have removed runltp and switched to kirk. We have no support
for this. I have repeatedly asked for help in switching but have not
received any, a such we likely need to remove ltp for the next LTS.
Cheers,
Richard
prev parent reply other threads:[~2026-03-16 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:45 Inquiry Regarding Package Upgrade Approach vs. Manual CVE Fixes in LTS Releases Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-12 8:58 ` Marko, Peter
2026-03-12 13:32 ` Yoann Congal
2026-03-16 9:39 ` Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-16 10:53 ` [OE-core] " Alexander Kanavin
2026-03-16 11:33 ` Paul Barker
2026-03-16 10:00 ` Richard Purdie [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=eb249cdc0bfb57d3e0ef4cb20dafffe7896c408b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=deeratho@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=vchavda@cisco.com \
--cc=yoann.congal@smile.fr \
/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