Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Prasanth R <ragaprasanth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Prasanth R <ragaprasanth@gmail.com>
Subject: [PATCH 1/3] recipeutils: fix NameError for recipes with unreliable upstream checks
Date: Sat, 21 Nov 2026 14:38:44 +0900	[thread overview]
Message-ID: <20261121053846.3614417-1-ragaprasanth@gmail.com> (raw)

Since b1d01911fa ("lib/oe/reciputils.py: parallelize upstream version
checks") pn is no longer set in get_recipe_upgrade_status(), so a recipe
with UPSTREAM_CHECK_UNRELIABLE = "1" makes devtool check-upgrade-status
fail with:

  NameError: name 'pn' is not defined

Take the name from the recipe data instead.

AI-Generated: Uses Claude
Signed-off-by: Prasanth R <prasanth.r@lineo.co.jp>
---
 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 522537e0d9..9b3a2d0638 100644
--- a/meta/lib/oe/recipeutils.py
+++ b/meta/lib/oe/recipeutils.py
@@ -1186,7 +1186,7 @@ def get_recipe_upgrade_status(recipes=None, stable_upgrade=False):
 
             unreliable = data.getVar('UPSTREAM_CHECK_UNRELIABLE')
             if unreliable == "1":
-                bb.note(" Skip package %s as upstream check unreliable" % pn)
+                bb.note(" Skip package %s as upstream check unreliable" % data.getVar('PN'))
                 continue
 
             data_copy = bb.data.init()
-- 
2.43.0


             reply	other threads:[~2026-11-21  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21  5:38 Prasanth R [this message]
2026-11-21  5:38 ` [PATCH 2/3] resulttool: fix NameError in filter_resultsdata() Prasanth R
2026-11-21  5:38 ` [PATCH 3/3] oeqa/qemutinyrunner: fix NameError when RUNQEMU_TMPFS_DIR is set Prasanth R

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261121053846.3614417-1-ragaprasanth@gmail.com \
    --to=ragaprasanth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox