public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. cad653aee39b9bd295fde607a99f732a29289dde
Date: Thu, 24 Mar 2016 20:39:19 +0000	[thread overview]
Message-ID: <20160324203919.841F51081BA6@git01.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".

The branch, master has been updated
       via  cad653aee39b9bd295fde607a99f732a29289dde (commit)
      from  5354877414fd0703556d481b299ef9635dd5d99b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit cad653aee39b9bd295fde607a99f732a29289dde
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Mar 24 19:57:50 2016 +0000

    strongswan: Update to 5.4.0
    
    Introduces a new configuration interface (VICI) and fixes
    several other bugs.
    
    Fixes #11080
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 strongswan/patches/strongswan-swanctl-1193106.patch | 10 ----------
 strongswan/strongswan.nm                            |  4 ++--
 2 files changed, 2 insertions(+), 12 deletions(-)
 delete mode 100644 strongswan/patches/strongswan-swanctl-1193106.patch

Difference in files:
diff --git a/strongswan/patches/strongswan-swanctl-1193106.patch b/strongswan/patches/strongswan-swanctl-1193106.patch
deleted file mode 100644
index cecef1f..0000000
--- a/strongswan/patches/strongswan-swanctl-1193106.patch
+++ /dev/null
@@ -1,10 +0,0 @@
-diff -urNp strongswan-5.2.2/init/systemd-swanctl/strongswan-swanctl.service.in strongswan-5.2.2-patched/init/systemd-swanctl/strongswan-swanctl.service.in
---- strongswan-5.2.2/init/systemd-swanctl/strongswan-swanctl.service.in	2014-09-26 09:04:24.000000000 -0400
-+++ strongswan-5.2.2-patched/init/systemd-swanctl/strongswan-swanctl.service.in	2015-02-20 09:42:17.822480297 -0500
-@@ -7,3 +7,6 @@ Type=notify
- ExecStart=@SBINDIR@/charon-systemd
- ExecStartPost=@SBINDIR@/swanctl --load-all --noprompt
- ExecReload=@SBINDIR@/swanctl --reload
-+
-+[Install]
-+WantedBy=multi-user.target
diff --git a/strongswan/strongswan.nm b/strongswan/strongswan.nm
index b8488e4..54b4f7d 100644
--- a/strongswan/strongswan.nm
+++ b/strongswan/strongswan.nm
@@ -4,8 +4,8 @@
 ###############################################################################
 
 name       = strongswan
-version    = 5.3.3
-release    = 3
+version    = 5.4.0
+release    = 1
 
 groups     = Networking/VPN
 url        = http://www.strongswan.org/


hooks/post-receive
--
IPFire 3.x development tree

                 reply	other threads:[~2016-03-24 20:39 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=20160324203919.841F51081BA6@git01.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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