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.
- Lucas
Doesn't look so:
m...@exez:~/Download$ grep -c libdbd-mysql-perl otrs2.log
12
m...@exez:~/Download$ grep -c libdbd-pg-perl otrs2.log
0
m...@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)
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.
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.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
