in net-misc/iputils all ebuilds except =net-misc/iputils-20121221-r1 (since this version do not have USE flag arping and traceroute): RDEPEND="arping? ( !net-misc/arping ) rarpd? ( !net-misc/rarpd ) traceroute? ( !net-analyzer/traceroute ) !static? ( ${LIB_DEPEND//\[static-libs(+)]} )" In lastest commit (efdcc07411a5b54a05d907560e0594e9fc82ced7) of portage, I don't find net-misc/arping and net-misc/rarpd. From /usr/portage/profile/updates I don't see any move for net-misc/arping and net-misc/rarpd, too. There is a package named with arping, it's net-analyzer/arping. However, net-analyzer/arping installs into /usr/sbin/arping2 while net-misc/iputils installs it's arping into /bin/arping. No conflict. At last, net-analyzer/traceroute installs into /usr/bin/traceroute and /usr/bin/traceroute6 while net-misc/iputils installs it's traceroute6 into /usr/sbin/traceroute6, still no conflict. So, finally, I suggest, remove arping/rarpd/traceroute from RDEPEND, making it be: RDEPEND="!static? ( ${LIB_DEPEND//\[static-libs(+)]} )" and einfo about traceroute6 command PATH priority. Also remove corresponding RDEPEND lines from net-analyzer/arping, net-analyzer/traceroute. Reproducible: Always Steps to Reproduce: 1. grep -A3 -ne "^RDEPEND" /usr/portage/net-misc/iputils/*.ebuild
> net-misc/arping > net-misc/rarpd they aren't in the tree anymore, but they were, and people with old installs will still run into troubles if they try to update. listing them in the depend doesn't cause problems. > net-analyzer/traceroute collisions in $PATH is largely the same as filesystem collisions. it's bad form.
