> I published an updated consolidated report this morning. As you can see, > there is an ABI change due to LFS in raft/uv.h > > https://adrien.dcln.fr/misc/armhf-time_t/2024-02-22T10%3A55%3A00/compat_reports/libraft-dev/base_to_lfs/compat_report.html > > It is possible some API is not supposed to be exposed or does not appear > in a shared library or something else, and it would therefore be safe to > ignore an ABI change that abi-compliance-checker reports. Since I don't > have specific experience with this package, I can't take such decisions > and it is ultimately your call.
I think a-c-c is confused here, the symbols it is complaining about are all from libuv (maybe it got confused by multiple files called "uv.h"?). So I think this package itself is unaffected, but will require a binNMU once all the directly affected packages have been rebuilt (like ~5000 other packages or whatever it is).
