From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6861966532913659904 Date: Mon, 5 Oct 2020 10:01:14 -0700 (PDT) From: "vijaikumar....@gmail.com" To: isar-users Message-Id: <8ab38825-8d9e-4b2a-91eb-f37084e9644en@googlegroups.com> In-Reply-To: References: <20200817160009.16462-1-Vijaikumar_Kanagarajan@mentor.com> <20200819213540.543b6bbe@md1za8fc.ad001.siemens.net> Subject: Re: [PATCH v2] bitbake: Update to 1.46.2 release MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_66_1111131346.1601917274207" X-TUID: LE7g3WHawUHL ------=_Part_66_1111131346.1601917274207 Content-Type: multipart/alternative; boundary="----=_Part_67_2038447576.1601917274207" ------=_Part_67_2038447576.1601917274207 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Can this be merged? On Thursday, August 20, 2020 at 2:18:15 AM UTC+5:30 vijaikumar....@gmail.com wrote: > Hi Henning, > > On Thu, Aug 20, 2020 at 1:05 AM Henning Schild > wrote: > > > > The mail is almost too big to handle, maybe use a cover letter for > > potential future discussions leaving the big path in a mail nobody > > needs to really look into. > > Sure. Will take care of it in future. > > > > > It is always a good idea to stay up to date with upstream, but maybe > > you have a reason on why you would like to see the bump. Last time we > > updated bitbake we inherited some issues around git submodules. And > > with the long due update of wic we are drifting apart and risk breaking > > wic. > > Any reason is fine, but if we get issues we need to know how to deal > > with them. Maybe if a revert would be ok because the bump was more > > cosmetic than technically needed. > > I started the work on wic update with a quick bitbake update. > Later I found no technical need for the same. But the effort was already > put and > it made sense to complete it. Hence this upstreaming. > > CI-build: http://ci.isar-build.org:8080/job/isar_vkk_devel/70/ > > WIC update is in works. And I don't(yet) see it breaking with the > latest or the older version of > ISAR's bitbake. Will try to send the patches soon. > > Thanks, > Vijai Kumar K > > > > > Henning > > > > Am Mon, 17 Aug 2020 21:30:09 +0530 > > schrieb Vijai Kumar K : > > > > > Update bitbake to the latest 1.46.2 release. > > > This release is tagged to the below upstream commit ID: > > > cc11dfa4eb3616547a8a3909f89da0cc4f35dc57 > > > > > > The version in bin/bitbake is not updated to 1.46.2 and still shows > > > 1.46.0. Please use the above commit ID to validate it is indeed > > > 1.46.2 release. > > > > > > Signed-off-by: Vijai Kumar K > ------=_Part_67_2038447576.1601917274207 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Can this be merged?  

On Thursday, August 20, 2020 at 2:18:15 AM UTC+5:30 vijaikumar....@gmail.com wrote:
Hi Henning,

On Thu, Aug 20, 2020 at 1:05 AM Henning Schild
<henning...@siemens.com> wrote:
>
> The mail is almost too big to handle, maybe use a cover letter for
> potential future discussions leaving the big path in a mail nobody
> needs to really look into.

Sure. Will take care of it in future.

>
> It is always a good idea to stay up to date with upstream, but maybe
> you have a reason on why you would like to see the bump. Last time we
> updated bitbake we inherited some issues around git submodules. And
> with the long due update of wic we are drifting apart and risk breaking
> wic.
> Any reason is fine, but if we get issues we need to know how to deal
> with them. Maybe if a revert would be ok because the bump was more
> cosmetic than technically needed.

I started the work on wic update with a quick bitbake update.
Later I found no technical need for the same. But the effort was already put and
it made sense to complete it. Hence this upstreaming.

CI-build: http://ci.isar-build.org:8080/job/isar_vkk_devel/70/

WIC update is in works. And I don't(yet) see it breaking with the
latest or the older version of
ISAR's bitbake. Will try to send the patches soon.

Thanks,
Vijai Kumar K

>
> Henning
>
> Am Mon, 17 Aug 2020 21:30:09 +0530
> schrieb Vijai Kumar K <Vijaikumar_...@mentor.com>:
>
> > Update bitbake to the latest 1.46.2 release.
> > This release is tagged to the below upstream commit ID:
> > cc11dfa4eb3616547a8a3909f89da0cc4f35dc57
> >
> > The version in bin/bitbake is not updated to 1.46.2 and still shows
> > 1.46.0. Please use the above commit ID to validate it is indeed
> > 1.46.2 release.
> >
> > Signed-off-by: Vijai Kumar K <Vijaikumar_...@mentor.com>
------=_Part_67_2038447576.1601917274207-- ------=_Part_66_1111131346.1601917274207--