Created attachment 353452 [details] build.log Attempting to install iptables 1.4.19.1 fails with "newinid failed". We're using systemd as openrc was causing us some problems affecting /proc. Any ideas how we can identify the cause of this?
Created attachment 353454 [details] emerge.info
Created attachment 353456 [details] emerge -pqv
Created attachment 353458 [details] environment
Please don't do that.
Thanks for looking into this. I'm not sure what the error means in the summary though.
(In reply to Tim from comment #3) > declare -x SHELL="/bin/zsh" It looks very bad. Show: ls -l /bin/{ba,z,}sh
-rwxr-xr-x 1 root root 741936 Jul 11 06:10 /bin/bash* lrwxrwxrwx 1 root root 4 Jul 11 06:10 /bin/sh -> bash* -rwxr-xr-x 2 root root 696808 Jul 16 14:49 /bin/zsh*
Do you set SHELL in make.conf or anywhere else? What shell is used by root? Reinstall app-shells/bash.
Preference is to use zsh, therefore I emerged zsh, made sure the configuration exists in /root/.zshrc and changed the root shell with chsh -s /bin/zsh root. Do you think this is related?
Show: head -n1 /usr/lib64/portage/bin/ebuild-helpers/newinitd
# head -n1 /usr/lib64/portage/bin/ebuild-helpers/newinitd #!/bin/bash
Does reinstallation of app-shells/bash or sys-apps/portage help?
Trying to re-emerge portage results in "___eapi_best_version_and_has_version_support_--host-root': not a valid identifier" Same error as python-exec and iptables :(
You can try extracting this to replace /bin/bash: http://tinderbox.dev.gentoo.org/default/linux/amd64/app-shells/bash-4.2_p45.tbz2
Too many packages throwing the same error. We gave up on this, formatted the drive and installed from scratch again. It seems to be working fine this time, perhaps it was a result of a bad stage3 tar ball or something to do with webrsync process (this time we downloaded the portage snapshot tar ball and extracted manually).
