[debian-mysql] initial feedback on mariadb

Otto Kekäläinen otto at fsfe.org
Fri Aug 16 08:51:59 UTC 2013


Hello,

Sorry for the delay on implementing this feedback. I assume we are all
back now online, have time to look into this and get the packages to
experimental?

2013/5/14 Nicholas Bamber <nicholas at periapt.co.uk>:
> 1.) The debian/copyright file has a non-standard  format. See
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> When the format is corrected we can do some stuff with license-reconcile.
>
> You can find my debian/copyright file and license-reconcile file in
> git://git.debian.org/git/pkg-mysql/packages/mysql.git

I merged the files to my best knowledge. I'll ping Kristian from
MariaDB to add more MariaDB mentions.

> 2.) There is no point having Norbert Tretkowski as an uploader.

Removed.

> 3.) The build dependencies includes stuff I am sure are no longer
> needed. As a first stab consider what I had in git:
> debhelper (>= 9), libaio-dev[linux-any], libncurses5-dev (>= 5.0-6),
> perl, libwrap0-dev (>= 7.6-8.3), zlib1g-dev (>= 1:1.1.3-5),
> libreadline-dev, po-debconf, psmisc, chrpath, gawk, bison, lsb-release,
> hardening-wrapper, cmake, gcc-4.4 [any-i386], g++-4.4 [any-i386]
> Notice in particular no doxygen, ghostscript, automake. The gcc-4.4
> stuff was one of those oracle bugs we're complaining about so may not be
> needed in MariaDB. I have not yet checked whether you have enabled the
> stuff that required libaio-dev.

See message http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005611.html
from Kristian of MariaDB why libreadline-gplv2-dev is required (and
therefore I earlier added it to the build dependencies).

I am now experimenting with your stab and evaluating the list at
https://wiki.debian.org/Teams/MySQL/BuildDependencies
So far so good.

> 4.) Note we have a new standards version 3.9.4. We have no excuse for
> not conforming to that before uploading.

Updated 3.9.3->3.9.4. Nice progress, as I started out with version 1.0 :)

> 5.) THe naming of the packages (and associated clauses) has all the
> issues that the current packages have. I tried discussing what to do
> about it
> (http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2012-June/004778.html)
> and the issues with the contents of the packages
> (http://wiki.debian.org/Teams/MySQL/WhichPackage). My considered
> response is in the git repository.

This is a more challenging issue. It seems that the message
http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2012-June/004778.html
lists lots of plans what to do to get into an ideal state. I will
think about it, but I am afraid reaching the ideal state would require
quite a lot of work.

Changes are visible at https://github.com/ottok/pkg-mariadb/commits/master

Next I'll update the upstream 5.5-29->5.5.32 and do a lot of testing
on the end result to nail down possible issues we haven't considered.



More information about the pkg-mysql-maint mailing list