Upon merging the recent zfs-0.6.4.ebuild the following expected scripts where missing: /usr/lib/dracut/modules.d/90zfs/module-setup.sh /usr/lib/dracut/modules.d/90zfs/mount-zfs.sh /usr/lib/dracut/modules.d/90zfs/export-zfs.sh /usr/lib/dracut/modules.d/90zfs/parse-zfs.sh Reproducible: Always Steps to Reproduce: 1.emerge =sys-fs/zfs-0.6.4 2.ls /usr/lib/dracut/modules.d/90zfs Actual Results: ls: cannot access /usr/lib/dracut/modules.d/90zfs: No such file or directory Expected Results: export-zfs.sh module-setup.sh mount-zfs.sh parse-zfs.sh Adding the following line (~line 85) to src_configure function produces the expected results: --with-dracutdir="/usr/$(get_libdir)/dracut"
(In reply to Corin Lawson from comment #0) > Adding the following line (~line 85) to src_configure function produces the > expected results: > --with-dracutdir="/usr/$(get_libdir)/dracut" "/usr/$(get_libdir)/dracut" is incorrect. dracut is always installed under /usr/lib/dracut, regardless of the value of LIBDIR.
Thanks Mike, I wasn't sure as I just copied that line from zfs-9999.ebuild...
This also bit me, twice. Once on initial install of a new server. Then after a portage update caused the zfs-0.6.4.ebuild to be restored to the original, (and new kernel then failed to boot). Nothing serious for me, just wanted to add my 2 cents worth to request upstream EBuild fix. Same hardware, AMD64 Linux.
Created attachment 407368 [details, diff] adding dracut config if USE-flag is set please add a USE-flag `dracut` for dracut-module support.
This is a regression from https://bugs.gentoo.org/show_bug.cgi?id=478684 where this bug was already fixed. According to ryao, "the new policy on small files, the dracut module is installed unconditionally," without needing a USE flag.
This was fixed in the 0.6.5 ebuild. I will try to do a revision to fix it in the older ebuilds.
this has been fixed in all in-tree ebuilds https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=20c8e69ec3b25a431ee1c0e8cf3d1f0274dbffec