Package: wasmedge Version: 0.16.1+dfsg-1 Severity: wishlist X-Debbugs-Cc: [email protected]
Control: tags -1 + patch Dear Maintainer, Upstream WasmEdge 0.17.0 was released on 2026-05-18: https://github.com/WasmEdge/WasmEdge/releases/tag/0.17.0 I am a WasmEdge upstream developer (Second State). I have prepared and validated a packaging update to 0.17.0-1 and attach the changes as a git format-patch series against debian/latest. (I intended to open a Salsa MR, but my Salsa account is still pending admin approval; I will reference this bug from the MR once that clears.) Packaging notes: * Drop the +dfsg repack: upstream removed the only excluded file (utils/android/app/gradle/wrapper/gradle-wrapper.jar), so the pristine tarball is DFSG-compliant. Repacksuffix dropped from debian/watch, Files-Excluded dropped from debian/copyright. uscan with the updated watch file produces wasmedge_0.17.0.orig.tar.xz directly. Version ordering is safe (0.17.0-1 > 0.16.1+dfsg-1), no epoch needed. * debian/libwasmedge0.symbols updated from the dpkg-gensymbols diff: 12 new C symbols @0.17.0 (RunMode, Limit-context and RegisterImportWithAlias families); 3 C++ WasmEdge::Allocator symbols changed uint32 -> uint64 (Memory64 support). * debian/rules: generate a VERSION file from DEB_VERSION_UPSTREAM before configure (removed in clean), so `wasmedge --version` reports the real version instead of "0.0.0-unreleased". This also affects the current 0.16.1+dfsg-1 package in unstable. * No debian/patches needed. ABI/API impact (please review): * SONAME is unchanged: libwasmedge.so.0 (upstream WASMEDGE_CAPI_SOVERSION is still "0"; the release notes' "SOVERSION bumped to 0.1.1" actually refers to WASMEDGE_CAPI_VERSION, the file version). No package rename. * However, upstream made breaking C API changes under the same SONAME: the WasmEdge_Limit struct was replaced by a limit context, and several functions keep their symbol names with changed signatures. The C++ Allocator symbols changed as noted above. crun (the only external reverse dependency of libwasmedge0) should be rebuilt and checked after acceptance. As an upstream developer I have raised the need for a proper SONAME bump on C API breaks with the project: https://github.com/WasmEdge/WasmEdge/issues/4933 * Plugin API_VERSION bumped 4 -> 5 upstream; not applicable to this packaging (plugins are disabled via -DWASMEDGE_BUILD_PLUGINS=OFF). Validation performed: * dpkg-buildpackage -us -uc -b in a debian:sid container (arm64): clean build from a pristine tree; all 5 binary packages built. * lintian on the .changes: no findings. * Smoke test: installed wasmedge + libwasmedge0; `wasmedge --version` prints "wasmedge version 0.17.0"; the new --run-mode flag is present. * Limitations: this was not a clean sbuild chroot, the build arch was arm64 (not amd64), and the test suite was skipped (DEB_BUILD_OPTIONS=nocheck). An sbuild run on amd64 with tests is still advisable before upload. Intent: After this lands in unstable, the Ubuntu development series currently carries no delta, so it should auto-sync (or a sync can be requested if a freeze intervenes). A sponsor upload is welcome if more convenient. Happy to adjust anything or push the branch to Salsa once my account is approved. Thanks for maintaining wasmedge! Vincent WasmEdge upstream / Second State
0001-Drop-dfsg-repack-update-changelog-for-0.17.0-1.patch
Description: Binary data
0002-Update-symbols-for-0.17.0-fix-version-string-via-VER.patch
Description: Binary data
