Re: Reverting Python 3 Migration Improvements Change
On Mon, 23 Feb 2015 08:11:20 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com wrote: Hi, I have to inform you that I had to revert the Python 3 Migration Improvements change for F22 - more precisely, its parts that would've caused both Python 2 and Python 3 being on atomic host or minimal cloud image. The reason is mentioned in [1] - in short, policycoreutils-python3 has only partial functionality compared to policycoreutils-python, which I didn't understand from my communication with its maintainers previously. It's too late to implement and repackage that now, so I'm reverting the change. ...snip... Thanks for understanding. And huge thanks goes to everyone who took part in this effort. We really did tons of work and were very close - for F23, we're doing this! Regards, Slavek (damn, this was hard to write...) I understand, but I think you made the right call. ;) We can do this right in F23 and get everything lined up now. Thanks a lot for all your work on this change. Its really appreciated by me at least. kevin pgpRn80X_aXxX.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reverting Python 3 Migration Improvements Change
On Mon, Feb 23, 2015 at 8:37 AM, Kevin Fenzi ke...@scrye.com wrote: On Mon, 23 Feb 2015 08:11:20 -0500 (EST) Bohuslav Kabrda bkab...@redhat.com wrote: Hi, I have to inform you that I had to revert the Python 3 Migration Improvements change for F22 - more precisely, its parts that would've caused both Python 2 and Python 3 being on atomic host or minimal cloud image. The reason is mentioned in [1] - in short, policycoreutils-python3 has only partial functionality compared to policycoreutils-python, which I didn't understand from my communication with its maintainers previously. It's too late to implement and repackage that now, so I'm reverting the change. ...snip... Thanks for understanding. And huge thanks goes to everyone who took part in this effort. We really did tons of work and were very close - for F23, we're doing this! Regards, Slavek (damn, this was hard to write...) I understand, but I think you made the right call. ;) We can do this right in F23 and get everything lined up now. Thanks a lot for all your work on this change. Its really appreciated by me at least. Yes, same from me as well. This is a great example of how a Change should look when we reach and don't quite make it. Great communication throughout. Thanks again. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Reverting Python 3 Migration Improvements Change
Hi, I have to inform you that I had to revert the Python 3 Migration Improvements change for F22 - more precisely, its parts that would've caused both Python 2 and Python 3 being on atomic host or minimal cloud image. The reason is mentioned in [1] - in short, policycoreutils-python3 has only partial functionality compared to policycoreutils-python, which I didn't understand from my communication with its maintainers previously. It's too late to implement and repackage that now, so I'm reverting the change. I went on and asked maintainers of packages that are either on atomic host or minimal cloud image to revert the Python 3 changes in F22 (authconfig and firewalld) - I did this myself for packages that didn't seem to have maintainers online (pcp and gettext) - these are the packages marked with (*) in [2] (some of them were supposed to be rebuilt today, so I put a note in BZ to only rebuild for F23). Since both Python interpreters have already been on livedvd for several releases, I think it's still safe to rebuild the rest with Python 3 (== those not marked with (*)) for F22, if their maintainers wish to do so. Either way, this change is not happening for F22 as submitted. For F23, I'll do some updates to [3], then discuss the form of bugreport to mass file here and then do mass filing. Hopefully I'll get to this during this week or next week. Thanks for understanding. And huge thanks goes to everyone who took part in this effort. We really did tons of work and were very close - for F23, we're doing this! Regards, Slavek (damn, this was hard to write...) [1] https://bugzilla.redhat.com/show_bug.cgi?id=1194577#c4 [2] https://fedoraproject.org/wiki/Changes/Python_3_Migration_Improvements#Scope [3] http://fedoraproject.org/wiki/Changes/Python_3_as_Default -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reverting Python 3 Migration Improvements Change
Bohuslav Kabrda wrote: I have to inform you that I had to revert the Python 3 Migration Improvements change for F22 - more precisely, its parts that would've caused both Python 2 and Python 3 being on atomic host or minimal cloud image. The reason is mentioned in [1] - in short, policycoreutils-python3 has only partial functionality compared to policycoreutils-python, which I didn't understand from my communication with its maintainers previously. So we're stuck on an obsolete Python because of SELinux, grrr! Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
