From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.9.0
Date: Wed, 13 Feb 2019 17:32:00 +0000 [thread overview]
Message-ID: <5B8FE7D3-271F-4171-9A37-AC01EBE42BCF@ipfire.org> (raw)
In-Reply-To: <20190209094036.11201-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
Hi,
I did *not* merge this one, yet.
The change log that you linked wasn’t very helpful, but there was an announcement email with some more details:
https://nlnetlabs.nl/pipermail/unbound-users/2019-February/011353.html
This release contains all the EDNS Flag Day changes and that might cause some trouble. I would prefer to merge this with the next Core Update because Core 128 should already have been closed and I do not want to risk re-opening it.
So, please remind me to merge this next week in case I forgot.
Best,
-Michael
> On 9 Feb 2019, at 09:40, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> For details see:
> https://nlnetlabs.nl/svn/unbound/tags/release-1.9.0/doc/Changelog
>
> Best,
> Matthias
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/unbound | 2 +-
> lfs/unbound | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/unbound b/config/rootfiles/common/unbound
> index 9a8126c15..843e0eeca 100644
> --- a/config/rootfiles/common/unbound
> +++ b/config/rootfiles/common/unbound
> @@ -11,7 +11,7 @@ etc/unbound/unbound.conf
> #usr/lib/libunbound.la
> #usr/lib/libunbound.so
> usr/lib/libunbound.so.8
> -usr/lib/libunbound.so.8.0.3
> +usr/lib/libunbound.so.8.1.0
> #usr/lib/pkgconfig/libunbound.pc
> usr/sbin/unbound
> usr/sbin/unbound-anchor
> diff --git a/lfs/unbound b/lfs/unbound
> index 07501d1d6..b090010d4 100644
> --- a/lfs/unbound
> +++ b/lfs/unbound
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.8.3
> +VER = 1.9.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 = 4646203343d3b8f5aeb1b57753c27ead
> +$(DL_FILE)_MD5 = 1026159991a3883518525bc18e25582f
>
> install : $(TARGET)
>
> --
> 2.18.0
>
next prev parent reply other threads:[~2019-02-13 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 9:40 Matthias Fischer
2019-02-13 17:32 ` Michael Tremer [this message]
2019-02-14 7:05 ` Matthias Fischer
2019-02-14 11:01 ` Michael Tremer
2019-02-14 17:26 ` Matthias Fischer
2019-02-15 11:34 ` Michael Tremer
2019-02-15 16:48 ` Matthias Fischer
2019-02-26 9:54 ` Michael Tremer
2019-02-15 13:12 ` ummeegge
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=5B8FE7D3-271F-4171-9A37-AC01EBE42BCF@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