tags 23871 moreinfo thanks I have no trouble installing login.
------------------------------------------------- [EMAIL PROTECTED] sudo apt-get install login/unstable Reading Package Lists... Done Building Dependency Tree... Done Selected version 1:4.0.3-3 (Debian:unstable) for login 1 packages upgraded, 0 newly installed, 0 to remove and 44 not upgraded. Need to get 255kB of archives. After unpacking 602kB will be used. Get:1 http://ftp.debian.org sid/main login 1:4.0.3-3 [255kB] Fetched 255kB in 1m9s (3652B/s) (Reading database ... 106385 files and directories currently installed.) Preparing to replace login 20000902-12 (using .../login_1%3a4.0.3-3_i386.deb) ... Unpacking replacement login ... Setting up login (4.0.3-3) ... Installing new version of config file /etc/pam.d/login ... Installing new version of config file /etc/login.defs ... Installing new version of config file /etc/securetty ... removing logoutd cruft Removing any system startup links for /etc/init.d/logoutd ... /etc/rc0.d/K20logoutd /etc/rc1.d/K20logoutd /etc/rc2.d/S20logoutd /etc/rc3.d/S20logoutd /etc/rc4.d/S20logoutd /etc/rc5.d/S20logoutd /etc/rc6.d/K20logoutd ------------------------------------------------- More info will be needed in order to reproduce this bug. My guess is that one of dpkg's status files was corrupt when this happened. -- Thomas Hood
