hardy->intrepid upgrade failed

[Michael Vogt]

Binary package hint: samba

A upgrade from hardy to intrepid failed with the following message:

Setting up samba-common (2:3.2.3-1ubuntu2) ...
dpkg: error processing samba-common (--configure):
 subprocess post-installation script returned error exit status 1

It seems like this happend in the ucf prompt (but that is just a guess currently). Wenn "dpkg --configure -a" is run later (as a attempt to recover) the following is displayed on the screen:

Setting up samba-common (2:3.2.3-1ubuntu2) ...
Package configuration
  ┌────────────────────────────┤ Samba Server ├─────────────────────────────┐
  │ A new version of configuration file /etc/samba/smb.conf is available, │
  │ but the version installed currently has been locally modified. │
  │ │
  │ What would you like to do about smb.conf? │
  │ │
  │ install the package maintainer's version │
  │ keep the local version currently installed │
  │ show the differences between the versions │
  │ show a side-by-side difference between the versions │
  │ show a 3-way difference between available versions │
  │ do a 3-way merge between available versions (experimental) │
  │ start a new shell to examine the situation │
  │ │
  │ │
  │ <Ok> │
  │ │
  └─────────────────────────────────────────────────────────────────────────┘

I will attach the full log.

[Michael Vogt (mvo)]

This happend to 'silbs' in the office, I think its not unlikely that cancel was pressed (that results in the exit status 1 error).

[Steve Langasek (vorlon)]

Can you please attach all of /etc/samba/smb.conf*, to see why there was a user prompt in the first place?

[Michael Vogt (mvo)]

I'm a proxy here, but I will forward the request.

I suspect that the error happend because cancel was clicked, I uploaded a new debconf gnome version that will not show cancel (and the window close button) when release upgrades are in progress so I think this part of the bug can be closed.

[Steve Langasek (vorlon)]

Why should hiding of the cancel button be specific to release upgrades? That sounds wrong to me, I think the UI should be consistent across all uses of the debconf GNOME frontend (i.e., hide it in all cases).