• [deleted]

  • Post #1
Hi

After an upgrade of 66 from 0.2.4.0-5 to 0.2.4.0-6 there is a big issue. All my trees have disappeared except boot. 
66-intree

Name         : boot
Initialized   : no
Enabled     : no
Starts after : None
Current       : no
Allowed      : root
Symlinks     : svc->source db->source
66-intree: fatal: unable to build the graph from: /var/lib/66/system/boot/servicedirs
EDIT: Also I can not poweroff the system. 
poweroff
66-hpr: fatal: Unable to notify 66-shutdownd: No such device or address.
huh, nothing change between between release 5 and 6, it just a convenient rebuild to match the framagit tag.
did you try to run an 66-update (it should be not necessary) ?

I curious to know if you are alone on this case
I had to "upgrade too", checked trees before, 66-update -d, 66-update, checked trees, all OK.
I guess if the tree structure gets mixed up and boot is affected then shutdown is no longer supervised, so it will not respond?
So the boot tree at least has to be remade and reactivated?

  • [deleted]

  • Post #4
Hi,

My bad. I don't know how did I come to the conclusion that I was updating 66 from the version 0.2.4.0-5 but that was not the case. After all the time I spent with Eric debugging 66-update ...

So, after a day of rest and a look at my pacman logs, I was updating 66 in my VM, from the version 0.2.3.2-2 to 0.2.4.0-6.
From this version, 66-update -d followed by 66-update as root and user worked as expected without any issues.

Sorry for my mistake. On another side we are now more than sure that 66-update work as expected

You have the right to flog me :D

Powered by Obarun