All of lore.kernel.org
 help / color / mirror / Atom feed
From: shibi.cbe@gmail.com
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch2/cooker: Fix source revision handling with floating upstreams
Date: Tue, 20 Sep 2022 01:18:26 -0700	[thread overview]
Message-ID: <18843.1663661906268649916@lists.openembedded.org> (raw)
In-Reply-To: <20220210175426.2695614-1-richard.purdie@linuxfoundation.org>

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

Hello  Richard Purdie

Above patch in lib/bb/fetch2/git.py fails "devtool modify" for the recipe which uses ${AUTOREV}

Raised a topic on the same(below URL).

https://lists.openembedded.org/g/Openembedded-issues/topic/devtool_fails_if_srcrev_is/93705955?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,93705955,previd%3D1663264030971523351,nextid%3D1298300470000000000&previd=1663264030971523351&nextid=1298300470000000000

Not expert in complete workflow. To verify it set __BBSEENSRCREV as 1 above your patch( which is totally wrong this is just to check if its the issue). It actually works as expected

d.setVar('__BBSEENSRCREV', '1')

if not d.getVar("__BBSEENSRCREV"):

raise bb.fetch2.FetchError("Recipe uses a floating tag/branch without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE).")

Just want to understand how __BBSEENSRCREV is set. is it possible to set this variable/ignore this check for devtool operations

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

      parent reply	other threads:[~2022-09-20  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 17:54 [PATCH] fetch2/cooker: Fix source revision handling with floating upstreams Richard Purdie
2022-02-13 22:13 ` [bitbake-devel] " Peter Kjellerstedt
     [not found]   ` <8229aa5ea01b346aa9c2519c7c46883e4c06b48b.camel@linuxfoundation.org>
2022-02-18  7:44     ` Alexander Kanavin
2022-02-18 10:59       ` Richard Purdie
2022-02-18 11:10         ` Alexander Kanavin
2022-09-20  8:18 ` shibi.cbe [this message]

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=18843.1663661906268649916@lists.openembedded.org \
    --to=shibi.cbe@gmail.com \
    --cc=bitbake-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.