Hello Andreas, On Mon, Mar 23, 2026 at 07:55:45AM +0100, Andreas Dolp wrote: > thanks for your mail. I'm speaking for the suricata package maintainers side > and coordinated my answer with suricata maintainer Sascha (@satta).
Tnank you for your feedback. > As we understand your reqeuest, from the suricata perspective, this is just > rebuilding and bin-uploading suricata/1:8.0.4-1 on riscv64 to unstable so > that the "new" libunwind-dev with disabled C++ exception support will be > used, right? Confirmed. The practical effect (confirmed in a local test build) is that suricata will start linking libgcc_s. > For that case, there are no objections from the suricata package maintainers > side for that binNMU. Thank you for confirming. > Am I right assuming that you will do all the further coordination and the > upload, for suricata as well as for libunwind? suricata will not be uploaded. Such a binNMU must be approved and scheduled by the release team. I intend to handle the libunwind side as it needs a sourceful upload adding Breaks. > Are there any things left we have to do from the package maintainers side? Nothing I see. For now, the ball is with the release team in assessing whether the requested ABI break of libunwind is acceptable for inclusion in forky. Helmut
