Currently when attempting to perform a stage 3 install from the latest experimental/hardened/musl/amd64 tarball, an emerge -NuD world fails because the main tree ships sys-libs/libcap-ng 0.7.4 as stable. The hardened-dev overlay with musl patches still ships 0.7.3, thus Portage will prefer and attempt to install the main tree version, which will then fail.
An alternative solution would be to add >=sys-libs/libcap-ng-0.7.4 to the hardened/linux/musl profiles' package.mask until the patches are forward-ported to 0.7.4, if that turns out to be nontrivial.
I've bumped this on the overlay, but the patch should go upstream. Its trivial and POSIX-correct. It adds #include <unistd.h> for pid_t and uid_t. I've looked at http://people.redhat.com/sgrubb/libcap-ng/ bug I can't find any bug reporting process.
Does anyone in base-system know? Do I just submit at https://bugzilla.redhat.com/?
Judging from earlier bugs, https://bugzilla.redhat.com seems to be the place to go.
(In reply to Anthony Basile from comment #1)
where is the patch ?
Presumably, he means the patch in the hardened-development overlay.
(In reply to Shiz from comment #4)
that patch is fine for the main tree once it's cleaned & properly documented:
The patch is now in the our tree for libcap-ng-0.7.5 (not previous)
and it is submitted upstream at the above URL.
Upstream says the fix is in 0.7.7. I'll bump and see if it works.
(In reply to Anthony Basile from comment #7)
> Upstream says the fix is in 0.7.7. I'll bump and see if it works.
It works. I bumped 0.7.6 (with my patch) and 0.7.7 (without my patch) to the tree. The next version of libcap-ng to stabilize should be 0.7.7.
can be closed, 0.7.7 is stable on all related archs.