From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
maira.canal@usp.br, akuster808 <akuster808@gmail.com>
Subject: Re: [OE-core] broken dunfell
Date: Mon, 08 Nov 2021 11:30:55 +0000 [thread overview]
Message-ID: <f14d3a8317338299c2cccebc59e15e4e8ce35738.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAAfyv35N15Ec_LU3UqcDfWRtuo6BgFWmiqLTpG5YSRDyLRGv-g@mail.gmail.com>
On Mon, 2021-11-08 at 12:23 +0100, Belisko Marek wrote:
> On Mon, Nov 8, 2021 at 12:08 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Mon, 2021-11-08 at 11:53 +0100, Marek Belisko wrote:
> > > Hello, latest commit in meta-openembedded on dunfell branch raise an error:
> > >
> > > meta-openembedded/meta-python/recipes-devtools/python/python3-fasteners_0.16.3.bb:14:
> > > unparsed line: 'RDEPENDS:${PN} += " ${PYTHON_PN}-logging
> > > ${PYTHON_PN}-fcntl "'
> > >
> > > Seems new syntax is used in this commit, fix is simple:
> > >
> > > diff --git a/meta-python/recipes-devtools/python/python3-fasteners_0.16.3.bb
> > > b/meta-python/recipes-devtools/python/python3-fasteners_0.16.3.bb
> > > index 1ba2c6f..7ebaa45 100644
> > > --- a/meta-python/recipes-devtools/python/python3-fasteners_0.16.3.bb
> > > +++ b/meta-python/recipes-devtools/python/python3-fasteners_0.16.3.bb
> > > @@ -8,7 +8,7 @@ SRC_URI[sha256sum] =
> > > "b1ab4e5adfbc28681ce44b3024421c4f567e705cc3963c732bf1cba334
> > >
> > > inherit pypi setuptools3
> > >
> > > -RDEPENDS:${PN} += "\
> > > +RDEPENDS_${PN} += "\
> > > ${PYTHON_PN}-logging \
> > > ${PYTHON_PN}-fcntl \
> > > "
> > >
> > > Thanks and BR,
> >
> >
> > Whilst that probably shouldn't be there, I suspect if you upgrade bitbake you
> > won't see that issue.
> I want to say on dunfell due fact it's LTS release ;)
>
Bitbake as well as OE-Core, meta-openembedded and Poky have LTS branches. I
doubt you're using the most recent revisions of bitbake on that LTS branch.
I wasn't suggesting you upgrade to the latest master.
Cheers,
Richard
next prev parent reply other threads:[~2021-11-08 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 10:53 broken dunfell Belisko Marek
2021-11-08 11:08 ` [OE-core] " Richard Purdie
2021-11-08 11:23 ` Belisko Marek
2021-11-08 11:30 ` Richard Purdie [this message]
2021-11-08 11:44 ` Belisko Marek
2021-11-08 14:02 ` Steve Sakoman
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=f14d3a8317338299c2cccebc59e15e4e8ce35738.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=maira.canal@usp.br \
--cc=marek.belisko@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox