public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] strongswan: Update to 5.3.3
Date: Fri, 16 Oct 2015 21:52:52 +0100	[thread overview]
Message-ID: <1445028772.18375.94.camel@ipfire.org> (raw)
In-Reply-To: <1445028733.2021.27.camel@ipfire.org>

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

This entire process is meant to be less try-and-error.

On Fri, 2015-10-16 at 22:52 +0200, Stefan Schantl wrote:
> Drop that patch, the compiled binaries does not work.
> 
> I will upload a new patch for a fixed version.
> 
> -Stefan
> > Why are there no systemd scriptlets?
> > 
> > On Fri, 2015-10-16 at 17:44 +0200, Stefan Schantl wrote:
> > > 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-16 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 15:44 Stefan Schantl
2015-10-16 15:49 ` Michael Tremer
2015-10-16 20:52   ` Stefan Schantl
2015-10-16 20:52     ` Michael Tremer [this message]
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=1445028772.18375.94.camel@ipfire.org \
    --to=michael.tremer@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