Query on issue#2389 BIND 9.16.10
Reindl Harald
h.reindl at thelounge.net
Mon Oct 18 23:07:01 UTC 2021
Am 19.10.21 um 00:46 schrieb raf:
> On Mon, Oct 18, 2021 at 01:02:07PM +0200, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>> Am 18.10.21 um 12:57 schrieb Rajnish Kamboj via bind-users:
>>> Upgrading to latest release will fix the issue
>>
>> lesson to learn: report issues after you made sure you are using the latest
>> version which probably would fix it
>>
>>> Can you also help us with scenarios as to why this issue is occurring?
>>> May be this will help us in quick workaround (if possible) till the time we plan for latest BIND.
>>
>> what exactly do you need to plan?
>> just update!
>>
>> shoudn't take more than 5 minutes with packages
>>
>> 9.16.10 to 9.16.21 is a bugfix update, case closed
>
> Packaging is not always that simple. For example, on
> Debian stable, the current version is 9.16.15. However,
> the Debian team will backport security patches from
> 9.5.16-21 if necessary.
dunno Debian well but on Fedora 2007 it took me not that much time to
learn build rpms
when one have issues with 9.16.10 it's not likely Debian at all - look
at 9.16.15 versus 9.16.10 from the OP
even Debian seems to be more recent and i don't like the "we are smarter
than upstream on only god knows which fixes our package
contains"-attitude to say it polite
so what's the point of running 9.16.10?
look "Upgrading to latest release will fix the issue" means "i know what
will fix the issue but i still seek for whatever workaround instead
solve the problem"
More information about the bind-users
mailing list