The change[1] that added the stable_upgrade argument made it optional
for the high-level get_recipe_upgrade_status() function, but not
get_recipe_upstream_version().
This function is exposed API so be kind to users and also make it an
optional argument there.
[1] oe-core 1ed8fdda035 ("recipeutils: add optional stable_upgrade parameter to
get_recipe_upgrade_status")
Signed-off-by: Ross Burton <[email protected]>
---
meta/lib/oe/recipeutils.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oe/recipeutils.py b/meta/lib/oe/recipeutils.py
index 7c1df518a8d..64bf2f950f8 100644
--- a/meta/lib/oe/recipeutils.py
+++ b/meta/lib/oe/recipeutils.py
@@ -1009,7 +1009,7 @@ def get_recipe_pv_with_pfx_sfx(pv, uri_type):
return (pv, pfx, sfx)
-def get_recipe_upstream_version(rd, stable_upgrade):
+def get_recipe_upstream_version(rd, stable_upgrade=False):
"""
Get upstream version of recipe using bb.fetch2 methods with support for
http, https, ftp and git.
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#238231):
https://lists.openembedded.org/g/openembedded-core/message/238231
Mute This Topic: https://lists.openembedded.org/mt/119703634/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
