New comment by mobinmob on void-packages repository https://github.com/void-linux/void-packages/pull/45578#issuecomment-1932552536 Comment: > > preprod for 66 in not a final release, it is an rc (I know, I am the one who proposed beta etc releases to @Obarun ).I am waiting for the final release and (more) testing. Going from 0.6.0.x to 0.7.0.x is a major change and I didn't have the time yet to test as much as I like. > > That is why I created a draft PR for testing. Building looks fine now and of course we would need to wait for `66` to have a stable `0.7.0.0` available. But seeing check marks already is a good sign for testing the packages. I already have a PR (https://github.com/void-linux/void-packages/pull/47177), since the 66 has to be upgraded (breaking changes from the skarnet stack), but have not yet pushed all needed programs. Maybe your approach is better :) > > You are ofc free to create another PR and the devs to merge whatever they want. > > I would like to go further together with you if you don't mind. If you've other plans I don't want to get into your way. > I will gladly work with you to advance **66** in voidlinux, please sent an email - github comments is not the ideal place for collaboration beyond reviews :) > I'm not yet using s6 and with the PR on the way and all green. I would now test the PR versions and try out s6 and the other packages as well. The current 66 release is stable and well-tested. See the links in the first post on how to setup a system with this. 0.7.0.0 is quite different - my current working branch for boot-66serv voidlinux is void-linux-dev: https://git.obarun.org/mobinmob/boot-66serv/-/tree/voidlinux-dev?ref_type=heads What needs to be done for this is: - revamp the 66boot-* utils to use the new 66 subcommands (not really diffcult) - developed in [codeberg](https://codeberg.org/mobinmob/66-voidlinux) - revise the services in [voidlinux-66-services](https://github.com/mobinmob/void-66-services) for the new format (easy) - revice the documentation (straightforward) - test and then test some more :P I plan to do most of the above if not all (well testing will continue...) in the following days and the weekend...