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 · r15 | SNode.C status |
| MQTTSuite | 1.0.2 · r15 | MQTTSuite status |
Start with your installed system, not an ongoing build: use the distribution chooser, check the guide’s requirements, then choose complete sets or selected packages. Follow its Check and Next steps to confirm installation and configure your applications. Status pages are optional: consult them to compare available packages with a replacement build.
Select the guide matching your installed distribution, release and package architecture. Each guide covers requirements, quick installation, manual repository setup and updates.
The supported release and architecture matrix is generated from the publisher's target definitions. Availability is reported per project and target.
| Distribution guide | Releases | Architectures |
|---|---|---|
| OpenWrt | 24.10, 25.12 | 25 per release (names can differ) |
| Raspberry Pi OS | bookworm, trixie | arm64 |
| Debian | forky, sid, trixie | amd64, arm64, armhf, riscv64 |
| Ubuntu | noble, resolute | amd64, arm64 |
| Rocky Linux | 10, 9 | 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.
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.