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 =app-misc/pax-utils-0.8.1 as stable and =app-misc/pax-utils-0.8.1-r99 is unstable in the hardened-dev overlay. This causes Portage to install the main tree version, which then fails because it doesn't apply the necessary musl compatibility patches.
An alternative solution is to add =app-misc/pax-utils-0.8.1-r99 ~* to the hardened/linux/musl profiles' package.accept_keywords, or <app-misc/pax-utils-0.8.1-r99 to package.mask.
This is fixed in 0.9.1 and above, see bug #507470. What we should do is stabilize 1.0.3 if the maintainer is okay with that.
@vapier. okay to stabilize?
1.0.3 is the only one that should go stable now. earlier ones are no good.
stable on ppc and ppc64.
24 May 2015; Mikle Kolyada <email@example.com> pax-utils-1.0.3.ebuild:
amd64 stable wrt bug #550300
forgot to remove amd64 from cc list.
Stable for HPPA.