Great, thank you guys, looking forward for it.
(I mistyped FC35 but meant FC36, not working with FC35 and not aware what's the state there.)
 
27.10.2022, 10:17, "Jiri Olsa" <olsaj...@gmail.com>:

On Thu, Oct 27, 2022 at 07:45:39AM +0900, Dominique Martinet wrote:

 +Jiri in To
 
 Dave Stux wrote on Wed, Oct 26, 2022 at 09:39:23PM -0000:
 > I have opened bugs relating to bcc, and I see no reply on them.
 > Currently, at least in my testing, the state of ,pst pf the bcc dependent tools in F35 is broken.
 > Examples:
 > https://bugzilla.redhat.com/show_bug.cgi?id=2127642
 > https://bugzilla.redhat.com/show_bug.cgi?id=2057139
 
 bcc 0.22 is quite old and I think you have it right in this bug: just updating
 to a newer bcc version would likely fix all these issues.
 
 fedora 37+ have bcc 0.24 which is more reasonable and probably works, so
 I guess it'd just be a matter of pushing it for f35/36 as well.
 
 (note there's a bcc 0.25 that might be good for rawhide, but it breaks
 API on bcc_prog_load_xattr() breaking e.g. older gobpf or bpftrace,
 see https://github.com/iovisor/bpftrace/issues/2340 , so that one should
 not be backported -- but I'm not aware of any such problem for bcc 0.22
 to 0.24)
 
 > I have filled non-responsive bug, but there's no reply on it too:
 > https://bugzilla.redhat.com/show_bug.cgi?id=2136222
 >
 > Can anyone contact Jiri Olsa or update if he is out on vacation?
 > Is there an additional package maintainer?


hi,
sorry for delay.. I talked to Jerome on Monday and he will
take care of that

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

Reply via email to