Jan, are you willing to test the packages once I build them ? I do not yet use EL7 anywhere so I cannot do any form of local testing, hence my reluctance to push EPEL7 packages

No problem, I can test it immediatelly if it will be in koji. May be from git too. :-)

EL7 is similar to Fedora 18, so you can build current Fedora package.

If you need, I can try to build git/master against EPEL7.

I'll be glad to help test in an EL7 environment.  Thanks for taking the lead on this one, Manuel. ;)

Build Info: http://koji.fedoraproject.org/koji/buildinfo?buildID=597031

Please test and provide feedback. If all is well, I will push those to testing
Thank you

Works perfectly. Thank you.

Btw, there is a new version 1.3.0 (see bz#1070136). Any plans to update to this version?

Excellent question. So far I've just maintained the EPEL branches, following Ville Skyttä's lead. I guess I could try to update the package, at least for rawhide and EPEL7....

Success on CentOS 7.

Major: I assume you meant the version I just built, not 1.3.0, right ?
In this case, I suggest the followin plan:
 - push the recently built 1.2.0 to epel7-testing
 - push 1.3.0 to rawhide
 - wait until 1.2.0 can be promoted to stable
 - build, test and assuming OK, push 1.3.0 to epel7-testing
 - maybe push to older distributions ?
Does it sound reasonable?

That sounds reasonable.  I'm waiting on one GitHub user to finish up a pull request and I'll probably make a new version number since the remaining patches since 1.3.0 have been baking for quite some time.

Would you want to skip 1.3.0 and grab the next version for rawhide?

Sure, there is no pressure ( AFAIK ). We've been using 1.2.0 for long enough, I doubt a day or a week more will matter. But you know that since you are a maintainer, you can just push yourself new versions/packages whenever you want, right ? :)

I'll be glad to do it!  I didn't want to step on your toes if you were already on it. ;)

nice. we JUST avoided a deadlock, waiting on each other :)

Hah, I'll push a new version into koji as soon as this GitHub PR is done.

mysqltuner-1.2.0-7.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/mysqltuner-1.2.0-7.el7

Package mysqltuner-1.2.0-7.el7:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing mysqltuner-1.2.0-7.el7'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4464/mysqltuner-1.2.0-7.el7
then log in and leave karma (feedback).

mysqltuner-1.2.0-7.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.