The latest update to the zfs live ebuild added some pam configuration, but set the pam configuration directory to /dev/null. https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-fs/zfs/zfs-9999.ebuild?id=5b075422250d1ced0c6d4346ffe32412b5f4ed05 Portage does not detect any file collisions with other packages, so it moves /dev/null to /dev/null.backup.0000 and merges the /dev/null directory.
that's unfortunate. I did not hit it while testing ls -la /dev/null crw-rw-rw- 1 root root 1, 3 Jun 30 15:15 /dev/null But I'll fix asap.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2247323ce9e28f424b66eca83680f52d55a851b8 commit 2247323ce9e28f424b66eca83680f52d55a851b8 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2020-07-05 01:38:19 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2020-07-05 01:59:13 +0000 sys-fs/zfs: update live ebuild, fix pam dir removal Closes: https://bugs.gentoo.org/730772 Package-Manager: Portage-2.3.103, Repoman-2.3.23 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> sys-fs/zfs/zfs-9999.ebuild | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
thanks for catching and reporting quickly and sorry about this.
