Using git is good. The root of the problem here was that another DD had tagged commit https://salsa.debian.org/mariadb- team/mariadb-10.1/commit/d6c1b1f9cac58d988882c3a0494c501e40d905b5 as https://salsa.debian.org/mariadb- team/mariadb-10.1/commits/debian/10.1.25-1 falsely.
In reality, the tag debian/10.1.25-1 should have been on commit https://salsa.debian.org/mariadb- team/mariadb-10.1/commit/8927cd141a3c7bbfb918d3c8f8e0e6ee6acef178 This lead me to work on the wrong revision, as I trusted the tag to not be false (never before has it been wrong). Thus the resulting thing lost the commits d6c1b1f..8927cd. The long term solution would be to code into tracker.debian.org or some similar a tool that automaticaly checks the git tags and alerts if the source uploaded to Debian does not match and the tag is wrongly placed. -- 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
