debdiff attached. It's in the spirit of the Debian fix: checks for /etc
/dbconfig-common/zabbix-server-{my,pg}sql files and sets db_type
accordingly. It falls back to previous behaviour if those files don't
exist.This fixes the problem if the frontend and server packages are installed on the same machine by auto-detecting which server type was installed. However, the problem still exists for instances where the server is remote from the frontend. Probably, the zabbix package should make the db_type question "high" priority, but I didn't feel comfortable making that change. Regardless of a change in question priority, this fix is nice because it auto-detects in the local case. ** Attachment added: "patch to choose db_type based on installed zabbix server" http://launchpadlibrarian.net/10315714/zabbix_1.4.1-2ubuntu0.1.debdiff -- db_type is set to MYSQL even when using zabbix-server-pgsql https://bugs.launchpad.net/bugs/161083 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
