Your message dated Tue, 08 Sep 2026 08:34:00 +0000
with message-id <[email protected]>
and subject line Bug#1138857: fixed in wasmedge 0.17.1-1
has caused the Debian Bug report #1138857,
regarding wasmedge: prepared packaging update for 0.17.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1138857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1138857
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: wasmedge
Source-Version: 0.17.1-1
Done: Faidon Liambotis <[email protected]>
We believe that the bug you reported is fixed in the latest version of
wasmedge, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Faidon Liambotis <[email protected]> (supplier of updated wasmedge package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 08 Sep 2026 10:59:25 +0300
Source: wasmedge
Architecture: source
Version: 0.17.1-1
Distribution: unstable
Urgency: medium
Maintainer: Faidon Liambotis <[email protected]>
Changed-By: Faidon Liambotis <[email protected]>
Closes: 1133663 1138857
Changes:
wasmedge (0.17.1-1) unstable; urgency=medium
.
* New upstream release:
- Thanks to Zigang Lin from Second State for providing patches and
working with upstream on some of the issues below. (Closes: #1138857)
- Fixes FTBFS with GCC 16. (Closes: #1133663)
- Drop the +dfsg repack, as upstream removed the only remaining binary
artifact, see (see upstream #4495).
- Update symbols with the newly-introduced symbol versioning that retain
compatibility with <= 0.16.1, as well as the new 0.17.x symbols.
* Generate a VERSION file from DEB_VERSION_UPSTREAM, so what wasmedge
--version works again.
* Update debian/copyright to reflect a path change and year bump.
* Bump Standards-Version to 4.7.4, no changes needed.
Checksums-Sha1:
86fd3c11664cbb96fd75cae3c90c4814d604a74d 2258 wasmedge_0.17.1-1.dsc
dc285478fea2b157dcce421cf4e7a05a1eb3e3a7 3528029 wasmedge_0.17.1.orig.tar.gz
7cbbbbd9fc48a0b57e9546d749c06e0ba0237c37 11784 wasmedge_0.17.1-1.debian.tar.xz
dd151309e285bfea57b238b5f2aa60bb05208140 8939 wasmedge_0.17.1-1_amd64.buildinfo
Checksums-Sha256:
69c68f487709c954ee01976394d960d986a43ba32d17c9eeb6eeb1d4313299c7 2258
wasmedge_0.17.1-1.dsc
09107f25e9192fa698436fe3b54935ba662665383e9cdcd7aa8a7f8f16aa7dc1 3528029
wasmedge_0.17.1.orig.tar.gz
1a2287a951f80123be26b01346bf8a1fa58f7ef678e0e9ab12be95e31044657a 11784
wasmedge_0.17.1-1.debian.tar.xz
02c5594654d910e37434ce89c8562e2612cb7c2dbe92ebe0fa139470cbc75aaf 8939
wasmedge_0.17.1-1_amd64.buildinfo
Files:
423e85a539826cd9e04cff32377a5955 2258 web optional wasmedge_0.17.1-1.dsc
000d021aef03c2ce0e49ead2a307b0f8 3528029 web optional
wasmedge_0.17.1.orig.tar.gz
8d0c133b4d084b0f665bdb071a110195 11784 web optional
wasmedge_0.17.1-1.debian.tar.xz
ec9882b78b4564f5cdeecf11cb4c87ed 8939 web optional
wasmedge_0.17.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAmqfwecACgkQnQteWx7s
jw7X3Q/+LgFUwBQXWGa9N0Wq/01D13KyL9jg1FqQ7klotqXyk1xxR0wCh5GU6S4Q
ItXUKv1P72D/79CO/GaZVQKZsqkoRt+Qy8GVn0tQznWd94OSOcbZN2SZPQVNm5xp
WSS0ADxd3tcrSuWSAa0Q20Gh9BjNkcyTrszoeHs1nPj9h+t1aQE5nXBr4viI5a8Q
ssSVL1Ami5eHbEhdJtdz7L4fVGd6g/nP5dxzLzzB56xrCoNuiOjaI72vzRQl8arR
VpvD8kkZv+9LoplwJGYbN2yalwiEh/PI3AD1P0jQK2cHy5mPQSsQ3FeMK32oYJph
pHCutSK4wy8HI7nssx19+THko33xj+cT9nBK1xM4XSKnKv2y33PMrhA1BOdJXDup
rNJ2R7OUADBBJa5NxRr+GGB+zEpu5VgOnTbTyOpk7emthnAcWLOFHkVhuW3zuCKN
hr961LRdYbU6g5Pp5CMlIcxax2oejaNEaGLq3YBixzUirOIXXY80jVwZ7YVRxxHy
YoHfbMQ8HIlQQa79cwKBsardGTbJd8FusEdNQqYISPz5U79SKSsYhwSFdkC4x7Bp
Yx/rDYbKtn9UbwjuhZQBTdsVryXCgYcs6qcOYhsgCFMosTGkmCw9tkjMb/iyafPu
l5PqxGbIFw/SqZK1K1YxkW1J0eg0j4VINEJKY0DBrqfHRdAEiGs=
=zeCB
-----END PGP SIGNATURE-----
pgphJ6chBZTL6.pgp
Description: PGP signature
--- End Message ---
