All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco)" <schitrod@cisco.com>
To: "Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC
	at Cisco)" <schitrod@cisco.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"raj.khem@gmail.com" <raj.khem@gmail.com>
Subject: RE: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18
Date: Sat, 27 May 2023 03:10:21 +0000	[thread overview]
Message-ID: <SJ0PR11MB6717215C1B92036799E1AC2EDC449@SJ0PR11MB6717.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1760742CFB0AAE9D.26337@lists.openembedded.org>

Hi all,

Any update/comment ?
@raj.khem@gmail.com can you please guide me on how to procced further ?

Thanks,
Sanjay

-----Original Message-----
From: openembedded-devel@lists.openembedded.org <openembedded-devel@lists.openembedded.org> On Behalf Of Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) via lists.openembedded.org
Sent: Friday, May 19, 2023 10:56 AM
To: openembedded-devel@lists.openembedded.org
Cc: Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) <schitrod@cisco.com>
Subject: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

As per gnulib_2018-03-07 recipe information, SRCREV = "0d6e3307bbdb8df4d56043d5f373eeeffe4cbef3"
This revision was committed on "2018-12-18".

There is a discrepancy between SRCREV and the recipe version.
Which reports "CVE-2018-17942" as unpatched.

To report "CVE-2018-17942" as patched,
We need to align a recipe name with SRCREV commit date.

Signed-off-by: Sanjay Chitroda <schitrod@cisco.com>
---
 .../gnulib/{gnulib_2018-03-07.03.bb => gnulib_2018-12-18.bb}      | 0
 1 file changed, 0 insertions(+), 0 deletions(-)  rename meta-oe/recipes-support/gnulib/{gnulib_2018-03-07.03.bb => gnulib_2018-12-18.bb} (100%)

diff --git a/meta-oe/recipes-support/gnulib/gnulib_2018-03-07.03.bb b/meta-oe/recipes-support/gnulib/gnulib_2018-12-18.bb
similarity index 100%
rename from meta-oe/recipes-support/gnulib/gnulib_2018-03-07.03.bb
rename to meta-oe/recipes-support/gnulib/gnulib_2018-12-18.bb
--
2.35.6



       reply	other threads:[~2023-05-27  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1760742CFB0AAE9D.26337@lists.openembedded.org>
2023-05-27  3:10 ` Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) [this message]
2023-05-19  5:26 [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18 Sanjay Chitroda
2023-05-30  9:26 ` Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco)
2023-05-30 16:12   ` Khem Raj
2023-05-31 14:58     ` [oe] " akuster808

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=SJ0PR11MB6717215C1B92036799E1AC2EDC449@SJ0PR11MB6717.namprd11.prod.outlook.com \
    --to=schitrod@cisco.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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.