Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

2024-06-17 Thread Darren Ankney 
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 before executing `dnf upgrade` in the coming weeks.

Thank you,
Darren Ankney

On Fri, Jun 14, 2024 at 10:58 AM Sebby, Brian A. via bind-users
 wrote:
>
> No, I haven’t run BIND on Solaris in years – this question is regarding the 
> EPEL repos that ISC provides that can be used by CentOS and RHEL.  I just 
> mentioned Solaris because there were no binary releases back then, and to 
> thank ISC since it’s a lot easier to install BIND from the EPEL packages 
> rather than building from source.
>
>
>
>
>
> Brian
>
>
>
> --
>
> Brian Sebby (he/him/his)  |  Lead Systems Engineer
>
> Email: se...@anl.gov  |  Information Technology Infrastructure
>
> Phone: +1 630.252.9935|  Business Information Services
>
> Cell:  +1 630.921.4305|  Argonne National Laboratory
>
>
>
> From: Stacey Marshall 
> Date: Friday, June 14, 2024 at 4:09 AM
> To: Sebby, Brian A. 
> Cc: bind-users@lists.isc.org 
> Subject: Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV 
> transition
>
> On 14 Jun 2024, at 0: 32, Sebby, Brian A. via bind-users wrote: > I spent 
> years having to compile BIND myself on Solaris Curious, Solaris 11. 4 
> provides a recent 9. 18 ESV release. Though not the monthly drops that ISC 
> have been providing for
>
> ZjQcmQRYFpfptBannerStart
>
> This Message Is From an External Sender
>
> This message came from outside your organization.
>
>
>
> ZjQcmQRYFpfptBannerEnd
>
> On 14 Jun 2024, at 0:32, Sebby, Brian A. via bind-users wrote:
>
>
>
> > I spent years having to compile BIND myself on Solaris
>
>
>
> Curious, Solaris 11.4 provides a recent 9.18 ESV release.
>
> Though not the monthly drops that ISC have been providing for a while,
>
> is that what you wanted?
>
>
>
>
>
>
>
> Mr. Stacey Marshall - Principal Software Engineer
>
> Oracle Global Services Limited
>
> --
> 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
-- 
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

Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

2024-06-17 Thread Michał Kępień 
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 
> switched to using the stable channel to get 9.18, but I just want to make 
> sure that we switch back to the ESV channel once it provides 9.18 so we don’t 
> accidentally switch to a new version once 9.20 becomes the new stable release.

If you have been using our repositories for a few years indeed, you
might remember that such a switch already happened about two years ago,
when "bind-esv" moved from 9.11 to 9.16 (and the other two repositories
were "rolled over" accordingly).

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.

If you would like to see how things turned out in the past in a similar
situation, please consult the lists of past builds in all our Copr
repositories:

  - https://copr.fedorainfracloud.org/coprs/isc/bind-esv/builds/
  - https://copr.fedorainfracloud.org/coprs/isc/bind/builds/
  - https://copr.fedorainfracloud.org/coprs/isc/bind-dev/builds/

Hope this helps,

-- 
Best regards,
Michał Kępień
-- 
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

Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

2024-06-17 Thread John Thurston 
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 Thurston907-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

Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

2024-06-17 Thread Robert Wagner 
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 pipeline.

The rollover plan and the graphic ISC's Software Support Policy and Version 
Numbering do not seem to match.

Robert Wagner



From: bind-users  on behalf of John Thurston 

Sent: Monday, June 17, 2024 11:19 AM
To: bind-users@lists.isc.org 
Subject: Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV 
transition

This email originated from outside of TESLA

Do not click links or open attachments unless you recognize the sender and know 
the content is safe.

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 Thurston907-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

Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

2024-06-17 Thread Ondřej Surý 
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 means there will be no further updates, it doesn’t mean that the version is broken the moment we mark it as EOL.It is difficult to explain to leadership why something was marked as EOL, but is still active in the pipeline.I don’t understand. Are you saying that you can’t upgrade to BIND 9.18 because of how the repositories are structured or named?The repositories are provided for the convenience and you can still build your own binaries or packages if those are not convenient for you.Ondrej--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.On 17. 6. 2024, at 20:24, Robert Wagner  wrote:






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 pipeline.




The rollover plan and the graphic 
ISC's Software Support Policy and Version Numbering do not seem to match.




Robert Wagner








From: bind-users  on behalf of John Thurston 
Sent: Monday, June 17, 2024 11:19 AM
To: bind-users@lists.isc.org 
Subject: Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition
 


This email originated from outside of TESLA


Do not click links or open attachments unless you recognize the sender and know the content is safe.

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 Thurston907-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 listISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.bind-users mailing listbind-users@lists.isc.orghttps://lists.isc.org/mailman/listinfo/bind-users-- 
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