Q: [DONE] dbconfig-common - depends or recommends (preferably depend)?
A: Update documentation to recommend Depends but leave the decision to the discretion of the maintainer as e.g. python binding may not need the full library and the client is too much overhead

Q: [NOT GOING TO BE DONE] dependency on database servers? (without it dbconfig-common might not detect it and will not allow the user to select it in the debconf prompt)
A: Answers on debian-devel suggest this is really unwanted (even recommends is too much)
A: Anyways dbconfig-common detects this.

Q: [DONE] How to solve RC bug #793599 about failure during removal due to client being removed first?
A: Bug dpkg/apt to sort Recommends as well as Depends
A: [DONE] noninteractive can maybe just ignore iso fail
A: Policy seems to not say this explicitely, but 3.9 says that during installation "must not continue after an error."

Remark: openstack is "abusing" config to preseed from configuration file (against the documentation)
 - current behavior needs to be supported until strech release due to backports to jessie

Q: How to fix bug 593154 (active PostgreSQL failure)?
A: Partially: recommend putting dbc_go stuff after #DEB_HELPER# tag in remove (something like this is indeed described in the merged bug 755908)



IDEAS:

- support parsing app specific config files to preserve changes made by users directly to config files
  - maybe provide parsers for a few formats
  - There is a debconf bug open about this already for years, shouldn't it go there?
    - 6903900
  - get rid of registry in /etc/dbconfig-common/<package>.conf
- get dbconfig-common mentioned in the policy
- [DONE] split dbconfig-common into multiple package that DEPEND on their client and
  recommend or suggest the server + dbconf-common-none that conflicts with the
  rest
- check if upgrade code is used by any package and remove it when not used to
  simplify the code base
- add more warnings to the first question that this doesn't always work in cornercases
- mention the required server side packages in the first question
- zigo: multiple python implementations different connection strings