Backport of bacula 7.4.3+dfsg-1
Hi,
we (the Bacula Packaging Team) have prepared a backport of bacula
7.4.3+dfsg-1 (which is in testing), but it contains a small change (see
the attached diff or ¹). The change is necessary to ensure that the old
bacula-director daemon is stopped and we don't end up with the old and
new one running on the system. The init file is not in the same package
as the daemon, so the test for "same executable" via "start-stop-daemon
--exec" can fail because the binary could already have been replaced by
the newer one.
Is that an acceptable change from the version in testing and can I go
ahead and upload to backports?
Carsten
(1) https://anonscm.debian.org/cgit/pkg-bacula/bacula.git/diff/?h=jessie-backports&id=b2285c59c04b843af9f387e26999b0dd9df147a8&id2=3620d6a589347707f9c7934de6128b9880915d5b
diff --git a/debian/bacula-director-common.bacula-director.init b/debian/bacula-director-common.bacula-director.init
index f8884aa..8557074 100644
--- a/debian/bacula-director-common.bacula-director.init
+++ b/debian/bacula-director-common.bacula-director.init
@@ -76,7 +76,7 @@ do_start()
do_stop()
{
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \
- --retry TERM/30/KILL/5 --exec $DAEMON -- -c $CONFIG $ARGS
+ --retry TERM/30/KILL/5 --name `basename $DAEMON`
}
diff --git a/debian/changelog b/debian/changelog
index d16fdec..cd75376 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+bacula (7.4.3+dfsg-1~bpo8+1) jessie-backports; urgency=medium
+
+ * Rebuild for jessie-backports.
+ * Fix bacula-director init script to make sure the daemon is restarted
+ on upgrades
+
+ -- Carsten Leonhardt <leo@debian.org> Wed, 03 Aug 2016 12:25:50 +0200
+
bacula (7.4.3+dfsg-1) unstable; urgency=medium
* New upstream release
Reply to: