UCF offers merging of configs. So, I find it strange that it didn't in
this case. But, /var/log/distupgrademainlog then gives us an answer:
2008-11-14 11:41:53,153 WARNING no activity on terminal for 240 seconds
(Configuring samba-common)
2008-11-14 12:07:14,942 ERROR got an error from dpkg for
Marking this one as won't fix and moving to update-manager. It's not
samba bug. update-manager waits for 4 minutes for user input. If user
doesn't provide it, it takes some action. In this case, it waited for
user input on ucf. Since user didn't provide input, it picked default
option - merging of
fwiw, here is the root cause:
Setting up samba-common (2:3.2.3-1ubuntu3) ...
Merging changes into the new version
Conflicts found! Please edit `/etc/samba/smb.conf' and sort them out manually.
The file `/etc/samba/smb.conf.ucf-new' has a record of the failed merge of the
configuration file.
Well, I give up. Apparently no one on the Ubuntu team views an upgrade
process which scrambles users' computers to be a serious problem so I
scrubbed the machine and did a fresh installation. Don't bother to post
the normal are you still having the problem you reported six months
ago? can we
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/19650473/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/19650474/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
After the bug report was initially filed, the upgrade process aborted,
with a warning that the system might not work properly. So what do I do
now?
--
package samba-common 2:3.2.3-1ubuntu3 failed to install/upgrade:
https://bugs.launchpad.net/bugs/298126
You received this bug notification
