Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=3.5_M1 2021-12-04T23:39:52+00:00 2021-12-04T23:39:52+00:00 Joshua Watt JPEWhacker@gmail.com 2021-12-04T20:01:29+00:00 urn:sha1:467c21abe432aab8cf985fcad917d9728052f5e9 Relaxes the case requirements for checks in the README file so that word like "Maintainer" and "Patch" are allowed (From OE-Core rev: fdedf94d406ad3da85cb45d43ef87d3fdc8c14d4) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-12-04T23:39:52+00:00 Jon Mason jdmason@kudzu.us 2021-12-04T18:18:09+00:00 urn:sha1:17d1c837a4ea98a6a83d88679cdcc168bb3ee427 It is permissible to have a layer's README reference another README. If this is the case, avoid other checks. Do this by checking for the word README (case insensitive) in the README file. This might be too permissive, but follows the pattern of looking for exact words (like "patch" or "maintainer") in READMEs. (From OE-Core rev: 443c73d638519d6a7ea44d1c0e80d76306687ddc) Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-12-03T23:37:16+00:00 Dhruva Gole goledhruva@gmail.com 2021-11-30T05:43:35+00:00 urn:sha1:aec629185efe563c361844049b1009bc99a4f4fc This adds: - Test case to review if the README file specifies the maintainer. - Test case to review if the README file specifies the word patch. - Test case to review if the README file contains an email address. [YOCTO #11131] (From OE-Core rev: 5d4937bce191b7e22b807c0595d4845c88ecc560) Signed-off-by: Dhruva Gole <goledhruva@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-12-01T16:23:45+00:00 Dhruva Gole goledhruva@gmail.com 2021-11-28T17:38:08+00:00 urn:sha1:95de7e2b62527f10f6dc9e9b79b12161969bc67a (From OE-Core rev: 8ea17456ae5318ed7a3b4c8f75c8441456d8b979) Signed-off-by: Dhruva Gole <goledhruva@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-07-28T22:47:00+00:00 Nicolas Dechesne nicolas.dechesne@linaro.org 2021-07-22T12:46:43+00:00 urn:sha1:8dbef94dce59c70c5904e418647eae6a4365163c What this function does is really to find a layer, not a 'depends'. We are using this function to find a dependent layer, but the name is confusing. (From OE-Core rev: e9b7690ab30d0e7c07471034f6cb89ccc3168a11) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-07-28T22:47:00+00:00 Nicolas Dechesne nicolas.dechesne@linaro.org 2021-07-22T12:46:42+00:00 urn:sha1:4f452a8be1088ba4bf5da79059de375e3f9ae7c0 Split add_layer_dependencies() into 2 parts. First search for layer dependencies, and then add them to the config. That allows us to call get_layer_dependencies() independently. (From OE-Core rev: 08edf928aac3f2daaa0c256d4c21e56e2db72bff) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-07-27T09:37:58+00:00 Lee Chee Yang chee.yang.lee@intel.com 2020-07-24T04:16:24+00:00 urn:sha1:4cbea1019781e9595655448347a38dae1db5ee29 layer under test should absent from BBLAYERS when running yocto-check-layer. This allow to get signatures before layer under test. There are existing steps to add the layer under test to BBLAYERS after getting initial signatures. add steps to check for layer under test in BBLAYERS before running any test, skip test for the layer if the layer under test exist in BBLAYERS. [YOCTO #13176] (From OE-Core rev: be02e8dbfb0d1decce125322f9f1e11a649756c0) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-06-28T07:36:00+00:00 Nicolas Dechesne nicolas.dechesne@linaro.org 2020-06-26T12:29:30+00:00 urn:sha1:c0a16eaae08edaa21c551947726b189a1afec1ae LAYERDEPENDS is a string of this format: "DEPEND1 (optional version) DEPEND2 (optional version) ..." However when we parse LAYERDEPENDS in _get_layer_collections() we parse it as a simple string, and if any optional versions are there the 'depends' field is wrong. For example, running yocto-check-layer might result in such errors: ERROR: Layer meta-python depends on (>= and isn't found. ERROR: Layer meta-python depends on 12) and isn't found. Let's use bb.utils.explode_dep_versions2() to parse LAYERDEPENDS, and create a string that contains all dependencies, effectively skipping/ignoring any optional versions. [YOCTO #13957] (From OE-Core rev: f81f07afc200fe06c5c06ea81a4f8a3a43436faf) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-05-24T22:56:03+00:00 Joshua Watt JPEWhacker@gmail.com 2020-05-22T22:08:26+00:00 urn:sha1:57daea00de5676315c99c6791f6dfbd6957989d3 As in other places in the file, skip layers that don't define a collection when searching for a layer to resolve a dependency. Fixes KeyError exceptions when attempting to access the layer collections later (From OE-Core rev: 26090a2861ebe21224aaf89d7be0c0a89ca58e48) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-08-30T16:10:28+00:00 Mark Hatle mark.hatle@windriver.com 2019-08-28T18:22:46+00:00 urn:sha1:b4932a18ab76c8b671f22ca8ad528049f0dd30b4 It's become more commone for files to be named "readme" or "Readme" on github servers in recent time. So adjust the scanning to allow any mix of case. (From OE-Core rev: afe46eca15b6ddfa15c75cb7b707d6dd9aae3eae) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>