linux/meta-cloud-services.git/conf, branch nanbieldMirror of git.yoctoproject.org/meta-cloud-services.githttps://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=nanbield2023-09-11T01:43:21+00:00conf: update compatibility to match oe-core2023-09-11T01:43:21+00:00Bruce Ashfieldbruce.ashfield@gmail.com2023-09-11T01:43:21+00:00urn:sha1:6523dbec44bf1ecea7a7f7cd82249fac251be00f
OE Core has bumped to the next version, we update to match.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: mark layer compatible with mickledore2023-01-04T01:31:28+00:00Bruce Ashfieldbruce.ashfield@gmail.com2023-01-04T01:31:28+00:00urn:sha1:5340b7a40b0d6c99b93af118c5dd8d31f9d74759
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
layer.conf: add meta-virtualization to LAYERDEPENDS2022-12-22T15:34:42+00:00Mingli Yumingli.yu@windriver.com2022-12-12T02:35:20+00:00urn:sha1:b7eaf24eb1e007aad05760771944a5a0d23f78ad
Fix the below yocto compliance issue, the libibverbs under
meta-virtualization provides virtual/libibverbs.
ERROR: Nothing PROVIDES 'virtual/libibverbs' (but /build/layers/meta-cloud-services/recipes-extended/glusterfs/glusterfs_6.1.bb DEPENDS on or otherwise requires it). Close matches:
virtual/libc
virtual/libiconv
virtual/librpc
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'glusterfs', 'virtual/libibverbs']
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
layer.conf: set langdale compatibility2022-09-30T03:09:34+00:00Bruce Ashfieldbruce.ashfield@gmail.com2022-09-30T03:09:34+00:00urn:sha1:77923310b2d3cd97dff12656b3f1a606077aeb06
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: drop honister from compatibility2022-02-22T00:33:14+00:00Bruce Ashfieldbruce.ashfield@gmail.com2022-02-22T00:33:14+00:00urn:sha1:cd822b11ba25d755bee203d87e56ca908a3a4cce
The variable renames in OE core are parse errors, not warnings, so
maintaining compatibility for both honister and kirkstone in the
same branch isn't feasible. So we drop honister in preparation for
release.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: add kirkstone to layer compatibility2022-02-18T14:00:52+00:00Bruce Ashfieldbruce.ashfield@gmail.com2022-02-18T14:00:52+00:00urn:sha1:7398aa81d8eac29a8dd6d7bc3e3067d5090b3b5c
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: set compatibility to honister2021-08-01T03:51:46+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-08-01T03:51:46+00:00urn:sha1:f4b1d9d404af79289f70f3db1ee283bd5abdd523
Now that the overrides have been converted, set compatibity
to honister.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: drop gatesgarth from layer compatibility2021-06-04T12:49:58+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-06-04T12:49:58+00:00urn:sha1:3cf833c11ee776222a41732d5ad7c321904c63ba
The longer compatibility string causes warnings in the layer
index, and we aren't testing against gatesgarth. So we drop
it from our compatbility listing.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: add honister to LAYERSERIES_COMPAT2021-06-04T02:27:55+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-06-04T02:27:55+00:00urn:sha1:186cce60cdc7d09816cbc054ce77239bca1bf61d
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: add hardknott compatibility2021-03-15T15:10:30+00:00Bruce Ashfieldbruce.ashfield@gmail.com2021-03-15T15:10:30+00:00urn:sha1:dd6c4b92a1e4ba9da801237f5e3e667c7d6b78e1
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>