Multiple issues with 66 0.8x -> 0.9.1.2

eilenbeb

Firstly, the only modification I ever did was to set 'localtime' instead of UTC.
Following forum post
https://news.obarun.org/2026/08/22/upgrading-to-66-0910.html
Following directions, I ran into several probs.

In: /etc/66/conf/boot@system/0.9.1.2/:
modifying boot@system has no effect.
modifying .boot@system did what I needed.
this wasn't expected.

Next:
# 66 reconfigure boot@system
works fine EXEPT:
parse: info: key Version at section [Main] was not set -- define it to: 0.9.1.2
I can't seem to find [Main] anywhere.

Also several other commands complain about EDITOR not being set.
Can't seem to find that one either.

That should be enough for now. There's more, but if 'version' isn't set....

Thanks

eric

advesperascit @eric, my scandir@<user> and boot-user@<user> are under the root user "session" tree (# 66 tree status session).. should I just remove these as root?

Yes and use 66-userd as replacement. Follow the instruction of the migration documentation page, it should work.

@eilenbeb
Spaming the forum will not help to get a quick answer!

First, NEVER TOUCH ANY FILES BY HAND, this is the best way to broke the system, use the proper corresponding tools.

You can ignore safely the warning about the Version key missing at [Main]. This warning should appear as trace message instead of warning. little verbosity level bug here.

eilenbeb In: /etc/66/conf/boot@system/0.9.1.2/:
modifying boot@system has no effect.
modifying .boot@system did what I needed.
this wasn't expected.

Are you sure because it should be the contrary. AFAIK we have no bugs about that.
Anyway, you should use the 66 configure -e <editor> boot@system command, again never touch any files by hand.

eilenbeb also have no access to Obarun archives, cannot downgrade.

you have: https://web.obarun.org/package/obarchive/

So, you post a lot of things but nothing concret.

Do you have error messages?
What error messages?
What the final state of the machine at boot?
Do you have the tty12 running?

Share the output of the following command

# 66 tree status -g
# 66 log system

eilenbeb

I think I know what might have happened.

In the directions, 'Before you start':
between 0.8.0.0 and 0.9.0.0 ... between 0.7.2.1 and 0.8.2.2 ...

Ver 0.8.2.1 (which I had) falls under both.

Hope that helps someone to help me, I can't seem to get 0.8.2.2, Ideas?
The instructions were not concise.
I tried anyways, my bad.
also have no access to Obarun archives, cannot downgrade.
help plz. my only other options is re-install.
when s6/66 gets upgraded, reinstall has been my only option bc no commands
work. a litle bit of help here plz before re-install is my last resort. sorry. peace.

advesperascit

I saw the same message, parse: info: key Version at section [Main] was not set -- define it to: 0.9.1.2.

For EDITOR you can pass -e <editor> like # 66 configure -e nvim boot@system to let the program know which editor to use. Did you modify any file in /etc/66/conf/boot@system/0.9.1.2/ without using 66 configure? That could be a problem. I followed the guide, with exception of $ 66 remove scandir@<user>, and my laptop boots into desktop (I haven't upgraded my workstation yet). I had to make changes with # 66 configure -e nvim boot@system as none of my previous settings were carried over.

@eric, my scandir@<user> and boot-user@<user> are under the root user "session" tree (# 66 tree status session).. should I just remove these as root?

eilenbeb

sry, i am newb. When u get 'editor unset' u can add the -e editor commend. ie 66 blah -e nano blah.

eilenbeb

sry i am less than me, sry

eilenbeb

sry, let me read... sry

eilenbeb

Did U read my edit? I might have fsck'd myself self by upgrading 0.8.2.1 without going to 08.2.2

eilenbeb

Thanks for reply

eilenbeb

@advesperascit thanks, I will try. B out, tima sleep. see ya

eilenbeb

Yep, -e EDITOR is fine, thanks. If I knew what file to edit I could do it manually. No disrespect intended. I am using the base install with 66 ver 0.8.2.1 upgraded to 66 ver 0.9.blah.blah. I am one nap away from backup and re-install. Everytime I get a 66 error it turns into a hororshow. This time i tried. One more day then I re-install. Thanks and peace.

eilenbeb

Dammit, EDITOR was never a prob, I was asking how to set editor. sry for me=ass.

eilenbeb

still no progress. everytime i use a cmdline regaurding 66 all i get is error. the only change i ever made from base install was 'localtime'.
looks like a reinstall. again. getting sick of this. b out.

sorry someone made sugestion i didn't read fully. read, will try again. once again sorry for me=ass. laters

eilenbeb

Thenks advesperascit, sorry for being pissy. My primary system is totally bork'd, and I got lot'sa wurk to do and kinda in panic mode.
Thru out the history of s6/66 no command has ever worked for me, I feel stupid thinking it would work this time.

Thanks for helping, take care.

eilenbeb

Thanks for not kicking me out. Plz delete my many pointless and stupid drunken bs posts.
I am emberrased(sp?).

The install in question has been altered, so I think this might be mute.
Take care, idiot out.