Created attachment 470536 [details]
emerge --info polkit
After polkit is built the following message is displayed:
* Messages for package sys-auth/polkit-0.113:
* Failed to set XATTR_PAX markings -mre test/polkitbackend/.libs/polkitbackendjsauthoritytest.
This can't be good.
I think this is only relevant to Hardened.
do you have PAX_MARKINGS set in your make.conf?
is your /var/tmp/portage/ on a tmpfs?
and what happens if you try to manually do:
paxctl-ng -mre test/polkitbackend/.libs/polkitbackendjsauthoritytest
(In reply to Jason Zaman from comment #2)
> do you have PAX_MARKINGS set in your make.conf?
> is your /var/tmp/portage/ on a tmpfs?
> and what happens if you try to manually do:
> paxctl-ng -mre test/polkitbackend/.libs/polkitbackendjsauthoritytest
~ # cd /var/tmp/portage/sys-auth/polkit-0.113/work/polkit-0.113/
polkit-0.113 # paxctl-ng -mre test/polkitbackend/.libs/polkitbackendjsauthoritytest-su: paxctl-ng: command not found
Created attachment 471906 [details]
(In reply to Coacher from comment #3)
> (In reply to Jason Zaman from comment #2)
> > do you have PAX_MARKINGS set in your make.conf?
> > is your /var/tmp/portage/ on a tmpfs?
> > and what happens if you try to manually do:
> > paxctl-ng -mre test/polkitbackend/.libs/polkitbackendjsauthoritytest
> ~ # cd /var/tmp/portage/sys-auth/polkit-0.113/work/polkit-0.113/
> polkit-0.113 # paxctl-ng -mre
> test/polkitbackend/.libs/polkitbackendjsauthoritytest-su: paxctl-ng: command
> not found
Adding to this:
# ls test/polkitbackend/.libs/polkitbackendjsauthoritytest
ls: cannot access 'test/polkitbackend/.libs/polkitbackendjsauthoritytest': No such file or directory
I guess tests are not built without test USE.
Indeed, tests are built according to test USE flag, however even if it is not built, PAX marking does not fail on my system because it looks like paxctl-ng does not fail when given multiple files, some of which does not exist.
So it looks like you could fix it by just upgrading your paxctl installation but there might be something for hardened to look into with paxctl-ng behavior.
i saw this message in my log after world update after recent profile switch... i'm not using hardened either (basically what comment3 says...). that message is kindof irritating, it should at least be a bit more verbose IMHO