Am 18.02.2014 01:33, schrieb Andreas Beckmann:
This is a wanted behaviour, from the 3.2.1+dfsg1-1 changelog:
* Drop patch 24-default-myisam and check with the new otrs.CheckDB.pl
script,
if the available tables and the used storage engine are equal. If it is not
the case the installation should abort, so that the administrator can fix
his MySQL server or the already created tables.
Closes: #690306
If it's too difficult to sort this out automatically, the package needs
to carry documentation how to solve this manually. (My first try was
README.Debian.) And ideally the error message should point to this
documentation.
Automagic is not possible. I have added the following to README.Debian:
Upgrading to MySQL >= 5.5:
--------------------------
Since MySQL 5.5 changed its default storage engine from MyISAM to InnoDB you
might encounter problems on upgrading OTRS from the otrs.CheckDB.pl script.
Here you will find additional notes about this problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707075
Here you will find a possible solution:
http://blog.otrs.org/2013/02/20/about-otrs-mysql-myisam-and-innodb-storage-engines/
And I wouldn't mind a receipe how I can fix this up easily in piuparts
in a scriptable way (either changing mysql config or doing some sql or
whatever).
For piuparts it might be a better idea to test it with Postgres as
database backend, or while you upgrade your MySQL server adding
default-storage-engine=MYISAM to the my.cnf, but this is ugly.
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
