Comment 5 for bug 1577858

@Kern, quick question. We can obviously backport http://www.bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-7.4&id=36d647345df3c98a2cc1ad24af31e73aaff4a2e9 [note the bug referenced in the commit message seems to be incorrect? http://bugs.bacula.org/view.php?id=1849 ].

But that only helps with fresh installs of bacula in 16.04.

If a user is upgrading from 14.04 or 15.10 -> 16.04 and going through the MySQL transition, we also need to update their tables (aiui). Would that normally be done by an update_mysql_tables call? Should there have been a corresponding change in the upstream commit?

Thanks!
-Nish