[oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[Nishanth Menon]

Hi,

Series of patches to get ourselves synced with the latest
dunfell to pick up fixes from upstream - esp around thinprovisioning and
dropping our internal version of the fix for mariadb.

This brings arago-config and arago-next-config both in sync with latest
dunfell and dunfell-next tips appropriately.

This series obviously will need to be followed up at an appropriate time
with a stable commit sha patch to pin things up.

Nishanth Menon (2):
  Revert "arago-dunfell-next: Temporarily redirect meta-openembedded"
  Revert "arago-dunfell: Pin all layers to last known good build SHA"

 configs/arago-dunfell-config.txt      | 8 ++++----
 configs/arago-dunfell-next-config.txt | 3 +--
 2 files changed, 5 insertions(+), 6 deletions(-)

-- 
2.25.1.377.g2d2118b814c1

[oe-layersetup][PATCH 1/2] Revert "arago-dunfell-next: Temporarily redirect meta-openembedded"

[Nishanth Menon]

This reverts commit 99f72a0bd64e3f7e0d395a0bb5c26017d745a185.

MariaDB issue has been resolved in upstream, no need to use a TI private
repository for build.

Signed-off-by: Nishanth Menon <nm@ti.com>
---
 configs/arago-dunfell-next-config.txt | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/configs/arago-dunfell-next-config.txt b/configs/arago-dunfell-next-config.txt
index 14e6fa8c9d6a..8d629c4bf42d 100644
--- a/configs/arago-dunfell-next-config.txt
+++ b/configs/arago-dunfell-next-config.txt
@@ -6,8 +6,7 @@ meta-arago,git://arago-project.org/git/meta-arago.git,dunfell-next,HEAD,layers=m
 #meta-browser,git://github.com/OSSystems/meta-browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
 meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,HEAD,layers=
 meta-virtualization,git://git.yoctoproject.org/meta-virtualization,dunfell,HEAD,layers=
-#meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
-meta-openembedded,ssh://git@bitbucket.itg.ti.com/coresdk_pub/meta-openembedded.git,dunfell,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
+meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
 meta-ti,git://git.yoctoproject.org/meta-ti,dunfell-next,HEAD,layers=
 meta-arm,git://git.yoctoproject.org/meta-arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-arm:meta-arm-toolchain
 oe-core,git://git.openembedded.org/openembedded-core,dunfell,HEAD,layers=meta
-- 
2.25.1.377.g2d2118b814c1

[oe-layersetup][PATCH 2/2] Revert "arago-dunfell: Pin all layers to last known good build SHA"

[Nishanth Menon]

This reverts commit 3e3b838e5cee047251fa97842509de70d1d5b42f.

Now that we dont have an issue with upstream dunfell, switch to bleeding
edge of dunfell

Signed-off-by: Nishanth Menon <nm@ti.com>
---
 configs/arago-dunfell-config.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/configs/arago-dunfell-config.txt b/configs/arago-dunfell-config.txt
index b82c0d79f306..b45ee3e026df 100644
--- a/configs/arago-dunfell-config.txt
+++ b/configs/arago-dunfell-config.txt
@@ -4,11 +4,11 @@
 bitbake,git://git.openembedded.org/bitbake,1.46,HEAD
 meta-arago,git://arago-project.org/git/meta-arago.git,dunfell,HEAD,layers=meta-arago-distro:meta-arago-extras
 #meta-browser,git://github.com/OSSystems/meta-browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
-meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,0d8eb956015acdea7e77cd6672d08dce18061510,layers=
-meta-virtualization,git://git.yoctoproject.org/meta-virtualization,dunfell,92cd3467502bd27b98a76862ca6525ce425a8479,layers=
-meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,f2d02cb71eaff8eb285a1997b30be52486c160ae,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
+meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,HEAD,layers=
+meta-virtualization,git://git.yoctoproject.org/meta-virtualization,dunfell,HEAD,layers=
+meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
 meta-ti,git://git.yoctoproject.org/meta-ti,dunfell,HEAD,layers=
 meta-arm,git://git.yoctoproject.org/meta-arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-arm:meta-arm-toolchain
-oe-core,git://git.openembedded.org/openembedded-core,dunfell,72431ee8de5e3a53d259cebf420a7713ac9e1f14,layers=meta
+oe-core,git://git.openembedded.org/openembedded-core,dunfell,HEAD,layers=meta
 OECORELAYERCONF=./sample-files/bblayers.conf.sample
 OECORELOCALCONF=./sample-files/local-arago64.conf.sample
-- 
2.25.1.377.g2d2118b814c1

Re: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[Nishanth Menon]

On 12:08-20210316, Nishanth Menon wrote:

I have no idea what ate up my $subject -> I intended to add "Move to
dunfell/dunfell-tip from upstream.

> 
> This brings arago-config and arago-next-config both in sync with latest
> dunfell and dunfell-next tips appropriately.
> 
> This series obviously will need to be followed up at an appropriate time
> with a stable commit sha patch to pin things up.

K, I might be missing the motivation here - the pinning may not be
required given that dunfell is always a rolling config.. and used only
in the cases of exceptions.. So, please ignore my comment.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Re: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[Denys Dmytriyenko]

On Tue, Mar 16, 2021 at 12:18:01PM -0500, Nishanth Menon wrote:
> On 12:08-20210316, Nishanth Menon wrote:
> 
> I have no idea what ate up my $subject -> I intended to add "Move to
> dunfell/dunfell-tip from upstream.
> 
> > 
> > This brings arago-config and arago-next-config both in sync with latest
> > dunfell and dunfell-next tips appropriately.
> > 
> > This series obviously will need to be followed up at an appropriate time
> > with a stable commit sha patch to pin things up.
> 
> K, I might be missing the motivation here - the pinning may not be
> required given that dunfell is always a rolling config.. and used only
> in the cases of exceptions.. So, please ignore my comment.

Looks good to me.

Praneeth, I see you only merged one of two patches?

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

Re: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[Bajjuri, Praneeth]

On 3/16/2021 1:45 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 16, 2021 at 12:18:01PM -0500, Nishanth Menon wrote:
>> On 12:08-20210316, Nishanth Menon wrote:
>>
>> I have no idea what ate up my $subject -> I intended to add "Move to
>> dunfell/dunfell-tip from upstream.
>>
>>>
>>> This brings arago-config and arago-next-config both in sync with latest
>>> dunfell and dunfell-next tips appropriately.
>>>
>>> This series obviously will need to be followed up at an appropriate time
>>> with a stable commit sha patch to pin things up.
>>
>> K, I might be missing the motivation here - the pinning may not be
>> required given that dunfell is always a rolling config.. and used only
>> in the cases of exceptions.. So, please ignore my comment.
> 
> Looks good to me.
> 
> Praneeth, I see you only merged one of two patches?

Yes , only pulled the dunfell-next config .. started the build job to 
check if builds are ok. Will pull the dunfell patch in couple of hrs.


> 

Re: [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to

[Denys Dmytriyenko]

On Tue, Mar 16, 2021 at 02:13:09PM -0500, Bajjuri, Praneeth wrote:
> 
> 
> On 3/16/2021 1:45 PM, Denys Dmytriyenko wrote:
> >On Tue, Mar 16, 2021 at 12:18:01PM -0500, Nishanth Menon wrote:
> >>On 12:08-20210316, Nishanth Menon wrote:
> >>
> >>I have no idea what ate up my $subject -> I intended to add "Move to
> >>dunfell/dunfell-tip from upstream.
> >>
> >>>
> >>>This brings arago-config and arago-next-config both in sync with latest
> >>>dunfell and dunfell-next tips appropriately.
> >>>
> >>>This series obviously will need to be followed up at an appropriate time
> >>>with a stable commit sha patch to pin things up.
> >>
> >>K, I might be missing the motivation here - the pinning may not be
> >>required given that dunfell is always a rolling config.. and used only
> >>in the cases of exceptions.. So, please ignore my comment.
> >
> >Looks good to me.
> >
> >Praneeth, I see you only merged one of two patches?
> 
> Yes , only pulled the dunfell-next config .. started the build job
> to check if builds are ok. Will pull the dunfell patch in couple of
> hrs.

Ok, thanks.