Closed Bug 803830 Opened 12 years ago Closed 12 years ago

Lightning linux & win32 build fail 'configure: error: Cannot build on Python 2.5. You need at least 2.6.'

Categories

(Calendar :: Build Config, defect)

Lightning 2.1
All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ssitter, Unassigned)

References

Details

Linux x86 and x64 comm-central lightning nightly builds are failing again. 
This time because of incorrect Python version:

> checking for Python version >= 2.6 but not 3.x... 
> configure: error: Cannot build on Python 2.5. You need at least 2.6.
Downloading Packages:
(1/3): libffi-3.0.5-1.el5 100% |=========================|  21 kB    00:00     
(2/3): python26-libs-2.6. 100% |=========================| 670 kB    00:00     
(3/3): python26-2.6.8-1.e 100% |=========================| 6.5 MB    00:00     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : libffi                                                   1/3 
  Installing     : python26                                                 2/3 
  Installing     : python26-libs                                            3/3 

Installed: python26.i386 0:2.6.8-1.el5
Dependency Installed: libffi.i386 0:3.0.5-1.el5 python26-libs.i386 0:2.6.8-1.el5

Complete!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
WINNT 5.2 comm-central lightning nightly failed with the very same error today. Could you upgrade it too?
I've changed the path to use python2.7. I might need to install some additional modules, we'll see about that in the next build run. I'd appreciate if you could monitor the builds and file a new bug or comment on this one once its through in case there are some python modules missing.
Win32 comm-central and comm-aurora lightning nightly failed with
>   _=d:/mozilla-build/python27/python
>  closing stdin
>  using PTY: False
> Traceback (most recent call last):
>   File "tools/buildfarm/maintenance/purge_builds.py", line 31, in <module>
>     import win32file
> ImportError: No module named win32file
Installed pywin32, lets hope it works. Thanks for the report!
Win32 comm-aurora lightning nightly build succeeded. Win32 comm-central lightning nightly build failed. Seems it still uses the old Python version 2.5:

> checking for python2.7... (cached) /d/mozilla-build/python25/python2.5
> Creating Python environment
> *** Fix above errors and then restart with               "make -f client.mk build"
> make[1]: Leaving directory `/e/builds/slave/cc-win32-nightly/build'
> e:/builds/slave/cc-win32-nightly/build/mozilla/build/virtualenv/populate_virtualenv.py:170: Warning: 'with' will become a reserved keyword in Python 2.6
>   File "e:/builds/slave/cc-win32-nightly/build/mozilla/build/virtualenv/populate_virtualenv.py", line 170
>     with open(os.path.join(python_lib, package[0]), 'a') as f:
>             ^
> SyntaxError: invalid syntax
> configure: error: /e/builds/slave/cc-win32-nightly/build/mozilla/configure failed for mozilla
Summary: Lightning linux build fail 'configure: error: Cannot build on Python 2.5. You need at least 2.6.' → Lightning linux & win32 build fail 'configure: error: Cannot build on Python 2.5. You need at least 2.6.'
Probably needs a clobber only. I've started deleting files, one of the next builds will probably work.
Win32 comm-central lightning nightly build still fails with the error from Comment 6: https://tinderbox.mozilla.org/showlog.cgi?log=CalendarTrunk/1351246356.1351248056.23116.gz#err3
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Todays error message indicates that only Python 2.5 is installed / found on the server: https://tinderbox.mozilla.org/showlog.cgi?log=CalendarTrunk/1351591200.1351592340.5383.gz#err0

> checking for python2.7... no
> checking for python2.6... no
> checking for python2.5... /d/mozilla-build/python25/python2.5
Aurora is green, central has moved to Thunderbird build infra. I think we can close this bug?
Error shows on https://tinderbox.mozilla.org/showbuilds.cgi?tree=Calendar-Aurora

Maybe we can just stop the builders now that bug 793628 is activated for comm-aurora?
I've stopped the aurora builders on our infra and removed the *-xpi directories, therefore this should be WFM with the new infra.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.