From: Babanpreet Singh <bbnpreetsingh@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Randy MacLeod <randy.macleod@windriver.com>,
Gyorgy Sarvari <skandigraun@gmail.com>,
Chris Laplante <chris.laplante@agilent.com>,
Adrian Freihofer <adrian.freihofer@siemens.com>,
Peter Kjellerstedt <pkj@axis.com>,
Babanpreet Singh <bbnpreetsingh@gmail.com>
Subject: [PATCH 0/2] devtool: fix finish for recipes using AUTOREV
Date: Mon, 13 Jul 2026 06:04:42 +0000 [thread overview]
Message-ID: <20260713060444.7-1-bbnpreetsingh@gmail.com> (raw)
devtool finish (and devtool update-recipe in srcrev mode) crashes with
"fatal: bad revision 'AUTOINC'" on any recipe with SRCREV = "${AUTOREV}",
e.g. one created with devtool add --autorev, because the unresolved
AUTOREV placeholder is passed to git format-patch as the base revision
for exporting patches.
Patch 1 uses the initial revision(s) recorded in the workspace bbappend
instead (as patch mode already does), and stops replacing the AUTOREV
with a pinned revision on finish. Patch 2 adds the oe-selftest case
Randy asked for in the bug; it fails with the exact reported error
before patch 1 and passes after.
While investigating I verified this is not a recent regression: the
same crash reproduces on wrynose, whinlatter, scarthgap and kirkstone,
so it most likely dates back to the introduction of --autorev.
Tested on oe-core master in a qemux86-64 build environment:
- devtool add --autorev + devtool finish: fails before, passes after,
finished recipe keeps SRCREV = "${AUTOREV}"
- devtool add (pinned) + devtool finish: unchanged
- oe-selftest -r devtool.DevtoolAddTests.test_devtool_add_git_autorev_finish
(new): PASSED
- oe-selftest -r devtool.DevtoolUpdateTests.test_devtool_update_recipe_git
devtool.DevtoolUpdateTests.test_devtool_update_recipe_append_git: PASSED
[YOCTO #16354]
Babanpreet Singh (2):
devtool: standard: fix finish/update-recipe for recipes using AUTOREV
oeqa/selftest/devtool: add test for finishing a recipe using AUTOREV
meta/lib/oeqa/selftest/cases/devtool.py | 32 +++++++++++++++++++++++++
scripts/lib/devtool/standard.py | 16 +++++++++++--
2 files changed, 46 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-13 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 6:04 Babanpreet Singh [this message]
2026-07-13 6:04 ` [PATCH 1/2] devtool: standard: fix finish/update-recipe for recipes using AUTOREV Babanpreet Singh
2026-07-13 6:04 ` [PATCH 2/2] oeqa/selftest/devtool: add test for finishing a recipe " Babanpreet Singh
2026-07-13 13:22 ` [OE-core] " Alexander Kanavin
2026-07-14 2:32 ` Babanpreet Singh
2026-07-14 3:20 ` [PATCH v2 1/2] devtool: standard: fix finish/update-recipe for recipes " Babanpreet Singh
2026-07-14 3:20 ` [PATCH v2 2/2] oeqa/selftest/devtool: exercise devtool finish on an AUTOREV recipe Babanpreet Singh
2026-07-14 10:16 ` Alexander Kanavin
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=20260713060444.7-1-bbnpreetsingh@gmail.com \
--to=bbnpreetsingh@gmail.com \
--cc=adrian.freihofer@siemens.com \
--cc=chris.laplante@agilent.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pkj@axis.com \
--cc=randy.macleod@windriver.com \
--cc=skandigraun@gmail.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