From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] strongswan: Update to 5.3.3
Date: Fri, 16 Oct 2015 17:44:06 +0200 [thread overview]
Message-ID: <1445010246-26720-1-git-send-email-stefan.schantl@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
This is a minor update to the latest stable version of strongswan.
The support and usage of systemd explicitly has been enabled and
the dependency to systemd has been updated because the configure script
of strongswan is looking for the systemd compat libraries which are provided
by systemd 221-2 and later versions.
Fixes #10896.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
strongswan/strongswan.nm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/strongswan/strongswan.nm b/strongswan/strongswan.nm
index b386083..dd0a137 100644
--- a/strongswan/strongswan.nm
+++ b/strongswan/strongswan.nm
@@ -4,7 +4,7 @@
###############################################################################
name = strongswan
-version = 5.3.2
+version = 5.3.3
release = 1
groups = Networking/VPN
@@ -38,8 +38,7 @@ build
openssl-devel
perl
sqlite-devel
- systemd-devel
- systemd-units
+ systemd-devel >= 221-2
end
configure_options += \
@@ -61,6 +60,7 @@ build
--enable-eap-identity \
--with-capabilities=libcap \
--enable-swanctl \
+ --enable-systemd \
--enable-kernel-libipsec
if "%{DISTRO_ARCH}" == "i686"
--
2.4.3
next reply other threads:[~2015-10-16 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 15:44 Stefan Schantl [this message]
2015-10-16 15:49 ` Michael Tremer
2015-10-16 20:52 ` Stefan Schantl
2015-10-16 20:52 ` Michael Tremer
2015-10-16 21:08 ` [PATCHv2] " Stefan Schantl
2015-10-16 21:11 ` Michael Tremer
2015-10-16 21:20 ` [PATCH v3] " Stefan Schantl
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=1445010246-26720-1-git-send-email-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