Re: Bind 9.16.17 update built for packages?

From: Simon Wright <>
Date: Mon, 21 Jun 2021 07:49:41 UTC
Indeed "these things they do 'appen!" :) Is it possible/worth adding a
note to UPDATING to not upgrade to 9.16.17?

Something like this:

AFFECTS: users of bind916 9.16.17

ISC have issued a warning to users to not upgrade to this version of
bind916 due to bug in the lookup tables which is likely to cause
operational errors for most users.

The issue does not exist in 9.16.16 and is fixed in 9.16.18, please wait
for that package to be released before upgrading.


Or probably better, roll changes back to remove the faulty package?



On 21/06/2021 2:56 pm, Mathieu Arnold wrote:
> On Mon, Jun 21, 2021 at 07:46:50AM +0800, Simon Wright wrote:
>> Hi Mat and all,
>> ISC released a warning not to upgrade to versions 9.16.17 or 9.17.14
>> which Xavier Humbert forwarded to ports@ on 18 June due a bug in the
>> code (mail attached):
>> This morning I saw that the package build servers have completed a build
>> using ports tree hash 7e413d93a62 and poudriere has built bind-9.16.17
>> and bind-tools-9.16.17 for distribution which is the version warned about.
>> This bug has been corrected in 9.16.18
>> Shouldn't 9.16.17 have been skipped and these ports moved straight to
>> 9.16.18?
> Well, if I had been able to see into the future and know that, when I
> updated to 9.16.17, it was a bad idea, I would probably not have done it.
> Hindsight is great, but, well...