[pkg-bacula-devel] Bug#1108272: Bug#1108272: bacula-director-pgsql: update_postgresql_tables script fails due to bad shell quoting
Carsten Leonhardt
leo at debian.org
Sat Jun 28 21:12:06 BST 2025
Hi Wouter,
Wouter Verhelst <w at uter.be> writes:
> So debconf-show bacula-director-pgsql shows me this, amongst others:
>
> * bacula-director-pgsql/dbconfig-upgrade: false
>
> Which indicates that perhaps, somehow, it is indeed disabled. This is
> not what I wanted.
>
> I don't remember manually setting this option. When I run
> "dpkg-reconfigure -plow bacula-director-pgsql" to correct it, it asks me
> if I want to *reinstall* the database (which I read as "throw away
> everything in your catalog away and start from scratch", which is a hard
> "no"), but does not ask me the question about upgrading.
>
> This feels wrong on so many levels. I'm not sure whether this is decided
> in dbconfig-common or in bacula, but if the latter, please fix that :-)
I'd recommend that you use an editor to set
dbc_upgrade='true'
in /etc/dbconfig-common/bacula-director-pgsql.conf. That will make
future upgrades work.
In the debconf information included in the original bug report the
corresponding line starts with an '*'. That probably means that it
was set to deviate from the default via debconf. How that happened is a
question that will be hard to answer. Which version of bacula did you
start your deployment with originally?
Groetjes,
Carsten
More information about the pkg-bacula-devel
mailing list