public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] meta/conf/bitbake.conf: enable SRCPV support for AUTOREV
Date: Thu, 13 Apr 2023 12:39:09 +0530	[thread overview]
Message-ID: <CAB2Z2nM3yyd9VjU1mWsVB4gZDhqPazttOmS+i7A-xmp8kjchXQ@mail.gmail.com> (raw)
In-Reply-To: <1e8a8cb1-68e6-be14-0d42-13a8a5ff1dea@siemens.com>

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

On Thu, Apr 13, 2023 at 12:32 PM 'Jan Kiszka' via isar-users <
isar-users@googlegroups.com> wrote:

> On 12.04.23 12:17, Srinuvasan Arjunan wrote:
> > From: Srinuvasan A <srinuvasan_a@mentor.com>
> >
> > One of our downstream project recipe uses `SRCREV = "${AUTOREV}"` to get
> > the latest changes always, but this not works after bitbake 2 migration,
> > it throws the below error.
> >
> > do_fetch: Fetcher failure: Recipe uses a floating tag/branch without a
> fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for
> OE).
> >
> > Till now we don't have support for SRCPV in ISAR, hence add this support
> > as like OE.
> >
> > Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
> > ---
> >  meta/classes/base.bbclass | 2 ++
> >  meta/conf/bitbake.conf    | 4 ++++
> >  2 files changed, 6 insertions(+)
> >
> > diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> > index 53550ae..cc2b195 100644
> > --- a/meta/classes/base.bbclass
> > +++ b/meta/classes/base.bbclass
> > @@ -120,6 +120,8 @@ root_cleandirs() {
> >  python() {
> >      import re
> >
> > +    d.setVar("SRCPV", "${@bb.fetch2.get_srcrev(d)}")
> > +
>
> This is likely not correct. OE upstream checks if there is any SCM in
> the SRC_URI entries and only then adds this. I've played with
> unconditionally adding SRCPV (though via bitbake.conf), and I got errors.
>
> Jan
>

    Sure jan, will check and send the next version.

>
> >      for e in d.keys():
> >          flags = d.getVarFlags(e)
> >          if flags and flags.get('task'):
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index f421050..124bf49 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -36,6 +36,10 @@ PR = "${@bb.parse.vars_from_file(d.getVar('FILE',
> False),d)[2] or 'r0'}"
> >  PROVIDES = ""
> >  S = "${WORKDIR}/${P}"
> >  AUTOREV = "${@bb.fetch2.get_autorev(d)}"
> > +AUTOREV[vardepvalue] = "${SRCPV}"
> > +# Set Dynamically in base.bbclass
> > +# SRCPV = "${@bb.fetch2.get_srcrev(d)}"
> > +SRCPV[vardepvalue] = "${SRCPV}"
> >  SRC_URI = ""
> >  STAMPS_DIR ?= "${TMPDIR}/stamps"
> >  STAMP = "${STAMPS_DIR}/${DISTRO}-${DISTRO_ARCH}/${PN}/${PV}-${PR}"
>
> --
> Siemens AG, Technology
> Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google Groups
> "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/1e8a8cb1-68e6-be14-0d42-13a8a5ff1dea%40siemens.com
> .
>

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

  reply	other threads:[~2023-04-13  7:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 10:17 Srinuvasan Arjunan
2023-04-13  7:02 ` Jan Kiszka
2023-04-13  7:09   ` Srinuvasan Arjunan [this message]
2023-04-14  8:57     ` Srinuvasan Arjunan
2023-04-14  9:00       ` Jan Kiszka
2023-04-14  9:12         ` Srinuvasan Arjunan
2023-04-14  9:16           ` Jan Kiszka
2023-04-17 13:27             ` Srinuvasan Arjunan
2023-04-17 14:10               ` Jan Kiszka
2023-04-18  6:25                 ` Srinuvasan Arjunan
2023-04-18  7:06                 ` Uladzimir Bely
2023-04-19  2:40                   ` [PATCH v2] " Srinuvasan Arjunan
2023-04-19 13:43                     ` Jan Kiszka
2023-05-08 17:57                     ` 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=CAB2Z2nM3yyd9VjU1mWsVB4gZDhqPazttOmS+i7A-xmp8kjchXQ@mail.gmail.com \
    --to=srinuvasanasv@gmail.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=srinuvasan_a@mentor.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