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 took
me a a bit to figure out if it was due to the switch of BIND-ESV from
9.11 - > 9.16 in the repository, or the switch from 9.16.x -> 9.16.y in
the code-release.
If we could have the version published in the BIND-ESV repository
advance to the same version which was most recently published in BIND
repository (i.e. ship 9.18.x in BIND, a couple of weeks later roll
BIND-ESV to 9.18.x and BIND to 9.20.x, and a couple of weeks later
release 9.18.y and 9.20.y), then problems with the COPR "roll over"
would be a little more obvious.
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
On 6/17/2024 2:32 AM, Michał Kępień wrote:
While I don't have a specific date for you, we plan to do such a
"rollover" again when BIND 9.20.1 or 9.20.2 gets released, i.e. in about
2-3 months from now. We will definitely roll all three repositories at
the same time, i.e.:
- "bind-esv" will move from 9.16 to 9.18,
- "bind" will move from 9.18 to 9.20,
- "bind-dev" will move from 9.19/9.20 to 9.21.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
