It is easiest if we list the commits that caused the regressions, and then selectively revert them.
Here are some I found quickly: - -pie https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/b4fe91faee29bc1597e2876e1c2cc6bdd162fb66 - dh_systemd_start removal https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/9f49e4b494f3dad8c403972996f7a1ebceb4b34f At least the commits above are well documented and will help to understand if reverting them is the truly correct thing to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757107 Title: Security update 10.1.30-0ubuntu0.17.10.1 regresses smoke test, mariadb not started upon install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
