[pkg-bacula-devel] [bacula] 02/04: Move bscan into it's own package, making bacula-sd-DBTYPE obsolete
Carsten Leonhardt
leo at debian.org
Mon Aug 1 01:01:46 UTC 2016
Hi,
> One minor thing: I think bacula-director could only Recommend
> bacula-bscan, just like bacula-sd does, because it is technically not
> needed but just a strong enhancement of the package.
you mean the metapackage bacula-server? I think the default for people
not picking the packages they want by themselves it's better to install
everything except bat. They won't mind the little extra diskspace taken.
[after switching from sqlite3 to mysql)
> I now notice that needrestart wants to restart bacula-director after the
> installation, because it detects the usage of the now-deleted sqlite3
> library.
As per my observations, the director is not stopped and started. But
even if it is started because needrestart is used, it will not work
because when switching from sqlite3 to mysql or pgsql the configuration
isn't compatible.
> I am of the opinion right now, that if the admin decides to switch the
> DBTYPE, then it is his duty to change the config-file to reflect that.
> The packaging logic can only provide the initial configuration at first
> installation, everything else would be too complex to do for such a
> marginal use case.
Yes, agreed. Anyway the database will be empty after a switch, if
someone wants to switch the database type, they are on their own.
> Aside from that, the packaging is now in really good shape and all
> dependencies work as they should.
My tests agree with that, that's why I've uploaded the new version to
experimental a few minutes ago.
Carsten
More information about the pkg-bacula-devel
mailing list