[Bug 53049] Re: Fails to upgrade non-interactively
gcc
chris+ubuntu at qwirx.com
Fri Oct 2 10:29:21 BST 2009
It just failed for me on hardy while updating samba, resulting in smbd
not being running this morning:
Subject: Cron <root at fen-apps> apt-get -qq update && apt-get -qq upgrade &&
apt-get clean
(Reading database ... 79236 files and directories currently installed.)
Preparing to replace smbclient 3.0.22-1ubuntu3.8 (using
.../smbclient_3.0.22-1ubuntu3.9_i386.deb) ...
Unpacking replacement smbclient ...
Preparing to replace samba 3.0.22-1ubuntu3.8 (using
.../samba_3.0.22-1ubuntu3.9_i386.deb) ...
* Stopping Samba daemons...
...done.
Unpacking replacement samba ...
Preparing to replace samba-common 3.0.22-1ubuntu3.8 (using
.../samba-common_3.0.22-1ubuntu3.9_i386.deb) ...
Unpacking replacement samba-common ...
Setting up samba-common (3.0.22-1ubuntu3.9) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Setting up smbclient (3.0.22-1ubuntu3.9) ...
Setting up samba (3.0.22-1ubuntu3.9) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Couldn't reopen stdin(/dev/tty): No such device or address at
/usr/sbin/update-inetd line 29.
dpkg: error processing samba (--configure):
subprocess post-installation script returned error exit status 6
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
In other words: same problem, fix *not* released in hardy.
--
Fails to upgrade non-interactively
https://bugs.launchpad.net/bugs/53049
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
More information about the Ubuntu-server-bugs
mailing list