linux/poky.git/meta/lib/oe/recipeutils.py, branch kirkstone-next

recipeutils: Add missing get_srcrev() call

2022-02-18T11:37:34+00:00

Updates within bitbake now require this call to be triggered somewhere with floating git source revs. Add the missing call. Issue can be reproduced with: devtool check-upgrade-status dbus-wait (From OE-Core rev: d7088b2b5012f9e386914a6837685f5869379cc5) Signed-off-by: Richard Purdie

meta: Manual override fixes

2021-08-02T14:44:10+00:00

The automated conversion of OE-Core to use the new override sytax isn't perfect. This patches some mis-converted lines and some lines which were missed by the automation. (From OE-Core rev: 4e9a06b64b43131b731fb59a0305f78a98e27fbd) Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

oe/recipeutils: Fix copying patches when BBLAYERS entries are not normalised

2021-02-19T11:17:11+00:00

`devtool` uses `copy_recipe_files` for the upgrade operation when creating the new, workspace recipe. Before handling the copy operations, the function checks the entry in `SRC_URI` against `FILE` while in turn uses absolute paths. When BBLAYERS contains entries that are not normalised, this check will fail resulting in having the recipe in the workspace without the initial patches. Signef-off-by: Robert Drab (From OE-Core rev: 777fc24ab2c332954b56dac28cd9b3032808828c) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

lib/oe/recipeutils.py: add support for BBFILES_DYNAMIC

2020-08-27T07:28:03+00:00

Instead of relying on value of BBFILES from bitbake, devtool parses the layer.conf because the layer might not be in bblayers.conf. And it currently does not consider the value of BBFILES_DYNAMIC because of which recipes, in paths defined by BBFILES_DYNAMIC, upgraded using devtool end up in wrong location. Include the code from bitbake to append values to BBFILES based on what is in BBFILES_DYNAMIC too. (From OE-Core rev: c7bbb98ea8ccd3568dd8bded6e404e2f781e6841) Signed-off-by: Naveen Saini Signed-off-by: Richard Purdie

lib/oe/recipeutils.py: add AUTHOR; BBCLASSEXTEND

2020-07-12T21:39:41+00:00

If you try to create a plugin for recipetool that adds the AUTHOR field, it is impossible to put it in the recommended position [1] without adding to the recipe_progression variable. While we are at it, also add BBCLASSEXTEND at the end, as also recommended by [1]. [1] http://www.openembedded.org/wiki/Styleguide (From OE-Core rev: d687c5b7b10b3decdd80d5c2fd61072a87f061f2) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

lib/oe/recipeutils.py: passthrough of FETCHCMD

2020-05-19T21:57:26+00:00

let FETCHCMD_* settings be passed to upstream check functions from get_recipe_upgrade_status. It enables using different values for the fetching tools, as otherwise always the defaults are used. E.g. use different timeout or retry values for wget. This is especially useful for remote server that do request-limiting (429) or that are simply unavailable (500, 504) and can speedup upgrade-check for a larger set of recipe significantly (From OE-Core rev: f69347744241afea19f155d9ff5115c675e9043d) Signed-off-by: Konrad Weihmann Signed-off-by: Richard Purdie

oe/recipeutils: Drop obsolete GITDIR reference

2020-03-29T11:05:31+00:00

The fetcher GITDIR variable wase dropped a while back, drop the obsolete reference to it (thanks Robert Day). (From OE-Core rev: de035e687e26cef96e9b737c47bfc291bdfbea48) Signed-off-by: Richard Purdie

recipeutils: set SRCPV for devupstream variant

2019-12-28T23:25:42+00:00

Otherwise bitbake is unable to expand it if the main variant is not using a SCM fetcher. (From OE-Core rev: 24e59094de42b4b0bed3584ca8571c4c19080428) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

lib/oe/reciputils.py: support character `+' in git pv

2019-06-04T08:09:42+00:00

While pv contains char `+' (such as ncurses 6.1+20181013), it was incorrectly converted to `6.1' In this commit: - Convert [^\+]* to .*? Support pv to contain char `+' and not greedy match (Such as ncurses 6.1+20181013) - Add [^\+] to sfx match Support sfx contains extra chars between `+' and `git' (such as asciidoc "8.6.9+py3-gitAUTOINC+618f6e6f6b") - Make sfx and rev greedy match Run `devtool check-upgrade-status --all' in poky and compare results, only one difference on ncurses version: Without the commit: INFO: ncurses 6.1 6.1+20181013 Hongxu Jia 7a97a7f937762ba342d5b2fd7cd090885a809835 With the commit: INFO: ncurses 6.1+20181013 MATCH Hongxu Jia 7a97a7f937762ba342d5b2fd7cd090885a809835 (From OE-Core rev: 8049bd34b89e710f7bb20883813ba3f929d9e997) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie