Bug#606707: otrs2: installation fails

2010-12-20 Thread Julien Cristau
tag 606707 squeeze-ignore
kthxbye

On Sat, Dec 11, 2010 at 19:30:01 +0100, Patrick Matthäi wrote:

 @release team:
 Should I fix it with squeeze (only a noteable change for testing
 environments) or should it be squeeze ignore?
 
Tagging squeeze-ignore.  An actual user probably knows what database
backend they want.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#606707: otrs2: installation fails

2010-12-11 Thread Patrick Matthäi
Am 11.12.2010 01:40, schrieb Lucas Nussbaum:
 Package: otrs2
 Version: 2.4.9+dfsg1-3
 Severity: serious
 User: debian...@lists.debian.org
 Usertags: instest-20101207 instest
 
 Hi,
 
 While testing the installation of all packages in squeeze, I ran
 into the following problem:
 

[...]

 + chown root:www-data /var/lib/otrs/Config/ZZZAuto.pm
 + chmod 0664 /var/lib/otrs/Config/ZZZAuto.pm
 + [ -f /etc/otrs/database.pm ]
 + /usr/share/otrs/bin/otrs.RebuildConfig.pl
 dpkg: error processing otrs2 (--configure):
 subprocess installed post-installation script returned error exit status 2
 configured to not write apport reports
 Errors were encountered while processing:
 otrs2
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 -- Stopping postgresql anyway: OK
 Stopping PostgreSQL 8.4 database server: main.
 -- Stopping mysql anyway: OK
 Stopping MySQL database server: mysqld.
 
 The full build log is available from:
  http://people.debian.org/~lucas/logs/2010/12/07/otrs2.log
 
 It is reproducible by installing your package in a clean chroot, using
 the debconf Noninteractive frontend, and priority: critical.
 
 This test was carried out using about 50 AMD64 nodes of the Grid'5000
 platform.  Internet was not accessible from the nodes.
 

Hi Lucas,

I think the problem here is, that your test suite setup otrs2 with
postgres as database backend, but you missed to install libdbd-pg-perl,
just libdbd-mysql-perl is installed (which is a OR dependency).

Could you please verify, if it was installed before, or not?

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/



signature.asc
Description: OpenPGP digital signature


Bug#606707: otrs2: installation fails

2010-12-11 Thread Patrick Matthäi
Am 11.12.2010 11:41, schrieb Lucas Nussbaum:
 On 11/12/10 at 10:54 +0100, Patrick Matthäi wrote:
 Am 11.12.2010 01:40, schrieb Lucas Nussbaum:
 Package: otrs2
 Version: 2.4.9+dfsg1-3
 Severity: serious
 User: debian...@lists.debian.org
 Usertags: instest-20101207 instest

 Hi,

 While testing the installation of all packages in squeeze, I ran
 into the following problem:


 [...]

 + chown root:www-data /var/lib/otrs/Config/ZZZAuto.pm
 + chmod 0664 /var/lib/otrs/Config/ZZZAuto.pm
 + [ -f /etc/otrs/database.pm ]
 + /usr/share/otrs/bin/otrs.RebuildConfig.pl
 dpkg: error processing otrs2 (--configure):
 subprocess installed post-installation script returned error exit status 2
 configured to not write apport reports
 Errors were encountered while processing:
 otrs2
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 -- Stopping postgresql anyway: OK
 Stopping PostgreSQL 8.4 database server: main.
 -- Stopping mysql anyway: OK
 Stopping MySQL database server: mysqld.

 The full build log is available from:
  http://people.debian.org/~lucas/logs/2010/12/07/otrs2.log

 It is reproducible by installing your package in a clean chroot, using
 the debconf Noninteractive frontend, and priority: critical.

 This test was carried out using about 50 AMD64 nodes of the Grid'5000
 platform.  Internet was not accessible from the nodes.


 Hi Lucas,

 I think the problem here is, that your test suite setup otrs2 with
 postgres as database backend, but you missed to install libdbd-pg-perl,
 just libdbd-mysql-perl is installed (which is a OR dependency).

 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$


-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/



signature.asc
Description: OpenPGP digital signature


Bug#606707: otrs2: installation fails

