Bug 432983 - libcap needs to be updated!
Summary: libcap needs to be updated!
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libcap
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-15 16:14 UTC by Jonathan Kamens
Modified: 2013-01-10 04:34 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-15 20:01:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2008-02-15 16:14:55 UTC
With today's Rawhide update, named no longer starts:

Starting named: named: capset failed: Invalid argument: please ensure that the 
capset kernel module is loaded.  see insmod(8)
^[[60G[^[[0;31mFAILED^[[0;39m]

According to http://lkml.org/lkml/2008/2/6/533, the problem is an out-of-date 
libcap.  Apparently libcap in Rawhide needs to be updated and named needs to be 
linked against the newest libcap.

Comment 1 Karsten Hopp 2008-02-15 20:01:16 UTC
I've built libcap-2.06-1.fc9 in Rawhide. Named isn't linked against libcap at
all, so I wonder how this is could be the cause for your problems.

Comment 2 Karsten Hopp 2008-02-18 11:40:34 UTC
the new libcap has a different soname and I've untagged it from rawhide as I
need to notify the maintainers of dependent packages first.

Comment 3 Kevin Kofler 2008-02-20 07:13:44 UTC
And now it has reappeared due to the rel-eng GCC 4.3 autorebuilds. This breaks 
dependencies on core components like dbus-libs and is also causing many of the 
subsequent autorebuilds to fail.

Comment 4 Karsten Hopp 2008-02-20 11:21:21 UTC
$%#&!

I've built a new libcap (2.06-3) package that should fix these problems.


Note You need to log in before you can comment on or make changes to this bug.