Get invovlved !
There is a lot to do, fix and improve. If you want to help, you're welcome !
There is plenty of easy tasks too, so basic packaging knowledge should be sufficient.
The description here will be very short, gathering most basic info and links that should help to solve them.
If you have any questions, just write a mail to me and we'll can get into details:
- mschorm (at) redhat.com
TO-DO list
I'll leave a list of tasks, that would be nice to have done. I'll get back to it time to time to update it.
There is a expected difficulty (from my POV) for each task which can help you orientate.
Last update: 5/2018
mariadb-connector-c
* Run the testsuite - MEDIUM
* the connector will need to run a databse during its build
* the database will pull in connector-c package
* need to ensure, that the testsuite is ran against the newly build library, instead of the one from the package
* ensure, that the testsuite will also run properly on 'fedpkg local' buid, not damaging the host machine
* http://miroslav.suchy.cz/blog/archives/2017/11/24/how_to_run_a_database_in_check_section_of_rpm_spec_file/index.html
* https://bugzilla.redhat.com/show_bug.cgi?id=1519945
* Fix the testsuite - MEDIUM
* currently, one of the tests 'ps_bugs' is failing
* Fix CMake paths for the mariadb_config binary - EASY
* the mariadb_config binary gets its paths from CMake macros, set during the build.
* They don't work for Fedora, becasue they expect to set prefix "/usr" and then only the following directories "/bin" "/lib" ...
But RPM macros only exists as a full path ( %{_libdir} means /usr/lib or /usr/lib64 )
* try %{_prefix} macro?
* Drop 'Conflicts' on F27 EOL - TRIVIAL
* Drop Scriptlet on F28 EOL - TRIVIAL
* It fixed an issue in F26 and F27. Give the users time to update (for 1 fedora relase) an then remove it.
* Check that other packages use the mariadb-connector-c-devel only - EASY
* create PRs to the rest of them
* https://bugzilla.redhat.com/show_bug.cgi?id=1486480
mariadb-connector-odbc
* Run the testsuite - MEDIUM
* same issues as with mariadb-connector-c
* the testsuite is currently not packed with the source codes: https://jira.mariadb.org/browse/ODBC-145
* OS-CI - MEDIUM
* https://fedoraproject.org/wiki/CI
* fix current test with FMF to be run againt both MariaDB and MySQL
* trigger on MariaDB, MySQL and mariadb-connector-c update too
* upstream internal RH tests
* Move unixODBC plugins to %{_libdir} subdirectory
* links to unixODBC issue
unixODBC
* Move unixODBC plugins to %{_libdir} subdirectory - MEDIUM
* https://bugzilla.redhat.com/show_bug.cgi?id=1165561
* ask the upstream, which path would be OK ( %{_libdir}/unixodbc/ ?? )
* Do it as a one update for unixODBC and all of its plugins (~5 pkgs in Fedora)
* It may be necessary to set up a path in unixODBC to search for the plugins in
mysql-connector-odbc
* Update to 8.0.11 - EASY
* Fix FTBFS - HARD ?
* Run the testsuite - MEDIUM
* same issues as with mariadb-connector-c
* Check unused patches, investigate - HARD ?
* Move unixODBC plugins to %{_libdir} subdirectory
* links to unixODBC issue
galera
* FTBFS with "-Wp,-D_GLIBCXX_ASSERTIONS" - HARD
* https://bugzilla.redhat.com/show_bug.cgi?id=1546787
* https://jira.mariadb.org/browse/MDEV-15389
* Check if requires for systemd are still needed - TRIVIAL
* Fix the Source URL - EASY
* Run the testsuite - MEDIUM
* upstream the systemd unit file - MEDIUM
Misc info
I still didn't manage to create lists of tasks for mariadb and community-mysql packages, as they are often quite complex and long-term.
But I'll add them too.