public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] bind: Update to 9.16.39
Date: Sat, 18 Mar 2023 20:40:56 +0100	[thread overview]
Message-ID: <20230318194056.3410171-1-matthias.fischer@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3747 bytes --]

For details  see:
https://downloads.isc.org/isc/bind9/9.16.39/doc/arm/html/notes.html#notes-for-bind-9-16-39

"Notes for BIND 9.16.39
Feature Changes

    libuv support for receiving multiple UDP messages in a single
    recvmmsg() system call has been tweaked several times between libuv
    versions 1.35.0 and 1.40.0; the current recommended libuv version is
    1.40.0 or higher. New rules are now in effect for running with a
    different version of libuv than the one used at compilation time. These
    rules may trigger a fatal error at startup:

        Building against or running with libuv versions 1.35.0 and 1.36.0
        is now a fatal error.

        Running with libuv version higher than 1.34.2 is now a fatal error
        when named is built against libuv version 1.34.2 or lower.

        Running with libuv version higher than 1.39.0 is now a fatal error
        when named is built against libuv version 1.37.0, 1.38.0, 1.38.1,
        or 1.39.0.

    This prevents the use of libuv versions that may trigger an assertion
    failure when receiving multiple UDP messages in a single system call.
    [GL #3840]

Bug Fixes

    named could crash with an assertion failure when adding a new zone into
    the configuration file for a name which was already configured as a
    member zone for a catalog zone. This has been fixed. [GL #3911]"

    When named starts up, it sends a query for the DNSSEC key for each
    configured trust anchor to determine whether the key has changed. In
    some unusual cases, the query might depend on a zone for which the
    server is itself authoritative, and would have failed if it were sent
    before the zone was fully loaded. This has now been fixed by delaying
    the key queries until all zones have finished loading. [GL #3673]"

Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
 config/rootfiles/common/bind | 14 +++++++-------
 lfs/bind                     |  4 ++--
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/config/rootfiles/common/bind b/config/rootfiles/common/bind
index 49a56107e..aabaae6fa 100644
--- a/config/rootfiles/common/bind
+++ b/config/rootfiles/common/bind
@@ -271,24 +271,24 @@ usr/bin/nsupdate
 #usr/include/pk11/site.h
 #usr/include/pkcs11
 #usr/include/pkcs11/pkcs11.h
-usr/lib/libbind9-9.16.38.so
+usr/lib/libbind9-9.16.39.so
 #usr/lib/libbind9.la
 #usr/lib/libbind9.so
-usr/lib/libdns-9.16.38.so
+usr/lib/libdns-9.16.39.so
 #usr/lib/libdns.la
 #usr/lib/libdns.so
-usr/lib/libirs-9.16.38.so
+usr/lib/libirs-9.16.39.so
 #usr/lib/libirs.la
 #usr/lib/libirs.so
-usr/lib/libisc-9.16.38.so
+usr/lib/libisc-9.16.39.so
 #usr/lib/libisc.la
 #usr/lib/libisc.so
-usr/lib/libisccc-9.16.38.so
+usr/lib/libisccc-9.16.39.so
 #usr/lib/libisccc.la
 #usr/lib/libisccc.so
-usr/lib/libisccfg-9.16.38.so
+usr/lib/libisccfg-9.16.39.so
 #usr/lib/libisccfg.la
 #usr/lib/libisccfg.so
-usr/lib/libns-9.16.38.so
+usr/lib/libns-9.16.39.so
 #usr/lib/libns.la
 #usr/lib/libns.so
diff --git a/lfs/bind b/lfs/bind
index 6782ab24a..584cb7e5a 100644
--- a/lfs/bind
+++ b/lfs/bind
@@ -25,7 +25,7 @@
 
 include Config
 
-VER        = 9.16.38
+VER        = 9.16.39
 
 THISAPP    = bind-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = af74f3867837741102f9e1b9eb0fa44948131fc2122a5ea6a707b92408604d62f95350ff561ec98787ce516c96ef971b1a03d775aaba99ebc4ea334cd9800ed2
+$(DL_FILE)_BLAKE2 = d9fb51435dce11c8854084cc21de79df3ae6529baead76dcf27711bcff33469d1fd6fbd3366b61bc921f92850620c9b7464d4dbe08dd0c7e2f3e5e1c1100cb79
 
 install : $(TARGET)
 
-- 
2.34.1


                 reply	other threads:[~2023-03-18 19:40 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=20230318194056.3410171-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@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