From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. aacab139dc272d9c1b42340100cccb15cd7a302f
Date: Tue, 23 Feb 2016 18:23:58 +0000 [thread overview]
Message-ID: <20160223182359.78E091081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 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 2.x development tree".
The branch, master has been updated
via aacab139dc272d9c1b42340100cccb15cd7a302f (commit)
from 829b0ba85156fbf3514b3f5d5b13c0f3254fae49 (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 aacab139dc272d9c1b42340100cccb15cd7a302f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Feb 23 09:40:31 2016 -0800
stunnel: Bump release version
The version on the server seems to be still linked against
the older 0.9.8 series of openssl and needs to be updated
on all systems.
I manually pushed this update for the 2.17 branch on i586.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/stunnel | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/stunnel b/lfs/stunnel
index f6f27e0..4585151 100644
--- a/lfs/stunnel
+++ b/lfs/stunnel
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = stunnel
-PAK_VER = 1
+PAK_VER = 2
DEPS = ""
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-02-23 18:23 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=20160223182359.78E091081BC7@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