On 07/07/2013 08:15 PM, Alex Efros wrote:
Hi!
On Mon, Jul 08, 2013 at 01:34:07AM +0200, "Tóth Attila" wrote:
I have a feeling some system settings are wrong. These things happen the
same way on my laptop and the server.
I'm too sleepy now and may misunderstood your issue, but at glance:
1) don't enable both PT and XT in kernel, choose only one (XT)
2) https://bugs.gentoo.org/show_bug.cgi?id=465000 may be actual for you,
maybe you should try >=portage-2.1.12.9 (~ARCH now)
>=portage-2.1.12.9 contains an install wrapper I wrote which preserves
xattr pax markings no matter where they are in the ebuild (before or
after install). While it is possible for ebuilds to do something crazy
like using cp instead of install and circumvent this (these should be
fixed anyhow), this bug should now be fixed.
@Toth. Please enable either PAX_PT_PAX_FLAGS or PAX_XATTR_PAX_FLAGS in
your kernel, not both. It is problematic to set both.
In your make.conf set PAX_MARKINGS="PT" in the former case or
PAX_MARKINGS="XT". It is safe to set both: PAX_MARKINGS="PT XT"
On my system, I have "PAX_PT_PAX_FLAGS not set", PAX_XATTR_PAX_FLAGS=y
in my kernel, PAX_MARKINGS="PT XT" in my make.conf and I am using
>=portage-2.1.12.9. So far everything works. Markings get where they
are supposed to go and all the usual problematic packages work.
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
