I don't why, but my databases are not only information_schema and mysql, but there is also a performance_schema, in addition to the database dedicated to the application:
So, when you use bin/pkgi-mysqlbackup, there is more than one database to dump (and perhaps separated by a carriage return), and only the first one is dump (in my case, it is empty, giving a 424 bytes-length gzipped file).
I don't why, but my databases are not only information_schema and mysql, but there is also a performance_schema, in addition to the database dedicated to the application:
mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | app | +--------------------+
So, when you use bin/pkgi-mysqlbackup, there is more than one database to dump (and perhaps separated by a carriage return), and only the first one is dump (in my case, it is empty, giving a 424 bytes-length gzipped file).
I tried this in mysql/bin/pkgi-mysqltools:
And it worked.
I still have to learn how to do a pull request ;)