EDIT 25082020
---------------------
As per https://forum.obarun.org/viewtopic.php?pid=6407# p6407

BEFORE you do the upgrade from 0.4 to 0.5 issue this command: 
% sudo 66-enable -t boot -F -C boot
This ensures that your active boot tree is structured based on the last boot-66service and not configured based on older editions, which causes problems.
-----------------------


I highly recommend before you do any upgrades, if you haven't done so, since this is a major 66 upgrade, run these two commands "as user":
% 66-intree -zg >~/user-trees
% sudo 66-intree -zg >~/root-trees

Those two output files will be saved in your home directory as reference in case something goes wrong.

DO NOT RUN 66-update from chroot! It must be a live booted system.

Be extra careful while upgrading 66 one last time. From this edition and forward you will not have to do any additional work other than upgrading with pacman.

When you finish the pkg upgrade of 66, you MUST run 66-update -d, I suggest you run it as: 66-update -v2 -zd (add color and medium detail). If you see any warnings especially anything saying "fatal" repeat the command only with -v4 : 66-update -v4 -zd

for root trees: (command as if logged in as user, not root) 
% sudo  66-update -v4 -zd
for user trees: 
% 66-update -v4 -zd
If neither one shows any issues run the same two commands without the -d (dry run, no changes) and you are done. Run 66-intree for both user and root to verify your trees are in tact.

If either shows any problems do nothing more, copy the output with -v4 here and someone will try to help you out (remember to enclose the copied output from the terminal with 
[code]...
[/code] brackets.
thanks for the heads-up

update worked flawless for me
getting: 
66-update(src/lib66/parser_write.c: write_services: 108): tracing: Write service system-hostname ...
66-update(src/lib66/ss_environ.c: env_make_symlink: 255): warning: compare version: system-hostname vs: 1.2.1
66-update(src/lib66/parser_write.c: write_common: 610): warning: unable to compute environment
66-update(src/lib66/parser_write.c: write_oneshot: 221): warning: unable to write common files
66-update(src/lib66/parser_write.c: write_services: 124): warning: unable to write: /tmp/boot:mNp7F0/db/source/system-hostname
66-update(src/lib66/ssexec_enable.c: start_write: 149): fatal: unable to write service: system-hostname
what to do?
Can you provide me the complete output of the following command: 
% ls -Rla /etc/66
% pacman -Qs 66
Ok, the solution was found on the IRC obarun channel but it enligth me a little trouble when the update come from a very old version of the boot-66serv. Meaning, if you have the last version installed but you never updated your boot tree by the 66-enable -F -C -t boot boot command, the 66-update crash.

So, first be sure to have your service up to date and running it on your system.
Second, let me a little time to rectify the code to handle this special case.

User which as followed the progressive update should not get any troubles.
... I got this 
66-update: fatal: unable to write service: system-fontnkey
but after downgraded to 66-0.4.0.1-1, than restarted and updated again ... everything went without any problem
i did a bug fix release (v0.5.0.1) to handle this special case. So please synchronize and try again, this should be good now.
For the 3-4 of us here, who already made the upgrade, is 66-update necessary from 0.5.0.0-2 to 0.5.0.1-1?
fungal_net wroteFor the 3-4 of us here, who already made the upgrade, is 66-update necessary from 0.5.0.0-2 to 0.5.0.1-1?
As far as you have installed the 0.5.0.0 all new releases do not need any intervention from the user part. Just install the new version with pacman and that's it.

You can now consider 66-update as a convenient tool when you want to rebuild all your tree by an automatic way.
3 years later
eric unstickied the discussion .

Powered by Obarun