[pkg-bacula-devel] Bug#830999: Bug#830999: bacula-director-mysql db-config installation fails with reference to ${db_name}

Nish Aravamudan nish.aravamudan at canonical.com
Fri Jul 15 16:26:48 UTC 2016

On 15.07.2016 [17:48:08 +0200], Carsten Leonhardt wrote:
> tags 830999 + confirmed patch
> thanks
> Dear Nish,
> > That seems very right to me, I will try and test it here too.
> >
> > update_mysql_tables.in
> > update_mysql_tables_10_to_11.in
> > update_mysql_tables_11_to_12.in
> >
> > may need similar changes (they did in 7.4.1+dfsg-1, and I haven't
> > rebased yet to check if they still apply).
> I've committed a different fix to git now which doesn't need to touch
> all these files.

Great, thanks!

> > Also, depending on the source, you may want to ensure that
> > update_mysql_tables.in's db_name assignemnt properly uses the
> > ${db_name:- at db_name@} so that environment variables can be used with it.
> You mean for people not using dbconfig-common?

Yeah, iirc, the scripts end up living in /usr/share/bacula-director/ and
are sometimes referenced online as a way to manually do migrations, etc.

I believe upstream has made the referenced changed already, in a bugfix:

More information about the pkg-bacula-devel mailing list