walterw

Thanks - I will wait then.

Thanks - I tried that many times. I also started over with a new stage3. My systems with zfs in them all have this problem, the systems without do not. I have no idea why yet.

Thanks - the bug report is closed, what are the next steps for this?

I am attempting to update my systems and for whatever reason, when running: emerge --newuse -uD world -vp mips-sources is complaining of eapi7-ver: EAPI=5 not supported. I don't have mips-sources installed and I'm on an x86/64 system. Calculating dependencies / * ERROR: sys-kernel/mips-sources-4.13.16::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.13.16.ebuild' * mips-sources-4.13.16.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' - * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.13.16::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.13.16::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.13.16/work/linux--20171007' | * ERROR: sys-kernel/mips-sources-4.9.75::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.9.75.ebuild' * mips-sources-4.9.75.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.9.75::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.9.75::nokit'`. - * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.9.75/work/linux--20161216' \ * ERROR: sys-kernel/mips-sources-4.4.110::nokit failed (depend phase): * eapi7-ver: EAPI=5 not supported * * Call stack: * ebuild.sh, line 603: Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.4.110.ebuild' * mips-sources-4.4.110.ebuild, line 27: Called inherit 'eapi7-ver' 'eutils' 'kernel-2' * ebuild.sh, line 294: Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * ebuild.sh, line 79: Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass' * eapi7-ver.eclass, line 62: Called die * The specific snippet of code: * die "${ECLASS}: EAPI=${EAPI:-0} not supported";; * * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.4.110::nokit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.4.110::nokit'`. * Working directory: '/usr/lib64/python2.7/site-packages' * S: '/var/tmp/portage/sys-kernel/mips-sources-4.4.110/work/linux--20160123' ... done! Total: 0 packages, Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-python/urllib3:0 dev-python/urllib3-1.23:0/0::python-modules-kit, ebuild scheduled for merge conflicts with <dev-python/urllib3-1.23[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by dev-python/elasticsearch-py-6.3.0:0/0::python-modules-kit, installed Now, the interesting thing is, I only get this error when updating systems with ZFS, but those ebuilds don't appear to have changed recently. I'm running the default kits, but I also tried updating to 1.2 where possible, but that didn't seem to make any difference.

Hi cafaia, File received, I see it is compressed with gzip. I see that scandelay actually supports no args, it waits 3 seconds by default (when passed as an argument with no parameters) I didn't see anything that stood out, can you try editing /usr/share/genkernel/defaults/linuxrc and adding echo statements throughout to see where it might be occurring, followed by rebuilding the initramfs (and booting up with the modified init)? Then, we can narrow down exactly. Don't forget to backup your original ... Also, share the updated initramfs just so I can see it was updated as expected.

Hi cafaia, If you don't mind, can you post your initramfs? That is the only way I see to troubleshoot this. The other alternative is to look at the source files in /usr/share/genkernel to try and backtrack what is going on there. BTW, I checked my linuxrc (/usr/share/genkernel/defaults/linuxrc), and I don't see an ro option, is that a kernel command-line option? Just for giggles, can you remove that argument?

I masked gentoo-sources > 4.15.0 and rebuilt everything since apparently 4.17 is not ready yet and the newer ZFS ebuilds are not yet available.

Hi cafaia, Hmm, this is an example of what I use, I have a modified initramfs ... linux /kernel-genkernel-x86_64-4.8.7-hardened consoleblank=300 crypt_root=/dev/disk/by-uuid/87f271ea dolvm doluks root=/dev/250.1/root-1 real_root=/dev/250.1/root-1 rootfstype=squashfs scandelay=2 memory tmpfs_size=4G initrd /initramfs-genkernel-x86_64-4.8.7-hardened If you modified your initramfs, please share. If not, please also confirm. It is odd to be getting that message if you haven't modified the initramfs and before openrc starts. In my case, I've gotten a variation before in shell scripts when I'm expecting a variable to be set, but it is not.

I thought scandelay took a numerical argument. I use this to boot off of USB devices because it sometimes takes a second or 2 to see them

I have previously installed ZFS with no issues, but am currently getting: sed: can't read /var/tmp/portage/sys-kernel/spl-9999/work/spl-9999/scripts/check.sh: No such file or directory * ERROR: sys-kernel/spl-9999::core-kit failed (prepare phase): * Cannot patch check.sh I see in the upstream zfsonlinux/spl.git repository that there is indeed no check.sh script - it appears I should be using the spl-0.7.9999.ebuild. However, that is not available in portage in any of the kits (1.0, 1.1, or 1.2).

I am building funtoo root images for a different target architecture than the build system and wondering if that is causing some packages to fail to run. I am starting with a generic subarch: https://www.funtoo.org/Generic_64 And, I modify /etc/make.conf to: CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=x86-64 -O2 -pipe" CXXFLAGS="-march=x86-64 -O2 -pipe" CPU_FLAGS_X86="mmx mmxext sse sse2" I do that to hopefully ensure that gcc won't build for my system which is an i7 and the target systems are a 64-bit Intel Atom and a 64-bit AMD netbook processor. However, I still am unable to run a select few applications as I get invalid opcode during execution (they do run just fine on the system on which I built them). Am I missing a step to build for a different target architecture? I don't believe distcc is required here, but all I really want to do is tell gcc not to use march=native which it prefers to do by default.

