[I] net-misc/iputils Available versions: 20101006-r2 20121221 (~)20121221-r1{tbz2} **99999999 {SECURITY_HAZARD caps doc +filecaps gnutls idn ipv6 ssl static} Installed versions: 20121221-r1{tbz2}(11:05:07 PM 02/19/2013)(filecaps ipv6 ssl -SECURITY_HAZARD -caps -doc -gnutls -idn -static) Homepage: http://www.linuxfoundation.org/collaborate/workgroups/networking/iputils Description: Network monitoring tools including ping and ping6 sys-libs/libcap is only pulled in as package #373 in this list... >>> Emerging binary (318 of 1075) net-misc/iputils-20121221-r1 * iputils-20121221-r1.tbz2 MD5 SHA1 size ;-) ... [ ok ] >>> Extracting info >>> Extracting net-misc/iputils-20121221-r1 >>> Installing (318 of 1075) net-misc/iputils-20121221-r1 * Setting caps 'cap_net_raw=ep' on file '/bin/arping' failed: * /var/tmp/portage/net-misc/iputils-20121221-r1/temp/environment: line 1315: setcap: command not found * ERROR: net-misc/iputils-20121221-r1 failed (postinst phase): * could not set caps * * Call stack: * ebuild.sh, line 93: Called pkg_postinst * environment, line 2250: Called fcaps 'cap_net_raw' 'bin/arping' 'bin/ping' 'bin/ping6' 'usr/bin/clockdiff' * environment, line 1319: Called die * The specific snippet of code: * die "could not set caps"; * * If you need support, post the output of `emerge --info '=net-misc/iputils-20121221-r1'`, * the complete build log and the output of `emerge -pqv '=net-misc/iputils-20121221-r1'`. * The complete build log is located at '/var/tmp/portage/net-misc/iputils-20121221-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/iputils-20121221-r1/temp/environment'. * Working directory: '/var/tmp/portage/net-misc/iputils-20121221-r1' * S: '/var/tmp/portage/net-misc/iputils-20121221-r1/work/iputils-20121221' Reproducible: Always
Please don't do that.
Maybe it should have IUSE=filecaps and test for that in pkg_postinst()?
What did I do wrong? http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml "If a bug report pertains to a specific package, then you enter the package's directory in your copy of the gentoo-x86 CVS repository (or perhaps the online version which should always be more or less up to date) and read the metadata.xml file you find there. When metadata.xml lists a single maintainer or herd, then you assign the bug to that maintainer or herd"
missing setcap is no longer fatal. it'll fall back to set*id. http://sources.gentoo.org/eclass/fcaps.eclass?r1=1.3&r2=1.4