The skarnet.org service manager https://git.skarnet.org/cgit/s6-rc/atom/src/include?h=main 2026-10-15T08:19:48Z 2026-10-15T08:19:48Z Laurent Bercot ska-skaware@skarnet.org 2026-10-15T08:19:48Z urn:sha1:db3fb428599c9c8fe105dcf4ba8d1c914c54cc26 If a db format upgrade is necessary, we need to compile the snapshot with the new s6-rc-compile. There's data we need to pass to it that isn't stored (options passed when committing the original set), so we store it in the db itself (patching s6-rc-compile). We modify the s6-rc-compile wrappers to pass all this metadata. Next, we will compile the snapshot. 2026-10-09T00:59:02Z Laurent Bercot ska-skaware@skarnet.org 2026-10-09T00:59:02Z urn:sha1:c71344185cc93d9322513a1d9506cb14b1c308a2 2026-10-05T18:16:38Z Laurent Bercot ska-skaware@skarnet.org 2026-10-05T18:16:38Z urn:sha1:55850e313752497880ffde33870540b0b57814c1 s6-rc-set-install is undergoing changes, it might not work properly. The rest is coming this week. 2026-10-03T02:19:00Z Laurent Bercot ska-skaware@skarnet.org 2026-10-03T02:19:00Z urn:sha1:3245c92eaa3528a4176e05ab9beaa9718afc8868 2026-10-02T02:22:28Z Laurent Bercot ska-skaware@skarnet.org 2026-10-02T02:22:28Z urn:sha1:7c93a058c8d7e21aea2aad8f3114c8422bf6faf7 In order to work across major bumps, we need to add a call to s6-rc-format-upgrade before s6-rc-update in the s6-rc-set-install sequence of commands. s6-rc-format-upgrade only works when the db is exactly the same across s6-rc versions. That means we need to have the source version of the current live set at all times, in order to compile it with the new s6-rc version before upgrading and then updating. So: 1. we take a snapshot of the source version of a set every time we commit. 2. we refuse to install if we don't have the snapshot. 3. we add s6-rc-format-upgrade to the processing chain 4. for cleanup: after installing, we delete all the snapshots of the set except the one that corresponds to the newly installed live set. This commit implements 1: taking the snapshot. It's a regular s6-rc-set-copy, using an internal name. We refactor s6-rc-set-copy and s6-rc-set-delete to have primitives we can use internally. Wait for later commits before using repo, else you'll fill your repository with snapshots that won't get cleaned up. TBD: how to store the s6-rc version in the compiled db. We probably need to add a small file in there. 2026-07-09T08:13:55Z Laurent Bercot ska-skaware@skarnet.org 2026-07-09T08:13:55Z urn:sha1:6209d961fd35c1d4e92d26c76a8ba0e98f1a6415 2026-06-14T04:37:32Z Laurent Bercot ska-skaware@skarnet.org 2026-06-14T04:37:32Z urn:sha1:87b8fcabeecf2a9cff2ca596da54d6c1cf17d89f - s6-rc-bundle deleted. Changing bundles without recompiling is not supported anymore. (It works, but it incentivizes poor workflows; it is better to handle stuff at the source level and recompile when in doubt, that's what s6-frontend does.) - new db format, need to recompile and use s6-rc-format-upgrade on new live db - support for the reload-signal file in service directories - new reload scripts for oneshots (which is why the db format has changed) - new "s6-rc reload" command, calling s6-svc -l on longruns (which makes use of reload-signal, HUP by default) and the reload script on oneshots - the live state now tracks when a service has been explicitly brought up as opposed to by pulled by dependencies. Nothing uses the feature for now but now the tech is there for an auto-stop-if-unneeded feature. 2026-01-24T16:17:39Z Laurent Bercot ska-skaware@skarnet.org 2026-01-24T16:17:39Z urn:sha1:7551c712d73f1d07f6dec2c9b8183a43204f4aa5 2025-12-20T23:50:19Z Laurent Bercot ska-skaware@skarnet.org 2025-12-20T23:50:19Z urn:sha1:b24a07fca1f2a410b3d97d1e3dc5de7720ad1d76 2025-12-09T05:46:14Z Laurent Bercot ska-skaware@skarnet.org 2025-12-09T05:46:14Z urn:sha1:420d8cef5cb8eed461a1b17dcd17de270571baf9