Seems like running `unsymlink-lib --migrate` while under 077 umask leaves the system broken for non-root users due to path traversal issues caused by non-world readable directories.
Running rollback, changing umask to 022 and re-running --migrate works.
Perhaps the tool should set umask 022 for it's own process tree.
The bug has been referenced in the following commit(s):
Author: Michał Górny <firstname.lastname@example.org>
AuthorDate: 2019-06-16 17:34:37 +0000
Commit: Michał Górny <email@example.com>
CommitDate: 2019-06-16 17:35:03 +0000
app-portage/unsymlink-lib: Bump to v16
Bump to version 16. Fixes wrong umask.
Signed-off-by: Michał Górny <firstname.lastname@example.org>
app-portage/unsymlink-lib/Manifest | 1 +
app-portage/unsymlink-lib/unsymlink-lib-16.ebuild | 30 +++++++++++++++++++++++
2 files changed, 31 insertions(+)
Fix released as v16. Since this is a major issue, please test and stabilize.