902520 - Update all foopies to Python 2.7.3

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[(not currently active) Ted Mielczarek]

Joel tells me that foopies are still running Python 2.6.6 (bug 715884 comment 10). I am disappoint. We should get them updated to 2.7.3 so we don't have to deal with Python < 2.7 anywhere.

Comment 1

[Justin Wood (:Callek)]

Useful info:

[[e-mail] ~]$ which -a python2.7
/usr/local/bin/python2.7
/usr/local/bin/python2.7
[[e-mail] ~]$ ls -la `which -a python2.7`
lrwxrwxrwx 1 root root 29 Apr 12 11:45 /usr/local/bin/python2.7 -> /tools/python27/bin/python2.7
lrwxrwxrwx 1 root root 29 Apr 12 11:45 /usr/local/bin/python2.7 -> /tools/python27/bin/python2.7
[[e-mail] ~]$ ls -la `which -a python2`
lrwxrwxrwx. 1 root root 6 Mar 18 06:06 /usr/bin/python2 -> python
[[e-mail] ~]$ ls -la `which -a python`
-rwxr-xr-x 2 root root 9176 Dec  7  2011 /usr/bin/python
[[e-mail] ~]$ find /tools/python\* -name python
find: `/tools/python*': No such file or directory
[[e-mail] ~]$ find /tools/python* -name python
/tools/python
[[e-mail] ~]$ find /tools/python* -name python\*
/tools/python
/tools/python2
/tools/python26
/tools/python26/bin/python2.6
/tools/python26/bin/python2.6-config
/tools/python26/include/python2.6
/tools/python26/include/python2.6/pythonrun.h
/tools/python26/lib/python2.6
/tools/python26/lib/python2.6/config/python.o
/tools/python26/lib/python2.6/idlelib/Icons/python.gif
/tools/python27
/tools/python27/bin/python2.7
/tools/python27/bin/python2.7-config
/tools/python27/include/python2.7
/tools/python27/include/python2.7/pythonrun.h
/tools/python27/lib/python2.7
/tools/python27/lib/python2.7/config/python.o
/tools/python27/lib/python2.7/idlelib/Icons/python.gif
/tools/python27/lib/pkgconfig/python-2.7.pc
/tools/python27-mercurial
/tools/python27-mercurial/lib/python2.7
[[e-mail] ~]$ echo $PATH
/usr/local/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/cltbld/bin


So it looks like there is no `python` binary of py2.7, probably worth making sure there is one, and then making sure PATH will find it first. trying to call python2.7 likely will be a lot harder.

:dustin do you recall why our mozilla* py rpm's don't include |python| ?

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Nope - the whole process and logic of creating those RPMs was pretty mysterious to me.  I don't see any reason not to add it for 2.7 and, once that's done, rm -rf the heck out of the python26 package.

Comment 3

[Armen [:armenzg]]

What are the next steps for this bug? I see the dep bug fixed.

Comment 4

[Justin Wood (:Callek)]

(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #3)
> What are the next steps for this bug? I see the dep bug fixed.

* Update PATH as used on foopies for watch_devices (and subsequently for buildbot)
* Delete *.pyc generated from py2.6 in tools repo
* Stage said change
* Deploy said change

This should be pretty easy to do, I'm wanting to stagger this change outside of the other larger-impact changes we're making of course.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Do we have an update for this bug? Are we going to upgrade those machines?

Comment 6

[Jonathan Griffin (:jgriffin)]

Can we close this bug now that tegras are history?

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

I don't see why not.