hi niko (et al), On Saturday 08 March 2008 02:17:12 pm Niko Tyni wrote:
> 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
aha, that makes sense...
> 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?
i think both of those are overkill, really. the former because phpN-cli would
bring in a chunk of dependencies not needed for other non-php db apps. the
latter because the packager would still need to modify their depends to
ensure this, and in that case they could just add the direct dependencies
that they need instead (i.e. php5-cli). this is would also be in line with
the approach that i've taken towards the same problem with needing the
database client programs (mysql/pgsql/sqlite).
> 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.)
also, the dbconfig-common stuff could handle it a bit smarter, for the cases
where d-l-i is being automagically invoked. for example, d-l-i could be
patched with a "dry run" or "query" mode, which could be run immediately
close to the beginning of dbc_go(), and if failure occurred, the script could
automatically defer. additionally, a failure of the same thing in the second
call of the config script could be detected, and an informative error could
be displayed via debconf.
> As for dbconfig-common, at least documenting the issue and possibly a
> Suggests: php5-cli seem to be needed.
that seems reasonable too.
sean
signature.asc
Description: This is a digitally signed message part.
