I had a feeling that not only mydumper is suffering from that, but apparently I'm wrong.
mydumper has a build option not to include the file resulting in less functional, but working package. I don't think they will fix that anytime soon, since their resolution is to disable this part of code: https://bugs.launchpad.net/mydumper/+bug/1276743 . I used this approach in my new build of the package, which is waiting for my sponsor to review and upload it. In case anyone else is interested in doing that the package is available on mentors.d.n [1]. [1] https://mentors.debian.net/package/mydumper 2015-07-02 12:44 GMT+02:00 Robie Basak <robie.ba...@ubuntu.com>: > On Tue, Jun 30, 2015 at 05:55:04PM +0200, Mateusz Kijowski wrote: > > http://bugs.mysql.com/bug.php?id=70672 seems to be the reason. Perhaps > we > > can hack the mysql package to include it? > > If it's not part of the public API, then I don't think it's appropriate > for the package to include it. We'd effectively be forking the MySQL > ABI, breaking compatibility with the rest of the ecosystem and generally > causing future pain and confusion. > > This confusion is what I believe upstream are busy trying to fix by > better clearly defining the available API to avoid future compatibility > problems. It seems like you've fallen on the wrong side of this. > > Can you work with upstream to get the functionality you need included as > part of the public API? >