similar to https://bugzilla.mozilla.org/show_bug.cgi?id=711299 I suppose this would require bumping places like: https://dxr.mozilla.org/build-central/source/puppet/modules/packages/manifests/mozilla/python27.pp#48 ? rail: looks like you have done this in the past. Any thoughts? I believe you did windows too judging by: Bug 711299 comment 12 however, I bet windows too is managed by Puppet? Might need to loop in the new windows experts..
(In reply to Jordan Lund (:jlund) from comment #1) > ^ comment 0 and see Bug 711299 comment 7 err I mean, Bug 1257249 comment 7
I have no memories of Python on Windows... IIRC it's managed by puppet now. Q may know. Regarding Python for Ubuntu (which is https://dxr.mozilla.org/build-central/source/puppet/modules/packages/manifests/mozilla/python27.pp#54 actually). IIRC Callek tried to create a package which can be installed in parallel with system python, but I'm not sure if it was successful. We can try multiple options: * upgrade system python to 2.7.4 * upgrade system python to 2.7.11 (!!!) I'd prefer 2.7.11, so we also get better SSL support. Both options require rebuilding the packages in 12.04 from backports.
https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes-python2.7/+packages tells me that it's not impossible to build 2.7.11 on 12.04
ftr - I'm not actively working on this. please yell if this is a blocker and someone from releng needs to pick it up.
Per chat with coop: * We'll update to 2.7.11 * We'll target `build` [and `try`] class of slaves first * Linux `build` slaves will be the last effort out of build slaves, since Taskcluster could make that easier on that end * We'll update `Test` class machines next * And `Server` class machines last (since there is more involved there) Since each type of machine is its own can of worms, We'll do dep bugs off this one for all of the real work
Assignee: nobody → bugspam.Callek
Summary: Deploy python 2.7.4 to all test machines → Deploy python 2.7.11 to all releng machines
I would advise against upgrading the system Python package. From my experience, swapping in a custom built system Python package can lead to unexpected issues. For example, some Python tools installed by the system may rely on the SSL in Python <2.7.9 sucking! I recommend installing Python somewhere in userland (e.g. /opt/python-2.7.11) and running everything explicitly with that Python.
(In reply to Gregory Szorc [:gps] from comment #7) > I would advise against upgrading the system Python package. From my > experience, swapping in a custom built system Python package can lead to > unexpected issues. For example, some Python tools installed by the system > may rely on the SSL in Python <2.7.9 sucking! > > I recommend installing Python somewhere in userland (e.g. > /opt/python-2.7.11) and running everything explicitly with that Python. That is the intent on at least windows, linux and OSX builders. I think ubuntu testers install to system dir though, so if things break there we can revert/investigate
(In reply to Justin Wood (:Callek) from comment #6) > Per chat with coop: > > * We'll update to 2.7.11 > * We'll target `build` [and `try`] class of slaves first > * Linux `build` slaves will be the last effort out of build slaves, since > Taskcluster could make that easier on that end Coop filed bugs for this set already: Bug 1193461 is the main tracker...
Depends on: 1193461
This is something that Buildduty can look into. Not sure though how prioritized so I'll default to P5 to being with.
Component: Platform Support → Buildduty
Priority: -- → P5
Since we are moving to Taskcluster, is this something that we still need?
Andrei, that's a great question. Given that we don't have any blockers on this right now coupled with sentiments we felt here: https://bugzilla.mozilla.org/show_bug.cgi?id=1193461#c6 this is pretty low on priority and we should close this bug in favor of putting efforts elsewhere.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.