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.
Our packages .config looks like:
> if [ -f /usr/share/dbconfig-common/dpkg/frontend.config ]; then
> 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"
> dbc_dbtypes="mysql, pgsql"
> dbc_dbuser=zabbix
> dbc_dbname=zabbix
> . /usr/share/dbconfig-common/dpkg/frontend.config
> dbc_go zabbix-frontend-php $@
> fi
and our .postinst:
> dbc_first_version="1:1.4.2-3"
> dbc_generate_include=template:/etc/zabbix/dbconfig.php
> dbc_generate_include_owner="root:www-data"
> dbc_generate_include_perms="640"
> dbc_generate_include_args="-U -o
> template_infile=/usr/share/doc/zabbix-frontend-php/dbconfig.php"
>
> dbc_go zabbix-frontend-php $@
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:
1) What connection method to use (socket / tcp/ip)
2) What Database server to use.
3) What Database port to use.
4) What Database user to use.
now for the issue:
1) prompting is okey here imho.
2) the value from the old config is not preseeded, and this
question could IMHO also be omitted, as we are loading
this value from our old config file (-sDB_SERVER)
3) prompting is okey here imho.
4) the value from the old config file is preseeded here, so
this question could IMHO also be omitted.
bye,
- michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
