Arch Linux User Repository

My build don't have this dependency 🤷‍♂️

[k0ste@host /]$ sudo ldd /usr/bin/zebra
        linux-vdso.so.1 (0x00007fe5e86d1000)
        libfrr.so.0 => /usr/lib/libfrr.so.0 (0x00007fe5e8000000)
        libunwind.so.8 => /usr/lib/libunwind.so.8 (0x00007fe5e8695000)
        libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x00007fe5e8665000)
        libprotobuf-c.so.1 => /usr/lib/libprotobuf-c.so.1 (0x00007fe5e865a000)
        libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007fe5e828f000)
        libcap.so.2 => /usr/lib/libcap.so.2 (0x00007fe5e864e000)
        libyang.so.2 => /usr/lib/libyang.so.2 (0x00007fe5e7ec0000)
        libpcre2-posix.so.3 => /usr/lib/libpcre2-posix.so.3 (0x00007fe5e8647000)
        liblua.so.5.4 => /usr/lib/liblua.so.5.4 (0x00007fe5e7e7b000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007fe5e7d83000)
        libjson-c.so.5 => /usr/lib/libjson-c.so.5 (0x00007fe5e827b000)
        libatomic.so.1 => /usr/lib/libatomic.so.1 (0x00007fe5e8270000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007fe5e7b93000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fe5e86d3000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fe5e7b5f000)
        libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007fe5e7ab3000)
[k0ste@host /]$

"For what binary?"

At least /usr/bin/ospfd and /usr/bin/zebra.

[root@igw-elite ~]# ldd /usr/bin/zebra
linux-vdso.so.1 (0x00007ffd351a3000)
libfrr.so.0 => /usr/lib/libfrr.so.0 (0x00007df487977000)
libunwind.so.8 => /usr/lib/libunwind.so.8 (0x00007df48795c000)
libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x00007df48792c000)
libprotobuf-c.so.1 => /usr/lib/libprotobuf-c.so.1 (0x00007df487921000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007df4877b0000)
libcap.so.2 => /usr/lib/libcap.so.2 (0x00007df4877a4000)
libyang.so.3 => /usr/lib/libyang.so.3 (0x00007df48764e000)
libpcre2-posix.so.3 => /usr/lib/libpcre2-posix.so.3 (0x00007df487649000)
liblua.so.5.4 => /usr/lib/liblua.so.5.4 (0x00007df487604000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007df48750c000)
libjson-c.so.5 => /usr/lib/libjson-c.so.5 (0x00007df4874f8000)
libatomic.so.1 => /usr/lib/libatomic.so.1 (0x00007df4874ed000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007df4872fb000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007df487e17000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007df4872c7000)
libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007df48721b000)
libxxhash.so.0 => /usr/lib/libxxhash.so.0 (0x00007df487210000)

"xxhash" is missing as a dependency

For what binary?

Hi. I can confirm that FRR works with current "libyang" - 3.12.2-1.

But, "xxhash" is missing as a dependency.

@Frankkkkk Thanks for the great work.

Edit: it seems like dependencies declared with version restrictions (e.g. libyang<3.0.0) do not work with provides entries (e.g. provides=('libyang')). So I guess this should be done instead:

diff --git a/PKGBUILD b/PKGBUILD
index b1a318d..8b772f8 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@ arch=('x86_64' 'aarch64' 'armv7h')
 url="https://frrouting.org"
 license=('GPL2')
 depends=('libcap' 'libnl' 'readline' 'ncurses' 'perl' 'pam' 'json-c' 'net-snmp'
-    'rtrlib' 'libyang>=2.1.128' 'libunwind' 'c-ares' 'protobuf-c' 'pcre2'
+    'rtrlib' 'libyang2>=2.1.128' 'libunwind' 'c-ares' 'protobuf-c' 'pcre2'
     'lua53' 'sqlite')
 makedepends=('gcc' 'bison' 'perl-xml-libxml' 'python-sphinx')
 checkdepends=('python-pytest')

BTW: I've published libyang2 https://aur.archlinux.org/packages/libyang2 which is fixed to the latest 2 SO. It's an alternative to the current broken libyang and makes frr work :-)

Thanks k0ste!

FRR isn't just about BGP ... it has versatile uses. Don't think for the user. I have nothing more to add. Thanks for your time.

If you use the AUR repo and service it like I do, for example YAY - https://github.com/Jguer/yay, then pacman https://wiki.archlinux.org/title/pacman is still used and I set IgnorePkg=libyang in it so it doesn't force me to update libyang to a new version. If the user doesn't know this, then FRR can break it and I'm pointing this out to you.

If a user appears who will configure a BGP router and build packets on the same router by some manager, and at the same time he does not know what he is doing, then these are the personal problems of this person and/or the problems of his employer. I can’t imagine anyone doing this, much less rolling out packets to a router without prior testing

@k0ste Slack - https://frrouting.org/community/

If you use the AUR repo and service it like I do, for example YAY - https://github.com/Jguer/yay, then pacman https://wiki.archlinux.org/title/pacman is still used and I set IgnorePkg=libyang in it so it doesn't force me to update libyang to a new version. If the user doesn't know this, then FRR can break it and I'm pointing this out to you.

@vecino

Precisely because FRR 10.0 cannot be compiled with the new libyang 2.2.8, it is clear that this will cause problems for people who automatically migrate to this version.

Just don't migrate

Watch more Slack frr community. Then you'll be in the loop and know what's going on.

I don't know what is Slack. They can write me on the vk, if wanna

That's why I've disabled libyang updates in my pacman

Don't know what is mean. pacman isn't work with AUR. You can upgrade package if you are not put it into repository

„It should be noted that the libyang developers changed the major version of the SO as it is not backward compatible with the previous libyang v2 release. I believe the recommendation is to have the package named after the SO major version (i.e., so there should be libyang, libyang2 and libyang3 packages)."

If someone want do this work - he can. May be that's you?