s6-rc, branch v0.8.0.0The skarnet.org service managerhttps://git.skarnet.org/cgit/s6-rc/atom/?h=v0.8.0.02026-10-19T03:02:49Z version: 0.8.0.02026-10-19T03:02:49ZLaurent Bercotska-skaware@skarnet.org2026-10-19T03:02:49Zurn:sha1:97621e4fbe85041cf0ea6a627977bbc5b107bb27 Update NEWS2026-10-19T02:53:03ZLaurent Bercotska-skaware@skarnet.org2026-10-19T02:53:03Zurn:sha1:3e37d6e758b4784dde313016098000ea699a6019 Next batch of bugfixes, it is functional now!2026-10-19T00:19:35ZLaurent Bercotska-skaware@skarnet.org2026-10-19T00:19:35Zurn:sha1:d05e4f8615ae9ebfe14e6adff7bd6d52cba26fb1 null and empty string are the same for catchall, fdhuser and defbundle2026-10-18T03:05:27ZLaurent Bercotska-skaware@skarnet.org2026-10-18T03:05:27Zurn:sha1:eeb89b66cde623c57c5551c795a97fab247e8881 bugfix: I can't count to 142026-10-18T01:42:42ZLaurent Bercotska-skaware@skarnet.org2026-10-18T01:42:42Zurn:sha1:3cf5ff95f97a81402c132caf4876a6eed17aab21 Louis, I think this is the beginning of a long series of bugfixes.2026-10-18T01:30:52ZLaurent Bercotska-skaware@skarnet.org2026-10-18T01:30:52Zurn:sha1:e94bf09e61d2c9098e8f38d59a23ac420f610938 Part four: we delete all the snapshots after set-install2026-10-18T00:30:27ZLaurent Bercotska-skaware@skarnet.org2026-10-18T00:30:27Zurn:sha1:ebf148d99e2dab6135794149553c193abe4e675d
Except the snapshot corresponding to the new live db, of course.
Also, in order to accommodate snapshots without risking name
conflicts, the real name of set foobar isn't .foobar:XXXXXX
anymore, but .real.foobar:XXXXXX
Now the automatic upgrade in case of major bump is complete.
Next comes testing and debugging.
Third part of the format-upgrade inclusion: add support in s6-rc-set-install2026-10-17T04:10:16ZLaurent Bercotska-skaware@skarnet.org2026-10-17T04:10:16Zurn:sha1:6ada80ed7e45ed630e4d9877a9b11e2dfddb4758
Now that everything is in place, we go for the main thing: add
snapshot support to s6-rc-set install. The workflow is:
- check the major version of the old db against the current s6-rc
- if the old db is up to date, nothing changes
- otherwise:
+ find the snapshot corresponding to the old db
+ compile it
+ copy the snapshot db to the bootdir
+ call s6-rc-format-upgrade on it
+ atomically switch the bootdb to it. At this point the snapshot
is the new bootdb: same as the old db, but with the correct major version.
+ unconditionally remove the old db
+ and now we can perform the regular s6-rc-update with the
wanted set, since they have the same major.
We also add --no-snapshot options to s6-rc-set-commit and
s6-rc-set-install, and propagate them in the supporting functions,
so users can manually skip all this bloat (and this is important
for the initial install).
All that remains is cleaning up obsolete snapshots. This will
probably go at the end of s6-rc-set-install as well.
More work on format-upgrade inclusion: real meta-information storage2026-10-15T08:19:48ZLaurent Bercotska-skaware@skarnet.org2026-10-15T08:19:48Zurn: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.
Second part of the format-upgrade support: ensure snapshots are there2026-10-15T05:17:26ZLaurent Bercotska-skaware@skarnet.org2026-10-15T05:17:26Zurn:sha1:91a0655557e707977f583b2142bda898ee599fd8
We don't want to install compiled dbs without having a snapshot of
their source set, so whenever we test that the compiled db is up to
date, we also test that a snapshot is present. This is important
because we will auto-cleanup unused snapshots after installation.