xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: xenomai@lists.linux.dev
Subject: [xenomai-images][PATCH v3 02/10] Replace incorrect string strip method with replace
Date: Wed, 10 Jan 2024 05:45:54 +0100	[thread overview]
Message-ID: <f92f86eb56e6b9ea74515d8fc4a272764e4b1f81.1704861962.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1704861962.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

We want the leading 'AUTOINC+' string stripped off but that is not
reliably done by Python's strip() method with works per character.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 recipes-kernel/linux/linux-xenomai.inc | 2 +-
 recipes-xenomai/xenomai/xenomai.inc    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-xenomai.inc b/recipes-kernel/linux/linux-xenomai.inc
index ca63fea..4761d01 100644
--- a/recipes-kernel/linux/linux-xenomai.inc
+++ b/recipes-kernel/linux/linux-xenomai.inc
@@ -30,7 +30,7 @@ TEMPLATE_FILES += "rules.tmpl"
 
 def get_commit(d):
     try:
-        return bb.fetch2.get_srcrev(d).strip('AUTOINC+')
+        return bb.fetch2.get_srcrev(d).replace('AUTOINC+', '')
     except bb.fetch2.FetchError:
         return ""
 
diff --git a/recipes-xenomai/xenomai/xenomai.inc b/recipes-xenomai/xenomai/xenomai.inc
index 0a32981..26ee654 100644
--- a/recipes-xenomai/xenomai/xenomai.inc
+++ b/recipes-xenomai/xenomai/xenomai.inc
@@ -25,7 +25,7 @@ PACKAGE_ARCH:compat-arch = "${COMPAT_DISTRO_ARCH}"
 # use bitbake get_srcrev to get the current commit id
 def get_commit(d):
     try:
-        return bb.fetch2.get_srcrev(d).strip('AUTOINC+')
+        return bb.fetch2.get_srcrev(d).replace('AUTOINC+', '')
     except bb.fetch2.FetchError:
         return ""
 
-- 
2.35.3


  parent reply	other threads:[~2024-01-10  4:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  4:45 [xenomai-images][PATCH v3 00/10] Add evl support to xenomai-images Jan Kiszka
2024-01-10  4:45 ` [xenomai-images][PATCH v3 01/10] Add Isar patch to permit linux-libc-dev upgrades in the sbuild environment Jan Kiszka
2024-01-10  9:00   ` Florian Bezdeka
2024-01-10  9:04     ` Jan Kiszka
2024-01-10  4:45 ` Jan Kiszka [this message]
2024-01-10  4:45 ` [xenomai-images][PATCH v3 03/10] Factor out print-revision class Jan Kiszka
2024-01-10  4:45 ` [xenomai-images][PATCH v3 04/10] linux-xenomai: Rename linux-xenomai to linux-xenomai-3 Jan Kiszka
2024-01-10  4:45 ` [xenomai-images][PATCH v3 05/10] xenomai-3: Mark xenomai 3 specific configs Jan Kiszka
2024-01-10  4:45 ` [xenomai-images][PATCH v3 06/10] xenomai-4: Enable kernel build Jan Kiszka
2024-01-10  4:45 ` [xenomai-images][PATCH v3 07/10] xenomai-4: Add evl userspace Jan Kiszka
2024-01-10  9:03   ` Florian Bezdeka
2024-01-10 10:43     ` Jan Kiszka
2024-01-10  4:46 ` [xenomai-images][PATCH v3 08/10] kconfig: Add build options for evl Jan Kiszka
2024-01-10  4:46 ` [xenomai-images][PATCH v3 09/10] ci: Rename xenomai 3 files Jan Kiszka
2024-01-10  4:46 ` [xenomai-images][PATCH v3 10/10] ci: Prepare for xenomai-4 test cases Jan Kiszka

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=f92f86eb56e6b9ea74515d8fc4a272764e4b1f81.1704861962.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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).