I am a bit puzzled about the state of the library libyang, used by frr.
The frr/package.toml at this time (2025-11-11):
…wants to check out and build libyang v3.4.2 along with frr stable/10.2
However, the corresponding VyOS x86 live build (2025-11-11) has libyang2 installed, not libyang3. This is from an actual live build 2025-11-11 x86 boot:
vyos@vyos:~$ ls -l /usr/lib/*/libyang*
lrwxrwxrwx 1 root root 17 May 4 2021 /usr/lib/x86_64-linux-gnu/libyang.so.2 -> libyang.so.2.46.3
-rw-r–r-- 1 root root 1290216 May 4 2021 /usr/lib/x86_64-linux-gnu/libyang.so.2.46.3
vyos@vyos:~$ dpkg-query -l libyang2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-==================================>
ii libyang2:amd64 2.1.148-1 amd64 parser toolkit for IETF YANG data >
vyos@vyos:~$
vyos@vyos:~$ show version | grep 2025
Version: VyOS 2025.11.11-0020-rolling
Built on: Tue 11 Nov 2025 00:20 UTC
vyos@vyos:~$
It is not possible to have libyang2 and libyang3 installed at the same time as they conflict with each other, so what is going on here?
Per Debian 12 — FRR latest documentation they want libyang 2.1.128 at this time (see their “DEB packages are available as CI artifacts here.” link), so having libyang3 (v3.4.2) in the package.toml seems suspicious.