This may or may not be related to this update, but I noticed some SELinux errors for some python3 programs trying to write to their __pycache__ directories lately (for example abrt and firewalld).
@decathorpe thank you for testing it. This seems to be related to SELinux policy that those packages (abrt and firewald) ship. But can you provide some more details on the errors?
All of those are caused by python3 trying to write to a __pycache__ directory ... maybe something changed in python that causes the interpreter to re-compile some cached files?
This update requires re-building all python3-packages, because it bumps the python magic-bytes from 3350 (for Python 3.5) to 3351 (for Python 3.5.3) and thus invalidates the pre-built pycache.
One can easily verify by installing this update, rpmbuilding a python3-package and run rpmlint on it.
Good catch besser82. The issue is actually http://bugs.python.org/issue27286 where upstream bumped the magic number, something that is not supposed to happen between minor releases. The fedora package issue is being worked on currently in order to keep the same magic number.
I tested the update on a VM and everything seems to work OK. However, I am refraining from giving karma due to the magic number issue cited by @besser82, which I have not independently verified.
This update has been submitted for testing by ishcherb.
ishcherb edited this update.
ishcherb edited this update.
New build(s):
This update has been pushed to testing.
No regressions here on x86_64.
Works fine on x86_64.
Works great! LGTM! =)
works for me
No regressions noted.
No regressions
Works
LGTM
looks good to me
Works for me.
No issues or regressions encountered.
works for me
This may or may not be related to this update, but I noticed some SELinux errors for some python3 programs trying to write to their
__pycache__directories lately (for example abrt and firewalld).@decathorpe thank you for testing it. This seems to be related to SELinux policy that those packages (abrt and firewald) ship. But can you provide some more details on the errors?
@ishcherb sure I can:
firewalld error: https://gist.github.com/decathorpe/93f32ad919183ca723223b7f83cff672
gdb error: https://gist.github.com/decathorpe/3d2fff9726698202b0db710e0b885126
abrt-action-not error: https://gist.github.com/decathorpe/b534591422a782ebd5165ca65d7c840e
All of those are caused by python3 trying to write to a
__pycache__directory ... maybe something changed in python that causes the interpreter to re-compile some cached files?At a closer look:
This update requires re-building all python3-packages, because it bumps the python magic-bytes from
3350(for Python 3.5) to3351(for Python 3.5.3) and thus invalidates the pre-built pycache.One can easily verify by installing this update, rpmbuilding a python3-package and run rpmlint on it.
Please unpush asap or fix it.
Good catch besser82. The issue is actually http://bugs.python.org/issue27286 where upstream bumped the magic number, something that is not supposed to happen between minor releases. The fedora package issue is being worked on currently in order to keep the same magic number.
abrt, firewalld etc issues originate from that
https://bugzilla.redhat.com/show_bug.cgi?id=1420986
works fine
I tested the update on a VM and everything seems to work OK. However, I am refraining from giving karma due to the magic number issue cited by @besser82, which I have not independently verified.
After some investigation I was able to reproduce the issue mentioned by @besser82
Thanks for testing. The magic number issue is being worked on, hence unpushing the update.
This update has been unpushed.
ishcherb edited this update.
Removed build(s):
This update has been submitted for testing by ishcherb.
This update has been obsoleted by python3-3.5.3-3.fc25.