From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bind: Update to 9.11.14
Date: Sun, 05 Jan 2020 00:46:55 +0100 [thread overview]
Message-ID: <48c98185-d44d-3032-8165-261bd0de1eef@ipfire.org> (raw)
In-Reply-To: <28872c3b53c4faf27debc9f2c8e929d4@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]
Hi,
Hm, that's strange.
I tested again today with Core 138 (*32bit*) and once again with current
'next'.
Besides, 'bind 9.11.14' is running here for about two weeks now: no seen
problems.
Can it be that this is a problem with 64bit builds only?
On 03.01.2020 22:39, Arne Fitzenreiter wrote:
> I had reverted this because it fails on armv5tel. (also on my builder,
> not only on nightly)
>
> https://nightly.ipfire.org/next/2020-01-02%2016:17:54%20+0000-c846ed16/armv5tel/
>
>
> Am 2019-12-23 15:47, schrieb Matthias Fischer:
>> For details see:
>> https://downloads.isc.org/isc/bind9/9.11.14/RELEASE-NOTES-bind-9.11.14.html
>>
>> "Bug Fixes
>>
>> Fixed a bug that caused named to leak memory on reconfiguration when
>> any
>> GeoIP2 database was in use. [GL #1445]
>>
>> Fixed several possible race conditions discovered by Thread Sanitizer."
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>> config/rootfiles/common/bind | 4 ++--
>> lfs/bind | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/config/rootfiles/common/bind
>> b/config/rootfiles/common/bind
>> index df6bbf4b6..e5435bd02 100644
>> --- a/config/rootfiles/common/bind
>> +++ b/config/rootfiles/common/bind
>> @@ -272,11 +272,11 @@ usr/lib/libbind9.so.161.0.4
>> #usr/lib/libdns.la
>> #usr/lib/libdns.so
>> usr/lib/libdns.so.1107
>> -usr/lib/libdns.so.1107.1.0
>> +usr/lib/libdns.so.1107.1.1
>> #usr/lib/libisc.la
>> #usr/lib/libisc.so
>> usr/lib/libisc.so.1104
>> -usr/lib/libisc.so.1104.0.0
>> +usr/lib/libisc.so.1104.0.1
>> #usr/lib/libisccc.la
>> #usr/lib/libisccc.so
>> usr/lib/libisccc.so.161
>> diff --git a/lfs/bind b/lfs/bind
>> index 6bb23a143..249328843 100644
>> --- a/lfs/bind
>> +++ b/lfs/bind
>> @@ -25,7 +25,7 @@
>>
>> include Config
>>
>> -VER = 9.11.13
>> +VER = 9.11.14
>>
>> THISAPP = bind-$(VER)
>> DL_FILE = $(THISAPP).tar.gz
>> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_MD5 = 17de0d024ab1eac377f1c2854dc25057
>> +$(DL_FILE)_MD5 = 5aa75bcb6cdad102f151cae4a53f117f
>>
>> install : $(TARGET)
>
prev parent reply other threads:[~2020-01-04 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 14:47 Matthias Fischer
2020-01-03 21:39 ` Arne Fitzenreiter
2020-01-04 23:46 ` Matthias Fischer [this message]
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=48c98185-d44d-3032-8165-261bd0de1eef@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