Actually, now that we are polishing the last bits of 9.20.0 would be a good
time to start
9.16->9.18 transition.
The current plan is that on next Wednesday (next week), the bind-esv
repositories will
be bumped from 9.16 to 9.18, the 'bind' repository will stay on 9.18 until 9.20
is released,
an
> 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,
2 matches
Mail list logo
