From: Srinuvasan A <Srinuvasan_A@mentor.com>
To: <isar-users@googlegroups.com>
Cc: <jan.kiszka@siemens.com>, Srinuvasan A <srinuvasan_a@mentor.com>
Subject: [PATCH] deb-dl-dir.bbclass: grep exact package from dpkg.log file
Date: Mon, 9 May 2022 18:21:28 +0530 [thread overview]
Message-ID: <20220509125128.897009-1-Srinuvasan_A@mentor.com> (raw)
From: Srinuvasan A <srinuvasan_a@mentor.com>
When we grep the package status from dpkg.log file it returns the output
with partial matches, this leads to downlaod src packages with unknown version fixed that.
Ex: we try to grep this "libgmp10:amd64 2:6.2.1+dfsg-1" package, but it
returns "libgmp10:amd64 2:6.2.1+dfsg-1+deb11u1" package, hence fixed
this grep pattern processing part.
Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
---
meta/classes/deb-dl-dir.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/deb-dl-dir.bbclass b/meta/classes/deb-dl-dir.bbclass
index eace510..4780228 100644
--- a/meta/classes/deb-dl-dir.bbclass
+++ b/meta/classes/deb-dl-dir.bbclass
@@ -12,7 +12,7 @@ is_not_part_of_current_build() {
# Since we are parsing all the debs in DEBDIR, we can to some extend
# try to eliminate some debs that are not part of the current multiconfig
# build using the below method.
- local output="$( grep -hs "status installed ${package}:${arch} ${version}$" \
+ local output="$( grep -xhs ".* status installed ${package}:${arch} ${version}" \
"${IMAGE_ROOTFS}"/var/log/dpkg.log \
"${BUILDCHROOT_HOST_DIR}"/var/log/dpkg.log \
"${BUILDCHROOT_TARGET_DIR}"/var/log/dpkg.log | head -1 )"
--
2.25.1
next reply other threads:[~2022-05-09 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:51 Srinuvasan A [this message]
2022-05-09 14:14 ` Jan Kiszka
2022-05-10 5:00 ` Srinuvasan A
2022-05-18 11:03 ` 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=20220509125128.897009-1-Srinuvasan_A@mentor.com \
--to=srinuvasan_a@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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