On Thu, Sep 20, 2007 at 10:06:35AM +0200, Michael Ablassmeier wrote: > Package: dbconfig-common > Version: 1.8.36 > Severity: normal > > hi sean, > > we have been migrating our packages to use dbconfig-common for the frontend > code aswell, which means we have to migrate our old configuration file > creation > to the handling with dbconfig-common.
> > dbc_first_version="1:1.4.2-3" > > dbc_load_include="php:/etc/zabbix/dbconfig.php" > > dbc_load_include_args="-tDB_TYPE -sDB_SERVER -dDB_DATABASE -uDB_USER > -pDB_PASSWORD" > while upgrading zabbix-frontend-php from 1.4.2-2 to 1.4.2-3 dbconfig-common > notices its converting from an old configuration file and starts prompting > several questions: Hi, I can reproduce this when php5-cli is not installed. The problem is that dbconfig-load-include needs /usr/bin/php to read in the old dbconfig.php file. There should be something like migrating old settings into dbconfig-common: failed. in /var/log/dbconfig-common/dbc.log in this case. Consider: % dbconfig-load-include -f php /tmp/t.php error: php format but i can't find a php binary! I'm not versed in PHP at all, but at least php5-cli provides /usr/bin/php through the alternatives system. This could be fixed by making dbconfig-common depend on php5-cli, but looking at its dependencies, that seems overkill. Hm, how about a separate dbconfig-common-php package? Lacking that, I suppose the zabbix-frontend-php package should depend on php5-cli, and its .config script should defer the package configuration with an 'exit 0' if /usr/bin/php is not there yet (as the dependency isn't necessarily satisfied yet when preconfiguring.) As for dbconfig-common, at least documenting the issue and possibly a Suggests: php5-cli seem to be needed. Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
