Re: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

2023-05-31 Thread Armin Kuster
On 5/30/23 12:12 PM, Khem Raj wrote: On Tue, May 30, 2023 at 2:27 AM Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) wrote: Hi all, Any update/comment ? @raj.k...@gmail.com can you please guide me on how to procced further ? the master branch has gnulib_2018-12-18.

Re: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

2023-05-30 Thread Khem Raj
On Tue, May 30, 2023 at 2:27 AM Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) wrote: > > Hi all, > > Any update/comment ? > @raj.k...@gmail.com can you please guide me on how to procced further ? > the master branch has gnulib_2018-12-18.bb so this patch is not for mast

Re: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

2023-05-30 Thread Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) via lists.openembedded.org
Hi all, Any update/comment ? @raj.k...@gmail.com can you please guide me on how to procced further ? Thanks, Sanjay -Original Message- From: Sanjay Chitroda Sent: Friday, May 19, 2023 10:56 AM To: openembedded-devel@lists.openembedded.org Cc: Sanjaykumar kantibhai Chitroda -X (schitrod

Re: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

2023-05-26 Thread Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) via lists.openembedded.org
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) Subject: [oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18 As per gnulib_2018-03-07 recipe information, SRCREV

[oe] [meta-oe][PATCH] gnulib: Update recipe name to 2018-12-18

2023-05-18 Thread Sanjaykumar kantibhai Chitroda -X (schitrod - E-INFO CHIPS INC at Cisco) via lists.openembedded.org
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 t