Fedora Account System
Red Hat Associate
Red Hat Customer
retis failed to build from source in Fedora rawhide/f44 https://koji.fedoraproject.org/koji/taskinfo?taskID=141204676 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild Please fix retis at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, retis will be orphaned. Before branching of Fedora 45, retis will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 2126941 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 2126942 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 2126943 [details] state.log
This is actually a libbpf error, https://github.com/libbpf/libbpf/commit/d88ca951338a765bcb28672dc7b1221fde8e4ae4 Retis consumes it as part of libbpf-rs which does from libbpf-sys. This is fixed since https://github.com/libbpf/libbpf-rs/releases/tag/v0.26.0-beta.1 (in Retis https://github.com/retis-org/retis/issues/572). Fixing this is basically a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2431444 as the libbpf-rs/sys bump was done in v1.6.3. @decathorpe you mentioned upgrading libbpf-rs on the other bz. Is that still planned? One thing I'm not sure is if we can actually use the v0.26.0-beta.1 version as it's not a "proper" release? BTW let me know if you need help on that.
> Is that still planned? Seems like you already did upgrade libbpf-rs to 0.25 :) The question still stands though, we need it to support newer versions of libbpf-sys. One option is upgrading to v0.26.0-beta.1 (see previous comment), another might be to backport the relevant commits to 0.25 (if no incompatibilities).
Actually, it seems like this FTBFS is no longer accurate. The package no longer fails to build from source in current rawhide (hence also why the CI on my PR to bump the bindgen dependency passed). I've just submitted a new build to koji. It should be possible to also submit a new build for F43 after the libbpf-sys 1.6.2 update lands in "stable" there too. If you need libbpf-rs v0.26.0-beta.1, that's something I can do (doing pre-releases just involves a bit of additional weirdness due to how cargo chooses versions during dependency resolution).
(In reply to Fabio Valentini from comment #6) > The package no longer fails to build from source in current rawhide (hence > also why the CI on my PR to bump the bindgen dependency passed). I've just > submitted a new build to koji. It should be possible to also submit a new > build for F43 after the libbpf-sys 1.6.2 update lands in "stable" there too. Thanks! > If you need libbpf-rs v0.26.0-beta.1, that's something I can do (doing > pre-releases just involves a bit of additional weirdness due to how cargo > chooses versions during dependency resolution). Given the above let me try to use libbpf-rs 0.25 for the Retis 1.6.3 update, if that does not work I'll reach out.