Am 20.02.2014 11:17, schrieb Patrick Matthäi:
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 fr
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 a
On 2013-05-07 11:33, Patrick Matthäi wrote:
> Am 07.05.2013 11:22, schrieb Andreas Beckmann:
>>applying upgrade script for 3.1.7+dfsg1-8 -> 3.2.0.
>>Trying to connect to database
>>DSN: DBI:mysql:database=otrs2;host=localhost;port=3306;
>>DatabaseUser: otrs
>>
>>Connected.
>>
Am 07.05.2013 11:22, schrieb Andreas Beckmann:
applying upgrade script for 3.1.7+dfsg1-8 -> 3.2.0.
Trying to connect to database
DSN: DBI:mysql:database=otrs2;host=localhost;port=3306;
DatabaseUser: otrs
Connected.
Your storage engine is InnoDB.
These tables use a different
Package: otrs2
Version: 3.2.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (scroll to the bot
5 matches
Mail list logo
