Fix scripts which cause set date & time failure at first boot

At first boot, alarm-server will failed to listen on the key
db/system/timechange changed event because it doesn't exist.

However, once you try to set date & time from "settings", system server
will create that key, and after alarm-server restarted, set date & time
works well.

Change-Id: I0dd5c5ff8fef8fb0c8aab5d3864bc5cb173fc035
Signed-off-by: Chengwei Yang <chengwei.yang@intel.com>

diff --git a/packaging/alarm-manager.spec b/packaging/alarm-manager.spec
index bce6ae9..3af2b62 100644 (file)
--- a/packaging/alarm-manager.spec
+++ b/packaging/alarm-manager.spec
@@ -91,12 +91,12 @@ install -m0644 %{SOURCE101} %{buildroot}%{_libdir}/systemd/system/
 ln -sf ../alarm-server.service %{buildroot}%{_libdir}/systemd/system/multi-user.target.wants/alarm-server.service
 
 
-%preun
+%preun -n alarm-server
 if [ $1 == 0 ]; then
     systemctl stop alarm-server.service
 fi
 
-%post
+%post -n alarm-server
 /sbin/ldconfig
 
 heynotitool set setting_time_changed -a
@@ -108,7 +108,7 @@ if [ $1 == 1 ]; then
     systemctl restart alarm-server.service
 fi
 
-%postun
+%postun -n alarm-server
 /sbin/ldconfig
 systemctl daemon-reload
 if [ "$1" == 1 ]; then