Fix can not write memory backend key at image creation stage

Whenever vconf to write the memory backend key, it first check if
vconf was initialized, /tmp/vconf-initialized exists, which will be
created by vconf-init at system boot up. However, this is not true at
image creation stage, so all the afterwards installed packages will
created *empty* memory backend keys. And the whole image broken.

This is a temporary workaround, which creates /tmp/vconf-initialized in
%post script, a later fix which remove the initialized check will be
merged later.

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

diff --git a/packaging/vconf.changes b/packaging/vconf.changes
index 991d1518339940bbd5249c44d7cb5eb8314ddba7..e3c0f8500ac91393d77ef96c7e2d713e0b9158d9 100644 (file)
--- a/packaging/vconf.changes
+++ b/packaging/vconf.changes
@@ -1,3 +1,6 @@
+* Web Sep 25 2013 Chengwei Yang <chengwei.yang@intel.com>
+- Fix can not write memory backend key at image creation stage
+
 * Fri Sep 20 2013 Anas Nashif <anas.nashif@intel.com> accepted/tizen/20130913.063407@c8eb1a2
 - cleanup spec and changelog
 

diff --git a/packaging/vconf.spec b/packaging/vconf.spec
index 6631f4095115308aa5946ff44bb94d4cc19cf21c..7dd6f25e6f09a364fccf635dd589ad9e121682ba 100755 (executable)
--- a/packaging/vconf.spec
+++ b/packaging/vconf.spec
@@ -57,6 +57,7 @@ install -m0644 %SOURCE2 %{buildroot}%{_prefix}/lib/tmpfiles.d/
 ln -sf ../vconf-setup.service %{buildroot}%{_unitdir}/basic.target.wants/
 
 %post
+touch /tmp/vconf-initialized
 /sbin/ldconfig
 systemctl daemon-reload