Bug 380619

Summary:	liboping and capabilities
Product:	Gentoo Linux	Reporter:	Andreas K. Hüttel <dilfridge>
Component:	[OLD] Library	Assignee:	Andreas K. Hüttel <dilfridge>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugs
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	liboping-1.6.1-build.log

Description Andreas K. Hüttel archtester

2011-08-25 10:59:42 UTC

[12:53:05] <jbergstroem> 2. liboping bump assumes (set|get)cap is available, need to check for it first
[12:53:11] <dilfridge> :|
[12:53:20] <dilfridge> won't work
[12:53:26] <jbergstroem> oh?
[12:53:37] <jbergstroem> libcap?
[12:53:47] <dilfridge> it can work but there is no guarantee so far
[12:54:01] <jbergstroem> you mean from a FS point of view?
[12:54:14] <dilfridge> because there is no specification what portage does with caps when the image is merged into the installation

Comment 1 Johan Bergström 2011-08-25 11:02:11 UTC

Created attachment 284597 [details]
liboping-1.6.1-build.log

Build log when capabilities fail. If libcap(-ng) isn't installed, it will fail with "setcap not found"

Comment 2 Andreas K. Hüttel archtester

2011-08-25 21:14:13 UTC

You get this error because you dont use FEATURES="usersandbox userpriv" (which I do, and then the configure script does not even try setting caps or suid).

Bad bad buildsystem... basically we need to hard-disable this mechanism, and do whatever is needed later by hand in the ebuild.

Comment 3 Andreas K. Hüttel archtester

2011-08-25 21:31:12 UTC

"fixed" by backing out the change and setting suid by hand... caps would be an improvement, but that needs handling in portage first