Comment 6 for bug 1605493

Sorry for the long delay in replying. It seems that at some point somebody who did the upload has had some mixup, and used the debian/* contents from the mariadb.org upstream and not from the sources I provided.

The mixup is understandable. When you untar the upstream package, there is already some contents in debian/* (upstream legacy). The uploader needs to remove that, import the debian/* from the current package in Ubuntu and then apply the debdiff I provided to get the new changelog entry etc.

From now on I will only provide git-buildpackage branches and ask the uploader to use them. That is less error prone, as the uploader does not need to untar and move folders and apply patches manually at all. Running git-buildpackage is all that is needed, and everything can be verified thanks to the pristine-tar and gpg signatures provides by git-buildpackage.

What to do with the mixed up mariadb-5.5 in 14.04 then? I don't know. I will continue to maintain the branch ubuntu-14.04 at https://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/log/?id=refs/heads/ubuntu-14.04 how it was and should be. I would hope the mariadb-5.5 in Ubuntu official repos would have the mixup cleaned away, but I don't have resources at the moment to test if that causes some regressions and if it is feasible to do.