Am 08.01.20 um 15:55 schrieb Dominique Leuenberger / DimStar:
On Wed, 2020-01-08 at 15:38 +0100, Wolfgang Rosenauer wrote:
Hi,
Now what needs to be done: 1) package can be using just py2 and needs it -> remove it 2) package has optional support of py2 a) remove the part if you don't plan backporting b) add %bcond_without python2 and wrap it in if statements for the opensuse_version to enable it on old codestreams
After the bulk of 'killing' is done we will continue by creating specialized staging project where we will switch off the build of python2-* packages and have another list of stuff that needs adjustments.
do we know what will break in Tumbleweed when Python2 is removed? What if things break which we cannot fix short and mid term but which are essential for Tumbleweed?
If we talk about essential stuff in TW, then I'm afraid the 'drop python2 team' will have to step up their game. the final removal of python2 can only happen when Stagings pass.
IIRC, Firefox still uses py2 in its own build system too. So that for one will be a fun challenge already. Clearly, I will not accept a python2 delreq before Firefox can build without it.
that case was what I had in mind when I asked the question. The Firefox buildsystem is highly complex and switching everything to Python3 is not happening short term. The upstream meta bug was opened 2 years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1388447 And this is nothing we can accelerate much. Actually probably the 'drop python2 team' can assist upstream so it will be done soon(er)? Anyway feel free to drop python2 stuff as long as other packages do not break or can be fixed from our side. At least I cannot "fix" Firefox on my own. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org