Yocto Project Discussions
 help / color / mirror / Atom feed
From: acox@reliablecontrols.com
To: yocto@lists.yoctoproject.org
Subject: Re: Devtool fails if SRCREV is set to ${AUTOREV} #kirkstone #devtool #yocto
Date: Fri, 26 Aug 2022 13:38:22 -0700	[thread overview]
Message-ID: <3684.1661546302833449840@lists.yoctoproject.org> (raw)
In-Reply-To: <xSB7.1660818745077819917.g6sG@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

I'm having the exact same issue when just modifying a custom linux recipie which is essntially the same as the one provided but referencing 5.15 after transposing recipies from dunfell to kirkstone. The builds without any devtool modify sources work fine but the second I am working with a devtool'd linux it produces that error. So the current best workflow seems to be to make changes in a branch on the remote repository which will require forking the kernel sources and then pointing the branch at the branch created on the fork of the repository.

In my naieve attempts to troubleshoot this I tried changing SRCREV to the same branch name I was referencing and changed the error message to the new format where it changes the raise line to the following it seemed to be using SRCREV for ud.unresolvedrev[name], that doesn't seem correct to me as if I changed the SRCREV to "5.15" (different from the git branch) it would output "5.15". Not sure if this is expected.

raise bb.fetch2.FetchError("Recipe uses a floating tag/branch '%s' for repo '%s' without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE)." % (ud.unresolvedrev[name], ud.host+ud.path))

^ https://git.yoctoproject.org/poky/plain/bitbake/lib/bb/fetch2/git.py

[-- Attachment #2: Type: text/html, Size: 1298 bytes --]

  reply	other threads:[~2022-08-26 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 10:32 Devtool fails if SRCREV is set to ${AUTOREV} #kirkstone #devtool #yocto shibi.cbe
2022-08-26 20:38 ` acox [this message]
2023-07-11 21:54   ` Tom Isaacson
2023-07-12 17:03     ` [yocto] " Alexander Kanavin
2023-07-12 17:43       ` Tom Isaacson
2023-07-12 17:55         ` Alexander Kanavin
2023-11-08 16:28           ` Chris Wyse
2023-11-08 22:59             ` [yocto] " Yoann Congal

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=3684.1661546302833449840@lists.yoctoproject.org \
    --to=acox@reliablecontrols.com \
    --cc=yocto@lists.yoctoproject.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