Created attachment 620702 [details] /var/tmp/portage/sys-fs/zfs-0.8.3-r1/temp + emerge --info I have been dealing with this error for a while by creating a new ebuild without the fperms portion. When trying to compile any of the recent zfs versions (0.8) I receive the following error chmod: cannot access '/var/tmp/portage/sys-fs/zfs-0.8.3-r1/image/etc/conf.d/zfs': No such file or directory * ERROR: sys-fs/zfs-0.8.3-r1::gentoo failed (install phase): * fperms failed Attached is a tar.gz containing /var/tmp/portage/sys-fs/zfs-0.8.3-r1/temp. I have also run emerge -v --info sys-fs/zfs-0.8.3-r1 and included the output in the tar.gz as emerge-info
> checking default init config directory... /etc/sysconfig ^ this is from your log this should only happen on rpm systems from mine log it's > checking default init config directory... /etc/conf.d check is AC_MSG_CHECKING([default init config directory]) case "$VENDOR" in alpine) DEFAULT_INITCONF_DIR=/etc/conf.d ;; gentoo) DEFAULT_INITCONF_DIR=/etc/conf.d ;; toss) DEFAULT_INITCONF_DIR=/etc/sysconfig ;; redhat) DEFAULT_INITCONF_DIR=/etc/sysconfig ;; fedora) DEFAULT_INITCONF_DIR=/etc/sysconfig ;; sles) DEFAULT_INITCONF_DIR=/etc/sysconfig ;; ubuntu) DEFAULT_INITCONF_DIR=/etc/default ;; debian) DEFAULT_INITCONF_DIR=/etc/default ;; *) DEFAULT_INITCONF_DIR=/etc/default ;; esac vendor check is AC_DEFUN([ZFS_AC_DEFAULT_PACKAGE], [ AC_MSG_CHECKING([linux distribution]) if test -f /etc/toss-release ; then VENDOR=toss ; elif test -f /etc/fedora-release ; then VENDOR=fedora ; elif test -f /etc/redhat-release ; then VENDOR=redhat ; elif test -f /etc/gentoo-release ; then VENDOR=gentoo ; elif test -f /etc/arch-release ; then VENDOR=arch ; elif test -f /etc/SuSE-release ; then VENDOR=sles ; elif test -f /etc/slackware-version ; then VENDOR=slackware ; elif test -f /etc/lunar.release ; then VENDOR=lunar ; elif test -f /etc/lsb-release ; then VENDOR=ubuntu ; elif test -f /etc/debian_version ; then VENDOR=debian ; elif test -f /etc/alpine-release ; then VENDOR=alpine ; else VENDOR= ; do you have, by any chance, file named /etc/{fedora,redhat}-release on the system? it yes, it's the one screwing up build for you. build systems determines wrong vendor and the file gets installed to different place and that's why ebuild fails.
I have been looking at this error for months and couldn't see what was right in front of me! Had to create this to bypass something else and completely forgot about it. Thanks for the quick help Georgy!
glad I could help =)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b87f490d0b7e66e51cc2c9d159ebee1e238db9f1 commit b87f490d0b7e66e51cc2c9d159ebee1e238db9f1 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2020-08-28 19:15:36 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2020-08-28 19:52:13 +0000 sys-fs/zfs: update live ebuild, pass --with-vendor=gentoo Upstream PR: https://github.com/openzfs/zfs/pull/10835 Bug: https://bugs.gentoo.org/712902 Bug: https://bugs.gentoo.org/739234 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> sys-fs/zfs/zfs-9999.ebuild | 1 + 1 file changed, 1 insertion(+)
