meta-arago.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Aniket Limaye <a-limaye@ti.com>
To: <meta-arago@lists.yoctoproject.org>
Cc: <reatmon@ti.com>, Aniket Limaye <a-limaye@ti.com>
Subject: [meta-arago][master/kirkstone][PATCH] tisdk-bundle: Fix generate_sw_manifest_table
Date: Wed, 4 Oct 2023 12:09:45 +0530	[thread overview]
Message-ID: <20231004063945.703846-1-a-limaye@ti.com> (raw)

The generated manifest file is expected to strictly have 7 columns,
delimited by '|' while the License section also sometimes has '|'
character. Replace this one by 'or' to fix manifest file

Signed-off-by: Aniket Limaye <a-limaye@ti.com>
---
 meta-arago-distro/classes/tisdk-bundle.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-arago-distro/classes/tisdk-bundle.bbclass b/meta-arago-distro/classes/tisdk-bundle.bbclass
index 1ebdb6fb..d2d31381 100644
--- a/meta-arago-distro/classes/tisdk-bundle.bbclass
+++ b/meta-arago-distro/classes/tisdk-bundle.bbclass
@@ -553,7 +553,7 @@ EOF
         package="`cat $i | grep Package: | awk {'print $2'}`"
         version="`cat $i | grep Version: | awk {'print $2'} | cut -f1-2 -d-`"
         long_version="`cat $i | grep Version: | awk {'print $2'}`"
-        license="`cat $i | grep License: | cut -d: -f2 `"
+        license="`cat $i | grep License: | cut -d: -f2 | sed 's/|/or/g' `"
         architecture="`cat $i | grep Architecture: | awk {'print $2'}`"
         sources="`cat $i | grep Source: | cut -d ':' -f2-`"
         location="$package""_""$long_version""_""$architecture"".ipk"
-- 
2.34.1



             reply	other threads:[~2023-10-04  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  6:39 Aniket Limaye [this message]
2023-10-04 13:33 ` [meta-arago][master/kirkstone][PATCH] tisdk-bundle: Fix generate_sw_manifest_table Ryan Eatmon
2023-10-04 14:56   ` Limaye, Aniket

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=20231004063945.703846-1-a-limaye@ti.com \
    --to=a-limaye@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.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).