Signed packages for the SNode.C ecosystem. Choose a project and distribution, install using its signed package source, and inspect availability separately from ongoing builds.
Documentation index: installation guides, package catalogs, status meanings and troubleshooting.
| Project | Latest release | Status |
|---|---|---|
| SNode.C | 2.0.0 · r16 | SNode.C status |
| MQTTSuite | 1.0.2 · r19 | MQTTSuite status |
Select the guide matching your installed distribution, release and package architecture. Each guide covers requirements, quick installation, manual repository setup and updates.
The supported releases and architectures are generated from the publisher's target definitions. Package availability per project, release and architecture is on the status pages.
| Distribution guide | Releases | Architectures |
|---|---|---|
| OpenWrt | 24.10, 25.12 | 25 per release (names can differ) |
| Raspberry Pi OS | bookworm, trixie | arm64 |
| Debian | trixie, forky, sid | amd64, arm64, armhf, riscv64 |
| Ubuntu | noble, resolute | amd64, arm64 |
| Rocky Linux | 9, 10 | aarch64, x86_64 |
| Fedora | 43, 44 | aarch64, x86_64 |
Verify downloads with the signing keys for your package manager. Keys are shared across architectures; keep signature verification enabled.
Diagnose installation errors, or compare available packages and replacement builds on project status.
Packages is the generated destination for signed feeds, installation guides and recorded build status; DistributionPackages owns publication. See the organization workflow graph for the build, signing and dependent-build chain.
Read the column meanings and publication model. Maintainer operations belong to DistributionPackages.
Report installation issues in Packages. Documentation and publisher changes belong to DistributionPackages. Do not edit generated feeds, keys or status pages by hand.