I didn't laugh my ass ofter after discovering that python stopped working
after upgrade. Especially since the package management system depends on a
working python instance.
Right after emerging python-2.7.5:
paxctl-ng -v /usr/bin/python2.7
/usr/bin/python2.7:
PT_PAX : -E---
XATTR_PAX : not found
Let's put there the missing "m":
paxctl-ng -m /usr/bin/python2.7
Check back:
paxctl-ng -v /usr/bin/python2.7
/usr/bin/python2.7:
PT_PAX : -Em--
XATTR_PAX : -em--
If PT_PAX has E, python2.7 would not start on my system.
Let's correct that:
paxctl-ng -e /usr/bin/python2.7
Check back:
paxctl-ng -v /usr/bin/python2.7
/usr/bin/python2.7:
PT_PAX : -em--
XATTR_PAX : -em--
Now python works again.
What should I properly configure the above mentioned behavior? Is it just
my system?
I keep the habit of creating regular binary package archives.
In the mean time, freshly installed firefox binary is correct:
paxctl-ng -v /usr/lib64/firefox/bin/firefox
/usr/lib64/firefox/bin/firefox:
PT_PAX : -em--
XATTR_PAX : -em--
Sidenote:
Even after running migrate-pax -m, there are binaries on the system having
only PT_PAX marking. Example:
migrate-pax -m
paxctl-ng -v /usr/bin/clear
/usr/bin/clear:
PT_PAX : -e---
XATTR_PAX : not found
Is that expected?
Regards:
Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057
