Hello!
As you can see in the git blame of debian/rules, I did not do any changes to
the line with -pie:
https://salsa.debian.org/mariadb-team/mariadb-10.1/blame/ubuntu-17.10/debian/rules
I think I found out what has happened. If I look at the changelog found
in via 'pull-lp-source -d mariadb-10.1 artful-release' it says:
****
mariadb-10.1 (10.1.25-1) unstable; urgency=medium
* New upstream version 10.1.25
* Update quilt patches on top of mariadb-10.1.25 release
* Explicitly add dh_systemd_start snippets to mariadb-server-10.1
because it's all messed up with different name for sysvinit ('mysql')
and systemd ('mariadb') (Closes: #865870)
* Don't disable PIE, it's enabled by upstream anyway (Closes: #865737)
* Add default socket location for client (Closes: #864662)
-- Ondřej Surý <[email protected]> Sun, 30 Jul 2017 14:15:48 +0200
****
While in the Debian git repository what was committed and tagged as the
10.1.25-1 upload is:
****
mariadb-10.1 (10.1.25-1) unstable; urgency=medium
* New upstream version 10.1.25
* Update quilt patches on top of mariadb-10.1.25 release
-- Ondřej Surý <[email protected]> Wed, 12 Jul 2017 09:39:19 +0200
****
(source https://salsa.debian.org/mariadb-
team/mariadb-10.1/commit/d6c1b1f9cac58d988882c3a0494c501e40d905b5)
After that the next commit was importing 10.1.26 so I had no reason to
suspect this would be a wrong commit.
So the mistake here is that I have been working off a false base while
preparing the debdiff. I could have spotted this if I would have double
checked the contents of git by downloading the package and extracting it
over the repository and running git diff.
The person who handled the Launchpad issue could also have spotted that
what they were about to upload did not match the output of the debdiffs
I attached and linked to.
So I have not intentionally done anything to pie or any of the other
things you said. My commits have none of those changes. They have been
introduced when the person doing the Ubuntu upload has recreated the
debdiffs using a different base version.
I guess we need to start safeguarding the git contents better and run
regular syncing/checking scripts that ensure that whatever is uploaded
to Debian/Ubuntu is tracked in git and not done outside of it, eroding
the whole maintenance process.
--
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
