Comment 7 for bug 311981

Revision history for this message
Gerry Reno (greno-verizon) wrote :

I just pulled bzr and tested the client and still seeing an error:
...
-rwxrwxr-x greno/greno 8059 2008-12-30 09:33:53 openerp-client-5.0.0_rc2/setup.py
-rw-rw-r-- greno/greno 705 2008-11-29 21:21:02 openerp-client-5.0.0_rc2/Makefile
-rw-rw-r-- greno/greno 166 2008-12-31 08:32:22 openerp-client-5.0.0_rc2/MANIFEST.in
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd openerp-client-5.0.0_rc2
++ /usr/bin/id -u
+ '[' 500 = 0 ']'
++ /usr/bin/id -u
+ '[' 500 = 0 ']'
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.83672
+ umask 022
+ cd /home/greno/build/python-dist/openerp-client-5.0.0_rc2/build/bdist.linux-i686/rpm/BUILD
+ cd openerp-client-5.0.0_rc2
+ LANG=C
+ export LANG
+ unset DISPLAY
+ python setup.py build
Traceback (most recent call last):
  File "setup.py", line 129, in ?
    check_modules()
  File "setup.py", line 68, in check_modules
    exec('import %s' % modname)
  File "<string>", line 1, in ?
  File "/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 76, in ?
    _init()
  File "/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 64, in _init
    _gtk.init_check()
RuntimeError: could not open display
error: Bad exit status from /var/tmp/rpm-tmp.83672 (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.83672 (%build)
error: command 'rpmbuild' failed with exit status 1
============================================

We build everything through remote terminal sessions so setup should not be requiring a display. There is no display.