66-update trouble at update time

Some user report this error at update time with the 66-update tool:

# 66-update -d -v4
66-update(src/66/66-update.c: main: 271): info: dry run do: save state of tree: boot_backup-2019-04-15-46
66-update(src/66/66-update.c: tree_allowed: 119): tracing: dry run do: allowed user(s) for tree: boot_backup-2019-04-15-46 are: root
66-update(src/66/66-update.c: main: 287): info: dry run do: save service(s) list of tree: boot_backup-2019-04-15-46
66-update(src/66/66-update.c: tree_contents: 144): tracing: dry run do: tree: boot_backup-2019-04-15-46 contain service: tty12
66-update(src/lib66/resolve.c: ss_resolve_src: 182): warning: unable to open : /etc/66/service/: No such file or directory
66-update(src/lib66/resolve.c: ss_resolve_src_path: 133): warning: unable to parse source directory: /etc/66/service/: No such file or directory
66-update(src/66/66-update.c: tree_contents: 146): fatal: unable to resolve source path of: tty12

As you can see, 66-update cannot find the /etc/66/service directory. Between the version v0.2.3.0 and v0.2.3.1, the creation of this directory has changed. Previously this directory was created by pacman at installation/upgrade time. This directory is now created directly if it missing by the 66-tree tool.

So, at upgrade time pacman has removed the /etc/66/service if it was empty. If the 66-tree was never used after this change, the /etc/66/service directory is now missing on your system.

To resolve this trouble, just create the /etc/66/service directory (with root privilegies)

# mkdir -p -m 0755 /etc/66/service

The 66-update tool should not complain anymore and you should be able to upgrade your system.

Hope you found this bulletin usefull for you.

If you have any questions or trouble, please do not hesitate in making a report.

Thanks for your attention.

eric.vidal@obarun.org