The problem is indeed with eucalyptus. There is now a check in the init script that will make it fail if the EUCALYPTUS value of the configuration file is "not_configured". The config that shipped in the last version indeed was. Somehow, the config file did not got upgraded to the new version, despite that I did accept the package maintainer's version. Manually fixing the config file makes the eucalyptus-nc start, and I can fix the package installation with "apt-get install -f".
The problem is indeed with eucalyptus. There is now a check in the init script that will make it fail if the EUCALYPTUS value of the configuration file is "not_configured". The config that shipped in the last version indeed was. Somehow, the config file did not got upgraded to the new version, despite that I did accept the package maintainer's version. Manually fixing the config file makes the eucalyptus-nc start, and I can fix the package installation with "apt-get install -f".