On Sun, Mar 13, 2005 at 01:38:37PM +0100, Martin Pitt wrote: > Robert Hunter [2005-03-13 1:21 +1300]: > > I'm upgrading an unused installation and was suprised to > > see the following: > > > > Setting up postgresql (7.4.7-3) ... > > dpkg: error processing postgresql (--configure): > > subprocess post-installation script returned error exit status 10 > > Errors were encountered while processing: > > postgresql > > > I've never seen this; can you please look which debconf version you have > (dpkg -s debconf) and please also try to do > > $ sudo su > # export DEBCONF_DEBUG=developer > # bash -x /var/lib/dpkg/info/postgresql.postinst configure > > This should produce debconf debugging output, maybe this reveals the > bug. The installed debconf is version: 1.4.22 The debugging output from the command listed abpve looks pretty straightforward for the most part (I've saved the full output and I can attach it if needed).
However, this part (right at the end) looks interesting: debconf (developer): starting /var/lib/dpkg/info/postgresql.postinst configure debconf (developer): <-- FSET ucf/changeprompt seen false debconf (developer): --> 10 ucf/changeprompt doesn't exist I'd never heard of ucf before, but it seems that running it from the commandline (in the same way that postinst calls it) shows the same behaviour: exits with return code 10, and no output. A bug in ucf? Interesting that of all the upgrades, only configuring postgres has triggered it. Any ideas? (Thanks for your time, by the way, and have a fantastic day!) -- Clothes make the man. Naked people have little or no influence on society. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]