bash does not export variables (was Re: CORRECTION: ^c broken in latest potato)

2000-01-09 Thread Andrei D. Caraman
On Sat, Jan 08, 2000 at 05:34:52PM -0800, Alex Romosan wrote: > ... when i am logged in as root using bash > as my shell things start to break. also, bash doesn't seem to export > environment variables. this breaks a lot of scripts. we better get > this fixed soon. I suppose you did a `set -a',

Re: CORRECTION: ^c broken in latest potato

2000-01-09 Thread Bob Nielsen
Today's potato upgrade has debconf 0.2.67 which fixes the problem. On Sun, Jan 09, 2000 at 02:02:40AM -, Pollywog wrote: > I also read (on Dalnet #debian) this morning that debconf is broken so it > should not be upgraded. > > -- > Andrew > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL

Re: CORRECTION: ^c broken in latest potato

2000-01-09 Thread Pollywog
I also read (on Dalnet #debian) this morning that debconf is broken so it should not be upgraded. -- Andrew

Re: CORRECTION: ^c broken in latest potato

2000-01-09 Thread Alex Romosan
George Bonser <[EMAIL PROTECTED]> writes: > ^C only seems to be broken for SOME programs. > > If I, for example, go to /var/lib/dpkg/info and do an ls ... a ^C will not > stop it. > > If I issue ^C at the bash prompt, I get a new prompt. ^C also seems to > kill top. > > ^C will not kill a ps