Skip to contentSkip to conversation

lib/oe/recipeutils: make stable_upgrade argument optional in get_recipe_upstream_version()

PATCH New Ross Burton 1 participant 1 message Jun 8

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 lib/oe/recipeutils: make stable_upgrade argument optional in get_recipe_upstream_version()

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")

---
 meta/lib/oe/recipeutils.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/lib/oe/recipeutils.py +1 -1
index 7c1df518a8d..64bf2f950f8 100644
@@ -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.
Signature · 1 line
2.43.0