From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. ef8980a8367631c40ff30063658868bac520e0fb
Date: Sun, 10 Feb 2013 21:47:06 +0100 [thread overview]
Message-ID: <20130210204706.D8D79200D9@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1666 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 ef8980a8367631c40ff30063658868bac520e0fb (commit)
from ec04fe8c24d057e2bf08c6f2637866f61bf2494d (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 ef8980a8367631c40ff30063658868bac520e0fb
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Feb 10 19:29:16 2013 +0100
openvpn: Remove polarssl as a build dependency.
It was never ment to use polarssl as the SSL implementation
of openvpn, but I must have forgotten to remove the line.
openvpn is not capable of all the features it normally
supports when it is compiled with polarssl.
-----------------------------------------------------------------------
Summary of changes:
openvpn/openvpn.nm | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Difference in files:
diff --git a/openvpn/openvpn.nm b/openvpn/openvpn.nm
index 6698978..88c9bd9 100644
--- a/openvpn/openvpn.nm
+++ b/openvpn/openvpn.nm
@@ -5,7 +5,7 @@
name = openvpn
version = 2.3.0
-release = 1
+release = 2
groups = Networking/VPN
url = http://openvpn.net/
@@ -31,7 +31,6 @@ build
lzo-devel
openssl-devel
pam-devel
- polarssl-devel
end
configure_options += \
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-02-10 20:47 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=20130210204706.D8D79200D9@argus.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