Am 15.07.20 um 23:54 schrieb Hilmar Preuße:
This issue seems to be solved in the (to be released) 1.3.7 version [1] & [2], but not in 1.3.6. We'll release next Debian release w/ 1.3.7. Should we try to get the issue solved for next buster point release? In this case the issue should be at least severity important.
Thank you! It looks like the upstream fix still depends on the mysql/mariadb client library; without compiling and testing it I can't say whether that will make it work.
If/when you'll have a package based on the new upstream, I can gladly test it.
I'm not sure this warrants an update for the next point release; it appears this functionality is used very rarely.
Kind regards -- Andreas Trottmann
