Re: fedora libbpf upgrade to 1.0
On Fri, Nov 11, 2022 at 12:04 PM Jiri Olsa wrote: > > On Fri, Nov 04, 2022 at 09:59:49AM +0100, Jiri Olsa wrote: > > hi, > > I'm upgrading libbpf to 1.0 and because it's changing the soname it > > requires changes in dependent packages. > > > > You're receiving this email because you're maintainer of one of those > > packages (if not please kindly forward this to the maintainer). > > > > Following the guidelines for such upgrade in: > > > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#updating_inter_dependent_packages > > > > I need to create a side tag and build new libbpf and all its users in > > that. After that it will get submitted to bodhi and it will happen ;-) > > > > > > I created side tag 'f38-build-side-59808': > > https://koji.fedoraproject.org/koji/taginfo?tagID=59808 > > > > and it has libbpf 1.0 built in: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=93681960 > > > > I was able to build following packages with that: > > > > - dpdk > > - iproute > > - pcp > > - kernel-tools > > - qemu > > - xdp-tools > > > > and I can make the change myself for them (please scream if you want > > to do it yourself) > > > > I was NOT able to build following packages with libbpf 1.0: > > > >- bcc (needs 0.25 update first) > >- bpftrace (needs bcc update first) > >- below > >- knot > >- rust-libbpf-cargo > >- openvswitch > >- suricata > > > > and I'd need to ask to help with them.. which means: > > > > - adjust your package to build with libbpf 1.0 > > - build your package for 'f38-build-side-59808' > > > > > > Please note the side tag was created on Nov 4th and it seems it will > > be removed in 30 days. > > heya, > > as of today packages done: > xdp-tools > iproute > bcc > bpftrace > > > packages still need to be updated: > dpdk > iproute > pcp > kernel-tools > qemu > below > knot > rust-libbpf-cargo > openvswitch > suricata > > I'll need above owners to actually update the packages, > because I don't have rights to do that kernel-tools is done. thanks, Justin > thanks, > jirka > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fedora libbpf upgrade to 1.0
(hmm, never seemed to get the first mail...) Just recaping infos I got/researched for nixos. Fabio Valentini wrote on Fri, Nov 04, 2022 at 04:32:35PM +0100: >> I was NOT able to build following packages with libbpf 1.0: >> >>- bcc (needs 0.25 update first) note bcc upgrade in turns breaks gobpf, which indirectly breaks stuff like oci-seccomp-bpf-hook. gobpf got updated in https://github.com/iovisor/gobpf/pull/311 (unreleased, but we don't package it directly so we probably don't care) oci-seccomp-bpf-hook got updated with it in v1.2.8 so that will need an update. Didn't check if there are other reverse dependencies on gobpf in fedora. This one is backwards compatible, so the hook can be updated first with no side effect. >>- bpftrace (needs bcc update first) (update with bcc 0.25 works, so just needs updating together with bcc. Conversely older bpftrace does not work with bcc 0.25 iirc so it's not just one after the other, but both together...) >>- knot knot got fixed in 3.2.1 and also "just" needs to be updated. https://gitlab.nic.cz/knot/knot-dns/-/tags/v3.2.1 >>- suricata suricata got fixed in https://github.com/OISF/suricata/pull/7884 included in 7.0.0-beta1 last week, so will probably need to wait for an actual release... >>- below >>- rust-libbpf-cargo >>- openvswitch (didn't see/check these for nixos) -- Dominique ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fedora libbpf upgrade to 1.0
On Fri, Nov 04, 2022 at 09:59:46AM +0100, Jiri Olsa wrote: > hi, > I'm upgrading libbpf to 1.0 and because it's changing the soname it > requires changes in dependent packages. > > You're receiving this email because you're maintainer of one of those > packages (if not please kindly forward this to the maintainer). > > Following the guidelines for such upgrade in: > > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#updating_inter_dependent_packages > > I need to create a side tag and build new libbpf and all its users in > that. After that it will get submitted to bodhi and it will happen ;-) > > > I created side tag 'f38-build-side-59808': > https://koji.fedoraproject.org/koji/taginfo?tagID=59808 > > and it has libbpf 1.0 built in: > https://koji.fedoraproject.org/koji/taskinfo?taskID=93681960 > > I was able to build following packages with that: > > - dpdk > - iproute > - pcp > - kernel-tools > - qemu > - xdp-tools > > and I can make the change myself for them (please scream if you want > to do it yourself) > > I was NOT able to build following packages with libbpf 1.0: > >- bcc (needs 0.25 update first) >- bpftrace (needs bcc update first) >- below >- knot >- rust-libbpf-cargo >- openvswitch >- suricata > > and I'd need to ask to help with them.. which means: > > - adjust your package to build with libbpf 1.0 > - build your package for 'f38-build-side-59808' > > > Please note the side tag was created on Nov 4th and it seems it will > be removed in 30 days. > > Please let me know if you have any questions. > > thanks a lot for your help, > jirka > Hi Jiri, Thanks for taking care of this. As for iproute, please go ahead with the necessary changes. Thanks, Andrea ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fedora libbpf upgrade to 1.0
On Fri, Nov 4, 2022 at 9:59 AM Jiri Olsa wrote: > > hi, > I'm upgrading libbpf to 1.0 and because it's changing the soname it > requires changes in dependent packages. (snip) > I was NOT able to build following packages with libbpf 1.0: > >- bcc (needs 0.25 update first) >- bpftrace (needs bcc update first) >- below >- knot >- rust-libbpf-cargo >- openvswitch >- suricata As far as I know, rust-libbpf-cargo and below will need an update for the Rust bindings for libbpf (which is not ready yet), so please just ignore these for now. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
