Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package bind for openSUSE:Factory checked in
at 2023-05-18 15:18:18
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/bind (Old)
and /work/SRC/openSUSE:Factory/.bind.new.1533 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "bind"
Thu May 18 15:18:18 2023 rev:195 rq:1087546 version:9.18.15
Changes:
--------
--- /work/SRC/openSUSE:Factory/bind/bind.changes 2023-04-22
21:59:49.464988297 +0200
+++ /work/SRC/openSUSE:Factory/.bind.new.1533/bind.changes 2023-05-18
15:18:23.565569237 +0200
@@ -1,0 +2,35 @@
+Wed May 17 09:39:55 UTC 2023 - Jorik Cronenberg <jorik.cronenb...@suse.com>
+
+- Update to release 9.18.15
+ Bug Fixes:
+ * The max-transfer-time-in and max-transfer-idle-in statements
+ have not had any effect since the BIND 9 networking stack was
+ refactored in version 9.16. The missing functionality has been
+ re-implemented and incoming zone transfers now time out
+ properly when not progressing.
+ * The read timeout in rndc is now 60 seconds, matching the
+ behavior in BIND 9.16 and earlier. It had previously been
+ lowered to 30 seconds by mistake.
+ * When the ISC_R_INVALIDPROTO (ENOPROTOOPT, EPROTONOSUPPORT)
+ error code is returned by libuv, it is now treated as a network
+ failure: the server for which that error code is returned gets
+ marked as broken and is not contacted again during a given
+ resolution process.
+ * When removing delegations from an opt-out range,
+ empty-non-terminal NSEC3 records generated by those delegations
+ were not cleaned up. This has been fixed.
+ * Log file rotation code did not clean up older versions of log
+ files when the logging channel had an absolute path configured
+ as a file destination. This has been fixed.
+
+ Known Issues:
+ * Sending NOTIFY messages silently fails when the source port
+ specified in the notify-source statement is already in use.
+ This can happen e.g. when multiple servers are configured as
+ NOTIFY targets for a zone and some of them are unresponsive.
+ This issue can be worked around by not specifying the source
+ port for NOTIFY messages in the notify-source statement; note
+ that source port configuration is already deprecated and will
+ be removed altogether in a future release.
+
+-------------------------------------------------------------------
Old:
----
bind-9.18.14.tar.xz
bind-9.18.14.tar.xz.asc
New:
----
bind-9.18.15.tar.xz
bind-9.18.15.tar.xz.asc
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ bind.spec ++++++
--- /var/tmp/diff_new_pack.ZTSZ0Y/_old 2023-05-18 15:18:24.349573224 +0200
+++ /var/tmp/diff_new_pack.ZTSZ0Y/_new 2023-05-18 15:18:24.353573245 +0200
@@ -56,7 +56,7 @@
%define _fillupdir %{_localstatedir}/adm/fillup-templates
%endif
Name: bind
-Version: 9.18.14
+Version: 9.18.15
Release: 0
Summary: Domain Name System (DNS) Server (named)
License: MPL-2.0
++++++ bind-9.18.14.tar.xz -> bind-9.18.15.tar.xz ++++++
++++ 2469 lines of diff (skipped)
