OK, so I managed to reproduce this and find out the cause. While adding an extra check for cases of upgrading from 1.2 to 2.0, I managed to break cluster init in the Debian init script (upstream init script is fine, but gives more errors).
I'll try to cook up a fixed one ASAP. In the meantime, remove the for/if block in the init script that contains this: log_warning_msg "Configuration not upgraded to 2.0, will not run." thanks, iustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
