Hi,

just updated my sources fiile on a Debian Jessie server to upgrade from OpenProject 6.15 to 7.0 (openproject:amd64 7.0.0-1496397818.c893b74.jessie)
apt-get upgrade worked fine and it urged me to run openproject configure as usual.

I have to say it is UNACCEPTABLE to get mariadb REMOVED in favour of mysql WITHOUT ASKING. Absolute No-Go to autoremove packages even in a manually started configuration task. I ctrl-c’d during download and browsed the forums…

Here it says one should run openproject reconfigure. I switched from “install” to “reuse” of the local DB system. This fails with the very exciting error message

E: Unable to correct problems, you have held broken packages.

openproject configure now does similar things:

Launching installer for openproject...
Selected addons: legacy-installer mysql apache2 repositories smtp memcached openproject
[legacy-installer] ./bin/configure
[mysql] ./bin/configure
E: Unable to correct problems, you have held broken packages.

In a web browser, the installation just shows a “Powered by OpenProject” greeting page and nothing else (it did, before the initial configure…)

/var/log/openproject (symlink of the /opt/openproject/log folder) does not hold any logs of this.

There’s also no “configure” file in the bin folder. Maybe that’s some ruby stuff that I don’t understand. I could dig deeper, but I guess upgrading OP from the oldstable 6.15 to the new stable 7.0 on a current Debian setup is very common, and there will be others running into that problem.

So…is there gonna be a hotfix to enable MariaDB as a drop-in replacement to the currently enforced MySQL installation? Or is there any workaround by e.g. tweaking some installation scripts?