Summary: | sys-libs/libcap: pam_cap.so installed into /usr/lib*/security (which is not used by PAM) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michał Górny
2012-01-11 22:31:29 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 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. |