You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steinar H. Gunderson has reported in Debian (https://bugs.debian.org/972758) that the 0.7 release broke the ABI in commit 0f05173 when adding the kflags member to struct io_uring_cq. I think at this point the best way forward might be to just quickly release 2.0 and request any downstream to avoid 0.7 and package that instead?
The text was updated successfully, but these errors were encountered:
Oops yes, that is unfortunate. As 0.7 is 3 months old, it's definitely out there. I guess people just recompiled, I hadn't heard any complaints.
In any case, I don't think we need to be quick on the next release, we're already more than 3 months into this. For 2.0, at least the padding is there for future cases.
Hi!
Steinar H. Gunderson has reported in Debian (https://bugs.debian.org/972758) that the 0.7 release broke the ABI in commit 0f05173 when adding the kflags member to struct io_uring_cq. I think at this point the best way forward might be to just quickly release 2.0 and request any downstream to avoid 0.7 and package that instead?
The text was updated successfully, but these errors were encountered: