Re: Term Variable in automatic updates SOLVED

2011-01-05 Thread Roger Leigh
On Wed, Jan 05, 2011 at 12:13:40PM +0100, Josep M. Gasso wrote: > Just now I found what was giving error, the package console-setup was > not installed, installing this all is ok, of course I will add the > environment variable DEBCONF_FRONTEND=noninteractive to my script. Please don't top-post.

Re: Term Variable in automatic updates SOLVED

2011-01-05 Thread Josep M. Gasso
Hello. Just now I found what was giving error, the package console-setup was not installed, installing this all is ok, of course I will add the environment variable DEBCONF_FRONTEND=noninteractive to my script. Thanks Josep El mié, 05-01-2011 a las 11:04 +, Roger Leigh escribió: > On Wed, Ja

Re: Term Variable in automatic updates

2011-01-05 Thread Roger Leigh
On Wed, Jan 05, 2011 at 11:31:16AM +0100, Josep M. Gasso wrote: > Hello. > > I have one script for do automatic updates with aptitude, the TERM > variable in my system is xterm > > > $ echo ${TERM} > xterm > > > But, what value should be set for the TERM variable when doing automatic > updates

Term Variable in automatic updates

2011-01-05 Thread Josep M. Gasso
Hello. I have one script for do automatic updates with aptitude, the TERM variable in my system is xterm $ echo ${TERM} xterm But, what value should be set for the TERM variable when doing automatic updates? As now seems that fails for this. Setting up console-setup (1.66) ... debconf: unabl