wasmedge-debian-packaging

name	wasmedge-debian-packaging
description	Use when helping WasmEdge move an upstream release through the official Debian packaging path and into Ubuntu via Debian sync, merge, or backports. Covers Debian Salsa packaging, maintainer/sponsor handoff, Ubuntu requestsync, Launchpad sync bugs, authority boundaries, and the repo-local packaging helper.
metadata	{"short-description":"Push WasmEdge releases through Debian into Ubuntu"}

WasmEdge Debian Packaging

Use this skill when the user wants the official path for updating WasmEdge packages in Ubuntu, especially when the current Ubuntu package lags behind upstream. It can also be used by an AI agent to coordinate a release handoff, provided the agent respects the archive authority boundaries and produces reviewable artifacts instead of assuming upload rights.

Core premise: upstream WasmEdge maintainers normally cannot directly update Ubuntu archive packages. The official route is to update the Debian package first, get it accepted by a Debian Developer/Maintainer or sponsor, then let Ubuntu auto-sync or request a manual sync/merge into the Ubuntu development release. Released Ubuntu series usually require backports or SRU, not a normal feature-version update.

For detailed commands, issue templates, and decision points, read references/official-path.md.

Default Workflow

1. Verify current state using current sources:
   • upstream release: GitHub releases
   • Debian status: Debian tracker and Salsa packaging repo
   • Ubuntu status: Launchpad source package page and Ubuntu packages
   • Repology only as a downstream status dashboard, not as an official source
2. Identify whether Debian is behind upstream.