Bug 475064 – www-client/firefox-22.0 fails to configure with "_curses.error: setupterm: could not find terminal"

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Mickaël Bucas 2013-06-28 06:25:26 UTC]

I run emerge in an cron job. When trying to install Firefox 22, I get then following error :

[...]
creating ./config.status
Traceback (most recent call last):
  File "./config.status", line 939, in <module>
    config_status(**args)
  File "/var/tmp/portage/www-client/firefox-22.0/work/mozilla-release/build/ConfigStatus.py", line 117, in config_status
    log_manager.add_terminal_logging(level=log_level)
  File "/var/tmp/portage/www-client/firefox-22.0/work/mozilla-release/python/mach/mach/logging.py", line 177, in add_terminal_logging
    if self.terminal:
  File "/var/tmp/portage/www-client/firefox-22.0/work/mozilla-release/python/mach/mach/logging.py", line 149, in terminal
    terminal = blessings.Terminal(stream=sys.stdout)
  File "/var/tmp/portage/www-client/firefox-22.0/work/mozilla-release/python/blessings/blessings/__init__.py", line 98, in __init__
    self._init_descriptor)
_curses.error: setupterm: could not find terminal
[...]

See build log attached.

I think an ebuild should not need a terminal.

Reproducible: Always

Steps to Reproduce:
Start Firefox build in a cron job

Actual Results:  
Firefox build fails

Expected Results:  
Firefox builds normally

[Comment 1 Mickaël Bucas 2013-06-28 06:26:23 UTC]

Created attachment 352138 [details]
build.log

[Comment 2 Mickaël Bucas 2013-06-28 07:09:01 UTC]

As a workaround, I've run the build in a terminal, and the build terminates with success

[Comment 3 Jory A. Pratt 2013-06-30 13:14:25 UTC]

Upstream requires a terminal for setting up the virtual env. If you are not happy with this, please open a bug upstream, you might also concider switching to firefox-bin.

[Comment 4 Ivan Yarych 2013-07-02 06:57:36 UTC]

How about pre-build check or something like that? For early fail.

[Comment 5 Peter Stuge 2013-08-11 23:45:11 UTC]

(In reply to Jory A. Pratt from comment #3)
> Upstream requires a terminal for setting up the virtual env. If you are not
> happy with this, please open a bug upstream

This also affects catalyst builds.

[Comment 6 Peter Stuge 2013-08-12 00:07:35 UTC]

To add some clarification, the error is that the TERM environment variable isn't set to a terminal type that can be found in the terminfo database.

I resolved this with a hack for catalyst. (export TERM=foo in sh scripts)

You could try setting TERM=vt100 in make.conf for manual emerge.

[Comment 7 Rick Farina (Zero_Chaos) 2013-08-12 03:49:46 UTC]

(In reply to Peter Stuge from comment #6)
> To add some clarification, the error is that the TERM environment variable
> isn't set to a terminal type that can be found in the terminfo database.
> 
> I resolved this with a hack for catalyst. (export TERM=foo in sh scripts)
> 
> You could try setting TERM=vt100 in make.conf for manual emerge.

I'm not sure if this is an ugly hack, or a fix for catalyst.  If you would like to open a new bug with your thoughts on this assigned to the catalyst team I would be interested.

[Comment 8 Jory A. Pratt 2013-08-12 13:24:40 UTC]

*** Bug 480726 has been marked as a duplicate of this bug. ***