Hello Brian,
Currently, 9.18 is the only non-development version that is not EOL.
I imagine that 9.18 will enter the "bind-esv" state when 9.20 is
released. 9.20 will probably trigger a switch at the time of release.
I would keep a close eye on this and perhaps check what is currently
provided be
Hi Brian,
> We’ve been using the ISC BIND 9 COPR repositories at
> https://copr.fedorainfracloud.org/coprs/isc/ for a few years now, but I had a
> question – is there a planned date to update the “bind-esv” channel to
> provide BIND 9.18 rather than BIND 9.16? Since 9.16 is now EOL we’ve
> sw
Have you considered scheduling the change in version published in each
COPR repository so it doe /not/ coincide with the release of a new
version of BIND?
I have some hosts tied to the COPR for BIND-ESV, and some tied to BIND.
I hit a stumbling block during the last "roll over" event, and it t
If 9.16 was EOL at the end of April:
https://kb.isc.org/docs/bind-9-end-of-life-dates Help me understand why ESV
wasn't rolled to 9.18 at that time or before in 2023 when it was marked as ESV?
It is difficult to explain to leadership why something was marked as EOL, but
is still active in the
The repository labels are best approximation that allow you to stay on a single repository and get the upgrades when needed.The other option was to have repositories named bind-9.16, bind-9.18 and so on, but that would require manual intervention every time there’s a version bump.The BIND 9.16 EOL
5 matches
Mail list logo
