Am 11.12.2010 19:23, schrieb Lucas Nussbaum:
On 11/12/10 at 19:10 +0100, Patrick Matthäi wrote:Am 11.12.2010 18:53, schrieb Lucas Nussbaum:On 11/12/10 at 17:34 +0100, Patrick Matthäi wrote:Am 11.12.2010 12:38, schrieb Lucas Nussbaum:Could you please verify, if it was installed before, or not?According, to the log, yes, it was. - LucasDoesn't look so: me@exez:~/Download$ grep -c libdbd-mysql-perl otrs2.log 12 me@exez:~/Download$ grep -c libdbd-pg-perl otrs2.log 0 me@exez:~/Download$Sorry, I thought that "it" was libdbd-mysql-perl.No problem ;) Are you okay with closing this bug?Why should it be closed? This sounds like a real bug if you can end up in a situation where the package won't be installable.I fully agree with you, but this is a limitation of our dependency system, which appears in much more package: otrs2 supports postgres and mysql as database backend. Both servers are needed (like a dependency), but surely also a remote server could be used (that's why it is recommends). The same is the case for the dbd driver, but okay one of them has to be installed on the system, the mysql or the pg one (or dependency). Debian needs something like: Depends: (a&& b) | (c&& d)Well, you could use a dependency package if you wanted to do that. Package: ab Depends: a, b Package: cd Depends: c, d Package: otrs2 Depends: ab | cd
This would be a good idea for my otrs3 package and would also solve the client problem, but I can still not depend with the -mysql package e.g. on mysql-server, many users (myself) would complain :)
But this also would not solve the problem with the remote database server. So what has your build script now done? It was a stupid user, it installed postgres and mysql server, but only the mysql DBD driver and then it decided to use postgres as database backend.Would it be possible that the mysql DBD driver comes first in the recommends list (so APT prefers it), but that the debconf template defaults to postgres?
dbconfig-common defaults to postgres here, but yeah I could change the order if the depends, so that postgres would be the default one, but it would not be a great functional change, just for testing environments.
This is not a bug, which is solvable with the otrs packaging, only if I would drop e.g. the support for postgres and then add Depends: mysql-server, libdbd-mysql-perl You will find this "bug" (misshandling?) in many packages.Actually, I don't, that's why it's surprising.
If you choose another database backend, you will, but okay the default handling may be the problem ;)
@release team:Should I "fix" it with squeeze (only a noteable change for testing environments) or should it be squeeze ignore?
Cheers.