From 3701bc4d30526c52be1e1789afb24c90a23beab6 Mon Sep 17 00:00:00 2001 From: Tim Orling Date: Tue, 28 Nov 2023 20:11:36 -0800 Subject: [PATCH] python3-cryptography-vectors: add RECIPE_NO_UPDATE_REASON Comments in the recipe are insufficient to prevent folks from attempting to upgrade the recipe without also upgrading python3-cryptography. These two recipes MUST be upgraded in lock step to the exact same version. Signed-off-by: Tim Orling Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie --- .../python/python3-cryptography-vectors_41.0.5.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.5.bb b/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.5.bb index 44c67fdd76b..e304c4261a2 100644 --- a/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.5.bb +++ b/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.5.bb @@ -27,3 +27,5 @@ do_install:append () { BBCLASSEXTEND = "native nativesdk" UPSTREAM_CHECK_REGEX = "" + +RECIPE_NO_UPDATE_REASON = "Must be updated in sync with python3-cryptography." -- 2.47.3