Package: src:linux Severity: wishlist X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ker...@lists.debian.org
libbpf source has moved to a separate github repo but keeps the kernel as the true/first source, and updating github repo when release is ready. In Steve's word the problem they faced is: > The problem I'm now having is that I'm looking at fixing and updating > some of the code in this library, and since library versioning is > critical for applications that depend on it, we need to have a way to > update the versions, and this does not correspond with the Linux > versions. So, looking at libbpf github repo at [1], I can see libbpf has already released v0.0.6 but we only have v0.0.5 in Debian and there is no way to update that unless the kernel is updated to v5.5+. And looking at the kernel repo I can see libbpf people are working on v0.0.7. The full discussion is at [2]. Do we package libbpf from their github repo independent of the kernel update? Then we will need to remove the libbpf building bits from the Debian kernel source and create a separate package for libbpf. And so, it will be great if kernel team will like to package and maintain it, if not, then I will be happy to do it. Please reject this bug report if you think libbpf should not be done separately and should live inside kernel source package. [1]. https://github.com/libbpf/libbpf [2]. https://lore.kernel.org/lkml/20200102234950.GA14768@krava/ -- Regards Sudip
