1st is the correct format of the command something like:
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?
% 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?