From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com, Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v1 01/11] meta: change deprecated parse calls
Date: Tue, 21 Jun 2022 16:38:46 +0300 [thread overview]
Message-ID: <20220621133856.4673-2-amikan@ilbers.de> (raw)
In-Reply-To: <20220621133856.4673-1-amikan@ilbers.de>
Function vars_from_file was moved from bb.parse.BBHandler to bb.parse by
https://git.openembedded.org/bitbake/commit/?id=fda0707d772e0964a0185d4ec4d016522f6972f3
It was still left for compatibility and marked as deprecated, but will be
removed in Barebox 1.52 version. So change all the calls to correct ones for
the future Barebox update.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/conf/bitbake.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 20a218f..e55e49b 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -30,9 +30,9 @@ DEBDIR = "${DL_DIR}/deb"
DEBSRCDIR = "${DL_DIR}/deb-src"
P = "${PN}-${PV}"
PF = "${PN}-${PV}-${PR}"
-PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[0] or 'defaultpkgname'}"
-PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[1] or '1.0'}"
-PR = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[2] or 'r0'}"
+PN = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[0] or 'defaultpkgname'}"
+PV = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[1] or '1.0'}"
+PR = "${@bb.parse.vars_from_file(d.getVar('FILE', False),d)[2] or 'r0'}"
PROVIDES = ""
S = "${WORKDIR}/${P}"
AUTOREV = "${@bb.fetch2.get_autorev(d)}"
--
2.17.1
next prev parent reply other threads:[~2022-06-21 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:38 [PATCH v1 00/11] Migrate to Bitbake 2.0 Anton Mikanovich
2022-06-21 13:38 ` Anton Mikanovich [this message]
2022-06-21 13:38 ` [PATCH v1 02/11] scripts/contrib: Add override conversion script Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 03/11] scripts/contrib: configure " Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 04/11] dpkg-base: fix conflicting variable names Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 05/11] meta-isar: set default branch names Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 06/11] meta: remove non recommended syntax Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 07/11] bitbake: Update to Bitbake 2.0.1 Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 08/11] doc: require zstd tool Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 09/11] meta: update bitbake variables Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 10/11] meta: mark network access required tasks Anton Mikanovich
2022-06-21 13:38 ` [PATCH v1 11/11] meta: update overrides syntax Anton Mikanovich
2022-06-21 14:49 ` [PATCH v1 00/11] Migrate to Bitbake 2.0 Schmidt, Adriaan
2022-06-21 15:07 ` Anton Mikanovich
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=20220621133856.4673-2-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.com \
/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