[PATCH] CI: use bitbake+oe-core instead of poky

Moving forwads, it's expected that the poky repository will no longer be
updated as the integration of bitbake-setup means that users are
encouraged to use bitbake+oe-core separately instead.

We also need to fetch meta-yocto as our CI is currently explicitly based
on the poky distribution.

This is effectively a no-op change, as poky is simply these component
repositories glued into a single repository for convenience.

Signed-off-by: Ross Burton <[email protected]>
---
 ci/base.yml         | 21 +++++++++++++++------
 ci/genericarm64.yml |  2 +-
 2 files changed, 16 insertions(+), 7 deletions(-)

diff --git a/ci/base.yml b/ci/base.yml
index d89533901c..87192fba26 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -10,18 +10,27 @@ defaults:
     branch: master
 
 repos:
+  bitbake:
+    url: https://git.openembedded.org/bitbake
+    layers:
+      bitbake: disabled
+
+  core:
+    url: https://git.openembedded.org/openembedded-core
+    layers:
+      meta:
+
+  meta-yocto:
+    url: https://git.yoctoproject.org/meta-yocto
+    layers:
+      meta-poky:
+
   meta-arm:
     layers:
       meta-arm:
       meta-arm-bsp:
       meta-arm-toolchain:
 
-  poky:
-    url: https://git.yoctoproject.org/poky
-    layers:
-      meta:
-      meta-poky:
-
 env:
   BB_LOGCONFIG: ""
   TOOLCHAIN_DIR: ""
diff --git a/ci/genericarm64.yml b/ci/genericarm64.yml
index 2fbe766f70..48818fb19c 100644
--- a/ci/genericarm64.yml
+++ b/ci/genericarm64.yml
@@ -6,7 +6,7 @@ header:
     - ci/base.yml
 
 repos:
-  poky:
+  meta-yocto:
     layers:
       meta-yocto-bsp:
 
-- 
2.43.0