From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bind: Update to 9.11.25
Date: Fri, 21 Jan 2022 22:42:11 +0100 [thread overview]
Message-ID: <42b78abc-2041-7b0d-d2da-12670cb6217f@ipfire.org> (raw)
In-Reply-To: <20220121164724.3464738-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4038 bytes --]
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 21/01/2022 17:47, Matthias Fischer wrote:
> For details (v9.16.22-v9.16.25) see:
> https://downloads.isc.org/isc/bind9/9.16.25/doc/arm/html/notes.html#notes-for-bind-9-16-25
>
> "Notes for BIND 9.16.25
> Feature Changes
>
> Overall memory use by named has been optimized and reduced,
> especially on systems with many CPU cores. The default memory
> allocator has been switched from internal to external. A new
> command-line option -M internal allows named to be started with the
> old internal memory allocator. [GL #2398]
>
> Bug Fixes
>
> On FreeBSD, TCP connections leaked a small amount of heap memory,
> leading to an eventual out-of-memory problem. This has been fixed.
> [GL #3051]
>
> If signatures created by the ZSK were expired and the ZSK private
> key was offline, the signatures were not replaced. This behavior has
> been amended to replace the expired signatures with new signatures
> created using the KSK. [GL #3049]
>
> Under certain circumstances, the signed version of an inline-signed
> zone could be dumped to disk without the serial number of the
> unsigned version of the zone. This prevented resynchronization
> of the zone contents after named restarted, if the unsigned zone
> file was modified while named was not running. This has been fixed.
> [GL #3071]
> ...
> "
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/bind | 14 +++++++-------
> lfs/bind | 6 +++---
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/config/rootfiles/common/bind b/config/rootfiles/common/bind
> index a89af5bcb..4ea64dc0c 100644
> --- a/config/rootfiles/common/bind
> +++ b/config/rootfiles/common/bind
> @@ -274,24 +274,24 @@ usr/bin/nsupdate
> #usr/include/pk11/site.h
> #usr/include/pkcs11
> #usr/include/pkcs11/pkcs11.h
> -usr/lib/libbind9-9.16.22.so
> +usr/lib/libbind9-9.16.25.so
> #usr/lib/libbind9.la
> #usr/lib/libbind9.so
> -usr/lib/libdns-9.16.22.so
> +usr/lib/libdns-9.16.25.so
> #usr/lib/libdns.la
> #usr/lib/libdns.so
> -usr/lib/libirs-9.16.22.so
> +usr/lib/libirs-9.16.25.so
> #usr/lib/libirs.la
> #usr/lib/libirs.so
> -usr/lib/libisc-9.16.22.so
> +usr/lib/libisc-9.16.25.so
> #usr/lib/libisc.la
> #usr/lib/libisc.so
> -usr/lib/libisccc-9.16.22.so
> +usr/lib/libisccc-9.16.25.so
> #usr/lib/libisccc.la
> #usr/lib/libisccc.so
> -usr/lib/libisccfg-9.16.22.so
> +usr/lib/libisccfg-9.16.25.so
> #usr/lib/libisccfg.la
> #usr/lib/libisccfg.so
> -usr/lib/libns-9.16.22.so
> +usr/lib/libns-9.16.25.so
> #usr/lib/libns.la
> #usr/lib/libns.so
> diff --git a/lfs/bind b/lfs/bind
> index 8544f0f1f..fc6e7654e 100644
> --- a/lfs/bind
> +++ b/lfs/bind
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -25,7 +25,7 @@
>
> include Config
>
> -VER = 9.16.22
> +VER = 9.16.25
>
> THISAPP = bind-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 6a45478b33c04c830d4263635d8cd137
> +$(DL_FILE)_MD5 = 361a54fc5ebeb3a1af77abec08b33661
>
> install : $(TARGET)
>
next prev parent reply other threads:[~2022-01-21 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 16:47 Matthias Fischer
2022-01-21 21:42 ` Adolf Belka [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-06 9:34 Matthias Fischer
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=42b78abc-2041-7b0d-d2da-12670cb6217f@ipfire.org \
--to=adolf.belka@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