[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: trouble installing the latest ssh from woody



Here's what I get now.  any idea what's going on?

danjah:/home/tim# DEBCONF_DEBUG=developer apt-get install ssh
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
  ssh 
0 packages upgraded, 1 newly installed, 0 to remove and 0  not upgraded.
2 packages not fully installed or removed.
Need to get 0B/600kB of archives. After unpacking 1352kB will be used.
Preconfiguring packages ...
debconf (developer): starting /tmp/config.97771 configure 
debconf (developer): <-- VERSION 2.0
debconf (developer): --> 0 2.0
debconf (developer): <-- SET ssh/use_old_init_script true
debconf (developer): --> 10 ssh/use_old_init_script doesn't exist
debconf (developer): <-- FSET ssh/use_old_init_script isdefault false
debconf (developer): --> 10 ssh/use_old_init_script doesn't exist
debconf (developer): <-- INPUT medium ssh/protocol2_only
debconf (developer): --> 10 "ssh/protocol2_only" doesn't exist
debconf (developer): <-- INPUT medium ssh/SUID_client
debconf (developer): --> 10 "ssh/SUID_client" doesn't exist
debconf (developer): <-- INPUT medium ssh/run_sshd
debconf (developer): --> 10 "ssh/run_sshd" doesn't exist
debconf (developer): <-- INPUT low ssh/forward_warning
debconf (developer): --> 10 "ssh/forward_warning" doesn't exist
debconf (developer): <-- GO 
debconf (developer): --> 0 ok
(Reading database ... 64061 files and directories currently installed.)
Unpacking ssh (from .../ssh_1%3a3.0.2p1-8_i386.deb) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is ssh
debconf (developer): starting /var/lib/dpkg/tmp.ci/config configure 
debconf (developer): <-- VERSION 2.0
debconf (developer): --> 0 2.0
debconf (developer): <-- SET ssh/use_old_init_script true
debconf (developer): --> 10 ssh/use_old_init_script doesn't exist
debconf (developer): <-- FSET ssh/use_old_init_script isdefault false
debconf (developer): --> 10 ssh/use_old_init_script doesn't exist
debconf (developer): <-- INPUT medium ssh/protocol2_only
debconf (developer): --> 10 "ssh/protocol2_only" doesn't exist
debconf (developer): <-- INPUT medium ssh/SUID_client
debconf (developer): --> 10 "ssh/SUID_client" doesn't exist
debconf (developer): <-- INPUT medium ssh/run_sshd
debconf (developer): --> 10 "ssh/run_sshd" doesn't exist
debconf (developer): <-- INPUT low ssh/forward_warning
debconf (developer): --> 10 "ssh/forward_warning" doesn't exist
debconf (developer): <-- GO 
debconf (developer): --> 0 ok
debconf (developer): starting /var/lib/dpkg/tmp.ci/preinst install
debconf (developer): <-- VERSION 2.0
debconf (developer): --> 0 2.0
debconf (developer): <-- GET ssh/use_old_init_script
debconf (developer): --> 10 ssh/use_old_init_script doesn't exist
dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--unp
ack):
 subprocess pre-installation script returned error exit status 10
Errors were encountered while processing:
 /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
danjah:/home/tim# 


I'm also getting exit status 10 while trying to upgrade cvs and ash,
and while trying to uninstall gdm

Is my debconf setup just messed up?  Is there an easy way to clean it
up?

thanks,
Tim


On Wed, Mar 13, 2002 at 02:59:47PM -0600, Colin Watson wrote:
> On Wed, Mar 13, 2002 at 11:36:09AM -0500, Tim Olsen wrote:
> > I'm having trouble installing the latest ssh from woody:
> [..]
> > dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--install):
> >  subprocess pre-installation script returned error exit status 10
> 
> Exit code 10 is usually a debconf error. Try it with
> DEBCONF_DEBUG=developer set in the environment.
> 
> Cheers,
> 
> -- 
> Colin Watson                                  [cjwatson@flatline.org.uk]
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: