Bug 251654

Summary:	sys-libs/libcap-1.10-r11.ebuild needed by app-emulation/virtualbox-bin-2.1.0
Product:	Gentoo Linux	Reporter:	Alessio Cassibba (X-Drum) <swapon>
Component:	New packages	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	cheepeero, flameeyes, jokey, kronenpj, scen, sven.koehler
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	251335

Description Alessio Cassibba (X-Drum) 2008-12-19 17:10:32 UTC

app-emulation/virtualbox-bin-2.1.0[1] is linked aganist libcap.so.1,
but no 1.x ebuild is present in tree, please consider (if possible)
to reinstate this ebuild.

[1] see bug #251335

Reproducible: Always

Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev

2008-12-19 17:16:56 UTC

Reassigning to base-system herd.

Comment 2 Frank Szczerba 2008-12-20 01:39:13 UTC

sys-libs/libcap-2.11 works fine with virtualbox. All that's required is a libcap.so.1 symlink.

Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev

2008-12-20 01:41:37 UTC

Such a symlink is NOT GOING TO HAPPEN.

That's *NOT* a solution, as the two libcap version have different ABIs.

Fooling with the linker this way is going to break things in subtle ways.

Comment 4 Paul Kronenwetter 2008-12-22 15:34:03 UTC

Just a thought...  Would it be possible / permissible to include libcap-1.x in the installation until it's fixed upstream?  I placed a copy of libcap-1.10 from debian (it's a proxy filtering thing at work) in /opt/VirtualBox and it appears to be happy for me...

I don't know if it would be better to drop a binary in the installation or compile it from source upon installation.

Comment 5 Frank Szczerba 2008-12-22 16:53:08 UTC

This may not be necessary. Virtualbox only uses 2 entry points to libcap (cap_set_proc() and cap_from_text()), and those are ABI-compatible between libcap1 and libcap2.

I think it makes more sense to address this with an LD_PRELOAD in the virtualbox-bin package rather than re-introduce libcap1 (which apparently uses insecure kernel interfaces, thus the move to libcap2).

Comment 6 Roman Karshiev 2009-01-20 13:24:03 UTC

> This may not be necessary. Virtualbox only uses 2 entry points to libcap

VirtualBox-bin 2.0.1 can't work with network with libcap2:

Failed to open/create the internal network 'HostInterfaceNetworking-br0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND).

NS_ERROR_FAILURE (0x80004005)
Console
IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}

Comment 7 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev

2009-01-21 21:58:40 UTC

*** Bug 255792 has been marked as a duplicate of this bug. ***

Comment 8 SpanKY gentoo-dev

2009-01-21 22:29:05 UTC

if that's true, then you can cheat by doing this in the ebuild:
dosym /lib/libcap.so.2 /opt/VirtualBox/libcap.so.1

all of the virtualbox binaries have RPATH's with $ORIGIN in them, so you can put the symlink in /opt/VirtualBox/ without affecting any other package