Sorry, I was using only 'dgit -d ubuntu clone mariadb-10.1 bionic,-security' to fetch repo contents, apparently need to use 'dgit -d ubuntu clone mariadb-10.1 bionic,-security,-updates' in the future. This is the first time anybody has ever done a non-securiy upload of MariaDB to a stable Ubuntu release.
Interesting commit by Dan Streetman <ddstr...@canonical.com> in that .2. I am surprised he didn't notify the maintainer or maintainer mailing list about this in any way, nor did a merge request on salsa.debian.org to get this incorporated into git where this package is maintained. Looks like he attempted to do a clean up that I already cleaned up last year, originally introduced by Ondrej Sury's upload in the year before which he never saved in the git repository (https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/comments/11). I am not sure if I want to get tangled in a fixup again because somebody did direct uploads without working via version control and pre-upload quality testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825572 Title: April 2019 Oracle CPU might also affect MariaDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1825572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