2010-12-11 Thread Lucas Nussbaum
On 11/12/10 at 10:54 +0100, Patrick Matthäi wrote:
 Am 11.12.2010 01:40, schrieb Lucas Nussbaum:
  Package: otrs2
  Version: 2.4.9+dfsg1-3
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: instest-20101207 instest
  
  Hi,
  
  While testing the installation of all packages in squeeze, I ran
  into the following problem:
  
 
 [...]
 
  + chown root:www-data /var/lib/otrs/Config/ZZZAuto.pm
  + chmod 0664 /var/lib/otrs/Config/ZZZAuto.pm
  + [ -f /etc/otrs/database.pm ]
  + /usr/share/otrs/bin/otrs.RebuildConfig.pl
  dpkg: error processing otrs2 (--configure):
  subprocess installed post-installation script returned error exit status 2
  configured to not write apport reports
  Errors were encountered while processing:
  otrs2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  -- Stopping postgresql anyway: OK
  Stopping PostgreSQL 8.4 database server: main.
  -- Stopping mysql anyway: OK
  Stopping MySQL database server: mysqld.
  
  The full build log is available from:
   http://people.debian.org/~lucas/logs/2010/12/07/otrs2.log
  
  It is reproducible by installing your package in a clean chroot, using
  the debconf Noninteractive frontend, and priority: critical.
  
  This test was carried out using about 50 AMD64 nodes of the Grid'5000
  platform.  Internet was not accessible from the nodes.
  
 
 Hi Lucas,
 
 I think the problem here is, that your test suite setup otrs2 with
 postgres as database backend, but you missed to install libdbd-pg-perl,
 just libdbd-mysql-perl is installed (which is a OR dependency).
 
 Could you please verify, if it was installed before, or not?

According, to the log, yes, it was.

- Lucas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606707: otrs2: installation fails

2010-12-11 Thread Lucas Nussbaum
On 11/12/10 at 11:45 +0100, Patrick Matthäi wrote:
 Am 11.12.2010 11:41, schrieb Lucas Nussbaum:
  On 11/12/10 at 10:54 +0100, Patrick Matthäi wrote:
  Am 11.12.2010 01:40, schrieb Lucas Nussbaum:
  Package: otrs2
  Version: 2.4.9+dfsg1-3
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: instest-20101207 instest
 
  Hi,
 
  While testing the installation of all packages in squeeze, I ran
  into the following problem:
 
 
  [...]
 
  + chown root:www-data /var/lib/otrs/Config/ZZZAuto.pm
  + chmod 0664 /var/lib/otrs/Config/ZZZAuto.pm
  + [ -f /etc/otrs/database.pm ]
  + /usr/share/otrs/bin/otrs.RebuildConfig.pl
  dpkg: error processing otrs2 (--configure):
  subprocess installed post-installation script returned error exit status 
  2
  configured to not write apport reports
  Errors were encountered while processing:
  otrs2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  -- Stopping postgresql anyway: OK
  Stopping PostgreSQL 8.4 database server: main.
  -- Stopping mysql anyway: OK
  Stopping MySQL database server: mysqld.
 
  The full build log is available from:
   http://people.debian.org/~lucas/logs/2010/12/07/otrs2.log
 
  It is reproducible by installing your package in a clean chroot, using
  the debconf Noninteractive frontend, and priority: critical.
 
  This test was carried out using about 50 AMD64 nodes of the Grid'5000
  platform.  Internet was not accessible from the nodes.
 
 
  Hi Lucas,
 
  I think the problem here is, that your test suite setup otrs2 with
  postgres as database backend, but you missed to install libdbd-pg-perl,
  just libdbd-mysql-perl is installed (which is a OR dependency).
 
  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.

- Lucas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606707: otrs2: installation fails

2010-12-11 Thread Patrick Matthäi

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?



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606707: otrs2: installation fails

2010-12-11 Thread 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.

- Lucas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606707: otrs2: installation fails

2010-12-11 Thread Patrick Matthäi

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



Bug#606707: otrs2: installation fails

2010-12-11 Thread 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.
 
 - 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)

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

 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?

 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.

- Lucas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606707: otrs2: installation fails

2010-12-11 Thread Patrick Matthäi

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.

- 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)


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.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org