I run 66-intree and all trees "appear" broken to 66-intree output.
This is expected, inner format change and so tools cannot be read correctly configuration file like /var/lib/system/<tree>/servicedirs/.resolve/.
So I do the normal erase boot erase root, -n boot -cnE root, populate, and run 66-intree ... everything appears OK, still on x on a terminal, no sensed problem anywhere.
....
Unless 66-intree shows false information, because it is new 66-intree, and if I had run 66-update before and then run intree there would be no problem. I can't make any other sense out of it.
This is exactly the purpose of 66-update, avoids you to erase,create,populate.
So:
- pacman -Syu
- 66-update
- 66-intree to verify
Till you run update 66-intree will not work correctly, right?
correct, again format change so 66-intree cannot retrieve the information correctly.
ALL tools will be not able to read the information of your system/tree correctly. So, if you reboot without updating the format you will go on trouble.
They are not broken, they are in transition.
you get the point :).
Basically if say fungalnet-66serv has a dependency on ntpd-66serv and ntpd has a dependency on dhcpcd isn't this all defined on the -66serv packages?
I thought the dependencies didn't exist before (previous 66) ... am I missing something?
this was always the case. xxx-66serv package define dependencies and the frontend too.
IOW, should new format -66serv pkgs appear on observice-testing? Or does the update also rewrites the installed pkg contents?
Inner format change as nothing to do with frontend file. Frontend file are only changed if i remove a field or add a mandatory field, for the rest the frontend do not need to be changed. For example @ optsdepends is a new field but not a mandatory one, so already existing frontend do not need to be changed except if i want to add this new field inside it like sddm for consolekit elogind