Re: debconf 0.1.71 broken

1999-11-02 Thread Hartmut Koptein
> The autobuilder built whiptail (which is within the newt source package) > against newt0.30 while it was building libnewt 0.50. Nice chicken or egg > problem, eh? I uploaded new binaries to master yesterday which are correctly > linked against newt 0.50. It is already fixed: isis:~# dpkg -s w

Re: debconf 0.1.71 broken

1999-11-02 Thread Matt Porter
On Tue, Nov 02, 1999 at 08:53:50AM +0100, christian mock wrote: > X-Mailer: exmh version 2.0.2 2/24/98 > To: Frank Petzold <[EMAIL PROTECTED]> > Cc: debian-powerpc@lists.debian.org > Subject: Re: debconf 0.1.71 broken > In-Reply-To: Your message of "Tue,

Re: debconf 0.1.71 broken

1999-11-02 Thread christian mock
--- Begin Message --- > I get the same error with the latest version now (0.2.5?). It seems that > some script that is sourced by debconf.postinst exits. I chased that one down in my setup, it was debconf deciding to use whiptail, which didn't run (some library problem, IIRC). Setting the envir

Re: debconf 0.1.71 broken

1999-11-02 Thread Frank Petzold
Thus spake Frank Petzold ([EMAIL PROTECTED]): > When I try to install debconf, I get: > > Setting up debconf (0.1.71) ... > dpkg: error processing debconf (--configure): > subprocess post-installation script returned error exit status 127 > I get the same error with the latest version now (0.2

debconf 0.1.71 broken

1999-10-28 Thread Frank Petzold
When I try to install debconf, I get: Setting up debconf (0.1.71) ... dpkg: error processing debconf (--configure): subprocess post-installation script returned error exit status 127 I tried to install an older version, this now fails also. I tried to have a look at the scripts that are execut