zqservices mentioned an issue in IRC.

We test a xenial install in gitlab with https://gitlab.com/aegir/provision/blob/7.x-3.x/scripts/ci-aegir-dev-ins...

I changed the mysql-server line to be mariadb-server to test this, and then apt removes mariadb again on apt-get install --fix-broken

Here's a debug log of what happens...

 apt-get install --assume-no -f  -u -o Debug::pkgProblemResolver=1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) mariadb-server-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-server-10.0:amd64 Depends on mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-10.0:amd64 0 as a solution to mariadb-server-10.0:amd64 2
  Added mariadb-client-10.0:amd64 to the remove list
  Fixing mariadb-server-10.0:amd64 via keep of mariadb-client-10.0:amd64
Investigating (0) mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-client-10.0:amd64 Depends on mariadb-client-core-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-core-10.0:amd64 0 as a solution to mariadb-client-10.0:amd64 0
  Removing mariadb-client-10.0:amd64 rather than change mariadb-client-core-10.0:amd64
Investigating (1) mariadb-server-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-server-10.0:amd64 Depends on mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-10.0:amd64 0 as a solution to mariadb-server-10.0:amd64 2
  Added mariadb-client-10.0:amd64 to the remove list
  Fixing mariadb-server-10.0:amd64 via keep of mariadb-client-10.0:amd64
Investigating (1) mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-client-10.0:amd64 Depends on mariadb-client-core-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-core-10.0:amd64 0 as a solution to mariadb-client-10.0:amd64 0
  Removing mariadb-client-10.0:amd64 rather than change mariadb-client-core-10.0:amd64
Investigating (2) mariadb-server-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-server-10.0:amd64 Depends on mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-10.0:amd64 0 as a solution to mariadb-server-10.0:amd64 2
  Added mariadb-client-10.0:amd64 to the remove list
  Fixing mariadb-server-10.0:amd64 via keep of mariadb-client-10.0:amd64
Investigating (2) mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-client-10.0:amd64 Depends on mariadb-client-core-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-core-10.0:amd64 0 as a solution to mariadb-client-10.0:amd64 2
  Added mariadb-client-core-10.0:amd64 to the remove list
Broken mariadb-client-10.0:amd64 Conflicts on mysql-client-core-5.7 [ amd64 ] < none -> 5.7.21-0ubuntu0.16.04.1 > ( database )
  Considering mysql-client-core-5.7:amd64 0 as a solution to mariadb-client-10.0:amd64 2
  Added mysql-client-core-5.7:amd64 to the remove list
  Conflicts//Breaks against version 5.7.11-0ubuntu6 for mysql-client-core-5.7 but that is not InstVer, ignoring
Broken mariadb-client-10.0:amd64 Breaks on mysql-client [ amd64 ] < none -> 5.7.21-0ubuntu0.16.04.1 > ( database )
  Considering mysql-client:amd64 0 as a solution to mariadb-client-10.0:amd64 2
  Added mysql-client:amd64 to the remove list
  Conflicts//Breaks against version 5.7.11-0ubuntu6 for mysql-client but that is not InstVer, ignoring
Broken mariadb-client-10.0:amd64 Breaks on mysql-client-5.7 [ amd64 ] < none -> 5.7.21-0ubuntu0.16.04.1 > ( database )
  Considering mysql-client-5.7:amd64 0 as a solution to mariadb-client-10.0:amd64 2
  Added mysql-client-5.7:amd64 to the remove list
  Conflicts//Breaks against version 5.7.11-0ubuntu6 for mysql-client-5.7 but that is not InstVer, ignoring
Broken mariadb-client-10.0:amd64 Breaks on virtual-mysql-client [ amd64 ] < none ->  > ( none )
  Considering mysql-client-5.7:amd64 0 as a solution to mariadb-client-10.0:amd64 2
  Added mysql-client-5.7:amd64 to the remove list
  Conflicts//Breaks against version 5.7.11-0ubuntu6 for mysql-client-5.7 but that is not InstVer, ignoring
  Fixing mariadb-client-10.0:amd64 via keep of mariadb-client-core-10.0:amd64
  Fixing mariadb-client-10.0:amd64 via keep of mysql-client-core-5.7:amd64
  Fixing mariadb-client-10.0:amd64 via keep of mysql-client:amd64
  Fixing mariadb-client-10.0:amd64 via keep of mysql-client-5.7:amd64
  Fixing mariadb-client-10.0:amd64 via keep of mysql-client-5.7:amd64
