s6-rc/src/repo/s6-rc-set-install.c, branch v0.8.0.1The skarnet.org service managerhttps://git.skarnet.org/cgit/s6-rc/atom/src/repo/s6-rc-set-install.c?h=v0.8.0.12026-10-19T00:19:35Z Next batch of bugfixes, it is functional now!2026-10-19T00:19:35ZLaurent Bercotska-skaware@skarnet.org2026-10-19T00:19:35Zurn:sha1:d05e4f8615ae9ebfe14e6adff7bd6d52cba26fb1 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.
And add similar options to s6-rc-set-install2026-01-24T08:25:53ZLaurent Bercotska-skaware@skarnet.org2026-01-24T08:25:53Zurn:sha1:b71b06951c8f9250f87a16cd1e60b2d779bfcfff
s6-rc-set-install downs essential services by default. This is
different from the s6-rc-update default.
Option is --no-update, not ----no-update. Also fix dotpc.2026-01-19T06:59:15ZLaurent Bercotska-skaware@skarnet.org2026-01-19T06:59:15Zurn:sha1:ba3120f4bfed495e6f7406e2d686c8685464312d Add --no-update option to s6-rc-set-install2026-01-17T23:07:49ZLaurent Bercotska-skaware@skarnet.org2026-01-17T23:07:49Zurn:sha1:25f4880b88f77188cc8a099832cafa814d7c2930 s6-rc-set-install fixes2025-12-21T16:27:04ZLaurent Bercotska-skaware@skarnet.org2025-12-21T16:27:04Zurn:sha1:aff2e0c6435433a6f73b9d29c93a3109bfe146ca Next batch of fixes2025-12-09T05:46:14ZLaurent Bercotska-skaware@skarnet.org2025-12-09T05:46:14Zurn:sha1:420d8cef5cb8eed461a1b17dcd17de270571baf9 Some bugfixes2025-12-08T12:04:26ZLaurent Bercotska-skaware@skarnet.org2025-12-08T12:04:26Zurn:sha1:7e6654b43fde098df6f080c6bc57489bfe3c5095 Finish repo documentation; make bootdb configurable; fix install2025-10-30T23:23:52ZLaurent Bercotska-skaware@skarnet.org2025-10-30T23:23:52Zurn:sha1:35b102dae60e53a4be06dbe1c5d2950ee862542b