Bug 2431444 - retis version 1.6.3 is available
Summary: retis version 1.6.3 is available
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: retis
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Antoine Tenart
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-20 23:11 UTC by Fabio Valentini
Modified: 2026-02-09 08:29 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-02-09 08:29:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabio Valentini 2026-01-20 23:11:44 UTC
It appears that release-monitoring.org was not correctly set up for retis:
https://release-monitoring.org/project/377632/

This was missing a mapping to the Fedora package (which I have added now).

I found that this update is missing from Fedora as part of investigating action items for a pending Change Proposal: https://fedoraproject.org/wiki/Changes/Bump_Minimum_Rust_Bindgen_To_v0.72

retis v1.6.0+ has already bumped its bindgen dependency to v0.72. It would be great if this could land in Fedora Rawhide / F44+, otherwise the bindgen dependency will likely need to get patched to v0.72.1 downstream.


Reproducible: Always

Comment 1 Antoine Tenart 2026-01-21 08:47:53 UTC
Thanks for fixing release monitoring!

I did try to bump Retis to 1.6+ but it has an hard requirement on libbpf-rs >= 0.25 and in Fedora we still have 0.24. In order to bump libbpf-rs a number of other packages have to be updated too, which makes the process quite complex and time consuming. I did try and opened a PR, https://src.fedoraproject.org/rpms/rust-libbpf-rs/pull-request/2, but needed some answers and that never got attraction. I have to admit I postponed getting back to it for a while... Now I'm wondering when to make the effort as Retis 1.7 should be coming in the next months and will depend on libbpf-rs 0.26+ (https://github.com/retis-org/retis/issues/572).

Anyway we can try to restart the effort, either for bumping to 1.6 then 1.7, or preparing 1.7 directly. Could you look at the two questions in the libbpf-rs PR (1. How to tackle many updates depending on a pre-requisite? 2. Is the way I'm testing things locally the right way?). Thanks!

Comment 2 Fabio Valentini 2026-01-21 15:59:38 UTC
Oh, I didn't realize that this might be tangled up with the libbpf-rs updates.
I'll try to get those un-stuck ASAP.

Comment 3 Antoine Tenart 2026-01-30 15:09:00 UTC
(In reply to Fabio Valentini from comment #2)
> Oh, I didn't realize that this might be tangled up with the libbpf-rs
> updates.
> I'll try to get those un-stuck ASAP.

Thanks for upgrading libbpf-rs to 0.25! As discussed in the other bz I tried upgrading Retis while using libbpf-rs 0.25, that looks possible but there's also a requirement on libbf-cargo 0.25. Any reason it was not upgraded alongside libbpf-rs? Any plan to do so? Thanks!

Comment 4 Fabio Valentini 2026-02-05 16:25:25 UTC
libbpf-cargo 0.25.0 is now available too.

I see that v0.26.0 was now published for both libbpf-rs and libbpf-cargo. Do you plan to need that, or is 0.25.0 OK for now?

Comment 5 Antoine Tenart 2026-02-06 16:15:04 UTC
(In reply to Fabio Valentini from comment #4)
> libbpf-cargo 0.25.0 is now available too.

Thanks!

> I see that v0.26.0 was now published for both libbpf-rs and libbpf-cargo. Do
> you plan to need that, or is 0.25.0 OK for now?

For Retis 1.6.3 this should be fine, I was able to build & test it.

As far as I remember libbpf-rs/cargo 0.25 vs 0.26 doesn't impact Retis for the current stable and dev versions atm.

Comment 6 Antoine Tenart 2026-02-09 08:29:22 UTC
Retis was upgraded to 1.6.3 in f44 & Rawhide.


Note You need to log in before you can comment on or make changes to this bug.