398579 – sys-libs/libcap: pam_cap.so installed into /usr/lib*/security (which is not used by PAM)

Bug 398579 - sys-libs/libcap: pam_cap.so installed into /usr/lib*/security (which is not used by PAM)

Summary: sys-libs/libcap: pam_cap.so installed into /usr/lib*/security (which is not u...

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-01-11 22:31 UTC by Michał Górny
Modified:	2012-01-13 15:21 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Michał Górny archtester

2012-01-11 22:31:29 UTC

sys-libs/libcap-0.22 installs:

/usr/lib64/security/pam_cap.so

while PAM only looks for its modules in /lib*/security. Thus, the module is unreachable if referred from pam.d file just as 'pam_cap.so'.

Comment 1 SpanKY gentoo-dev

2012-01-13 06:16:56 UTC

that's not happening over here.  please post full build logs and emerge info as attachments like a normal bug report.

$ USE=pam ebuild libcap-2.22.ebuild install

$ tree /var/tmp/portage/sys-libs/libcap-2.22/image/lib64/
/var/tmp/portage/sys-libs/libcap-2.22/image/lib64/
|-- libcap.so.2 -> libcap.so.2.22
|-- libcap.so.2.22
`-- security
    `-- pam_cap.so

$ tree /var/tmp/portage/sys-libs/libcap-2.22/image/usr/lib64/
/var/tmp/portage/sys-libs/libcap-2.22/image/usr/lib64/
|-- libcap.a
`-- libcap.so

Comment 2 Michał Górny archtester

2012-01-13 15:21:38 UTC

Hmm, weird thing. It seems that 'qlist libcap' lists the pam_cap.so installed both in /lib64/security and /usr/lib64/security. Emerging it again removed the /usr copy; maybe it was fixed earlier without a revision bump.