packaging: cannot merge config files on system with ostree

[sergey-safarov]

On Fedora Core when installed Kamailio and then installed additional packages then receive error

[root@caloes-1 ~]# journalctl -flu ostree-boot-complete.service -o cat
Starting ostree-boot-complete.service - OSTree Complete Boot...
error: ostree-finalize-staged.service failed on previous boot: During /etc merge: Modified config file newly defaults to directory 'kamailio', cannot merge
ostree-boot-complete.service: Main process exited, code=exited, status=1/FAILURE
ostree-boot-complete.service: Failed with result 'exit-code'.
Failed to start ostree-boot-complete.service - OSTree Complete Boot.
ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed.
ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed.
ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed.

Suggestion place default Kamailio config into dedicated package "kamailio-config-default".

[miconda]

Can you present in more details what exactly the problem is? From the logs (and not a fedora user) is hard to figure out.

[sergey-safarov]

This is not related to C source code.
This is related to the file system used by OS.
https://en.wikipedia.org/wiki/OSTree

I think, more prefer to use CFGFILE variable in the /etc/sysconfig/kamailio to define a custom config file, like

[root@ip-100-85-120-8 ~]# head /etc/sysconfig/kamailio 
CFGFILE=/etc/sbc/kamailio.cfg

#
# Kamailio startup options
#

# Amount of shared memory to allocate for the running Kamailio server (in Mb)
SHM_MEMORY=128

# Amount of per-process (package) memory to allocate for Kamailio (in Mb)

And when I "upgrade" or "install" packages then it will not conflict with files (symbolic links) manually placed on the file system.

[miconda]

IMO, at least the default config should be part of main kamailio package, it is how most packages do afaik (ok, on debian/ubuntu). Maybe that is going to be changed, but for the moment it seems to be the norm.

On the other hand, I am not leveraging the packages that much, if something new is required by recent distros, then I am open to changes if there are not objections from others or better proposals.

[github-actions]

This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks.