[pkg-bacula-devel] [bacula] 02/04: Move bscan into it's own package, making bacula-sd-DBTYPE obsolete
sven at svenhartge.de
Tue Jul 26 08:33:44 UTC 2016
On 26.07.2016 10:02, Carsten Leonhardt wrote:
>> Right now the systemd parts have been disabled by you in debian/rules
>> and the units this still get installed into the bacula-director-DBTYPE
>> package and dh_systemd_start is run (because no override-section exists).
>> The init-script on the other hand is installed into bacula-director and
>> dh_installinit does its job. Right now, this situation will lead to
>> chaos at configuration time.
> I think the last commit ("Move bacula-director.service to package
> bacula-director") fixes this.
Yes, it does.
But now we may run into a problem if the director is restarted before
bacula-director-DBTYPE is configured correctly. For example we may miss
the needed DB updates or the new libbaccats.so is not yet unpacked.
This is why in the original packages the prerm/postinst of
bacula-director-DBTYPE had a hardcoded invoke-rc.d to stop and start the
directord, while the init-script was in bacula-director-common.
Maybe we need a pre-depends on bacula-director-DBTYPE? (Ugly, I think.)
Or the init-script/systemd unit has to stay inside
bacula-director-DBTYPE to ensure the directord is (re)started at the
BTW: the wrong dependency on bacula-common-pgsql appears in
bacula-director as well:
Depends: bacula-common (= 7.4.3+dfsg-3), bacula-director-sqlite3 (=
7.4.3+dfsg-3) | bacula-director-pgsql (= 7.4.3+dfsg-3) | bacula-di
rector-mysql (= 7.4.3+dfsg-3), bsd-mailx | mailx, lsb-base,
init-system-helpers (>= 1.18~), bacula-common-pgsql, libc6 (>= 2.14), libc
ap2 (>= 1:2.10), libgcc1 (>= 1:3.0), libssl1.0.2 (>= 1.0.2d), libstdc++6
(>= 4.1.1), libwrap0 (>= 7.6-4~), zlib1g (>= 1:1.1.4)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the pkg-bacula-devel