Public bug reported: After building a package, RHEL calls the __os_install_post macro, which invokes brp-python-bytecompile to create .pyc/.pyo files if needed. Without an argument, brp-python-bytecompile would erroneously use the system python instead of the python for which you are building a package, resulting in .pyc/.pyo files with an ABI version corresponding to the system python. brp-python-bytecompile was later updated to intelligently use the python(s) for which you are building a package [0]. This change was made in time to be included in EL6 (rpm >= 4.7.1-8), but EL5 is still affected.
We currently only build python27 and python31 for EL5. Since python 3.1 is EOL this month [1], we will not be correcting the issue for those packages. For all existing python27 packages, we have corrected this by overriding the __os_install_post macro. More details can be found in the comments of the python27 spec file [2]. Not affected (build from main python27 rpm): python27 python27-debug python27-devel python27-libs python27-test Updated: python27-backports python27-backports-ssl_match_hostname python27-setuptools python27-mod_wsgi python27-pip python27-wheel python27-virtualenv python27-psutil python27-lxml The updated builds are already in the testing repos. Please evaluate these and let us know of any issues. [0] https://bugzilla.redhat.com/show_bug.cgi?id=531117 [1] https://www.python.org/download/releases/3.1.5 [2] https://github.com/iuscommunity-pkg/python27/blob/master/SPECS/python27.spec#L59-90 ** Affects: ius Importance: Undecided Status: New -- You received this bug notification because you are a member of IUS Core Development, which is subscribed to IUS Community Project. https://bugs.launchpad.net/bugs/1328603 Title: python27 byte compile magic Status in IUS Community Project: New Bug description: After building a package, RHEL calls the __os_install_post macro, which invokes brp-python-bytecompile to create .pyc/.pyo files if needed. Without an argument, brp-python-bytecompile would erroneously use the system python instead of the python for which you are building a package, resulting in .pyc/.pyo files with an ABI version corresponding to the system python. brp-python-bytecompile was later updated to intelligently use the python(s) for which you are building a package [0]. This change was made in time to be included in EL6 (rpm >= 4.7.1-8), but EL5 is still affected. We currently only build python27 and python31 for EL5. Since python 3.1 is EOL this month [1], we will not be correcting the issue for those packages. For all existing python27 packages, we have corrected this by overriding the __os_install_post macro. More details can be found in the comments of the python27 spec file [2]. Not affected (build from main python27 rpm): python27 python27-debug python27-devel python27-libs python27-test Updated: python27-backports python27-backports-ssl_match_hostname python27-setuptools python27-mod_wsgi python27-pip python27-wheel python27-virtualenv python27-psutil python27-lxml The updated builds are already in the testing repos. Please evaluate these and let us know of any issues. [0] https://bugzilla.redhat.com/show_bug.cgi?id=531117 [1] https://www.python.org/download/releases/3.1.5 [2] https://github.com/iuscommunity-pkg/python27/blob/master/SPECS/python27.spec#L59-90 To manage notifications about this bug go to: https://bugs.launchpad.net/ius/+bug/1328603/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ius-coredev Post to : [email protected] Unsubscribe : https://launchpad.net/~ius-coredev More help : https://help.launchpad.net/ListHelp
