Jon Haugsand wrote:
* Russell Shaw

dpkg --audit
or
dpkg --yet-to-unpack


dpkg --audit
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
 console-common       Basic infrastructure for text console configuration

nbjhh1-laptop:/# dpkg --yet-to-unpack
nbjhh1-laptop:/#


Try: apt-get install -t testing --fix-broken console-common

apt-get install -t testing --fix-broken console-common Reading Package Lists... Building Dependency Tree... Sorry, console-common is already the newest version. 0 packages upgraded, 0 newly installed, 0 to remove and 80 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Setting up console-common (0.7.25) ... Looking for keymap to install: no dpkg: error processing console-common (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: console-common E: Sub-process /usr/bin/dpkg returned an error code (1)

(Tanks for your effort. I must be pretty hopeless..)

dpkg -p console-common shows it pre-depends on debconf.

dpkg -p debconf
shows it depends on a bunch of other things.

I'd either use dselect to install debconf from testing (with all its
suggests/recommends), or:

apt-get update
apt-get install -t testing <all the following packages>

Depends: debconf-i18n | debconf-english
Pre-Depends: perl-base (>= 5.6.1-4)
Recommends: apt-utils (>= 0.5.1)
Suggests: debconf-doc, debconf-utils, whiptail | dialog | gnome-utils,
  libterm-readline-gnu-perl, libgnome-perl, libnet-ldap-perl, perl
Conflicts: cdebconf, debconf-utils (<< 1.1.0), debconf-tiny (<< 1.0),
  apt (<< 0.3.12.1), menu (<= 2.1.3-1), dialog (<< 0.9b-20020814-1),
  whiptail (<< 0.51.4-7), whiptail-utf8 (<= 0.50.17-13)

apt-get install -t testing console-common


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to