Investigating (2) aegir3-provision [ amd64 ] < 3.121+36126865.caea3ef > ( admin )
Broken aegir3-provision:amd64 Depends on mysql-client [ amd64 ] < none -> 5.7.21-0ubuntu0.16.04.1 > ( database )
  Considering mysql-client:amd64 2 as a solution to aegir3-provision:amd64 0
  Try Installing mysql-client [ amd64 ] < none -> 5.7.21-0ubuntu0.16.04.1 > ( database ) before changing aegir3-provision:amd64
Investigating (3) mariadb-server-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-server-10.0:amd64 Depends on mariadb-client-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-client-10.0:amd64 2 as a solution to mariadb-server-10.0:amd64 2
  Removing mariadb-server-10.0:amd64 rather than change mariadb-client-10.0:amd64
Investigating (3) mariadb-server [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database )
Broken mariadb-server:amd64 Depends on mariadb-server-10.0 [ amd64 ] < 10.0.34-0ubuntu0.16.04.1 > ( universe/database ) (>= 10.0.34-0ubuntu0.16.04.1)
  Considering mariadb-server-10.0:amd64 2 as a solution to mariadb-server:amd64 1
  Removing mariadb-server:amd64 rather than change mariadb-server-10.0:amd64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages were automatically installed and are no longer required:
  libcgi-fast-perl libcgi-pm-perl libdbd-mysql-perl libdbi-perl libencode-locale-perl libfcgi-perl libhtml-parser-perl libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libio-html-perl liblwp-mediatypes-perl libmysqlclient20 libterm-readkey-perl
  libtimedate-perl liburi-perl mariadb-common mariadb-server-core-10.0
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  apache2 apache2-bin apache2-data apache2-utils fontconfig-config fonts-dejavu-core libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libfontconfig1 libgd3 libjbig0 libjpeg-turbo8 libjpeg8 liblua5.1-0 libtiff5 libvpx3 libxpm4 libxslt1.1 mysql-client mysql-client-5.7
  mysql-client-core-5.7 php7.0-gd php7.0-xml unzip
Suggested packages:
  www-browser apache2-doc apache2-suexec-pristine | apache2-suexec-custom libgd-tools zip
The following packages will be REMOVED:
  mariadb-client-10.0 mariadb-client-core-10.0 mariadb-server mariadb-server-10.0
The following NEW packages will be installed:
  apache2 apache2-bin apache2-data apache2-utils fontconfig-config fonts-dejavu-core libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libfontconfig1 libgd3 libjbig0 libjpeg-turbo8 libjpeg8 liblua5.1-0 libtiff5 libvpx3 libxpm4 libxslt1.1 mysql-client mysql-client-5.7
  mysql-client-core-5.7 php7.0-gd php7.0-xml unzip
0 upgraded, 26 newly installed, 4 to remove and 181 not upgraded.
3 not fully installed or removed.
Need to get 12.4 MB of archives.
After this operation, 33.0 MB disk space will be freed.
Do you want to continue? [Y/n] N
Abort.


Comments

helmo created an issue. See original summary.

helmo’s picture

Status: Active » Needs review

Installing the 'mariadb-client' package beforehand seems to fix this issue.

zqservices’s picture

I can confirm that installing 'mariadb-client' package prior to the aegir 3 install does seem to fix this issue.

zqservices’s picture

I have confirmed that installing the 'mariadb-client' does seem to fix this issue.

helmo’s picture

Status: Needs review » Fixed

I've now also added mariadb-client to the instructions on http://www.aegirproject.org/

colan’s picture

Status: Fixed » Needs review

sudo apt-get install mariadb-server mariadb-client apt-transport-https

That makes it look mandatory to use MariaDB. Maybe we can add a comment above it:

# If you'd like to use MariaDB instead of MySQL, install it first. Otherwise, you can skip this step.

I was interested in running it for a while because it's more open-source friendly, but I've switched back to MySQL for the simple reason that Canonical supports it (and not MariaDB) on Ubuntu.

helmo’s picture

Thought Ubutu had also changed the default like Debian did ...

We could change it to default-mysql-server default-mysql-client but that was introduced in artful 17.10 .

But maybe we can just remove it ... I remember that it was needed in the past to get a successfull install, but just installed on 16.04, 18.04 and Debian stretch without it :)

helmo’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.