I have now adopted a workflow where I use dgit to verify that what is in the packaging git matches what is uploaded.
Example: git clone salsa..../mariadb-10.1.git salsa dgit -d ubuntu clone mariadb-10.1 bionic,-security distro cp -ra distro/* salsa cd salsa git diff This will make me able to catch is another maintainer has tagged a release that was not actually that release. @xnox: the autopkgtests have been fixed via commits https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/96d3f8abcbe51894d0a5f7c7cadd5219e0dc2823 https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/596c2581176102b29751786e5d8fac05dde3a3e4 -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
