13792 2020-02-15 05:08:40 +0000 bind is even = stable, need to upgrade to 9.16.x 2020-03-05 16:03:05 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 3.1 x86 Multiple RESOLVED WONTFIX High normal 3.1 M3 1 tim.orling akuster808 akuster bunk meta.mr.watcher meta.watcher randy.macleod richard.purdie --- --- Don't know oldest_to_newest 86452 0 tim.orling 2020-02-15 05:08:40 +0000 bind now follows an even-is-stable release pattern, we have 9.11 and the latest stable is 9.14.10 https://downloads.isc.org/isc/bind9/9.14.10/RELEASE-NOTES-bind-9.14.10.html 86455 1 akuster 2020-02-15 07:18:14 +0000 They do stable once a year and extended support on certain versions like 9.11. BIND 9.11 is an Extended Support version, and will be supported until December, 2021. So does OE want latest or long term versions? 9.14 will be EOL by the end of this year. Please see: https://kb.isc.org/docs/aa-00896 86457 2 bunk 2020-02-16 01:02:59 +0000 The recipe already follows the ESV versions: # stay at 9.11 until 9.16, from 9.16 follow the ESV versions divisible by 4 UPSTREAM_CHECK_REGEX = "(?P<pver>9.(11|16|20|24|28)(\.\d+)+(-P\d+)*)/" I would recommend against switching to short-term stable releases like 9.14. 86467 3 tim.orling 2020-02-18 19:57:55 +0000 Thank you both for the clarity. I agree with the extended support sentiment, so we should wait until 9.16. 86468 4 akuster 2020-02-18 20:12:44 +0000 one thing not talked about if we should have the latest stable bind recipe that folks could enable via PREFERRED-VERSION. I have been thinking about have one just to keep up the build breakages as things move along in the bind world. It might make transitions easier between EOS versions. 86469 5 bunk 2020-02-18 20:23:25 +0000 (In reply to comment #4) > one thing not talked about if we should have the latest stable bind recipe > that folks could enable via PREFERRED-VERSION. > > I have been thinking about have one just to keep up the build breakages as > things move along in the bind world. The common build breakage are new bind versions breaking the build of the dhcp recipe. Which usually needs fixing of dhcp. > It might make transitions easier between EOS versions. Who will do the additional work of maintaining the non-default version? The overall amount of work increases when maintaining two versions, and problems seen with 9.14 might already have been fixed by upstream for 9.16. 86506 6 richard.purdie 2020-02-19 23:47:46 +0000 Could be a case for enabling and testing in poky-bleeding? :) 86522 7 tim.orling 2020-02-20 15:48:59 +0000 Although I would love to live in the world where we could do the poky-bleeding, I think reality is we continue with status quo. Meaning we stay with 9.11 until 9.16 is out. Closing. 86588 8 akuster808 2020-02-26 00:19:22 +0000 Bind 9.16.0 just dropped. Do we want to get this in 3.1 ? 86589 9 akuster808 2020-02-26 00:55:25 +0000 it needs libuv package which is in meta-oe 86590 10 akuster808 2020-02-26 01:33:05 +0000 needs to check 3 OE specific patches. Here is what I have so far. https://git.openembedded.org/openembedded-core-contrib/log/?h=akuster/bind_9.16_wip 86604 11 randy.macleod 2020-02-27 15:39:22 +0000 Armin agreed to do this. 86634 12 akuster808 2020-03-01 17:09:44 +0000 patches sent https://patchwork.openembedded.org/patch/170608/ https://patchwork.openembedded.org/patch/170609/ 86667 13 akuster 2020-03-05 16:03:05 +0000 This bind update requires a newer dhcp to be released which one has not. This therefore will not make 3.1