This issue appears to be fixed with the 2.1.128 release of libyang? https://github.com/CESNET/libyang/releases/tag/v2.1.128 On 8/25/23 12:16, Donald Sharp wrote:
All --
The latest libyang2 release 2.1.111 has an incompatible change to it's ABI and causes FRR to no longer be able to work properly with it. See this issue filed for an explanation:
https://github.com/FRRouting/frr/issues/14258 <https://github.com/FRRouting/frr/issues/14258>
Additionally it is discussed here:
https://github.com/CESNET/libyang/issues/2090 <https://github.com/CESNET/libyang/issues/2090>
Since FRR needs to make changes to its code in order for FRR to continue to use newer versions of libyang2 it is not recommended that anyone upgrade to libyang2.1.111 or later at this point in time. We currently expect to be able to make these changes for the 9.1 release.
What can you do?
If you are using FRR 8.0 or later do not upgrade to libyang2.1.111 at this point in time. If you have, please downgrade to 2.1.80 or earlier.
thanks!
donald
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog