error when upgrading iputils-20101006-3-arm

[replabrobin]

I got this error upgrading today on my sheeva plug

$this->bbcode_second_pass_code('', '(15/21) upgrading iputils [----------------------] 100%
Failed to set capabilities on file `usr/bin/ping' (Operation not supported)
usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN > ]

Note <filename> must be a regular (non-symlink) file.
Failed to set capabilities on file `usr/bin/ping6' (Operation not supported)
usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN > ]

Note <filename> must be a regular (non-symlink) file.
>> Traceroute is now provided by core/traceroute
New optional dependencies for iputils
xinetd: for tftpd
')

not at all sure what the problem is.
$this->bbcode_second_pass_code('', '$ uname -a
Linux delilah 3.1.10-11-ARCH #1 PREEMPT Mon May 21 05:59:32 UTC 2012 armv5tel GNU/Linux')

I'm running on an ext2 fs; perhaps it dosen't support capablities?

[Geoff]

I found the same issue on a Pogo Pro, with an ext3 filesytem and uname -r => 2.6.31.6_SMP_820 ... I'm pretty sure ext3 supports file capabilities, so I guess file capabilities are not enabled in these kernels. I would suggest that a workaround for now might be "chmod u+s /usr/bin/ping /usr/bin/ping6" so that non-root users can once again use ping.

[karog]

I just ran into this. The following are the offending commands (from iputils/.INSTALL):
$this->bbcode_second_pass_code('', '
setcap cap_net_raw=ep usr/bin/ping
setcap cap_net_raw=ep usr/bin/ping6
')
where from man capabilities one finds:
$this->bbcode_second_pass_code('', '
CAP_NET_RAW
* use RAW and PACKET sockets;
* bind to any address for transparent proxying.
')

[replabrobin]

So this is trying to give the ping{6] commands certain abilities without having them run as root. I tried the
$this->bbcode_second_pass_code('', 'chmod ug+s /usr/bin/ping{,6}')
command and that does allow ping to work. Prior to that ping errors
$this->bbcode_second_pass_code('', '$ ping bunyip
ping: icmp open socket: Operation not permitted
')
presumably standard arch kernels either have setcap or the install must do some kind of test; I don't recall seeing this error in my pc arch updates.