Thanks, that fixed it - I followed the gentoo docs and not the funtoo ones.

I am trying to launch a container with lxd and am not having any such luck. These are the steps I followed: https://wiki.gentoo.org/wiki/LXD 1. install lxd (I did not install criu and will add that for a future build) 2. manually configure kernel for lxd (I didn't do ebuild lxc or ebuild criu) 3. lxd group / user didn't exist, so I created it 4. add myself to that group 5. started lxd 6. initialized lxd (the order on the gentoo website says otherwise, but I couldn't do it in that order) 7. lxd automatically setup the network interface via the lxd service, so I didn't have the net.lxbr0 to worry about 8. images repository already existed, I just chose alpine linux since it was tiny lxc launch images:alpine/3.4 Creating the container Container name is: peaceful-racer Starting peaceful-racer error: Failed to run: /usr/sbin/lxd forkstart peaceful-racer /var/lib/lxd/containers /var/log/lxd/peaceful-racer/lxc.conf: Try `lxc info --show-log local:peaceful-racer` for more info lxc info --show-log local:peaceful-racer Name: peaceful-racer Remote: unix:// Architecture: x86_64 Created: 2018/03/13 10:24 UTC Status: Stopped Type: persistent Profiles: default Log: lxc 20180313102453.772 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102453.772 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.308 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18127 0 1000000 1000000000 lxc 20180313102454.309 ERROR lxc_start - start.c:lxc_spawn:1276 - Failed to set up id mapping. lxc 20180313102454.448 WARN lxc_network - network.c:lxc_delete_network_priv:2557 - Failed to remove interface "vethPDC82W" from "lxdbr0": Invalid argument lxc 20180313102454.448 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.448 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.449 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "ABORTING" instead of "RUNNING" lxc 20180313102454.452 ERROR lxc_start - start.c:__lxc_start:1459 - Failed to spawn container "peaceful-racer". lxc 20180313102454.452 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.452 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.610 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18143 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.611 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18143" lxc 20180313102454.611 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/openrc//lxc/peaceful-racer lxc 20180313102454.645 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18145 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.645 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18145" lxc 20180313102454.645 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuset//lxc/peaceful-racer lxc 20180313102454.676 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18147 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.677 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18147" lxc 20180313102454.677 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpu//lxc/peaceful-racer lxc 20180313102454.708 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18149 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.709 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18149" lxc 20180313102454.709 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuacct//lxc/peaceful-racer lxc 20180313102454.743 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18151 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.743 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18151" lxc 20180313102454.743 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/blkio//lxc/peaceful-racer lxc 20180313102454.777 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18153 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.778 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18153" lxc 20180313102454.778 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/memory//lxc/peaceful-racer lxc 20180313102454.810 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18155 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.811 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18155" lxc 20180313102454.811 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/devices//lxc/peaceful-racer lxc 20180313102454.841 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18157 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.842 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18157" lxc 20180313102454.842 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/freezer//lxc/peaceful-racer lxc 20180313102454.874 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18159 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.874 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18159" lxc 20180313102454.875 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/net_cls//lxc/peaceful-racer lxc 20180313102454.903 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18161 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.903 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18161" lxc 20180313102454.903 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/perf_event//lxc/peaceful-racer lxc 20180313102454.928 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18163 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.929 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18163" lxc 20180313102454.929 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/hugetlb//lxc/peaceful-racer lxc 20180313102454.960 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18165 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.960 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18165" lxc 20180313102454.960 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/pids//lxc/peaceful-racer lxc 20180313102454.961 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.961 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.963 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:125 - Command get_cgroup failed to receive response: Connection reset by peer. lxc config --expanded show peaceful-racer architecture: x86_64 config: image.architecture: amd64 image.description: Alpine 3.4 amd64 (20180312_17:50) image.os: Alpine image.release: "3.4" image.serial: "20180312_17:50" volatile.base_image: 2ef5588b926349408eb1689bda8aa2f42123248f1bb3fc34c2ad4d6c5bb02962 volatile.eth0.hwaddr: 00:16:3e:67:65:8b volatile.eth0.name: eth0 volatile.idmap.base: "0" volatile.idmap.next: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]' volatile.last_state.idmap: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]' volatile.last_state.power: STOPPED devices: eth0: nictype: bridged parent: lxdbr0 type: nic root: path: / pool: default type: disk ephemeral: false profiles: - default stateful: false description: "" My system is using a squashfs root with an ext4 backed overlayfs.

Jira closed, talk about speedy service! I am emerging the package now!

raised: https://bugs.funtoo.org/browse/FL-4844