Hi Faidon,

Quick update: 0.17.1 was released (2026-07-06) and carries the symbol
versioning natively, so the a/b question from my last mail is moot -- no
debian/patch is needed. I've prepared 0.17.1-1 and opened a Salsa MR:

https://salsa.debian.org/debian/wasmedge/-/merge_requests/2

Summary of the update:
 - Plain 0.17.1-1 (no +dfsg; upstream dropped the only excluded file, so
 the pristine tarball is DFSG-compliant).
 - debian/libwasmedge0.symbols regenerated for the symbol-versioned ABI:
 every export now under @WASMEDGE_0.16, and the five limit functions
 also export @WASMEDGE_0.17 with an @WASMEDGE_0.16 compat alias. SONAME
 stays libwasmedge.so.0, so a 0.16 consumer like crun keeps working
 without a rebuild.
 - No debian/patches needed.
 - Built clean in a sid container (arm64): dpkg-buildpackage OK, empty
 dpkg-gensymbols diff, lintian no E/W. The symbols were regenerated on
 arm64, so amd64 remains the authoritative run -- yours, as you offered.

Ready for your review whenever it suits.

Thanks,
Vincent
WasmEdge upstream / Second State

Reply via email to