The problem is illustrated in this forum post: https://forums.gentoo.org/viewtopic-t-1075150-start-0.html Basically, catalyst must mount a tmpfs to /run before chroot in order to prevent samba ebuild from messing with the /var/lock symlink. Reproducible: Always Steps to Reproduce: 1. create a spec file that emerges net-fs/samba 2. run catalyst 3. behold the following: * Installation of a directory is blocked by a file: * '/var/lock' * This file will be renamed to a different name: * '/var/lock.backup.0000' Actual Results: You have a /var/lock/samba and /var/lock.backup.0000 -> /run in the /var directory in the stage root. Expected Results: we have to have a /var/lock -> /run symlink and /run/samba
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=2e91db10c272e3943b768573b27477bca02e53d3 commit 2e91db10c272e3943b768573b27477bca02e53d3 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2019-10-19 23:55:46 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2019-10-20 00:00:08 +0000 Mount tmpfs at /run Closes: https://bugs.gentoo.org/659238 Signed-off-by: Matt Turner <mattst88@gentoo.org> catalyst/base/stagebase.py | 3 +++ catalyst/defaults.py | 2 ++ 2 files changed, 5 insertions(+)
Thank you for the suggestion! I've tagged a 3.0.7 release with this patch in it. I would be grateful if you confirmed that it indeed fixes the problem for you.
