Emerging net-firewall/psad-2.1.7 from binary package failed. Emerging from source or making the binary package is OK, but emerging the binary package (even on the same machine) failed. Probably the reason is that "fix_psad_conf" function in ebuild is called from pkg_preinst. This function manipulates files used during compilation that are not available in binary merge, so probably it shoud not be in pkg_.... Ebuild of Previous version 1.4.8 calls this in src_install, which is OK. Steps to reproduce: emerge -b =net-firewall/psad-2.1.7 emerge -k =net-firewall/psad-2.1.7 ==================== /var/tmp/portage/net-firewall/psad-2.1.7/temp/environment: line 2630: cd: /var/tmp/portage/net-firewall/psad-2.1.7/work/psad-2.1.7: No such file or directory cp: cannot stat `psad.conf': No such file or directory sed: can't read psad.conf: No such file or directory * ERROR: net-firewall/psad-2.1.7 failed: * fix_psad_conf failed * * Call stack: * ebuild.sh, line 56: Called pkg_preinst * environment, line 2631: Called fix_psad_conf * environment, line 1399: Called die * The specific snippet of code: * sed -i "s:HOSTNAME\(.\+\)\_CHANGEME\_;:HOSTNAME\1${myhostname}${mydomain};:" psad.conf || die "fix_psad_conf failed"; *
That configuration manipulation stuff has all been removed in 2.2 - not only was it being "fixed" in the wrong ebuild phase, but more importantly: users of this package should be smart enough to RTFM and configure it properly themselves. Thanks for reporting! Please test 2.2 and file new bug reports for any remaining issues.
