Bug 551738 – sys-apps/likwid-3.1.3 : postinst fails with 'Failed to set capabilities'

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Helmut Jarausch 2015-06-11 09:24:54 UTC]

* Setting caps 'cap_sys_rawio=ep' on file '/usr/sbin/likwid-accessD' failed:
 * Failed to set capabilities on file `/usr/sbin/likwid-accessD' (Invalid argument)
 * usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
 * 
 *  Note <filename> must be a regular (non-symlink) file.
 * ERROR: sys-apps/likwid-3.1.3::gentoo failed (postinst phase):
 *   could not set caps

This fail if the kernel configuration
CONFIG_EXT4_FS_SECURITY  is not set.

The same problem occurred in bug 551672

[Comment 1 Mike Gilbert 2015-06-13 23:52:10 UTC]

Set USE=-filecaps, or reconfigure your kernel.

[Comment 2 Helmut Jarausch 2015-06-14 14:36:45 UTC]

(In reply to Mike Gilbert from comment #1)
> Set USE=-filecaps, or reconfigure your kernel.

Yes, but it was hard to find out that the package depends on a specific kernel option.

It would be nice if the ebuild would check the existence of that kernel option.

[Comment 3 Brendan Horan 2015-06-15 00:49:05 UTC]

Currently I check only for :
CONFIG_CHECK="~X86_MSR"

Should I change this to be :
CONFIG_CHECK="~X86_MSR ~EXT4_FS_SECURITY"

Or it assumed that "CONFIG_EXT4_FS_SECURITY" should be in most peoples .config ?
The "gnome-keyring" package does not have this in it's CONFIG_CHECK.

[Comment 4 Ian Delaney (RETIRED) 2015-06-22 06:56:47 UTC]

I suggest you ping a dev who deals with this directly or CC them.  Once closed INVALID this will not attract any response