Problem removing software with APT

**Compunuts** · 09-12-2003, 08:03 AM

First was when I did "dist-upgrade" the system. My Courier-MTA goes nuts. Almost the same type of error. Then, it's this.

Code:

SUPRA:/home/compunuts# apt-get dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages have been kept back
  mysql-navigator
0 packages upgraded, 0 newly installed, 0 to remove and 1  not upgraded.
3 packages not fully installed or removed.
Need to get 0B of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n]
Setting up console-common (0.7.25) ...
Looking for keymap to install:
us
dpkg: error processing console-common (--configure):
 subprocess post-installation script returned error exit status 127
Setting up console-data (2002.12.04dbs-16) ...
Looking for keymap to install:
us
dpkg: error processing console-data (--configure):
 subprocess post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of base-config:
 base-config depends on console-data (&gt;= 1999.08.29-13); however:
  Package console-data is not configured yet.
dpkg: error processing base-config (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 console-common
 console-data
 base-config
E: Sub-process /usr/bin/dpkg returned an error code (1)
SUPRA:/home/compunuts#

So now, what's the remedy for this?

Second, when I did "apt-get -clean", I have this.

Code:

SUPRA:/home/compunuts# apt-get -clean
E: Opening configuration file lean - ifstream::ifstream (2 No such file or directory)
SUPRA:/home/compunuts#

Is that mean my APT tool is doomed?

Appreciate any pointers for this.

TIA

**demian** · 09-14-2003, 06:40 PM

Hmm. Exit status 127 means "command not found". So it seems that the post-install script calls some command that is not in your path. This shouldn't happen unless you messed with root's $PATH or you're using unstable (where this might happen occasionally).

On my debian unstable system root's $PATH reads:

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11

Maybe you will have to try and identify the post-install script (no idea where I would look, though) and see what happens there.