public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] multipath-tools: Update to 0.9.4
Date: Tue, 21 Feb 2023 12:52:45 +0100	[thread overview]
Message-ID: <20230221115245.632297-1-stefan.schantl@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
 multipath-tools/multipath-tools.nm | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/multipath-tools/multipath-tools.nm b/multipath-tools/multipath-tools.nm
index 02bfeeaf3..881c2dfd0 100644
--- a/multipath-tools/multipath-tools.nm
+++ b/multipath-tools/multipath-tools.nm
@@ -4,7 +4,7 @@
 ###############################################################################
 
 name       = multipath-tools
-version    = 0.6.3
+version    = 0.9.4
 release    = 1
 
 groups     = System/Base
@@ -17,26 +17,29 @@ description
 	instructing the device-mapper multipath kernel module what to do.
 end
 
-# git archive 0.6.3 --prefix=multipath-tools-0.6.3/ --format=tar | gzip --best > multipath-tools-0.6.3.tar.gz
+source_dl  = https://github.com/opensvc/%{name}/archive/refs/tags/%{version}.tar.gz#/
 sources    = %{thisapp}.tar.gz
 
 build
 	requires
 		gzip
+		json-c-devel
 		libaio-devel
 		libdevmapper-devel
 		libudev-devel
+		liburcu-devel
 		ncurses-devel
 		readline-devel
 	end
 
-	make_build_targets += -C kpartx LIB=%{lib} LDFLAGS="%{LDFLAGS} -ldevmapper"
+	make_build_targets += kpartx LIB=%{lib} LDFLAGS="%{LDFLAGS} -ldevmapper"
 
 	# Install everything to the correct locations.
 	make_install_targets += \
 		-C kpartx \
 		bindir=%{sbindir} \
 		syslibdir=%{libdir} \
+		mandir=%{mandir} \
 		libdir=%{libdir}/multipath \
 		unitdir=%{unitdir}
 end
@@ -49,6 +52,7 @@ packages
 		end
 
 		files
+			/usr/lib/udev
 			%{sbindir}/kpartx
 			%{mandir}/man8/kpartx.8*
 		end
-- 
2.30.2


                 reply	other threads:[~2023-02-21 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230221115245.632297-1-stefan.schantl@ipfire.org \
    --to=stefan.schantl@ipfire.org \
    --cc=development@lists.ipfire.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