Hardy Upgrade freezes on phpbb2-conf-mysql

Script being run during freeze:
/usr/bin/ucf --three-way /tmp/phpbb2.config.php.R19308 /etc/phpbb2/config.php

This also occurs when installing the package in hardy. Attaching a strace produces the following (attached while frozen):
"Process 18933 attached - interrupt to quit
read(0,
"

So it seems to be waiting for input, even after the debconf window has closed!

Hi,

This has been fixed elsewhere (e.g. boxbackup) by changing it to use

  ucf --three-way --debconf-ok

and dropping the /dev/tty redirection.

Thanks,

James

Hi,

I have made the modification, could you please test the
packages at

  http://jameswestby.net/scratch/phpbb2_2.0.22-3ubuntu0.1~hardy1_all.deb
  http://jameswestby.net/scratch/phpbb2-conf-mysql_2.0.22-3ubuntu0.1~hardy1_all.deb

However, we need to be careful that installing them a different
way does not mask the bug.

Thanks,

James

Hi,

Attached is the proposed patch if the above .debs work.

Thanks,

James

Yes, the above deb packages work for me.

I had the same problem by installing the packages from the official repository :
Prendre(Take) :3 http://fr.archive.ubuntu.com hardy/universe phpbb2 2.0.22-3 [549kB]
Prendre(Take) :5 http://fr.archive.ubuntu.com hardy/universe phpbb2-conf-mysql 2.0.22-3 [57,2kB]
Dépaquetage(Unpacking) de phpbb2 (à partir de .../phpbb2_2.0.22-3_all.deb) ...
Dépaquetage(Unpacking) de phpbb2-conf-mysql (à partir de .../phpbb2-conf-mysql_2.0.22-3_all.deb) ...
Paramétrage(Configure) de phpbb2 (2.0.22-3) ...
Paramétrage(Configure) de phpbb2-conf-mysql (2.0.22-3) ...
Creating MySQL database...
Creating MySQL user...
Creating MySQL tables if they don't exist yet...
Creating phpbb_sessions_keys table if it doesn't exist yet...
Creating search_time column if it doesn't exist yet...

The script then freezes, as described above.
By using the links you provide, it works (after a warning : an older version is in the repository).

Shouldn't this packages be in the repository ? (since this packages are 3 months old)

James version works flawlessly. Thank you!

This exact bug (it appears to be the exact same) exists on Ubuntu 8.10 as of 9 Oct.