From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 22870c037560a37577fabfde824862981c792b0c
Date: Thu, 25 May 2017 21:06:52 +0100 [thread overview]
Message-ID: <20170525200653.31BA910853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1585 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, next has been updated
via 22870c037560a37577fabfde824862981c792b0c (commit)
from d1e67bcaff7a0a280420f88ac2c34f31afc441ff (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 22870c037560a37577fabfde824862981c792b0c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu May 25 20:58:54 2017 +0100
openssl: Update to 1.0.2l
This release only contains bug fixes but no security-related fixes
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/openssl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/openssl b/lfs/openssl
index d6be5a9..b613ed7 100644
--- a/lfs/openssl
+++ b/lfs/openssl
@@ -24,7 +24,7 @@
include Config
-VER = 1.0.2k
+VER = 1.0.2l
THISAPP = openssl-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -94,7 +94,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = f965fc0bf01bf882b31314b61391ae65
+$(DL_FILE)_MD5 = f85123cd390e864dfbe517e7616e6566
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-05-25 20:06 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=20170525200653.31BA910853C3@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