From: Insu Park <insu0.park@gmail.com>
To: bitbake-devel@lists.openembedded.org, steve@sakoman.com
Cc: Insu Park <insu0.park@gmail.com>
Subject: [dunfell][1.46][PATCH 0/1] Fix dependency handling bug of remove operator
Date: Wed, 27 Dec 2023 23:56:16 +0900 [thread overview]
Message-ID: <20231227145617.8940-1-insu0.park@gmail.com> (raw)
This commit has merged on Sep 19 on the master branch. (b90520eedb1dbc7f6a3928d089fe74fafb864eb5)
I think this bug should also be fixed on the LTS branches, kirkstone and dunfell.
This bug is not that common within the meta layers under the Yocto projects, but could be a problem in production domains.
I cherry-picked it by myself because it requires to resolve conflicts for each branch.
Please see the details on the previous post: https://lists.openembedded.org/g/bitbake-devel/message/15082
Insu Park (1):
data: Add missing dependency handling of remove operator
lib/bb/data.py | 1 +
lib/bb/tests/codeparser.py | 26 ++++++++++++++++++++++++++
2 files changed, 27 insertions(+)
--
2.25.1
next reply other threads:[~2023-12-27 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 14:56 Insu Park [this message]
2023-12-27 14:56 ` [dunfell][1.46][PATCH 1/1] data: Add missing dependency handling of remove operator Insu Park
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=20231227145617.8940-1-insu0.park@gmail.com \
--to=insu0.park@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=steve@sakoman.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).