1st is the correct format of the command something like:
% sudo 66-env -t boot -V boot@ sys
/etc/66/conf/boot@ sys/2.3.0 current
/etc/66/conf/boot@ sys/2.2.1
/etc/66/conf/boot@ sys/2.2.0

% sudo 66-env -v4 -t boot -c 2.3.0 boot@ sys
66-env(src/lib66/ss_environ.c: env_append_version(): 272): warning: unable to find the versioned directory: 2.3.0/etc/66/conf/boot@ sys/2.3.0: No such file or directory
66-env(src/lib66/ssexec_env.c: ssexec_env(): 285): fatal: unable to append version

% sudo 66-env -v4 -t boot -c 2.2.0 boot@ sys
66-env(src/lib66/ss_environ.c: env_append_version(): 272): warning: unable to find the versioned directory: 2.2.0/etc/66/conf/boot@ sys/2.2.0: No such file or directory
66-env(src/lib66/ssexec_env.c: ssexec_env(): 285): fatal: unable to append versione
I noticed this configuring the 2.3.0 boot-66serv on void and thought it is void configuration that it is at fault, but coming back here I see the same exact error. The path given seems very strange 2.2.0/etc/66...

In the past using this worked, I could shift versions with -c

2nd
When current was 2.2.0 after configuring the module and using -F on 66-enable the version shifted on its own to 2.3.0, is it supposed to? When current is 2.2.0 and we use 66-env -e it edits the 2.2.0 file, if it is shifted to 2.3.0 through enable then 2.3.0 is not configured yet. Right?
I noticed this configuring the 2.3.0 boot-66serv on void and thought it is void configuration that it is at fault, but coming back here I see the same exact error. The path given seems very strange 2.2.0/etc/66...
WT... how i hadn't seen a bug like this?
Thanks for the reports and fixed with 0.6.1.2 release.
When current was 2.2.0 after configuring the module and using -F on 66-enable the version shifted on its own to 2.3.0, is it supposed to?
correct
When current is 2.2.0 and we use 66-env -e it edits the 2.2.0 file, if it is shifted to 2.3.0 through enable then 2.3.0 is not configured yet. Right?
correct
Thank mobinmob and his announcement it made me go back and resurrect my voids, from the ashes of neglect, and used his boot-66serv

https://www.reddit.com/r/voidlinux/comments/lz84k6/66_and_s6rc_an_alternative_init_system_for/

and in the process of upgrading 66 in void all trees had to be recreated :P

Look at this sacrilege (I only bumped the runlevel)
      
[main]
@ type = classic
@ version = 0.0.1
@ description = "runit"
@ user = (root)

[start]
@ build = custom
@ shebang = ( "/bin/sh" )
@ execute = (
exec 2>&1

PATH=/usr/bin:/usr/sbin
runlevel=666

runsvchdir "${runlevel}"
s6-mkdir -v -p /run/runit/runsvdir
ln -s /etc/runit/runsvdir/current /run/runit/runsvdir/current
s6-rmrf /var/service/current
s6-rmrf /var/service/supervise

exec s6-env -i PATH=$PATH \
    runsvdir -P /run/runit/runsvdir/current
 )

[stop]
@ build = custom
@ shebang = ( "/bin/sh" )
@ execute = ( sv force-stop /var/service/* }
 sv exit /var/service/* )

[logger]
@ backup = 3
@ maxsize = 1000000

Powered by Obarun