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.
| Project | Latest release | Status |
|---|---|---|
| SNode.C | 2.0.0 · r10 | SNode.C status → |
| MQTTSuite | 1.0.2 · r10 | MQTTSuite status → |
- Choose a project above; its status page shows the latest captured release and the packages actually available for each target.
- Open your distribution guide below and check its requirements, including CRB/EPEL on Rocky Linux.
- Choose complete sets or selected packages before installing. The guide provides both routes and manual signed-repository setup; dependencies are installed automatically.
Select the guide matching your installed distribution, release and package architecture. Each guide covers requirements, quick installation, manual repository setup and updates. To install selected components rather than the complete sets, use the project catalogs.
The supported release and architecture matrix is generated from the publisher's target definitions. Availability is reported per project and target.
| Distribution | 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 |
The key guide identifies each verification key, its supported distributions, fingerprints and installation method. Keys do not vary by architecture. Keep signature verification enabled.
Read installation troubleshooting for repository, key and dependency problems. For an ongoing build or an older version still available, open project status.
Publication architecture explains signing, revisions, status semantics and documentation ownership. Maintainer operations live in DistributionPackages.
Report installation issues in Packages. Documentation and publisher changes belong to DistributionPackages. Do not edit generated feeds, keys or status pages by hand.