https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #6 from Jiri Olsa <jolsa(a)redhat.com> ---
(In reply to Iñaki Ucar from comment #5)
(In reply to Jiri Olsa from comment #3)
> however, upstream team decided to keep and maintain GitHub libbpf
> sources (which are regirarly sync from kernel tree) to maintain
> compatibility in between distributions and mainly to have stable
> relases of libbpf based on github tree tags rather then on random
> kernel versions (from libbpf point of view)
But that GitHub mirror follows bpf-next, right? So the question is whether
right
it could happen that an update of the standalone libbpf has a soname
bump
that makes it incompatible with the kernel versions packaged in Fedora
(which cannot happen if libbpf is a subpackage of kernel-tools, because it
has the same versioning and provides from the same "snapshot").
well at the moment nothing depends on libbpf and libbpf itself
checks on kernel features before using them, so I don't see any
possible incompatibility issue
new libbpf has the 'Epoch:1' set, so it takes over old libbpf smoothly
jirka
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component