[Maria-developers] TokuDB QA issues - should we fix them ourself or are any of the upstream devs listening?
Hello! While working on the Debian packaging I noticed multiple minor QA level issues that stem from problems in TokuDB: - Debian builds are not reproducable due to random embedded build id in the TokuDB plugin, see https://reproducible.debian.net/dbd/unstable/amd64/mariadb-10.0_10.0.23-1.di... (subpage of https://reproducible.debian.net/rb-pkg/unstable/amd64/mariadb-10.0.html) - Lintian complains about missing man page for binary tokuftdump. Also Lintian complains about outdated autotool files in TokuDB sources. For both see https://lintian.debian.org/maintainer/pkg-mysql-maint@lists.alioth.debian.or... I'd like to see these fixed. What is the best process to proceed with these? File an issue at mariadb.org/jira or https://github.com/percona/PerconaFT or what..? Please advice. - Otto MariaDB Foundation
Hi Otto, For one, Matt Griffin <matt.griffin@percona.com> no longer works at Percona (according to his Linkedin profile anyway)
While working on the Debian packaging I noticed multiple minor QA level issues that stem from problems in TokuDB:
- Debian builds are not reproducable due to random embedded build id in the TokuDB plugin, see https://reproducible.debian.net/dbd/unstable/amd64/mariadb-10.0_10.0.23-1.di... (subpage of https://reproducible.debian.net/rb-pkg/unstable/amd64/mariadb-10.0.html)
- Lintian complains about missing man page for binary tokuftdump. Also Lintian complains about outdated autotool files in TokuDB sources. For both see https://lintian.debian.org/maintainer/pkg-mysql-maint@lists.alioth.debian.or...
I'd like to see these fixed. What is the best process to proceed with these? File an issue at mariadb.org/jira or https://github.com/percona/PerconaFT or what..?
I’m going to guess the best way is to report them upstream. And I would wait a month to see what the status of the bugs are, and in the case they are not addressed, make a man page for tokuftdump (this isn’t hard to do; and it might also make us want to update our man pages) As for the reproducible builds, what is the fix to this? I’m glad that the above issues are not related to the MariaDB Server merge of TokuDB (er, PerconaFT), but are generic issues -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
I apologize for the delay in responding, been on holiday for the last few weeks. Matt Griffin is no longer with Percona, for now, I am the contact for all things TokuDB related and for Debian/Ubuntu distro packaging. To date, we have not packaged TokuDB with Percona Server into a distro and thus have not yet run into the issue(s). The TokuDB project has been merged directly into the Percona Server project tree on github and that is where all active development of TokuDB will be performed. The former ft-index project, now known as PerconaFT is still a standalone project at github.com/percona. Currently, I have quite a backlog of TokuDB work so to be honest, the fastest way to get this fixed would be to file a bug on launchpad at https://launchpad.net/percona-server and submit patches to whatever projects need fixing (TokuDB in Percona Server or the PerconaFT project). I would review it with our release team and get it merged immediately if there are no issues. Alternately, MariaDB can patch their fork directly but then have another point to watch during merges. On Sat, Jan 2, 2016 at 12:47 AM, Colin Charles <byte@aeon.com.my> wrote:
Hi Otto,
For one, Matt Griffin <matt.griffin@percona.com> no longer works at Percona (according to his Linkedin profile anyway)
While working on the Debian packaging I noticed multiple minor QA level issues that stem from problems in TokuDB:
- Debian builds are not reproducable due to random embedded build id in the TokuDB plugin, see
https://reproducible.debian.net/dbd/unstable/amd64/mariadb-10.0_10.0.23-1.di...
(subpage of https://reproducible.debian.net/rb-pkg/unstable/amd64/mariadb-10.0.html)
- Lintian complains about missing man page for binary tokuftdump. Also Lintian complains about outdated autotool files in TokuDB sources. For both see https://lintian.debian.org/maintainer/pkg-mysql-maint@lists.alioth.debian.or...
I'd like to see these fixed. What is the best process to proceed with these? File an issue at mariadb.org/jira or https://github.com/percona/PerconaFT or what..?
I’m going to guess the best way is to report them upstream. And I would wait a month to see what the status of the bugs are, and in the case they are not addressed, make a man page for tokuftdump (this isn’t hard to do; and it might also make us want to update our man pages)
As for the reproducible builds, what is the fix to this?
I’m glad that the above issues are not related to the MariaDB Server merge of TokuDB (er, PerconaFT), but are generic issues -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
-- George O. Lorch III Software Engineer, Percona US/Arizona (GMT -7) skype: george.ormond.lorch.iii
participants (3)
-
Colin Charles -
George Lorch -
Otto Kekäläinen