From: Alexander Egorenkov <egorenar-dev@posteo.net>
To: buildroot@buildroot.org
Cc: Alexander Egorenkov <egorenar-dev@posteo.net>
Subject: [Buildroot] [PATCH 1/2] package/multipath-tools: bump version to 0.9.6
Date: Sat, 16 Sep 2023 09:18:30 +0000 [thread overview]
Message-ID: <20230916091831.13118-1-egorenar-dev@posteo.net> (raw)
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
---
package/multipath-tools/Config.in | 3 +++
package/multipath-tools/multipath-tools.hash | 2 +-
package/multipath-tools/multipath-tools.mk | 4 ++--
3 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/package/multipath-tools/Config.in b/package/multipath-tools/Config.in
index 222f78b86ce6..4c648a6abb34 100644
--- a/package/multipath-tools/Config.in
+++ b/package/multipath-tools/Config.in
@@ -18,6 +18,9 @@ config BR2_PACKAGE_MULTIPATH_TOOLS
select BR2_PACKAGE_LVM2
select BR2_PACKAGE_LVM2_STANDARD_INSTALL
select BR2_PACKAGE_READLINE
+ select BR2_PACKAGE_UTIL_LINUX
+ select BR2_PACKAGE_UTIL_LINUX_LIBS
+ select BR2_PACKAGE_UTIL_LINUX_LIBMOUNT
help
This package provides the following binaries to drive
the Device Mapper multipathing driver:
diff --git a/package/multipath-tools/multipath-tools.hash b/package/multipath-tools/multipath-tools.hash
index ecaad05e25ad..158f0faa960e 100644
--- a/package/multipath-tools/multipath-tools.hash
+++ b/package/multipath-tools/multipath-tools.hash
@@ -1,5 +1,5 @@
# Locally computed:
-sha256 6ed3cf6e786da20a451d9747cbd4c5817815388b8fc8022d1074b3018479031d multipath-tools-0.9.4.tar.gz
+sha256 401c6f6e8dc5d3feaaee76280716aee718579ac024ce4f2fae77c798dc7a0f9f multipath-tools-0.9.6.tar.gz
sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 LICENSES/GPL-2.0
sha256 3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986 LICENSES/GPL-3.0
sha256 b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c LICENSES/LGPL-2.0
diff --git a/package/multipath-tools/multipath-tools.mk b/package/multipath-tools/multipath-tools.mk
index 23b3cc944267..d9d0f959943d 100644
--- a/package/multipath-tools/multipath-tools.mk
+++ b/package/multipath-tools/multipath-tools.mk
@@ -4,7 +4,7 @@
#
################################################################################
-MULTIPATH_TOOLS_VERSION = 0.9.4
+MULTIPATH_TOOLS_VERSION = 0.9.6
MULTIPATH_TOOLS_SITE = $(call github,opensvc,multipath-tools,$(MULTIPATH_TOOLS_VERSION))
MULTIPATH_TOOLS_LICENSE = \
@@ -20,7 +20,7 @@ MULTIPATH_TOOLS_LICENSE_FILES = \
README.md
MULTIPATH_TOOLS_CPE_ID_VENDOR = opensvc
-MULTIPATH_TOOLS_DEPENDENCIES = lvm2 json-c readline udev liburcu libaio host-pkgconf
+MULTIPATH_TOOLS_DEPENDENCIES = lvm2 json-c readline udev liburcu libaio host-pkgconf util-linux-libs
MULTIPATH_TOOLS_MAKE_OPTS = \
kernel_incdir=$(STAGING_DIR)/usr/include \
LIB="lib" \
--
2.42.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-09-16 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 9:18 Alexander Egorenkov [this message]
2023-09-16 9:18 ` [Buildroot] [PATCH 2/2] package/makedumpfile: bump version to 1.7.3 Alexander Egorenkov
2023-09-16 12:09 ` Yann E. MORIN
2023-09-16 12:08 ` [Buildroot] [PATCH 1/2] package/multipath-tools: bump version to 0.9.6 Yann E. MORIN
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=20230916091831.13118-1-egorenar-dev@posteo.net \
--to=egorenar-dev@posteo.net \
--cc=buildroot@buildroot.org \
/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