From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 4/4] linux-custom: Fix linux-libc-dev version check
Date: Tue, 2 Apr 2019 08:20:51 +0200 [thread overview]
Message-ID: <7d012cc880bc305460e1716ef04e9ef737001ada.1554186051.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1554186051.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1554186051.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
We deploy "${PV}-1". Comparing against "${PV}" prevents package updates
and triggers false-positive warnings.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/recipes-kernel/linux/files/build-kernel.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/files/build-kernel.sh b/meta/recipes-kernel/linux/files/build-kernel.sh
index 842b585..4fdf3ed 100644
--- a/meta/recipes-kernel/linux/files/build-kernel.sh
+++ b/meta/recipes-kernel/linux/files/build-kernel.sh
@@ -127,6 +127,6 @@ rm -f linux-headers-${PV}_${PV}-1_*.deb
# linux-libc-dev causes dependency problems if we downgrade
# remove it after the build so the downgraded version does not get deployed
LINUX_LIBC_DEV_V=$( dpkg-query --show --showformat '${Version}' linux-libc-dev )
-if dpkg --compare-versions $LINUX_LIBC_DEV_V gt $PV; then
+if dpkg --compare-versions $LINUX_LIBC_DEV_V gt $PV-1; then
rm -f linux-libc-dev_${PV}*.deb
fi
--
2.16.4
next prev parent reply other threads:[~2019-04-02 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 6:20 [PATCH 0/4] Patch improvements, more templating fallouts, linux-libc-dev fix Jan Kiszka
2019-04-02 6:20 ` [PATCH 1/4] patch: Add support for patchdir parameter Jan Kiszka
2019-04-02 6:20 ` [PATCH 2/4] Make patch task repeatedly applicable Jan Kiszka
2019-04-02 6:20 ` [PATCH 3/4] template: Remove KERNEL_NAME from default TEMPLATE_VARS Jan Kiszka
2019-04-02 6:20 ` Jan Kiszka [this message]
2019-04-03 18:36 ` [PATCH 0/4] Patch improvements, more templating fallouts, linux-libc-dev fix Maxim Yu. Osipov
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=7d012cc880bc305460e1716ef04e9ef737001ada.1554186051.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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