From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ef2bb434022a72393bbaa270a886ce4cf579901f
Date: Fri, 16 Dec 2016 10:32:44 +0000 [thread overview]
Message-ID: <20161216103245.0D3971078E80@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2138 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 ef2bb434022a72393bbaa270a886ce4cf579901f (commit)
from b2f96a94e3535a7fccbfd6b7dd18370718d5804b (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 ef2bb434022a72393bbaa270a886ce4cf579901f
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Fri Dec 16 09:50:19 2016 +0100
unbound: Update to 1.6.0
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
For details, see:
http://www.unbound.net/download.html
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/unbound | 2 +-
lfs/unbound | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/unbound b/config/rootfiles/common/unbound
index 722d730..c31b8a6 100644
--- a/config/rootfiles/common/unbound
+++ b/config/rootfiles/common/unbound
@@ -10,7 +10,7 @@ etc/unbound/unbound.conf
#usr/lib/libunbound.la
#usr/lib/libunbound.so
usr/lib/libunbound.so.2
-usr/lib/libunbound.so.2.4.2
+usr/lib/libunbound.so.2.4.3
usr/sbin/unbound
usr/sbin/unbound-anchor
usr/sbin/unbound-checkconf
diff --git a/lfs/unbound b/lfs/unbound
index b2ef6ac..3494a7b 100644
--- a/lfs/unbound
+++ b/lfs/unbound
@@ -24,7 +24,7 @@
include Config
-VER = 1.5.10
+VER = 1.6.0
THISAPP = unbound-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 0a3a236811f1ab5c1dc31974fa74e047
+$(DL_FILE)_MD5 = 78409eccf7260d260b6463f85e59c66b
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-12-16 10:32 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=20161216103245.0D3971078E80@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