Bug#745135: Top 10 reasons you should sponsor MariaDB 10.0 into Debian this weekend (Re: Bug#745135: RFS: mariadb-10.0/10.0.13-1 [ITP] -- Latest version of worlds most popular non-Oracle database)
2014-09-23 10:28 GMT+03:00 Guido van Steen <vansteen@users.sourceforge.net>:
> I would like Mariadb to be accepted before the freeze as well. However
> I am not a DD, so I cannot sponsor it myself.
Thanks for your feedback!
> In order to get Mariadb sponsored you might handle at least the
> Lintian error (https://lintian.debian.org/tags/build-depends-on-obsolete-package.html,
> http://labs.seravo.fi/~otto/mariadb-repo/logs/mariadb-10.0/mariadb-10.0_10.0.13-1_amd64.build-d992d30.log).
> If it is a false positive, please explain why.
You are talking about:
E: mariadb-10.0 source: missing-build-dependency dpkg-dev (>= 1.16.1~)
Isn't this a bug in Lintian? The package dpkg-dev is part of
build-essential and there should not be any need to specify it. Why
does Lintian add the version number, what is special about 1.16.1~ ?
The package builds ok on sid, wheezy, trusty and precise, which most
have older dpkg-dev than those.
The changelog of dpkg-dev has under 1.16.1 from September 2011:
* dpkg-buildflags now returns hardening flags by default. Closes: #489771
They can be individually enabled/disabled via DEB_BUILD_MAINT_OPTIONS,
see dpkg-buildflags(1). Thanks to Kees Cook for his help.
I did the commit
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=f577ead67affc143989b1373b8a15a2824805033
to replace the old hardening-wrapper, because Lintian complained that
perfectly well working system was deprecated. What does Lintian want
me here, to specify a versioned dpkg-dev dependency on a version that
has been in Debian for over 3 years?
Reply to: