Change dependency on callmgr.service 20/314820/1 accepted/tizen_unified_dev accepted/tizen/unified/20240808.160400 accepted/tizen/unified/dev/20240808.094928 accepted/tizen/unified/toolchain/20240812.133501 accepted/tizen/unified/x/20240809.012938 accepted/tizen/unified/x/20240809.015623 accepted/tizen/unified/x/asan/20240813.231944
authorŁukasz Stelmach <l.stelmach@samsung.com>
Fri, 19 Jul 2024 16:59:07 +0000 (18:59 +0200)
committerŁukasz Stelmach <l.stelmach@samsung.com>
Fri, 19 Jul 2024 16:59:07 +0000 (18:59 +0200)
commite5927cfe0852f9a4fb6276aed6670ad6603e9f18
tree5696a5499410a2e85dce8294d40c061f6b989111
parent05f7f87745a69b89b7c68bc6c4fd78f155a74e8c
Change dependency on callmgr.service

Due to a bug[1] in systemd missing callmgr.service didn't prevent
lbs-server.service from starting. The bug was fixed in systemd 254 and
lbs-server does not start whith the hard dependency on callmgr. Changing
the dependency type from Requires to Wants makes lbs-server start properly
under the new systemd.

[1] https://github.com/systemd/systemd/issues/11338

Change-Id: I4e3df83f1afa9ed983d6af7b2f9cb5802bd7b2d0
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
packaging/lbs-server.service