It's kind of stupid, but if you perform any action using etcat on a masked build, etcat will not find it. You must unmask the build first in order for etcat to work correctly. This seems a little broken, as etcat is usually run on builds which have already been installed. If it's already been installed, why would you need to umask it? Reproducible: Always Steps to Reproduce: 1). Perform any action using etcat on a masked build 2). Unmask the build which you are using to test 3). Perform action #1 again. Actual Results: dshanker root # emerge -s ipsec Searching... [ Results for search key : ipsec ] [ Applications found : 1 ] * net-firewall/ipsec-tools [ Masked ] Latest version available: 0.2.4 Latest version installed: 0.2.4 Size of downloaded files: 696 kB Homepage: http://ipsec-tools.sourceforge.net/ Description: IPsec-Tools is a port of KAME's IPsec utilities to the Linux- 2.6 IPsec implementation. License: BSD dshanker root # etcat -s ipsec-tools [ Results for search key : ipsec-tools ] [ Candidate applications found : 0 ] No packages found. dshanker root # !export export ACCEPT_KEYWORDS="~x86" dshanker root # etcat -s ipsec-tools [ Results for search key : ipsec-tools ] [ Candidate applications found : 3 ] Only printing found installed programs. * net-firewall/ipsec-tools-0.2.4 Total Files : 39 Total Size : 916.44 KB Expected Results: You shouldn't need to umask the build This problem seems to be a bigger problem in portage, as I usually run into issues where a "newer" stable version of a build is out and portage wants to install it over my current masked (masked because of development/unstable or what not) build currently installed.
this tool is deprecated
